Date: Tue, 26 Oct 2004 10:58:45 +0400 From: Vladimir Grebenschikov <vova@fbsd.ru> To: "M. Warner Losh" <imp@bsdimp.com> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: fxp does not work after upgrade to latest current Message-ID: <1098773925.1071.9.camel@localhost> In-Reply-To: <20041025.212820.60925870.imp@bsdimp.com> References: <1098564131.1064.3.camel@localhost> <20041025.212820.60925870.imp@bsdimp.com>
next in thread | previous in thread | raw e-mail | index | archive | help
=F7 =D0=CE, 25/10/2004 =D7 21:28 -0600, M. Warner Losh =D0=C9=DB=C5=D4: > In message: <1098564131.1064.3.camel@localhost> > Vladimir Grebenschikov <vova@fbsd.ru> writes: > : fxp0: DMA timeout > : fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > : fxp0: SCB timeout: 0xff 0xff 0xff 0xffff > :=20 > : any clues ? > :=20 > : With about week-old kernel all is ok. >=20 > Uggg. Maybe this is due to the address that is assigned to it. I'm > having horrible luck with your machine, no? Not sure, I think some development glitches is normal living on - CURRENT. Playing with problem I have found that week-day old kernel report same problem and them problem disappear. Actually I can't reproduce problem now. Nothing was changed but problem disappear. I have only one guess about problems reason: At day when it happens I have installed fresh winXP pro, it even does not install driver for fxp (as for many other hardware, fbsd has better hw support out of the box :-) And probably (I think not, but not sure) it was warm reboot after this winXP. After some play with this winXP I've rolled back to native notebook's winXP home with all drivers, and see problem after that only once. I know, this scenario sounds strange but I have no better guess why it happens. > Warner --=20 Vladimir B. Grebenchikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1098773925.1071.9.camel>