From owner-freebsd-smp@FreeBSD.ORG Thu Jun 30 23:03:45 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 C4FF616A41C; Thu, 30 Jun 2005 23:03:45 +0000 (GMT) (envelope-from hvleest@signet.nl) Received: from bsd.local.jellevanleest.nl (cp417515-a.dbsch1.nb.home.nl [84.27.32.116]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BC8343D48; Thu, 30 Jun 2005 23:03:42 +0000 (GMT) (envelope-from hvleest@signet.nl) Received: from [192.168.100.105] (unknown [192.168.100.105]) by bsd.local.jellevanleest.nl (Postfix) with ESMTP id 8170A62B5; Fri, 1 Jul 2005 01:07:04 +0200 (CEST) Message-ID: <42C47A49.3030407@signet.nl> Date: Fri, 01 Jul 2005 01:03:37 +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: John Baldwin References: <42BECC86.3090404@signet.nl> <42C2F278.60408@signet.nl> <42C2F957.3010308@signet.nl> <200506301054.28770.jhb@FreeBSD.org> In-Reply-To: <200506301054.28770.jhb@FreeBSD.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-smp@freebsd.org Subject: Re: Boot error SMP X-BeenThere: freebsd-smp@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: hvleest@signet.nl List-Id: FreeBSD SMP implementation group List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Jun 2005 23:03:46 -0000 Tested machine with memtest and stress. But no errors at all, except these messages: got 326MB (342781952 bytes), trying mlock ...too many pages, reducing... Which, as I understand it, is a mesage when memory is used How do I continue? John Baldwin wrote: >On Wednesday 29 June 2005 03:41 pm, Hans van Leest wrote: > > >>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. >> >> > >Are you sure the RAM and CPUs are ok? Have you tried running memtest on it? > > > >>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" >>> >>> >>_______________________________________________ >>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" >> >> > > >