From owner-freebsd-current Mon Apr 6 05:11:53 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15407 for freebsd-current-outgoing; Mon, 6 Apr 1998 05:11:53 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15401; Mon, 6 Apr 1998 05:11:50 -0700 (PDT) (envelope-from jkh@time.cdrom.com) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.8/8.8.8) with ESMTP id FAA04001; Mon, 6 Apr 1998 05:04:03 -0700 (PDT) (envelope-from jkh@time.cdrom.com) To: "Eugene Radchenko" cc: "Alex" , ache@nagual.pp.ru, scsi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: SCSI errors with latest -current In-reply-to: Your message of "Mon, 06 Apr 1998 15:03:38 +0400." <005f01bd614b$b01d65c0$6330fa9e@org-qsar2.chem.msu.su> Date: Mon, 06 Apr 1998 05:04:03 -0700 Message-ID: <3997.891864243@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > As I tried to shout all over the SCSI list recently (to no avail), this is > not limited to -current or 2.2.5. I had something like this even in 2.1 > (though not as drastic -- just dump died and not the whole system). I have > the feeling that 2.1 had not done tagged queueing yet. Things don't get fixed by shouting, they get fixed by fixing. That's free software. Feel free, Eugene! ;-) Jordan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message