Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750933AbWATM7M (ORCPT ); Fri, 20 Jan 2006 07:59:12 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750925AbWATM7M (ORCPT ); Fri, 20 Jan 2006 07:59:12 -0500 Received: from 84-72-6-10.dclient.hispeed.ch ([84.72.6.10]:12437 "EHLO steudten.com") by vger.kernel.org with ESMTP id S1750909AbWATM7L (ORCPT ); Fri, 20 Jan 2006 07:59:11 -0500 Message-ID: <43D0DE83.6000009@steudten.org> Date: Fri, 20 Jan 2006 13:58:43 +0100 From: "alpha @ steudten Engineering" Organization: Steudten Engineering MIME-Version: 1.0 To: LinuxAlpha , LKML , becker@scyld.com Subject: Kernel panic on alpha cpu 2.6.13-2.6.15 not in 2.6.10 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Mailer: Mailer X-Check: 67896610c56208aa744771aa67179e7c on steudten.com Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2564 Lines: 62 Was: "Kernel crash on alpha cpu 2.6.13-2.6.15" Part 2: The system has crashed again today with "kernel panic - not syncing: Aiee, killing interrupt handler!" After 3 days uptime! Is there any way with do_exit() to find out, which interrupt or kernel code this is? Is it possible to print out a kernel stack trace in do_exit()? The Magic Keys don't work in the normal way for the alpha. Original Mail: Hello Summary: alpha cpu 64 Bit kernel-2.6.10: ok kernel-2.6.13-2.6.15: problem eth0: 3Com Corporation 3C905B Fast Etherlink XL 10/100 Kernel crash, reboot problem due to kernel-log-buffer flooted with message. No problem on x86 with same network card. Kernel not stable on alpha cpu! With hardreset (power-off) everything is ok, until the next time. Detail: kernel-2.6.15: Kernel crashs after 5-15days, no message is logged in syslog (klogd -2 -p -c 3). Autoreboot after crash is active and when the kernel boots again, the syslog is flooted with the messages: kernel: eth0: Host error, FIFO diagnostic register 0000. kernel: eth0: PCI bus error, bus status 40000020 kernel: eth0: Host error, FIFO diagnostic register 0000. kernel: eth0: PCI bus error, bus status 40000020 kernel: eth0: Host error, FIFO diagnostic register 0000. kernel: eth0: PCI bus error, bus status 40000020 kernel: eth0: Host error, FIFO diagnostic register 0000. kernel: eth0: PCI bus error, bus status 40000020 kernel: eth0: Host error, FIFO diagnostic register 0000. [..] About 20 lines per second! -> BTW: Why this is not catched from klogd/syslogd to one entry per second? The text is in "drivers/net/3c59x.c line 2149 (2.6.15): 3c59x.c:2149: printk(KERN_ERR "%s: Host error, FIFO diagnostic register %4.4x.\n", A diff between 2.6.10 and 2.6.15 3c59x.c shows a lot of lines changed, and the i/o calls like "inw" changed to "ioread16" aso - maybe this is a probem. 00:09.0 Ethernet controller: 3Com Corporation 3c905B 100BaseTX [Cyclone] (rev 30) Subsystem: 3Com Corporation 3C905B Fast Etherlink XL 10/100 Flags: bus master, medium devsel, latency 32, IRQ 24 I/O ports at 8c00 [size=128] Memory at 000000000a064000 (32-bit, non-prefetchable) [size=128] Expansion ROM at 000000000a020000 [disabled] [size=128K] Capabilities: [dc] Power Management version 1 Regards Thomas - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/