Re: fxp SCB timeout problems [FIX]

2001-08-28 Thread Jonathan Lemon

On Tue, Aug 28, 2001 at 09:32:22AM -0600, Brad Huntting wrote:
> 
> > 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?

It should still do wake-on-lan, although the fxp driver doesn't support
that right now - it doesn't appear to be a useful feature.

Powersave transitions (D0 -> D3) should also still work.  What the fix
does is prevent the board from reducing power in idle state, which is
a subset of D0.  (Intel has D0-active and D0-idle, or some such).
-- 
Jonathan

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fxp SCB timeout problems [FIX]

2001-08-28 Thread Brad Huntting


> 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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fxp SCB timeout problems [FIX]

2001-08-28 Thread Terry Lambert

Mike Tancsa wrote:
> > 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...

[ ... actual chipset bug ... ]

Ah, thanks!  I think I'll drag this into my local 4.3 based
source tree, when I get some time.

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fxp SCB timeout problems [FIX]

2001-08-27 Thread Mike Tancsa

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 [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fxp SCB timeout problems [FIX]

2001-08-27 Thread Terry Lambert

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 exactly is "Dynamic Standby Mode"?  What's being lost
here, when it is disabled, instead of being handled as the
card manufacturer expects the OS to handle it?

-- Terry

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fxp SCB timeout problems [FIX]

2001-08-27 Thread Mike Tancsa


Its looking great so far! In the two production machines I put it in last 
night, zero time outs as expected!! These are both EM machines.  On my two 
internal ET machines, also zero problems.  The machines are in 10BaseT/UTP, 
and 10BaseT full duplex.

inphy0:  on miibus1
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

and

fxp0:  port 0xdf00-0xdf3f mem 0xff6ff000-0xff6f 
irq 11 at device 8.0 on pci1
fxp0: Ethernet address 00:03:47:6f:f7:e0
inphy0:  on miibus0
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

Thank you *VERY* much for fixing this problem.

 ---Mike


At 01:43 PM 8/26/01 -0400, Mike Tancsa wrote:

>I have it on two machines with this chipset and it looks good so 
>far.  After installing, dmesg shows
>
>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 ***
>fxp0: Ethernet address 00:01:80:02:d0:34
>inphy0:  on miibus1
>inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>
>
>and then one more reboot shows
>
>fxp0:  port 0xc400-0xc43f mem 
>0xd5001000-0xd5001fff irq 11 at device 8.0 on pci1
>fxp0: Ethernet address 00:01:80:02:d0:34
>inphy0:  on miibus1
>inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
>
> ---Mike
>
>
>
>At 10:11 AM 8/26/2001 -0500, Jonathan Lemon wrote:
>>   I believe that I have a real fix for the SCB timeout problems
>>that have been plauging users of recent Intel fxp boards.
>>
>>   If you have a board that uses the Intel ICH2/ICH2-M chipset
>>(usually 815E style boards) and feel comfortable applying
>>patches to the system, please contact me to test a fix.
>>
>>   The patch works on two different boards here, but I would like
>>to get some wider testing before I commit it to the tree.
>>--
>>Jonathan
>>
>>To Unsubscribe: send mail to [EMAIL PROTECTED]
>>with "unsubscribe freebsd-stable" in the body of the message
>
>
>Mike Tancsa,  tel +1 519 651 3400
>Network Administration,   [EMAIL PROTECTED]
>Sentex Communications www.sentex.net
>Cambridge, Ontario Canada www.sentex.net/mike
>
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-stable" in the body of the message


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



Re: fxp SCB timeout problems [FIX]

2001-08-26 Thread Mike Tancsa


I have it on two machines with this chipset and it looks good so 
far.  After installing, dmesg shows

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 ***
fxp0: Ethernet address 00:01:80:02:d0:34
inphy0:  on miibus1
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto


and then one more reboot shows

fxp0:  port 0xc400-0xc43f mem 0xd5001000-0xd5001fff 
irq 11 at device 8.0 on pci1
fxp0: Ethernet address 00:01:80:02:d0:34
inphy0:  on miibus1
inphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto

 ---Mike



At 10:11 AM 8/26/2001 -0500, Jonathan Lemon wrote:
>   I believe that I have a real fix for the SCB timeout problems
>that have been plauging users of recent Intel fxp boards.
>
>   If you have a board that uses the Intel ICH2/ICH2-M chipset
>(usually 815E style boards) and feel comfortable applying
>patches to the system, please contact me to test a fix.
>
>   The patch works on two different boards here, but I would like
>to get some wider testing before I commit it to the tree.
>--
>Jonathan
>
>To Unsubscribe: send mail to [EMAIL PROTECTED]
>with "unsubscribe freebsd-stable" in the body of the message


Mike Tancsa,  tel +1 519 651 3400
Network Administration,   [EMAIL PROTECTED]
Sentex Communications www.sentex.net
Cambridge, Ontario Canada www.sentex.net/mike


To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message



fxp SCB timeout problems [FIX]

2001-08-26 Thread Jonathan Lemon

  I believe that I have a real fix for the SCB timeout problems
that have been plauging users of recent Intel fxp boards.

  If you have a board that uses the Intel ICH2/ICH2-M chipset
(usually 815E style boards) and feel comfortable applying 
patches to the system, please contact me to test a fix.

  The patch works on two different boards here, but I would like
to get some wider testing before I commit it to the tree.
-- 
Jonathan

To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message