Date: Wed, 29 Dec 2004 16:53:33 +0300 From: Vladimir Grebenschikov <vova@fbsd.ru> To: Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= <des@des.no> Cc: "current@freebsd.org" <current@freebsd.org> Subject: Re: fxp EEPROM checksum mismatch in recent -CURRENT Message-ID: <1104328413.4852.1.camel@localhost> In-Reply-To: <xzpwtv1te7n.fsf@dwp.des.no> References: <xzpu0qa2pzi.fsf@dwp.des.no><xzpwtv1te7n.fsf@dwp.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
=D0=92 =D1=81=D1=80, 29/12/2004 =D0=B2 14:40 +0100, Dag-Erling Sm=C3=B8rgra= v =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > Peter Edwards <peadar.edwards@gmail.com> writes: > > Tracing further, it looks like on waking up from D3 into D0, the fxp > > device needs some time to settle, or the config write to restore the > > BAR doesn't "take". That explains why it works if it's dragged in from > > the loader: the device probes without ever going to sleep. >=20 > That explains why the problem disappeared when I compiled fxp into the > kernel. Great detective work! I'll test your patch and let you know > if it works for me. Good research ! I have seen this bug twice, and both times it disappears after some days and influenced by previous loaded OS, module reload and etc.=20 > DES --=20 Vladimir B. Grebenchikov vova@fbsd.ru
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1104328413.4852.1.camel>