From owner-freebsd-stable@FreeBSD.ORG Fri Oct 26 20:19:11 2012 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 2F10FC8D; Fri, 26 Oct 2012 20:19:11 +0000 (UTC) (envelope-from jmg@h2.funkthat.com) Received: from h2.funkthat.com (gate2.funkthat.com [208.87.223.18]) by mx1.freebsd.org (Postfix) with ESMTP id 009378FC08; Fri, 26 Oct 2012 20:19:10 +0000 (UTC) Received: from h2.funkthat.com (localhost [127.0.0.1]) by h2.funkthat.com (8.14.3/8.14.3) with ESMTP id q9QKIKix039106 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 26 Oct 2012 13:18:20 -0700 (PDT) (envelope-from jmg@h2.funkthat.com) Received: (from jmg@localhost) by h2.funkthat.com (8.14.3/8.14.3/Submit) id q9QKIKgM039104; Fri, 26 Oct 2012 13:18:20 -0700 (PDT) (envelope-from jmg) Date: Fri, 26 Oct 2012 13:18:19 -0700 From: John-Mark Gurney To: Jim Harris Subject: Re: tws bug ? (LSI SAS 9750) Message-ID: <20121026201819.GF1563@funkthat.com> Mail-Followup-To: Jim Harris , Mike Tancsa , FreeBSD-STABLE Mailing List , delphij@freebsd.org References: <505CC8EC.4030608@sentex.net> <505CE601.4070106@sentex.net> <505D0846.8050108@sentex.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.2.3i X-Operating-System: FreeBSD 7.2-RELEASE i386 X-PGP-Fingerprint: 54BA 873B 6515 3F10 9E88 9322 9CB1 8F74 6D3F A396 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html X-to-the-FBI-CIA-and-NSA: HI! HOW YA DOIN? can i haz chizburger? X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.2.2 (h2.funkthat.com [127.0.0.1]); Fri, 26 Oct 2012 13:18:20 -0700 (PDT) Cc: delphij@freebsd.org, FreeBSD-STABLE Mailing List X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 26 Oct 2012 20:19:11 -0000 Jim Harris wrote this message on Fri, Sep 21, 2012 at 20:17 -0700: > On Fri, Sep 21, 2012 at 5:37 PM, Mike Tancsa wrote: > > On 9/21/2012 8:03 PM, Jim Harris wrote: > >>> . > >>> then a lot of > >>> . > >>> (probe65:tws0:0:65:0): INQUIRY. CDB: 12 0 0 0 24 0 > >>> (probe65:tws0:0:65:0): CAM status: Invalid Target ID > >>> (probe65:tws0:0:65:0): Error 22, Unretryable error > >>> (probe1:tws0:0:1:0): INQUIRY. CDB: 12 0 0 0 24 0 > >>> (probe1:tws0:0:1:0): CAM status: Invalid Target ID > >>> (probe1:tws0:0:1:0): Error 22, Unretryable error > >>> (probe2:tws0:0:2:0): INQUIRY. CDB: 12 0 0 0 24 0 > >>> (probe2:tws0:0:2:0): CAM status: Invalid Target ID > >>> . > >>> . > >>> . > >>> (probe63:tws0:0:63:0): INQUIRY. CDB: 12 0 0 0 24 0 > >>> (probe63:tws0:0:63:0): CAM status: Invalid Target ID > >>> (probe63:tws0:0:63:0): Error 22, Unretryable error > >>> (probe64:tws0:0:64:0): INQUIRY. CDB: 12 0 0 0 24 0 > >>> (probe64:tws0:0:64:0): CAM status: Invalid Target ID > >>> (probe64:tws0:0:64:0): Error 22, Unretryable error > >> > >> These can be ignored. CAM is just telling you that there are no > >> devices attached at these target IDs. > > > > What about a change similar to what Alexander Motin did in > > > > http://lists.freebsd.org/pipermail/svn-src-head/2012-June/038196.html > > Ah, yes. I was thinking you had CAM_DEBUG enabled which is why you > were seeing this spew - but that's not the case. This indeed should > be fixed and not just ignored. > > Seeing the attributions on Alexander's commit, you certainly seem to > have a monopoly on controllers that exhibit this problem on FreeBSD. > :) > > I believe the CAM_LUN_INVALID here should be fixed as well, similar to > the twa commit. If you send me a revised patch I will commit it. I'm seeing similar stuff on the hpt27xx driver: (probe18:hpt27xx0:0:18:0): INQUIRY. CDB: 12 0 0 0 24 0 (probe18:hpt27xx0:0:18:0): CAM status: Invalid Target ID (probe18:hpt27xx0:0:18:0): Error 22, Unretryable error Should I make a similar change in sys/dev/hpt27xx/osm_bsd.c? Looks like there are two CAM_TID_INVALID lines, but from reading the comments, only the second one should change... Correct? If so, I'll try making the change and make sure everything works well. Thanks. -- John-Mark Gurney Voice: +1 415 225 5579 "All that I will do, has been done, All that I have, has not."