From owner-freebsd-current Sat Oct 3 15:32:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA09829 for freebsd-current-outgoing; Sat, 3 Oct 1998 15:32:08 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from word.smith.net.au (castles246.castles.com [208.214.165.246]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA09775 for ; Sat, 3 Oct 1998 15:31:58 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by word.smith.net.au (8.9.1/8.8.8) with ESMTP id PAA08307; Sat, 3 Oct 1998 15:32:29 -0700 (PDT) (envelope-from mike@dingo.cdrom.com) Message-Id: <199810032232.PAA08307@word.smith.net.au> X-Mailer: exmh version 2.0.2 2/24/98 To: Manfred Antar cc: Mike Smith , Robert Nordier , osa@etrust.ru, current@FreeBSD.ORG Subject: Re: CRUSH after recompile kernel... In-reply-to: Your message of "Sat, 03 Oct 1998 14:55:28 PDT." <4.1.19981003144608.00a30c20@192.168.0.1> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 03 Oct 1998 15:32:28 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > >> Thanks > >> Thats what I tried with elf kernels (both SMP an single CPU ones) but I > >> get a: > >> > >> Fatal trap 12: page fault while in kernel mode > >> fault virtual address = 0x36719cc7 > >> fault code = supervisor read, page not present > >> instruction pointer = 0x8:0xf0126294 > >> stack pointer = 0x10:f0291f84 > >> frame pointer = 0x10:f0291f98 > >> code segment = base 0x0, limit 0xfffff, type 0x1b > >> = DPL 0, pres 1, def32 1, gran 1 > >> processor eflags = resume, IOPL = 0 > >> current process = 0 () > >> interrupt mask = net tty bio cam > >> kernel: type 12 trap, code=0 > >> Stopped at 0xf0126294: movl 0(%esi),%ecx > >> db> > >> > >> This happens after it starts loading the kernel. > > > >When did you try this? Where is 0x10:f0291f84 in the kernel? How current > >is your loader and kernel? > > > >We need much more information before we can debug this. > > This is from very current sources and kernel 2:30 pm pacific time > From a new elf kernel it stops at 0x0126294 > closest i can get is > f0126260 t X_bd_sym_init > f0126230 T db_put_value > f0126260 t gcc2_compiled I presume the next value is higher than 0xf012694? This actually looks like a crash inside ddb - do you see two trap messages go past in quick succession? Can you hang a serial console off the system and record the actual process? The original trap is the most interesting one. > I have no trouble booting a aout kernel with the new loader I'd hope not. 8) Mind you, I'd hope you had no trouble with ELF kernels too... -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message