Question: Cardbus Tulip card works unreliably (system crash) 

Forum: PCMCIA Network Adapter Issues
Date: 2000, Feb 03
From: <rolf.fiedler@ferrari.de>

I hvae a cardbus tulip based 10/100 eth card, and it is detected by the pcmcia core and the proper drivers are loaded. The system is a palmax pd1000 running 2.2.14 with pcmcia 3.1.9. once the card is inserted, it is detected and ifconfig and route is done. I can ping the network (reliably). I can do telnet and everything that does not transfer a lot of data. However, if I try to transfer data (like a ftp download) the whole system freezes and I have to turn it off. I don't know how to debug the problem, since the system crashes. An ne2000 compatible ethernet card works like a charm, however it is a friend's card :-(. On the cardbus card it says "Gericom Cardbus 10/100 Fast Ethernet" I have tried to play around with the resource info in the pcmcia config., however without success (same behaviour). I have tried a 2.3.3? kernel, same result. Any hints?

[ Next-in-Thread ]  [ Next Message ] 

Messages Inline: [ 0 ]  [ 1 ] 

System log messages? Re: Question: Cardbus Tulip card works unreliably (system crash) Date: 2000, Feb 03 From: David Hinds <dhinds@pcmcia.sourceforge.org>

It is often useful to include system log messages with bug reports. The PCMCIA-HOWTO has some instructions for debugging system crashes, which may yield some additional information. -- Dave

Feedback: sys log messages Re: System log messages? (David Hinds) Date: 2000, Feb 04 From: <rolf.fiedler@ferrari.de>

you asked for it... here it comes: ... while booting .... Feb 1 22:07:59 mini kernel: EXT2-fs warning: mounting unchecked fs, running e2fsck is recommended Feb 1 22:07:59 mini kernel: Linux PCMCIA Card Services 3.1.9 Feb 1 22:07:59 mini kernel: kernel build: 2.2.14 #20 Die Feb 1 19:33:28 CET 2000 Feb 1 22:07:59 mini kernel: options: [pci] [cardbus] [apm] Feb 1 22:07:59 mini kernel: PCI routing table version 1.0 at 0xfdf30 Feb 1 22:07:59 mini kernel: unknown PCI interrupt router 1078:0002 Feb 1 22:07:59 mini kernel: Intel PCIC probe: Feb 1 22:07:59 mini kernel: TI 1220 PCI-to-CardBus at slot 00:0b, mem 0x68000000 Feb 1 22:07:59 mini kernel: host opts [0]: [isa irq] [no pci irq] [lat 64/176] [bus 32/34] Feb 1 22:07:59 mini kernel: host opts [1]: [isa irq] [no pci irq] [lat 64/176] [bus 35/37] Feb 1 22:07:59 mini kernel: ISA irqs (scanned) = 3,4,10 polling interval = 1000 ms Feb 1 22:07:59 mini kernel: cs: IO port probe 0x0c00-0x0cff: excluding 0xcf8-0xcff Feb 1 22:07:59 mini kernel: cs: IO port probe 0x0800-0x08ff: clean. Feb 1 22:07:59 mini kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x398-0x39f 0x480-0x48f 0x4d0-0$ Feb 1 22:07:59 mini kernel: cs: IO port probe 0x0a00-0x0aff: excluding 0xaf8-0xaff Feb 1 22:08:00 mini crond: crond startup succeeded Feb 1 22:08:01 mini inet: inetd startup succeeded Feb 1 22:08:02 mini xntpd: xntpd startup succeeded ... -> card insertion Feb 1 22:10:53 mini cardmgr[204]: initializing socket 0 Feb 1 22:10:53 mini cardmgr[204]: socket 0: Linksys EtherFast 10/100 Feb 1 22:10:53 mini kernel: cs: cb_alloc(bus 32): vendor 0x1011, device 0x0019$ Feb 1 22:10:53 mini cardmgr[204]: executing: 'insmod /lib/modules/2.2.14/pcmcia /cb_enabler.o' Feb 1 22:10:53 mini cardmgr[204]: + /lib/modules/2.2.14/pcmcia/cb_enabler.o: a$ module named cb_enabler already exists Feb 1 22:10:53 mini cardmgr[204]: insmod exited with status 1 Feb 1 22:10:53 mini cardmgr[204]: executing: 'modprobe cb_enabler' Feb 1 22:10:53 mini kernel: cs: cb_config(bus 32) Feb 1 22:10:53 mini kernel: fn 0 bar 1: io 0x100-0x17f Feb 1 22:10:53 mini kernel: fn 0 bar 2: mem 0x600c0000-0x600c03ff Feb 1 22:10:53 mini kernel: fn 0 rom: mem 0x60080000-0x600bffff Feb 1 22:10:53 mini kernel: tulip_attach(bus 32, function 0) Feb 1 22:10:53 mini kernel: tulip.c:v0.91g-ppc 7/16/99 becker@cesdis.gsfc.nasa.gov Feb 1 22:10:53 mini kernel: eth0: Digital DS21143 Tulip rev 65 at 0x100, 00:E0:98:71:CD:61, IRQ 3. Feb 1 22:10:53 mini kernel: eth0: EEPROM default media type Autosense. Feb 1 22:10:53 mini kernel: eth0: Index #0 - Media MII (#11) described by a 21142 MII PHY (3) block. Feb 1 22:10:53 mini kernel: eth0: MII transceiver #0 config 3000 status 7809 advertising 01e1. Feb 1 22:10:54 mini cardmgr[204]: executing: './network start eth0' Feb 1 22:12:19 mini xntpd[345]: synchronized to LOCAL(0), stratum=10 Feb 1 22:12:19 mini xntpd[345]: kernel pll status change 89 -> crash happened here -> next boot Feb 2 08:33:11 mini syslogd 1.3-3: restart. Feb 2 08:33:11 mini syslog: syslogd startup succeeded Feb 2 08:33:11 mini syslog: klogd startup succeeded Feb 2 08:33:11 mini kernel: klogd 1.3-3, log source = /proc/kmsg started. Feb 2 08:33:11 mini kernel: Inspecting /boot/System.map-2.2.14 Feb 2 08:33:12 mini kernel: Loaded 5942 symbols from /boot/System.map-2.2.14. Feb 2 08:33:12 mini kernel: Symbols match kernel version 2.2.14. Feb 2 08:33:12 mini kernel: Loaded 61 symbols from 7 modules. Feb 2 08:33:12 mini kernel: Linux version 2.2.14 (rfie@server.private.net) (gcc version egcs-2.91.66 19990314/Linux (egcs-1.1.2 release)) #20 Die Feb 1 19:33:28 CET 2000 Feb 2 08:33:12 mini kernel: Console: colour VGA+ 80x25 Feb 2 08:33:12 mini kernel: Calibrating delay loop... 55.50 BogoMIPS ... As far as I can see from that, the start of the pcmcia modules went ok, and the start of the network (card insertion) was ok. There were no syslog messages related to the system freeze, since the cpu just stopped (no time to write anything). I am afraid that is not very helpful

More: detailed bug report Re: Question: Cardbus Tulip card works unreliably (system crash) Date: 2000, Feb 07 From: <rolf.fiedler@ferrari.de>

I did some more experiments regarding the previously-mentioned bug. I tried (kernel/pcmcia) 2.2.14/1.3.9 and 2.2.14/1.3.10 with the same results. I can insert the card and the network config is done. I can ping & telnet without crashes. I can do a ftp and everything on the control connection works. If I do a download the system crashed without any messages printed anywhere (irq pending and not handled?). I thought the packet size is triggering the bug. So I did a ping -s 1500. That works long enough to make experiment boring. Next theory is the packet rate. What happens if new packets arrive while the previous is not transferred off the DEC-chip yet? I thought a flood ping might show this and it did. A ping -f kills the system after a while (60 seconds or so). Please note that we are talking about a slow computer here. It is a 166MHz Cyrix MediaGX with only 55bogomips (that is 0.055 bogogips :-). I will do any experiments that are suggested (well, the ones that seem useful - I will not stand on my head and hold my breath for 30 minutes). who is maintaining the tulip_cb module? I suspect the bug there. What can I do if I have a kernel that I know how to crash reproducable but that just enters an endless loop (irq condition not reset?) or locks the bus or whatever. How do I debug this? I would love some oopses, but I can't get any :-( Many thanks, Rolf

Warning: Problem resolved Re: Question: Cardbus Tulip card works unreliably (system crash) Date: 2000, Feb 08 From: <rolf.fiedler@ferrari.de>

The Palmax PD1000 mini-notebook requires the setting of PCIC_OPTS="cb_write_post=0" in /etc/sysconfig/pcmcia to work reliably with the tulip cardbus driver. Without the option the system will hang if the ethernet packet arrival rate is high. thank you David! Rolf

[ Add Message ]  to: "Cardbus Tulip card works unreliably (system crash)"

[ Members ]  [ Subscribe ]  [ Admin Mode ] 
[ Show Frames ]  [ Help for HyperNews at pcmcia-cs.sourceforge.net 1.10 ]