Date: Mon, 18 Oct 2004 15:13:56 -0400 From: Anish Mistry <mistry.7@osu.edu> To: Poul-Henning Kamp <phk@phk.freebsd.dk> Cc: Nate Lawson <nate@root.org> Subject: Re: RELENG_5 panic: mtx_lock() with ACPI Message-ID: <200410181514.05861.mistry.7@osu.edu> In-Reply-To: <48908.1096571186@critter.freebsd.dk> References: <48908.1096571186@critter.freebsd.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
--nextPart16894977.buHMIWeCEl Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 a= ny=20 way I could provide more info? =2D-=20 Anish Mistry --nextPart16894977.buHMIWeCEl Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBdBX9xqA5ziudZT0RAt6HAJ0ZuKskQ+XyS+cT7+tBOjzWxp/RzwCdHYDh Z7pazBIxCsPfE0qIUN1sCUE= =50QH -----END PGP SIGNATURE----- --nextPart16894977.buHMIWeCEl--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200410181514.05861.mistry.7>