From owner-freebsd-current@FreeBSD.ORG Fri Sep 14 05:44:05 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 11E3416A417 for ; Fri, 14 Sep 2007 05:44:05 +0000 (UTC) (envelope-from imperial_courier@yahoo.com) Received: from web53901.mail.re2.yahoo.com (web53901.mail.re2.yahoo.com [206.190.36.211]) by mx1.freebsd.org (Postfix) with SMTP id CAEC713C45D for ; Fri, 14 Sep 2007 05:44:04 +0000 (UTC) (envelope-from imperial_courier@yahoo.com) Received: (qmail 51345 invoked by uid 60001); 14 Sep 2007 05:44:04 -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=a5vCxTLUjT0lUVek4fewptk2+sT7gUoAHWDZGHnf33oKuQsaEakxdDMdwy9XvJ+y37u0xNEPMODh2wQBrr8MF8Wkh+ra/92Yf+VcI/5hmgJkC0DYfqepXTar/itpGimY6iV++mB+GPki2rOQJihCtC9g+NpOb/pnhJKel2Gy0YU=; X-YMail-OSG: 6Ado.g8VM1nGn3Lxi1tzM78qXTf4HM7KcxPEBRlMkM9Di8_jGJsfp7B3pqpZP22igA-- Received: from [209.166.103.197] by web53901.mail.re2.yahoo.com via HTTP; Thu, 13 Sep 2007 22:44:03 PDT Date: Thu, 13 Sep 2007 22:44:03 -0700 (PDT) From: Dave Frantz To: Kip Macy In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Message-ID: <978104.51071.qm@web53901.mail.re2.yahoo.com> Cc: 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 05:44:05 -0000 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 > > > _______________________________________________ > 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" > ____________________________________________________________________________________ Tonight's top picks. What will you watch tonight? Preview the hottest shows on Yahoo! TV. http://tv.yahoo.com/