From owner-freebsd-current@FreeBSD.ORG Wed Dec 29 13:40:51 2004 Return-Path: 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 80F7516A4CE; Wed, 29 Dec 2004 13:40:51 +0000 (GMT) Received: from smtp.des.no (flood.des.no [217.116.83.31]) by mx1.FreeBSD.org (Postfix) with ESMTP id 0737F43D1D; Wed, 29 Dec 2004 13:40:51 +0000 (GMT) (envelope-from des@des.no) Received: by smtp.des.no (Pony Express, from userid 666) id C2890530C; Wed, 29 Dec 2004 14:40:49 +0100 (CET) Received: from dwp.des.no (des.no [80.203.228.37]) by smtp.des.no (Pony Express) with ESMTP id A580E5308; Wed, 29 Dec 2004 14:40:28 +0100 (CET) Received: by dwp.des.no (Postfix, from userid 2602) id 25BD1B874; Wed, 29 Dec 2004 14:40:28 +0100 (CET) To: peadar@freebsd.org References: <34cb7c840412290444497d2dd7@mail.gmail.com> From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) Date: Wed, 29 Dec 2004 14:40:28 +0100 In-Reply-To: <34cb7c840412290444497d2dd7@mail.gmail.com> (Peter Edwards's message of "Wed, 29 Dec 2004 12:44:33 +0000") Message-ID: User-Agent: Gnus/5.110002 (No Gnus v0.2) Emacs/21.3 (berkeley-unix) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on flood.des.no X-Spam-Level: X-Spam-Status: No, score=0.1 required=5.0 tests=AWL,FORGED_RCVD_HELO autolearn=disabled version=3.0.1 cc: "Li-Lun Wang \(Leland Wang\)" cc: 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 List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Dec 2004 13:40:51 -0000 Peter Edwards 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. 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. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no