Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
06-20-2007, 10:33 AM
|
#16
|
Member
Registered: Sep 2003
Location: Bulgaria
Distribution: Ubuntu 9.10, FreeBSD 7.2
Posts: 459
Rep:
|
Heya, penguins.
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?
|
|
|
07-05-2007, 06:07 PM
|
#17
|
Member
Registered: Sep 2005
Location: Baltimore, MD, USA
Distribution: Fedora, Gentoo, Debian, Slackware, IRIX, OS X
Posts: 192
Rep:
|
Worked for me on a Toshiba Satellite A105-S2071. Thanks.
|
|
|
08-23-2007, 03:56 PM
|
#18
|
Senior Member
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: SlackWare > Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy .. bullseye bookworm
Posts: 1,849
Original Poster
Rep: 
|
Hya,
I am not sure, however, my penguin lives stable than used to be with
append="apic=debug"
I just wanted to see if any useful message shows up.
Maybe very slight change in timing or so.
Try at your risk.
Happy Penguins!
|
|
|
09-04-2007, 09:13 AM
|
#19
|
Senior Member
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: SlackWare > Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy .. bullseye bookworm
Posts: 1,849
Original Poster
Rep: 
|
Hya,
Does anybody know if the following thread is related?
http://www.linuxquestions.org/questi...d.php?t=579842
Happy Penguins!
|
|
|
09-12-2007, 12:52 PM
|
#20
|
LQ Newbie
Registered: Aug 2007
Posts: 9
Rep:
|
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:
Code:
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)
Any suggestions?
Last edited by v2k; 09-12-2007 at 12:54 PM.
Reason: added network card
|
|
|
09-24-2007, 09:06 AM
|
#21
|
Senior Member
Registered: Apr 2005
Location: Penguin land, with apple, no gates
Distribution: SlackWare > Debian testing woody(32) sarge etch lenny squeeze(+64) wheezy .. bullseye bookworm
Posts: 1,849
Original Poster
Rep: 
|
Hya,
I tried 2.6.21 and 2.6.22. It looks better, although I have not used extensively yet. I will update.
Happy Penguins!
Edit:
It is more stable, but it happens also. 
Last edited by kaz2100; 09-24-2007 at 07:25 PM.
Reason: update
|
|
|
10-03-2007, 04:12 AM
|
#22
|
Member
Registered: Aug 2006
Posts: 147
Rep:
|
boo
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 "noacpi"
not "noapci" (whatever the heck that is)
noapic
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.
Last edited by fozner; 10-15-2007 at 03:09 AM.
|
|
|
12-07-2007, 05:51 AM
|
#23
|
LQ Newbie
Registered: Nov 2007
Distribution: debian
Posts: 1
Rep:
|
hi,all
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.
|
|
|
11-04-2008, 05:34 AM
|
#24
|
LQ Newbie
Registered: Nov 2006
Posts: 5
Rep:
|
I had the same problem, my solution was loading yenta_socket with option "disable_clkrun". Now everything works like a charm.
Kernel 2.6.27.2 Slackware 12.1
|
|
|
12-03-2010, 08:37 AM
|
#25
|
LQ Newbie
Registered: Dec 2010
Posts: 13
Rep:
|
Another solution - LOW TECH
I suffered the same problem with realtek rtl card.
Had an intuition to simply move the card to another and never been used PCI slot.
Did the job.
Regards,
Amit.
|
|
|
05-24-2013, 09:14 AM
|
#26
|
LQ Newbie
Registered: May 2013
Location: Pune
Distribution: Ubuntu
Posts: 7
Rep: 
|
Hi,
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
regards
Subhajit..
Quote:
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.
|
|
|
|
All times are GMT -5. The time now is 01:28 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|