Messages in this thread | | | From | Neil Brown <> | Date | Tue, 5 Dec 2006 15:07:11 +1100 | Subject | Re: 2.6.19-rc6-mm2 |
| |
On Tuesday December 5, neilb@suse.de wrote: > > I notice it says: > | > v > > 090: 6b 6b 6b 6b 6a 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b 6b > > Single bit error detected. Probably bad RAM. > > Run memtest86+ or a similar memory test tool. > > Have you tried running memtest86 ??
As Andrew correctly pointed out, this bit error is not a RAM problem. It is actually the low bit of a counter a spinlock that was decremented just before the WARN_ON. So it simply indicates that the inode had already been freed, which I think we knew already.
Unfortunately I still have no idea why that inode had been freed but was still referenced by a dentry....
How repeatable as this bug? How did you narrow it down to that patch? Did you use git-bisect or something else?
Thanks, NeilBrown - 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/
| |