WARNING: at /build/buildd/linux-2.6.35/arch/x86/include/asm/processor.h:1005 read_measured_perf_ctrs+0x78/0x90()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Linux |
Unknown
|
Unknown
|
|||
linux (Ubuntu) |
Triaged
|
Medium
|
Unassigned |
Bug Description
Happens at each time Ubuntu starts up, apport shows up with this. Kernel is still stable after that, no problem to report when I'm using it.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
Reproducible: Yes
ProcVersionSign
Uname: Linux 2.6.35-22-generic x86_64
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
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: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: ALC269 Analog [ALC269 Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] Aucun fichier ou dossier de ce type
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf7cf8000 irq 46'
Mixer name : 'Realtek ALC269'
Components : 'HDA:10ec0269,
Controls : 9
Simple ctrls : 5
Date: Mon Sep 20 14:45:34 2010
Failure: oops
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
MachineType: ASUSTeK Computer INC. 1005PX
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
SourcePackage: linux
Title: WARNING: at /build/
dmi.bios.date: 04/30/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0601
dmi.board.
dmi.board.name: 1001PX
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: x.xx
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer INC.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: 1005PX
dmi.product.
dmi.sys.vendor: ASUSTeK Computer INC.
Hi Julien,
It seems this is being actively investigated by the upstream kernel devs. I've added and upstream bug watch to the upstream bugzilla.kernel.org bug report. Thanks.