From owner-freebsd-scsi Fri May 19 8: 4:52 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from p2.acadia.net (p2.acadia.net [205.217.210.2]) by hub.freebsd.org (Postfix) with ESMTP id 7D19237BDB8; Fri, 19 May 2000 08:04:37 -0700 (PDT) (envelope-from tbuswell@acadia.net) Received: from smpbox (ip142167010111.acadia.net [142.167.10.111]) by p2.acadia.net (8.9.3/8.9.3) with ESMTP id LAA02204; Fri, 19 May 2000 11:13:17 -0400 (EDT) Received: (from tbuswell@localhost) by smpbox (8.9.3/8.9.3) id LAA00499; Fri, 19 May 2000 11:09:27 -0400 (EDT) (envelope-from tbuswell) From: Ted Buswell MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Fri, 19 May 2000 11:08:27 -0400 (EDT) To: wietse@porcupine.org (Wietse Venema) Cc: freebsd-mobile@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Subject: Re: Need FreeBSD 4.0 removable SCSI support In-Reply-To: <20000518231606.5AE974563D@spike.porcupine.org> References: <20000518231606.5AE974563D@spike.porcupine.org> X-Mailer: VM 6.43 under 20.4 "Emerald" XEmacs Lucid Message-ID: <14629.21138.578322.41745@smpbox> Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Wietse Venema writes: > Summary: Generic FreeBSD 4.0-RELEASE + Thinkpad 600 + SlimSCSI > 1460B + Jaz 2GB locks up the machine. > > I conclude that FreeBSD 4.0 cannot work with my hardware. Perhaps > it gets upset by garbage from the Jaz disk. I do not care anymore. > Even though you don't care anymore, whether or not the Jaz is upsetting the card or driver by spewing garbage is easy to determine: with nothing plugged into your bus adapter, does the rescan still lockup your machine? And while we're talking about it, is the lockup a real lockup, or is it simply that the camcontrol process hangs and you have it in your startup sequence in such a way that the boot is not able to continue? Also, did you do the obvious things like trying the aic on different interrupts [well, at least both of the interrupts that you stated you use with other devices successfully]? In your second(? third?) message to the -scsi list, you sent the following (snippets from) dmesg: >aic1: at port 0x340-0x35f irq 3 slot 0 on pccard0 >aic1: aic6360, dma, disconnection, parity check >(probe0:aic1:0:0:0): ccb 0xc0b3c000 - timed out, phase 0xa6, state 1 I'm not sure about yours, but my 1460B does not list irq 3 as one of the valid IRQ's that it can generate. Check "pccardc dumpcis" and search for IRQ. While "timed out" messages could also be cable/device related, on my setup they indicated an IRQ conflict. For what it's worth, 5.0-CURRENT + SMP 2xPII + SlimSCSI 1460B (irq 9) + Iomega Zip works. > It looks like Linux will have to be my long-term solution. It was > nice knowing you people. > > Wietse Apologies in advance if this was meant to convey that you are no longer interested in resolving this problem. -Ted To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message