From owner-freebsd-acpi@FreeBSD.ORG Tue Jan 4 13:58:03 2005 Return-Path: Delivered-To: freebsd-acpi@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 66BF116A4CE for ; Tue, 4 Jan 2005 13:58:03 +0000 (GMT) Received: from crumpet.united-ware.com (ddsl-66-42-172-210.fuse.net [66.42.172.210]) by mx1.FreeBSD.org (Postfix) with ESMTP id B373143D5D for ; Tue, 4 Jan 2005 13:58:02 +0000 (GMT) (envelope-from mistry.7@osu.edu) Received: from [192.168.0.5] (adsl-69-208-54-135.dsl.wotnoh.ameritech.net [69.208.54.135]) (authenticated bits=0)j04DYZWp044934 (version=TLSv1/SSLv3 cipher=RC4-MD5 bits=128 verify=NO); Tue, 4 Jan 2005 08:34:37 -0500 (EST) (envelope-from mistry.7@osu.edu) From: Anish Mistry To: Nate Lawson Date: Tue, 4 Jan 2005 09:01:21 -0500 User-Agent: KMail/1.7 References: <48908.1096571186@critter.freebsd.dk> <200410211526.48432.mistry.7@osu.edu> <41783E96.90908@root.org> In-Reply-To: <41783E96.90908@root.org> MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart3011248.Fb2WFiFyWU"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200501040901.29358.mistry.7@osu.edu> X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=no version=2.64 X-Spam-Checker-Version: SpamAssassin 2.64 (2004-01-11) on crumpet.united-ware.com cc: freebsd-acpi@freebsd.org Subject: Re: RELENG_5 panic: mtx_lock() with ACPI X-BeenThere: freebsd-acpi@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 04 Jan 2005 13:58:03 -0000 --nextPart3011248.Fb2WFiFyWU Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 21 October 2004 06:56 pm, you wrote: > Anish Mistry wrote: > > On Monday 18 October 2004 03:35 pm, you wrote: > >>Anish Mistry wrote: > >>>On Thursday 30 September 2004 03:06 pm, Poul-Henning Kamp wrote: > >>>>In message <415C4F5A.2080701@root.org>, Nate Lawson writes: > >>>>>I assume phk would be handling this since it's in the tty code. If > >>>>> not, please let us know so one of us can address this before the > >>>>> release. > >>>>> > >>>>>>>>struct tty * > >>>>>>>>ttymalloc(struct tty *tp) > >>>>>>>>{ > >>>>>>>> static int once; > >>>>>>>> > >>>>>>>> if (!once) { > >>>>>>>> mtx_init(&tty_list_mutex, "ttylist", NULL, > >>>>>>>> MTX_DEF); once++; > >>>>>>>> } > >>>>>>>> > >>>>>>>>This code is not MP safe as multiple processors could attempt to > >>>>>>>> call mtx_init() twice. > >>>> > >>>>We have no calls to ttymalloc() which are not protected by Giant, > >>>>so this theory doesn't explain the problem. > >>> > >>>Any progress, I'd hate to have to disable ACPI for the release. Is > >>> there any way I could provide more info? > >> > >>I'll try to look at it on the bus tonight. See if you can narrow down > >>if one ACPI component is contributing to this, i.e. > >>debug.acpi.disabled=3D"cpu" or whatever (see acpi.4 for the full list). > >>The sysctl run from the rc scripts to get entropy is what triggers the > >>panic. > > > > My monitor died, sorry for the slow response. > > Well I've gone through to try to figure out which component is causing > > the issue, and I've narrowed it down to 3. I couldn't get any better > > since when one of these are disabled then the hard drives aren't > > detect and thus can't boot. > > pci bus children > > > >>I have no idea how acpi can affect the tty mutex. > > Interesting, I'll try to look into this in more detail. I'm just > slammed with work at my Real Job currently. I just found the problem. I had viapm in my kernel config. I've updated=20 to -STABLE and removed that and the system now boots with ACPI. =2D-=20 Anish Mistry --nextPart3011248.Fb2WFiFyWU Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQBB2qG5xqA5ziudZT0RArt1AJ4l/D5qUAbwPlB1LzD7TDtl0jZe3wCgtxpf 04hvrzGe4h3WA+Nsf6Q9ocE= =MHx5 -----END PGP SIGNATURE----- --nextPart3011248.Fb2WFiFyWU--