From owner-freebsd-usb@FreeBSD.ORG Thu Apr 23 12:34:13 2009 Return-Path: Delivered-To: freebsd-usb@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id DA203106566C; Thu, 23 Apr 2009 12:34:13 +0000 (UTC) (envelope-from hselasky@c2i.net) Received: from swip.net (mailfe01.swip.net [212.247.154.1]) by mx1.freebsd.org (Postfix) with ESMTP id 1319A8FC08; Thu, 23 Apr 2009 12:34:12 +0000 (UTC) (envelope-from hselasky@c2i.net) X-Cloudmark-Score: 0.000000 [] X-Cloudmark-Analysis: v=1.0 c=1 a=nyMGgD1UoDIA:10 a=A9fe73ChuGazO53Bn-QA:9 a=tT1I7HXlkSwwLqnn1rgcR8EGcWsA:4 a=SUW4-KwYzMtWZh0r:21 a=10-NGy_3TaLB5fVX:21 Received: from [81.191.55.181] (account mc467741@c2i.net HELO [10.36.2.183]) by mailfe01.swip.net (CommuniGate Pro SMTP 5.2.13) with ESMTPA id 180461597; Thu, 23 Apr 2009 14:34:11 +0200 From: Hans Petter Selasky To: freebsd-current@freebsd.org Date: Thu, 23 Apr 2009 14:36:43 +0200 User-Agent: KMail/1.9.7 References: <49ED3E7D.8080606@gddsn.org.cn> <200904212123.14016.hselasky@c2i.net> <49F05F8F.5000407@entel.upc.edu> In-Reply-To: <49F05F8F.5000407@entel.upc.edu> MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200904231436.43735.hselasky@c2i.net> Cc: freebsd-usb@freebsd.org, wsk Subject: Re: boot panic on current(04.20) X-BeenThere: freebsd-usb@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: FreeBSD support for USB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Apr 2009 12:34:14 -0000 On Thursday 23 April 2009, Gustau Perez wrote: > Hans Petter Selasky wrote: > > On Tuesday 21 April 2009, wsk wrote: > >> lists > >> boot panic on current(2009.04.20).it seems caused by usbus4 > >> > >> Root mount waiting for: usbus4 > >> uhub4: 8 ports with 8 removable, self powered > >> Root mount waiting for: usbus4 > >> ugen4.2: at usbus4 > >> Fatal trap 12: page fault while in kernel mode > >> cpuid = 0; apic id = 00 > >> fault virtual address = 0x0 > >> fault code = supervisor read, page not present > >> instruction pointer = 0x20:0xc08ed3a3 > >> stack pointer = 0x28:0xe4c38b40 > >> frame pointer = 0x28:0xe4c38b44 > >> 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 = 28 (usbus4) > >> trap number = 12 > >> panic: page fault > >> cpuid = 0 > >> uptime: 5s > >> Cannot dump. Device not defined or unavailable. > > > > Can you compile a kernel with debugging and get a backtrace? > > I'm trying to get the dump saved to /var/crash but seems it is not > working. As the crash happens before /etc/rc.d/dumpon executes, dumpon > doesn't get executed,so dumpdev doesn't point to the place where to save > the dump. > > I tried booting single user without loading both uhci and ehci. I > booted fined. I tried launching swapon /dev/ad4s3b and /etc/rc.d/dumpon > start. Looking at /dev/dumpdev it points to /dev/ad4s3b, fine. Compiled > the kernel with ; > > # Debugging for use in -current > options KDB # Enable kernel debugger support. > options DDB # Support DDB. > > and changed sysctl kern.coredump=1. > > Loading uchi throws me to the debugger (ok, that's what I wanted), > but the core is not saved to /dev/ad4s3b. Is there something I'm doing > wrong ? Am I missing something ? > > > Is the panic reproducible? > > Yes it is. When uhci.ko is loaded is panics. If you type "bt" in the debugger, what are the USB functions being called? --HPS