Date: Tue, 27 Aug 2019 19:45:12 -0400 From: Michael Butler <imb@protected-networks.net> To: freebsd-current@freebsd.org Subject: Re: ses no longer attaches Message-ID: <6940ee11-bb2c-eb19-e85f-6ba39536c1e2@protected-networks.net> In-Reply-To: <3d769833-8e94-8922-2d95-16d25407f38c@protected-networks.net> References: <90483961-9da2-fba1-21da-c38b28e99e06@freebsd.org> <fa9a98aa-ecfc-98b6-bc7c-661944aa90a6@FreeBSD.org> <41c91917-13c2-f3a7-d8fd-6464c2ce3c6d@freebsd.org> <3d769833-8e94-8922-2d95-16d25407f38c@protected-networks.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2019-08-27 19:41, Michael Butler wrote: > On 2019-08-27 19:15, Niclas Zeising wrote: >> 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". > > I can confirm this behaviour (haven't checked versioning) .. working > kernel yields .. > > Aug 20 17:40:06 toshi kernel: ses0 at ahciem0 bus 0 scbus4 target 0 lun 0 > Aug 20 17:40:06 toshi kernel: ses0: <AHCI SGPIO Enclosure 2.00 0001> > SEMB S-E-S 2.00 device > Aug 20 17:40:06 toshi kernel: ses0: SEMB SES Device > Aug 20 17:40:06 toshi kernel: ses0: ada0,pass0 in 'Slot 00', SATA Slot: > scbus0 target 0 > Aug 20 17:40:06 toshi kernel: ses0: ada1,pass1 in 'Slot 01', SATA Slot: > scbus1 target 0 Should have been .. Aug 20 17:40:06 toshi kernel: ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported Aug 20 17:40:06 toshi kernel: ahcich0: <AHCI channel> at channel 0 on ahci0 Aug 20 17:40:06 toshi kernel: ahcich1: <AHCI channel> at channel 1 on ahci0 Aug 20 17:40:06 toshi kernel: ahcich4: <AHCI channel> at channel 4 on ahci0 Aug 20 17:40:06 toshi kernel: ahcich5: <AHCI channel> at channel 5 on ahci0 Aug 20 17:40:06 toshi kernel: ahciem0: <AHCI enclosure management bridge> on ahci0 > > [ .. other stuff .. ] > > Aug 20 17:40:06 toshi kernel: ses0 at ahciem0 bus 0 scbus4 target 0 lun 0 > Aug 20 17:40:06 toshi kernel: ses0: <AHCI SGPIO Enclosure 2.00 0001> > SEMB S-E-S 2.00 device > Aug 20 17:40:06 toshi kernel: ses0: SEMB SES Device > Aug 20 17:40:06 toshi kernel: ses0: ada0,pass0 in 'Slot 00', SATA Slot: > scbus0 target 0 > Aug 20 17:40:06 toshi kernel: ses0: ada1,pass1 in 'Slot 01', SATA Slot: > scbus1 target 0 > > .. non working reports .. > > Aug 27 11:06:28 toshi kernel: ahciem0: <AHCI enclosure management > bridge> at channel 2147483647 on ahci0 > Aug 27 11:06:28 toshi kernel: device_attach: ahciem0 attach returned 6 > > imb > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org" >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6940ee11-bb2c-eb19-e85f-6ba39536c1e2>