amr driver broken since March 12

Scott Lambert lambert at
Fri Mar 27 09:40:12 PDT 2009

On Fri, Mar 27, 2009 at 06:52:32PM +0300, Danny Braniss wrote:
> > Danny Braniss wrote:
> > > at least for me :-)
> > > [and sorry for the cross posting]
> > > 
> > > old (March 12 , i know need the svn rev number but...)
> > 
> > None of the commit activity on March 12 is jumping out at me as being 
> > suspicious.  However, you are now the second person who has told me 
> > about AMR problems in 7.1 recently.  If you have a precise svn change
> > number, it would help greatly.
> > 
> > Scott (Long)
> my bad. the last working amr/iir is from March 12.
> I first detected the problem sometime later, but not later than March 23.
> So it has to be changes in that time frame.

I think Scott Long was actually asking if you could try to cvsup (or
csup) to a date between those two and see if the problem shows there.
If you go for, (23 - 12/2) + 12, something like March 17, it would help
to narrow what changes could be causing the problem.  If you see the
problem with a March 17 kernel, you can split the time between March 12
and 17 and try again.  Then just keep cutting the search space in half
until you can pretty much say "This is the commit that broke things for

It's not always possible for someone to take the time to do the binary
search for the actual commit which broke things for them.  But when they
can, it really helps the developers.  Just cutting it down from 11 days
to 5 or 6 days can probably be a big help.

Scott Lambert                    KC5MLE                       Unix SysAdmin
lambert at

More information about the freebsd-scsi mailing list