Jason Thorpe wrote:
> On Tue, 1 Jun 1999 13:32:10 -0700 (PDT) 
>  Colin Wood <cwood@ichips.intel.com> wrote:
> 
>  > it looks like you're now getting bit by the bug which has been affecting
>  > the AV macs for some time.  it looks like a kernel-size dependency is
>  > somehow affecting the direct-to-hardware driver's delay loop timing.
>  > switching to the MRG-based driver should serve as a usable workaround
>  > (although not the best long-term solution, of course).  turning on the
>  > DEBUG option has fixed it for other people.  is the "cpu delay factor"
>  > reported for this kernel different than that of previous kernels?
> 
> LAME!!!  :-)
> 
> So, in working kernel:
> 
> cpu: delay factor 355
> 
> In broken kernel:
> 
> cpu: delay factor 388
> 
> "Oh, that's COOL!"

yep, that's the kind of thing that some other people are seeing as well.
apparently the delay timing on the newer ADB hardware is quite sensitive,
and having the wrong delay factor completely blows the 3ms timing loop in
adb_direct.c.  now _why_ the delay factor is different from one kernel to
the next is a completely different (and more interesting) question....

later.

colin