I've got almost exactly the same problem, and haven't yet figured out what combination of options and such can fix it yet. I've tried a few combinations (and tried versions 3.0.12, 3.0.14, 3.1.8 and 3.1.14 of pcmcia-cs). Here are what I think are the relevant files... If I've missed anything, just ask for it. -=-=-=-=-=- /etc/pcmcia/config.opts: # # Local PCMCIA Configuration File # # System resources available for PCMCIA devices # include port 0x100-0x4ff, port 0x1000-0x17ff include memory 0xc0000-0xfffff include memory 0xa0000000-0xa0ffffff, memory 0x60000000-0x60ffffff # Extra port range for IBM Token Ring include port 0xa00-0xaff # # Resources we should not use, even if they appear to be available # First built-in serial port exclude irq 4 # Second built-in serial port exclude irq 3 # First built-in parallel port exclude irq 7 # built-in sound exclude irq 5 -=-=-=-=-=- Should I remove the line for the Token Ring? I don't use it, but could it be interfering with something somehow? -=-=-=-=-=- /etc/sysconfig/pcmcia: PCMCIA=yes PCIC=i82365 PCIC_OPTS="pci_int=1 pci_csc=1" CORE_OPTS= -=-=-=-=-=- Commands used to start up pcmcia, and then test to see if the problem manifests: root@gopher(tty1):~ 65 # /etc/rc.d/init.d/pcmcia start Starting PCMCIA services: modules cardmgr. root@gopher(tty1):~ 66 # ping -f tigger PING tigger (172.19.1.22) from 172.19.1.28 : 56(84) bytes of data. ................................................................................ ................................................................................ ................................................................................ ................................................................................ .......................... --- tigger ping statistics --- 16715 packets transmitted, 16369 packets received, 2% packet loss round-trip min/avg/max = 0.1/0.3/6.9 ms root@gopher(tty1):~ 67 # (The display showed only three dots for almost 45 seconds, then the dots just started streaming across the screen. That is usually good evidence that the problem manifested, and then I got two kernel messages from eth0, at the end of /var/log/messages) -=-=-=-=-=- /var/log/messages: Apr 20 21:58:08 gopher kernel: Linux PCMCIA Card Services 3.1.14 Apr 20 21:58:08 gopher kernel: kernel build: 2.2.14 #7 Sun Mar 5 17:04:18 PST 2000 Apr 20 21:58:08 gopher kernel: options: [pci] [cardbus] [apm] [pnp] Apr 20 21:58:08 gopher kernel: PCI routing table version 1.0 at 0xfdf80 Apr 20 21:58:08 gopher kernel: PnP: PNP BIOS installation structure at 0xc00f6780 Apr 20 21:58:08 gopher kernel: PnP: PNP BIOS version 1.0, entry at f0000:b31a, dseg at 400 Apr 20 21:58:08 gopher kernel: Intel PCIC probe: Apr 20 21:58:08 gopher kernel: TI 1220 rev 02 PCI-to-CardBus at slot 00:04, mem 0x68000000 Apr 20 21:58:08 gopher kernel: host opts [0]: [ring] [serial pci & irq] [pci irq 10] [lat 64/176] [bus 32/34] Apr 20 21:58:08 gopher kernel: host opts [1]: [ring] [serial pci & irq] [pci irq 10] [lat 64/176] [bus 35/37] Apr 20 21:58:08 gopher kernel: ISA irqs (scanned) = 3,4,7,9 PCI status changes Apr 20 21:58:08 gopher cardmgr[1629]: starting, version is 3.1.14 Apr 20 21:58:08 gopher cardmgr[1629]: watching 2 sockets Apr 20 21:58:08 gopher kernel: cs: IO port probe 0x1000-0x17ff: clean. Apr 20 21:58:08 gopher kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x378-0x37f Apr 20 21:58:08 gopher kernel: cs: IO port probe 0x0a00-0x0aff: clean. Apr 20 21:58:08 gopher kernel: cs: cb_alloc(bus 35): vendor 0x10b7, device 0x5157 Apr 20 21:58:08 gopher cardmgr[1629]: initializing socket 0 Apr 20 21:58:08 gopher kernel: cs: memory probe 0xa0000000-0xa0ffffff: clean. Apr 20 21:58:08 gopher cardmgr[1629]: socket 0: Serial or Modem Apr 20 21:58:08 gopher cardmgr[1629]: executing: 'insmod /lib/modules/2.2.14/pcmcia/serial_cs.o' Apr 20 21:58:08 gopher kernel: tty03 at 0x02e8 (irq = 9) is a 16550A Apr 20 21:58:08 gopher cardmgr[1629]: executing: './serial start ttyS3' Apr 20 21:58:09 gopher cardmgr[1629]: initializing socket 1 Apr 20 21:58:09 gopher cardmgr[1629]: socket 1: 3Com 3CCFE575B/3CXFE575B Fast EtherLink XL Apr 20 21:58:09 gopher cardmgr[1629]: executing: 'insmod /lib/modules/2.2.14/pcmcia/cb_enabler.o' Apr 20 21:58:09 gopher cardmgr[1629]: executing: 'insmod /lib/modules/2.2.14/pcmcia/3c575_cb.o' Apr 20 21:58:09 gopher kernel: 3c59x.c:v0.99L 5/28/99 Donald Becker http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html Apr 20 21:58:09 gopher kernel: cs: cb_config(bus 35) Apr 20 21:58:09 gopher kernel: fn 0 bar 1: io 0xa00-0xa7f Apr 20 21:58:09 gopher kernel: fn 0 bar 2: mem 0xa0061000-0xa006107f Apr 20 21:58:09 gopher kernel: fn 0 bar 3: mem 0xa0060000-0xa006007f Apr 20 21:58:09 gopher kernel: fn 0 rom: mem 0xa0040000-0xa005ffff Apr 20 21:58:09 gopher kernel: vortex_attach(bus 35, function 0, device 5157) Apr 20 21:58:09 gopher kernel: eth0: 3Com 3CCFE575 Cyclone CardBus at 0xa00, 00:50:04:29:45:34, IRQ 10 Apr 20 21:58:09 gopher kernel: eth0: CardBus functions mapped a0060000->cc072000 Apr 20 21:58:09 gopher kernel: 8K byte-wide RAM 5:3 Rx:Tx split, MII interface. Apr 20 21:58:09 gopher kernel: MII transceiver found at address 0, status 7809. Apr 20 21:58:09 gopher kernel: Enabling bus-master transmits and whole-frame receives. Apr 20 21:58:09 gopher cardmgr[1629]: executing: './network start eth0' Apr 20 21:58:09 gopher pumpd[1678]: starting at Thu Apr 20 21:58:09 2000 Apr 20 21:58:12 gopher pumpd[1678]: configured interface eth0 Apr 20 21:58:12 gopher cardmgr[1629]: + Determining IP information for eth0... done. Apr 20 21:58:33 gopher kernel: eth0: transmit timed out, tx_status 00 status e681. Apr 20 21:58:33 gopher kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? Apr 20 21:58:43 gopher kernel: eth0: transmit timed out, tx_status 00 status e601. Apr 20 21:58:43 gopher kernel: eth0: Interrupt posted but not delivered -- IRQ blocked by another device? -=-=-=-=-=- One point of interest, usually, when this happens, the status code on the first of the two messages is different for each occurance, if this is important. I downloaded and built mii-diag, but it reports everything is a-ok, autonegotiated at 100base-Tx. It even reports this when the card isn't responding. I'm confused, and hoping I don't have to buy a different ethernet device. Any help would be much appreciated. |
Messages