bug in via-rhine network-driver (transmit timed out)
Hi,
I successfully got the old transmit-out-error again ;-)
- and this time with "options via-rhine debug=3" in modules.conf. So here are the debug-messages:
dmesg:
eth0: Shutting down ethercard, status was 081a.
eth0: via_rhine_open() irq 9.
eth0: reset finished after 5 microseconds.
eth0: Done via_rhine_open(), status 081a MII status: 7809.
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Shutting down ethercard, status was 883a.
eth0: via_rhine_open() irq 9.
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Done via_rhine_open(), status 881a MII status: 782d.
eth0: no IPv6 routers present
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0000, PHY status 782d, resetting...
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Shutting down ethercard, status was 883a.
eth0: via_rhine_open() irq 9.
eth0: reset did not complete in 10 ms.
eth0: reset finished after 10005 microseconds.
eth0: Done via_rhine_open(), status 881a MII status: 7829.
eth0: Shutting down ethercard, status was 883a.
lsmod was:
via-rhine 13612 2
mii 1232 0 [via-rhine]
Signature · 2 lines
Bye. Kristof <[email protected]>
Quoted 4 lines · On Mon, Dec 09, 2002 at 05:54:07PM +0100, [email protected] wrote:
Hi,
I successfully got the old transmit-out-error again ;-)
- and this time with "options via-rhine debug=3" in modules.conf.
Does booting with "noapic" in lilo/grub fix this?
Hi,
Quoted 3 lines
Quoted 3 lines
I successfully got the old transmit-out-error again ;-)
- and this time with "options via-rhine debug=3" in modules.conf.
JG> Does booting with "noapic" in lilo/grub fix this? Yes, it did - as I mentioned in my previous postings ;) ..this was just a debug-report for source-bugfixing.
--
Bye.
Kristof <[email protected]>
Adaptec 2940 not working on 2.5.50
after watching from the sidelines for a while I finally had some time to try the 2.5 kernels over the weekend.
unfortunantly I was unable to build a kernel that will work for me.
the system is a K6-3 400 with several IDE drives and a SCSI drive hooked to an adaptec 2940. LILO and the boot kernels are on IDE, but the linux root filesystem is on the SCSI drive
I compile the kernel without a problem, but when it boots it generates several screens of errors as it attempts to initialize the SCSI buss. unfortunantly I don't have a serial console on that box so I haven't been able to capture the messages (I can't capture dmesg becouse the system never finds the drive and so can't complete the boot)
I have verbose errors turned on, and have attempted both the old and the new drivers with the same results.
this system ran 2.4.0 up until about two months ago when I upgraded to 2.4.18 and has had no problems.
a quick google search has not found any posts about this, although 2.5.50-ac1 has a fix for this driver (doesn't sound like quite the same problem though)
suggestions? additional info required?
David Lang