Re: kernel BUG at inode.c:654!

From: Santiago Garcia Mantinan (manty@udc.es)
Date: Mon May 28 2001 - 03:13:20 EST

Next message: Carlos E Gorges: "[PATCH] tiny cleanup ..."
Previous message: Stefan.Bader@de.ibm.com: "loop.c: (rare) race condition"
In reply to: Alexander Viro: "Re: kernel BUG at inode.c:654!"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Lovely... It's one of the long lists and these asserts (lines 650 and 654)
> are exactly what would happen if it was corrupted at some place. OTOH, it
> may be for real - i.e. real inodes in wrong state getting on the list, rather
> than corrupted pointer.

You were right, corrupted pointer.

It was due to general memory corruption caused by RAM problems, sorry, it
happened just as I switched to 2.4.5 and I blamed it, it probably started
failing now, after months without any problem, because of the high
temperatures we are having this days.

Thanks for your help and sorry to have disturbed you all for not making a
memtest before :-(

Regards...

-- 
Manty/BestiaTester -> http://manty.net
-
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/

Next message: Carlos E Gorges: "[PATCH] tiny cleanup ..."
Previous message: Stefan.Bader@de.ibm.com: "loop.c: (rare) race condition"
In reply to: Alexander Viro: "Re: kernel BUG at inode.c:654!"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Thu May 31 2001 - 21:00:35 EST