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

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:

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

65c65
< CONFIG_HIGHIO=y
---

# CONFIG_HIGHIO is not set

69c69
< CONFIG_NR_CPUS=32
---

CONFIG_NR_CPUS=4

87c87
< CONFIG_ISA=y
---

# CONFIG_ISA is not set

109c109
< # CONFIG_ACPI is not set
---

CONFIG_ACPI=y

110a111,127

CONFIG_ACPI_BUS=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_MMCONFIG=y
CONFIG_ACPI_SLEEP=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_ACPI_AC is not set
# CONFIG_ACPI_BATTERY is not set
# CONFIG_ACPI_BUTTON is not set
# CONFIG_ACPI_FAN is not set
# CONFIG_ACPI_PROCESSOR is not set
# CONFIG_ACPI_THERMAL is not set
# CONFIG_ACPI_ASUS is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_DEBUG is not set

385c402
< # CONFIG_AIC7XXX_DEBUG_ENABLE is not set
---

CONFIG_AIC7XXX_DEBUG_ENABLE=y

387c404
< # CONFIG_AIC7XXX_REG_PRETTY_PRINT is not set
---

CONFIG_AIC7XXX_REG_PRETTY_PRINT=y

492,493d508
< # CONFIG_AT1700 is not set
< # CONFIG_DEPCA is not set
500d514
< # CONFIG_AC3200 is not set
585,589d598
< # Old CD-ROM drivers (not SCSI, not IDE)
< #
< # CONFIG_CD_NO_IDESCSI is not set
<
< #
864,865c873,874
< # CONFIG_DEBUG_HIGHMEM is not set
< # CONFIG_DEBUG_SLAB is not set
---

CONFIG_DEBUG_HIGHMEM=y
CONFIG_DEBUG_SLAB=y

-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: Willy Tarreau <[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: 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]>

• Prev by Date: Re: wireless: recap of current issues (other issues)
• Next by Date: [STABLE] Fix oops in ufs_fill_super at mount time
• 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]