From: Tomasz Chmielewski <mangoo@wpkg.org>
Cc: Linux-Raid <linux-raid@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sysfs Kernel BUG when RAID bitmap file has IO errors
Date: Wed, 12 Mar 2008 10:51:38 +0100 [thread overview]
Message-ID: <47D7A7AA.8000302@wpkg.org> (raw)
In-Reply-To: <47D7A502.6020701@wpkg.org>
Tomasz Chmielewski schrieb:
(...)
> Let's access "/sys/block/md0/md/dev-sdd1/super":
>
> # cat /sys/block/md0/md/dev-sdd1/super
>
> # dmesg -c
> ------------[ cut here ]------------
> Kernel BUG at 78178626 [verbose debug info unavailable]
It turns out a broken RAID bitmap file has nothing to do with it - the
same happens on a different machine without a bitmap file:
------------[ cut here ]------------
Kernel BUG at 7817736a [verbose debug info unavailable]
invalid opcode: 0000 [#1]
Modules linked in: as_iosched nfs lockd nfs_acl sunrpc bonding dm_mirror
dm_snapshot e1000 sata_mv
Pid: 2494, comm: cat Not tainted (2.6.24.3-1 #1)
EIP: 0060:[<7817736a>] EFLAGS: 00010212 CPU: 0
EIP is at sysfs_read_file+0x88/0xd4
EAX: 00000001 EBX: 961b5880 ECX: 00000000 EDX: 964ef360
ESI: 00001000 EDI: 964ef3c0 EBP: 9705bd04 ESP: 971f1f54
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process cat (pid: 2494, ti=971f0000 task=970ad9a0 task.ti=971f0000)
Stack: 96443080 0804b4d8 00001000 0804e000 961b5894 7835f6f0 96193400
0804e000
781772e2 00001000 78149bd5 971f1fa0 00001000 96193400 fffffff7
0804e000
971f0000 78149f03 971f1fa0 00000000 00000000 00000000 00000003
0804e000
Call Trace:
[<781772e2>] sysfs_read_file+0x0/0xd4
[<78149bd5>] vfs_read+0x88/0x10a
[<78149f03>] sys_read+0x41/0x67
[<78103bba>] syscall_call+0x7/0xb
=======================
Code: c0 74 61 8b 47 18 8b 4b 0c 8b 40 04 89 43 24 89 e8 8b 74 24 14 8b
57 14 ff 16 89 c6 89 f8 e8 18 0b 00 00 81 fe ff 0f 00 00 7e 04 <0f> 0b
eb fe 85 f6 78 31 c7 43 20 00 00 00 00 89 33 eb 07 be f4
EIP: [<7817736a>] sysfs_read_file+0x88/0xd4 SS:ESP 0068:971f1f54
---[ end trace e39b88900c26a529 ]---
Certainly, it doesn't happen with 2.6.18 kernels.
--
Tomasz Chmielewski
http://wpkg.org
WARNING: multiple messages have this Message-ID (diff)
From: Tomasz Chmielewski <mangoo@wpkg.org>
To: unlisted-recipients:; (no To-header on input)
Cc: Linux-Raid <linux-raid@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: sysfs Kernel BUG when RAID bitmap file has IO errors
Date: Wed, 12 Mar 2008 10:51:38 +0100 [thread overview]
Message-ID: <47D7A7AA.8000302@wpkg.org> (raw)
In-Reply-To: <47D7A502.6020701@wpkg.org>
Tomasz Chmielewski schrieb:
(...)
> Let's access "/sys/block/md0/md/dev-sdd1/super":
>
> # cat /sys/block/md0/md/dev-sdd1/super
>
> # dmesg -c
> ------------[ cut here ]------------
> Kernel BUG at 78178626 [verbose debug info unavailable]
It turns out a broken RAID bitmap file has nothing to do with it - the
same happens on a different machine without a bitmap file:
------------[ cut here ]------------
Kernel BUG at 7817736a [verbose debug info unavailable]
invalid opcode: 0000 [#1]
Modules linked in: as_iosched nfs lockd nfs_acl sunrpc bonding dm_mirror
dm_snapshot e1000 sata_mv
Pid: 2494, comm: cat Not tainted (2.6.24.3-1 #1)
EIP: 0060:[<7817736a>] EFLAGS: 00010212 CPU: 0
EIP is at sysfs_read_file+0x88/0xd4
EAX: 00000001 EBX: 961b5880 ECX: 00000000 EDX: 964ef360
ESI: 00001000 EDI: 964ef3c0 EBP: 9705bd04 ESP: 971f1f54
DS: 007b ES: 007b FS: 0000 GS: 0033 SS: 0068
Process cat (pid: 2494, ti=971f0000 task=970ad9a0 task.ti=971f0000)
Stack: 96443080 0804b4d8 00001000 0804e000 961b5894 7835f6f0 96193400
0804e000
781772e2 00001000 78149bd5 971f1fa0 00001000 96193400 fffffff7
0804e000
971f0000 78149f03 971f1fa0 00000000 00000000 00000000 00000003
0804e000
Call Trace:
[<781772e2>] sysfs_read_file+0x0/0xd4
[<78149bd5>] vfs_read+0x88/0x10a
[<78149f03>] sys_read+0x41/0x67
[<78103bba>] syscall_call+0x7/0xb
=======================
Code: c0 74 61 8b 47 18 8b 4b 0c 8b 40 04 89 43 24 89 e8 8b 74 24 14 8b
57 14 ff 16 89 c6 89 f8 e8 18 0b 00 00 81 fe ff 0f 00 00 7e 04 <0f> 0b
eb fe 85 f6 78 31 c7 43 20 00 00 00 00 89 33 eb 07 be f4
EIP: [<7817736a>] sysfs_read_file+0x88/0xd4 SS:ESP 0068:971f1f54
---[ end trace e39b88900c26a529 ]---
Certainly, it doesn't happen with 2.6.18 kernels.
--
Tomasz Chmielewski
http://wpkg.org
next prev parent reply other threads:[~2008-03-12 9:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 9:40 sysfs Kernel BUG when RAID bitmap file has IO errors Tomasz Chmielewski
2008-03-12 9:51 ` Tomasz Chmielewski [this message]
2008-03-12 9:51 ` Tomasz Chmielewski
2008-03-12 22:36 ` Andrew Morton
2008-03-12 22:43 ` Andrew Morton
2008-03-14 4:34 ` Neil Brown
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=47D7A7AA.8000302@wpkg.org \
--to=mangoo@wpkg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.