Re: Kernel Locks During Device Probe on 7.0 Current

It could be a problem of syscons.
Try the following patch or serial/dcons console, or disable HTT.

http://lists.freebsd.org/pipermail/freebsd-current/2007-August/076377.html

On 9/14/07, Dave Frantz <imperial_courier_at_yahoo.com> wrote:
> Actually, I didn't have bootverbose set. The same
> GENERIC kernel, with bootverbose and ACPI set, gives:
>
> subsystem 9000000
>    tcov_init(0)... done.
> subsystem a000000
>    synch_setup(0)... done.
> subsystem a800000
>    run_interrupt_driven_config_hooks(0)...rr232x: no
> controller detected
> acpi_acad0: acline initialization start
> acpi_acad0: On Line
> acpi_acad0: acline initialization done, tried 1 times
> battery0: battery initialization start
> battery0: battery initialization done, tried 1 times
>
> then hangs. With bootverbose set and with ACPI off, I
> get:
>
> subsystem 9000000
>    tcov_init(0)... done.
> subsystem a000000
>    synch_setup(0)... done.
> subsystem a800000
>    run_interrupt_driven_config_hooks(0)... rr232x: no
> controllers detected.
> firewire0: 2 nodes, maxhop <=1, cable IRM=1 (me)
> firewire0: bus manager 1 (me)
>
> and stop.
>
> I've compiled a new GENERIC kernel. The new
> 7.0-current kernel has VERBOSE_SYSINIT and ddb, and
> I've compiled out all Firewire devices (firewire, sbp,
> fwe, fwip, dcons, and dcons_crom.)
>
> The new kernel, with bootverbose and ACPI set, gives:
>
> subsystem 9000000
>    tcov_init(0)... done.
> subsystem a000000
>    synch_setup(0)... done.
> subsystem a800000
>    run_interrupt_driven_config_hooks(0)...rr232x: no
> controller detected
> acpi_acad0: acline initialization start
> acpi_acad0: On Line
> acpi_acad0: acline initialization done, tried 1 times
> battery0: battery initialization start
>
> then hangs. With bootverbose set and with ACPI off, I
> get:
>
> subsystem 9000000
>    tcov_init(0)... done.
> subsystem a000000
>    synch_setup(0)... done.
> subsystem a800000
>    run_interrupt_driven_config_hooks(0)... rr232x: no
> controllers detected.
>
> and then it hangs.
>
> I don't think Firewire is causing this, unfortunately.
> At least not directly.
>
> Thank you very much for your help, by the way.
>
> --- Kip Macy <kip.macy_at_gmail.com> wrote:
>
> > Try taking out firewire. And just to confirm  - you
> > have bootverbose set?
> >
> >  -Kip
> >
> > On 9/13/07, Dave Frantz <imperial_courier_at_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_at_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_at_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
> > >
> > _______________________________________________
> > freebsd-current_at_freebsd.org mailing list
> >
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> > To unsubscribe, send any mail to
> > "freebsd-current-unsubscribe_at_freebsd.org"
> >
>
>
>
>
>       ____________________________________________________________________________________
> Tonight's top picks. What will you watch tonight? Preview the hottest shows on Yahoo! TV.
> http://tv.yahoo.com/
>
> _______________________________________________
> freebsd-current_at_freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-current
> To unsubscribe, send any mail to "freebsd-current-unsubscribe_at_freebsd.org"
>
>


-- 
/\ Hidetoshi Shimokawa
\/  simokawa_at_FreeBSD.ORG