WARNING: at /build/buildd/linux-2.6.31/fs/buffer.c:1152 mark_buffer_dirty - scsi bug

[Michael Shulman]

I just upgraded to karmic alpha, and after mounting and unmounting some external drives (regarding another bug), I was prompted by a message to file this bug. I noticed some other people with similar error messages mentioned suspending+resuming, but I haven't suspended since the upgrade & reboot.

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: i386
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: shulman 2370 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'ICH6'/'Intel ICH6 with AD1981B at irq 22'
   Mixer name : 'Analog Devices AD1981B'
   Components : 'AC97a:41445374'
   Controls : 26
   Simple ctrls : 18
Date: Sat Sep 19 22:34:10 2009
DistroRelease: Ubuntu 9.10
Failure: oops
HibernationDevice: RESUME=
Lsusb:
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: IBM 2527B4U
Package: linux-image-2.6.31-10-generic 2.6.31-10.34
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: root=UUID=c79287f0-f0e9-4326-bf22-fde180e1d028 ro resume=/dev/sda6 acpi_sleep=s3_bios quiet splash
ProcVersionSignature: Ubuntu 2.6.31-10.34-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-10-generic N/A
 linux-firmware 1.19
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-10-generic i686
dmi.bios.date: 03/14/2006
dmi.bios.vendor: IBM
dmi.bios.version: 74ET61WW (2.06 )
dmi.board.name: 2527B4U
dmi.board.vendor: IBM
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: IBM
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnIBM:bvr74ET61WW(2.06):bd03/14/2006:svnIBM:pn2527B4U:pvrThinkPadX41:rvnIBM:rn2527B4U:rvrNotAvailable:cvnIBM:ct10:cvrNotAvailable:
dmi.product.name: 2527B4U
dmi.product.version: ThinkPad X41
dmi.sys.vendor: IBM

[Bernard Opic (cpio)]

The issue occured with an external USB Hard Drive.

[Paolo Sammicheli (xdatap1)]

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.

[Paolo Sammicheli (xdatap1)]

ops, sorry. I made Paste in the wrong tab. LOL

[Paolo Sammicheli (xdatap1)]

I tryied to unify all duplicated bug into this one which seem the oldest. Please add your toughts and workaround you found here.

Thank you for taking the time to report bugs and helping to make Ubuntu better.

[Mathieu Charron (elwillow)]

confirmed on a Fujitsu A6110 running karmic 2.6.31-14-generic amd64.

I can't tell what happen. I was away from my computer. I had an external usb disk plugged in.

[Andis (andis-lazdins)]

It happened also on Acer Aspire 9420 running Karmic 2.6.31-14 32 bit

[Peter B P (peterbp)]

Happened on Lenovo SL500 when trying to access an external 2,5" USb drive that had been attached for some hours, and was spun down. The drive disappeared from the desktop and was reattached and remounted seemingly without problem.

[deLeewit (thomsin)]

It happens on my Gateway GT5228 running Karmic 2.6.31-14 64bit with an external USB drive (Maxtor OneTouchPlus formatted as ext3). The drive spins down and unmounts itself after awhile. Unplugging and plugging back in remounts it.

[Brian Lassiter (darknightviii)]

I'm running a Compaq Presario, SR5214X Intel Pentium Dual-Core E2140. I tried to load a dvd to install a program and got this.

[Paul Tap (paul-tap)]

Same here on a Lenovo D10. I attached and detached an external USB drive and got the message. Stupid me, forgot to unmount, but I don't think this should happen. Just let me lose all my data or so...

[wirechief (wirechief)]

I did a update with the update manager however this crash might of occurred before i did the update, i was half asleep when i checked the results (usually everything just works) i am using virtualbox and if i continue to have
issues will resort to using a earlier snapshot and doing the update another day.

[Gabe Gorelick (gabegorelick)]

Switched the upstream watch from Gentoo to Linux, since that bug report is actually a Linux bug report that just so happens to effect Gentoo.

[agentfusion (digital-aggressor)]

same bug here too. it seems to be prevalent in Acer and Lenovo systems, or any system with the AC97 chipset. Almost exclusively notebooks/netbooks with this bug, and always after using a USB device of some sort. It has been my experience that nothing actually -happens- afterwards though... it does not make the system in any way unstable. May be a false-positive. recommend ignoring it.

[Adrian Black (a-black-italia)]

"same bug here too. it seems to be prevalent in Acer and Lenovo systems, or any system with the AC97 chipset. Almost exclusively notebooks/netbooks with this bug, and always after using a USB device of some sort. It has been my experience that nothing actually -happens- afterwards though... it does not make the system in any way unstable. May be a false-positive. recommend ignoring it."

What the ....

My system doesn't have an AC97 chipset - it is not a notebook and it is definitely not an Acer or lenovo.

Prevalent - yeps (sarcasm)

Recommend not ignoring it - it happens to me every single day of the week on an AMD tower with a nvidia card.

Unstable - no - but it means that copying anything from a USB drive to anywhere other than local is unstable hence unreliable as the drive is liable to reset halfway through a long copy.

[gf (gfcyb.org)]

my system is a Apple iMac 7.1 (aluminium).
i'm using ubuntu 10.04 Alpha 3, with all the updates of the day, taken from official repositories.

external usb-drive is this 1 TB Iomega (aluminium case): Prestige Desktop Hard Drive, USB 2.0
https://iomega-eu-en.custhelp.com/cgi-bin/iomega_eu_en.cfg/php/enduser/std_adp.php?p_faqid=20144&p_sid=RERuMVRj&p_lva=20147&p_sp=&p_li=

[goose (m3tmh)]

Hmm yes. My system is a HP Pavillion DV6700, Karmic 2.6.31-14-generic, uptime 8 days. It happened with a removable 2.5'' USB HDD, but as Adrian Black says, it doesn't *seem* to do anything adverse. I think the message appeared while I was away but nothing seems wrong.

[Broomer68 (jbezemer)]

On my homebrew Athlon X2 this happenend to me today, althoug I did nog experience strange things.
I was swapping SD-cards and mounting/flashing my ebook-reader.
This with Lucid beta (64) with up to today's updates.

[blippe (blippe-mailinator)]

I got this bug now in ubuntu10.04beta1 and the bug-reporting thing led me here,
but I don't know anything more about it.

[PappaTobbe (pappatobbe-deactivatedaccount)]

got the bug just now...just updated...

[DrFrank (cimryan)]

Running Ubuntu 9.10 from a live SD card on an Acer Aspire Revo 3610. Plugged in an 8 GB USB drive that contained another live install of 9.10.

[Mike Kupfer (mkupfer37)]

I got the same error trying to use an ext3 partition from an old
Iomega 40GB disk (external USB). Different stack trace, though.

This was the first time I tried to use the disk under Karmic. There
may well be a problem with the disk, though it seemed to work okay
under Jaunty. I've attached excerpts from /var/log/syslog, including
the stack trace.

[skquinn (skquinn)]

I just came home to this after being away from my system for about 24 hours. No idea what could have caused it.

[Brad Figg (brad-figg)]

This bug was filed against a series that is no longer supported and so is being marked as Won't Fix. If this issue still exists in a supported series, please file a new bug.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.