From owner-freebsd-scsi Wed Apr 5 1: 9:25 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from caladan.tdx.co.uk (caladan.tdx.co.uk [195.188.177.4]) by hub.freebsd.org (Postfix) with ESMTP id 50CCC37B8BE for ; Wed, 5 Apr 2000 01:09:12 -0700 (PDT) (envelope-from kpielorz@tdx.co.uk) Received: from tdx.co.uk (lorca-tx.tdx.co.uk [195.188.177.242]) by caladan.tdx.co.uk (8.10.0/8.10.0/Kp) with ESMTP id e3589XG11608; Wed, 5 Apr 2000 09:09:33 +0100 (BST) Message-ID: <38EAF491.93C92B8E@tdx.co.uk> Date: Wed, 05 Apr 2000 09:08:49 +0100 From: Karl Pielorz Organization: TDX - The Digital eXchange X-Mailer: Mozilla 4.7 [en-gb] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: "Justin T. Gibbs" Cc: scsi@FreeBSD.ORG Subject: Re: Problems with 4.0 - CAM when 3.4 was OK? (long post) References: <200004041849.MAA00285@narnia.plutotech.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Justin T. Gibbs" wrote: > > If I boot a 4.0-STABLE kernel, I get heaps of: > > > > " > > Waiting 4 seconds for SCSI devices to settle > > de0: enabling 10baseT port > > (probe15:ahc1:0:0:0): SCB 0xe - timed out in Message-in phase, SEQADDR == > > 0x157 > > (probe15:ahc1:0:0:0): Other SCB Timeout > > (probe16:ahc1:0:1:0): SCB 0xd - timed out in Message-in phase, SEQADDR == > > 0x157 > > This really looks like the system is not seeing interrupts from this > card. I don't know why (perhaps an mptable problem), but the > errors are consistent with that. Hi Justin, Thanks for the pointer - I think you may have hit this straight on the head (and thanks for not even mentioning cables :-) Under 3.X, in the dmesg I had lurking some: /kernel: bogus MP table, 2 IO APIC pins connected to the same PCI device or ISA/EISA interrupt /kernel: Registered extra interrupt handler for int 18 (in addition to int 16) Under 4.0, in the dmesg I don't appear to see them... So the question has to be - where's my buggy APIC workaround gone from 3.X to 4.0? :) I'm going to double check on this, then fire a post to -SMP, Thanks -Karl To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message