Date: Thu, 23 Apr 2009 14:42:19 +0200 From: "Paul B. Mahol" <onemda@gmail.com> To: Gustau Perez <gperez@entel.upc.edu> Cc: current@freebsd.org Subject: Re: boot panic on current(04.20) Message-ID: <3a142e750904230542l14a742aw6aa37205a3da054d@mail.gmail.com> In-Reply-To: <49F05F8F.5000407@entel.upc.edu> References: <49ED3E7D.8080606@gddsn.org.cn> <200904212123.14016.hselasky@c2i.net> <49F05F8F.5000407@entel.upc.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
On 4/23/09, Gustau Perez <gperez@entel.upc.edu> 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: <NEC> 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 ? ddb(4) > >> Is the panic reproducible? >> > > Yes it is. When uhci.ko is loaded is panics. >> --HPS >> > > Regards, > > Gus >> _______________________________________________ >> freebsd-current@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-current >> To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >> > > _______________________________________________ > freebsd-current@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" > -- Paul
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3a142e750904230542l14a742aw6aa37205a3da054d>