Re: [issue531] ACPI bugs on Intel motherboards

[YONETANI Tomokazu <qhwt+dfly@xxxxxxxxxx>]

On Tue, Jan 23, 2007 at 06:22:59PM +0900, YONETANI Tomokazu wrote:
> On Mon, Jan 22, 2007 at 10:59:06PM -0000, eugene wrote:
> > Here is the output of "trace":
> > lwkt_sendmsg(10,c810bee0,c18af23c,ccbfccc4) at lwkt_sendmsg+0x4a
>                ~~
> > AcpiOsExecute(2,c0736ab7,c18af23c,102f,0) at AcpiOsExecute+0x6f
> > AcpiEvGpeDispatch(c18af23,1d,c1706b15,3,0) at AcpiEvGpeDispatch+0x11f
> > AcpiEvGpeDetect(c15a1940,c0614550,ccbfcd1c,c0758a25,c15a1940) at
> > AcpiEvGpeDetect+0xd7
> > AcpiEvSciXruptHandler(c15a1940,0,ccbfcd84,c02b21d9,c15a1940) at
> > AcpiEvSciXruptHandler+0x19
> > InterruptWrapper(c15a1940,0,0,0,1) at InterruptWrapper+0x2b
> > ithread_handler(9,0,0,0,0) at ithread_handler+0x9d
> > lwkt_exit() at lwkt_exit
> > db>
> 
> Looks to me like acpi_task_thread is used (via AcpiOsExecute())
> before the msgport is initialized, but it shouldn't happen since
> most part of acpi_attach() is protected by critical section, which
> suspends the interrupt.  This is just a shot in the dark, but I wonder
> what happens if you move up the call to acpi_task_thread_init()
> before the call to AcpiEnableSubsystem(), which installs the interrupt
> handler called above (patch attached)?

> Index: acpi.c
[snip]

Hi,
I committed this (with slight modification) patch, as this shouldn't do
any harm anyway, and I wanted to narrow down the possible cause.  Please
let me know if anyone else still has the similar problem with updated
source.

Cheers.