Hello,

What's the meaning of this message

NETDEV WATCHDOG: eth0 transmit timed out

when I ping another PC on a local network ?

I'm trying to configure a diskless PC, so, I adapt the initrd that comes from
the live system of the second install disk of the slackware 9.1 (maybe not the
better choice, but...)

For now, the PC boots correctly with netboot and pxelinux, the network adapter
is detected. I've installed only the few necessary modules and very reduced
init scripts, so the /etc/rc.d/rc.M contains these lines extracted from the
original /etc/rc.d/rc.inet1 (variables are transmitted from the kernel
command-line)

/sbin/ifconfig lo 127.0.0.1
/sbin/route add -net 127.0.0.0 netmask 255.0.0.0 lo
BROADCAST=`/bin/ipmask ${NETMASK} ${IPADDR} | cut -f 1 -d ' '`
# Set up the ethernet card:
echo "Configuring eth0:"
echo "/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}"
/sbin/ifconfig eth0 ${IPADDR} broadcast ${BROADCAST} netmask ${NETMASK}
/sbin/route add default gw ${GATEWAY} metric 1

So I get :

$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
i192.168.1.0 * 255.255.255.0 U 0 0 0 eth0
loopback * 255.0.0.0 U 0 0 0 lo
default 192.168.1.1 0.0.0.0 UG 1 0 0 eth0
$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:20:AF:F2:A5:32
inet addr:192.168.1.5 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:280149 errors:0 dropped:0 overruns:0 frame:0
TX packets:221215 errors:0 dropped:0 overruns:0 carrier:0
collisions:33 txqueuelen:100
RX bytes:283495402 (270.3 Mb) TX bytes:77614894 (74.0 Mb)
Interrupt:11 Base address:0xec00

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:7192 errors:0 dropped:0 overruns:0 frame:0
TX packets:7192 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:645342 (630.2 Kb) TX bytes:645342 (630.2 Kb)

That seems correct, but the network doesn't work (see above).

Any suggestions ? The next step should be setting NFS service.

--
^^ Gauthier
(_____/°°-ç
| \_`-"
)/@mmm||
\nn \nn FOE-Belgium : http://www.amisdelaterre.be

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

In alt.os.linux.slackware, Gauthier dared to utter,
> What's the meaning of this message
> NETDEV WATCHDOG: eth0 transmit timed out
>
> I'm trying to configure a diskless PC

I recommend you ask this question of people who are very much "in" to
diskless linux such as the Linux Terminal Server Project. Those people
are much more likely to be able to handle such a request.

Some google searches seem to indicate that the NETDEV WATCHDOG error
might be related to some bad kernel options related to the processor.
I'm really not sure though. I've not gotten that error before.

Hmm.... I just grepped the kernel source and found this little tidbit
in Documentation/networking/e1000.txt

CAUTION: When setting RxIntDelay to a value other than 0, adapters may
hang (stop transmitting) under certain network conditions. If
this occurs a NETDEV WATCHDOG message is logged in the system
event log. In addition, the controller is automatically reset,
restoring the network connection. To eliminate the potential for
the hang ensure that RxIntDelay is set to 0.

- --
It is better to hear the rebuke of the wise,
Than for a man to hear the song of fools.
Ecclesiastes 7:5
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)

iD8DBQFBVtz9lKR45I6cfKARAtMZAJ4kU3pRyptks7b4mjod1J wyShLBqwCgjRvL
az09Um4JuGmvVwmsANu/qp0=
=brCO
-----END PGP SIGNATURE-----

NOTE: This message was sent thru a mail2news gateway.
No effort was made to verify the identity of the sender.
--------------------------------------------------------

pgp trash troll delete

+Alan Hicks+ <alan@lizella.network> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> In alt.os.linux.slackware, Gauthier dared to utter,
>> What's the meaning of this message
>> NETDEV WATCHDOG: eth0 transmit timed out
>>
>> I'm trying to configure a diskless PC
>
> I recommend you ask this question of people who are very much "in" to
> diskless linux such as the Linux Terminal Server Project. Those people
> are much more likely to be able to handle such a request.
>
> Some google searches seem to indicate that the NETDEV WATCHDOG error
> might be related to some bad kernel options related to the processor.
> I'm really not sure though. I've not gotten that error before.
>
> Hmm.... I just grepped the kernel source and found this little tidbit
> in Documentation/networking/e1000.txt
>
> CAUTION: When setting RxIntDelay to a value other than 0, adapters may
> hang (stop transmitting) under certain network conditions. If
> this occurs a NETDEV WATCHDOG message is logged in the system
> event log. In addition, the controller is automatically reset,
> restoring the network connection. To eliminate the potential for
> the hang ensure that RxIntDelay is set to 0.
>
> - --
> It is better to hear the rebuke of the wise,
> Than for a man to hear the song of fools.
> Ecclesiastes 7:5
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.1 (GNU/Linux)
>
> iD8DBQFBVtz9lKR45I6cfKARAtMZAJ4kU3pRyptks7b4mjod1J wyShLBqwCgjRvL
> az09Um4JuGmvVwmsANu/qp0=
> =brCO
> -----END PGP SIGNATURE-----

Le 26 Sep 2004 10:16:13 -0500, +Alan Hicks+ <alan@lizella.netWORK> a écrit:
>
> Some google searches seem to indicate that the NETDEV WATCHDOG error
> might be related to some bad kernel options related to the processor.
> I'm really not sure though. I've not gotten that error before.

It's strange because I used the same standard kernel and modules than
those of the system installed on the PC (it 's not yet really a diskless
workstation...), and I didn't encountered this error this way.
Thanks aniway,
--
^^ Gauthier
(_____/°°-ç
| \_`-"
)/@mmm||
\nn \nn FOE-Belgium : http://www.amisdelaterre.be