From owner-freebsd-current@FreeBSD.ORG Mon Dec 22 15:49:20 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 16AE716A4CE for ; Mon, 22 Dec 2003 15:49:20 -0800 (PST) Received: from mailhub1.midco.net (mailhub1.midco.net [24.220.0.32]) by mx1.FreeBSD.org (Postfix) with ESMTP id D31FE43D1D for ; Mon, 22 Dec 2003 15:49:17 -0800 (PST) (envelope-from pmes@bis.midco.net) Received: (qmail 29771 invoked by uid 0); 22 Dec 2003 23:49:17 -0000 Received: from host-195-219-220-24.midco.net (HELO bis.midco.net) ([24.220.219.195]) (envelope-sender ) by lvs-pop.midco.net (qmail-ldap-1.03) with SMTP for ; 22 Dec 2003 23:49:17 -0000 Message-ID: <3FE782FC.5040408@bis.midco.net> Date: Mon, 22 Dec 2003 17:49:16 -0600 From: Peter Schultz User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.6b) Gecko/20031215 X-Accept-Language: en-us, en MIME-Version: 1.0 To: John Baldwin References: In-Reply-To: Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit cc: freebsd-current@freebsd.org Subject: Re: new interrupts not working for me X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Mon, 22 Dec 2003 23:49:20 -0000 John Baldwin wrote: > On 22-Dec-2003 Peter Schultz wrote: > >>John Baldwin wrote: >> >>>On 05-Nov-2003 Peter Schultz wrote: >>> >>> >>>>I have a Tyan S1832DL w/dual pii 350s and it's not able to boot. Seems >>>>to be having trouble with my adaptec scsi controller, I get a whole >>>>bunch of output like this hand transcribed bit, it comes after "waiting >>>>15 seconds for scsi devices to settle": >>>> >>>>ahc0 timeout SCB already complete interrupts may not be functioning >>>>Infinite interrupt loop INTSTAT=0(probe3:ahc0:0:3:0): SCB 0x6 - timed out >>>> >>>>Anyone else seeing this? There are probably 100+ related lines of >>>>output, I'll have to configure serial debugging if you need to see it. >>> >>> >>>The dmesg output excluding all the ahc0 errors would help figure out >>>why your interrupts aren't working. However, I just committed a patch >>>that might fix your problem. >>> >> >>Here is the output I was able to capture: > > > Disable ACPI for now. It looks like you have a buggy BIOS. > Can you put your ASL up at a URL somewhere? > http://bis.midco.net/pmes/tyan_s1832dl.asl Pete...