WARNING: at /build/buildd/linux-2.6.35/fs/buffer.c:1151 mark_buffer_dirty+0x70/0x90()

Bug #628362 reported by Ben Hamblin-Pyke
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Running ubuntu 10.10, kernel crashed. Dell latitude D820

ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-19-generic 2.6.35-19.28
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-19.28-generic 2.6.35.3
Uname: Linux 2.6.35-19-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: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: qakgob 1426 F.... pulseaudio
 /dev/snd/pcmC0D0p: qakgob 1426 F...m pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xefebc000 irq 46'
   Mixer name : 'SigmaTel STAC9200'
   Components : 'HDA:83847690,102801cc,00102201 HDA:14f12bfa,14f100c3,00090000'
   Controls : 12
   Simple ctrls : 7
Date: Wed Sep 1 21:26:08 2010
Failure: oops
HibernationDevice: RESUME=UUID=96e36b02-d7c7-4783-bbf0-08971f0ecc00
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release i386 (20100816.1)
MachineType: Dell Inc. Latitude D820
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-19-generic root=UUID=12ba30b0-8b18-4d8a-90a4-5c667c0de436 ro quiet splash
RelatedPackageVersions: linux-firmware 1.38
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.35/fs/buffer.c:1151 mark_buffer_dirty+0x70/0x90()
dmi.bios.date: 06/04/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0GF470
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA09:bd06/04/2008:svnDellInc.:pnLatitudeD820:pvr:rvnDellInc.:rn0GF470:rvr:cvnDellInc.:ct8:cvr:
dmi.product.name: Latitude D820
dmi.sys.vendor: Dell Inc.

Revision history for this message
Ben Hamblin-Pyke (benzo3000) wrote :
Brad Figg (brad-figg)
tags: added: acpi
tags: added: acpi-table-checksum
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

Ben Hamblin-Pyke, thank you for reporting this and helping make Ubuntu better. Maverick reached EOL on April 2012.
Please see this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We were wondering if this is still an issue in a supported release? If so, 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 in a supported release from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

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.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.