Greetings, I cvsup'd and rebuilt a FreeBSD 4.8 system last Friday after receiving the realpath security advisory. The machine is remote and the NIC uses the rl driver. After booting the machine I had no network connectivity. The person at the remote site says the boot was normal and he could see that the NIC was properly configured but he could not ping it and I could not login. We booted off kernel.old and everything came up fine. I browsed the stable list here and noticed someone else had the same problem with the rl driver, "rl(4) is broken in stable". Could not see any problems at all with the boot just the nic appears not to be working. Its a RealTek 8139 10/100BaseTX. I re-built the kernel again yesterday after again cvsuping the source on Monday August 18th. Thanks John Rushford jjr@alisa.org
I had a similar problem: after the update (I cvsup'd on sunday morning) the system was able to send packages but unable to receive any (both via rl0). After several hours I finally found a solution that works for me: I rm'd /usr/src, installed the sources from the 4.8-RELEASE-CD, rebuild the whole system (userland and kernel), cvsup'd to STABLE (sunday afternoon) and rebuild the whole system again ... after that the problem was gone Maybe deleting /usr/src and cvsup'ing to STABLE again is enough ... mfg worldi> Greetings, > > I cvsup'd and rebuilt a FreeBSD 4.8 system last Friday after receiving > the realpath security advisory. The machine is remote and the NIC > uses the rl driver. After booting the machine I had no network > connectivity. The person at the remote site says the boot was normal > and he could see that the NIC was properly configured but he could not > ping it and I could not login. We booted off kernel.old and everything > came up fine. > > I browsed the stable list here and noticed someone else had the same > problem with the rl driver, "rl(4) is broken in stable". Could not > see any problems at all with the boot just the nic appears not to be > working. Its a RealTek 8139 10/100BaseTX. I re-built the kernel > again yesterday after again cvsuping the source on Monday August 18th. > > Thanks > John Rushford > jjr@alisa.org > > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to > "freebsd-stable-unsubscribe@freebsd.org" >-- "Du bist hier, weil du etwas wei?t, etwas, das du nicht erkl?ren kannst, aber du f?hlst es. Du f?hlst es schon dein ganzes Leben lang, da? mit der Welt etwas nicht stimmt. Du wei?t nicht was, aber es ist da: wie ein Splitter in deinem Kopf, der dich verr?ckt macht." - Morpheus
There were 2 commits to stable for the rl driver. The commit logs show
---------------------
wpaul 2003/08/15 15:52:34 PDT
FreeBSD src repository
Modified files: (Branch: RELENG_4)
sys/pci if_rl.c if_rlreg.h
Log:
MFC: port all the support for the 8139C+ and 8169 chips to -stable.
Revision Changes Path
1.38.2.17 +1637 -298 src/sys/pci/if_rl.c
1.14.2.6 +358 -19 src/sys/pci/if_rlreg.h
wpaul 2003/08/16 22:30:01 PDT
FreeBSD src repository
Modified files: (Branch: RELENG_4)
sys/pci if_rl.c
Log:
Undo small portion of MFC: revert the rl_rxeof() function to its old
use of m_devget(). The m_devget() function in -stable doesn't work
like it does in -current.
Revision Changes Path
1.38.2.18 +20 -7 src/sys/pci/if_rl.c
------------------------------------------------
My guess is you got the first commit, but not the second. rm -R'ing your
src tree probably didnt do anything. It was the re-cvsup later which
downloaded the second commit that fixed your problem.
In general, I find that if I am tracking stable, its important to watch the
cvs-commit mailing list. A simple procmail rule
:0 BH
* ^Sender: owner-cvs-all
*.RELENG_4.*
! fcvsup-releng4-l
will help you look at just the releng_4 commits
---Mike
At 06:18 AM 20/08/2003 +0200, worldi wrote:
>I had a similar problem: after the update (I cvsup'd on sunday morning)
>the system was able to send packages but unable to receive any (both via
>rl0).
>
>After several hours I finally found a solution that works for me:
>
>I rm'd /usr/src, installed the sources from the 4.8-RELEASE-CD, rebuild
>the whole system (userland and kernel), cvsup'd to STABLE (sunday
>afternoon) and rebuild the whole system again ... after that the
>problem was gone
>
>Maybe deleting /usr/src and cvsup'ing to STABLE again is enough ...
>
>
>mfg worldi
>
>
>
> > Greetings,
> >
> > I cvsup'd and rebuilt a FreeBSD 4.8 system last Friday after
receiving
> > the realpath security advisory. The machine is remote and the NIC
> > uses the rl driver. After booting the machine I had no network
> > connectivity. The person at the remote site says the boot was normal
> > and he could see that the NIC was properly configured but he could not
> > ping it and I could not login. We booted off kernel.old and everything
> > came up fine.
> >
> > I browsed the stable list here and noticed someone else had the same
> > problem with the rl driver, "rl(4) is broken in stable".
Could not
> > see any problems at all with the boot just the nic appears not to be
> > working. Its a RealTek 8139 10/100BaseTX. I re-built the kernel
> > again yesterday after again cvsuping the source on Monday August 18th.
> >
> > Thanks
> > John Rushford
> > jjr@alisa.org
> >
> > _______________________________________________
> > freebsd-stable@freebsd.org mailing list
> > http://lists.freebsd.org/mailman/listinfo/freebsd-stable
> > To unsubscribe, send any mail to
> > "freebsd-stable-unsubscribe@freebsd.org"
> >
>
>
>
>--
>"Du bist hier, weil du etwas wei?t, etwas, das du nicht erkl?ren
>kannst, aber du f?hlst es. Du f?hlst es schon dein ganzes Leben
>lang, da? mit der Welt etwas nicht stimmt. Du wei?t nicht was,
>aber es ist da: wie ein Splitter in deinem Kopf, der dich verr?ckt
>macht." - Morpheus
>_______________________________________________
>freebsd-stable@freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>To unsubscribe, send any mail to
"freebsd-stable-unsubscribe@freebsd.org"
> There were 2 commits to stable for the rl driver. The commit logs show > > --------------------- > wpaul 2003/08/15 15:52:34 PDT > > FreeBSD src repository > > Modified files: (Branch: RELENG_4) > sys/pci if_rl.c if_rlreg.h > Log: > MFC: port all the support for the 8139C+ and 8169 chips to -stable. > > Revision Changes Path > 1.38.2.17 +1637 -298 src/sys/pci/if_rl.c > 1.14.2.6 +358 -19 src/sys/pci/if_rlreg.h > > > wpaul 2003/08/16 22:30:01 PDT > > FreeBSD src repository > > Modified files: (Branch: RELENG_4) > sys/pci if_rl.c > Log: > Undo small portion of MFC: revert the rl_rxeof() function to its old > use of m_devget(). The m_devget() function in -stable doesn't work > like it does in -current. > > Revision Changes Path > 1.38.2.18 +20 -7 src/sys/pci/if_rl.c > > ------------------------------------------------ > > > My guess is you got the first commit, but not the second. rm -R'ing your > src tree probably didnt do anything. It was the re-cvsup later which > downloaded the second commit that fixed your problem. > > In general, I find that if I am tracking stable, its important to watch > the cvs-commit mailing list.I don't think which the problem is that. http://www.freebsd.org/cgi/query-pr.cgi?pr=55727 -- Marco Trentini mark@remotelab.org http://www.remotelab.org/