[lkml]   [2007]   [Apr]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: NETDEV WATCHDOG and lockups
On Tue, 3 Apr 2007, Len Brown wrote:
> Which increased stability, disabling ACPI, or disabling the IOAPIC?

To be honest, we're not sure. See below.

> Your box has MPS, so you should be able to use the IOAPIC in either mode.

MPS - Multiprocessor Specification? SMP? Yes, it'd be good to use the
IOAPIC again.

> Note that you can do these both independently at boot-time with "acpi=off"
> and "noapic", respectively.
> eg. 4 combos
> 1. <default - no boot params>
> 2. noapic
> 3. acpi=off
> 4. acpi=off noapic
> you started with #1, and are running hard-coded #4 now, but skipped #2
> and #3

Indeed, we skipped quite a few options. As mentioned before, the boxes
are in production already so we don't have much time to play around and
we were just happy when they survived a few hours :(

But yes, we'll try booting with "acpi=off" and enabled IOAPIC again.

@Malte: when will we be able to do so?

Len et al., do you even suggest to use ACPI on a server system at all? I
myself always thought of ACPI being evil and to avoid when possible
(thus switching it off completely on a serversystem).

Since these NETDEV WATCHDOG issues seems to be a "known issue" (kinda,
since the many postings on the lists in the past), is there something
else we should look into? Would more debug .config options help to find
out why they lock up?

Thanks for your comments,
BOFH excuse #340:

Well fix that in the next (upgrade, update, patch release, service pack).
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2007-04-03 07:49    [W:2.072 / U:0.008 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site