Next-in-Thread Next Message

Question Dual PCMCIA NIC system (Linksys plus NDC ) time outs and lost interrupts 

Forum: PCMCIA Network Adapter Issues
Date: 2000, Jan 29
From: Dale moberg dmoberg

Report on dual PCMCIA MIC interface lost interrupt on Hewlett-Packard Omnibook 5500 CT

Second card (Linksys) yields time outs waiting for device to not be busy? First card working fine.

Message from log indicating what seems to be the core problem is

Jan 29 11:12:33 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=1000.

I enclose outputs from uname, lsmod, proc/interrupts, cardctl, ifconfig, lsmod, and startup log for pcmcia modules.

[root@redhatomni net]# uname -a
Linux redhatomni 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 i586 unknown
[root@redhatomni net]# cardctl -V
cardctl version 3.0.14
[root@redhatomni net]# lsmod
Module                  Size  Used by
parport_pc              5620   0  (unused)
parport                 7124   0  [parport_pc]
nls_iso8859-1           2020   1  (autoclean)
pcnet_cs                7572   2 
8390                    5920   0  [pcnet_cs]
ds                      5740   2  [pcnet_cs]
i82365                 22640   2 
pcmcia_core            39912   0  [pcnet_cs ds i82365]
[root@redhatomni net]# cat /proc/interrupts
           CPU0       
  0:    7572752          XT-PIC  timer
  1:      31645          XT-PIC  keyboard
  2:          0          XT-PIC  cascade
  3:       8964          XT-PIC  pcnet_cs
  5:          0          XT-PIC  pcnet_cs
  8:          1          XT-PIC  rtc
 12:     255634          XT-PIC  PS/2 Mouse
 13:          1          XT-PIC  fpu
 14:     561531          XT-PIC  ide0
 15:     601841          XT-PIC  ide1
NMI:          0
[root@redhatomni net]# cardctl config
Socket 0:
  Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0
  Interface type is memory and I/O
  IRQ 3 is exclusive, level mode, enabled
  Function 0:
    Config register base = 0x03f8
      Option = 0x60, status = 0000
    I/O window 1: 0x0300 to 0x031f, auto sized
Socket 1:
  Vcc = 5.0, Vpp1 = 0.0, Vpp2 = 0.0
  Interface type is memory and I/O
  IRQ 5 is exclusive, level mode, enabled
  Function 0:
    Config register base = 0x0fd0
      Option = 0x43, status = 0000, copy = 0000
    I/O window 1: 0x0340 to 0x035f, auto sized
[root@redhatomni net]# cardctl status
Socket 0:
  5V 16-bit card present
  Function 0: ready
Socket 1:
  5V 16-bit card present
  Function 0: ready

[root@redhatomni pcmcia]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:80:C6:F6:8E:1F  
          inet addr:192.168.88.149  Bcast:192.168.88.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:8306 errors:0 dropped:0 overruns:0 frame:21
          TX packets:927 errors:0 dropped:0 overruns:0 carrier:0
          collisions:1 txqueuelen:100 
          Interrupt:3 Base address:0x300 

eth1      Link encap:Ethernet  HWaddr 00:E0:98:06:AC:30  
          inet addr:204.210.245.55  Bcast:204.210.245.255  Mask:255.255.255.0
          UP BROADCAST RUNNING  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:2 overruns:0 frame:0
          TX packets:0 errors:45 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100 
          Interrupt:5 Base address:0x340 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:3924  Metric:1
          RX packets:247 errors:0 dropped:0 overruns:0 frame:0
          TX packets:247 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 

[root@redhatomni pcmcia]# route Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 255.255.255.255 * 255.255.255.255 UH 0 0 0 eth0 204.210.245.55 * 255.255.255.255 UH 0 0 0 eth1 192.168.88.149 * 255.255.255.255 UH 0 0 0 eth0 204.210.245.0 * 255.255.255.0 U 0 0 0 eth1 localnet * 255.255.255.0 U 0 0 0 eth0 127.0.0.0 * 255.0.0.0 U 0 0 0 lo

Startup from /var/log/debug

