ACPI crash on lid close - SMP race? - Kernel

This is a discussion on ACPI crash on lid close - SMP race? - Kernel ; If the _DOS flag on my HP 2510p is set to 0 (ie, signal OS when screen notification is requested, don't change automatically) then it'll crash on random lid open/closes. The trace generally makes little sense and depends on the ...

+ Reply to Thread
Results 1 to 6 of 6

Thread: ACPI crash on lid close - SMP race?

  1. ACPI crash on lid close - SMP race?

    If the _DOS flag on my HP 2510p is set to 0 (ie, signal OS when screen
    notification is requested, don't change automatically) then it'll crash
    on random lid open/closes. The trace generally makes little sense and
    depends on the kernel version and phase of the moon. I'd ignored this as
    firmware brokenness up until lately, but since having _DOS set to 0 is
    the only way to get a notification when the display switch key is
    pressed on this machine I'd be interested in fixing it properly.

    Unfortunately, I've got no real idea what on earth is going on. The only
    clue I've found so far is that booting with maxcpus=1 leaves it working
    perfectly. What parts of the ACPI stack could be triggering this?

    --
    Matthew Garrett | mjg59@srcf.ucam.org
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  2. Re: ACPI crash on lid close - SMP race?

    On Mon, Nov 10, 2008 at 05:26:35PM +0000, Sergio Monteiro Basto wrote:
    > Hi, About this _DOS , I reported this problem a long time ago, which now
    > is on http://bugzilla.kernel.org/show_bug.cgi?id=6001
    > Could you put yours comment on it ?
    >
    > On fedora stock kernel, appears one patch, (Now I see that you are the
    > author )
    >
    > I tested your patch and it works for me !


    Yeah, that's the "safe" patch which stops us executing the codepath that
    breaks, but also means I don't get display switch events. Having it set
    to 1 means executing BIOS code that's likely to interfere with the rest
    of the system, so a crash isn't surprising. But a setting of 0 *should*
    be safe, and I'm quite confused as to why it's exploding.

    --
    Matthew Garrett | mjg59@srcf.ucam.org
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  3. Re: ACPI crash on lid close - SMP race?

    On Tue, Nov 11, 2008 at 09:27:14AM +0800, Zhang Rui wrote:
    > well, there is a bug report for this problem:
    > http://bugzilla.kernel.org/show_bug.cgi?id=11259


    I'll give the noirqbalance case a go.

    > and there are some bug reports for a similar problem (system crashes on
    > lid close if _DOS=1, but on a UP platform).
    > http://bugzilla.kernel.org/show_bug.cgi?id=6001#c49


    I think the _DOS=1 case is somewhat different. There you'd expect
    significantly more system BIOS code to be run, and that's going to stand
    a much higher chance of causing unfortunate interactions with however
    Linux has set up the graphics.

    --
    Matthew Garrett | mjg59@srcf.ucam.org
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  4. Re: ACPI crash on lid close - SMP race?

    well, there is a bug report for this problem:
    http://bugzilla.kernel.org/show_bug.cgi?id=11259

    and there are some bug reports for a similar problem (system crashes on
    lid close if _DOS=1, but on a UP platform).
    http://bugzilla.kernel.org/show_bug.cgi?id=6001#c49

    but unfortunately we haven't made any progress in this issue.

    thanks,
    rui

    On Tue, 2008-11-11 at 00:11 +0800, Matthew Garrett wrote:
    > If the _DOS flag on my HP 2510p is set to 0 (ie, signal OS when screen
    > notification is requested, don't change automatically) then it'll crash
    > on random lid open/closes. The trace generally makes little sense and
    > depends on the kernel version and phase of the moon. I'd ignored this as
    > firmware brokenness up until lately, but since having _DOS set to 0 is
    > the only way to get a notification when the display switch key is
    > pressed on this machine I'd be interested in fixing it properly.
    >
    > Unfortunately, I've got no real idea what on earth is going on. The only
    > clue I've found so far is that booting with maxcpus=1 leaves it working
    > perfectly. What parts of the ACPI stack could be triggering this?
    >


    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  5. Re: ACPI crash on lid close - SMP race?

    On Tue, Nov 11, 2008 at 09:59:38AM +0800, Zhang Rui wrote:

    > oops. sorry, I mean system crashes on lid close if _DOS=0 on some UP
    > platform.


    Oh, ugh. I don't have any with that issue, but that ought to be
    "interesting" to fix.

    --
    Matthew Garrett | mjg59@srcf.ucam.org
    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

  6. Re: ACPI crash on lid close - SMP race?

    On Tue, 2008-11-11 at 09:33 +0800, Matthew Garrett wrote:
    > On Tue, Nov 11, 2008 at 09:27:14AM +0800, Zhang Rui wrote:
    > > well, there is a bug report for this problem:
    > > http://bugzilla.kernel.org/show_bug.cgi?id=11259

    >
    > I'll give the noirqbalance case a go.
    >
    > > and there are some bug reports for a similar problem (system crashes on
    > > lid close if _DOS=1, but on a UP platform).
    > > http://bugzilla.kernel.org/show_bug.cgi?id=6001#c49

    >
    > I think the _DOS=1 case is somewhat different. There you'd expect
    > significantly more system BIOS code to be run, and that's going to stand
    > a much higher chance of causing unfortunate interactions with however
    > Linux has set up the graphics.
    >

    oops. sorry, I mean system crashes on lid close if _DOS=0 on some UP
    platform.

    thanks,
    rui


    --
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

+ Reply to Thread