From owner-freebsd-current Sat Oct 3 16:49:33 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA21616 for freebsd-current-outgoing; Sat, 3 Oct 1998 16:49:33 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from pozo.pozo.com (pozo.pozo.com [207.201.8.18]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA21598 for ; Sat, 3 Oct 1998 16:49:25 -0700 (PDT) (envelope-from mantar@netcom.com) Received: from dual (DUAL [192.168.0.2]) by pozo.pozo.com (8.9.1/8.9.1) with SMTP id QAA00320; Sat, 3 Oct 1998 16:45:45 -0700 (PDT) (envelope-from mantar@netcom.com) Message-Id: <4.1.19981003164142.00a422a0@192.168.0.1> X-Sender: null@192.168.0.1 X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Sat, 03 Oct 1998 16:45:44 -0700 To: Mike Smith From: Manfred Antar Subject: Re: CRUSH after recompile kernel... Cc: Mike Smith , Robert Nordier , osa@etrust.ru, current@FreeBSD.ORG In-Reply-To: <199810032232.PAA08307@word.smith.net.au> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 03:32 PM 10/3/98 -0700, Mike Smith wrote: >> >> 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... > Just out of curiosity I built an elf kernel without the debugger and tried the /boot/loader. It worked fine. so the problem had something to do with the debugger code. I'll test it more Sunday. Manfred ============================== || mantar@netcom.com || || pozo@infinex.com || || Ph. (415) 681-6235 || ============================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message