From: Roberto Nibali <ratz@drugphish.ch>
To: Chris Stromsoe <cbs@cts.ucla.edu>
Cc: Willy Tarreau <willy@w.ods.org>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Marcelo Tosatti <marcelo.tosatti@cyclades.com>,
linux-kernel@vger.kernel.org
Subject: Re: bad pmd filemap.c, oops; 2.4.30 and 2.4.32
Date: Mon, 09 Jan 2006 21:16:02 +0100 [thread overview]
Message-ID: <43C2C482.6090904@drugphish.ch> (raw)
In-Reply-To: <Pine.LNX.4.64.0601070246150.29898@potato.cts.ucla.edu>
>> CONFIG_DEBUG_KERNEL=y
>> CONFIG_DEBUG_SLAB=y
>> CONFIG_MAGIC_SYSRQ=y
>> CONFIG_FRAME_POINTER=y
>
> kernel, sysrq, and frame_pointer were already enabled. I'll enable
> debug_slab, as well.
Excellent.
>>> booting with "nosmp acpi=off" did not help. The box hung as before, at
>>
>> Could you boot with pci=noacpi and report again? The difference is
>> that ACPI will still be used but not for IRQ routing. I have a few
>> boxes out with 2.4.x kernels and Adaptec HBAs that need this to work
>> reliably.
>
> Are you interested in results from "pci=noacpi" by itself or in
> conjunction with nosmp?
With SMP, please.
>> What's the SCSI BIOS version?
>
> The SCSI controller is an onboard AIC 7899 (in a Dell PowerEdge 2650),
> and reports itself as "25309".
What I meant was the SCSI Bios revision you get to see when you cold
reset the system.
>> If you find time, send me your BIOS settings and your .config in
>> private email. I didn't track this thread from the beginning, so I
>> don't know if you've already done this.
>
> <http://hashbrown.cts.ucla.edu/pub/oops-200512/> has the .config, lspci
> -v, and /proc/interrupts for 2.6.14.4 and 2.4.32.
Thanks, I'll skim over these and get back to you if I can correlate
anything with the issues we were having using this controller.
Regards,
Roberto Nibali, ratz
--
echo
'[q]sa[ln0=aln256%Pln256/snlbx]sb3135071790101768542287578439snlbxq' | dc
next prev parent reply other threads:[~2006-01-09 20:16 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-27 16:58 bad pmd filemap.c, oops; 2.4.30 and 2.4.32 Chris Stromsoe
2005-12-28 0:10 ` Marcelo Tosatti
2005-12-29 2:52 ` Chris Stromsoe
2005-12-29 5:12 ` Willy Tarreau
2005-12-29 9:33 ` Chris Stromsoe
2005-12-29 10:08 ` Willy Tarreau
2005-12-29 12:01 ` Chris Stromsoe
2005-12-31 0:12 ` Chris Stromsoe
2005-12-31 1:48 ` Chris Stromsoe
2005-12-31 4:00 ` Chris Stromsoe
2005-12-31 7:25 ` Willy Tarreau
2005-12-31 11:06 ` Chris Stromsoe
2005-12-31 7:12 ` Willy Tarreau
2005-12-31 10:39 ` Chris Stromsoe
2005-12-31 10:56 ` Willy Tarreau
2005-12-31 12:08 ` Alan Cox
2005-12-31 13:01 ` Willy Tarreau
2006-01-05 3:52 ` Chris Stromsoe
2006-01-05 5:43 ` Willy Tarreau
2006-01-06 21:54 ` Chris Stromsoe
2006-01-06 22:14 ` Chris Stromsoe
2006-01-06 22:16 ` Chris Stromsoe
2006-01-07 9:19 ` Roberto Nibali
2006-01-09 18:28 ` Chris Stromsoe
2006-01-09 20:16 ` Roberto Nibali [this message]
2006-01-09 20:22 ` Chris Stromsoe
2006-01-09 22:22 ` Roberto Nibali
2006-01-10 0:59 ` Chris Stromsoe
2006-01-15 11:29 ` Chris Stromsoe
2006-01-15 12:12 ` Willy Tarreau
2006-01-15 21:18 ` Chris Stromsoe
2006-01-15 22:38 ` Chris Stromsoe
2006-01-15 22:46 ` Willy TARREAU
2006-01-15 22:54 ` Chris Stromsoe
2006-01-16 20:52 ` Roberto Nibali
2006-01-16 21:32 ` Chris Stromsoe
2006-02-08 6:32 ` Chris Stromsoe
2006-02-08 6:37 ` Willy Tarreau
2006-01-08 9:45 ` Willy Tarreau
2006-01-09 18:33 ` Chris Stromsoe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=43C2C482.6090904@drugphish.ch \
--to=ratz@drugphish.ch \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=cbs@cts.ucla.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo.tosatti@cyclades.com \
--cc=willy@w.ods.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.