From owner-freebsd-current@FreeBSD.ORG  Wed Dec 29 13:53:38 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id C922E16A4CE; Wed, 29 Dec 2004 13:53:38 +0000 (GMT)
Received: from vbook.fbsd.ru (asplinux.ru [195.133.213.194])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 423A243D2F; Wed, 29 Dec 2004 13:53:38 +0000 (GMT)
	(envelope-from vova@vbook.fbsd.ru)
Received: from vova by vbook.fbsd.ru with local (Exim 4.43 (FreeBSD))
	id 1CjeGc-0001Hp-5h; Wed, 29 Dec 2004 16:53:34 +0300
From: Vladimir Grebenschikov <vova@fbsd.ru>
To: Dag-Erling =?ISO-8859-1?Q?Sm=F8rgrav?= <des@des.no>
In-Reply-To: <xzpwtv1te7n.fsf@dwp.des.no>
References: <xzpu0qa2pzi.fsf@dwp.des.no><xzpwtv1te7n.fsf@dwp.des.no>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Organization: SWsoft
Date: Wed, 29 Dec 2004 16:53:33 +0300
Message-Id: <1104328413.4852.1.camel@localhost>
Mime-Version: 1.0
X-Mailer: Evolution 2.0.0FreeBSD GNOME Team Port 
Sender: Vladimir Grebenschikov <vova@vbook.fbsd.ru>
cc: peadar@freebsd.org
cc: "current@freebsd.org" <current@freebsd.org>
Subject: Re: fxp EEPROM checksum mismatch in recent -CURRENT
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: vova@fbsd.ru
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 29 Dec 2004 13:53:38 -0000

=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