WARNING: at /build/buildd/linux-2.6.35/kernel/trace/ring_buffer.c:2017 rb_add_time_stamp+0x70/0x220()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Undecided
|
Unassigned |
Bug Description
I have no idea what this is about. This is a new laptop that I just installed Lucid on and upgraded to Maverick. After the first suspend/resume there was a notification telling me to file this kernel bug, but I have so far no idea what relation it has to anything: as far as I can tell my system is still working just fine.
For added unhelpfulness bugs.edge.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: No
Reproducible: No
ProcVersionSign
Uname: Linux 2.6.35-9-generic i686
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: Intel [HDA Intel], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf2620000 irq 46'
Mixer name : 'Intel IbexPeak HDMI'
Components : 'HDA:14f15069,
Controls : 14
Simple ctrls : 6
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'
Mixer name : 'ThinkPad EC 6IHT35WW-1.10'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Thu Jul 22 20:41:00 2010
Failure: oops
Frequency: This has only happened once.
HibernationDevice: RESUME=
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
Lsusb:
Bus 002 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 005: ID 17ef:480f Lenovo Integrated Webcam [R5U877]
Bus 001 Device 002: ID 8087:0020 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 2516CTO
ProcCmdLine: BOOT_IMAGE=
RelatedPackageV
SourcePackage: linux
Title: [1266874868.066736] ------------[ cut here ]------------
dmi.bios.date: 06/07/2010
dmi.bios.vendor: LENOVO
dmi.bios.version: 6IET65WW (1.25 )
dmi.board.name: 2516CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 2516CTO
dmi.product.
dmi.sys.vendor: LENOVO
tags: | added: kj-triage |
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
summary: |
- Unexplained crash report with no apparent symptom + WARNING: at /build/buildd/linux-2.6.35/kernel/trace/ring_buffer.c:2017 + rb_add_time_stamp+0x70/0x220() |
Andrew Bennetts, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 10, 2012. /wiki.ubuntu. com/Releases
Please see this document for currently supported Ubuntu releases:
https:/
We were wondering if this is still an issue in a supported release? If so, could you please provide the information following https:/ /wiki.ubuntu. com/DebuggingKe rnelSuspendHibe rnateResume ? As well, can you try with the latest development release of Ubuntu? ISO CD images are available from http:// cdimage. ubuntu. com/releases/ . However, note you can only test Suspend, not Hibernate, when using a LiveCD. If the issue remains, run the following command in the development release from a Terminal (Applications- >Accessories- >Terminal) as it will automatically gather and attach updated debug information to this report.
apport-collect -p linux <BUGNUMBER>
Additionally, if you could try to reproduce this with the upstream mainline kernel that would be great. It will allow additional upstream developers to examine the issue. Refer to https:/ /wiki.ubuntu. com/KernelMainl ineBuilds . 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.
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' .
Please let us know your results. Thanks in advance.