sudo halt won't cause halt

[Kalsan]

When typing sudo halt into a terminal, ubuntu shuts down completely, but won't turn off my hp compaq 6730s laptop. The hard disk makes a clicking sound (that means it's turned off), but power remains on, displaying a frozen ubuntu logo.
I upgraded from 11.10 via update-manager.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 1.94.1-0ubuntu1
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: sandro 1947 F.... pulseaudio
 /dev/snd/controlC1: sandro 1947 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0x98900000 irq 49'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c3614,00100400 HDA:11c11040,103c1378,00100200'
   Controls : 18
   Simple ctrls : 11
Card1.Amixer.info:
 Card hw:1 'U0x46d0x807'/'USB Device 0x46d:0x807 at usb-0000:00:1d.7-1.3, high speed'
   Mixer name : 'USB Mixer'
   Components : 'USB046d:0807'
   Controls : 2
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'Mic',0
   Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum
   Capture channels: Mono
   Limits: Capture 0 - 6144
   Mono: Capture 4608 [75%] [24.00dB] [on]
CurrentDmesg:
 [ 39.464297] CIFS VFS: cifs_mount failed w/return code = -113
 [ 42.496065] wlan0: no IPv6 routers present
 [ 45.464194] CIFS VFS: Error connecting to socket. Aborting operation
 [ 45.464293] CIFS VFS: cifs_mount failed w/return code = -113
 [ 54.987968] process `skype' is using obsolete setsockopt SO_BSDCOMPAT
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=d85b1d28-2ef4-4bd2-b2c2-88a768c1e4fb
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: Hewlett-Packard HP Compaq 6730s
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=e8d2876f-7ef9-4b1a-bc38-9e48f1db155a ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic 3.2.9
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-18-generic N/A
 linux-backports-modules-3.2.0-18-generic N/A
 linux-firmware 1.71
Tags: precise
Uname: Linux 3.2.0-18-generic i686
UpgradeStatus: Upgraded to precise on 2012-03-03 (6 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 12/06/2010
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PZU Ver. F.13
dmi.board.name: 30E8
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 94.1D
dmi.chassis.asset.tag: CNU91138XV
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PZUVer.F.13:bd12/06/2010:svnHewlett-Packard:pnHPCompaq6730s:pvrF.13:rvnHewlett-Packard:rn30E8:rvrKBCVersion94.1D:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6730s
dmi.product.version: F.13
dmi.sys.vendor: Hewlett-Packard

[Ubuntu Foundations Team Bug Bot (crichton)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https://wiki.ubuntu.com/Bugs/FindRightPackage. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.

To change the source package that this bug is filed about visit https://bugs.launchpad.net/ubuntu/+bug/950129/+editstatus and add the package name in the text box next to the word Package.

[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]

[Kalsan (info-kalsan)]

Thanks for your reply. The link https://wiki.ubuntu.com/Bugs/FindRightPackage is very helpful, but it doesn't say exactly how to categorize the shutdown. Looks though like it affects the kernel. Is that right?

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 950129

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Kalsan (info-kalsan)]

apport information

[Brad Figg (brad-figg)]

Thank you for taking the time to file a bug report on this issue.

However, given the number of bugs that the Kernel Team receives during any development cycle it is impossible for us to review them all. Therefore, we occasionally resort to using automated bots to request further testing. This is such a request.

We have noted that there is a newer version of the development kernel than the one you last tested when this issue was found. Please test again with the newer kernel and indicate in the bug if this issue still exists or not.

You can update to the latest development kernel by simply running the following commands in a terminal window:

    sudo apt-get update
    sudo apt-get upgrade

If the bug still exists, change the bug status from Incomplete to Confirmed. If the bug no longer exists, change the bug status from Incomplete to Fix Released.

If you want this bot to quit automatically requesting kernel tests, add a tag named: bot-stop-nagging.

 Thank you for your help, we really do appreciate it.

[Kalsan (info-kalsan)]

Installed newest updates, the but still occures.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/

[Kalsan (info-kalsan)]

I'm sorry I'm having technical problems.
I went to the last link you gave me and downloaded linux-headers-3.3.0-030300rc7_3.3.0-030300rc7.201203101735_all.deb
update, upgrade and then I installed the deb via Software-Center. Reboot. Sudo halt, same problem.
Then I tried to regenerate GRUB, as I might have booted the wrong kernel:
$ sudo update-grub
Generating grub.cfg ...
Found linux image: /boot/vmlinuz-3.2.0-18-generic
Found initrd image: /boot/initrd.img-3.2.0-18-generic
Found linux image: /boot/vmlinuz-3.2.0-17-generic
Found initrd image: /boot/initrd.img-3.2.0-17-generic
Found linux image: /boot/vmlinuz-3.0.0-16-generic
Found initrd image: /boot/initrd.img-3.0.0-16-generic
Found memtest86+ image: /boot/memtest86+.bin
Found Windows 7 (loader) on /dev/sda1
done
There's no 3.3... what did I do wrong?
Kalsan

[Joseph Salisbury (jsalisbury)]

There is some documentation here:
 https://wiki.ubuntu.com/KernelMainlineBuilds

You basically just need to download the .deb file for your arch from:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/

Then install the .deb with:
sudo dpkg -i FILE_NAME.deb

You can run sudo update-grub to automatically have grub updated to boot the new kernel by default. However, it is probably best to not update grub, and just select the new kernel from the grub menu.

The grub menu is hidden by default. You can access it by holding the "Shift" key after you power on your system.

[Kalsan (info-kalsan)]

The kernel is installed:
$ sudo apt-get autoremove lin<TAB><TAB>
lintian linux-headers-generic-pae
linux-firmware linux-image-3.0.0-16-generic
linux-generic linux-image-3.2.0-17-generic
linux-headers-3.2.0-18 linux-image-3.2.0-18-generic
linux-headers-3.2.0-18-generic linux-image-generic
linux-headers-3.2.0-18-generic-pae linux-libc-dev
linux-headers-3.3.0-030300rc7 linux-sound-base
linux-headers-generic

As I have a multiboot machine, GRUB shows up for 3 seconds at every boot. There's no entry for 3.3x...

[Kalsan (info-kalsan)]

Here's a screenshot from my GRUB.

[Joseph Salisbury (jsalisbury)]

You need to install the linux-image .deb:
http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-rc7-precise/linux-image-3.3.0-030300rc7-generic_3.3.0-030300rc7.201203101735_i386.deb

[Kalsan (info-kalsan)]

Thanks for your help. I autoremoved and purged the kernel I had previously installed, then I installed the suggested deb. update, upgrade. This time, GRUB listed 3.3. Booting 3.3, sudo halt. Same problem.
Added kernel-bug-exists-upstream and removed needs-upstream-testing; status changed to confirmed.

[Kalsan (info-kalsan)]

Weird, this happens on ANY computer I try, both Ubuntu 11.10 and 12.04, no matter if it's a Laptop computer, a tower (Lenovo ThinkCenter) or an iMac (different ages).
Just fire up a terminal (Ctrl+Alt+T), sudo halt and you'll see.
How come there's nobody confirming this bug? Is there a duplicate? Why is this page dead?

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/950129