From owner-freebsd-hackers Tue Mar 11 17:34:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA29714 for hackers-outgoing; Tue, 11 Mar 1997 17:34:06 -0800 (PST) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA29684 for ; Tue, 11 Mar 1997 17:34:00 -0800 (PST) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id MAA19972; Wed, 12 Mar 1997 12:02:56 +1030 (CST) From: Michael Smith Message-Id: <199703120132.MAA19972@genesis.atrad.adelaide.edu.au> Subject: Re: Trap 12's in machine over the last few days In-Reply-To: from Khetan Gajjar at "Mar 10, 97 01:51:28 pm" To: khetan@iafrica.com (Khetan Gajjar) Date: Wed, 12 Mar 1997 12:02:55 +1030 (CST) Cc: hackers@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Khetan Gajjar stands accused of saying: > I'm running 2.2-GAMMA, on a DTK motherboard w/512kb, with a Cyrix P150+ > processor and 48MB RAM. There are 3xIDE 1 gig drives, a SMC EtherPower > NIC and a Diamond Stealth 64. > > Over the last four days, my machine keeps breaking into the debugger, with > the following : > > Fatal Trap 12: page fault while in kernel mode > fault virtual address = 0x0 > fault code = supervisor read, page not present > instruction pointer = 0x8:0x0 Erk, that's a jump through a NULL pointer. > stack pointer = 0x10:0xefbffe54 > frame pointer = 0x10:0xefbffe5c > code segment = base 0x0, limit 0xfffff, type 0x1b > = dpl 0, pres 1, def32 1, gran 1 > processor eflags = interrupt enabled, resume, IOPL = 0 > current process = 248 (halt) > interrupt mask = > kernel:type 12 trap, code=0 > > (Sorry for any typo's - difficult to type this stuff) ... > Any pointers on how to see what the exact problem is ? Does the above trap > help ? I've tried various combinations of RAM, wiggling everything in, > etc, but it doesn't help. Yeah, the 'trace' command will do a reasonable job of unwinding the stack, which should help you work out where the traps are happening. > Khetan Gajjar [ http://www.iafrica.com/~khetan] -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[