Date: Tue, 4 Jan 2005 09:01:21 -0500 From: Anish Mistry <mistry.7@osu.edu> To: Nate Lawson <nate@root.org> Cc: freebsd-acpi@freebsd.org Subject: Re: RELENG_5 panic: mtx_lock() with ACPI Message-ID: <200501040901.29358.mistry.7@osu.edu> In-Reply-To: <41783E96.90908@root.org> References: <48908.1096571186@critter.freebsd.dk> <200410211526.48432.mistry.7@osu.edu> <41783E96.90908@root.org>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --]
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="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
to -STABLE and removed that and the system now boots with ACPI.
--
Anish Mistry
[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (FreeBSD)
iD8DBQBB2qG5xqA5ziudZT0RArt1AJ4l/D5qUAbwPlB1LzD7TDtl0jZe3wCgtxpf
04hvrzGe4h3WA+Nsf6Q9ocE=
=MHx5
-----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200501040901.29358.mistry.7>