From owner-freebsd-current@FreeBSD.ORG Thu Mar 26 21:26:06 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 EBF02106566C for ; Thu, 26 Mar 2009 21:26:06 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from ebb.errno.com (ebb.errno.com [69.12.149.25]) by mx1.freebsd.org (Postfix) with ESMTP id 9F9988FC13 for ; Thu, 26 Mar 2009 21:26:06 +0000 (UTC) (envelope-from sam@freebsd.org) Received: from trouble.errno.com (trouble.errno.com [10.0.0.248]) (authenticated bits=0) by ebb.errno.com (8.13.6/8.12.6) with ESMTP id n2QLQ3Xx056070 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 26 Mar 2009 14:26:03 -0700 (PDT) (envelope-from sam@freebsd.org) Message-ID: <49CBF2EB.40705@freebsd.org> Date: Thu, 26 Mar 2009 14:26:03 -0700 From: Sam Leffler Organization: FreeBSD Project User-Agent: Thunderbird 2.0.0.18 (X11/20081209) MIME-Version: 1.0 To: Damian Gerow References: <20090326202556.GB46908@plebeian.afflictions.org> In-Reply-To: <20090326202556.GB46908@plebeian.afflictions.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-DCC--Metrics: ebb.errno.com; whitelist Cc: freebsd-current@freebsd.org Subject: Re: panic in 8.0-CURRENT after svn from r189900 to r190389 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: Thu, 26 Mar 2009 21:26:07 -0000 Damian Gerow wrote: > I'm running into a similar problem here, on a Lenovo X200. I've been able > to narrow it down to r190100, which removed uscanner(4) from the tree: > > > > I've verified this by checking out sources from a few hours ago, reverting > r190100 (and, by extension, 190102), and I can now boot with the resulting > kernel. > > I'm not exactly sure how it is this change is causing a panic, though. For > reference, here's a snippet of a boot -v on a panicing kernel: > > ----- > ULE: setup cpu 0 > ULE: setup cpu 1 > ACPI: > MADT: Found IO APIC ID 1, Interrupt 0 at 0xfec00000 > ioapic0: Changing APIC ID to 1 > ioapic0: Routing external 8259A's -> intpin0 > MADT: Interrupt override: source 0, irq 2 > ioapic0: Routing IRQ 0 -> intpin 2 > MADT: Interrupt override: source 9, irq 9 > ioapic0: intpin 9 trigger: level > lapic0: Routing NMI -> LINT1 > lapic0: LINT1 trigger: edge > lapic0: LINT1 polarity: high > lapic1: Routing NMI -> LINT1 > lapic1: LINT1 trigger: edge > lapic1: LINT1 polarity: high > ioapic0 irqs 0-23 on motherboard > cpu0 BSP: > ID: 0x00000000 VER: 0x00050014 LDR: 0x00000000 DFR: 0xffffffff > lint0: 0x00010700 lint1: 0x00000400 TPR: 0x00000000 SVR: 0x000001ff > timer: 0x000100ef therm: 0x00010000 err: 0x00010000 pcm: 0x00000400 > wlan: <802.11 Link Layer> > kernel trap 12 with interrupts disabled > > > Fatal trap 12: page fault while in kernel mode > cpuid = 0; apic id = 00 > fault virtual address = 0x3c > fault code = supervisor write data, page not present > instruction pointer = 0x8:0xffffffff8056d9df > stack pointer = 0x10:0xffffffff80f82c70 > frame pointer = 0x10:0xffffffff80f82ca0 > 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 = 0 (swapper) > [thread pid 0 tid 100000 ] > Stopped at devclass_find_internal+0x10f: orl $0x1,0x3c(%rax) > db> bt > Tracing pid 0 tid 100000 td 0xffffffff80bb6260 > devclass_find_internal() at devclass_find_internal+0x10f > driver_module_handler() at driver_module_handler+0xb9 > module_register_init() at module_register_init+0x7d > mi_startup() at mi_startup+0x59 > btext() at btext+0x2c > db> > ----- > > Feels more like this change is triggering a problem elsewhere in the kernel. > Update; the problem has been fixed in r190417. Sam