From owner-freebsd-stable@FreeBSD.ORG Sat Sep 25 20:29:24 2004 Return-Path: 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 6519716A4CE for ; Sat, 25 Sep 2004 20:29:24 +0000 (GMT) Received: from carver.gumbysoft.com (carver.gumbysoft.com [66.220.23.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 52B6C43D31 for ; Sat, 25 Sep 2004 20:29:24 +0000 (GMT) (envelope-from dwhite@gumbysoft.com) Received: by carver.gumbysoft.com (Postfix, from userid 1000) id 4502772DD4; Sat, 25 Sep 2004 13:29:24 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by carver.gumbysoft.com (Postfix) with ESMTP id 42D5972DCB; Sat, 25 Sep 2004 13:29:24 -0700 (PDT) Date: Sat, 25 Sep 2004 13:29:24 -0700 (PDT) From: Doug White To: =?ISO-8859-1?Q?Eirik_=D8verby?= In-Reply-To: <5390CF52-0D22-11D9-862C-000D9335BCEC@anduin.net> Message-ID: <20040925132827.G65556@carver.gumbysoft.com> References: <41519A92.3070503@anduin.net> <20040922191436.A36124@carver.gumbysoft.com> <5390CF52-0D22-11D9-862C-000D9335BCEC@anduin.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=X-UNKNOWN Content-Transfer-Encoding: QUOTED-PRINTABLE cc: stable@freebsd.org Subject: Re: Obscure errors in dmsg, system instability X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Sep 2004 20:29:24 -0000 On Thu, 23 Sep 2004, [ISO-8859-1] Eirik =D8verby wrote: > On 23. Sep 2004, at 04:15, Doug White wrote: > > > Is something sharing an interrupt with that device? > > > > PCI bus errors are generally Bad News .. either some device or the > > mobo is inroducing errors. > > Well.. Yes, there is some interrupt sharing. Relevant parts of dmsg: > > [ltning@carnen] ~$ dmesg | grep "irq 2" > IOAPIC #0 intpin 19 -> irq 2 > uhci0: port 0xd400-0xd41f irq > 2 at device 4.2 on pci0 > ahc0: port 0xd000-0xd0ff mem > 0xe2000000-0xe2000fff irq 2 at device 6.0 on pci0 > amr0: mem 0xe3000000-0xe300ffff irq 2 at device 9.1 > on pci0 Apparently one of these devices doesn't like getting an interrupt when there's no data pending. It might be a FreeBSD driver bug, but being a 3-way share it'll make it hard to untangle. > I don't like the fact that the LSI and the Adaptec are sharing IRQs, > given that the LSI is the main system drive controller (which is why I > don't use the Adaptec at all - and it cannot be disabled in BIOS I > think!)... > > I should perhaps try to reallocate some of the IRQs, but I don't really > have a clue how to do that, since I have no VGA in that box.. Ohwell, I > guess I just have to rip it open ;) Yah .. rearrange the cards in the slots and see what you can convince it to do. --=20 Doug White | FreeBSD: The Power to Serve dwhite@gumbysoft.com | www.FreeBSD.org