Date: Mon, 31 Jan 2000 13:09:48 +1300 From: Wayne Knowles <w.knowles@niwa.cri.nz> To: itojun@iijlab.net Cc: current@FreeBSD.ORG, Yoshinobu Inoue <shin@nd.net.fujitsu.co.jp>, Alex Zepeda <jazepeda@pacbell.net>, Mattias Pantzare <pantzer@ludd.luth.se> Subject: Re: INET6 and fxp Message-ID: <3894D2CC.69CDDDD4@niwa.cri.nz> References: <20615.949212875@coconut.itojun.org>
next in thread | previous in thread | raw e-mail | index | archive | help
itojun@iijlab.net wrote: > >FWIW this doesn't happen with my card: > > > >fxp0: <Intel InBusiness 10/100 Ethernet> port 0x1000-0x103f mem 0xf4000000-0xf40 > >fffff,0xf4100000-0xf4100fff irq 10 at device 15.0 on pci0 > >fxp0: Ethernet address 00:90:27:d1:83:6a > >fxp0: supplying EUI64: 00:90:27:ff:fe:d1:83:6a > >fxp0: starting DAD for fe80:0001::0290:27ff:fed1:836a > >fxp0: DAD complete for fe80:0001::0290:27ff:fed1:836a - no duplicates found > > > > > >'course I don't actually use the card for internet access, just a local > >lan and the occasional IPv6 testing. > > (from what I've heard) the symptom highly depends on chip revision > so you are lucky. > > itojun The problem only occurs on faster machines. For me it didn't work in a PII 400MHz machine but moving the offending card to a P133 machine made it work again. The addition of the DELAY() fixes the problem. The problem stems from the fact that the driver init routine is called twice in quick succession - once for IPv4 and again for IPv6. The other way of fixing it is to disable the call to ifp->if_ioctl in netinet6/in6_ifattach.c Wayne -- _____ Wayne Knowles, Systems Manager / o \/ National Institute of Water & Atmospheric Research Ltd \/ v /\ P.O. Box 14-901 Kilbirnie, Wellington, NEW ZEALAND `---' Email: w.knowles@niwa.cri.nz To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3894D2CC.69CDDDD4>