> > 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?
No. This is the only one. Even when I enter 'reboot' and hit enter, it
just freezes without any message. For quite a while (more than 5').
Nothing more appears, niether on screen nor on my serial console.
> 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.
That I tested. No bad block on the remote host (assertion happens
only when writing to a loop residing on a samba share, on a Win2k
host).
> Could you also please run ksymoops to decode the log trace?
Unfortunately no, I haven't got enough place on the machine to test
more than two kernel at a time. Now is time for the 2.4.18-pre7 with
the ext3 debug patch. But this one will get ksymoops run against.
Regards,
Yann.
PS. Because I'm often away from work in these days, and because my
test machine is a plain old Pentium Pro, I can't do tests as often as
I might want to... Please forgive slowliness...
YEM.
PPS. I'm not subscribed to ext2-devel, please copy me (or lkml).
YEM.
-- .---------------------------.----------------------.------------------. | Yann E. MORIN | Real-Time Embedded | ASCII RIBBON /"\ | | Phone: (33/0) 662 376 056 | Software Designer | CAMPAIGN \ / | | http://ymorin.free.fr °----------------------: AGAINST X | | yann.morin.1998@anciens.enib.fr | HTML MAIL / \ | °--------------------------------------------------°------------------°
- 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/