Date: Wed, 28 Aug 2019 01:15:10 +0200 From: Niclas Zeising <zeising@freebsd.org> To: Alexander Motin <mav@FreeBSD.org>, imp@FreeBSD.org Cc: current@FreeBSD.org Subject: Re: ses no longer attaches Message-ID: <41c91917-13c2-f3a7-d8fd-6464c2ce3c6d@freebsd.org> In-Reply-To: <fa9a98aa-ecfc-98b6-bc7c-661944aa90a6@FreeBSD.org> References: <90483961-9da2-fba1-21da-c38b28e99e06@freebsd.org> <fa9a98aa-ecfc-98b6-bc7c-661944aa90a6@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-08-28 00:38, Alexander Motin wrote: > Hi. > > On 27.08.2019 18:03, Niclas Zeising wrote: >> I have an issue where the ses driver no longer attaches. Last known >> good version was r351188, r351544 is broken. In that interval, >> something happened. I haven't had time to bisect yet. > > I would appreciate some details, like dmesg, error messages, etc. On my > test systems I see no problems. > Hi! I did some more digging. r351355 is ok, while r351356 is bad. This is Warner's (CC:d) commit to add RST support to nvme, however, I'm using a ssd drive connected to ahci. What happens is that the ses driver doesn't attach to the AHCI SGPIO enclosure. This is on a laptop with an ssd (not an nvme) drive. I have the same issue on another computer as well. On the broken kernel, sesutil status complains about "No SES devices found", on the working kernel it reports "ok". Regards -- Niclas Zeising
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41c91917-13c2-f3a7-d8fd-6464c2ce3c6d>