[Hewlett-Packard HP Compaq 6710b (RM342UT#ABA)] came out of sleep and saw a message indicating a kernel problem

[Stephane Vaucher]

First time this happens, I just installed the beta and put my machine to sleep. Coming out of sleep I did not notice anything weird, but I saw there was a problem as indicated by the ubuntu diagnostic system. If this continues (after installing 9.10), I'll add any debugging information required to help out.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: vaucher 2478 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xe4804000 irq 16'
   Mixer name : 'Analog Devices AD1981'
   Components : 'HDA:11d41981,103c30c0,00100200 HDA:11c11040,103c1378,00100200'
   Controls : 12
   Simple ctrls : 10
Date: Thu Oct 29 08:41:17 2009
DistroRelease: Ubuntu 9.10
Failure: oops
MachineType: Hewlett-Packard HP Compaq 6710b (RM342UT#ABA)
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=289aebec-3c15-4138-b31d-efab0dd6a4f9 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-14-generic N/A
 linux-firmware 1.24
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/net/mac80211/scan.c:281 ieee80211_scan_completed+0xf1/0x470 [mac80211]()
Uname: Linux 2.6.31-14-generic x86_64
WpaSupplicantLog:

dmi.bios.date: 11/04/2008
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68DDU Ver. F.14
dmi.board.name: 30C0
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 71.2E
dmi.chassis.asset.tag: CNU8131FSH
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68DDUVer.F.14:bd11/04/2008:svnHewlett-Packard:pnHPCompaq6710b(RM342UT#ABA):pvrF.14:rvnHewlett-Packard:rn30C0:rvrKBCVersion71.2E:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP Compaq 6710b (RM342UT#ABA)
dmi.product.version: F.14
dmi.sys.vendor: Hewlett-Packard

[schifpine1 (sschifko)]

Same problem. I ignored it the first time. Then it cam back about 20 minutes later.
Does not seem to affect anything. Compaq Presario V6000. Sister model of Tom's.
Have had Ubuntu 9.10 on for a couple of months with no problems. I have also never updated, might try that.

[Jeremy Foshee (jeremyfoshee)]

Hi Stephane,

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 463268

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

[Stephane Vaucher (svaucher)]

Hi Jeremy, this issue has been resolved for me (probably between the beta and official 9.10 release). Unless others still have the issue, you can close the bug. Thank you.