As an update -- the other problem I was having with my sparc64 8p
system was an I/O driver related issue, not a kdb thing. With the
two-line fix I just emailed, I can't reproduce a problem on my sparc64
8p anymore. Jim -- do you have any specific sequences of kdb commands
that typically make things go wrong? Do the problems still occur when
you set kdb_flags to 0xffff0000 to get all the debugging info?
        -- Ethan


Reply via email to