Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 27 Oct 2003 22:59:10 +0100
From:      Thorsten Greiner <thorsten.greiner@web.de>
To:        Nate Lawson <nate@root.org>
Cc:        current@freebsd.org
Subject:   Re: ACPI trouble with EPIA-M
Message-ID:  <20031027215909.GA1108@tybalt>
In-Reply-To: <20031027123400.N78061@root.org>
References:  <20031023155431.L64034@root.org> <20031024212434.GA8126@tybalt> <20031027123400.N78061@root.org>

next in thread | previous in thread | raw e-mail | index | archive | help
* Nate Lawson <nate@root.org> [2003-10-27 22:13]:
> ...  What you probably want to do now is do "tr <pid>" for the
> pids below to see what they're blocked on.  Likely culprits are 24
> (since it's on irq 7), 23 (acpi), 29, and 25.  The most likely one
> is 24 because irq 7 is normally edge triggered/legacy and that
> means it cannot be shared.  But in your config, it is shared.  So
> my guess is that acpi is routing interrupts differently than $PIR
> mode.

OK, here we go:

pid 24 ([IWAIT] irq7: fwohci0 uhci1)
pid 35 ([IWAIT] irq0: ppc0)
pid 32 ([IWAIT] irq15: ata1)
pid 31 ([IWAIT] irq14: ata0)

stack trace:

    sched_switch()
    mi_switch()
    ithread_loop()
    fork_exit()
    fork_trampoline()

pid 23 (new [IWAIT] irq9: acpi0)
pid 29 (new [IWAIT] irq10: uhci2 pcm0)
pid 25 (new [IWAIT] irq11: vr0 uhci0)

stack trace (yes, this is just one line):

    fork_trampoline()

Hope that helps... (though I fear it does not)

Regards
        -Thorsten

-- 
There are 10 kinds of people in the world, those who
understand binary and those who don't.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20031027215909.GA1108>