From owner-freebsd-current@FreeBSD.ORG Mon Oct 27 12:39:26 2003 Return-Path: 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 89B1A16A4B3 for ; Mon, 27 Oct 2003 12:39:26 -0800 (PST) Received: from rootlabs.com (root.org [67.118.192.226]) by mx1.FreeBSD.org (Postfix) with SMTP id B7D7043FB1 for ; Mon, 27 Oct 2003 12:39:25 -0800 (PST) (envelope-from nate@rootlabs.com) Received: (qmail 78096 invoked by uid 1000); 27 Oct 2003 20:39:26 -0000 Date: Mon, 27 Oct 2003 12:39:26 -0800 (PST) From: Nate Lawson To: Thorsten Greiner In-Reply-To: <20031024212434.GA8126@tybalt> Message-ID: <20031027123400.N78061@root.org> References: <20031023155431.L64034@root.org> <20031024212434.GA8126@tybalt> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: ACPI trouble with EPIA-M X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2003 20:39:26 -0000 On Fri, 24 Oct 2003, Thorsten Greiner wrote: > * Nate Lawson [2003-10-24 22:57]: > > Type "tr" at the DDB prompt to get a trace of what is hanging. > > At the time of the hang a 'ps' in DDB shows two screenful's of > processes. Doing a simple 'tr' just gives the backtrace of how I got > into DDB which - I presume - is not relevant to this problem. Yes, that's true. What you probably want to do now is do "tr " 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. > I have no serial console, so I have to copy things by hand. A ps > shows (only selected columns): > > pid ... flag stat ... > 38 0000204 new [IWAIT] irq8: rtc > 37 0000204 new [IWAIT] irq4: sio0 > 36 0000204 new [IWAIT] swi0: tty:sio > 35 0000204 [IWAIT] irq0: ppc0 > 34 0000204 new [IWAIT] irq12: psm0 > 33 0000204 [CPU0] irq1: atkbd0 > 32 0000204 [IWAIT] irq15: ata1 > 31 0000204 [IWAIT] irq14: ata0 > 30 0000204 [SLP]usbdly 0x... usb2 > 29 0000204 new [IWAIT] irq10: uhci2 pcm0 > 28 0000204 [SLP] usbdly 0x... usb1 > 27 0000204 [SLP] usbtsk 0x... usbtask > 26 0000204 [SLP] usbdly 0q... usb0 > 25 0000204 new [IWAIT] irq11: vr0 uhci0 > 24 0000204 [IWAIT] irq7: fwohci0 uhci1 > 8 0000204 [SLP]actask 0x... acpi_task2 > 7 0000204 [SLP]actask 0x... acpi_task1 > 6 0000204 [SLP]actask 0x... acpi_task0 > 23 0000204 new [IWAIT] irq9: acpi0 > 22 0000204 new [IWAIT] irq13: > 21 0000204 new [IWAIT] swi3: cambio > 20 0000204 new [IWAIT] swi2: camnet > 19 0000204 new [IWAIT] swi5:+ > 5 0000204 [SLP]tqthr 0x... taskqueue > 18 0000204 [IWAIT] swi7: acpitaskq > 17 0000204 [IWAIT] swi6:+ > 16 0000204 [IWAIT] swi6: task queue > 15 0000204 [SLP]- 0x... random > 4 0000204 [SLP]- 0x... g_down > 3 0000204 [SLP]- 0x... g_up > 2 0000204 [SLP]- 0x... g_event > 14 0000204 new [IWAIT] swi5: vm > 13 000020c new [IWAIT] swi8: tty:sio clock > 12 0000204 new [IWAIT] swi1: net > 11 000020c [Can run] idle > 1 0000200 new [INACTIVE] swapper > 10 0000204 [CV]ktrace 0x... ktrace > 0 0000200 [SLP]conifhk 0x... swapper > > This state seems to be pretty reproducible. Any idea what is wrong? Something is blocked, no idea exactly what without more info. I have an EPIA-M 6000 but it's not set up. Perhaps I'll find some time to boot current on it to see. -Nate