On Thu, 31 Oct 2002, Daniel R. Killoran,Ph.D. wrote:

> Frederick Bruckman wrote:
> >
> >For a while there, making any single change was liable to change the
> >initial time/scaling loop, which could consistently cause the adb
> >driver to hang up. The clue was in the "cpu: delay factor" at the top
> >of the kernel messages: kernels with one "delay factor" consistently
> >worked, while kernels with the other "delay factor" didn't. It always
> >looked like the last change you made was responsible, but it wasn't.
> >Scott added a directive to line up the code that calculates the delay
> >factor on a cache line, and that seems to have fixed that. Does your
> >"delay factor" change with the working kernel vs. the good kernel?
>
> Alas, both SMALLRAM and GENERICSBC show the same "Delay Factor"(332)
>
> I forgot to mention that GENERICSBC DID boot ONCE (It was the second
> try) but has hung ever since, always at that same place.

I don't see any quick resolution (though I'm glad you have a kernel
that works now). Would you please file a PR, so at least the problem
isn't forgotten, only to be rediscovered after the next release?

Frederick