the pc's printed by the lock loop message are kernel code. you
have to load a debug kernel into acid.

--
cinap
--- Begin Message ---
> i assume you've fixed this?  (not yet fixed on sources.)

Yes, before I did that the errors occurred much more frequently;
there's definitely something in that, but as Russ points out, the fix
prevents panics and I have yet to see a panic.

I have a suspicion that we're looking at the wrong problem, but I
don't know how to approach it.

I tried acid, but I'm just not familiar enough with it to make it
work.  I tried

        rumble% acid 2052 /bin/exportfs
        /bin/exportfs:386 plan 9 executable
        /sys/lib/acid/port
        /sys/lib/acid/386
        acid: src(0xf01e7377)
        no source for ?file?

and that's where I have to leave it for the time being.  But
suggestions are welcome, I'll be back here at the end of the day (it's
07:00 now, I expect to be back after 19:00).

++L


--- End Message ---

Reply via email to