From owner-freebsd-stable@FreeBSD.ORG Wed Aug 9 10:15:21 2006 Return-Path: X-Original-To: freebsd-stable@freebsd.org Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1087616A4DE for ; Wed, 9 Aug 2006 10:15:21 +0000 (UTC) (envelope-from dom@goodforbusiness.co.uk) Received: from mailhost.graphdata.co.uk (mailhost.graphdata.co.uk [195.12.22.194]) by mx1.FreeBSD.org (Postfix) with ESMTP id 90DA043D45 for ; Wed, 9 Aug 2006 10:15:20 +0000 (GMT) (envelope-from dom@goodforbusiness.co.uk) Received: from localhost (localhost [127.0.0.1]) by mailhost.graphdata.co.uk (Postfix) with ESMTP id 453BA114037 for ; Wed, 9 Aug 2006 11:15:19 +0100 (BST) X-Virus-Scanned: amavisd-new at graphdata.co.uk Received: from mailhost.graphdata.co.uk ([127.0.0.1]) by localhost (mailhost.graphdata.co.uk [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 11mThJxwyBZU for ; Wed, 9 Aug 2006 11:15:16 +0100 (BST) Received: from [192.168.0.86] (gdc083.internal.graphdata.co.uk [192.168.0.86]) by mailhost.graphdata.co.uk (Postfix) with ESMTP id C28B5114032 for ; Wed, 9 Aug 2006 11:15:16 +0100 (BST) Message-ID: <44D9B5B4.7010208@goodforbusiness.co.uk> Date: Wed, 09 Aug 2006 11:15:16 +0100 From: Dominic Marks User-Agent: Thunderbird 1.5.0.4 (X11/20060718) MIME-Version: 1.0 To: freebsd-stable@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Device conflict 3ware twe and CMedia sound card X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Aug 2006 10:15:21 -0000 Hello, I seem to have a device conflict on my desktop. When attempting to fsck a gstripe volume attached via the twe card the system becomes 'choppy' and from looking at systat (when it isn't frozen) the system is receiving about 300k interrupts per second from the pcm device. If I leave the system in this state for a few minutes it will do an instant-reset, presumably because it can't cope. Verbose dmesg: http://goodforbusiness.co.uk/~dom/dmesg.boot Specific parts: twe0: <3ware Storage Controller. Driver version 1.50.01.002> port 0xdcb0-0xdcbf mem 0xdf000000-0xdf7fffff irq 49 at device 13.0 on pci3 twe0: Reserved 0x10 bytes for rid 0x10 type 4 at 0xdcb0 ioapic2: routing intpin 1 (PCI IRQ 49) to vector 49 twe0: [GIANT-LOCKED] twe0: AEN: twe0: 2 ports, Firmware FE8S 1.05.00.068, BIOS BE7X 1.08.00.048 twe0: Monitor ME7X 1.01.00.040, PCB Rev5 , Achip 3.20 , Pchip 1.30-66 twe0: port 0: WDC WD3200KS-00PFB0 305245MB twe0: port 1: WDC WD3200KS-00PFB0 305245MB pcm0: port 0xcc00-0xccff irq 17 at device 13.0 on pci7 pcm0: Reserved 0x100 bytes for rid 0x10 type 4 at 0xcc00 ioapic0: routing intpin 17 (PCI IRQ 17) to vector 55 pcm0: [MPSAFE] pcm0: sndbuf_setmap 3e8ee000, 4000; 0xe5408000 -> 3e8ee000 pcm0: sndbuf_setmap 3e8ea000, 4000; 0xe540c000 -> 3e8ea000 I believe I can use device.hints(5) to work around this, but I am unsure variable I can set in order to resolve this. Does the device 13.0 from dmesg refer to the 'drq' ? Thanks, Dominic