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 02:38:51PM -0800, Chris Stromsoe wrote:

On Sun, 15 Jan 2006, Chris Stromsoe wrote:

On Mon, 9 Jan 2006, Chris Stromsoe wrote:

On Mon, 9 Jan 2006, Roberto Nibali wrote:

That is the SCSI BIOS rev. The machine is a Dell PowerEdge 2650 and that's the onboard AIC 7899. It comes up as "BIOS Build 25309".

Brain is engaged now, thanks ;). If you find time, could you maybe compile a 2.4.32 kernel using following config (slightly changed from yours):

http://www.drugphish.ch/patches/ratz/kernel/configs/config-2.4.32-chris_s

If/when the current run with DEBUG_SLAB oopses, I'll reboot with the config modifications.

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:

I made a mistake.

The machine was /not/ booted into that config. It is running the original config from http://hashbrown.cts.ucla.edu/pub/oops-200512/config-2.4.32 with DEBUG_SLAB defined and "pci=noacpi" passed in on the command line.

The config with HIGHIO disabled an ACPI=y has not been tested.

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.

-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/

---

• Follow-Ups:
  • 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]>

• 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: 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: 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: [linux-usb-devel] Re: 2.6.15-mm3 [USB lost interrupt bug]
• 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]