cvs commit: src/sys/pci if_vr.c

Pyun YongHyeon pyunyh at gmail.com
Fri Oct 26 05:18:45 PDT 2007


On Fri, Oct 26, 2007 at 10:11:41AM -0200, JoaoBR wrote:
 > On Friday 26 October 2007 09:47:00 Pyun YongHyeon wrote:
 > > On Fri, Oct 26, 2007 at 07:49:11AM -0200, JoaoBR wrote:
 > >  > On Friday 12 October 2007 00:41:54 Pyun YongHyeon wrote:
 > >  > > yongari     2007-10-12 03:41:54 UTC
 > >  > >
 > >  > >   FreeBSD src repository
 > >  > >
 > >  > >   Modified files:        (Branch: RELENG_7)
 > >  > >     sys/pci              if_vr.c
 > >  > >   Log:
 > >  > >   MFC if_vr.c, 1.127 to RELENG_7:
 > >  > >     Not all VIA Rhine chips support 256 register space. So touching
 > >  > >     VR_STICKHW register would result in unexpected results on these
 > >  > >     hardwares. wpaul said the following for the issue.
 > >  > >
 > >  > >       The vr_attach() routine unconditionally does this for all
 > >  > > supported chips:
 > >  > >
 > >  > >           /*
 > >  > >            * Windows may put the chip in suspend mode when it
 > >  > >            * shuts down. Be sure to kick it in the head to wake it
 > >  > >            * up again.
 > >  > >            */
 > >  > >           VR_CLRBIT(sc, VR_STICKHW, (VR_STICKHW_DS0|VR_STICKHW_DS1));
 > >  >
 > >  > Hi
 > >  > since I upgraded to 7 this days I loss connection to a machine with vr
 > >  > nic
 > >  >
 > >  > the only event I can find after resetting (i have no phisical access) is
 > >  >
 > >  > Oct 26 04:31:56 ap-c kernel: vr0: link state changed to DOWN
 > >  >
 > >  > may it be related? What should I do?
 > >
 > > I'm pretty sure it's not related with my changes.
 > >
 > > If you think vr(4) is culprit for the issue try overhauled vr(4).
 > > I think I've fixed many unresolved vr(4) issues but it needs more
 > > testing.
 > > You can download the overhauled vr(4) at the following URL.
 > > http://people.freebsd.org/~yongari/vr/if_vr.c
 > > http://people.freebsd.org/~yongari/vr/if_vrreg.h
 > >
 > > Note, don't use the overhauled driver on your production system.
 > > I couldn't see any issues in the driver but it may have unnoticed
 > > bugs.
 > 
 > I will arrange a test machine to see how it goes
 > 

Ok. Let me know if you see any unusual things. Pluging/unpluging
cables shouldn't affect the operation of vr(4). I heard stock vr(4)
is vulerable to this type of link changes. In addition, you may
notice better Rx performance.

 > my people discovered when the vr goes down they can unplug the tp cable on the 
 > switch and back in again re-activates the nic
 > 

The overhauled vr(4) should not have this bug.

 > this machines run 7 fine, don't remember the exact src date but any day of the 
 > first week, then with the sources from and compiled on 24th do this
 > 
 > thank's
 > 

-- 
Regards,
Pyun YongHyeon


More information about the cvs-src mailing list