From owner-freebsd-current@FreeBSD.ORG Mon Oct 17 11:01:34 2005 Return-Path: X-Original-To: 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 2EC9216A41F for ; Mon, 17 Oct 2005 11:01:34 +0000 (GMT) (envelope-from mike@sentex.net) Received: from smarthost1.sentex.ca (smarthost1.sentex.ca [64.7.153.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id E6CF243D58 for ; Mon, 17 Oct 2005 11:01:32 +0000 (GMT) (envelope-from mike@sentex.net) Received: from pumice3.sentex.ca (pumice3.sentex.ca [64.7.153.26]) by smarthost1.sentex.ca (8.13.3/8.13.3) with ESMTP id j9HB1WXm055121 for ; Mon, 17 Oct 2005 07:01:32 -0400 (EDT) (envelope-from mike@sentex.net) Received: from lava.sentex.ca (pyroxene.sentex.ca [199.212.134.18]) by pumice3.sentex.ca (8.13.4/8.13.4) with ESMTP id j9HB1Vw7071145; Mon, 17 Oct 2005 07:01:31 -0400 (EDT) (envelope-from mike@sentex.net) Received: from simian.sentex.net (simeon.sentex.ca [192.168.43.27]) by lava.sentex.ca (8.13.3/8.13.3) with ESMTP id j9HB1Th9011191 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Mon, 17 Oct 2005 07:01:29 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <6.2.3.4.0.20051017065738.06d79048@64.7.153.2> X-Mailer: QUALCOMM Windows Eudora Version 6.2.3.4 Date: Mon, 17 Oct 2005 07:01:41 -0400 To: Dan Bilik , freebsd-current@freebsd.org From: Mike Tancsa In-Reply-To: <20051017114655.636eff01.dan@mail.neosystem.cz> References: <20051017114655.636eff01.dan@mail.neosystem.cz> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by amavisd-new X-Scanned-By: MIMEDefang 2.51 on 64.7.153.18 X-Scanned-By: MIMEDefang 2.53 on 64.7.153.26 Cc: Subject: Re: Possible fxp(4) problem in -CURRENT X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Mon, 17 Oct 2005 11:01:34 -0000 At 05:46 AM 17/10/2005, Dan Bilik wrote: >through it. It seems to be the same problem as described in PR >amd64/82425 with one exception - there is no 'device timeout' in logs. Its been a long time since I have seen fxp0: Disabling dynamic standby mode in EEPROM fxp0: New EEPROM ID: 0x48a0 fxp0: EEPROM checksum @ 0x3f: 0xf0f7 -> 0xf0f7 But, I seem to recall that when the driver detects this bug in the fxp card, you need to power cycle the box. But after that, you should never see the message again. On my old (i810) boards, I think I would only see this problem in 10baseT mode, and 100 would not be an issue (or perhaps the other way around, but its been a long time and I dont recall exactly). Not sure if thats your issue or not, or if the driver is incorrectly seeing that bug in your rev of the fxp. If thats the case, perhaps work around it by modifying the code to not try and program the phy like it is. ---Mike