From owner-freebsd-stable Tue Aug 28 8:32:51 2001 Delivered-To: freebsd-stable@freebsd.org Received: from hunkular.glarp.com (hunkular.glarp.com [199.117.25.251]) by hub.freebsd.org (Postfix) with ESMTP id 2DC1D37B408; Tue, 28 Aug 2001 08:32:38 -0700 (PDT) (envelope-from huntting@hunkular.glarp.com) Received: from hunkular.glarp.com (localhost [127.0.0.1]) by hunkular.glarp.com (8.11.3/8.11.3) with ESMTP id f7SFWM833600; Tue, 28 Aug 2001 09:32:22 -0600 (MDT) (envelope-from huntting@hunkular.glarp.com) Message-Id: <200108281532.f7SFWM833600@hunkular.glarp.com> To: Mike Tancsa Cc: tlambert2@mindspring.com, Jonathan Lemon , current@FreeBSD.ORG, stable@FreeBSD.ORG Subject: Re: fxp SCB timeout problems [FIX] In-Reply-To: Your message of "Tue, 28 Aug 2001 02:03:41 EDT." <5.1.0.14.0.20010828020210.032dc0b8@192.168.0.12> Date: Tue, 28 Aug 2001 09:32:22 -0600 From: Brad Huntting 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 > From my perspective, negative functionality is being lost. There is a > nice comment in the source code explaining what it is... > * Enable workarounds for certain chip revision deficiencies. > * > * Systems based on the ICH2/ICH2-M chip from Intel have a defect > * where the chip can cause a PCI protocol violation if it receives > * a CU_RESUME command when it is entering the IDLE state. The > * workaround is to disable Dynamic Standby Mode, so the chip never > * deasserts CLKRUN#, and always remains in an active state. > * > * See Intel 82801BA/82801BAM Specification Update, Errata #30. Will the card be able to function in suspend mode and do Wake-on-LAN correctly after this? brad To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message