ed0 and xl0 watchdog/timeout errors

[Kevin Kinsey]

M. Parsons wrote:
>> From /var/log/messages:
> 
> Jun 19 10:43:35 freebsd kernel: ed0: device timeout
> Jun 19 10:43:39 freebsd last message repeated 2 times
> Jun 19 10:43:41 freebsd kernel: xl0: watchdog timeout
> Jun 19 10:43:41 freebsd kernel: ed0: device timeout
> Jun 19 10:43:41 freebsd kernel: xl0: link state changed to DOWN
> Jun 19 10:43:43 freebsd kernel: ed0: device timeout
> Jun 19 10:43:43 freebsd kernel: xl0: link state changed to UP
> Jun 19 10:43:45 freebsd kernel: ed0: device timeout
> Jun 19 10:43:48 freebsd kernel: xl0: watchdog timeout
> Jun 19 10:43:48 freebsd kernel: ed0: device timeout
> Jun 19 10:43:48 freebsd kernel: xl0: link state changed to DOWN
> 
> dmesg says: (minus the mac addys which Ive removed)
> 
> xl0: <3Com 3c905B-TX Fast Etherlink XL> port 0xec80-0xecff mem
> 0xfebfff80-0xfebfffff irq 11 at device 11.0 on pci0
> miibus0: <MII bus> on xl0
> 
> ed0: <RealTek 8029> port 0xef40-0xef5f irq 10 at device 12.0 on pci0
> ed0: type RTL8029 (16 bit)
> 
> 
> ed0 is PCI card connected to a pppoe isp
> 
> xl0 is PCI connected to another computer via crossover/natted
> 
> The above happens if I use max upstream (60 KiloBytes/sec) on the pppoe
> connection for a long amount of time (>6 hours).  Otherwise, everything
> works fine.
> 
> Rebooting the machine is the only solution.  Killing pppd and restarting
> does not obtain an ip from the isp.  And restarting xl0 also does not bring
> back the lan connection.
> 
> 6.0-Release is the version Im using.
> 
> Any ideas?  Besides not using any upstream. :)

IANAE, but maybe the answer is to update?  6.0-RELEASE is pretty much
officially *old*, ;-) and it's quite likely that the devices will
work better with the newer driver code.  IIRC, there were lots
of messages with such issues "back in the day", and I don't
see as many anymore --- this one notwithstanding, of course.

Otherwise, I've no clue.

HTH,

Kevin Kinsey

-- 
Q:	What is orange and goes click, click?
A:	A ball point carrot.