Re: 2.1.119 on alpha

[Stephen Williams <steve icarus com>]

rth@cygnus.com said:
> Given that I believe the problem to be some sort of garbage pointer
> write corrupting data, what I need are kernels that _don't_ work, that
> _reliably_ don't work, and that continue to not work in the same way
> when attempts are made to debug them. 

Ugh!

What I was hoping to do was identify a faulty component by cutting it out
and seeing that the problem disappears. I don't have many things left to
cut out, though.

When doing embedded debugging, I'd be getting out the scope and the schematics
and looking for bus activity to see where things are locked up (unserviced
interrupts are good for this sort of thing) but I'm a bit busy right now
debugging the boards I'm paid to debug, not to mention I don't have the
requisite schematics.

Have you narrowed the problem at all?
-- 
Steve Williams                "The woods are lovely, dark and deep.
steve@icarus.com              But I have promises to keep,
steve@picturel.com            and lines to code before I sleep,
http://www.picturel.com       And lines to code before I sleep."