Messages in this thread | | | Date | Sat, 31 Dec 2005 03:06:16 -0800 (PST) | From | Chris Stromsoe <> | Subject | Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32 |
| |
On Sat, 31 Dec 2005, Willy Tarreau wrote: > On Fri, Dec 30, 2005 at 08:00:34PM -0800, Chris Stromsoe wrote: > >> I couldn't get the machine to come up with 2.4.32, 2.4.30, or 2.4.27. >> It was hanging and then throwing the SCSI errors below. The machine >> did come up with a vanilla 2.6.14.4 and appears to be working fine. >> I'm going to leave it up over the weekend and see if it oopses. If it >> would help, I can mail out the .config for the 2.4.32 and 2.6.14.4 >> builds, or provide other information of interest. > > Please do post at least the 2.4.32 .config, I'll try to boot it on my > system right here. I find it amazing that it suddenly stopped working > with the same kernels as before.
Both configs are at <http://hashbrown.cts.ucla.edu/pub/oops-200512/>.
I have no idea why it wouldn't come up with nosmp on the command line (being supplied by lilo as append="nosmp"). I tried warm boot, cold boot, removing all power from the hardware. I booted from a rescue cd that had 2.6 on it and the machine came up right away. I tried to go back to 2.4 and it hung and then had SCSI errors again, so I installed 2.6.14.4 and left it running. I can put a copy of the 2.4.32 kernel and modules up if that would help.
-Chris - 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/
| |