12.04 shutdown bug

[2sondad]

But it inot solved. Not all of us are using the same graphics card and the fixes that i have tried have only been temporary or 1 time successes.

[2sondad]

After weeks of shutdown problems, I finally came across a related thread that said Unity is the issue and needs to be reset. This was fascinating to me, as I do not use Unity, but rather Cinnamon.

Here's what I did:

• Opened a terminal
• Reset unity , by executing unity --reset
• Reset launcher icons by executing unity --reset-icons
• I had a lot of error messages, but let it run for about 5 minutes and I even had to shutdown the computer manually because I couldn't tell if it was still running anything in terminal.
• When I restarted, Cinnamon was up and running, even though when I reset Unity, it stopped Cinnamon and opened Unity while the terminal commands were executing.
• I have been able to shutdown normally ever since.

[GreatDanton]

I am not sure if this thread is active, but I will post it anyway. Ok here is something you should try in order to shutdown your OS in proper way. I made that and it worked for me.

Here are step by step commands.

gksudo gedit /etc/default/grub

Navigate to the line that looks like,

GRUB_CMDLINE_LINUX=""

And put acpi=force in there.

GRUB_CMDLINE_LINUX="acpi=force"

Save and close that file.

Now update grub by running,

sudo update-grub

And restart to see if it worked.

Also I think moderators should delete the upper post (spam).

[bcschmerker]

As it turns out, I have found that a problem does exist somewhere in the LinUX-Image-3.2.0-29-Generic source code.

As a matter of course for any Dist-Upgrade on my Everex®, I disable Quiet and Splash in GRUB 2.00 (using gksudo gedit /etc/default/grub and gksudo update-grub) in order to monitor startup and shutdown, and this gave us a clue to the complete-lockup problem. My Everex® "seized" during attempted shutdown on or around 06:00, 1 September 2012 (UTC), the output at the console being as follows (I was unable to capture the Lockup of CPU 0 before the CPU 1 seizure report shown):

