On Sat, Jun 25, 2005 at 08:41:38PM -0700, Stephen Jones wrote:
> I've submitted a bug report in hopes that we can get this fixed. Is
> anyone currently looking on this? What changed from 1.6.2 to 2.0.2
> that would cause the race condition that produces this symptom?
> Should I hire a NetBSD developer to fix this since Alpha is consider
> a tier 2 platform now? This probably isn't going to be a driver fix
> as the driver seems to be the same code as in 1.6.2.

Hmm, I'm not familiar with that... I've been running an fxp on my
AlphaPC 164 for years and haven't noticed any problems. Is this
problem something new to 2.0.2, but not in 2.0?

NetBSD 2.0 (YERFABLE) #214: Sun Dec 12 07:15:04 CST 2004
        khym@yerfable.azeotrope.org:/usr2/obj.alpha/sys/arch/alpha/compile/YERFABLE
Digital AlphaPC 164 500 MHz, s/n
[ ... ]
fxp0 at pci0 dev 5 function 0: Intel i82557 Ethernet, rev 1
fxp0: interrupting at eb164 irq 2
fxp0: Ethernet address 00:a0:c9:13:61:7e
nsphy0 at fxp0 phy 1: DP83840 10/100 media interface, rev. 0
nsphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
-- 
Name: Dave Huang         |  Mammal, mammal / their names are called /
INet: khym@azeotrope.org |  they raise a paw / the bat, the cat /
FurryMUCK: Dahan         |  dolphin and dog / koala bear and hog -- TMBG
Dahan: Hani G Y+C 29 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++