Bug#270376: PCMCIA Nic stops working after upgrading to 2.6.6/7/8
> -----Original Message-----
> From: maximilian attems [mailto:debian@sternwelten.at]
> On Wed, 30 Mar 2005, Jefferson Cowart wrote:
> > I'm downloading and testing all 3 now.
> >
> > The short version is none of the 3 worked (same problem as
> what I've already
> > seen on 2.6.6-10. Further details, dmsg, etc. below.
>
> ok bad new, but better to check. thanks for feedback.
> anyway we are getting closer inbetween of 2.6.5 and 2.6.6-rc1
> there were 2 bk snapshot. i build the bk1 for your testing pleasure,
> you'll find it at the same place:
> http://charm.itp.tuwien.ac.at/~mattems/
>
> it contains the pcmcia patches for 2.6.6, so most probably it
> will fail.
> please confirm before i hand pick different patches out of it.
It actually worked, with a few caveats.
(For reference my primary card is a 3C574. My secondary is a 3C589.)
I tried swapping to my other nic, by first ejecting the current one and then
putting the second one in. When I did that I got an error:
========
Mar 31 01:24:21 jcc02003-hawk kernel: irq 10: nobody cared!
Mar 31 01:24:21 jcc02003-hawk kernel: Call Trace:
Mar 31 01:24:21 jcc02003-hawk kernel: [__report_bad_irq+49/115]
__report_bad_ir
q+0x31/0x73
Mar 31 01:24:21 jcc02003-hawk kernel: [note_interrupt+76/111]
note_interrupt+0x
4c/0x6f
Mar 31 01:24:21 jcc02003-hawk kernel: [do_IRQ+146/249] do_IRQ+0x92/0xf9
Mar 31 01:24:21 jcc02003-hawk kernel: [common_interrupt+24/32]
common_interrupt
+0x18/0x20
Mar 31 01:24:21 jcc02003-hawk kernel: [__do_softirq+44/115]
__do_softirq+0x2c/0
x73
Mar 31 01:24:21 jcc02003-hawk kernel: [do_softirq+34/38]
do_softirq+0x22/0x26
Mar 31 01:24:21 jcc02003-hawk kernel: [do_IRQ+229/249] do_IRQ+0xe5/0xf9
Mar 31 01:24:21 jcc02003-hawk kernel: [common_interrupt+24/32]
common_interrupt
+0x18/0x20
Mar 31 01:24:21 jcc02003-hawk kernel: [default_idle+0/38]
default_idle+0x0/0x26
Mar 31 01:24:21 jcc02003-hawk kernel: [default_idle+35/38]
default_idle+0x23/0x
26
Mar 31 01:24:21 jcc02003-hawk kernel: [cpu_idle+29/50] cpu_idle+0x1d/0x32
Mar 31 01:24:21 jcc02003-hawk kernel: [start_kernel+389/393]
start_kernel+0x185
/0x189
Mar 31 01:24:21 jcc02003-hawk kernel:
Mar 31 01:24:21 jcc02003-hawk kernel: handlers:
Mar 31 01:24:21 jcc02003-hawk kernel:
[__crc_give_up_console+4053730/4336289] (y
enta_interrupt+0x0/0x27 [yenta_socket])
Mar 31 01:24:21 jcc02003-hawk kernel: Disabling IRQ #10
========
After this I pulled that card back out (running cardctl eject told me there
was no card) and put the first one back in. The LED indicating that that
socket had a card in it came up and linux found it. However at that point I
was not able to get my network back. (Rebooting fixed it)
Next I tried simply removing the original card and reinserting it without
first putting in the other card. That worked fine.
Next I tried booting with my secondary card plugged in. That didn't work.
The error I got was:
========
Mar 31 01:41:22 jcc02003-hawk kernel: eth0: 3Com 3c589, io 0x310, irq 11,
hw_addr 00:60:97:90:E6:51
Mar 31 01:41:22 jcc02003-hawk kernel: 8K FIFO split 5:3 Rx:Tx, auto xcvr
Mar 31 01:41:25 jcc02003-hawk kernel: eth0: flipped to 10baseT
Mar 31 01:41:26 jcc02003-hawk kernel: irq 10: nobody cared!
Mar 31 01:41:26 jcc02003-hawk kernel: Call Trace:
Mar 31 01:41:26 jcc02003-hawk kernel: [__report_bad_irq+49/115]
__report_bad_irq+0x31/0x73
Mar 31 01:41:26 jcc02003-hawk kernel: [note_interrupt+76/111]
note_interrupt+0x4c/0x6f
Mar 31 01:41:26 jcc02003-hawk kernel: [do_IRQ+146/249] do_IRQ+0x92/0xf9
Mar 31 01:41:26 jcc02003-hawk kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Mar 31 01:41:26 jcc02003-hawk kernel: [__do_softirq+44/115]
__do_softirq+0x2c/0x73
Mar 31 01:41:26 jcc02003-hawk kernel: [do_softirq+34/38]
do_softirq+0x22/0x26
Mar 31 01:41:26 jcc02003-hawk kernel: [do_IRQ+229/249] do_IRQ+0xe5/0xf9
Mar 31 01:41:26 jcc02003-hawk kernel: [common_interrupt+24/32]
common_interrupt+0x18/0x20
Mar 31 01:41:26 jcc02003-hawk kernel:
Mar 31 01:41:26 jcc02003-hawk kernel: handlers:
Mar 31 01:41:26 jcc02003-hawk kernel:
[__crc_give_up_console+4053730/4336289] (yenta_interrupt+0x0/0x27
[yenta_socket])
Mar 31 01:41:26 jcc02003-hawk kernel: Disabling IRQ #10
Mar 31 01:41:26 jcc02003-hawk kernel: NET: Registered protocol family 17
Mar 31 01:41:26 jcc02003-hawk kernel: eth0: interrupt(s) dropped!
========
(I put that card into a Windows XP laptop and it worked fine there so the
card itself is fine.)
Now I'm trying to see if I have these same problems on 2.5.5
First, Booting with the secondary card plugged in had the same failure as
above.
Next booting with the primary plugged in. It worked (as expected). Then I
was able to pull and re-insert the card without problems. However pulling
the primary and inserting the secondary killed the network (as expected).
Now I'm going back to 2.4.27 to figure out if my secondary card will work
there. It failed. I got a hard lock when I inserted the card. (Reboot button
needed.)
I'm 99.9% certain that my testing of 2.6.6-2.6.10 was using my primary nic,
but I'm booting 2.6.10 now to be sure. (I know the kernels I tested for you
yesterday used my primary nic.) As expected no networking.
>
> regards
> maks
>
>
It looks like we may have 2 different bugs here: one in the yenta_socket
driver starting somewhere after 2.6.5-bk1 and before 2.6.6-rc1 and one in
the 3c589 driver in I don't know what versions. (I seem to remember that
2.4.18 worked, but I'm not sure. If you want me to try that nic under and
older kernel let me know, however I think fixing the first bug is more
important.) If you need any further log info let me know.
----------------
Thanks
Jefferson Cowart
Jeff@cowart.net
Reply to: