Salut � tous,
Je suis actuellement en Mandrake 8 et je rencontre des pbs avec ma carte eepro100.
Celle ci se bloque r�guli�rement pendant 30 � 60 secondes. Je ne peux alors ni pinger 
d'autres machines ni me faire pinger. Bref, c'est comme si je n'�tais plus sur le 
r�seau pendant 1 minute !!
Les �ventuels sessions en cours ( telnet, ftp, nfs ) se retrouvent dans les choux.
Le fichier syslog me renvoit les messages qui suivent dans le mail, avant que tout ne 
redevienne normal.
J'ai notamment un "kernel: eepro100: wait_for_cmd_done timeout" qui me g�ne un peu !!!
Est ce que quelqu'un a une id�e ? Est ce un probl�me de config ? Est ce un probl�me du 
driver eepro100 ?  Dans ce cas, faut il le patcher et comment ( j'ai un kernel 
2.4.3.20 ) ?
Merci d'avance pour votre aide
Nicolas



___________________________
Jun 18 07:10:47 nribm2 kernel: eepro100: wait_for_cmd_done timeout!Jun 18 07:11:18 
nribm2 last message repeated 23 timesJun 18 07:11:19 nribm2 last message repeated 2 
timesJun 18 07:11:20 nribm2 amd[865]: file server rhea-test.tibco-test.fr type nfs is 
downJun 18 07:11:20 nribm2 amd[865]: file server charlie.tibco-test.fr type nfs is 
downJun 18 07:11:23 nribm2 kernel: NETDEV WATCHDOG: eth0: transmit timed outJun 18 
07:11:23 nribm2 kernel: eth0: Transmit timed out: status 0050  0c80 at 3725/3753 
command 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0: Tx ring dump,  Tx queue 3753 / 
3725:Jun 18 07:11:23 nribm2 kernel: eth0:     0 200c0000.Jun 18 07:11:23 nribm2 
kernel: eth0:     1 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:     2 000c0000.Jun 
18 07:11:23 nribm2 kernel: eth0:     3 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:   
  4 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:     5 000c0000.Jun 18 07:11:23 
nribm2 kernel: eth0:     6 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:     7
000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:     8 600c0000.Jun 18 07:11:23 nribm2 
kernel: eth0:   = 9 000ca000.Jun 18 07:11:23 nribm2 kernel: eth0:    10 000ca000.Jun 
18 07:11:23 nribm2 kernel: eth0:    11 000ca000.Jun 18 07:11:23 nribm2 kernel: eth0:   
 12 000ca000.Jun 18 07:11:23 nribm2 kernel: eth0:  * 13 000c0000.Jun 18 07:11:23 
nribm2 kernel: eth0:    14 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    15 
000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    16 200c0000.Jun 18 07:11:23 nribm2 
kernel: eth0:    17 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    18 000c0000.Jun 
18 07:11:23 nribm2 kernel: eth0:    19 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:   
 20 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    21 000c0000.Jun 18 07:11:23 
nribm2 kernel: eth0:    22 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    23 
000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    24 200c0000.Jun 18 07:11:23 nribm2 
kernel: eth0:    25 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    26
000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    27 000c0000.Jun 18 07:11:23 nribm2 
kernel: eth0:    28 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:    29 000c0000.Jun 
18 07:11:23 nribm2 kernel: eth0:    30 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0:   
 31 000c0000.Jun 18 07:11:23 nribm2 kernel: eth0: Printing Rx ring (next to receive 
into 210952, dirty index 210952).Jun 18 07:11:23 nribm2 kernel: eth0:     0 
00000001.Jun 18 07:11:23 nribm2 kernel: eth0:     1 00000001.Jun 18 07:11:23 nribm2 
kernel: eth0:     2 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:     3 00000001.Jun 
18 07:11:23 nribm2 kernel: eth0:     4 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:   
  5 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:     6 00000001.Jun 18 07:11:23 
nribm2 kernel: eth0: l   7 c0000001.Jun 18 07:11:23 nribm2 kernel: eth0:  *= 8 
00000001.Jun 18 07:11:23 nribm2 kernel: eth0:     9 00000001.Jun 18 07:11:23 nribm2 
kernel: eth0:    10 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    11
00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    12 00000001.Jun 18 07:11:23 nribm2 
kernel: eth0:    13 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    14 00000001.Jun 
18 07:11:23 nribm2 kernel: eth0:    15 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:   
 16 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    17 00000001.Jun 18 07:11:23 
nribm2 kernel: eth0:    18 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    19 
00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    20 00000001.Jun 18 07:11:23 nribm2 
kernel: eth0:    21 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    22 00000001.Jun 
18 07:11:23 nribm2 kernel: eth0:    23 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:   
 24 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    25 00000001.Jun 18 07:11:23 
nribm2 kernel: eth0:    26 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    27 
00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    28 00000001.Jun 18 07:11:23 nribm2 
kernel: eth0:    29 00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    30
00000001.Jun 18 07:11:23 nribm2 kernel: eth0:    31 00000001.Jun 18 07:11:50 nribm2 
amd[865]: file server charlie.tibco-test.fr type nfs is upJun 18 07:11:50 nribm2 
amd[865]: file server rhea-test.tibco-test.fr type nfs is up






-----------------------------------------------------------------
        Visit our Internet site at http://www.reuters.com

Any views expressed in this message are those of  the  individual
sender,  except  where  the sender specifically states them to be
the views of Reuters Ltd.

Répondre à