Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32

On Sun, 8 Jan 2006, Willy Tarreau wrote:

Eventhough I don't like this, I would join Roberto's advice to upgrade to 2.6 and stick to it. If you finally encounter the same problem on 2.6 after a very long time, then it would be an indication that the problem is well in your hardware.

I'll keep 2.4.32 with DEBUG_SLAB up until it oopses again and will report that. After, I'll probably stick with 2.6. Thanks.

-Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
    • From: Chris Stromsoe <[email protected]>
  • Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
    • From: Willy Tarreau <[email protected]>
  • Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
    • From: Chris Stromsoe <[email protected]>
  • Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
    • From: Willy Tarreau <[email protected]>

• Prev by Date: Re: [patch 2/2] Access Control Lists for tmpfs
• Next by Date: Re: PROBLEM: PS/2 keyboard does not work with 2.6.15
• Previous by thread: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
• Next by thread: Re: Recursive dependency for SAA7134 in 2.6.15-rc7
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]