Most recent kernel where this bug did *NOT* occur: Distribution: no idea Hardware Environment: latitude D800, D820 Software Environment: Fedora Core 6 Problem Description: Inserting the card results in: Dec 24 16:39:56 kitty6 kernel: pccard: PCMCIA card inserted into slot 0 Dec 24 16:39:56 kitty6 kernel: pcmcia: registering new device pcmcia0.0 Dec 24 16:39:56 kitty6 kernel: eth%d: pcnet_reset_8390() did not complete. Dec 24 16:39:56 kitty6 kernel: pcnet_cs: unable to read hardware net address for io base 0xd300 Dec 24 16:39:56 kitty6 kernel: eth%d: pcnet_reset_8390() did not complete. Dec 24 16:39:56 kitty6 kernel: pcnet_cs: unable to read hardware net address for io base 0xd300 Dec 24 16:39:56 kitty6 kernel: eth%d: pcnet_reset_8390() did not complete. Dec 24 16:39:56 kitty6 kernel: pcnet_cs: unable to read hardware net address for io base 0xd300 lsmod: pts/1#> lsmod Module Size Used by pcnet_cs 18224 0 8390 9984 1 pcnet_cs ipv6 264928 18 loop_blowfish 9728 0 loop_twofish 13568 1 loop_serpent 16768 0 loop 60044 5 loop_blowfish,loop_twofish,loop_serpent pcmcia 40492 1 pcnet_cs intel_agp 24092 1 yenta_socket 27788 4 rsrc_nonstatic 13312 1 yenta_socket uhci_hcd 24200 0 ehci_hcd 30856 0 agpgart 33072 1 intel_agp pcmcia_core 43540 4 pcnet_cs,pcmcia,yenta_socket,rsrc_nonstatic Steps to reproduce: re-inserting the card, fails very time.
This problem seems to be same as below problem. http://bugzilla.kernel.org/show_bug.cgi?id=7116 Please try kernel 2.6.20-rc1-mm1 or 2.6.20-rc2. Best Regards Komuro
Yes, you are right, this problem is related to http://bugzilla.kernel.org/show_bug.cgi?id=7116 but for the different card - I thought the problem was affecting my card only, have not realized that the pcnet_cs is broken. I tried 2.6.20-rc2, same results. Regards, Igor
Please post the full dmesg. What is the most recent kernel where this problem did _not_ occur. Actually, the pcnet_cs is not changed so much these days. I think this is a problem of the pcmcia_core modules or resource conflict. Best Regards Komuro
I have got the card like few weeks ago, I don't know if (and with which) earlier kernel it did work. I verified that it works in windows (on the same machine). I can try to download older versions of kernel, if that will help, any suggestions? Rgerads, Igor
Created attachment 9966 [details] dmesg
Created attachment 9967 [details] lspci
Created attachment 9968 [details] lspcmcia
>PCI: Bus #03 (-#06) is hidden behind transparent bridge #02 (-#02) (try 'pci=assign-busses') Please try to add "pci=assign-busses" to the kernel-parameter. If it still fails, please change your PC and try another PC. Best Regards Komuro
Created attachment 9969 [details] dmesg (with pci=asign-busses) Tried pci=assign-busses, the "hiding" message is gone from the dmesg, but results are the same. I have tried the card on D820 with the same results. I am trying to revive my ancient I8K, will let you know if it works there. Note that the card works under windows XP prof. on both D800 and D820 so it does not seem like a hardware problem. Regards, Igor
Created attachment 9974 [details] pcmciautils dump_cis utility Please post the output of dump_cis attached here. What io-port range does the PCMLM56 uses on WindowsXP? Best Regards Komuro
Created attachment 9975 [details] cis dump Note: The dump was made using the old libsysfs-1.3 instead of libfsys-2.0. On windows the card appears in several places: as a network adapter it has: i/o range: 0300-031f irq: 07 as a multi-function adapter it has: i/o range: 02e8-02ef i/o range: 0300-031f irq: 07
One of the difference between your Linux and WindowsXP is the ioport that PCMLM56 uses. Please add the below exclude option to your /etc/pcmcia/config.opts. exclude port 0xd000-0xefff Please post the output of "lspcmcia -vv ", too. Best Regards Komuro
Created attachment 9976 [details] dmesg (2.6.20-rc2 with pci=assign.. & exclude) It seems to work now! Except for the occasional: cs: pcmcia_socket0: unable to apply power.
Created attachment 9977 [details] pcmcia (2.6.20-rc2)
Created attachment 9978 [details] dmesg (2.6.20-rc2 with pci=assign.. & exclude) serial/modem access? Is there a way to access the modem on this combo card?
Created attachment 9979 [details] dmesg (2.6.18.1 with pci=assign.. & exclude) Except for the modem, the pci=assign-busses + exclude works also on 2.6.18.1 kernel. Thanks, Igor
>It seems to work now! Except for the occasional: O.K. Actually, "pci=assign-busses" is no relationship with this problem. >Is there a way to access the modem on this combo card? Please remove "include port 0xa00-0xaff" from the /etc/pcmcia/config.opts Best Regards Komuro
Created attachment 9980 [details] dmesg (modem) It seems one has to power down ethX on the card in order to access the modem, or the wrong module gets to handle IRQs? Both (eth & modem) work on 2.6.20-rc2, but modem does not work on 2.6.18.1 Also, it seems impossible to get more than 1.2 MB/s through the card, is this PCMCIA limitation? Thanks for the help! and happy New Year, Igor
Correction: both eth & modem work on both 2.6.18.1 & 2.6.20-rc2.
> Also, it seems impossible to get more than 1.2 MB/s through > the card, is this PCMCIA limitation? Yes, that is PCMCIA bus limitation. You need CardBus network card for 10 MB/s. > IRQ handler type mismatch for IRQ 3 >current handler: pcnet_cs > [<c014274e>] setup_irq+0x12e/0x1f0 Do you still have this message? Best Regards Komuro
OK, I was just wondering why would someone make 10/100 Mbs PCMCIA ethernet card (PCMLM56 is 10/100 Mbs card) if the PCMCIA bus limit won't let one use the card to its limits. The mismatch IRQ 3 message is present only if one drives ethernet and modem at the same time. If I turn off the ethernet part the modem works fine, no messages. Thanks, Igor
Has the problem been resolved? Thanks.
Yes, thanks! Igor.