On Sun, 20 Nov 2005, Bob Brose wrote:

>
> > > Also another odd thing, from adb. I was holding down the up arrow
> > > key to go through the history under bash and the computer though at
> > > some point that I never released the key. I couldn't do anything to
> > > get it to stop by repushing the down key or any other key for that
> > > matter.
> >
> > Do any other ADB events register? If no other keys do anything at all,
> > it's possible that the driver lost communication with the bus, and
> > isn't seeing anything to end the key repeat. Most likely this would
> > just be a bug in the driver.
>
> It seems like the adb gets hung. When it gets stuck, last time was on
> the "n" key, no other key makes it change, it keeps hammering out n's.
> When this happens, I can still access the machine via the ethernet. When
> I try a reboot (which appears to rely upon adb) the machine is unable to
> restart, it hangs at the point at which it's supposedly going to do a HW
> reboot.

A while ago I had the same "stuck" key problem (on very similar hardware).

http://marc.theaimsgroup.com/?l=linux-mac68k&m=112006052810878&w=2

> Now I tried a bunch of combinations of kernels and devices and made the
> following observations:
>
> With the b and c patches mentioned previously installed, if adb is
> DISABLED esp and sonic work ok. sg_verify suceeds on the whole disc.

OK, this means there isn't really any regression. CUDA ADB has been flakey
for as long as I've been using 2.6 kernels. (Small comfort, I know.)

-f
_______________________________________________
linux-mac68k mailing list
linux-mac68k@...
http://lists.purplehat.net/listinfo/linux-mac68k