FS#14817 - [kernel26] pccardd crash when pluggin in PCMCIA network Card

Attached to Project: Arch Linux
Opened by Benni (Prozent20) - Sunday, 24 May 2009, 23:40 GMT
Last edited by Roman Kyrylych (Romashka) - Monday, 27 July 2009, 08:48 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Thomas Bächler (brain0)
Architecture i686
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

When plugging in my PCMCIA network card into the PCMCIA slot of my Laptop (Toshiba Portégé 7200) I get an error of my pccardd beeing tainted followed by a stack trace and my PCMCIA card remains unrecognized (it is not shwon by lspci).
The type of the PCMCIA network card is TP-Link TF-5239 (I think it has an Realtek chipset). I tested it with an laptop running windows xp, and it runs fine, so it should not be the failure of the card. Also using a 3-com pcmcia network card the described problem the problem did not occur.
Updating all core packaes didn't help either.
It also has no effect if the realtek driver modules (8139too und 8139cp) are loaded into the kernel or not.
To reproduce to problem you simply have to plug the card in when the system is booted.
Also pluggin it in before booting doesn't help, but leads to a hang at boot with the same error begin displayed.

Attached is my output of the dmesg command. At the end of it, you can see the errors produced when I plug in the card.
   dmesg.txt (24.8 KiB)
This task depends upon

Closed by  Roman Kyrylych (Romashka)
Monday, 27 July 2009, 08:48 GMT
Reason for closing:  Upstream
Comment by Roman Kyrylych (Romashka) - Sunday, 31 May 2009, 11:49 GMT
looks like upstream issue, so I suggest searching/reporting the issue on bugzilla.kernel.org
Comment by Nicola (drakkan) - Sunday, 12 July 2009, 18:37 GMT
same issue here ...
Comment by Gerardo Exequiel Pozzi (djgera) - Sunday, 26 July 2009, 21:04 GMT
As Roman said some time ago, please report this to the bugzilla or send a mail to LKML with a cc to the maintainer of the driver. This is the best way to solve this type of bugs. We can do much nothing here ;)

Loading...