Date: Thu, 29 Aug 2019 10:01:02 +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: <5a970845-11c1-07f6-5310-2e1101f0b83f@freebsd.org> In-Reply-To: <2ecfba45-2819-947a-9744-1f06f3304eee@FreeBSD.org> References: <90483961-9da2-fba1-21da-c38b28e99e06@freebsd.org> <fa9a98aa-ecfc-98b6-bc7c-661944aa90a6@FreeBSD.org> <41c91917-13c2-f3a7-d8fd-6464c2ce3c6d@freebsd.org> <2ecfba45-2819-947a-9744-1f06f3304eee@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-08-29 00:07, Alexander Motin wrote: > On 27.08.2019 19:15, Niclas Zeising wrote: >> 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". > > Thank you for the report. r351589 should fix it. > I can confirm that it works. Thanks for fixing it! Regards -- Niclas Zeising
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5a970845-11c1-07f6-5310-2e1101f0b83f>