From owner-freebsd-current@freebsd.org Wed Oct 19 16:39:29 2016 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 12565C18C3B for ; Wed, 19 Oct 2016 16:39:29 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from mailman.ysv.freebsd.org (unknown [127.0.1.3]) by mx1.freebsd.org (Postfix) with ESMTP id F3431F02 for ; Wed, 19 Oct 2016 16:39:28 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: by mailman.ysv.freebsd.org (Postfix) id F2AF6C18C38; Wed, 19 Oct 2016 16:39:28 +0000 (UTC) Delivered-To: current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id F2323C18C34; Wed, 19 Oct 2016 16:39:28 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from vps-mail.nomadlogic.org (unknown [IPv6:2607:f2f8:a098::2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id CA31FF01; Wed, 19 Oct 2016 16:39:28 +0000 (UTC) (envelope-from pete@nomadlogic.org) Received: from la-dgt-31327.usa.tribune.com (nat-192-187-90-113.nat.tribpub.com [192.187.90.113]) by vps-mail.nomadlogic.org (OpenSMTPD) with ESMTPSA id 5fac46bc TLS version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO; Wed, 19 Oct 2016 09:39:27 -0700 (PDT) Subject: Re: LOR in mpr(4) To: geoffroy desvernay , current@freebsd.org, freebsd-stable@FreeBSD.org References: <5644D014.4080601@nomadlogic.org> <564B917E.4000205@nomadlogic.org> <9fc856a5-c91d-cdfa-5000-5d8fc8ea20f1@centrale-marseille.fr> From: Pete Wright Message-ID: Date: Wed, 19 Oct 2016 09:39:27 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:45.0) Gecko/20100101 Thunderbird/45.4.0 MIME-Version: 1.0 In-Reply-To: <9fc856a5-c91d-cdfa-5000-5d8fc8ea20f1@centrale-marseille.fr> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 19 Oct 2016 16:39:29 -0000 On 10/19/16 8:10 AM, geoffroy desvernay wrote: > On 11/17/2015 21:43, Pete Wright wrote: >> >> >> On 11/12/15 09:44, Pete Wright wrote: >>> Hi All, >>> Just wanted a sanity check before filing a PR. I am running r290688 and >>> am seeing a LOR being triggered in the mpr(4) device: >>> >>> $ uname -ar >>> FreeBSD srd0013 11.0-CURRENT FreeBSD 11.0-CURRENT #1 r290688: Wed Nov 11 >>> 21:28:26 PST 2015 root@srd0013:/usr/obj/usr/src/sys/GENERIC amd64 >>> >>> >>> lock order reversal: >>> 1st 0xfffff8000d26bc60 CAM device lock (CAM device lock) @ >>> /usr/src/sys/cam/cam_xpt.c:784 >>> 2nd 0xfffffe00012811c0 MPR lock (MPR lock) @ >>> /usr/src/sys/cam/cam_xpt.c:2620 >>> KDB: stack backtrace: >>> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame >>> 0xfffffe04608ee890 >>> witness_checkorder() at witness_checkorder+0xe79/frame 0xfffffe04608ee910 >>> __mtx_lock_flags() at __mtx_lock_flags+0xa4/frame 0xfffffe04608ee960 >>> xpt_action_default() at xpt_action_default+0xb6c/frame 0xfffffe04608ee9b0 >>> scsi_scan_bus() at scsi_scan_bus+0x1d5/frame 0xfffffe04608eea20 >>> xpt_scanner_thread() at xpt_scanner_thread+0x15c/frame 0xfffffe04608eea70 >>> fork_exit() at fork_exit+0x84/frame 0xfffffe04608eeab0 >>> fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe04608eeab0 >>> --- trap 0, rip = 0, rsp = 0, rbp = 0 --- >>> >> >> FWIW I filed the following PR as I can still reproduce this on boot: >> >> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=204614 >> >> cheers, >> -pete >> > Hi all, > > Sorry for cross-posting, let me know where this should go please, I > didn't figured it out :( > > On 11-RELEASE-p1 here (but replying on current@ where I found something > around mpr(4)) > > Not sure if it's related, but on a fresh new machine with Avago SAS3008 > and a 24 disks enclosure (single attached). > > I see a bunch of: > > mpr0: Found device <401,End Device> <12.0Gbps> handle<0x001b> > enclosureHandle<0x0002> slot 8 > (da0:mpr0:0:8:0): UNMAPPED > (da0:mpr0:0:8:0): CAM status: SCSI Status Error > (da0:mpr0:0:8:0): SCSI status: Check Condition > (da0:mpr0:0:8:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command > operation code) > (da0:mpr0:0:8:0): Error 22, Unretryable error > 10:0): UNMAPPED > (da0:mpr0:0:8:0): READ(10). CDB: 28 00 e8 e0 88 71 00 00 04 00 > (da0:mpr0:0:8:0): CAM status: SCSI Status Error > (da0:mpr0:0:8:0): SCSI status: Check Condition > (da0:mpr0:0:8:0): SCSI sense: ILLEGAL REQUEST asc:20,0 (Invalid command > operation code) > (da0:mpr0:0:8:0): Error 22, Unretryable error > ses0: da0: Element descriptor: 'Drive Slot 0' > ses0: da0: SAS Device Slot Element: 2 Phys at Slot 0 > ses0: phy 0: SAS device type 1 id 0 > ses0: phy 0: protocols: Initiator( None ) Target( SSP ) > ses0: phy 0: parent 520474729974b57f addr 5000c50097ce8215 > ses0: phy 1: SAS device type 1 id 1 > ses0: phy 1: protocols: Initiator( None ) Target( SSP ) > ses0: phy 1: parent 520474729974b5ff addr 5000c50097ce8216 > > (more complete dmesg.boot here: http://dgeo.perso.ec-m.fr/dmesg.boot ) > the issue you are seeing is most likely not related to the LOR from the original email and PR I filed. This looks like a media error with the disk device on your RAID controller. A quick google search turn's up quite a few threads on this - ranging from bad RAID/JBOD controllers to out of date firmware. Cheers, -pete -- Pete Wright pete@nomadlogic.org nomadlogicLA