From owner-freebsd-current@FreeBSD.ORG Tue Sep 14 23:04:49 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9EF516A4CF; Tue, 14 Sep 2004 23:04:48 +0000 (GMT) Received: from mail.vtec.ipme.de (C3B3C61C.dial.de.easynet.net [195.179.198.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id B5B7D43D45; Tue, 14 Sep 2004 23:04:46 +0000 (GMT) (envelope-from volker@vwsoft.com) Received: from [192.168.16.24] (unknown [192.168.16.24]) by bellona.sz.vwsoft.com (Postfix) with ESMTP id E6A17BB8E; Wed, 15 Sep 2004 00:54:01 +0200 (CEST) Message-ID: <4147768D.4050400@vwsoft.com> Date: Wed, 15 Sep 2004 00:54:05 +0200 From: Volker User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.2) Gecko/20040822 Thunderbird/0.7+ Mnenhy/0.6.0.101 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson References: In-Reply-To: X-Enigmail-Version: 0.85.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: fatal trap 12 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 14 Sep 2004 23:04:49 -0000 Hi Robert! Yes.... I got it right. I've setup a serial connection, rebuild the kernel (forgot to include debugging information, but kernel builds are slow on the AMD K6-2 500), installed, rebooted and was waiting for the first trap to come. Here we are: > Fatal trap 12: page fault while in kernel mode > fault virtual address = 0xffff5d00 > fault code = supervisor write, page not present > instruction pointer = 0x8:0xc054e86d > stack pointer = 0x10:0xca3f4c20 > frame pointer = 0x10:0xca3f4c20 > 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 = 34 (swi6: task queue) > [thread 100035] > Stopped at mb_ctor_pack+0x4d: movl $0x1,0(%eax) ddg trace gives: > db> trace > mb_ctor_pack(c1558400,100,ca3f4c60,1) at mb_ctor_pack+0x4d > uma_zalloc_arg(c1044ba0,ca3f4c60,1) at uma_zalloc_arg+0xf0 > ath_rxbuf_init(c1494000,c14a1f18) at ath_rxbuf_init+0x41 > ath_rx_proc(c1494000,1) at ath_rx_proc+0x3c4 > taskqueue_run(c1418ac0,ca3f4d20,c0545009,0,0) at taskqueue_run+0xb7 > taskqueue_swi_run(0) at taskqueue_swi_run+0xe > ithread_loop(c13b1b80,ca3f4d48) at ithread_loop+0x159 > fork_exit(c0544eb0,c13b1b80,ca3f4d48) at fork_exit+0x79 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip = 0, esp = 0xca3f4d7c, ebp = 0 --- For the case it might be some important piece of information, I've also copied the following ddb output (I'm not really highly experienced in kernel debugging, so I don't know which info is most important): > db> show registers > cs 0x8 > ds 0x10 > es 0x10 > fs 0x18 > ss 0x10 > eax 0xffff5d00 > ecx 0xc1558400 > edx 0x2 > ebx 0xc1044bd8 > esp 0xca3f4c20 > ebp 0xca3f4c20 > esi 0xc1044ba0 > edi 0 > eip 0xc054e86d mb_ctor_pack+0x4d > efl 0x10206 > dr0 0 > dr1 0 > dr2 0 > dr3 0 > dr4 0xffff0ff0 > dr5 0x400 > dr6 0xffff0ff0 > dr7 0x400 > mb_ctor_pack+0x4d: movl $0x1,0(%eax) > db> > db> show pcpu > cpuid = 0 > curthread = 0xc13e37d0: pid 34 "swi6: task queue" > curpcb = 0xca3f4da0 > fpcurthread = none > idlethread = 0xc13bd320: pid 10 "idle" > APIC ID = 0 > currentldt = 0x28 I'll start to rebuild the kernel with debugging information (takes about an hour) and restart again. I'll post more traces if I catch some. Do you need anything else? Thanks, Volker -- GPG/PGP fingerprint: FF93 13A1 2477 B631 E953 06DF 4C49 ADD9 E4BF 79B1