| To: | stimits@xxxxxxxxx |
|---|---|
| Subject: | Re: crash on linux-2.4.21-rc6-xfs (latest cvs) |
| From: | "Jeffrey E. Hundstad" <jeffrey.hundstad@xxxxxxxx> |
| Date: | Sun, 01 Jun 2003 22:44:49 -0500 |
| Cc: | linux-xfs@xxxxxxxxxxx |
| In-reply-to: | <3EDA5EEC.50205@xxxxxxxxx> |
| References: | <3512.1054466831@xxxxxxxxxxxxxxxxxxxxx> <3EDA4E3E.6040800@xxxxxxxxxxxx> <3EDA5EEC.50205@xxxxxxxxx> |
| Sender: | linux-xfs-bounce@xxxxxxxxxxx |
| User-agent: | Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4) Gecko/20030529 |
I may try this.... but keep in mind it worked for years before the
2.4.21-rcX kernels came out it was on 2.4.18 for a year.
D. Stimits wrote: Jeffrey E. Hundstad wrote:1. Are you running SMP or UP? SMP 2 if UP does your motherboard have an IO APIC? -NA-3. What sort of error are you seeing, is it a straight hang, does the NMIwatchdog kick in, are you running the NMI watchdog? Huh? I've not seen NMI or watchdog in the kernel messages. 4. Or do you get an oops? I'm getting oopses. Several have been posted. BTW: I don't actually have KDB compiled into the kernel at the moment. I'll do that too ;-)Try adding kernel parameter "noapic" to the boot. There are a few chipsets that do this due to wrong or inadequate IO-APIC, especially under heavy IO loads. If the problem goes away, chances are it is the chipset support.D. Stimits, stimits AT attbi DOT com |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: crash on linux-2.4.21-rc6-xfs (latest cvs), D. Stimits |
|---|---|
| Next by Date: | [Bug 248] xfs_check: Segmentation fault, bugzilla-daemon |
| Previous by Thread: | Re: crash on linux-2.4.21-rc6-xfs (latest cvs), D. Stimits |
| Next by Thread: | xfs performance tuning, Wendy Cheng |
| Indexes: | [Date] [Thread] [Top] [All Lists] |