From owner-freebsd-stable Mon Nov 5 12:11:15 2001 Delivered-To: freebsd-stable@freebsd.org Received: from prism.flugsvamp.com (cb58709-a.mdsn1.wi.home.com [24.17.241.9]) by hub.freebsd.org (Postfix) with ESMTP id 9948037B416 for ; Mon, 5 Nov 2001 12:11:09 -0800 (PST) Received: (from jlemon@localhost) by prism.flugsvamp.com (8.11.0/8.11.0) id fA5K8Ax49247; Mon, 5 Nov 2001 14:08:10 -0600 (CST) (envelope-from jlemon) Date: Mon, 5 Nov 2001 14:08:10 -0600 (CST) From: Jonathan Lemon Message-Id: <200111052008.fA5K8Ax49247@prism.flugsvamp.com> To: Robin_Blanchard@gactr.uga.edu, stable@freebsd.org Subject: Re: fxp0: DYNAMIC STANDBY MODE ?? - me too ! X-Newsgroups: local.mail.freebsd-stable In-Reply-To: References: Organization: Cc: Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG In article you write: >i just updated my stock Dell poweredge 1550 this morning: > FreeBSD 4.4-STABLE #0: Mon Nov 5 10:52:07 EST 2001 > >and get the same messages (on both internal fxp interfaces). >and, likewise, the box seems to run fine regardless. >??? > > >> fxp0: port 0x2400-0x243f mem >> 0xc4e00000-0xc4efffff,0xc4fff000-0xc4ffffff irq 10 at device 2.0 on pci0 >> fxp0: *** DISABLING DYNAMIC STANDBY MODE IN EEPROM *** >> fxp0: New EEPROM ID: 0x40a0 >> fxp0: EEPROM checksum @ 0xff: 0x5716 -> 0x5716 >> fxp0: *** PLEASE REBOOT THE SYSTEM NOW FOR CORRECT OPERATION *** Intel has a defect in their embedded 82559 controller on 815-class motherboards where the chip may violate the PCI timing specifications, causing a system lockup. The workaround is to toggle a bit in the EEPROM to avoid this (which also involves re-writing the eeprom checksum). This fix is in 4.4-RELEASE. However, this defect has *also* been reported on newer, non-815 boards as well, and the same workaround has resolved the problem. So I changed the logic to always disable standby mode on newer 82559 (and upwards) boards. Now, for boards that were working fine with the dynamic standby mode (read: automatic low power consumption), prior to this fix, this change should effectively be a NOP, and you can ignore the warning. Ideally, this should be a one time occurrence: we change the eeprom, update the checksum, and are done. If you see this warning more than once, then it indicates that something else (perhaps the system BIOS) is resetting the EEPROM back to a different value on startup. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message