From owner-freebsd-current Wed Mar 22 15:32:10 2000 Delivered-To: freebsd-current@freebsd.org Received: from mail.hellasnet.gr (mail.hellasnet.gr [212.54.192.3]) by hub.freebsd.org (Postfix) with ESMTP id 5D9FD37C2D0 for ; Wed, 22 Mar 2000 15:32:04 -0800 (PST) (envelope-from keramida@ceid.upatras.gr) Received: from hades.hell.gr (ppp3.patr.hellasnet.gr [212.54.197.18]) by mail.hellasnet.gr (8.9.1/8.9.1) with SMTP id BAA28911 for ; Thu, 23 Mar 2000 01:31:02 +0200 (GMT) Received: (qmail 21072 invoked by uid 1001); 22 Mar 2000 23:33:12 -0000 Date: Thu, 23 Mar 2000 01:33:11 +0200 From: Giorgos Keramidas To: Mike Smith Cc: current@freebsd.org Subject: Re: Not actually (Was Re: crash in atkbd_isa_intr() ) Message-ID: <20000323013311.A2468@hades.hell.gr> Reply-To: keramida@ceid.upatras.gr References: <20000323000017.A2325@hades.hell.gr> <200003222208.OAA03940@mass.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200003222208.OAA03940@mass.cdrom.com>; from msmith@freebsd.org on Wed, Mar 22, 2000 at 02:08:42PM -0800 X-PGP-Fingerprint: 62 45 D1 C9 26 F9 95 06 D6 21 2A C8 8C 16 C0 8E Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG 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