From owner-freebsd-scsi@FreeBSD.ORG  Mon Sep 15 22:38:34 2003
Return-Path: <owner-freebsd-scsi@FreeBSD.ORG>
Delivered-To: freebsd-scsi@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id A7C3716A4B3
	for <freebsd-scsi@freebsd.org>; Mon, 15 Sep 2003 22:38:34 -0700 (PDT)
Received: from w250.z064001178.sjc-ca.dsl.cnc.net
	(adsl-66.218.45.239.dslextreme.com [66.218.45.239])
	by mx1.FreeBSD.org (Postfix) with SMTP id C039F43FBF
	for <freebsd-scsi@freebsd.org>; Mon, 15 Sep 2003 22:38:31 -0700 (PDT)
	(envelope-from jos@catnook.com)
Received: (qmail 1064 invoked by uid 1000); 16 Sep 2003 05:38:51 -0000
Date: Mon, 15 Sep 2003 22:38:28 -0700
From: Jos Backus <jos@catnook.com>
To: freebsd-scsi@freebsd.org
Message-ID: <20030916053850.GA1022@lizzy.catnook.com>
Mail-Followup-To: freebsd-scsi@freebsd.org
References: <20030911165325.GA826@lizzy.catnook.com>
	<137850000.1063320278@aslan.btc.adaptec.com>
	<20030912032034.GA826@lizzy.catnook.com>
	<20030912184536.GM26878@cicely12.cicely.de>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <20030912184536.GM26878@cicely12.cicely.de>
User-Agent: Mutt/1.5.4i
Subject: Re: "Timedout SCB already complete. Interrupts may not be
	functioning."
X-BeenThere: freebsd-scsi@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: jos@catnook.com
List-Id: SCSI subsystem <freebsd-scsi.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-scsi>
List-Post: <mailto:freebsd-scsi@freebsd.org>
List-Help: <mailto:freebsd-scsi-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-scsi>,
	<mailto:freebsd-scsi-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 16 Sep 2003 05:38:34 -0000

On Fri, Sep 12, 2003 at 08:45:37PM +0200, Bernd Walter wrote:
> Sounds like Int routing got wrong results.
> Check if disabling helps you:
> Index: sys/dev/pci/pci.c
> ===================================================================
> RCS file: /home/ncvs/src/sys/dev/pci/pci.c,v
> retrieving revision 1.226
> diff -u -r1.226 pci.c
> --- sys/dev/pci/pci.c   22 Aug 2003 03:11:53 -0000      1.226
> +++ sys/dev/pci/pci.c   11 Sep 2003 19:01:56 -0000
> @@ -800,7 +800,7 @@
>         }
>  
>         if (cfg->intpin > 0 && PCI_INTERRUPT_VALID(cfg->intline)) {
> -#if defined(__ia64__) || (defined(__i386__) && !defined(SMP))
> +#if defined(__ia64__) || (defined(__noi386__) && !defined(SMP))
>                 /*
>                  * Try to re-route interrupts. Sometimes the BIOS or
>                  * firmware may leave bogus values in these registers.
> 

My apologies for the late response. Dankeschön Bernd, I'll try this tomorrow
and will report back here.

> I saw the same yesterday on an Asus T2P4 board and got the impression
> about a BIOS bug, but since I installed using old source I did not
> mention yet.
> In my case the result was the same in that all routing resulted in
> beeing IRQ4.
> 
> -- 
> B.Walter                   BWCT                http://www.bwct.de
> ticso@bwct.de                                  info@bwct.de

-- 
Jos Backus                       _/  _/_/_/      Sunnyvale, CA
                                _/  _/   _/
                               _/  _/_/_/
                          _/  _/  _/    _/
jos at catnook.com        _/_/   _/_/_/          require 'std/disclaimer'