Selecting "Shut Down" leads to a reboot

[Nick]

Shut Down not longer functions normally. Ubuntu appears to go through the shutdown processor normally but once power is turn off the system then automatically turns itself on again and boots up. The only way to keep the system off is to pull the cord when the system goes and before it comes back to life. I've been running this same box on Ubuntu since Dapper and I've never had any problems with Shut Down.

$ uname -a
Linux hal3200 2.6.24-16-generic #1 SMP Thu Apr 10 13:23:42 UTC 2008 i686 GNU/Linux

dmesg.log attached

[Nick (morrownr)]

lspci-vvnn.log attached

[Nick (morrownr)]

dmidecode.log attached

[Saivann Carignan (oxmosys)]

Thank you for your bug report. This bug is actually filed against usplash. In order to make sure that this bug is caused by usplash, can you boot your computer with usplash disabled and verify if the bug can be reproduced? You can do this by following these steps :

 1. Press Esc during Grub boot delay to access the boot menu.
 2. Select your actual Ubuntu boot line and press "e" to edit it.
 3. Select the "kernel" line and press "e" to edit it.
 4. At the end of the line, remove "splash" and "quiet" and press "enter".
 5. Type "b" to boot the custom boot line.

Also I wonder if ubuntu would shutdown correctly if you type "sudo shutdown -h now" in a terminal.. Can you also test this?

[Nick (morrownr)]

The 5 step process you listed did not change anything. The bug is
still present.

"sudo shutdown -h now" gives the same results. The bug is still
present. After shutdown the machine automatically starts again and
boots up. Shut Down is not effective at shutting the system down.

In the original post I did not list a subsystem as I am not very
familiar with the various subsystems (I wish there was a guide) but if
I had to guess I'd say this is a acpi bug.

FWIW: I've been watching the ubuntu forums and I've been seeing other
talk about this problem. Often it is hard to recognize that this is
the bug being talked about as folks are unsure what is going on. I
have went to great lenghts to check/change bios settings in an effort
to find any indication of what may be causing this but so far I am at
a loss. I wish there was a good guide to acpi but everything I have
found assumed a person already has a lot of knowledge about acpi.

Cheers.

On Wed, May 28, 2008 at 12:26 PM, Saïvann Carignan <email address hidden> wrote:
> Thank you for your bug report. This bug is actually filed against
> usplash. In order to make sure that this bug is caused by usplash, can
> you boot your computer with usplash disabled and verify if the bug can
> be reproduced? You can do this by following these steps :
>
> 1. Press Esc during Grub boot delay to access the boot menu.
> 2. Select your actual Ubuntu boot line and press "e" to edit it.
> 3. Select the "kernel" line and press "e" to edit it.
> 4. At the end of the line, remove "splash" and "quiet" and press "enter".
> 5. Type "b" to boot the custom boot line.
>
> Also I wonder if ubuntu would shutdown correctly if you type "sudo
> shutdown -h now" in a terminal.. Can you also test this?
>
> ** Changed in: usplash (Ubuntu)
> Assignee: (unassigned) => Saïvann Carignan (saivann)
> Status: New => Incomplete
>
> --
> Selecting "Shut Down" leads to a reboot
> https://bugs.launchpad.net/bugs/234700
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[Saivann Carignan (oxmosys)]

Thanks for your fast confirmation. Since this bug can be reproduced with usplash disabled, it can't be a usplash bug. I change the package to linux which I suspect to be the good one but if you find a more appropriate package name, don't hesitate to change it again. Also, if you find any workaround which fixes this issue, it might be very useful if you keep this bug report updated. I also suggest that you take a look at BIOS options since I really suspect that this bug has something to do with the BIOS of your computer. Thanks for your contribution to ubuntu so far.

[Nick (morrownr)]

I've continued testing. I found an individual that has a system that is almost identical to mine. The mb and bios are the same and we matched bios settings. Shutdown on his system seems to work fine but mind still produces a reboot instead of shutdown. There are 2 differences that I'm going to explore further as I have time:

My system:

- Is connected to the keyboard, mouse and monitor via KVM.
- ATI 9600 video card

His system:

- No KVM, all connected directly to system ports.
- NVidia 7600 video card

This is strange.

[Saivann Carignan (oxmosys)]

Nick : This is interesting! Can you also provide a "sudo lspci -nnvv" for that computer so we can compare?

[Nick (morrownr)]

Saivann, I am attaching the results of "sudo lspci -nnvv" from the person who has the indentical mb, bios and settings. The filename is "lspci." His system shutdown with 8.04 works as expected.

FYI: I temporarily removed the KVM from my setup this morning for testing. It appears the Avocent KVM is not the problem as shutdown continues causing a reboot instead of the normal shutdown.

Recap: I have used this P4 Northwood system for about 3 years. I built the system using Linux compatible parts and from Dapper to 7.10 both Reboot and Shutdown worked as we would expect. I was unable to test 8.04 during development so I can't say for sure when this new behavior started. I am down to the point now where the only system differences between my system and the nearly identical one where shutdown is working are:

