From owner-freebsd-hackers  Sat Nov 23 04:32:33 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id EAA22728
          for hackers-outgoing; Sat, 23 Nov 1996 04:32:33 -0800 (PST)
Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20])
          by freefall.freebsd.org (8.7.5/8.7.3) with SMTP id EAA22712;
          Sat, 23 Nov 1996 04:32:15 -0800 (PST)
Received: from x14.mi.uni-koeln.de (annexr3-8.slip.Uni-Koeln.DE) by Octopussy.MI.Uni-Koeln.DE with SMTP id AA06505
  (5.67b/IDA-1.5); Sat, 23 Nov 1996 13:32:11 +0100
Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.3/8.6.9) id NAA17848; Sat, 23 Nov 1996 13:32:05 +0100 (CET)
Message-Id: <199611231232.NAA17848@x14.mi.uni-koeln.de>
Date: Sat, 23 Nov 1996 13:32:04 +0100
From: se@freebsd.org (Stefan Esser)
To: sos@freebsd.org
Cc: hackers@freebsd.org (FreeBSD hackers)
Subject: Re: SCSI problem, anybody knows this ??
References: <199611222220.XAA03456@ravenock.cybercity.dk>
X-Mailer: Mutt 0.49-PL10
Mime-Version: 1.0
In-Reply-To: <199611222220.XAA03456@ravenock.cybercity.dk>; from Soren Schmidt on Nov 22, 1996 23:20:42 +0100
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

On Nov 22, sos@ravenock.cybercity.dk (Soren Schmidt), sos@freebsd.org wrote:
> 
> I'm fiddeling with different SCSI drives, and have now come up
> with one that just gives me this when trying to do anything:

Hmmm, but you don't by chance happen to know the exact 
brand and model of that particular disk drive ? ;)

> /kernel: , retries:2
> /kernel: sd3(ncr0:6:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted
> /kernel: , retries:1
> /kernel: sd3(ncr0:6:0): ABORTED COMMAND asc:4e,0 Overlapped commands attempted
> /kernel: , FAILURE

This is typically reported when there is a problem with
tagged commands, either because they are used incorrectly,
or because the drive does not implement them correctly.

What the drive is actually complaining about is, that the
driver mixed tagged and untagged commands, which is not 
legal. But I'm sure the driver didn't do that, so the 
drive must be wrong :)

> This snippet came when I tried to format the drive...

This message is for example generated by some IBM drives,
when they receive a command that can't actually be executed
simultanously with any other command (eg. START_STOP_UNIT,
perhaps also FORMAT) and this command is sent with a tag.

> Any clues ??

Yes, sure:

# ncrcontrol -t 6 -s tags=0

Let me know, whether that cures it for you ...

Regards, STefan