Re: dc(4) problems

[M. Warner Losh]

Andy,
I'm aware of this problem and have it on my list of things to
try to get fixed for 5.0.

Warner

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message

dc(4) problems

[Andy Farkas]

I have a Macronix 98715A network adpater that works on RELEASE-4.6-p2 but
not under very recent 5.0-CURRENT (same box).

Under -current the ethernet address is set to 00:00:00:00:00:00 and a
warning about sleeping with a lock set is emmitted.

dmesgs:


FreeBSD RELEASE-4.6-p2 #0: Sun Jul 14 22:29:30 GMT 2002
...
dc0:  port 0xe800-0xe8ff mem 0xf3fff000-0xf3fff0ff 
irq 10 at device 7.0 on pci0
dc0: Ethernet address: 00:00:e8:89:ba:90
miibus0:  on dc0
dcphy0:  on miibus0
dcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
...


FreeBSD 5.0-CURRENT #0: Tue Nov 26 03:09:21 EST 2002
...
dc0:  port 0xe800-0xe8ff mem 0xf3fff000-0xf3fff0ff 
irq 10 at device 7.0 on pci0
dc0: Ethernet address: 00:00:00:00:00:00
miibus0:  on dc0
dcphy0:  on miibus0
dcphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
/usr/src/sys/vm/uma_core.c:1330: could sleep with "dc0" locked from 
/usr/src/sys/pci/if_dc.c:1974
...



To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message