On Wed, Mar 22, 2000 at 02:08:42PM -0800, Mike Smith wrote:
>
> > Yes, I did, to get into the debugger. Now I wonder, if there is
> > some other bug that I need to chase around, how should I proceed?
>
> You can try looking at the stack further above the atkbd interrupt,
> since that's where it was running when it took the interrupt. If
> there's nothing there, then it was running in userspace and you might
> want to try the 'ps' command.
There is no frame above #12, which means that the problem is probably
not in atkbd_isa_intr() after all, but I can not the system to respond
after it stops. I'll try and run `ps' in ddd and see if I can get the
output written down somewhere.
In the mean time, I've recompiled a freshly cvsup'ed kernel, booted it,
and now I'm trying to build my world -- since it seems that compiling
the kernel and/or `world' triggers the funny condition I'm running into.
If that does not give me a working kernel/world, I might as well start
looking for hardware related problems, memory being the most likely
culprit for such kind of behavior.
- Giorgos Keramidas
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
