From owner-freebsd-scsi Wed Apr 5 8:15:30 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from overcee.netplex.com.au (peter1.yahoo.com [208.48.107.4]) by hub.freebsd.org (Postfix) with ESMTP id F149037BE87 for ; Wed, 5 Apr 2000 08:15:25 -0700 (PDT) (envelope-from peter@netplex.com.au) Received: from netplex.com.au (localhost [127.0.0.1]) by overcee.netplex.com.au (Postfix) with ESMTP id CCB231CE0; Wed, 5 Apr 2000 08:15:23 -0700 (PDT) (envelope-from peter@netplex.com.au) X-Mailer: exmh version 2.1.1 10/15/1999 To: Karl Pielorz Cc: "Justin T. Gibbs" , scsi@FreeBSD.ORG Subject: Re: Problems with 4.0 - CAM when 3.4 was OK? (long post) In-Reply-To: Message from Karl Pielorz of "Wed, 05 Apr 2000 09:08:49 BST." <38EAF491.93C92B8E@tdx.co.uk> Date: Wed, 05 Apr 2000 08:15:23 -0700 From: Peter Wemm Message-Id: <20000405151523.CCB231CE0@overcee.netplex.com.au> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Karl Pielorz wrote: > "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 This is a known problem. The workaround for the mptable and/or hardware configuration problem was implemented in the wrong place and hasn't been repaired and made to work for all drivers yet. Cheers, -Peter -- Peter Wemm - peter@FreeBSD.org; peter@yahoo-inc.com; peter@netplex.com.au "All of this is for nothing if we don't go to the stars" - JMS/B5 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message