System locks on boot

Bug Description

My system just updated to Linux (3.2.0-19.31) (I am running precise)

After the update it said I needed to restart. I restarted and the system just sat at a blank purple screen and would not respond to input such as ctr-alt-del. After some time I pulled the power and tried again, same. So I went into grub and booted into 3.2.0-18 and that worked. 3.2.0-19 worked prior to the .31 update.

I am not sure what to do to get you good debugging info because I can't find any logs about the event. It will not let me use the ubuntu-bug linux because the old 3.2.0-18 is no longer "official" and 3.2.0-19 no longer boots.
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.94.1-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: andy 2699 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf7e20000 irq 61'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:10ec0892,10438410,00100302 HDA:80862805,80860101,00100000'
Controls : 50
Simple ctrls : 22
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=5a04738b-b5b4-4fbc-8b6d-83b20cacb20c
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120209.2)
IwConfig:
lo no wireless extensions.

virbr0 no wireless extensions.

eth0 no wireless extensions.
MachineType: System manufacturer System Product Name
Package: linux 3.2.0.19.21
PackageArchitecture: amd64
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-18-generic root=UUID=d33da78e-4d23-4d1b-bc3d-96021215d807 ro crashkernel=384M-2G:64M,2G-:128M quiet splash acpi_osi=Linux mtrr_spare_reg_nr=1 reboot=e,w vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-18.29-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.72
RfKill:
0: hci0: Bluetooth
Soft blocked: yes
Hard blocked: no
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-18-generic x86_64
UpgradeStatus: Upgraded to precise on 2012年03月20日 (1 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 02/21/2012
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3203
dmi.board.asset.tag: To be filled by O.E.M.
dmi.board.name: P8Z68-V PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3203:bd02/21/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VPRO:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: System Product Name
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

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

apport-collect 961823

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.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Also, I tried booting into "recovery" mode and the system again crashed, but I could see what looked like the end of a core dump or something like that.

I ran the command but I am not able to run the command on the kernel that is crashing because I can't boot into it to do that.

Out of curiosity I tried the latest mainline kernel from http://kernel.ubuntu.com/~kernel-ppa/mainline/ and it dose the same thing.

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 dist-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.