[13397.130676] ------------[ cut here ]------------
[13397.130676] WARNING: at /build/buildd/linux-3.2.0/kernel/watchdog.c:241 watchdog_overflow_callback+0x9a/0xc0()
[13397.130676] hardware name: GA-MA78GM-S2HP
[13397.130676] Watchdog detected hard LOCKUP on cpu 1
[13397.130676] Modules linked in: btrfs zlib_deflate libcrc32c ufs qnx4 hfsplus minix ntfs vfat jfs xfs reiserfs ext2 bnep rfcomm bluetooth vesafb usblp snd_emu10k1_synth snd_emux_synth snd_seq_virmidi snd_seq_midi_emul fglrx(p) snd-emu10k1 snd_ac97_codec snd_rawmidi snd_hwdep snd_seq_midi_event snd_pcm snd_seq sp1500_tco psmouse snd_seq_device snd_timer snd_page_alloc lp shpchp edac_core edac_mce_amd mac_hid ppdev snd wmi serio_raw parport_pc parport i2c_piix4 emu10k1_gp gameport k8temp soundcore usbhid hid firewire_ohci usb_storage firewire_core crc_itu_t floppy r8169 pata_atiixp
[13397.130676] Pid: 2135, comm: dbus-launch Tainted: P      D W  O 3.2.0-29-generic #46-Ubuntu
[13397.130676] Call Trace:
[13397.130676]  <NMI>  [<ffffffff81066cff>] warn_slowpath_common+0x7f/0xc0
[13397.130676]  [<ffffffff81066df6>] warn_slowpath_fmt+0x46/0x50
[13397.130676]  [<ffffffff8101ae69>] ? sched_clock+0x9/0x10
[13397.130676]  [<ffffffff810d7d5a>] watchdog_overflow_callback+0x9a/0xc0
[13397.130676]  [<ffffffff811115e6>] __perf_event_overflow+0x96/0x1e0
[13397.130676]  [<ffffffff8110eb71>] ? perf_event_update_userpage+0x11/0xc0
[13397.130676]  [<ffffffff81024007>] perf_event_overflow+0x14/0x20
[13397.130676]  [<ffffffff81024007>] x86_pmu_handle_irq+0xd7/0x120
[13397.130676]  [<ffffffff8165b401>] perf_event_nmi_handler+0x21/0x30
[13397.130676]  [<ffffffff8165acc9>] default_do_nmi+0x69/0x220
[13397.130676]  [<ffffffff8165af00>] do_nmi+0x80/0x90
[13397.130676]  [<ffffffff8165a2f0>] nmi+0x20/0x30
[13397.130676]  [<ffffffff8103dc62>] ? __ticket_spin_lock+0x22/0x30
[13397.130676]  <<EOE>>  [<ffffffff81659bc5>] _raw_spin_lock_irq+0x15/0x20
[13397.130676]  [<ffffffff810b234a>] acct_collect+0xaa/0x1c0
[13397.130676]  [<ffffffff8106b75c>] do_exit+0x34c/0x420
[13397.130676]  [<ffffffff8165aa60>] oops_end+0xb0/0xf0
[13397.130676]  [<ffffffff8163fd63>] no_context+0x150/0x15d
[13397.130676]  [<ffffffff8163ff39>] __bad_area_nosemaphore+0x1c9/0x1e8
[13397.130676]  [<ffffffff8163f5e5>] ? pmd_offset+0x1f/0x25
[13397.130676]  [<ffffffff8163ff6b>] bad_area_nosemaphore+0x13/0x15
[13397.130676]  [<ffffffff8165d6b6>] do_page_fault+0x426/0x520
[13397.130676]  [<ffffffff81052746>] ? ttwu_do_activate.constprop.177+0x66/0x70
[13397.130676]  [<ffffffff81052806>] ? ttwu_queue+0xb6/0xd0
[13397.130676]  [<ffffffff8105f55e>] ? try_to_wake_up+0x18e/0x200
[13397.130676]  [<ffffffff8165a035>] page_fault+0x25/0x30
[13397.130676]  [<ffffffffa0248ef4>] ? firegl_sig_notifier+0x4/0x40 [fglrx]
[13397.130676]  [<ffffffffa023820e>] ? KCL_SGINAL_Notifier+0xe/0x10 [fglrx]
[13397.130676]  [<ffffffff81079d41>] __dequeue_signal+0x91/0xb0
[13397.130676]  [<ffffffff8107a12e>] dequeue_signal+0xce/0x180
[13397.130676]  [<ffffffff8107c7a8>] get_signal_to_deliver+0x128/0x420
[13397.130676]  [<ffffffff8108e870>] ? hrtimer_try_to_cancel+0x50/0xc0
[13397.130676]  [<ffffffff81013865>] do_signal+0x45/0x130
[13397.130676]  [<ffffffff8108dfe6>] ? update_rmtp+0x56/0x70
[13397.130676]  [<ffffffff8108f45d>] ? hrtimer_nanosleep+0xdd/0x180
[13397.130676]  [<ffffffff8108e000>] ? update_rmtp+0x70/0x70
[13397.130676]  [<ffffffff81013b15>] do_notify_resume+0x65/0x80
[13397.130676]  [<ffffffff81662190>] int_signal+0x12/0x17
[13397.130676] ---[ end trace 1b65ce952a307786 ]---

From my perspective, this is definitely High, if not Critical, in importance for a fix, especially given the fact that the process may have prevented Unmount of the hard-drive partitions and Remount (as Read-Only) of the Boot partition. Can this be Fixed in Precise, or Fix-Committed for 11.09b2 (package: linux-image-generic-lts-backport-quantal); or is this to be Triaged for the LinUX Kernel Project to review?

[jmate24]

If you are haveing a bug please report it to http://launchpad.net.

Thanks.

jmate24

[OldDinosaur]

I recently installed 12.04.1 on a Gateway box (64bit). While my shutdown hasn't frozen, it doesn't work correctly. Everytime I reboot, Ubuntu wants to do a disk check because of the poor shutdown.

I see a series of messages flash across the screen during the shutdown and catch a word or two, but cannot find the messages in the log files to know what they are.

It is quite frustrating.

[bcschmerker]

...As a matter of course for any Dist-Upgrade on my Everex®, I disable Quiet and Splash in GRUB 2.00 (using gksudo gedit /etc/default/grub and gksudo update-grub) in order to monitor startup and shutdown, and this gave us a clue to the complete-lockup problem. My Everex® "seized" during attempted shutdown on or around 06:00, 1 September 2012 (UTC)....

Update: The Hard Lockups appear directly related to conflicts among other Packages, so may or may not be a bug of linux-image-generic-3.2.0.