2003-08-02 21:09:46

by Hmamouche, Youssef

[permalink] [raw]
Subject: [PROBLEM] xircom CBE2-100(faulty) hangs kernel 2.4.{21, 22-pre8}


Hi,

I have a xircom CBE2-100 ethernet card that I know(as a matter of fact) is
faulty. The warranty on the card expired and couldn't take it back to
the manufacturer. Anyway, I hotplugged it into the sock with no problem at
all. However, when I try to bring up the interface, the kernel hangs. If I
unplug the card, the kernel comes back to life and resumes.

I broke to kdb(attached as kdb.txt) and noticed that the kernel was alive
but overwhelmed by the unacked interrupts(11) from the card. Here's what
it looks like on the /proc interface:

root@darkstar:/home/labo# cat /proc/interrupts; ifconfig eth1 up; cat
/proc/interrupts

CPU0
0: 93211 XT-PIC timer
1: 3905 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC Maestro3(i)
9: 7212 XT-PIC orinoco_cs
11: 142006 XT-PIC Texas Instruments PCI1225, Texas
Instruments PCI1225 (#2), usb-uhci
12: 3426 XT-PIC PS/2 Mouse
14: 3016 XT-PIC ide0
15: 5 XT-PIC ide1
NMI: 0
ERR: 0

CPU0
0: 93692 XT-PIC timer
1: 3906 XT-PIC keyboard
2: 0 XT-PIC cascade
5: 0 XT-PIC Maestro3(i)
9: 7213 XT-PIC orinoco_cs
11: 203826 XT-PIC Texas Instruments PCI1225, Texas
Instruments PCI1225 (#2), usb-uhci, eth1
12: 3426 XT-PIC PS/2 Mouse
14: 3016 XT-PIC ide0
15: 5 XT-PIC ide1
NMI: 0
ERR: 0


The symptoms of the problem show at
drivers/net/pcmcia/xircom_tulip_cb: xircom_interrupt() where the interrupt
is never acknowledge(due to flawed hardware).

I have attached the kernel logs(as dmesg.txt) pertaining to this
operation along with lspci, ver_linux, etc(hw.txt) .

Shouldn't the driver graciously filter/diagnose this anomaly before it
gets out of hands?

thank you for your time,

Youssef Hmamouche



Attachments:
kdb.txt (1.94 kB)
dmesg.txt (1.04 kB)
hw.txt (7.71 kB)
Download all attachments