WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/check.c:134 check_for_bios_corruption 0xcb/0xe0()

[callum]

This occurred after waking the laptop from hibernation laptop is a Compaq nc6120

ProblemType: KernelOops
DistroRelease: Ubuntu 10.04
Package: linux-image-2.6.32-21-generic 2.6.32-21.32
Regression: No
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: callum 1430 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 21'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 25
   Simple ctrls : 18
Date: Mon Apr 19 08:54:02 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=UUID=a8bdc11c-54fb-4e0c-add5-e0d008f38b70
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100417)
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Hewlett-Packard HP Compaq nc6120 (PY505ET#ABU)
PccardctlIdent:
 Socket 0:
   no product info available
 Socket 1:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
 Socket 1:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-21-generic root=UUID=c388f657-79c8-4f03-a282-0dda915f011c ro quiet splash
RelatedPackageVersions: linux-firmware 1.34
RfKill:

SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.32/arch/x86/kernel/check.c:134 check_for_bios_corruption+0xcb/0xe0()
dmi.bios.date: 11/21/2005
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DTD Ver. F.0C
dmi.board.name: 099C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 39.1E
dmi.chassis.asset.tag: CNU5440F29
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68DTDVer.F.0C:bd11/21/2005:svnHewlett-Packard:pnHPCompaqnc6120(PY505ET#ABU):pvrF.0C:rvnHewlett-Packard:rn099C:rvrKBCVersion39.1E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq nc6120 (PY505ET#ABU)
dmi.product.version: F.0C
dmi.sys.vendor: Hewlett-Packard

[Jeremy Foshee (jeremyfoshee)]

Hi callum,

This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 566472

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

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

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

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