Re: PROBLEM: 2.6.0-test10 BUG/panic in mpage_end_io_read

[Andrew Morton]

Eric Jensen <ej@xxxxxxxxxxxx> wrote:
>
> kernel BUG at mm/filemap.c:332!
>  invalid operand: 0000 [#1]
>  CPU:    0
>  EIP:    0060:[<c0130f4a>]    Not tainted
>  EFLAGS: 00010246
>  EIP is at unlock_page+0x1a/0x40
>  eax: 00000000   ebx: c1083b08   ecx: 00000017   edx: c1500400
>  esi: c1500cf4   edi: 00000001   ebp: 00000003   esp: dfcc1f0c
>  ds: 007b   es: 007b   ss: 0068
>  Process md0_raid5 (pid: 17, threadinfo=dfcc0000 task=dfcdd2d0)
>  Stack: dffd2e34 cbe5f540 c016201e cbe5f540 dfbcd298 ffffffff dfbcd298 c02a2f75
>         cbe5f540 00000000 00000000 dfbcd298 dfd20b00 dff7ae00 dfd20b08 c17f872c
>  	   c17f8764 00000000 dff7ae74 00000000 00000002 00000001 00000004 ffffffff
>  Call Trace:
>   [<c016201e>] mpage_end_io_read+0x5e/0x80
>   [<c02a2f75>] handle_stripe+0x9e5/0xb30
>   [<c02a341c>] raid5d+0xec/0x110
>   [<c02a9af9>] md_thread+0xf9/0x140
>   [<c02a9a00>] md_thread+0x0/0x140

Could be that the MD layer is calling ->bi_end_io() more than once
for a particular BIO.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/