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

On Sun, 15 Jan 2006, Willy Tarreau wrote:

On Sun, Jan 15, 2006 at 03:29:15AM -0800, Chris Stromsoe wrote:

I've been running stable with the propsed changes since the 10th. The original config and the currently running config are both at <http://hashbrown.cts.ucla.edu/pub/oops-200512/>. This is the diff:

cbs@hashbrown:~ > diff config-2.4.32 config-2.4.32-20060115

65c65
< CONFIG_HIGHIO=y
---
> # CONFIG_HIGHIO is not set

I wonder if this change could be suspected of affecting stability. With this unset, data will be sent from the card to low memory, then bounced to high mem when needed. Maybe the card, northbridge or anything else sometimes corrupts memory during direct highmem I/O from PCI ? :-/

I'll let it run for another week as it is. If it would be useful information, I can switch CONFIG_HIGHIO back to =y and let that kernel run for a while. Otherwise, I'll probably switch permanently to 2.6.

-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: 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: Chris Stromsoe <[email protected]>
  • Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
    • From: Roberto Nibali <[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: Roberto Nibali <[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: Roberto Nibali <[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: 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: Modify setterm color palette
• Next by Date: Re: Problems with eject and pktcdvd
• 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):
  • 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]