From owner-freebsd-current@FreeBSD.ORG Mon Aug 23 03:17:47 2010 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 5DBE010656A4 for ; Mon, 23 Aug 2010 03:17:47 +0000 (UTC) (envelope-from dougb@FreeBSD.org) Received: from mail2.fluidhosting.com (mx21.fluidhosting.com [204.14.89.4]) by mx1.freebsd.org (Postfix) with ESMTP id 08E2F8FC1D for ; Mon, 23 Aug 2010 03:17:46 +0000 (UTC) Received: (qmail 13433 invoked by uid 399); 23 Aug 2010 03:17:46 -0000 Received: from localhost (HELO lap.dougb.net) (dougb@dougbarton.us@127.0.0.1) by localhost with ESMTPAM; 23 Aug 2010 03:17:46 -0000 X-Originating-IP: 127.0.0.1 X-Sender: dougb@dougbarton.us Message-ID: <4C71E858.90009@FreeBSD.org> Date: Sun, 22 Aug 2010 20:17:44 -0700 From: Doug Barton Organization: http://SupersetSolutions.com/ User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.9.2.8) Gecko/20100807 Thunderbird/3.1.2 MIME-Version: 1.0 To: freebsd-current@freebsd.org, Andriy Gapon X-Enigmail-Version: 1.1.2 OpenPGP: id=1A1ABC84 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Subject: runaway intr problems: powerd and/or hw.acpi.cpu.cx_lowest related X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 23 Aug 2010 03:17:47 -0000 Thanks to help from Andriy I've been working on narrowing down the cause of my "runaway intr" problems and we've found some interesting things. First, if I use neither powerd nor set hw.acpi.cpu.cx_lowest less than C1 things seem to work fine. Using one or the other sort of works, but between the 2 powerd seems to cause the most problems. However, the more interesting thing is that generally the problem seems to be caused by contention on IRQ 20 between the following: 20 (ehci0) 20 (uhci0) 20 (hpet0) If I set the following in loader.conf: kern.eventtimer.timer1="i8254" kern.eventtimer.timer2="RTC" Then everything works (where "everything" is 40 minutes or so of watching a video that previously caused the runaway problem consistently in about 10-20 minutes, although in the past it sometimes took hours to manifest). Or, if I build a kernel with no USB (so IRQ 20 is no longer shared) then once again, everything works (as above) using: kern.eventtimer.timer1: LAPIC kern.eventtimer.timer2: HPET (I.e., the default) I also got another interesting set of data today from a "runaway intr" situation that did not involve swi:4. The symptoms were the same as previously, but the devices involved were totally different. This may have to do with the fact that I switched back to ULE for the testing today, and/or I hadn't set cx_lowest=C3. http://people.freebsd.org/~dougb/intr-out-3.txt This was with ULE + USB in the kernel, LAPIC/HPET, cx_lowest=C1, but running powerd with the following: powerd_flags="-a adaptive -b adaptive -n adaptive" ... and so it goes, Doug -- Improve the effectiveness of your Internet presence with a domain name makeover! http://SupersetSolutions.com/ Computers are useless. They can only give you answers. -- Pablo Picasso