Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
SDN 101: An Introduction to Software Defined Networking
Discover the advantages of SDN.
SDN has quickly become one of the hottest trends in IT. But not all SDN solutions offer real software-defined functionality. As more enterprises consider SDN, they want to know, “What is SDN? And what are the real benefits?” If you're ready to explore the advantages of SDN, and want to know how it should be implemented within your enterprise, start by reading our introductory white paper.
Click Here to receive this Complete Guide absolutely free.
This is a little old thread but I have exactly the same problem (happened after video card install) and don't know what to do. Tried recompiling kernel without any ACPI/APM features and network still keeps dying.
Tried append=pci-noacpi - nothing.
BTW what is the difference between ACPI and APCI and who of them is the bad guy here?
I'd like to join the club. I'm now getting this error as well, seemingly randomly on my Fedora7 webserver. From what I've read, it sounds likely that it may be due to having just upgraded my router to 10/100/1000.
Here's the log I'm seeing:
Sep 12 08:26:40 localhost kernel: NETDEV WATCHDOG: eth0: transmit timed out
Sep 12 08:26:40 localhost kernel: sky2 eth0: tx timeout
Sep 12 08:26:40 localhost kernel: sky2 eth0: disabling interface
Sep 12 08:26:40 localhost kernel: sky2 eth0: enabling interface
Sep 12 08:26:40 localhost kernel: sky2 eth0: ram buffer 0K
Sep 12 08:26:43 localhost kernel: sky2 eth0: Link is up at 1000 Mbps, full duplex, flow control both
This is my network card:
02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12)
Last edited by v2k; 09-12-2007 at 12:54 PM.
Reason: added network card
I finally solved (worked around) this (netdev watchdog timeout, eth0 kaput) problem (Fedora Rawhide, built-in network card 8139too, K8V800M motherboard) by appending noapic to the end of the kernel line in grub.conf
not "noapci" (whatever the heck that is)
Works for me, at least until somebody figures out a real solution.
It also stopped my video card from generating Xid errors. Seems IRQs are a bit tangled on this board.
i have the same problem.
i solved it by enabling "Onboard Lan Boot ROM" in the BIOS.
Integrated Peripherals -> Onboard Device -> Onboard Lan Boot ROM
my chip is realtek rtl8100c (onboard).
it works now.
the "Lan Boot ROM" can initialize the chip correctly but linux driver not, i guess.
it works all the time in windows no matter whether "Onboard Lan Boot ROM" is enabled or disabled.
will try doing this as i am facing the same issue over and over again,
the error that i am getting is with regard to the usb0.
thanks for the help. will keep posted on the same.
NETDEV WATCHDOG: usb0 (cdc_ether): transmit queue 0 timed out
Originally Posted by nemestrinus
I had this same problem, very mysterious. I would get the NETDEV WATCHDOG timeout error, seemingly at random times, and my network interface would stop working until I rebooted the whole machine. I partially disabled ACPI in the kernel (not APIC, these are two different things not a typo,) by entering the following line in my /etc/lilo.conf
append = "pci=noacpi"
Since then I have not (yet?) had a recurrence of the problem.