On Wed, Apr 9, 2008 at 6:36 PM, Andy Dills <[EMAIL PROTECTED]> wrote:
> On Wed, 9 Apr 2008, Chris Buechler wrote:
>
>  > Andy Dills wrote:
>  > > Good news, it appears my assumption was correct. There exists a flaw in
>  > > the realtek chipset (as quoted earlier in the thread), and it appears 
> that a
>  > > patch to the driver has been created:
>  > >
>  > > http://www.nabble.com/RELENG_7-panic-td16285669.html
>  > >
>  >
>  > that is good news. Do you know if this patch is in RELENG_7_0, and was it 
> back
>  > ported to RELENG_6_3? I know it has some updated drivers from the 6.2 we 
> use.
>  > The pfSense 1.2.1 release will be coming next month, and will be based on
>  > FreeBSD 6.3, so that might work out for you. The initial 7.0-based release
>  > will come first, but might not be something you want to use in production
>  > (though some of us developers are with no problems).
>
>  The patch just came out, but I would be very surprised if such a small
>  patch that fixes a frequent kernal panic in a common NIC didn't get
>  MFC'ed.

This is on HEAD, so I imagine it means MFC to RELENG_7, not sure if
there's a plan for RELENG_6

yongari     2008-04-10 01:06:05 UTC

 FreeBSD src repository

 Modified files:
   sys/pci              if_rl.c
 Log:
 It seems that RealTek 8129/8139 chip reports invalid length of
 received frame under certain conditions. wpaul said the length
 0xfff0 is special meaning that indicates hardware is in the
 process of copying a packet into host memory. But it seems
 there are other cases that hardware is busy or stuck in bad
 situation even if the received frame length is not 0xfff0.
 To work-around this condition, add a check that verifys that
 recevied frame length is in valid range. If received length is out
 of range reinitialize hardware to recover from stuck condition.

 Reported by:    Mike Tancsa ( mike AT sentex DOT net )
 Tested by:      Mike Tancsa
 Obtained from:  OpenBSD
 MFC after:      1 week

 Revision  Changes    Path
 1.174     +5 -3      src/sys/pci/if_rl.c

--Bill

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to