Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- From: Willy Tarreau <willy@xxxxxxxxx>
- Date: Sat, 31 Dec 2005 08:25:28 +0100
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.
> -Chris
Willy
-
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/
- Follow-Ups:
- Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- From: Chris Stromsoe
- Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- References:
- bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- From: Chris Stromsoe
- Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- From: Marcelo Tosatti
- Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- From: Chris Stromsoe
- Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- From: Chris Stromsoe
- Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- From: Chris Stromsoe
- Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- From: Chris Stromsoe
- bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- Prev by Date: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- Next by Date: Re: [PATCH 1/5] Swap Migration V5: LRU operations
- Previous by thread: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- Next by thread: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
- Index(es):