From owner-freebsd-current Mon Sep 4 13:15:57 2000 Delivered-To: freebsd-current@freebsd.org Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by hub.freebsd.org (Postfix) with ESMTP id 0F13337B422 for ; Mon, 4 Sep 2000 13:15:53 -0700 (PDT) Received: from teabag.demon.co.uk ([193.237.4.110]) by anchor-post-34.mail.demon.net with esmtp (Exim 2.12 #1) id 13W2el-000LKg-0Y for freebsd-current@freebsd.org; Mon, 4 Sep 2000 21:15:52 +0100 Received: from localhost (cbh@localhost) by teabag.demon.co.uk (8.11.0/8.9.3) with ESMTP id e84KEh560891 for ; Mon, 4 Sep 2000 21:14:51 +0100 (BST) (envelope-from cbh@teabag.demon.co.uk) Date: Mon, 4 Sep 2000 21:14:43 +0100 (BST) From: Chris Hedley X-Sender: cbh@teabag.cbhnet To: freebsd-current@freebsd.org Subject: Re: AIC-7890 problems with kernel build In-Reply-To: <200009041910.QAA08880@Den.BOFH.Halifax.NS.Ca> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, 4 Sep 2000, Brandon Hume wrote: > Just after the "waiting for SCSI devices to settle" message, I'll get a > number of SCB errors (which I don't have written down, unfortunately), and > then eventually a panic. This is with ACPI enabled... if I don't enable > ACPI, it will proceed immediately to the panic. Sounds similar to what I'm getting; after a boot I get a load of the following: ahc0: ahc_intr - referenced scb not valid during SELTO (31, 255) ahc1: ahc_intr - referenced scb not valid during SELTO (31, 139) followed by a panic: (probe0:ahc0:0:0:0): SCB 0x9 - timed out while idle, SEQADDR == 0xb panic: Waiting List inconsistency. SCB index == 255, yet numscbs == 20 (Being a technophobe I decided to write these down rather than dig out a breakout box to capture the serial port output!) Similar config to yours; a Tyan Thunder SMP BX with an onboard 7895 controller. I started getting this after my 29th Aug update, although this was a few days since the last working version I compiled (dmesg says the 24th so, er, I guess that's when it was) Lots of other blurb about "can't allocate register resources" for just about anything on the PCI bus, as I recall. Chris. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message