Re: [patch] Real-Time Preemption, -VP-2.6.9-rc4-mm1-U0

From: Ingo Molnar
Date: Thu Oct 14 2004 - 15:48:41 EST



* Daniel Walker <dwalker@xxxxxxxxxx> wrote:

> I'm not sure about this one ..
>
> ------------[ cut here ]------------
> kernel BUG at fs/buffer.c:1360!

> EIP is at __find_get_block+0xe1/0x100

> Call Trace:
> [<c01619fe>] __getblk+0x1e/0x60
> [<c0161a99>] __bread+0x19/0x40
> [<c019aff0>] ext3_get_branch+0x70/0x100
> [<c019b61a>] ext3_get_block_handle+0x7a/0x2e0
> [<c026b1ee>] as_choose_req+0xe/0x1e0
> [<c026bc5f>] as_update_arq+0x1f/0x60
> [<c019b8c3>] ext3_get_block+0x43/0x80
> [<c0163735>] generic_block_bmap+0x35/0x40
> [<c0134c73>] __mcount+0x13/0x20
> [<c019c26d>] ext3_bmap+0xd/0xa0
> [<c01797c5>] bmap+0x45/0x60
> [<c019c2dc>] ext3_bmap+0x7c/0xa0
> [<c019b880>] ext3_get_block+0x0/0x80
> [<c01797c5>] bmap+0x45/0x60
> [<c01af8c2>] journal_bmap+0x42/0xa0
> [<c0134c73>] __mcount+0x13/0x20
> [<c0134249>] _mutex_unlock+0x9/0x60
> [<c01af827>] journal_next_log_block+0x47/0xa0
> [<c0113d30>] mcount+0x14/0x18
> [<c01af832>] journal_next_log_block+0x52/0xa0
> [<c01af939>] journal_get_descriptor_buffer+0x19/0xc0
> [<c01ac4ec>] journal_commit_transaction+0xf6c/0x13e0
> [<c01aedee>] kjournald+0xce/0x260
> [<c013555c>] sub_preempt_count+0x7c/0xa0
> [<c0133d00>] autoremove_wake_function+0x0/0x60
> [<c03b2a33>] _spin_unlock_irq+0x13/0x40
> [<c0133d00>] autoremove_wake_function+0x0/0x60
> [<c0119459>] schedule_tail+0x19/0x60
> [<c01aece0>] commit_timeout+0x0/0x20
> [<c01aed20>] kjournald+0x0/0x260
> [<c0103339>] kernel_thread_helper+0x5/0xc

this is a weird one. This is the first message, right? I've reviewed
bh_lru_lock/unlock and cannot spot anything that could be wrong there.

Ingo
-
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/