kernel BUG at /build/buildd/linux-3.2.0/fs/btrfs/transaction.c:1337!

[Jan Simon]

I get a crash when i remove a USB-HDD with a btrfs partition on it without unmounting it.

ProblemType: KernelOops
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-20-generic
Uname: Linux 3.2.0-20-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
Date: Fri Mar 23 14:56:27 2012
Failure: oops
SourcePackage: linux
---
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: jaynfm 1982 F.... pulseaudio
CheckboxSubmission: 0126eb8c2d63dc5aa8166f1abaebf6da
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=254bd9c8-f78d-493a-aaa1-cb3aa6a7e2b1
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: LENOVO 7453WQ2
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=790e8b24-b458-43f6-8663-010704c37b27 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-20.32-generic 3.2.12
StagingDrivers: mei
Tags: precise staging
Uname: Linux 3.2.0-20-generic x86_64
UpgradeStatus: Upgraded to precise on 2012-02-14 (37 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 03/08/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 7WET68WW (3.18 )
dmi.board.name: 7453WQ2
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvr7WET68WW(3.18):bd03/08/2011:svnLENOVO:pn7453WQ2:pvrThinkPadX200Tablet:rvnLENOVO:rn7453WQ2:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 7453WQ2
dmi.product.version: ThinkPad X200 Tablet
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 963107

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

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

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Jan Simon (jan-simon)]

apport information

[Luis Henriques (henrix)]

Similar/same issue seems to be reported here: https://lkml.org/lkml/2012/2/11/102

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.3 kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[1] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.3-precise/

[Jan Simon (jan-simon)]

Tested it, bug exists upstream as well.

[Joseph Salisbury (jsalisbury)]

This issue appears to be an upstream bug, since you tested the latest upstream kernel. Would it be possible for you to open an upstream bug report at bugzilla.kernel.org [1]? That will allow the upstream Developers to examine the issue, and may provide a quicker resolution to the bug.

If you are comfortable with opening a bug upstream, It would be great if you can report back the upstream bug number in this bug report. That will allow us to link this bug to the upstream report.

[1] https://wiki.ubuntu.com/Bugs/Upstream/kernel

[Jan Simon (jan-simon)]

It's already reported there: https://bugzilla.kernel.org/show_bug.cgi?id=42953 . I linked this report there.