WARNING: at /build/buildd/linux-2.6.28/fs/buffer.c:1186 mark_buffer_dirty+0x84/0xb0()

[crashsystems]

When I started up a few minutes ago kerneloops prompted me to send a report about a kernel error. When that was complete a notification popped up mentioning a link to the report, though of course I was not able to click it or even see any link. A moment latter apport popped up, prompting me to report this bug.

I should mention that like many other people, I've recently been experiencing system lockups. In two of the three lockups I've experienced in the past 72 hours, the system has been idle, with only Firefox, Pidgin and Gwibber running. The third time, Handbrake was ripping a CC licensed movie. In all three occasions, I SSHd into the box and issues a halt command, which did not work. I then tried the system request keys (the REISUB trick), and that did not work ether. Ever time I was forced to do a hard reset.

System details:
Inspiron 1420
Ubuntu 9.04 amd64, last updated 11 April 18:00 GMT-5

apt-cache policy linux-image-2.6.28-11-generic
linux-image-2.6.28-11-generic:
  Installed: 2.6.28-11.41
  Candidate: 2.6.28-11.41
  Version table:
 *** 2.6.28-11.41 0
        500 http://us.archive.ubuntu.com jaunty/main Packages
        100 /var/lib/dpkg/status

ProblemType: KernelOops
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
DistroRelease: Ubuntu 9.04
Failure: oops
MachineType: Dell Inc. Inspiron 1420
Package: linux-image-2.6.28-11-generic 2.6.28-11.41
ProcCmdLine: root=UUID=ae2e44a5-f2b4-4f0f-a49e-9e348b0de5b6 ro quiet splash
ProcVersionSignature: Ubuntu 2.6.28-11.41-generic
SourcePackage: linux
Tags: kernel-oops
Title: WARNING: at /build/buildd/linux-2.6.28/fs/buffer.c:1186 mark_buffer_dirty+0x84/0xb0()

[crashsystems (crashsystems)]

Here is some more info that might be useful. Please let me know if there is
anything I can do to help diagnose the bug.

[Leann Ogasawara (leannogasawara)]

Hi crashsystems,

Just out of curiosity, you mention you are able to ssh into the system after it hangs. Are you able to capture the dmesg output after you ssh in and is it always this same warning or different than what's reported here? I have seen other bugs regarding ext4 related kernel panics and system lockups, but I think they are a bit different from what you have here (bug 330824 and bug 348836). Thanks.

[crashsystems (crashsystems)]

When I have the freezups, I can and have retrieved the contents of dmesg. I'm not sure how different they are from the one posted here, but you can check out the contents from one such freeze at the link below.

http://launchpadlibrarian.net/25268211/dmesg.log

[Tommy B Jesnen (tommybjensen)]

In my case it does not seem to affect the system that badly. I am able to continue working as usual, and it occurs each and every time I boot.

I have also seen the error while using sshfs through fuse. The error occurs, but the connection/mount is still working. I am using ext4 for my local filesystems.

[Leann Ogasawara (leannogasawara)]

Hi crashsystems,

Can you test and confirm this issue exists with the latest development Karmic Alpha 9.10 release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

Also, if you could test the latest upstream kernel available that would be great (currently 2.6.31-rc3). 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.

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]