linux-alpha.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "alpha @ steudten Engineering" <alpha@steudten.com>
To: LinuxAlpha <linux-alpha@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	becker@scyld.com
Subject: Kernel panic on alpha cpu 2.6.13-2.6.15 not in 2.6.10
Date: Fri, 20 Jan 2006 13:58:43 +0100	[thread overview]
Message-ID: <43D0DE83.6000009@steudten.org> (raw)

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


                 reply	other threads:[~2006-01-20 12:58 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=43D0DE83.6000009@steudten.org \
    --to=alpha@steudten.com \
    --cc=becker@scyld.com \
    --cc=linux-alpha@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).