- ATI 9600 video card vs NVidia 7600
- Keyboards
- Mice
- Monitor (my monitor is a hp L1940T)

If these is anything you or other can think of for me to test maybe we can get to the bottom of this issue. Thanks.

[Saivann Carignan (oxmosys)]

Nick : Thanks a lot for all these details. Since your computer does not shutdown, in my opinion, assuming that you have clean install of ubuntu on this computer, this problem can only be related to your motherboard. I might be wrong, but I don't see how the graphic card or the keyboard could cause the computer to reboot instead of a normal shutdown. I'm not an expert so I can't give more help on this until somebody who has the needed knowledge take a look at this bug report. From now on, what I would suggest would be to try changing some options in the BIOS (perhaps setting back the BIOS to default values?) and look to find if a specific option in the BIOS can have any effect on that special bug. If you have any news concerning this bug, don't forget to post more details here! Thanks again for all the informations you provided so far.

[Nick (morrownr)]

In the time since my last post I reset the bios to defaults. This did not help. I have changed many bios settings. No help. My bios settings are now back to the settings I have used for a long time. I've seen no evidence that a bios setting is causing this problem.

Today I installed Ubuntu 7.10 in a separate partition. That gives me 8.04 and 7.10 on the same system. 7.10 will shutdown as expected. 8.04 will not. Shutdown simply reboots the system in 8.04.

There has been a change somewhere in 8.04 that is causing this problem. I am about out of ideas.

P.S. I have an update report from the guy I know that uses the same mb as I do (I spoke about this above). When I first reported 8.04 shutdown was working on his system he had just installed 8.04 and tested once. He has since updated me with a report saying that shutdown in not working on his system either. Curiously, he appears to have a different problem. When he selects shutdown the shutdown simply does not complete and his only option is to remove power from the machine. This is new for him as he reports that using 7.10 and early he had no problems with shutdown.

[Saivann Carignan (oxmosys)]

Thanks again for all these details. Since you can reproduce the bug and that there seems to have a regression in hardy for your specific hardware, I set the status to Triaged, Importance to High and I assign it to kernel team per their bug policy. If you have any new information about that bug, the informations you provide are very appreciated.

[seldon7 (ubuntu-pengo)]

I have the same problem. For me, 7.10 was fine - now 8.04 reboots almost every time when I hit shutdown.

Occassionally, it does shutdown but too rarely for me to reproduce easily. Seems to depend on whether I turn my modem off or not - but that could be unrelated.

Intel 3 Ghz machine, Nvidia 6800GS card. I think an MSI motherboard (but not at home to check).

[Nick (morrownr)]

I have finally found a work around:

System >> Preferences >> Sessions >> Uncheck Power Management >> Reboot

Now Shutdown works normally. Of course now Suspend and Hibernate do not work but in the big scheme of things on this desktop system I never use Hibernate anyway. At least Shutdown and Reboot work fine now.

That tells me the problem is in "Power Management."

This is definitely a regression from 7.10 and earlier.

seldon7, my mb is a MSI, Intel 3.2 ghz, Northwood, ATI video

[Nick (morrownr)]

Disregard the work around in the previous message.

Further testing shows that Shutdown will work normally if I select Shutdown soon after booting up and without starting Firefox. If I start Firefox and browse for a while then Shutdown simply reboots the system. This happens whether Power Management is checked or not.

Oh, this is frustrating! I think it is time to test other distros.

[Nick (morrownr)]

Over the last 2 days I have tested Xubuntu.

Xubuntu 7.10 shuts down perfectly when Shutdown is selected.

Xubuntu 8.04 reboots when Shutdown is selected.

The problem is not just in Ubuntu 8.04 but is also in Xubuntu 8.04.

[Saivann Carignan (oxmosys)]

This is indeed weird and frustrating, but not surprising that the problem comes back with xubuntu since xubuntu use the same ubuntu kernel. Can you reproduce this bug with Debian, Mandriva, Fedora, openSuSE? Or, why not, intrepid 8.10 (which should have a working alpha 2 in 10 days).

[Nick (morrownr)]

Update: I downloaded and installed the alpha of Ubuntu 8.10 (Intrepid). Thus far I cannot reproduce this problem with Intrepid. Shutdown appears to work fine with Intrepid. I'll continue testing.

I have also downloaded Fedora and will test it as I have time.

My opinion: This bug appears to be specific to 8.04.

[Nick (morrownr)]

This bug does appear to be specific to 8.04.

I have now used 8.10 alpha for a couple of weeks. I tested this over and over. I've been unable to duplicate the problem. I never had this problem with 7.10 and before. I do not have the time to pursue this bug further so I am going to leave all systems I support at 7.10 and earlier versions while leaving this system on 8.10.

[Saivann Carignan (oxmosys)]

