7.1 Release broke my box

[M. Warner Losh]

In message: <18796.44888.658271.953215 at gromit.timing.com>
            John Hein <jhein at timing.com> writes:
: Markus Hitter wrote at 09:52 +0100 on Jan 12, 2009:
:  > 
:  > Am 12.01.2009 um 03:51 schrieb John Hein:
:  > 
:  > > Markus Hitter wrote at 01:31 +0100 on Jan 12, 2009:
:  > >> Last Friday, after seeing ext2fs doesn't work with the 7.0 kernel, I
:  > >> decided to do yet another step and upgrade to 7.1 Release. The
:  > >> virtual machine for building tinybsd setup and ran flawlessly, but a
:  > >> tinybsd image built from it doesn't like networking any longer. The
:  > >> non-working box is a Geode-based Flepo Alpha, which uses the re
:  > >> network driver.
:  > >
:  > > What happens if you build a kernel with the 7.0 version of
:  > > sys/dev/re/if_re.c?  You may have to roll back sys/pci/if_rlreg.h too.
:  > 
:  > The exactly same (had to roll back sys/pci/if_rl.c as well).
:  > 
:  > > What happens to the link light while these things are happening?
:  > 
:  > The green light stays on, the yellow one flickers, just like expected.
:  > 
:  > Obviously, the transmission gets interrupted at some higher level. Do  
:  > I really have to bisect the entire kernel with it's 10,000 revisions  
:  > now? *sigh*
: 
: My guess was the first obvious one I could think of since I knew
: changes happened in the re/rl drivers.  I can't think of anything else
: obvious between 7.0 & 7.1 that would affect this (particularly since I
: have an re that works fine in 7.1 - at least a 7.1 from, say,
: September).
: 
: As far as bisecting goes, I recommend binary search by date on the
: RELENG_7 branch rather than trying to rollback individual revs.  Note
: that cvs 1.12 allows checking out by date (-D) on a branch
: (-rRELENG_7) (but not 1.11).  Or you can use cvsup to help with that I
: think.

I also think there were some bugs fixed in re/rl in stable lately...

Warner