Kernel 2.6.20 reboots instead of shutting down

Please provide more information. A bug report needs details. Specifically your hardware type and the /var/log/kern.log showing the last messages before shutdown/reboot.

It's an acer travelmate 8000 series

Not much information there. Please provide output of "sudo dmidecode | tee dmi.log".

Attach the file to the bug report so I can see if there were some changes specifically for this board.

Thanks

I believe this is yet more functionality that is lost without the PHC patch.

Fixed in 2.6.19-7 doesn't seem related to the PHC patch.

mmm well this is pretty strange, It was working for a week, but yesterday it doesn't anymore...

Please retest against 2.6.20-2 when it is available in the feisty archive.

... I don't understand anything... It was working for about 2 days now with 2.6.19-7-lowlatency...

I'm sure that at the beginning of the week the machine was still rebooting. I didn't change anything related to kernel..

It does it again... :'(

I have this problem on 2.6.20, it was fine on 2.6.19. Acer TravelMate 8100, dmidecode output is here: http://librarian.launchpad.net/1853317/dmidecode.8103
Same problem on shutdown or hibernation, it reboots right away.

Please check latest 2.6.20-4

Still same problem with 2.6.20-4.6.

Kernel 2.19 was fine with me. Since we went to 2.20 Shutdown keeps rebooting. This is on an Acer Travelmate 4001 wLMI

my desktop computer keeps also rebooting instead of shutting down :(

Same problem on 2.6.20-6.11.

https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/83844
seems to be a duplicate

I can confirm this bug on a fresh install of Feisty Herd 5. The following methods all perform a restart instead of a shutdown:

1. Shutdown via the "shutdown, reboot, etc, menu" from gnome-panel
2. "Options -> Shut Down" from the login screen
3. "sudo shutdown -h now" from a terminal
4. "sudo shutdown -h now" from a console (Ctrl+Alt+F1)

Only option is to press the power-button...

on my acer aspire 1692 i have the same problem.
in edgy it work fine.

I can also confirm the bug on a acer Extensa 4101 with Kernel 2.6.20-9. There is no way to poweroff, but restart and suspend-to-RAM support is available without any problems.
In Edgy (2.6.17) it works still fine.

That is a dmesg exerpt from these lines which looks strange imho.
[ 18.471426] PnPBIOS: Disabled by ACPI PNP
[ 19.088000] ibm_acpi: ec object not found
[ 25.636000] apm: BIOS not found.

Additional I recognize that this bug only appears if you connect to ac/dc power supply. If you shutdown on battery supply it works correctly. Could anyone confirm this?

Is there a changelog for apmd, laptop-detect or laptop-mode-tools to 2.6.20 available?

thx

Thomas

>Additional I recognize that this bug only appears if you connect to ac/dc power supply. If you shutdown on battery supply it works correctly. Could anyone confirm this?

I've just tested and I can confirm that too

Same here as Laurent. Acer Aspire 1681 LCi.

I have an acer laptop too.. Acer specific?

I think so.

I ran my test on a desktop computer containing an Asus P4P800 Motherboard/Intel P4 HT, so I don't think the problem is Acer specific.

No. Asus P4P800 desktop, here.

I have to correct my post above.

1. Suspend to RAM does not work with kernel option "noapic".

2. >That is a dmesg exerpt from these lines which looks strange imho.
[ 18.471426] PnPBIOS: Disabled by ACPI PNP
[ 19.088000] ibm_acpi: ec object not found
[ 25.636000] apm: BIOS not found.<

I've just compared it to my Edgy output and there's no different.

So Asus P4P800 mainboards and some Acer laptops having this problem, by the looks of things. Anyone else?

On 3/6/07, Alex Jones <email address hidden> wrote:
> So Asus P4P800 mainboards and some Acer laptops having this problem, by
> the looks of things. Anyone else?

Yes,i have the same issue on my Asus mainboard based desktop.
> rebooting instead of shutting down
> https://launchpad.net/bugs/71040
>

I tried the LiveCD of fedora core Test2 for testing another bug.
It booted kernel:

Linux localhost.localdomain 2.6.20-1.2949.fc7 #1 SMP Mon Feb 26 18:37:35 EST 2007 i686 i686 i386 GNU/Linux

I could shut down the PC with no trouble...

Same problem with Asus P4C800 Deluxe motherboard and kernel 2.6.20-9.

same here, acer 8103.
see this bugreport for details about my bug (it's a duplicate of this bug)
https://launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/90936

The problem still exists on 2.6.20-10

Curiously, if set to hibernate instead of shutdown, the computer halts perfectly

The problem persists with the last kernel : 2.6.20-10
Acer laptop

I think I might have found the source of this problem!

While testing several things at once I was taking the following steps:

* I was trying to install my wireless with ndiswrapper and wpasupplicant (after installation I got no connection)
* I tried to shutdown the computer with the hibernate option, this halted my computer (as Carlos Fenollosa mentioned as well).
* I than removed network-manager !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
* When I tried the hibernate again, the computer was locked.
* I unlocked the computer and tried the shutdown option, guess what, the computer halted!

Could anyone please remove network-manager (network-manager-gnome and ubuntu-dekstop (meta-package, safe to remove) will also be removed) and see if this works for you too?

Ps. my wireless works fine as well now (without network-manager)

Uninstall network-manager takes no effect, but upgrade to 2.6.20-11 resolve the issue on acer Extensa 4101.

nice job... thx...

2.6.20-11 is also resolving the issue for Asus P4P800.

Can we have more confirmations, please?

2.6.20-11 resolves the issue for the Acer Aspire 1681 LCi too.

Work for me with my Acer TM laptop

Problem solved for me (Asus P4P800)

Solved on Acer Aspire 1692 with "Linux vayralemine 2.6.20-11-generic #2 SMP Thu Mar 15 08:03:07 UTC 2007 i686 GNU/Linux"

Fixed with 2.6.20-11 on Acer TravelMate 8101. Thanks!

The 2.6.20-11 kernel fixed the problem for me too. Thanks all for the good work.

Fixed, reported by multiple persons

Please could everybody who was affected by this bug see if they can suspend their computer. For me, suspend behaviour is EXACTLY the same as the broken shutdown behaviour here. I.e. a brief power-off, followed by an instant resume.

For me, hibernating works almost perfectly (see audio problems on resuming, Bug #80893), but the computer halts after hibernating.

I just tried suspending right now, while I was editing this comment, and the computer also halted after the suspending. By the way, suspending doesn't suffer the Bug #80893

Suspend is broken for me, the system powers-off and resumes immediately, showing the following error message:

[ ] pnp: Failed to active device 00:03.
[ ] pnp: Failed to active device 00:04.

Sorry, that was the Edgy kernel, I'll try 2.6.20-11 later on...

Feisty suspend:

System power down, immediately resumes and comes up in a locked state.
A crash report was waiting for me (vbetool), unfortunately, when I pressed "Send Report" nothing else happened. Therefore I have attached the report from /var/crash:

Weitse, can you report on bug 75497, please? (Add your HW info, too!)

Also, anyone else who is having this same problem with S3 suspend. Thanks!

Does anybody know what the kernel fix for this was? P4P800 suspend is still broken, for me, in exactly the same way. Nobody seems interested ATM, so I'd like to have a look myself.