v 06)
>
> By a heavy traffic i get the following error:
> NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
>
> As a workaround a turned off jumbo frames support. Is there any other
> solution making it possible to use jumbo frames??
>
> Thanks for any help in advance.
On Mon, Aug 20, 2018 at 05:57:16PM +, Grzegorz Sójka wrote:
By a heavy traffic i get the following error:
NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
As a workaround a turned off jumbo frames support. Is there any other
solution making it possible to use jumbo frames
(rev 06)
By a heavy traffic i get the following error:
NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
As a workaround a turned off jumbo frames support. Is there any other
solution making it possible to use jumbo frames??
Thanks for any help in advance.
Looks like this:
https
v 06)
>
> By a heavy traffic i get the following error:
> NETDEV WATCHDOG: eth1 (r8169): transmit queue 0 timed out
>
> As a workaround a turned off jumbo frames support. Is there any other
> solution making it possible to use jumbo frames??
>
> Thanks for any
Hi there,
I have following integrated network adapter:
# lspci -s 02:00
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
By a heavy traffic i get the following error:
NETDEV WATCHDOG: eth1 (r8169): transmit queue
Hello,
I am using Lenny (kernel : 2.6.26-2-686).
After I start my computer, in a few minutes, I lose my Network connection
with a kernel failure. In the error logs, it is saying that:
" r8169: eth0: link up
[ 3129.367003] NETDEV WATCHDOG: eth0: transmit timed out"
However, more interes
Sven Arvidsson wrote:
On Wed, 2007-01-24 at 11:13 +0100, Serban Udrea wrote:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status , PHY status 786d, resetting...
eth0: Setting full-duplex based on MII #1 link partner capability of 41e1
The box is running an uptodate
On Wed, 2007-01-24 at 11:13 +0100, Serban Udrea wrote:
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out, status , PHY status 786d, resetting...
> eth0: Setting full-duplex based on MII #1 link partner capability of 41e1
>
> The box is running an uptodate
Hello!
Since about one week I receive at irregular intervals messages like the
following at the console (tty1) and in kern.log:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status , PHY status 786d, resetting...
eth0: Setting full-duplex based on MII #1 link partner
Lately I am getting kernel messages like this:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status , resetting...
They appear in /var/log/messages and also at the console where I am
working, even being inserted into text I am editing.
My kernel is 2.6.11, my
I had recently the same problem
I have a very old system and I had a find & grep over / so I forgot to
exclude /dev as I did with /var/log and got some
grep: /dev/kmem: Bad address
grep: memory exhausted
grep: memory exhausted
after this I looked over the log files and found the message from the
On Tue, 28 Oct 2003, ScruLoose wrote:
> On Mon, Oct 27, 2003 at 10:06:18PM -0500, ScruLoose wrote:
> > Hi all,
>
> Still pluggin' away at this problem with my D-Link DFE-530TX NIC.
>
> NETDEV WATCHDOG: eth0: transmit timed out
> eth0: Transmit timed out,
I have since tried specifying an IP and netmask on the ifconfig command
line, and adding a route to my gateway.
These seem to work fine, according to the output of ifconfig and route.
But then when I try to ping the gateway, I get this:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit ti
On Sun, Feb 23, 2003 at 12:27:20AM +0100, Ulf Janitschke wrote:
> Hi,
>
> i had the same problem. First with a 'D-Link'-card with Via-Rhine Chipset.
> With a 2.2 kernel everything was fine. With the 2.4 i got 'netdev watchdog
> eth0 transmit timed out'. T
Hi,
i had the same problem. First with a 'D-Link'-card with Via-Rhine Chipset.
With a 2.2 kernel everything was fine. With the 2.4 i got 'netdev watchdog
eth0 transmit timed out'. The problem showed up with both, the 2.4.16 and
2.4.18 kernel.
Same thing with a RTL8139-ca
ing woody.
> > everything has gone well apart from this message which keeps coming
> > through every now and then:
> >
> > netdev watchdog eth0 transmit timed out
> >
> > i used the 2.4 kernel which came with the disks - 2.4.18-bf2.4. the
> > network cards
On Sun, Feb 02, 2003 at 11:42:58AM +1100, Sam Varghese wrote:
> g'day all,
>
> i've just set up a debian box for use as a server, using woody.
> everything has gone well apart from this message which keeps coming
> through every now and then:
>
> netdev watchdog
;ve just set up a debian box for use as a server, using woody.
> > everything has gone well apart from this message which keeps coming
> > through every now and then:
> >
> > netdev watchdog eth0 transmit timed out
> >
> > i used the 2.4 kernel which came
hi ya
On Sun, 2 Feb 2003, Sam Varghese wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> g'day all,
>
> i've just set up a debian box for use as a server, using woody.
> everything has gone well apart from this message which keeps coming
> throu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
g'day all,
i've just set up a debian box for use as a server, using woody.
everything has gone well apart from this message which keeps coming
through every now and then:
netdev watchdog eth0 transmit timed out
i used the 2.4 kernel which
I'm getting thousands of these all the time and the network keeps
stopping.
--
This is on a DWL-650 network card. I have also seen this on an
ISA 3com 905 card as well.
What is NETDEV WATCHDOG?
How can this get fixed?
--
Dec 7 15:45:32 thorin last message repeated 8 times
Dec 7 15:
Hi folks,
Basically, my question comes down to this:
What the heck is going on that this message occurs and my box gets
basically unusable? Using the nvidia module from their website, not nv
and everything else just stock unstable with kernel 2.4.2.
Mar 10 00:38:33 maniac kernel: NETDEV
22 matches
Mail list logo
