From: Diego Calleja <diegocg@gmail.com>
To: Thomas Meyer <thomas@m3y3r.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"linux-btrfs" <linux-btrfs@vger.kernel.org>
Subject: Re: kernel BUG at fs/btrfs/disk-io.c:2221!
Date: Sat, 1 Aug 2009 20:34:00 +0200 [thread overview]
Message-ID: <200908012034.01055.diegocg@gmail.com> (raw)
In-Reply-To: <1249120208.14496.3.camel@localhost>
You probably should have CC'ed the btrfs mailing list
(I already did in this mail)
On Sábado 01 Agosto 2009 11:50:08 Thomas Meyer escribió:
> kernel BUG at fs/btrfs/disk-io.c:2221!
> invalid opcode: 0000 [#1] PREEMPT SMP
> last sysfs file: /sys/block/sdc/sdc1/start
> CPU 1
> Modules linked in: btrfs olympic forcedeth rndis_wlan floppy [last unloaded: scsi_wait_scan]
> Pid: 23806, comm: umount Tainted: G W 2.6.31-rc4-rt1 #3 MS-7250
> RIP: 0010:[<ffffffffa00589ad>] [<ffffffffa00589ad>] write_all_supers+0x22f/0x259 [btrfs]
> RSP: 0018:ffff88009e575ce8 EFLAGS: 00010292
> RAX: 000000000000003a RBX: ffff8801980889f8 RCX: ffff88009e575ba8
> RDX: 0000000000000000 RSI: 0000000000000202 RDI: 000000005661d985
> RBP: 0000000000000001 R08: 0000000000000002 R09: 0000000000000000
> R10: 0000000000000000 R11: ffff88009e575c88 R12: ffff88011e0b2000
> R13: 0000000000000000 R14: ffff880198088980 R15: ffff88011e094ed6
> FS: 00007fa0ba6ef740(0000) GS:ffff8800280ac000(0000) knlGS:00000000f49ffb70
> CS: 0010 DS: 0000 ES: 0000 CR0: 000000008005003b
> CR2: 0000000000be1858 CR3: 000000009204a000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process umount (pid: 23806, threadinfo ffff88009e574000, task ffff8801bbd3a760)
> Stack:
> ffff88009e575d10 ffff88011e094ee6 0000000100000000 ffff88011e094dcb
> <0> ffff8801980889f8 000000008439bfff 000000008439c000 000000005661d985
> <0> 00000000852b4000 ffff88011e0b2000 ffff88018024f8a0 ffff880091c92d70
> Call Trace:
> [<ffffffffa005c510>] ? btrfs_commit_transaction+0x5ff/0x6d7 [btrfs]
> [<ffffffff810884bd>] ? autoremove_wake_function+0x0/0x55
> [<ffffffff81166dfc>] ? sync_quota_sb+0x58/0x133
> [<ffffffff8113a1a4>] ? __sync_filesystem+0x3b/0x82
> [<ffffffff81118cd3>] ? generic_shutdown_super+0x31/0x10c
> [<ffffffff81118e28>] ? kill_anon_super+0x1d/0x71
> [<ffffffff81119691>] ? deactivate_super+0x63/0xa6
> [<ffffffff81130949>] ? sys_umount+0x2e4/0x32a
> [<ffffffff8102bf2b>] ? system_call_fastpath+0x16/0x1b
> Code: 24 90 01 00 00 48 8b b8 b0 21 00 00 48 83 c7 48 e8 dd 30 7b e1 3b 6c 24 10 7e 14 89 ee 48 c7 c7 1a 39 09 a0 31 c0 e8 eb 09 7b e1 <0f> 0b eb fe 31 c0 48 8b 54 24 38 65 48 33 14 25 28 00 00 00 74
> RIP [<ffffffffa00589ad>] write_all_supers+0x22f/0x259 [btrfs]
> RSP <ffff88009e575ce8>
> ---[ end trace 1e2f23bdcf389667 ]---
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2009-08-01 18:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-01 9:50 kernel BUG at fs/btrfs/disk-io.c:2221! Thomas Meyer
2009-08-01 18:34 ` Diego Calleja [this message]
2009-08-03 14:02 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200908012034.01055.diegocg@gmail.com \
--to=diegocg@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=thomas@m3y3r.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox