Ubuntu
linux package

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

Bug #461272 reported by T Kortehisto on 2009-10-26

This bug report is a duplicate of: Bug #433365: WARNING: at /build/buildd/linux-2.6.31/fs/buffer.c:1152 mark_buffer_dirty - scsi bug. Edit Remove

This bug affects 5 people

Affects		Status	Importance	Assigned to	Milestone
	linux (Ubuntu)	New	Undecided	Unassigned

Bug Description

I was trying find out what partitions existed on Lacie Desktop 1 TB (USB drive) with testdisk because gparted does not regognize the drive partitions correctly (shows only unallocated space and 1 KB partition which is incorrect). Everything worked fine in testdisk, but after I exited it I got a message "Your system might become unstable now and might need to be restarted." and I was prompted for reporting a bug.

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: ALC880 Analog [ALC880 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
Architecture: i386
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/controlC0: terri 1977 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'Intel'/'HDA Intel at 0xf3afc000 irq 16'
   Mixer name : 'Realtek ALC880'
   Components : 'HDA:10ec0880,8086e203,00100800'
   Controls : 32
   Simple ctrls : 19
Date: Mon Oct 26 17:47:39 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=UUID=4c30c040-a2fe-441b-b637-1f5ad6fde82e
IwConfig:
lo no wireless extensions.

eth0 no wireless extensions.
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-14-generic 2.6.31-14.48
ProcCmdLine: BOOT_IMAGE=/vmlinuz-2.6.31-14-generic root=UUID=38a42af7-ab9f-41fc-ad46-3c9e7e039732 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
RfKill:

SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.31/fs/buffer.c:1152 mark_buffer_dirty+0x70/0x90()
Uname: Linux 2.6.31-14-generic i686
dmi.bios.date: 04/29/2005
dmi.bios.vendor: Intel Corp.
dmi.bios.version: EV91510A.86A.0444.2005.0429.2108
dmi.board.name: D915GAV
dmi.board.vendor: Intel Corporation
dmi.board.version: AAC64134-403
dmi.chassis.type: 2
dmi.modalias: dmi:bvnIntelCorp.:bvrEV91510A.86A.0444.2005.0429.2108:bd04/29/2005:svn:pn:pvr:rvnIntelCorporation:rnD915GAV:rvrAAC64134-403:cvn:ct2:cvr:

Tags:

Revision history for this message

T Kortehisto (kortehisto) wrote on 2009-10-26:

AlsaDevices.txt Edit (461 bytes, text/plain; charset="utf-8")
ArecordDevices.txt Edit (299 bytes, text/plain; charset="utf-8")
BootDmesg.txt Edit (41.0 KiB, text/plain; charset="utf-8")
Card0.Amixer.values.txt Edit (3.6 KiB, text/plain; charset="utf-8")
Card0.Codecs.codec.2.txt Edit (9.5 KiB, text/plain; charset="utf-8")
CurrentDmesg.txt Edit (4.0 KiB, text/plain; charset="utf-8")
Dependencies.txt Edit (1.2 KiB, text/plain; charset="utf-8")
Lspci.txt Edit (22.7 KiB, text/plain; charset="utf-8")
Lsusb.txt Edit (359 bytes, text/plain; charset="utf-8")
OopsText.txt Edit (1.6 KiB, text/plain; charset="utf-8")
PciMultimedia.txt Edit (1.6 KiB, text/plain; charset="utf-8")
ProcCpuinfo.txt Edit (1.2 KiB, text/plain; charset="utf-8")
ProcInterrupts.txt Edit (1.5 KiB, text/plain; charset="utf-8")
ProcModules.txt Edit (2.6 KiB, text/plain; charset="utf-8")
UdevDb.txt Edit (87.9 KiB, text/plain; charset="utf-8")
UdevLog.txt Edit (97.3 KiB, text/plain; charset="utf-8")
WifiSyslog.txt Edit (368.4 KiB, text/plain; charset="utf-8")

Brian Murray (brian-murray) on 2009-10-26

affects:

ubuntu → linux (Ubuntu)

Revision history for this message

Paolo Sammicheli (xdatap1) wrote on 2009-11-03:

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #433365, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.