From owner-freebsd-current Mon Aug 27 23: 3:54 2001 Delivered-To: freebsd-current@freebsd.org Received: from cage.simianscience.com (cage.simianscience.com [64.7.134.1]) by hub.freebsd.org (Postfix) with ESMTP id 0569337B401; Mon, 27 Aug 2001 23:03:48 -0700 (PDT) (envelope-from mike@sentex.net) Received: (from root@localhost) by cage.simianscience.com (8.11.6/8.11.5) id f7S63lg20308; Tue, 28 Aug 2001 02:03:47 -0400 (EDT) (envelope-from mike@sentex.net) Received: from chimp.sentex.net (fcage [192.168.0.2]) by cage.simianscience.com (8.11.6/8.11.5av) with ESMTP id f7S63g920299; Tue, 28 Aug 2001 02:03:42 -0400 (EDT) (envelope-from mike@sentex.net) Message-Id: <5.1.0.14.0.20010828020210.032dc0b8@192.168.0.12> X-Sender: mdtancsa@192.168.0.12 X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Tue, 28 Aug 2001 02:03:41 -0400 To: tlambert2@mindspring.com From: Mike Tancsa Subject: Re: fxp SCB timeout problems [FIX] Cc: Jonathan Lemon , current@freebsd.org, stable@freebsd.org In-Reply-To: <3B8B3183.708F007C@mindspring.com> References: <20010826101102.A96709@prism.flugsvamp.com> <5.1.0.14.0.20010827102227.0574d240@marble.sentex.ca> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Virus-Scanned: by AMaViS perl-10 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG At 10:52 PM 8/27/2001 -0700, Terry Lambert wrote: >Mike Tancsa wrote: > > >fxp0: port 0xc400-0xc43f mem > > >0xd5001000-0xd5001fff irq 11 at device 8.0 on pci1 > > >fxp0: *** DISABLING DYNAMIC STANDBY MODE IN EEPROM *** > > >fxp0: New EEPROM ID: 0x49a0 > > >fxp0: EEPROM checksum @ 0xff: 0xe441 -> 0xe443 > > >fxp0: *** PLEASE REBOOT THE SYSTEM NOW FOR CORRECT OPERATION *** > > What's being lost >here, when it is disabled, instead of being handled as the >card manufacturer expects the OS to handle it? 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message