Ethan Solomita wrote: > > 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
Hi Ethan, I just built a kernel with your SMP patch + my patch to the arch/i386/kdb/kdba_bp.c + your 2 line fix. On the first boot I let the system come up to multi-user When I hit pause key it hung. On the next boot I hit pause while the system was still booting. I got in to kdb o.k. I set the kdb_flag to 0x420000. I let the system continue and start X. I got back in with the pause key. I set a breakpoint at sys_open and continued several times. I disabled the breakpoint and did a go. Hit pause re-enabled the breakpoint. I repeated these steps a few more times. It seemed to be working. I changed kdb_flags to 0x20000. Still working. I disabled the breakpoint, did a go, pause again, cleared the breakpoint. then I cleared kdb_flags and did a go. Another pause and it was hung. Any idea why it hangs with the debug turned off aside from Murphy's law? Jim Houston - Concurrent Computer Corp.
