From owner-freebsd-smp@FreeBSD.ORG Wed Jun 29 19:41:17 2005 Return-Path: X-Original-To: freebsd-smp@freebsd.org Delivered-To: freebsd-smp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 4059E16A41C; Wed, 29 Jun 2005 19:41:17 +0000 (GMT) (envelope-from hvleest@signet.nl) Received: from smtpq1.home.nl (smtpq1.home.nl [213.51.128.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C6F2143D49; Wed, 29 Jun 2005 19:41:16 +0000 (GMT) (envelope-from hvleest@signet.nl) Received: from [213.51.128.134] (port=40378 helo=smtp3.home.nl) by smtpq1.home.nl with esmtp (Exim 4.30) id 1DniQt-000655-T9; Wed, 29 Jun 2005 21:41:15 +0200 Received: from cp417515-a.dbsch1.nb.home.nl ([84.27.32.116]:4988 helo=[192.168.100.105]) by smtp3.home.nl with esmtp (Exim 4.30) id 1DniQs-0007n4-Pq; Wed, 29 Jun 2005 21:41:14 +0200 Message-ID: <42C2F957.3010308@signet.nl> Date: Wed, 29 Jun 2005 21:41:11 +0200 From: Hans van Leest User-Agent: Mozilla Thunderbird 0.7.1 (Windows/20040626) X-Accept-Language: en-us, en MIME-Version: 1.0 To: hvleest@signet.nl References: <42BECC86.3090404@signet.nl> <200506281322.37414.jhb@FreeBSD.org> <42C2DFC7.2020409@signet.nl> <200506291430.00605.jhb@FreeBSD.org> <42C2F278.60408@signet.nl> In-Reply-To: <42C2F278.60408@signet.nl> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-AtHome-MailScanner-Information: Neem contact op met support@home.nl voor meer informatie X-AtHome-MailScanner: Found to be clean Cc: freebsd-smp@freebsd.org, John Baldwin Subject: Re: Boot error SMP X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 29 Jun 2005 19:41:17 -0000 i think something strange is going on. I booted four times on the SMP kernel, and 4 times I had a different error I don't thing that's oke, when a kernel crashes. boot1: fatal process exeption; page fault; fault VA=0x0 instruction pointer boot 2: 0xc07e8fd6 instruction pointer boot 3: 0xc0687a9c instruction pointer boot 4: 0xc05ee318 a gdb> list from the last one gave: No symbol table is loaded. Use the "file" command. Hans van Leest wrote: > I proberbly didn't uderstand you correct. I did the following. > Booted from SMP_DEBUG kernel and it crashed. Secondly I booted from a > working kernel and > #cd /usr/obj/usr/src/sys/SMP_DEBUG > #gdb /usr/obj/usr/src/sys/SMP_DEBUG > gdb> list *0xc061a5e7 > > It gave this back: > > (gdb) list *0xc061a5e7 > 0xc061a5e7 is in free (uma_int.h:388). > 383 { > 384 vm_page_t p; > 385 uma_slab_t slab; > 386 > 387 p = PHYS_TO_VM_PAGE(pmap_kextract(va)); > 388 slab = (uma_slab_t )p->object; > 389 > 390 if (p->flags & PG_SLAB) > 391 return (slab); > 392 else > (gdb) > > > > John Baldwin wrote: > >> On Wednesday 29 June 2005 01:52 pm, Hans van Leest wrote: >> >> >>> I got a boot with the new debug kernel, only I got an new instruction >>> pointer. this one is: >>> 0x8:0xc061a5e7 >>> When I type db> gdb, it replies that it can't find the backend >>> When I type tr after db> I get a lot of data so I want to use serial >>> console So I don't have to type it over. Only I get errors >>> >>> From the howto I did this >>> >>> cat /etc/ttys >>> --snip-- >>> # The 'dialup' keyword identifies dialin lines to login, fingerd etc. >>> ttyd0 "/usr/libexec/getty std.9600" vt100 on secure >>> ttyd1 "/usr/libexec/getty std.9600" vt100 on secure >>> ttyd2 "/usr/libexec/getty std.9600" vt100 on secure >>> ttyd3 "/usr/libexec/getty std.9600" vt100 on secure >>> >> >> >> These only let you login over the serial line, you don't need this >> for the kernel console. >> >> >> >>> bsd# cat /boot/loader.conf >>> set console="comconsole" >>> >> >> >> This should be all you need. >> >> >> >>> I got error like this: >>> bsd init: can't exec getty 'none' for port /dev/console: No such file >>> or directory >>> >> >> >> You must have something weird on the 'console' line in /etc/ttys. >> Normally the getty on that line should be 'off'. The way to grab the >> output is to use cut and paste or script(1) or some such on the >> machine that you are talking to the bsd box with, you don't capture >> the trace info on the bsd machine itself. For example, if you are >> using some Windows terminal app, you can cut and paste the trace info >> into notepad and then cut and paste that into an e-mail. If you are >> using another unix box without X11 as the client end of the console >> you could use script(1) to log the output to a file. >> >> That said, having the instruction pointer is good. To use that, boot >> the bsd box, find the kernel.debug from the kernel you built >> (probably /usr/obj/usr/src/sys//kernel.debug) and run >> gdb on it like so: >> >> # gdb /path/to/kernel.debug >> >> Then, at the gdb> prompt do a list: >> >> gdb> list *0xc061a5e7 >> >> >> > > _______________________________________________ > freebsd-smp@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-smp > To unsubscribe, send any mail to "freebsd-smp-unsubscribe@freebsd.org" >