Date: Thu, 3 May 2018 22:07:09 -0600 From: Warner Losh <imp@bsdimp.com> To: Craig Leres <leres@freebsd.org> Cc: "freebsd-hackers@freebsd.org" <freebsd-hackers@freebsd.org> Subject: Re: nvme0: async event occurred (log page id=0x2) Message-ID: <CANCZdfrTD9Jw%2BrnnvoCdSTLaKnh8a=gsz6wMF40HgaU0E1i8=A@mail.gmail.com> In-Reply-To: <960be682-9991-f8c6-0253-7d6f782d4cbe@freebsd.org> References: <960be682-9991-f8c6-0253-7d6f782d4cbe@freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Thu, May 3, 2018 at 9:56 PM, Craig Leres <leres@freebsd.org> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CANCZdfrTD9Jw%2BrnnvoCdSTLaKnh8a=gsz6wMF40HgaU0E1i8=A>