Re: Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS
Hi, This can be (and probably is) totally unrelated, but e.g. in Fedora 10 somewhere in their 2.6.27.xx kernel series updates, my USB 3G modem stopped to work if it was plugged to USB port at the boot time. After booting, doing unplug-replug it started to work normally. I just wonder if there is something wrong in the kernel hotplug system or something. Yes. Actually, if I connect the USB CDROM and boot linux, the USB CDROM is not detected and I need to replug it. So I think at least USB device support of udev has the bug. Best Regards Komuro ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: Re: Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS
This can be (and probably is) totally unrelated, but e.g. in Fedora 10 somewhere in their 2.6.27.xx kernel series updates, my USB 3G modem stopped to work if it was plugged to USB port at the boot time. After booting, doing unplug-replug it started to work normally. I just wonder if there is something wrong in the kernel hotplug system or something. sorry, I tried the Fedore11 + kernel-2.6.32 again. My USB CDROM is detected properly. ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS
Hi, what's the difference between lspcmcia -vvv when the problem exists, and when the problem does not appear? Can you read out the CIS via sysfs even when the problem exists, and is it the same as when the problem does not appear? The lspcmcia -vvv is same between the problem appear and problem does not appear. Actually, this problem appear when I connect the 3com card and boot linux. Even if the problem appear , after replugging the card, it works well. I can read the CIS from /sys/class/pcmcia_socket/pcmcia_socket0/cis. Socket 0 Bridge:[yenta_cardbus] (bus ID: :04:06.0) Configuration: state: on ready: yes Voltage: 5.0V Vcc: 5.0V Vpp: 0.0V Available IRQs: 3, 5, 7, 10, 11 Available ioports: 0x0100 - 0x03af 0x03e0 - 0x04cf 0x04d8 - 0x04ff 0x0820 - 0x08ff 0x0a00 - 0x0aff 0x0c00 - 0x0cf7 0x1000 - 0x1fff Available iomem:0x000c - 0x000f 0xd200 - 0xd2e6 0xd308 - 0xd3ee Socket 0 Device 0: [3c589_cs] (bus ID: 0.0) Configuration: state: on Product Name: 3Com Corporation 3C562D/3C563D EtherLink III LAN+Modem PC Car d Identification: manf_id: 0x0101 card_id: 0x0562 function: 6 (network) prod_id(1): 3Com Corporation (0xe1c0d2aa) prod_id(2): 3C562D/3C563D (0xaa0fba64) prod_id(3): EtherLink III (0xc9a029c2) prod_id(4): LAN+Modem PC Card (0x32d830f4) Socket 0 Device 1: [serial_cs] (bus ID: 0.1) Configuration: state: on Product Name: 3Com Corporation 3C562D/3C563D EtherLink III LAN+Modem PC Car d Identification: manf_id: 0x0101 card_id: 0x0562 function: 6 (network) prod_id(1): 3Com Corporation (0xe1c0d2aa) prod_id(2): 3C562D/3C563D (0xaa0fba64) prod_id(3): EtherLink III (0xc9a029c2) prod_id(4): LAN+Modem PC Card (0x32d830f4) ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS
Hey, Good to know it's reproducible... Does issuing # pccardctl eject # pccardctl insert without actually ejecting and inserting the card fix the issue you're seeing? Best, Dominik ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
Re: [ANOTHER BUG? kernel 2.6.32] 3com 3c562 card can't access CIS
Komuro, what's the difference between lspcmcia -vvv when the problem exists, and when the problem does not appear? Can you read out the CIS via sysfs even when the problem exists, and is it the same as when the problem does not appear? Best, Dominik On Wed, Dec 23, 2009 at 06:20:24PM +0900, Komuro wrote: Hi, The problem below is CIS problem and no relation with kernel/resource.c. This problem is introduced at kernel 2.6.32 or earlier. but if I connect the 3Com 3c562 and boot the linux, the mac address of 3c562 sometimes becomes ff:ff:ff:ff:ff:ff. the mac address becomes normal after replugging it. pcmcia 0.0: pcmcia: registering new device pcmcia0.0 pcmcia 0.1: pcmcia: registering new device pcmcia0.1 0.1: ttyS0 at I/O 0x3f8 (irq = 3) is a 16550A 3c589_cs 0.0: pcmcia: could not parse base and rmask0 of CIS eth0: 3Com 3c562, io 0x300, irq 3, hw_addr ff:ff:ff:ff:ff:ff 32K FIFO split 3:5 Rx:Tx, auto xcvr ___ Linux PCMCIA reimplementation list http://lists.infradead.org/mailman/listinfo/linux-pcmcia
