From owner-freebsd-current@FreeBSD.ORG Sat Aug 14 16:54:16 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 6963C1065672; Sat, 14 Aug 2010 16:54:16 +0000 (UTC) (envelope-from bf1783@googlemail.com) Received: from mail-ww0-f50.google.com (mail-ww0-f50.google.com [74.125.82.50]) by mx1.freebsd.org (Postfix) with ESMTP id D1E9D8FC17; Sat, 14 Aug 2010 16:54:15 +0000 (UTC) Received: by wwb24 with SMTP id 24so1358053wwb.31 for ; Sat, 14 Aug 2010 09:54:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:mime-version:received:received:reply-to:date :message-id:subject:from:to:cc:content-type; bh=Y4STPkGX7zMxujkAWn3zI9hqbEmQs9jsWgbNSC6ZRh4=; b=WUkdpRt9ZiK67IyRads33dJAZxrkEUfPxqtcizYT3xb4A/ZMHpF3HMTTYGE6AQruJF xCVx9J5HKqprp97By91yJ2WtA5kMC0wS155b/Dnv8dpUdfdh3dXueUd+0Y30aJcbzm04 8f5ZE80AwzfpV0nrlZkCT6BzAkHn4WlWPzSmQ= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=mime-version:reply-to:date:message-id:subject:from:to:cc :content-type; b=v2r0Et2O2K26V1mU3fYwGyX3jhK70Tts3Nj/9grmmlO66lO7lcdORaLdauWS50ld2M jebuKAVqIdwmZk7QwAia9/kltnWAUxWALrQphZhOyTJMTkJ2guxTngyJV83naFAFrzkx c8EIawxadL2lAOBLdGbxq924RmhiILPN7TdT8= MIME-Version: 1.0 Received: by 10.216.5.79 with SMTP id 57mr764094wek.93.1281804854803; Sat, 14 Aug 2010 09:54:14 -0700 (PDT) Received: by 10.216.183.212 with HTTP; Sat, 14 Aug 2010 09:54:14 -0700 (PDT) Date: Sat, 14 Aug 2010 16:54:14 +0000 Message-ID: From: "b. f." To: freebsd-current@FreeBSD.org Content-Type: text/plain; charset=ISO-8859-1 Cc: Doug Barton Subject: Re: Runaway intr, not flash related X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: bf1783@gmail.com List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 14 Aug 2010 16:54:16 -0000 >My "runaway intr" problem with flash has been continuing all along, but >since no one has been interested in helping with it I haven't reported >it for a while. However, today, for the first time, it happened when I >had not run flash at all since I booted. > >My system: >Dell D620, C2D, i386, SMP, r210908 > >swi4: clock is the culprit again this time, but when flash triggers this >problem I sometimes see hdac as the culprit, FYI. I wouldn't say that no one is interested in helping. (And I think you've received a few more suggestions than your other recent message to freebsd-developers suggests.) For my part, I find it a bit difficult to track the status of your interrupt problem, and the interactivity problem, which may or may not be related. --Have you ruled out any contribution from overheating, like I think you were experiencing before with this machine? At one point, you were following some of mav@'s suggestions for power-saving, but then you posted a configuration that suggested that you had abandoned some of these settings and returned to the defaults. So are you running hot, or being throttled now? Have you tried running at a kern.hz < 1000, with throttling disabled, to see if that ameliorates the problem? --What graphics driver are you using? You were using x11/nvidia-driver, but then after the kib@ and alc@'s vm changes that led to problems with that driver, I thought you were using x11-drivers/xf86-video-nv -- is that still the case? Does switching drivers seem to influence the frequency or severity of the problems? --When do you experience these problems? Do they ever occur when you are _not_ running X? Have you tried temporarily disabling your usb and network devices, to see if they are contributing to the problem? Are you able to watch flash videos from local media, as opposed to those from a remote site, without problems? --Did you follow mav@'s suggestion to use something other than your hpet for the eventcounter and timecounter? The possible use of the hpet is one of the main differences between the new and old timing code, and you reported some problems with your hpet earlier. --Did you follow attilio@'s suggestion to obtain scheduling traces for the interactivity problem, as described in src/tools/sched/schedgraph.py? b.