From owner-freebsd-current@FreeBSD.ORG Fri May 22 12:55:45 2009 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 1D495106568E for ; Fri, 22 May 2009 12:55:45 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from koef.zs64.net (koef.zs64.net [212.12.50.230]) by mx1.freebsd.org (Postfix) with ESMTP id 8CCF48FC13 for ; Fri, 22 May 2009 12:55:44 +0000 (UTC) (envelope-from stb@lassitu.de) Received: from localhost by koef.zs64.net (8.14.3/8.14.3) with ESMTP id n4MCtgKA042164 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for ; Fri, 22 May 2009 14:55:43 +0200 (CEST) (envelope-from stb@lassitu.de) (authenticated as stb) Message-Id: <8FE57686-E9EE-4118-A0F5-0DBF0B154D27@lassitu.de> From: Stefan Bethke To: FreeBSD Current In-Reply-To: <15095A18-F361-4F8E-8253-0B675C771FC4@lassitu.de> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v935.3) Date: Fri, 22 May 2009 14:55:42 +0200 References: <746CE32B-BCF8-460A-982D-25341554E8FD@lassitu.de> <4A167B39.2090405@ongs.co.jp> <15095A18-F361-4F8E-8253-0B675C771FC4@lassitu.de> X-Mailer: Apple Mail (2.935.3) Subject: Re: ifconfig triggers kernel trap on boot X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Fri, 22 May 2009 12:55:45 -0000 Am 22.05.2009 um 13:53 schrieb Stefan Bethke: > Am 22.05.2009 um 12:15 schrieb Daichi GOTO: > >> I have ifconfig(8) panic issue like you. >> >> With current, just do ifconfig(8) like follow leads panic. >> >> ifconfig re0 inet xxx.xxx.xxx.xxx netmask yyy.yyy.yyy.yyy >> >> I have tried on board re0 and attached fxp0, both have the >> same result. >> >> Anyone has any ideas around these panic issues? By my >> little research, kernel/world up until to 12/05/2009 03:00 >> has no problem. At least, kernel/world at 19/05/2009 JST >> has above panic issue. > > I've checked from single-user mode, and the panic is indeed > triggered by the address assignment. > > # sh ifc > ifconfig bridge0ke inet 44.128.65.rn1/28 > + ifconfigel bridge0 inet 44 t.128.65.1/28 > rap 9 with interrupts disabled > > > Fatal trap 9: general protection fault while in kernel mode > cpuid = 0; apic id = 00 > instruction pointer = 0x20:0xffffffff80323f5b > stack pointer = 0x28:0xffffff8076524760 > frame pointer = 0x28:0xffffff8076524770 > code segment = base 0x0, limit 0xfffff, type 0x1b > = DPL 0, pres 1, long 1, def32 0, gran 1 > processor eflags = resume, IOPL = 0 > current process = 48 (ifconfig) > [thread pid 48 tid 100056 ] > Stopped at turnstile_setowner+0x2b: movq %rcx, > 0x68(%rdx) > > A kernel compiled from the same sources with practically identical > configuration (GENERIC minus most devices) running inside VMware > (but also SMP) does not exhibit this issue. Using the failing kernel in VMware triggers the same panic, so it does appear to be configuration dependant. I'll see what's different between the two configs. Stefan -- Stefan Bethke Fon +49 151 14070811