Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
From: Chris Stromsoe
Date: Wed Feb 08 2006 - 01:30:51 EST
On Sun, 15 Jan 2006, Chris Stromsoe wrote:
On Sun, 15 Jan 2006, Willy TARREAU wrote:
Thanks for the precision. So logically we should expect it to break
sooner or later ?
It is the same .config as one that crashed before, except that it has
DEBUG_SLAB defined. If it does not crash, then adding pci=noacpi to the
command fixes the problem for me.
For what it's worth, I'm fairly certain at this point that the problem was
hardware related. After a week of uptime with 2.6 we had another pmd
error and oops. We then replaced the system board and one of the CPUs and
have not seen any problems since.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/