From owner-freebsd-current@FreeBSD.ORG Fri Sep 14 07:17:58 2007 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 51BB816A419 for ; Fri, 14 Sep 2007 07:17:58 +0000 (UTC) (envelope-from imperial_courier@yahoo.com) Received: from web53907.mail.re2.yahoo.com (web53907.mail.re2.yahoo.com [206.190.36.217]) by mx1.freebsd.org (Postfix) with SMTP id 0C33013C480 for ; Fri, 14 Sep 2007 07:17:57 +0000 (UTC) (envelope-from imperial_courier@yahoo.com) Received: (qmail 11982 invoked by uid 60001); 14 Sep 2007 07:17:57 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID; b=SCfL3F1NlwtnJR+bah8w66bNjB3ftuuj9bwrS62sSnVNQap5aEKLnBYeWmzo1FWVC5jAAEhT7GLt1grkvc4XxocYemQmtniOEg+w36t/JFG2hxwAX+2InczRAR9C8SIWuMM3ItWYThHmukrZ6/1YoN/J4KqOms+LDbj7f3C6l24=; X-YMail-OSG: KEuNS6AVM1n905gh8eyej1NE62GoAy3BAImqCfGwkeuAOtpNHkZzwwcCxgXTLr.kEyHx8yuYMcnfMjgwbM4DU3PCBqTzqzxr6zOHN6qE0oRd5F3tL.s53hm40w-- Received: from [209.166.103.197] by web53907.mail.re2.yahoo.com via HTTP; Fri, 14 Sep 2007 00:17:57 PDT Date: Fri, 14 Sep 2007 00:17:57 -0700 (PDT) From: Dave Frantz To: Hidetoshi Shimokawa In-Reply-To: <626eb4530709132342xef398f6gd16424aac395d6dc@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <246729.11385.qm@web53907.mail.re2.yahoo.com> Cc: Kip Macy , freebsd-current@freebsd.org Subject: Re: Kernel Locks During Device Probe on 7.0 Current 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: Fri, 14 Sep 2007 07:17:58 -0000 I just tried disabling HTT. Unfortunately, it still crashes in the exact same way. Thanks for the idea, though. --- Hidetoshi Shimokawa wrote: > 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 > 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 wrote: > > > > > Try taking out firewire. And just to confirm - > you > > > have bootverbose set? > > > > > > -Kip > > > > > > On 9/13/07, Dave Frantz > > > > 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 wrote: > > > > > > > > > Turn on VERBOSE_SYSINIT and ddb (although > clock > > > > > interrupts might not > > > > > be running at that point). > > > > > > > > > > > > > > > -Kip > > > > > > > > > > > > > > > On 9/13/07, Dave Frantz > > > > > > > > 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. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > ____________________________________________________________________________________ > > > > Catch up on fall's hot new shows on Yahoo! TV. > > > Watch previews, get listings, and more! > > > > http://tv.yahoo.com/collections/3658 > > > > > === message truncated === ____________________________________________________________________________________ Pinpoint customers who are looking for what you sell. http://searchmarketing.yahoo.com/