Very Computer

I have a strange problem with my network. I have two machines 1 Linux Suse
6.1 kernel 2.2.7 and an NT machine. They're connected with Macronix 100 mbit
network card using the tulip 0.91 driver.

Randomly network traffic stops and the only thing I can do is run "network
restart" with the Linux keyboard. (I run both machines on the NT display
using a X-Server). When I hook up a monitor to my Linux machine and ping NT
there are burst of network traffic every 30 seconds or so.

I've noticed that Netscape will cause this lockup quitte often but also
while working with NEdit and Perl the problem appears.

I already downloaded the diagnostics application for the tulip driver and
put it in a cron jobs to probe the status every 5 minutes. But there doesn't
seem to be a problem with the driver.

Disconnecting the cable temporarely doesn't solve the problem either.

Any clues on how to find out what's causing the problem?

Regards,
Willem joosten

Try using tcpdump on the linux box. An output of "ifconfig" and "route
-n" together with their NT equivalents can give us some clues. What
about samba, your NT X-Server and other programms eventually involved?

Johannes Niess

Could other applications block the entire networking sub-system? I guess the
Linux networking system is multithreaded en re-entrant (correct me if I'm
wrong).

Regards,
Willem Joosten

Route
--------
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use
Iface
10.100.0.1      0.0.0.0         255.255.255.255 UH    1      0        0
dummy0
194.109.6.1     0.0.0.0         255.255.255.255 UH    0      0        0
ippp0
10.0.0.0        0.0.0.0         255.255.255.0   U     0      0        0 eth1
10.100.0.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
194.109.6.0     0.0.0.0         255.255.255.0   U     0      0        0
ippp0
127.0.0.0       0.0.0.0         255.0.0.0       U     0      0        0 lo

Ifconfig (note eth0 is no longer used)
--------------------------------------------------
dummy0    Link encap:Ethernet  HWaddr 00:00:00:00:00:00
          inet addr:10.100.0.1  Bcast:10.255.255.255  Mask:255.255.255.255
          UP BROADCAST RUNNING NOARP  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

eth0      Link encap:Ethernet  HWaddr 00:80:48:C7:53:62
          inet addr:10.100.0.1  Bcast:10.100.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:100
          Interrupt:11 Base address:0xef40

eth1      Link encap:Ethernet  HWaddr 00:00:E8:58:27:F4
          inet addr:10.0.0.60  Bcast:10.0.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:766335 errors:0 dropped:7 overruns:0 frame:0
          TX packets:952686 errors:144 dropped:0 overruns:5 carrier:139
          collisions:0 txqueuelen:100
          Interrupt:12 Base address:0xec00

ippp0     Link encap:Point-to-Point Protocol
          inet addr:194.109.56.34  P-t-P:194.109.6.1  Mask:255.255.255.0
          UP POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:8088 errors:0 dropped:0 overruns:0 frame:0
          TX packets:8715 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:30

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:1044 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1044 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0

NT Ipconfig
----------------

Ethernet adapter MXNIC1:

 Description . . . . . . . . : PCI Bus Master Adapter
 Physical Address. . . . . . : 00-00-E8-58-27-F5
 DHCP Enabled. . . . . . . . : No
 IP Address. . . . . . . . . : 10.0.0.66
 Subnet Mask . . . . . . . . : 255.255.255.0
 Default Gateway . . . . . . : 10.0.0.60

NT route
------------
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ...00 00 e8 58 27 f5 ...... PCI Bus Master Adapter
0x3 ...00 00 00 00 00 00 ...... NdisWan Adapter
0x4 ...00 00 00 00 00 00 ...... NdisWan Adapter
0x5 ...00 00 00 00 00 00 ...... NdisWan Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0        10.0.0.60       10.0.0.66   1
         10.0.0.0    255.255.255.0        10.0.0.66       10.0.0.66   1
        10.0.0.66  255.255.255.255        127.0.0.1       127.0.0.1   1
   10.255.255.255  255.255.255.255        10.0.0.66       10.0.0.66   1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1   1
        224.0.0.0        224.0.0.0        10.0.0.66       10.0.0.66   1
  255.255.255.255  255.255.255.255        10.0.0.66       10.0.0.66   1
===========================================================================

I'm afraid I don't have the answer, but I am experiencing what I believe to
be the same problem.  I am running SUSE too, kernel 2.2.7 with IPChains. I
have a 3com cyclone nic and an eepro, with one going to my cable modem and
the eepro to the internal LAN.

After the linux box is idle for maybe 15 minutes I lose network connectivity
to the cable network from my LAN, a 98 box plus a laptop.  I cannot ping
out, nor ping the IP of the LAN-side nic.

Once I type on the console, the network will come up in a few secs.  I see
no messages in the messages file, the adm news files, nor on tty10 where
suse likes to print important messages.

Maybe this is the same problem?  Any ideas would be greatly appreciated!!!

<remove the 'dot' mojo to mail>

Quote:> Interface List
> 0x1 ........................... MS TCP Loopback interface
> 0x2 ...00 00 e8 58 27 f5 ...... PCI Bus Master Adapter
> 0x3 ...00 00 00 00 00 00 ...... NdisWan Adapter
> 0x4 ...00 00 00 00 00 00 ...... NdisWan Adapter
> 0x5 ...00 00 00 00 00 00 ...... NdisWan Adapter

Quote:> Active Routes:
> Network Destination        Netmask          Gateway       Interface
Metric
>           0.0.0.0          0.0.0.0        10.0.0.60       10.0.0.66   1
>          10.0.0.0    255.255.255.0        10.0.0.66       10.0.0.66   1
>         10.0.0.66  255.255.255.255        127.0.0.1       127.0.0.1   1
>    10.255.255.255  255.255.255.255        10.0.0.66       10.0.0.66   1
>         127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1   1
>         224.0.0.0        224.0.0.0        10.0.0.66       10.0.0.66   1
>   255.255.255.255  255.255.255.255        10.0.0.66       10.0.0.66   1

Quote:> After the linux box is idle for maybe 15 minutes I lose network
> connectivity to the cable network from my LAN, a 98 box plus a laptop.  I
> cannot ping out, nor ping the IP of the LAN-side nic.

> Once I type on the console, the network will come up in a few secs.  I
> see no messages in the messages file, the adm news files, nor on tty10
> where suse likes to print important messages.

Or set it up such that the ethernet IRQ will reload the APM timer, so that
it doesn't fall asleep while the ethernet is busy, and wakes up if it
receives an ethernet packet.

--
   Josef Drexler                 |    http://publish.uwo.ca/~jdrexler/
---------------------------------+----------------------------------------
 Please help Conserve Gravity    |  To email me, please change the country
 Stop flipping pancakes.         |  code to .ca - Death to Spammers!

Quote:> Hi,

> I have a strange problem with my network. I have two machines 1 Linux Suse
> 6.1 kernel 2.2.7 and an NT machine. They're connected with Macronix 100
mbit
> network card using the tulip 0.91 driver.

Quote:> Add the option "max_interrupt_work=1000" or some other high number to your
> loading of the module if you want to disable the "Too much work during an
> interrupt" check.

Regards,

Willem Joosten