Subject: rtk0: watchdog timeout in amd64 4.99.17
To: None <current-users@netbsd.org>
From: Marc Tooley <netbsdMLpostNO@spam.quake.ca>
List: current-users
Date: 04/18/2007 12:23:06
Somewhere between netbsd-3 and -current as of 4.99.17 my realtek chipset
managed to break itself in GENERIC.MP. I haven't begun rebuilding
kernels yet to locate the breakage to see whether Izumi Tsutsui's
changes are the problem or whether there are some kind of ACPI problems
going on. However, here're some relevant details:
NetBSD 4.99.17 (GENERIC.MP) #0: Sat Apr 14 19:38:59 PDT 2007
[...]
rtk0 at pci1 dev 6 function 0: Realtek 8139 10/100BaseTX (rev. 0x10)
APC1: Picked IRQ 16 with weight 0
rtk0: interrupting at ioapic0 pin 16 (irq 11)
rtk0: Ethernet address 00:0e:2e:82:58:44
rlphy0 at rtk0 phy 7: Realtek internal PHY
rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
Issuing the command:
ifconfig rtk0 media 100baseTX ; ifconfig rtk0 mediaopt full-duplex
... since I'm running a cross-over cable to an nfe0-based NetBSD on the
other end, the above is necessary because right now I can't get nfe0 to
work in anything *but* a specific 100baseTX, full-duplex mode. Back
when that amd64 machine was netbsd-3, the above would work just fine.
Now when I do it I get:
rtk0: watchdog timeout
rtk0: watchdog timeout
rtk0: watchdog timeout
If I set it back to autoselect I get 18KB/sec and less when traferring
files.
Comments appreciated. Is there a quick fix for this? A new kernel or
kernel option maybe?
-Marc
P.S. Please use the Reply-To: and reply to the list. Thanks.