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

Bug #621801 reported by shaniac
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Evidently, my kernel oopsed. I didn't notice, but apport did.

ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-17-generic 2.6.35-17.23
Regression: Yes
Reproducible: No
ProcVersionSignature: Ubuntu 2.6.35-17.23-generic 2.6.35.2
Uname: Linux 2.6.35-17-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: shane 30415 F.... pulseaudio
 /dev/snd/controlC0: shane 30415 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf3ff4000 irq 51'
   Mixer name : 'Realtek ALC889'
   Components : 'HDA:10ec0889,10de0175,00100004'
   Controls : 41
   Simple ctrls : 23
Card1.Amixer.info:
 Card hw:1 'Bt878'/'Brooktree Bt878 at 0xf32fe000, irq 22'
   Mixer name : 'Bt87x'
   Components : ''
   Controls : 3
   Simple ctrls : 5
Date: Sat Aug 21 07:51:03 2010
Failure: oops
Frequency: I don't know.
HibernationDevice: RESUME=UUID=a7ff69e5-d27a-4f27-9f05-1c9f542a328a
MachineType: OEM OEM
ProcCmdLine: root=UUID=99c13395-8d09-4a43-b364-3b515c2d09f5 ro crashkernel=384M-2G:64M,2G-:128M
RelatedPackageVersions: linux-firmware 1.38
RfKill:
 0: hci0: Bluetooth
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
Title: WARNING: at /build/buildd/linux-2.6.35/fs/buffer.c:1151 mark_buffer_dirty+0x7f/0xa0()
WpaSupplicantLog:

dmi.bios.date: 01/16/2009
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: 132-BL-E758
dmi.board.vendor: EVGA
dmi.board.version: Tylersburg
dmi.chassis.type: 3
dmi.chassis.vendor: OEM
dmi.chassis.version: OEM
dmi.modalias: dmi:bvnPhoenixTechnologies,LTD:bvr6.00PG:bd01/16/2009:svnOEM:pnOEM:pvrOEM:rvnEVGA:rn132-BL-E758:rvrTylersburg:cvnOEM:ct3:cvrOEM:
dmi.product.name: OEM
dmi.product.version: OEM
dmi.sys.vendor: OEM

Revision history for this message
shaniac (biff-shaniac) wrote :
Brad Figg (brad-figg)
tags: added: acpi-bad-address
tags: added: acpi-bad-length
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
tags: removed: regression-potential
Revision history for this message
penalvch (penalvch) wrote :

shaniac, 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.