From owner-freebsd-current Tue Dec 10 10:50:21 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 65D0D37B401; Tue, 10 Dec 2002 10:50:19 -0800 (PST) Received: from tasogare.imasy.or.jp (tasogare.imasy.or.jp [202.227.24.5]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3893A43EB2; Tue, 10 Dec 2002 10:50:17 -0800 (PST) (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) Date: Wed, 11 Dec 2002 03:49:37 +0900 (JST) 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 Subject: Re: pcm remaining problem (possible ACPI too) From: Mitsuru IWASAKI 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 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG 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: on motherboard # I worry about this... :P Thanks To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message