From owner-freebsd-current Mon Oct 28 09:38:22 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id JAA14097 for current-outgoing; Mon, 28 Oct 1996 09:38:22 -0800 (PST) Received: from rover.village.org (rover.village.org [204.144.255.49]) by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id JAA14090 for ; Mon, 28 Oct 1996 09:38:18 -0800 (PST) Received: from rover.village.org [127.0.0.1] by rover.village.org with esmtp (Exim 0.56 #1) id E0vHvd7-0002qr-00; Mon, 28 Oct 1996 10:37:41 -0700 To: alexandr@hawk.pearson.udel.edu Subject: Re: Jaz Woes? Cc: freebsd-current@freebsd.org In-reply-to: Your message of "Mon, 28 Oct 1996 10:52:44 EST." <199610281552.KAA00744@hawk.pearson.udel.edu> References: <199610281552.KAA00744@hawk.pearson.udel.edu> Date: Mon, 28 Oct 1996 10:37:41 -0700 From: Warner Losh Message-Id: Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199610281552.KAA00744@hawk.pearson.udel.edu> Jerry Alexandratos writes: : I'm getting some flakey results, and I was wondering if someone could : tell me where they think they're coming from. Now, whenever I try to : decompress a large file onto the Jaz drive, the file will uncompress, : than after a few seconds, my machine will hang and reboot. 8( I vaguely recall having to make sure parity was enabled on the Jaz drive before it worked. But that could have been any number of the last 20 SCSI devices that I've put on the bus. I do that automatically w/o thought these days. I'm using an UltraStor 34F right now, so that is at least one difference. Have you done the normal scsi checklist: Are you sure it is terminated? On both ends? Any extra termination? Repeat 1-3 until you are really really really sure :-) Are the cables good and tight and of good quality? Have you tried reseating them? Can you enable kernel core dumps (see dumpon if you don't have this in your kernel) and find out where it is dying? Warner