Date: Thu, 13 Sep 2007 21:30:26 -0700 From: "Kip Macy" <kip.macy@gmail.com> To: "Dave Frantz" <imperial_courier@yahoo.com> Cc: freebsd-current@freebsd.org Subject: Re: Kernel Locks During Device Probe on 7.0 Current Message-ID: <b1fa29170709132130o770440fcw10b386b6db9eaa04@mail.gmail.com> In-Reply-To: <352686.5608.qm@web53901.mail.re2.yahoo.com> References: <b1fa29170709131459k48633ffieb2da1cf8aafa374@mail.gmail.com> <352686.5608.qm@web53901.mail.re2.yahoo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Try taking out firewire. And just to confirm - you have bootverbose set? -Kip On 9/13/07, Dave Frantz <imperial_courier@yahoo.com> wrote: > Okay, I've recompiled the GENERIC 7.0-current kernel > with VERBOSE_SYSINIT. ddb is in the kernel too. > > Booting with the GENERIC kernel built with those > options and with ACPI enabled, I get: > > subsystem 9000000 > tcov_init(0)... done. > subsystem a000000 > synch_setup(0)... done. > subsystem a800000 > run_interrupt_driven_config_hooks(0)... > > And then the system hangs. I cannot break into ddb > with Ctrl+Alt+Esc at this point. > > If I disable ACPI and boot with the same kernel, I > get: > > > subsystem 9000000 > tcov_init(0)... done. > subsystem a000000 > synch_setup(0)... done. > subsystem a800000 > run_interrupt_driven_config_hooks(0)... firewire0: > 2 nodes, maxhop <=1, cable IRM=1 (me) > firewire0: bus manager 1 (me) > > And it hangs there. > > Any ideas on what I should do next? Thanks in advance. > > > > > --- Kip Macy <kip.macy@gmail.com> wrote: > > > Turn on VERBOSE_SYSINIT and ddb (although clock > > interrupts might not > > be running at that point). > > > > > > -Kip > > > > > > On 9/13/07, Dave Frantz <imperial_courier@yahoo.com> > > wrote: > > > I've been tracking 7.0 for several weeks now using > > > cvsup. Unfortunately, in this time, I haven't been > > > able to build a working kernel, even using > > GENERIC. > > > > > > When I try to use a 7.0 current kernel, the system > > > gets about 6/8ths through the device probe, then > > > simply stops. It does not visibly panic; it just > > stops > > > the device probe and does nothing. (It acts like > > the > > > kernel goes into a loop someplace and never gets > > out.) > > > This occurs whether ACPI is enabled or not. > > <snip> > > > > > ____________________________________________________________________________________ > Catch up on fall's hot new shows on Yahoo! TV. Watch previews, get listings, and more! > http://tv.yahoo.com/collections/3658 >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?b1fa29170709132130o770440fcw10b386b6db9eaa04>