From owner-acpi-jp@jp.FreeBSD.org Wed Dec 11 03:50:21 2002
Received: (from daemon@localhost)
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) id gBAIoLC89959;
	Wed, 11 Dec 2002 03:50:21 +0900 (JST)
	(envelope-from owner-acpi-jp@jp.FreeBSD.org)
Received: from tasogare.imasy.or.jp (root@tasogare.imasy.or.jp [202.227.24.5])
	by castle.jp.FreeBSD.org (8.11.6+3.4W/8.11.3) with ESMTP/inet id gBAIoK289948
	for <acpi-jp@jp.freebsd.org>; Wed, 11 Dec 2002 03:50:20 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Received: from localhost (iwa@tasogare.imasy.or.jp [202.227.24.5])
	by tasogare.imasy.or.jp (8.11.6+3.4W/8.11.6/tasogare) with ESMTP/inet id gBAInti25264;
	Wed, 11 Dec 2002 03:49:55 +0900 (JST)
	(envelope-from iwasaki@jp.FreeBSD.org)
Message-Id: <20021211.034937.113704719.iwasaki@jp.FreeBSD.org>
To: clive@tongi.org
Cc: cg@freebsd.org, freebsd-current@freebsd.org, acpi-jp@jp.FreeBSD.org
From: Mitsuru IWASAKI <iwasaki@jp.FreeBSD.org>
In-Reply-To: <20021206170044.GA96839@fatpipi.cirx.org>
References: <20021206170044.GA96839@fatpipi.cirx.org>
X-Mailer: Mew version 2.2 on Emacs 20.7 / Mule 4.0 (HANANOEN)
Mime-Version: 1.0
Content-Type: Text/Plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: acpi-jp@jp.FreeBSD.org
Precedence: list
Date: Wed, 11 Dec 2002 03:49:37 +0900
X-Sequence: acpi-jp 2031
Subject: [acpi-jp 2031] Re: pcm remaining problem (possible ACPI too)
Errors-To: owner-acpi-jp@jp.FreeBSD.org
Sender: owner-acpi-jp@jp.FreeBSD.org
X-Originator: iwasaki@jp.FreeBSD.org
X-Distribute: distribute version 2.1 (Alpha) patchlevel 24e+021210

Hi,

>     Since rescent -CURRENT is stable enough, I have the chance to find
> out remaining pcm problem. My MP box no more has double fatal fault
> and turns into random sleep. The random sleep happens after pcm having
> its own problem.
> 
>     uname -av is
> FreeBSD cartier.home 5.0-CURRENT FreeBSD 5.0-CURRENT #1: Wed Dec  4 23:07:36 CST 2002     root@cartier.home:/usr/obj/usr/src/sys/GENERI  i386
> 
>     Kernel config is simply a modified GENERIC, with options SMP,
> APIC_IO, and ident GENERI.
> 
>     Below is what I've got in my dmesg. Complete dmesg is at
> http://fatpipi.cirx.org/~clive/cartier_dmesg.txt
> 
> lock order reversal
>  1st 0xc6992900 pipe mutex (pipe mutex) @ /usr/src/sys/kern/sys_pipe.c:465
>  2nd 0xc0524600 sigio lock (sigio lock) @ /usr/src/sys/kern/kern_sig.c:2225
> acquiring duplicate lock of same type: "pcm channel"
>  1st pcm0:record:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
>  2nd pcm0:play:0 @ /usr/src/sys/dev/sound/pcm/sound.c:191
> wakeup from sleeping state (slept 00:02:06)
> ata0: resetting devices ..
> done

I think the real problem is in pcm on MP system as you said, IRQ 9 maybe
shared with pcm0 and acpi.  Could you show me this?
 # acpidump | grep SCI_INT

Also, I'd like to see which acpi event was occured on ramdom sleep.
Backtrace is helpful to track this down.
Press Ctrl+Alt+Esc into DDB, enter
 db> b acpi_SetSleepState
to set break point, then send me the output of
 db> t
when the ramdom sleep is occurred.

BTW, you can set ignoring some of acpi events like this:
 # sysctl hw.acpi.power_button_state=NONE
 # sysctl hw.acpi.sleep_button_state=NONE
 # sysctl hw.acpi.lid_switch_state=NONE

> acpi0: <RCC    RCCNILE > on motherboard
# I worry about this... :P

Thanks
