This bug was filed against a series that is no longer supported and so
is being marked as Won't Fix. If this issue still exists in a supported
series, please file a new bug.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
** Changed in: linux (Ubuntu)
Status: New = Confirmed
** Tags added: b73a1py79
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/454747
Title:
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue
** Also affects: linux-latest-2.6 (Debian)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/454747
Title:
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue
It seems that this bug also affects Ubuntu 10.10.
$ uname -a
Linux ubuntu 2.6.35-22-generic #34-Ubuntu SMP Sun Oct 10 09:24:00 UTC 2010 i686
GNU/Linux
This is the output from /var/log/messages :
Oct 14 18:07:14 ubuntu kernel: [ 77.054544] lo: Disabled Privacy Extensions
Oct 14 18:13:49
I've been trying to work around this problem for quite some time now,
and it seems that doing stuff like adding a bwlimit=200 to my rsync
script consistently keeps the machine on the network for months now.
There does seem to be something about heavy network traffic that is
relevant here.
--
I don't manually reset the device. This is done automatically, after the
reset it renegotiaties the NIC speed too 100 full duplex and resumes
operation. It might be that I also experience loss but my network load
is so low it isn't noticeable.
I've bypassed the problem as well now by removing the
Since I upgraded to Lucid 2 days ago I'm struck by this error, too. Never had
any problems with karmic, though.
Symptoms are the same: Network gets unresponsive under heavy load.
Aug 29 16:42:50 COMPAKT kernel: [ 404.51] [ cut here
]
Aug 29 16:42:50 COMPAKT kernel:
I made a clean install of Lucid. I can live with this bug, my network
load became less for the last months. Still, recently under 2.26.32-24
it became more frequent, so I use 2.26.32-23 daily. I haven't tried
2.6.35 yet, I had fglrx issues with the Ubuntu PPA latest stable kernel
last time.
I
I'm so tired of chasing bugs on this VIA board that I think I'll be
switching to a purely Intel board.
No one takes any notice when we add information to this bug, so I'm moving
on.
Good luck, guys.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Hmm, I have the same issue, however I do not have the option of adding
additional LAN cards. However the bug is not 'fatal' for my server
(Ubuntu 10.04LTS), it recovers without issues after the nic reset
occurs. Can't even detect packet loss when it happens! I did notice this
bug happening to the
Anybody try to reproduce this under kernel 2.6.35? I'll give this a go
once the release kernel is available in Ubuntu mainline for Lucid.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a
You have to create a fair amount of traffic with 9.04. Bittorrent alone
will not cause the problem. Try FTPing a couple of DVD ISOs from a local
node on the LAN simultaneously and see what happens.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
I'm using kernel 2.6.28-11-generic on Ubuntu 9.04 everytime. I don't
experience any issues. Which kernel version did you use on Jaunty?
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a
9.04 also has the same issue, just more infrequent than other versions.
I feel that the VIA chipset support in the kernel isn't up to scratch.
Hate to say this, but it's probably time to move to an Intel platform and be
rid of this long-lasting headache.
On Mon, Jul 5, 2010 at 2:55 AM, besson3c
I'm back on Ubuntu 9.04 without any issue since months.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
On Lucid, they've broken my workaround, RTL-8169, so now I have NO OPTIONS
but to go back to 9.10 and use the RTL-8169 since the VIA is still utterly
broken with all versions.
Someone please fix this damn bug...
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Do we know for absolute certain that 9.04 was not affected by this bug?
I don't remember having it when I used 9.04, but it seems weird that it
has been reproduced in other Linux OSes, the latest 2.6.33 kernels,
other versions of Ubuntu, but not 9.04. The symptoms where different,
but I even had
Same problem with Ubuntu Desktop x64 (kernel 2.6.32-23). Drops
connection every hour or so.
Asus UL30A
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I use Ubuntu 9.04 most of the time, which is not affected by this bug. I
experienced the same bug on 10.04 on the rare occasions I tried to use
it. I use the 2.6.33-02063303-generic kernel as well.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Unfortunately I'm still able to reproduce this problem in 2.6.33.
However, when my ethernet interface crapped out nothing was logged to
/var/log/messages. Doing an ifdown and then ifup did not restore the
interface, it was unable to get a lease from the DHCP server (all other
machines on the
Sorry, 2.6.33-02063303-generic to be exact...
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I haven't spent a whole lot of time in .33 yet, but after upgrading to
Ubuntu 10.04 and kernel 2.6.32-21-generic I'm still having this problem,
so no love for me.
If there is anyway to get sound and 3D Nvidia video working in the .33
kernels please let me know (if you know off the top of your
Hi nadasjo...@freemail.hu,
This bug was reported a while ago and there hasn't been any activity in it
recently. We were wondering if this is still an issue? Can you try with the
latest development release of Ubuntu? ISO CD images are available from
http://cdimage.ubuntu.com/releases/ .
I'm still experiencing this problem and would very much like this fixed,
and am assuming that this command can be run at any time, and not just
after the crash? It obviously won't work without network connectivity...
I'll add this report to this report and will start testing the newer
kernel
Stable Linux kernel 2.6.33 was released yesterday. Will try it soon
hopefully.
So far, I had no network issue with rc8, but my tests were not very
extensive. Still, 4 hours of continous torrent dowload is something I
couldn't manage before.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0
Ubuntu kernel 2.6.33 rc8 is already released, so I guess we will soon
see a stable 2.6.33.
You can install the latest kernel via .deb files from the Ubuntu PPA:
http://kernel.ubuntu.com/~kernel-ppa/mainline/
I'm currently writing from 2.6.33 rc7. It lacks Radeon support in my
setup, so Firefox
Running Kubuntu 9.10 with latest updates, same problem here on a ASUS
A8V-XE, running same VT6102 Rhine II controller. Under heavy network
load (file copying it crashes out. Adding acpi=off in Grub makes the PC
really slow (Athlon 64 x2 4200) and ther is not networking hat so ever!
Changing ACPI
The S1 didn't work, network dropped out AGAIN and got: :
Kubuntu64 kernel [ 7321.040164] eth1: Transmit timed out, status 0003,
PHY status 786d, resetting...
Kubuntu64 kernel [ 7321.040334] via-rhine: Reset not complete yet.
Trying harder.
Kubuntu64 kernel [ 7321.040912]
S3 dropped out quicker than I expected, same old problem.
Disabled on-board LAN, stuck in a old 3COM 3C905B PCI NIC. Can't disable
ACPI still in the BIOS.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification
Disabling the on-board Via-Rhine NIC and using the 3COM 3C905B PCI NIC
has resolved the problem. No timeouts and solid performance. Disabling
ACPI in the BIOS seems to be a red herring.
Therefore, to me suggests a driver bug which needs an urgent fix
especially as this chip-set is quite common.
Looks as though Lucid is going to be based on kernel 2.6.32, in which
case the above mentioned (#34) bug fix will not be included. Guess the
onboard LAN will remain disabled for a lot longer than I had hoped.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
I've been running for about 3 weeks with a Realtek RTL-8169 PCI card
(turns out that the Intel card I mentioned earlier was PCI-e and I was
already using that slot) with no problems with large file transfers.
I also would like to mention that Ubuntu 9.04 with no kernel updates
will also display
I believe this bug affects me as well. My network adapter ceases to work
after some time, restarting the network services doesn't help. I tried
disabling ACPI, but it resulted in sound issues.
Jan 10 22:40:25 oveges-desktop kernel: [ 6709.000211] [c0150107]
run_timer_softirq+0x117/0x200
Jan 10
No mention of a driver fix for via-rhine in the 2.6.33 changelogs
either. I think I'm gonna have to go ahead and install the Intel card
since I don't want to stay with 9.04 for much longer. I'll let you guys
know if changing the card helps the Shuttle or not.
--
NETDEV WATCHDOG: eth0
Hi
Has anyone tried with the latest kernel 2.6.32.2 ?
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Hello,
after I updated from Kubuntu 9.04 to 9.10 I have exactly the same issue with
the ethernet controller.
The motherboard is a MSI K9VGMV with the VT6102 [Rhine-II] (rev 7c).
Yesterday I installed the newest updates and the kernel is now
2.6.31-16, but the situation is the same than before.
I don't see any relevant changes in the 2.6.32.x changelogs so I don't
think it's worthwhile going through testing 2.6.32.2.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of
Yes you were right it changes nothing
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
This isn't an isolated issue with Ubuntu 9.10. I just tested using a
Fedora 12 Live CD, transferring 3x 8GB files simultaneously to a Windows
XP share and after about 15 minutes, the same problem occurred.
The kernel for Fedora 12 is 2.6.31.5-127.fc12.i686.
So the good news is that this isn't
If you point me at the bug thread I'll be happy to track it and provide
whatever info is useful. I'm anxious to see this fixed, this is
particularly annoying, and I would imagine that if it is at all
widespread that it would be a nice one to have fixed.
Any theories as to why I was able to
Found this: http://bugzilla.kernel.org/show_bug.cgi?id=11663
** Bug watch added: Linux Kernel Bug Tracker #11663
http://bugzilla.kernel.org/show_bug.cgi?id=11663
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug
I think the watchdog kicked-in because the via-rhine driver did not
respond to a command (I think I read somewhere that it waits 10ms). So,
assuming that the Ethernet controller has hung, the system attempts to
reset the VT6102 chip, but looking at the log that isn't successful
either, it just
I have an Intel Pro 1000, but I need both PCI slots for another cards,
so... I'll add a link in that thread you posted above to this one just
to sort of ping those guys on this.
Do you know of other PC vendors that use the VT chipsets for their
ethernet controllers? Have you looked into whether
I hope this is related: http://patchwork.kernel.org/patch/69308/
Would love to see this fixed by the next Ubuntu LTS release.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of
That's interesting, because I've been running 9.04 with 2.6.28-16 for
weeks now without this issue.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Yeah, I never once had this problem under 2.6.28 in 9.04 either. I guess
this is a combination of 9.10 and any kernel?
The only possible explanation to this is whether any kernel modules
might be causing this problem? I'm a little unclear as to how it is that
you can select an older kernel module
Dec 25 02:26:53 epistaxis kernel: [ 1021.816031] [ cut here
]
Dec 25 02:26:53 epistaxis kernel: [ 1021.816038] WARNING: at
/build/buildd/linux-2.6.28/net/sched/sch_generic.c:226 dev_\
watchdog+0x270/0x280()
Dec 25 02:26:53 epistaxis kernel: [ 1021.816043] NETDEV WATCHDOG:
Okay, this is really interesting... I reproduced this error in 2.6.28
just now. The best way to do this is by downloading or rsyncing some
large files so that there is a lot of heavy I/O (or at least, so it
seems, this may not be relevant at all).
Is this Watchdog thing a component of Ubuntu 9.10
Did some googling around and it seems Ubuntu is the only distro having this
issue.
Rather tempted to throw in an old HDD into the Shuttle and try testing a new
Fedora or openSUSE...
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You
hi
same problem here with a
00:12.0 Ethernet controller: VIA Technologies, Inc. VT6102 [Rhine-II] (rev 7c)
computer is runing fine until i get the following in kern.log
Dec 8 13:01:33 gwa194l kernel: [86311.31] [ cut here
]
Dec 8 13:01:33 gwa194l kernel:
This problem also persists with 2.6.31-16.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
2.6.28-16-generic (9.04) has been stable for over 2 weeks.
I wonder which kernel version broke the VIA-Rhine support?
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
I spoke prematurely... noapic seems to change the symptoms, but the
problem is still very apparent. Reproducing this is a little tricky, it
seems to happen randomly, but there are times where it will crap out
within seconds of starting some sort of download. It seems that heavy
downloads trigger
Nope, this problem still persists with 2.6.31-15-generic
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I went back to 9.04 and loaded all updates. No further problems for a
week. Even passed the ftp/smb tests that previously failed with
consistantly 9.10.
I will stay with 9.04 until this problem is repaired.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
So far I haven't been able to reproduce this problem with the new kernel
version that I just installed via apt-get (w/o noapic in the kernel
boot) FWIW...
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification
I think the noapic is actually a viable workaround for me. The two
freezes I mentioned above seem unrelated, due to low memory conditions
while running VMs. For now it looks like the noapic command has
stabilized my ethernet.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
Since adding noapic I have had two complete freezes. I have no idea if
this is related, but the last few lines in /var/log/messages before the
crash were:
Nov 17 05:04:05 mymachine kernel: [89002.594109] ata4: soft resetting link
Nov 17 05:04:05 mymachine kernel: [89002.791732] ata4.00:
I found some pretty old threads that dealt with this problem in other
OSes and the recommendation was to add noapic to the kernel boot. Have
you played around with any of these options? I've added noapic, and I
will report back if I'm still able to reproduce this problem.
--
NETDEV WATCHDOG:
I take my previous comment back. This occurs with a clean install on a
Shuttle SK22V10 with 9.10.
Here my latest messages log:
Nov 15 16:37:07 cube kernel: [338855.220066] usb 4-1: USB disconnect, address 2
Nov 15 16:37:07 cube kernel: [338855.220246] gspca: disconnect complete
Nov 15 16:59:35
I'm getting this too after the upgrade to 9.10... It occurs enough to be
a significant problem for me, I'm also on a Shuttle.
I'd really rather not wipe and reinstall, although I'm open to a dirty
reinstall if this will help. Seems like a rather bogus sort of solution
though...
--
NETDEV
I'm seeing the same thing periodically on my Shuttle PC with a clean
install of 9.10. This never happened with 9.04, but i've possibly seen
it with pre-9.04 versions (i say possibly because the behavior was the
same but i never checked the kernel log).
--
NETDEV WATCHDOG: eth0 (via-rhine):
Loaded Ubuntu 9.10 from scratch and not via update-manager and 9.04.
Problem has not returned.
Please ignore my comments for now.
--
NETDEV WATCHDOG: eth0 (via-rhine): transmit queue 0 timed out
https://bugs.launchpad.net/bugs/454747
You received this bug notification because you are a member
My Shuttle box also suffers from this problem after upgrading to 9.10
(9.04 was fine). Ethernet chip periodically locks up - about once a day
with the following log:
Nov 3 19:24:39 cube kernel: [ 9782.746442] EXT3-fs warning: maximal mount
count reached, running e2fsck is recommended
Nov 3
** Attachment added: AlsaDevices.txt
http://launchpadlibrarian.net/33905263/AlsaDevices.txt
** Attachment added: AplayDevices.txt
http://launchpadlibrarian.net/33905264/AplayDevices.txt
** Attachment added: ArecordDevices.txt
http://launchpadlibrarian.net/33905265/ArecordDevices.txt
65 matches
Mail list logo
