On Mon, Jan 28, 2002 at 05:07:12PM +0100, Yann E. MORIN wrote:
> I've encountered a reproductible 'Assertion failure' in 2.4.17.
> It happens on pure vanilla, as well as on sched O1-J0, and also on
> I'm able to write a bit of data on it (about a few Mib), and then I
> got this Assertion failure:
> --8<-- Begin --8<--
> Assertion failure in do_get_write_access() at transaction.c:728:
> "(((jh2bh(jh))->b_state & (1UL << BH_Uptodate)) != 0)"
Are there any other log messages in the kernel log?
The only easy way I can see for this to be triggered is if there is a
bad block on disk being accessed. That ought to appear in the log.
Could you also please run ksymoops to decode the log trace?
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/