From owner-freebsd-hackers@freebsd.org Fri May 4 04:07:12 2018 Return-Path: Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id D8A0EFC659C for ; Fri, 4 May 2018 04:07:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (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 702407EDBD for ; Fri, 4 May 2018 04:07:11 +0000 (UTC) (envelope-from wlosh@bsdimp.com) Received: by mail-io0-x22c.google.com with SMTP id d73-v6so24187101iog.3 for ; Thu, 03 May 2018 21:07:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bsdimp-com.20150623.gappssmtp.com; s=20150623; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=4FfCVdzuamlluyzQihgevS2wNz5TSRbPCHN5gCXLdL4=; b=P5mR5SUpXYTqoURlJYFiDujZLHLoX88CzBchz568oNfQpE2OrrvqiiONJdG7s50veV xeHLOIzEOZdH5WSjKkv+MoupA4hu+tJrkfu7i+LQdI3yiWwEon+CGGAoPlGftD20VuNR LmmudXVGe4zASxYgywEorULaOQFh0KhSGPJFUFM/yrOS2Jz8AReJzt7Qc6KSb8tu3LRW Y7RktMZ55CJvWQL/wffwVHPp08ePTmBzpXXafY4J/aBzHsPhAKKjmx4SWTE9hL1R8Biw MraWvMUZMRbxSVguMCNr0ZdZliJF8Va+hpxOJvrr7dykB/vfGLC5agi7kk713v1xc5du PE/Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=4FfCVdzuamlluyzQihgevS2wNz5TSRbPCHN5gCXLdL4=; b=aFIxZCfkI/lbvI8JfHM/NdWf18TVOCKsrYIE54IQllHgbiTud9ZxoOpjkN4ioLo09T rbhqZ82eNePitWSRqmwsmbj4Iv8Uo/RKafsXnwbHlFB03Bxr21zIkv4Iz/PrjJE3W6OP 9b33oxizBKEX50NAFL8USQoQv0oaIeE0aCh2dCRPO1fWDc6v/69x6CCwLltXb9Uvt9lF OFH2MXy5XlTl+EAVJRXXpLZIW3q8XZVioWhXohWsZB+FtM/SwNKknT5Mwb5FG5O5Ll3c PF+xmPUlFq3xzs30SWHxU2OyQ2sx3DJAl8v58nJB/LH/JZ4d/15XLGV75E/0RE36a75G jXGQ== X-Gm-Message-State: ALQs6tBqj2ISrKR/Ed1+Jn8Mm3iU5fDnWiSwBJROjc+SxIuCGd/gjMJD IJm9MZijwPGoCJ10sYEY8nBYMNp40cP58SbuCMtHeA== X-Google-Smtp-Source: AB8JxZoKFD4GpcA09a2qSnHnaX2/KdvxpsnN3ahuMFyAMl+n/MLn5SeINelaj76Bs9pj9i2TVwWDEFAx591y0d0syS8= X-Received: by 2002:a6b:12a3:: with SMTP id 35-v6mr27441720ios.168.1525406830503; Thu, 03 May 2018 21:07:10 -0700 (PDT) MIME-Version: 1.0 Sender: wlosh@bsdimp.com Received: by 2002:a4f:a65a:0:0:0:0:0 with HTTP; Thu, 3 May 2018 21:07:09 -0700 (PDT) X-Originating-IP: [2603:300b:6:5100:18a2:a4f7:170:8dd9] In-Reply-To: <960be682-9991-f8c6-0253-7d6f782d4cbe@freebsd.org> References: <960be682-9991-f8c6-0253-7d6f782d4cbe@freebsd.org> From: Warner Losh Date: Thu, 3 May 2018 22:07:09 -0600 X-Google-Sender-Auth: UQ6bPIlx69wUi_jMNm4-xPezeHM Message-ID: Subject: Re: nvme0: async event occurred (log page id=0x2) To: Craig Leres Cc: "freebsd-hackers@freebsd.org" Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.25 X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 May 2018 04:07:12 -0000 On Thu, May 3, 2018 at 9:56 PM, Craig Leres wrote: > I have an intel nuc (NUC6i3SYH) that ran 10.3-RELEASE until a few weeks > ago and now 11.1-RELEASE. The system disk is an intel 600p M.2 SSD and > there is also a 2TB seagate laptop drive (ST2000LM007). > > Occasionally the system SSD will go to sleep. It happened today with > this on the console: > > nvme0: async event occurred (log page id=0x2) > nvme0: resetting controller > nvme0: nvme_ctrlr_wait_for_ready called with desired_val = 0 but > cc.en = 1 > > Later it would occasionally print out: > > swap_pager: indefinite wait buffer: bufobj: 0, blkno: 1509, size: > 12200 > > There was an app playing music from the 2TB drive that was still working > when I reset the box. But no i/o was occurring with with the M.2 SSD. > > I see PR 209571 might be related (same async event log anyway at least). > > Does anyone have suggestions for me? > Async events are 'something went wrong' messages. Log page 2 is the smart log page. what does 'nvmecontrol logpage -p 2 nvme0' tell you right after this happens. My guess is that it's overheating. Warner