From owner-freebsd-current@FreeBSD.ORG  Tue Dec 28 01:27:07 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 572C116A4CE
	for <freebsd-current@freebsd.org>;
	Tue, 28 Dec 2004 01:27:07 +0000 (GMT)
Received: from infor.ck.tp.edu.tw (infor.ck.tp.edu.tw [203.64.26.200])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 1543743D49
	for <freebsd-current@freebsd.org>;
	Tue, 28 Dec 2004 01:27:07 +0000 (GMT)
	(envelope-from llwang@infor.ck.tp.edu.tw)
Received: by infor.ck.tp.edu.tw (Postfix, from userid 1001)
	id 4AE612DA780; Tue, 28 Dec 2004 09:27:05 +0800 (CST)
Date: Tue, 28 Dec 2004 09:27:05 +0800
From: "Li-Lun Wang (Leland Wang)" <llwang@infor.org>
To: freebsd-current@freebsd.org
Message-ID: <20041228012705.GA89824@Athena.infor.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii; x-action=pgp-signed
Content-Disposition: inline
User-Agent: Mutt/1.5.6i
X-Mailman-Approved-At: Tue, 28 Dec 2004 13:34:32 +0000
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
	<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: Tue, 28 Dec 2004 01:27:07 -0000

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi,

I have been having a similar problem for quite a while on 5.3 on my X31.
I am not sure about 5.2.1. If if_fxp is compiled into the kernel or if
the first module I load after I boot is if_fxp.ko, there is no problem.
If I enter X window (and thus load radeon.ko) before I load if_fxp.ko, I
always have the mismatch. Sometimes the problem goes away when I reload
the kernel module, and sometimes I have to reboot the system in order to
attach my fxp. I am quite sure I had not had the problem sometime
earlier on 5.2.

- -- Leland Wang
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (FreeBSD)

iD8DBQFB0LZmCQM7t5B2mhARAkp/AJ427NA2vhn86fmoMlnR8GrqWSVOagCZARvd
Jhr4/UtGzk9SHnTwgruKpcU=
=izkU
-----END PGP SIGNATURE-----