Jan 28 20:46:59 redhatomni pcmcia: Starting PCMCIA services:
Jan 28 20:46:59 redhatomni pcmcia:  modules
Jan 28 20:46:59 redhatomni kernel: Linux PCMCIA Card Services 3.0.14 
Jan 28 20:46:59 redhatomni kernel:   kernel build: 2.2.12-20 #1 Mon Sep 27 10:25:54 EDT 1999 
Jan 28 20:46:59 redhatomni kernel:   options:  [pci] [cardbus] [apm] 
Jan 28 20:46:59 redhatomni kernel: Intel PCIC probe:  
Jan 28 20:46:59 redhatomni kernel:   Cirrus PD6729 PCI-to-PCMCIA at bus 0 slot 3, port 0x3e0, 2 sockets 
Jan 28 20:46:59 redhatomni kernel:     host opts [0]: [ring] [1/5/0] [1/20/0] 
Jan 28 20:47:00 redhatomni kernel:     host opts [1]: [ring] [1/5/0] [1/20/0] 
Jan 28 20:47:00 redhatomni kernel:     ISA irqs (default) = 3,4,5,7,9,11,12 polling interval = 1000 ms 
Jan 28 20:46:59 redhatomni pcmcia:  cardmgr.
Jan 28 20:46:59 redhatomni cardmgr[367]: starting, version is 3.0.14
Jan 28 20:47:00 redhatomni rc: Starting pcmcia succeeded
Jan 28 20:47:01 redhatomni cardmgr[367]: watching 2 sockets
Jan 28 20:47:01 redhatomni kernel: cs: IO port probe 0x1000-0x17ff: clean. 
Jan 28 20:47:01 redhatomni kernel: cs: IO port probe 0x0100-0x04ff: excluding 0x220-0x22f 0x330-0x337 0x378-0x37f 0x388-0x38f 0x3b0-0x3ff 0x480-0x48f 
Jan 28 20:47:01 redhatomni kernel: cs: IO port probe 0x0a00-0x0aff: clean. 
Jan 28 20:47:01 redhatomni cardmgr[367]: initializing socket 0
Jan 28 20:47:01 redhatomni kernel: cs: memory probe 0x0d0000-0x0dffff: clean. 
Jan 28 20:47:01 redhatomni cardmgr[367]: socket 0: NDC Instant-Link Ethernet
Jan 28 20:47:01 redhatomni inet: inetd startup succeeded
Jan 28 20:47:02 redhatomni cardmgr[367]: executing: 'insmod /lib/modules/r[367]: executing: 'insmod /lib/modules/2.2.12-20/pcmcia/pcnet_cs.o'
Jan 28 20:47:02 redhatomni kernel: eth0: NE2000 Compatible: io 0x300, irq 3, hw_addr 00:80:C6:F6:8E:1F 
Jan 28 20:47:02 redhatomni cardmgr[367]: executing: './network start eth0'
Jan 28 20:47:03 redhatomni lpd: lpd startup succeeded
Jan 28 20:47:03 redhatomni keytable: Loading keymap: 
Jan 28 20:47:03 redhatomni keytable: Loading system font: 
Jan 28 20:47:03 redhatomni rc: Starting keytable succeeded
Jan 28 20:47:04 redhatomni cardmgr[367]: initializing socket 1
Jan 28 20:47:04 redhatomni cardmgr[367]: socket 1: NE2000 Compatible Ethernet
Jan 28 20:47:04 redhatomni kernel: eth1: NE2000 Compatible: io 0x340, irq 5, hw_addr 00:E0:98:06:AC:30 
Jan 28 20:47:04 redhatomni cardmgr[367]: executing: './network start eth1'

[omitted stuff. Now trying to ping hosts on immediate segment that eth1 sits on]

[these messages produced because device busy flag set within the 8390 module . The TSR and ISR values are in the header file, 8390.h Check 8390.c to find the format code for this printk message.

A 0x3 value seems to be a sum of ok values. So the device is flagged busy but the interrupt and transmit status registers do not appear to give anything too helpful. No other errors found. Notice that the ifconfig message has all TX errors for eth1. Is there an option I need to set?

eth0 is working fine on its segment. Can ping localhost and the address ifconfiged to the device.204.210.245.55

#

[root@redhatomni net]# Jan 29 11:02:58 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=953.

Jan 29 11:03:08 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000. 
Jan 29 11:03:48 redhatomni last message repeated 4 times
Jan 29 11:03:58 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3t=t=1000. 
Jan 29 11:12:13 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=49500. 
Jan 29 11:12:23 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=1000. 
Jan 29 11:12:33 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x2, t=1000. 
Jan 29 11:13:28 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=5500. 
Jan 29 11:13:38 redhatomni kernel: eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=1000. 
Jan 29 11:13:58 redhatomni last message repeated 2 times

Next-in-Thread Next Message

Select this message: Dual PCMCIA NIC system (Linksys plus NDC ) time outs and lost interrupts

Messages Inline: 1 All Outline: 1 2 All

1. None Sounds like a classic interrupt conflict by David Hinds, 2000, Jan 30
(_ Ok OK, I guess next time I will just ignore proc/interruptsI by Dale moberg, 2000, Jan 30

Message Administration

This form allows you to delete, move, or copy one or more messages. You can move messages by copying and deleting the original. The action will be applied to the messages you select above and all replies to those selected messages.


If you want to copy or move messages, specify the HyperNews path of a destination forum or message that all messages will be copied or moved to. The destination must already exist, so maybe create it first.

Path of Destination (a Forum or Message): (e.g. "test")

Notify Subscribers at destination
NO


If you want to delete messages (the default), specify that here. If you want to move messages, you need to delete the original messages; placeholders will be left pointing to where they were moved.

Delete Messages
NO


Caution: After deleteing messages (the default), if you have not copied them (i.e. no destination above), then the selected messages are not be recoverable.

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