[edgy] Restart takes much too long

[Suzan]

Binary package hint: linux-image-2.6.17-10-generic

It happens even on a fresh edgy install:

the restart takes much too long, about 5 minutes.

All goes well until "Will now restart". When the screen goes black and nothing happens. It takes about 5 minutes and the computer restarts. First I thought the system hangs completely, but it only takes very long. This happens every restart.

The normal start-up and shut-down went well.

I have an AMD64 machine with 32bit edgy, actual kernel 2.6.17-10-generic. And I dualboot with windows.

Btw: on Dapper the restart was normal

[albert kirk (albertkirk)]

I'm just confirming that I'm having this same issue and i also have a AMD64 system using the 32bit version of Ubuntu 6.10

[albert kirk (albertkirk)]

this bug is still present in the final release of edgy has a fix or workaround ever been found yet?

[Jglz (joshshanga)]

bug present here with the realese on hp athlon 3200 asus moderboard
but it isnot doing it in a older pc p3 800mhz

[Jglz (joshshanga)]

sorry i forgot to post that if i use the linux-image-2.6.15 k7 from drapper it works fine on the restarting problem maybe that could be the work around temporary.

[Dominique Derrier (derrierdo)]

The trouble seems about acpi ... battery module.
No trouble when the module is unloaded, but it's not a best fix for a laptop ;)

Multiple access to '/proc/acpi/battery/BAT0/state' hang this device.

Affect: my Asus A6Q00KM

But I haven't got any debug log :(
If you know a way to produce it ... I'll help you.

Thank's for your help
Dominique Derrier

[francoise (flabelle)]

My Athon xp 3000+ won't restart with Edgy's generic kernel (shutdown is ok). No problem with Dapper's K7 kernel.
I tried solutions found on the net without success (unloading the battery module, forcing or removing acpi).

Francoise Labelle

[albert kirk (albertkirk)]

this bug was never fixed in edgy, and now it's present again in feisty ever since herd 2 was released, it was fixed for a short time and now it's back after the latest kernel updates. will this bug ever be fixed in the final release of feisty yes or no, because i don't want to waste the time waiting for the next release just to have the same problem.

[Suzan (suzan72)]

Hm... it seems, that bug is still present in current Feisty.. For me even in live-cd-mode.

But it seems, this bug is only present for AMD processors? Anyone got news for this?

[Suzan (suzan72)]

Good news (at least for me):

Yesterday I've installed updated my Edgy to Feisty.

With kernel 2.6.20-5-generic and the new one, 2.6.20-6-generic the bug has gone!

Restart is now OK for me.

[albert kirk (albertkirk)]

it was for me to, right after the update, but after i restarted a couple of times it's now doing the same thing again.

[Suzan (suzan72)]

Sounds really weird!

I will watching this.

[pusher (thorsten-hehn)]

I recently installed Edgy on my AMD64 machine with kernel 2.6.17-10-generic and I'm observing the same problems as mentioned above. Shutdown works properly, but reboot doesn't. I tried hundreds of boot parameters concerning ACPI (acpi=off, acpi=force, noapic, nolapic, ...) with no success. Unloading the battery module as proposed doesn't show any effect either.

Hope this annoying bug will be fixed soon...

Thorsten

[pusher (thorsten-hehn)]

This is just an edit to my upper message: I'm not using kernel 2.6.17-10 but 2.6.17-11.

[albert kirk (albertkirk)]

i've found a temporary solution that seems to work ok on my system, go to System/Administration/Services and uncheck the box for powernowd this will disable cpu scaling, but it fixes not restarting the issue.

[pusher (thorsten-hehn)]

Hey cool, that works fine on my system, too. I deactivated powernowd and restarted my PC three times without any problems. The service remains deactivated after a restart, so I suppose the issue to be fixed. As I'm running Ubuntu on a desktop PC, I don't need CPU scaling at all.

[a-f-r-a (rum-knoblauch-nuss)]

I discovered the bug too on my System and got nearly mad on it... system: amd64 cpu with 32bit feisty
and the "solution" mentioned above seems to work...

[Brian Murray (brian-murray)]

I am assigning this bug to the 'ubuntu-kernel-team' per their bug policy. For future reference you can learn more about their bug policy at https://wiki.ubuntu.com/KernelTeamBugPolicies .

[Sergio Zanchetta (primes2h)]

The 18 month support period for Edgy Eft 6.10 has reached it's end of life. As a result, we are closing the linux-source-2.6.17 Edgy Eft kernel task.

Hardy Heron 8.04 was recently released. It would be helpful if you could test the new release and verify if this is still an issue - http://www.ubuntu.com/getubuntu/download . You should be able to test your bug using the LiveCD. Please let us know your results. Thanks.

[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)]

Unfortunately this bug report is being closed because we received no response to the last inquiry for information. However, the Intrepid Ibex 8.10 Beta release was most recently announced - http://www.ubuntu.com/testing/intrepid/beta . If you are able to confirm this is still an issue with this most recent release please feel free to reopen this report. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". 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.