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? |
Worked for me on a Toshiba Satellite A105-S2071. Thanks.
|
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! |
Hya,
Does anybody know if the following thread is related? http://www.linuxquestions.org/questi...d.php?t=579842 Happy Penguins! |
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 02:00.0 Ethernet controller: Marvell Technology Group Ltd. 88E8056 PCI-E Gigabit Ethernet Controller (rev 12) Any suggestions? |
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. :( |
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. |
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. |
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 |
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. |
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..:Pengy: Quote:
|
All times are GMT -5. The time now is 09:05 AM. |