linux-kernel - Re: 2.6.20.4: NETDEV WATCHDOG and lockups

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <Pine.LNX.4.64.0704031424570.3963@sheep.housecafe.de>
Date:	Tue, 3 Apr 2007 16:17:55 +0100 (BST)
From:	Christian Kujau <christian@...ouse.de>
To:	Chuck Ebbert <cebbert@...hat.com>
cc:	linux-kernel@...r.kernel.org, netdev@...r.kernel.org
Subject: Re: 2.6.20.4: NETDEV WATCHDOG and lockups

On Mon, 2 Apr 2007, Chuck Ebbert wrote:
> Where is the info from before you changed to "noapic"? Or were the
> machines always using XT-PIC for all the interrupts???

We booted with 'acpi=off lapic' (with ACPI options compiled in, to be 
able to boot with acpi=on later on) and the box locked up again.

I'll try to boot with a slightly different .config later on. With 
'lapic' /proc/interrupts looks like:

           CPU0       CPU1
   0:      63656      63396   IO-APIC-edge      timer
   1:          0          8   IO-APIC-edge      i8042
   2:          0          0    XT-PIC-XT        cascade
   4:          6          1   IO-APIC-edge      serial
   6:          0          3   IO-APIC-edge      floppy
   8:          0          1   IO-APIC-edge      rtc
  17:      17050          1   IO-APIC-fasteoi   eth1
  18:        102      80615   IO-APIC-fasteoi   eth0
  20:     195817      77721   IO-APIC-fasteoi   libata
NMI:          0          0
LOC:     126969     126970
ERR:          0
MIS:          0

Christian.

-- 
BOFH excuse #146:

Communications satellite used by the military for star wars.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/