Hi, On Thu, Jan 24, 2002 at 04:54:34PM +0100, frode wrote: > > I got the following error while rm'ing a 700mb file from an ext3 partition: > > Assertion failure in journal_unmap_buffer() at transaction.c:1857: > "transaction == journal->j_running_transaction" Hmm --- this is not one I think I've ever seen before. > >>EIP; c015ea1a <journal_unmap_buffer+fa/1b0> <===== > Trace; c015eb6e <journal_flushpage+9e/140> > Trace; c0156ae2 <ext3_flushpage+22/30> > Trace; c0125738 <do_flushpage+18/30> > Trace; c0125762 <truncate_complete_page+12/50> > Trace; c01258c6 <truncate_list_pages+126/190> > Trace; c0125970 <truncate_inode_pages+40/70> > Trace; c014485e <iput+ae/200> > Trace; c0142e4c <d_delete+4c/70> > Trace; c013c69c <vfs_unlink+13c/170> > Trace; c013c778 <sys_unlink+a8/120> > Trace; c0106e8a <system_call+32/38> Well, that's a straight forward trace, and looks perfectly normal for a delete operation. The buffer_head is locked at this point, and the transaction itself is pinned, so I can't see any way to have an unrecognised transaction here. > I use the 'mem=nopentium' option on the lilo prompt while booting, hoping to > reduce the rather large amount of oopses I have had recently, as I read > something about AMD Athlons and AGP causing troubles. Those problems included AGP cache coherency problems, but I didn't see any mention of other instabilities as a result. Also, > NVRM: loading NVIDIA NVdriver Kernel Module 1.0.2313 Tue Nov 27 12:01:24 PST 2001 with this driver loaded we really can't make any guarantees about your system stability at all. If you manage to eliminate other oopses and still get the ext3 one, even without the NVidia driver loaded, then there would be a much better change of debugging things, but right now it sounds like a hardware problem. Cheers, Stephen