Nick : Thank your very much for the time you spent to give more informations about this bug. This bug report contains sufficient data for developers so I think that your decision currently the best one. Thanks again.

[seldon7 (ubuntu-pengo)]

Seems like the exact same problem for me. I'll try the work around suggested, ie. switching off hibernation, etc.. Mine is also an MSI motherboard.

    description: Computer
    width: 32 bits
  *-core
       description: Motherboard
       physical id: 0
     *-memory
          description: System memory
          physical id: 0
          size: 1519MiB
     *-cpu
          product: Intel(R) Pentium(R) 4 CPU 3.00GHz
          vendor: Intel Corp.
          physical id: 1
          bus info: cpu@0
          version: 15.3.4
          serial: 0000-0F34-0000-0000-0000-0000
          size: 18EHz
          width: 32 bits
          capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe constant_tsc pebs bts sync_rdtsc pni monitor ds_cpl cid xtpr
          configuration: id=1
        *-logicalcpu:0
             description: Logical CPU
             physical id: 1.1
             width: 32 bits
             capabilities: logical
        *-logicalcpu:1
             description: Logical CPU
             physical id: 1.2
             width: 32 bits
             capabilities: logical
     *-pci
          description: Host bridge
          product: 82865G/PE/P DRAM Controller/Host-Hub Interface
          vendor: Intel Corporation
          physical id: 100
          bus info: pci@0000:00:00.0
          version: 02
          width: 32 bits
          clock: 33MHz
          configuration: driver=agpgart-intel module=intel_agp
        *-pci:0
             description: PCI bridge
             product: 82865G/PE/P PCI to AGP Controller
             vendor: Intel Corporation
             physical id: 1
             bus info: pci@0000:00:01.0
             version: 02
             width: 32 bits
             clock: 66MHz
             capabilities: pci normal_decode bus_master
           *-display
                description: VGA compatible controller
                product: NV43 [GeForce 6800 GS]
                vendor: nVidia Corporation
                physical id: 0
                bus info: pci@0000:01:00.0
                version: a2
                width: 32 bits
                clock: 66MHz
                capabilities: vga_controller bus_master cap_list
                configuration: driver=nvidia latency=248 maxlatency=1 mingnt=5 module=nvidia
        *-usb:0
             description: USB Controller
             product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #1
             vendor: Intel Corporation
             physical id: 1d
             bus info: pci@0000:00:1d.0
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: uhci bus_master
             configuration: driver=uhci_hcd latency=0 module=uhci_hcd
        *-usb:1
             description: USB Controller
             product: 82801EB/ER (ICH5/ICH5R) USB UHCI Controller #2
             vendor: Intel Corporation
             physical id: 1d.1
             bus info: pci@0000:00:1d.1
             version: 02
             width: 32 bits
             clock: 33MHz
             capabilities: uhci bus_master
             configuration: driver=uhci_hcd latenc...

[seldon7 (ubuntu-pengo)]

Note there is also a forum thread about this bug:

http://ubuntuforums.org/showthread.php?t=14253

[Leann Ogasawara (leannogasawara)]

The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would appreciate it if you could please test this newer 2.6.27 Ubuntu kernel. There are one of two ways you should be able to test:

1) If you are comfortable installing packages on your own, the linux-image-2.6.27-* package is currently available for you to install and test.

--or--

2) The upcoming Alpha5 for Intrepid Ibex 8.10 will contain this newer 2.6.27 Ubuntu kernel. Alpha5 is set to be released Thursday Sept 4. Please watch http://www.ubuntu.com/testing for Alpha5 to be announced. You should then be able to test via a LiveCD.

Please let us know immediately if this newer 2.6.27 kernel resolves the bug reported here or if the issue remains. More importantly, please open a new bug report for each new bug/regression introduced by the 2.6.27 kernel and tag the bug report with 'linux-2.6.27'. Also, please specifically note if the issue does or does not appear in the 2.6.26 kernel. Thanks again, we really appreicate your help and feedback.

[Ralph Janke (txwikinger)]

The Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . It contains the 2.6.27 Ubuntu kernel. It would be great if you could test and verify if this is still an issue. The status is being set to Incomplete until we receive further feedback. Thanks.

[Launchpad Janitor (janitor)]

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

[seldon7 (ubuntu-pengo)]

sorry for the long delay - once i upgraded to 8.10 this bug went away.

set to resolved / fixed??

[Saivann Carignan (oxmosys)]

Nick : Can you confirm seldon7 comment? Is this bug fixed for you with latest 8.10 ou 9.04 ubuntu release?

[Colin Ian King (colin-king)]

@Nick: Can you confirm this issue exists with the most recent Jaunty Jackalope 9.04 release - http://www.ubuntu.com/news/ubuntu-9.04-desktop . Please let us know your results. Thanks.

[Leann Ogasawara (leannogasawara)]

Having not heard back for Nick, I'm closing this bug based on comment #27 from seldon7:

https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/234700/comments/27