From owner-freebsd-scsi@freebsd.org Thu Jun 1 18:12:39 2017 Return-Path: Delivered-To: freebsd-scsi@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 D480AB7B9EA for ; Thu, 1 Jun 2017 18:12:39 +0000 (UTC) (envelope-from stephen.mcconnell@broadcom.com) Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9368584BD6 for ; Thu, 1 Jun 2017 18:12:39 +0000 (UTC) (envelope-from stephen.mcconnell@broadcom.com) Received: by mail-it0-x234.google.com with SMTP id m62so975642itc.0 for ; Thu, 01 Jun 2017 11:12:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=broadcom.com; s=google; h=from:references:in-reply-to:mime-version:thread-index:date :message-id:subject:to:cc:content-transfer-encoding; bh=1K4d03gRUSHJZ8Izjcsy+IdXncmSCpAUvNGyaZv/hbk=; b=etSepBVqvX1G0PcPXM7RuxNEC9+IjYeHvM5f+ARdOy7IHbkRyHjuiW2/fTWd7iMU2/ lU+6sKVMfH5gMMpcBkSZi4ZFkPBPZogRR7G01FMA3lB9ciOyBLHUUOAU97tXIUhwFIY6 jH5RdwBjHEDtSwINSDoc0ycV4fkmUVHeV+zPc= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:references:in-reply-to:mime-version :thread-index:date:message-id:subject:to:cc :content-transfer-encoding; bh=1K4d03gRUSHJZ8Izjcsy+IdXncmSCpAUvNGyaZv/hbk=; b=Bu+RMfdlAzJteSGgwQRUJJprhO+6hQmpraa67NbPENL2wXhwYhAuDTb6FkoV2GNvgi fGqOAaPbxDZknvI12k68omTfnA02BkDhE2f4RhsHoxz0249iEeOB9ymqXRYEzlKnbyYf O0d+xpWHnOVKdcisO5Ica2KOKf8WJyXrjQEkxtWHwlhSzpmy69RVDPCSBe8GZTijRWtE ngArumcY20H8rHDzD+hNoi3qMnhz2m78bym409Ms2qkFGMfjIAmKsHe4xNWcTfrsM3sF gCtCiHUDrdWn371EhlVFM+HpHkpPskuj+ffTF/ZxwOEOpecZHc6Q8lyl/Ovwxgl+NNsm a2SA== X-Gm-Message-State: AODbwcBOdKxnNk9I19iUjph5AynCDvmQ//Z4lzRADL91nzin4XHNpjj5 D6h0RDmQqn2wRSKcGbnF3nsy/lqpSaEQ X-Received: by 10.36.238.129 with SMTP id b123mr609014iti.10.1496340758836; Thu, 01 Jun 2017 11:12:38 -0700 (PDT) From: Stephen Mcconnell References: <592FDE8C.1090609@omnilan.de> 12a36df9eff99c77ec621987efbe75fe@mail.gmail.com <59303484.1040609@omnilan.de> <593056E9.6000807@omnilan.de> In-Reply-To: <593056E9.6000807@omnilan.de> MIME-Version: 1.0 X-Mailer: Microsoft Outlook 14.0 Thread-Index: AQK5uw9AxlTbZs3SRUL7gsvMDeNX4QK127o/Aqh6HjgB6++7AwGq54Urn/rkm7A= Date: Thu, 1 Jun 2017 12:12:37 -0600 Message-ID: Subject: RE: mps(4) blocks panic-reboot To: Harry Schmalzbauer Cc: freebsd-scsi@freebsd.org, Scott Long Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-scsi@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: SCSI subsystem List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 18:12:39 -0000 > -----Original Message----- > From: Harry Schmalzbauer [mailto:freebsd@omnilan.de] > Sent: Thursday, June 01, 2017 12:03 PM > To: Stephen Mcconnell > Cc: freebsd-scsi@freebsd.org; Scott Long > Subject: Re: mps(4) blocks panic-reboot > > Bez=C3=BCglich Stephen Mcconnell's Nachricht vom 01.06.2017 19:36 (localt= ime): > > Can you try the attached patch and let me know how it goes? I didn't > > test it, but since you know how, it might be easier this way. This was > > diff'd from the latest mps files in stable/11, which I recently updated > > (today). > > Thanks a lot, I noticed the highly appreciated MFC! > Things are cooking... There were sysdecode userland changes, so I need to > buidl > world also, before my rollout system provides the update for this > machine =E2=80=93 will > be ready in an hour. > > Since I have expert's attention, I'd like to ask a another mps(4) related > question: > > I had unionfs deadlocks. (I'm aware of the broken status of unionfs, and > since > I'm not able to fix it myself at the moment, I already replaced it with > nullfs > where possible, true for the following event) > > Since this machine has a memory-disk as rootfs (and 5 SSDs via mps(4) for > bootpool and a separate syspool, where /var e.g. lives), I guess the > deadlock is > responsible for simultanious disappearance of all mps(4) attached drives. > > Is that plausable? (meaning, does the mps(4) driver depend on filesystem > subsystem?) > > Or do you have any idea what else could lead to disapearance of all drive= s > simultaniously? Other ata drives, via on-board ahci (C203) were not > affected! > UNfortunately, I haven't been able to record any kernel messages when tha= t > happened (3 times as far as I remember, no occurence since abandoning > unionfs > yet) This doesn't seem like an mps driver problem to me, but maybe someone else here can help more than I can. I can't think of anything that might be causing your drives to disappear. It would help if you could get some kerne= l logs when this happens. > > Thanks, > > -harry