From owner-freebsd-current@FreeBSD.ORG Mon Oct 17 14:44:04 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 3C85416A41F for ; Mon, 17 Oct 2005 14:44:04 +0000 (GMT) (envelope-from dan@mail.neosystem.cz) Received: from gem.neosystem.cz (gem.neosystem.cz [81.95.103.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id B556F43D46 for ; Mon, 17 Oct 2005 14:44:03 +0000 (GMT) (envelope-from dan@mail.neosystem.cz) Received: from localhost (localhost [127.0.0.1]) by gem.neosystem.cz (Postfix) with ESMTP id 22D8338AF8F for ; Mon, 17 Oct 2005 16:44:06 +0200 (CEST) Received: from gem.neosystem.cz ([127.0.0.1]) by localhost (gem [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 08180-02 for ; Mon, 17 Oct 2005 16:44:04 +0200 (CEST) Received: from moon.kancelar.seznam.cz (proxy.seznam.cz [212.80.76.5]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gem.neosystem.cz (Postfix) with ESMTP id 4C62E38AF8D for ; Mon, 17 Oct 2005 16:44:04 +0200 (CEST) Date: Mon, 17 Oct 2005 16:40:04 +0200 From: Dan Bilik To: freebsd-current@freebsd.org Message-Id: <20051017164004.23126e63.dan@mail.neosystem.cz> In-Reply-To: <6.2.3.4.0.20051017065738.06d79048@64.7.153.2> References: <20051017114655.636eff01.dan@mail.neosystem.cz> <6.2.3.4.0.20051017065738.06d79048@64.7.153.2> Organization: neosystem.cz X-Mailer: Sylpheed version 2.0.2 (GTK+ 2.6.10; i386-portbld-freebsd6.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at neosystem.cz 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 14:44:04 -0000 On Mon, 17 Oct 2005 07:01:41 -0400 Mike Tancsa 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 > ... Well, it seems to be "lucky" day... One of our boxes stopped network communication (as described in previous post) just an hour ago. After power cycling it, dmesg says: ... fxp0: Disabling dynamic standby mode in EEPROM fxp0: New EEPROM ID: 0x48a0 fxp0: EEPROM checksum @ 0x3f: 0x356 -> 0x356 ... fxp1: Disabling dynamic standby mode in EEPROM fxp1: New EEPROM ID: 0x48a0 fxp1: EEPROM checksum @ 0x3f: 0x7259 -> 0x7259 Probably no advance here. Machine booted with apic(4) disabled - I prepared it that way after short mailing with Maxime Henrion. We'll see if that helped. So far there is significant performance drop because of SMP loss. Dan