From owner-freebsd-current@FreeBSD.ORG Sat Feb 10 19:21:42 2007 Return-Path: X-Original-To: current@FreeBSD.org Delivered-To: freebsd-current@FreeBSD.ORG Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5164A16A406; Sat, 10 Feb 2007 19:21:42 +0000 (UTC) (envelope-from Yuriy.Tsibizov@gfk.ru) Received: from mx.gfk.ru (mx.gfk.ru [84.21.231.130]) by mx1.freebsd.org (Postfix) with ESMTP id 55B1613C441; Sat, 10 Feb 2007 19:21:41 +0000 (UTC) (envelope-from Yuriy.Tsibizov@gfk.ru) Received: from ex.hhp.local by mx.gfk.ru (MDaemon PRO v9.5.3) with ESMTP id md50000899312.msg; Sat, 10 Feb 2007 22:02:51 +0300 Received: from dialup-chibis.gfk.ru ([10.0.6.45]) by ex.hhp.local with Microsoft SMTPSVC(6.0.3790.1830); Sat, 10 Feb 2007 22:03:31 +0300 Date: Sat, 10 Feb 2007 22:02:45 +0300 (MSK) From: Yuriy Tsibizov X-X-Sender: chibis@free.home.local To: Rink Springer In-Reply-To: <20070209182021.GA63685@rink.nu> Message-ID: <20070210213917.G45255@free.home.local> References: <20070209182021.GA63685@rink.nu> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed X-OriginalArrivalTime: 10 Feb 2007 19:03:31.0690 (UTC) FILETIME=[27F70CA0:01C74D46] X-Spam-Processed: mx.gfk.ru, Sat, 10 Feb 2007 22:02:51 +0300 (not processed: message from valid local sender) X-MDRemoteIP: 10.0.0.30 X-Return-Path: Yuriy.Tsibizov@gfk.ru X-Envelope-From: Yuriy.Tsibizov@gfk.ru X-MDAV-Processed: mx.gfk.ru, Sat, 10 Feb 2007 22:02:52 +0300 Cc: current@FreeBSD.org, multimedia@FreeBSD.org Subject: Re: snd_emu10k1 tremendous interrupt load? 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: Sat, 10 Feb 2007 19:21:42 -0000 > Hi people, > > Over the last few days, my CURRENT box has started to slow down to a > crawl. top(1) reports most CPU load is spent on interrupts, and a quick > vmstat -i to support this completely: > > interrupt total rate > irq1: atkbd0 1631 0 > irq15: ata1 14197 2 > irq16: pcm0 1056243398 160109 Rate for emu10k1 cards should be arount 48 interrupts/s. Do you record or play sound? Can you see any changes in interrupt rate when you change hw.snd.latency_profile? You can also try to go back to dev/sound/pcm before 2007-02-01 09:30. > Does anyone have any ideas why this is happening? Quick inspection of > /sys/dev/sound/pci/emu10k1.c:emu_intr() seems to hint that the > emu_rd(sc, IPR, 4) value takes a long time to clear, anyone have more > hints on this annoying behaviour? It may take some time because usual read rate should be around 48-96 reads/second and HW can't survive high register I/O rate. Other possibility is very low HW timer settings (like "interrupt after each 16 bytes", that is very unusual too) that will re-set this register after very small delay, comparable with duration of sound buffer callbacks. This will keep driver in interrupt loop and slow down everything. snd_emu10kx may work better in this situation (it uses different timer interrupt settings). Yuriy.