Date: Thu, 23 Mar 2000 01:33:11 +0200 From: Giorgos Keramidas <keramida@ceid.upatras.gr> To: Mike Smith <msmith@freebsd.org> Cc: current@freebsd.org Subject: Re: Not actually (Was Re: crash in atkbd_isa_intr() ) Message-ID: <20000323013311.A2468@hades.hell.gr> In-Reply-To: <200003222208.OAA03940@mass.cdrom.com>; from msmith@freebsd.org on Wed, Mar 22, 2000 at 02:08:42PM -0800 References: <20000323000017.A2325@hades.hell.gr> <200003222208.OAA03940@mass.cdrom.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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 majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20000323013311.A2468>