This bug report is being closed because we received no response to the
previous inquiry for information. Please reopen if this is still an
issue in the current Ubuntu release, Jaunty Jackalope 9.04 -
http://www.ubuntu.com/getubuntu/download. If the issue remains in
Jaunty, please test the latest
Hello.
I had this problem too, until today.
On high load my nic (realtek 8169) cut the connection. I've add acpi=off
to the /boot/grub/menu.lst at the ende of the kernel line. After
rebooting the system i have copy 10 GB and 27 GB to my server without
any transmit error.
Perhaps somebody can
As of today, with all updates, this is still a problem.
I have kept the output of lshw and the syslog for the period (see
attachments). It looks to me like my two ethernet cards eth0/1 get
swapped around from the irq point of view. Maybe this will help someone
get a better understanding of the
** Attachment added: lshw output when not ok
http://launchpadlibrarian.net/18999330/lshw.eth0.nok.txt
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
** Attachment added: syslog when all is ok
http://launchpadlibrarian.net/18999656/syslog.eth0.ok.txt
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
** Attachment added: syslog when not ok
http://launchpadlibrarian.net/18999861/syslog.eth0.nok.txt
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I've just been assisting a user on #ubuntu who was experiencing this
error message when trying to connect two PCs via cross-over cable.
There are a huge number of reports in forums blogs and mailing lists
across the Internet, but few concrete solutions.
The best hints I could find were:
*
I no longer use the same hardware and not able to perform the suggested
test...
Sorry for not being able to help the community on this.
2008/8/29 Leann Ogasawara [EMAIL PROTECTED]
The Ubuntu Kernel Team is planning to move to the 2.6.27 kernel for the
upcoming Intrepid Ibex 8.10 release. As a
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
I had the same problem with Gutsy and Asrock 945G-DVI but not with the
Asus A2M-VM motherboard which has the same Realtek NIC.
POSSIBLE WORKAROUND:
For Asrock I tried everything, disabling acpi, updating BIOS and adding irqpoll
to grub. Then again I disabled ACPI HPET-table from BIOS. It did
Running Gutsy (7.10) gives same intermittent network failure problem -
and no problems at all under Windows XP
01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI
Express Gigabit Ethernet controller (rev 01)
Subsystem: ASRock Incorporation Unknown device 8168
Kernel 2.6.23 is out! And guess what is in the changelog!
Change INT0 trigger mode from edge-sense mode to level-sense mode,
in order to fix the following timeout error:
'NETDEV WATCHDOG: eth0: transmit timed out'.
Coool! :)
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
Unfortunately the bug is in the 2.6.22 kernel too :( It keeps occuring to me
again.
I'll wait until the 2.6.23 kernel and see if they'd fix that in it :(
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you
Unfortunately this happens with a 3com 3c905 card and after a unpredicted
period of time :(
I compiled a new kernel - 2.6.22.9 and I'm leaving the computer on for a long
time to see if it will drop the network again, but so far it hadn't :)
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed
I also use a 3com 3c905b NIC card in my PC, and I am sure that my
problems are related to this component.
Do we have to replace this NIC card with a newer one and which ones
could be the best choice for use in both Ubuntu and Vista ?
This NIC card WAS a famous and reliable one in the past, but I
I've been using the new kernel 2.6.22.9 since yesterday and I have no
drops or problems ;)
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
I do not know if it could help someone here: I'm on 64Studio (not
Ubuntu) and I have a Realtek 8139 that gave a similar message today
(netdev watchdog eth1: transmit out.
I finally found that a Windows Update (Realtek 8139 new driver) I made
last week gave this weird result in my Linux
I have the same problem with Feisty...
Lan is disabled after minutes or hours.
I have tried the pci=noacpi directive and I am looking for results, but
up to now I see that this directive seems to cause troubles like
disabling the sound...
I used Edgy on the same PC without a similar problem...
So, any idea when this bug will be fixed? Or suggestions wich kernel
verion to choose?
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
Disabling ACPI using pci=noacpi directive in grub menu.lst did not fix
my problem !
So I have removed this useless directive from my menu.lst.
I am back to Edgy, up to a reliable solution would fix this annoying
Feisty bug.
I hope this bug will be fixed in Ubuntu 7.10 Gutsy so that I could
Disabling ACPI support in the BIOS solved my problem.
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
Today the bug struck here for the second time, about 6 weeks since the
first time (comment 9).
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
Same here in Ubuntu-Feisty server with kernel 2.6.20-15 and 2.6.20-16
First appeared with a RhineII (built-in) LAN adapter. I first thought it might
be broken so I disabled it in Bios and replaced it with a Realtek (Ovislink-PCI
card):
00:06.0 Ethernet controller: Realtek Semiconductor Co., Ltd.
Same problem, but with 2 network cards. They are a 3COM 3c900B-TPO Etherlink XL
[Cyclone] and an nVidia MCP51 Ethernet Controller.
See also bug
https://bugs.launchpad.net/ubuntu/+source/linux-source-2.6.20/+bug/109629
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
Similar here too. The machine disappears from the network until reboot.
The card is
01:01.0 Ethernet controller: 3Com Corporation 3c905C-TX/TX-M [Tornado] (rev 78)
Subsystem: 3Com Corporation 3C905C-TX Fast Etherlink for PC Management
NIC
Control: I/O+ Mem+ BusMaster+ SpecCycle-
I have same error, with similar logs
My system: Gigabyte GA-M61PS3 Sempron 3200+ 1GB ram RTL-8029(AS)
/var/log/messages/
Jun 7 13:45:48 ubuntu kernel: [ 1841.092000] NETDEV WATCHDOG: eth1: transmit
timed out
Jun 7 13:45:50 ubuntu kernel: [ 1843.092000] NETDEV WATCHDOG: eth1: transmit
timed
I'm seeing the same problem, and it would make me sad if it couldn't be
resolved in time for the release of feisty...
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is
The update make some days ago make the network bug after a few minutes
rather than some hours
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://bugs.launchpad.net/bugs/87078
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: Ben Collins = Ubuntu Kernel Team
Status: Needs Info = Confirmed
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://launchpad.net/bugs/87078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
dmesg log after the bug:
[11919.567929] NETDEV WATCHDOG: eth1: transmit timed out
[11919.567936] eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=63.
[11919.967551] NETDEV WATCHDOG: eth1: transmit timed out
[11919.967560] eth1: Tx timed out, lost interrupt? TSR=0x3, ISR=0x3, t=88.
with irqpoll the computer freeze during the GNOME login
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://launchpad.net/bugs/87078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
Please attach full dmesg.
** Changed in: linux-source-2.6.20 (Ubuntu)
Assignee: (unassigned) = Ben Collins
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://launchpad.net/bugs/87078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
Can you add irqpoll to the kernel command line arguments and try to
reproduce it?
** Changed in: linux-source-2.6.20 (Ubuntu)
Importance: Undecided = Medium
Status: Unconfirmed = Needs Info
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://launchpad.net/bugs/87078
--
With linux 2.6.17 there is no problem
--
RTL-8029: NETDEV WATCHDOG: eth1: transmit timed out
https://launchpad.net/bugs/87078
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
34 matches
Mail list logo
