DragonFlyBSD

do you get a
db>

prompt there? could you submit the output of "trace"?

thanks
simon

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>

~~

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)?

Cheers.

[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.

That's very good!
Sorry but I haven't got sources for world from that date - the bug was on a CD.
I'm very grateful to You.

Hi, eugene,
does that mean that the problem is solved in the more recent version
of Live CD, or just that you couldn't try the patch because you couldn't
download the source tree for some reason? FWIW I built the patched
module and put here:
http://les.ath.cx/DragonFly/issue531.zip
(les.ath.cx should resolve to 61.205.61.15)

the driver for UP kernel is named acpi-up.ko, and SMP acpi-smp.ko .
The module is built without -march= option, so it should work on any
x86-ish CPUs. The only problem is I'm not sure if or how it's possible
to boot with the LiveCD and load the driver from floppy disk or other
stuff...

Cheers.

Really there were both ways :) - the problem is really solved in more latest
version (I've tried to start from a 1.8-release CD) and I was not able to
download sources for that date for some days. Now I'd simply downloaded release
ISO and tried on the same machine - everything is OK.

Thank You!