*** This bug is a duplicate of bug 347711 ***
https://bugs.launchpad.net/bugs/347711
** Changed in: linux
Status: Confirmed = Fix Released
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
https://bugs.launchpad.net/bugs/76489
You received this
*** This bug is a duplicate of bug 347711 ***
https://bugs.launchpad.net/bugs/347711
I'm running 2.6.28.15 kernel on my D945GCLF2 (realtek 8111c , using r8169). I
Just got that:
I experimenting random connection drop when transmitting data (heavy load
1Gbits) to an other pc thru Samba
I *had* exactly the same problem on ubuntu 9.04 with linux-
image-2.6.28-13-server.
I have found something interesting in the last kernel changelog
(2.6.30):
http://kernel.org/pub/linux/kernel/v2.6/ChangeLog-2.6.30
commit fd4d34295b36c5d9a1aba3d3f2764d721db093be
Merge: 4d11eff 52ea3a5
Author:
Downloaded and installed 2.6.30-generic
It's better... but not fixed. I got through about 150GB then it died again. I
have not tried again... but will as soon as I have time
Tom
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
*** This bug is a duplicate of bug 347711 ***
https://bugs.launchpad.net/bugs/347711
** This bug has been marked a duplicate of bug 347711
Realtek RTL8111/8168B PCI Express Gigabit Ethernet controller Unstable on
Jaunty
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0:
I'm seeing this bug with xubuntu 9.04 also :(
lspci
00:00.0 Host bridge: Intel Corporation 82945G/GZ/P/PL Memory Controller Hub
(rev 02)
00:02.0 VGA compatible controller: Intel Corporation 82945G/GZ Integrated
Graphics Controller (rev 02)
00:1b.0 Audio device: Intel Corporation 82801G (ICH7
Ubuntu, Jaunty Jackalope, 2.6.28-11-server:
http://www.newegg.com/Product/Product.aspx?Item=N82E16856101079
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 02)
[15752.970039] [ cut here ]
My 1Gb/s card is now working because I have connected it to a 100Mb/s
switch. I am guessing since it can only work at 1/10 of the speed, it
never feels heavy load, so it never goes down.
Hope it helps someone as temporal solution.
--
network device, module r8169, fails with NETDEV WATCHDOG:
sudo ethtool -K eth0 tso off stops the debug log, but I still get
network drops.
I'm using the eee b202 as a cheap fileserver and I'm trying to backup a 1TB
drive to a local 1TB drive over the lan (good sysadmin, huh? ;-) )
Anyway - I have not successfully backed up anything yet because a
I am having the same problem using Ubuntu Server 9.04 (Jaunty). The
machines is the Atom 330 based board D945GCLF2 with the RealTek RTL8111C
Ethernet Controller.
After a whil of heavy load (sometimes seconds) the network stops
working. After some time (arrond 1 or 2 minutes) it recovers itself
Tryed solution proposed at the beggining of this thread, consisting on
turning off TSO (TCP Segmentation Offload) with sudo ethtool -K eth0
tso off, but it does not work. The network stops working under heavy
load.
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
I am seeing this identical problem on an Ubuntu Server 9.04 (Jaunty)
install, whenever there's a brief period of heavy network activity, the
network locks up for a minute, with NETDEV WATCHDOG: eth0 (r8169):
transmit timed out in the logs, followed by a similar stack trace to the
above posters.
On Mon, 2009-05-04 at 21:02 +, Manoj Iyer wrote:
Can you please try the jaunty kernel
I am running jaunty (linux-image-2.6.28-11-generic version 2.6.28-11.42)
on an EeeBox B202 with this chip:
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit
Downloading and compiling r8168 from realtek solved my network problems.
Had to blacklist the r8169 module.
I tried to install the kernel today, but got a dependency error on installing
headers
eg: linux-headers-2.6.28-13-generic_2.6.28-13.44~lp76489manjo1_amd64.deb
depends on
Just setup an Asus eee Box with Ubuntu 9.04 server
The bug's still there
uname -r
2.6.28-11-server
lspci
03:00.0 Network controller: RaLink RT2860
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 02)
log (server is called
Can you please try the jaunty kernel in
http://people.ubuntu.com/~manjo/lp76489-jaunty/
and let me know if it fixes the above issue ?
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
https://bugs.launchpad.net/bugs/76489
You received this bug
Report.sh does not work for me either:
la...@backend:~$ sudo ./report.sh good
Failed to find any device with vendor ID 10ec
la...@backend:~$
yet:
la...@backend:~$ lspci -nn|grep 10ec
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd.
RTL8111/8168B PCI Express Gigabit Ethernet
I have a similair problem, although report.sh doesnt work for me
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 02)
Subsystem: ASUSTeK Computer Inc. Device 82c6
Flags: bus master, fast devsel, latency 0, IRQ
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = TJ (intuitivenipple)
** Bug watch added: Linux Kernel Bug Tracker #12500
http://bugzilla.kernel.org/show_bug.cgi?id=12500
** Also affects: linux via
http://bugzilla.kernel.org/show_bug.cgi?id=12500
Importance: Unknown
** Changed in: linux
Status: Unknown = Confirmed
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
https://bugs.launchpad.net/bugs/76489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
It looks likely this is related to bug #326891 2.6.27.11 kernel breaks
r8169 support for rtl8102e. The fix for that issue was to introduce
five patches that correct the handling of the various realtek devices.
Some devices are recognised by PCI ID and some by their MAC, with work-
arounds for the
Looking back through the comments Giraya's observation that the PCI
device flags change after rmmod/insmod is potentially a clue.
Could those affected collect reports from a fresh boot before the issue
strikes. I'd like to see the result of lspci for the realtek device
before and after
** Changed in: linux (Ubuntu)
Importance: Medium = High
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
https://bugs.launchpad.net/bugs/76489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
** Changed in: linux-source-2.6.22 (Ubuntu)
Assignee: Brian Murray (brian-murray) = (unassigned)
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
https://bugs.launchpad.net/bugs/76489
You received this bug notification because you are a member of
Ubuntu 8.10 x64
$ uname -a
Linux pc3 2.6.27-11-generic #1 SMP Thu Jan 29 19:28:32 UTC 2009 x86_64 GNU/Linux
Mar 25 15:21:27 pc3 kernel: [ 1091.804030] [ cut here ]
Mar 25 15:21:27 pc3 kernel: [ 1091.804042] WARNING: at
Awesome! this bug never ends!
2009/3/3 Siva hellos...@gmail.com
I have the latest Jaunty and I am getting the same message.
[175559.988029] [ cut here ]
[175559.988038] WARNING: at
/build/buildd/linux-2.6.28/net/sched/sch_generic.c:226
dev_watchdog+0x219/0x230()
I have the latest Jaunty and I am getting the same message.
[175559.988029] [ cut here ]
[175559.988038] WARNING: at
/build/buildd/linux-2.6.28/net/sched/sch_generic.c:226
dev_watchdog+0x219/0x230()
[175559.988044] NETDEV WATCHDOG: eth0 (r8169): transmit timed out
I am experiencing same bug with kernel 2.6.27-11 (after upgrade from
2.6.27-7).
** Attachment added: dmesg dump
http://launchpadlibrarian.net/21997137/dmesg-r8169-watchdog-timeout.txt
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
I'm having the same problem on a gigabyte board with built-in realtek
nic. I've found numerous bugs for the same issue, not sure which is the
main one and if ubuntu team is checking for duplicates.
I have created a script on another machine that emails me when the link
is down. I then
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
https://bugs.launchpad.net/bugs/76489
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Why is this set to triaged when it is only confirmed?
2008/11/29 Leann Ogasawara [EMAIL PROTECTED]
** Changed in: linux (Ubuntu)
Status: Incomplete = Triaged
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit
timed out
https://bugs.launchpad.net/bugs/76489
Hi,
I'm seeing the same problem when transfering large files. The network
works until it crashes. I'm using Intrepid Ibex with the latest updates:
$ dmesg
[ ... ]
[ 1159.988394] [ cut here ]
[ 1159.988402] WARNING: at
Hi,
dmesg and lspci output is already attached to this bug report, see the
attachments at the side. Also, the network card related to this bug is
not the same as the one in the other bug report you mention. This bug is
very intermittent (in terms of months).
Thanks
--
network device, module
Here is the current state of the kernel r8169 driver development,
if you can follow my instructions, please post
the rep.txt file and report success or failure
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/256331/comments/12
Thanks,
Martin
--
network device, module r8169, fails with
It does not seem to be firmly connected to the data transfer, I have on
occasion turned the computer on and loaded up google but hitting search and
the page wont load.. due to this bug. On other occasions the system has been
connected for several days solid and there has been no network issue
Dear Friends,
Now I am not in a position to test the version now, since that system is in
production environment. Really i appreciate the effect taken by you guys.
As a linux addict I would like to get linux update to my mail id.
Cheers,
Baskar
On Thu, Aug 28, 2008 at 10:34 PM, Leann
I have a Hardy system using the r8169 driver for a device with PCI ID
[10ec:8168] and I'm running kernel version 2.6.24-19.34-server.
TSO is disabled by default:
[EMAIL PROTECTED]:~/kvm-images$ ethtool -k eth0
Offload parameters for eth0:
rx-checksumming: on
tx-checksumming: off
scatter-gather:
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a result, the kernel team would
appreciate it if you could please test this newer 2.6.27 Ubuntu kernel.
There are one of two ways you should be able to test:
1) If you are comfortable
This bug is back in full force with the latest kernel updates:
2.6.24-19-generic
Please advise me on any information that I can provide before / after
occurrence of this issue so that I can help.
Alan
On Thu, Mar 6, 2008 at 12:48 AM, Giraya [EMAIL PROTECTED] wrote:
Hi,
exactly the same
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
Status: Fix Released = Triaged
** Tags added: regression
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
https://bugs.launchpad.net/bugs/76489
You received this bug notification
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = Ubuntu Kernel Team (ubuntu-kernel-team)
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
https://bugs.launchpad.net/bugs/76489
You received this bug notification because you are a member of Ubuntu
Hi Alan,
After you experience this issue, can you capture your entire dmesg
output and attach it to this report? Thanks.
** Changed in: linux (Ubuntu)
Status: Triaged = Incomplete
--
network device, module r8169, fails with NETDEV WATCHDOG: eth0: transmit timed
out
Hi,
exactly the same thing here.
Maybe this is nothing, but after the watchdog timeout, i've tried to
rmmod/insmod r8169 and then done lspci -v.
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 01)
Subsystem: ASRock
Unfortunately this bug has reappeared, no updates or other changes have
been made to this system since upgrading to the hardy kernel a few month
or two ago. The NETDEV WATCHDOG time out thing happened just now on it,
I imagine this bug could be hard to pin down if it only manifests it's
self once
I'm marking this as 'Fix Released' agains the Hardy development kernel
based on Alan's comments that this appears fixed and there has not been
feedback from the original reporter. Thanks Alan for testing. Against
linux-source-2.6.20 and linux-source-2.6.22 this will be closed.
Thanks.
**
Hi Alan,
We have onboard network card as RTL8168b and extra pci card 3Com Fast
EtherLink XP Pci (3C9058-TX).
We have tried to install both ubuntu 7.10 server(Guesty) and ubuntu 7.04
desktop (Feisty), but network doesnt work on both OS.
But you said it was fixed with 2.6.24-2-generic.
I could
Hi Baskar,
When you say it doesn't work do you mean that you don't get any network
interface at all with this card under 7.10 or 7.04? Or that you are
suffering from this specific bug? If you don't get any network interface at
all then thats a separate issue and you should check the ubuntu forums
Hi Alan,
Thanks for your replay.
I meant to say Network doesnt work under 7.10 or 7.04.
I want to install vmware server 2.0 on the OS what i am going to install
Regards,
Baskar
On Jan 23, 2008 6:08 PM, Alan Mc [EMAIL PROTECTED] wrote:
Hi Baskar,
When you say it doesn't work do you mean
This is a bug reporting system. For support issues please see the Ubuntu
forums or IRC room #ubuntu on irc.freenode.net
On Jan 23, 2008 2:01 PM, baskar [EMAIL PROTECTED] wrote:
Hi Alan,
Thanks for your replay.
I meant to say Network doesnt work under 7.10 or 7.04.
I want to install vmware
Thanks for the update Alan. Klaas, since you are the original bug
reporter, can you confirm if this issue is resolved with the newer
development kernel from Hardy?
** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New =
At last this seems to be resolved. I have had no further issues since
upgrading to 2.6.24-2-generic before Christmas (tested for about 6 or 7
days straight). Lets hope it stays this way for me and the others
affected!
For anyone else with this issue, upgrading to the hardy kernel ( =
Alan Mc - Did you find out anything when testing this bug with the
2.6.24 kernel from Hardy? Thanks in advance.
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Phillip Lougher (phillip-lougher) = Ubuntu Kernel Team
(ubuntu-kernel-team)
** Description changed:
ubuntu feisty fawn
Hi Brian,
So far so good. I have only been back from holiday for a couple of days
but have been using the affected system extensively since then. So far
there have been no issues what so ever but as can be seen from earlier
reports, a few days can go by without this bug surfacing.
Will update
Alan: Something worth doing in the interim would be to try with hardy's kernel
and see if it does the same (I can only see daily alternate installers, but
booted into the expert mode I expect you can get a shell and set up the network
by hand and run some stress testing on it).
If that's going
Thanks for the suggestion, I will give it a try but I myself won't be
able to test as I am going away tomorrow for three weeks. Will
definitely give it a shot when I get back though, thanks.
Alan
On Dec 20, 2007 6:33 PM, Chris Jones [EMAIL PROTECTED] wrote:
Alan: Something worth doing in the
Am using hardy kernel now, 2.6.24. Will do some big transfers to see
what happens :)
Alan
On Dec 20, 2007 8:46 PM, mr [EMAIL PROTECTED] wrote:
Thanks for the suggestion, I will give it a try but I myself won't be
able to test as I am going away tomorrow for three weeks. Will
definitely give
56 matches
Mail list logo
