Kernel 2.6.32-24 regression - Lucid 10.04 Freezes at Shutdown

[nomnex]

Kernel 2.6.32-24 regression. My system freezes at shutdown, during the dots countdown (when the third dot change from white to red).

Kernel 2.6.32-21 (default image on my 10.04 installation) does not freeze the system at shutdown.

Kernel 2.6.32-24, I have edited the /etc/grub with the parameter "nomodset". The system did not freeze at shutdown, but it was barely usable (black screen instead of a background image, grub2 heavily flickering). The parameter "acpi=off" had no effect, the system froze at shutdown.

Please instruct with the commands to troubleshoot this bug

[nomnex (nomnex)]

You can merge this bug. Kernel 2.6.32-21 freezes randomly too. With either kernel 2.6.32-21/-24 editing the grub with different parameters "acpi=oldboot", "nomodeset", "acpi=force" did not solved the issue. Fairly standard an old hardware (year 2004 notebook) here. Pentium IV, Mobility radeon 9000.

[nomnex (nomnex)]

Fedora 13 is stable with my (3) different hardware. The latest Ubuntu has been a bad experience. Too much eye candy and too many well documented bugs related to installation/log-in/shutdown.

[Aurélien Dominguez (tenkaistar)]

Same probleme here on X86_64 ubuntu 10.04...
PC hangs on shutdown...
I disabled splash to get messages... All processes are correctly terminated, crypted partition are correctly closed and then unmounted and the last message I get is : System will now Hald...
I hear hard drives shutdown, then I just have to push (with no need to hold) the power button for it to shutdown.
I think that the system is correctly shutdown, it just "wait" after everything is actually stopped, the same way it would wait for user to remove disk on live-cd shutdown ...

[exactt (giesbert)]

i just read https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.22/+bug/126140 . maybe this a a similar problem. how could one find out if one of the modules hangs and which one the culprit is?

[Aurélien Dominguez (tenkaistar)]

I finally managed to fix the problem by removing the acpi=off from my grub kernel options...
Don't know if it's a bug or not, but I also installed the nut package (and enabled it to standalone mode).
The reason I installed it is that when I had a look at "/etc/init.d/halt" script, I noticed that in case of shutdown, it called the /etc/init.d/ups-monitor which was not installed...

[nomnex (nomnex)]

From memory, acpi=off (or any other grub parameter) did not solve my issue. More than once, I though having solved the issue entering a new grub parameter. Since the freeze on shutdown occurred randomly on my machine, it was only a matters of hours (day) before reproducing the issue.

[Aurélien Dominguez (tenkaistar)]

Well it's probably not the same problem then since the freeze on shutdown
was 100% of the time for me...
No matter if it was from Gnome or from TTY with shutdown -P now, it always
froze...
I just did not noticed it before because I had faulty hard drive which made
my PC freeze randomly so I always hard rebooted ^^

On Wed, Aug 25, 2010 at 9:06 AM, nomnex <email address hidden> wrote:

> >From memory, acpi=off (or any other grub parameter) did not solve my
> issue. More than once, I though having solved the issue entering a new
> grub parameter. Since the freeze on shutdown occurred randomly on my
> machine, it was only a matters of hours (day) before reproducing the
> issue.
>
> --
> Kernel 2.6.32-24 regression - Lucid 10.04 Freezes at Shutdown
> https://bugs.launchpad.net/bugs/613897
> You received this bug notification because you are a direct subscriber
> of the bug.
>

[penalvch (penalvch)]

nomnex, thank you for reporting this bug to Ubuntu. Lucid Desktop reached EOL on May 9, 2013.
See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

Is this an issue in a supported release? If so, could you please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 613897

[Launchpad Janitor (janitor)]

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]