Re: ses device over T-SGPIO
Oh, that means you don't have SGPIO after all. If you do, you'll see entries like this: at scbus0 target 0 lun 0 (pass0,ada0) at scbus1 target 0 lun 0 (pass1,ada1) at scbus2 target 0 lun 0 (pass2,ada2) at scbus6 target 0 lun 0 (ses0,pass3) On Fri, Jan 29, 2021 at 1:34 PM Slawa Olhovchenkov wrote: > On Fri, Jan 29, 2021 at 10:12:03AM -0700, Alan Somers wrote: > > > What does "camcontrol devlist" show? > > Only 2 disk: usb-flash and da1 (isci connected) > (I am currently just boot from 12.2 install) > > > On Fri, Jan 29, 2021 at 10:06 AM Slawa Olhovchenkov > wrote: > > > > > On Fri, Jan 29, 2021 at 09:51:33AM -0700, Alan Somers wrote: > > > > > > > I've never used any tool with SGPIO. The hardware simply isn't > powerful > > > > enough to be useful. sesutil works, in theory, to control the > LEDs. But > > > > it's of limited usefulness since there's no way to tell which drives > are > > > > installed in which slots. > > > > > > For me sesutil failed w/ "No SES device found" > > > > > > > > > > > On Fri, Jan 29, 2021 at 9:44 AM Slawa Olhovchenkov > > > wrote: > > > > > > > > > On Fri, Jan 29, 2021 at 09:22:47AM -0700, Alan Somers wrote: > > > > > > > > > > > The short story is: SGPIO sucks. It doesn't detect drive > presence, > > > much > > > > > > less provide physical path information. The only thing you can > do > > > with > > > > > it > > > > > > is control the fault LEDs. But doing that usefully requires you > to > > > have > > > > > > some extra source of information about what drives are installed > in > > > what > > > > > > slots. Basically, you need to track that kind of information > > > offline. > > > > > > sesutil ought to be able to control the LEDs, at least, but I've > > > never > > > > > > personally used it with SGPIO. > > > > > > > > > > What tool you used with SGPIO? > > > > > What additional drivers need? > > > > > > > > > > > On Fri, Jan 29, 2021 at 9:02 AM Slawa Olhovchenkov < > s...@zxy.spb.ru> > > > > > wrote: > > > > > > > > > > > > > I am have Supermicro MB X9DBU-iF connected to bcakplane > > > BPN-SAS-825TQ > > > > > > > by T-SGPIO cables. sesutil don't found any SES device. > > > > > > > > > > > > > > Is this posible to have control to this backplane? > > > > > > > ___ > > > > > > > freebsd-stable@freebsd.org mailing list > > > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > > > > To unsubscribe, send any mail to " > > > > > freebsd-stable-unsubscr...@freebsd.org" > > > > > > > > > > > > > ___ > > > > > > freebsd-stable@freebsd.org mailing list > > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > > > To unsubscribe, send any mail to " > > > freebsd-stable-unsubscr...@freebsd.org > > > > > " > > > > > > > > > ___ > > > > freebsd-stable@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > To unsubscribe, send any mail to " > freebsd-stable-unsubscr...@freebsd.org > > > " > > > > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ses device over T-SGPIO
On Fri, Jan 29, 2021 at 10:12:03AM -0700, Alan Somers wrote: > What does "camcontrol devlist" show? Only 2 disk: usb-flash and da1 (isci connected) (I am currently just boot from 12.2 install) > On Fri, Jan 29, 2021 at 10:06 AM Slawa Olhovchenkov wrote: > > > On Fri, Jan 29, 2021 at 09:51:33AM -0700, Alan Somers wrote: > > > > > I've never used any tool with SGPIO. The hardware simply isn't powerful > > > enough to be useful. sesutil works, in theory, to control the LEDs. But > > > it's of limited usefulness since there's no way to tell which drives are > > > installed in which slots. > > > > For me sesutil failed w/ "No SES device found" > > > > > > > > On Fri, Jan 29, 2021 at 9:44 AM Slawa Olhovchenkov > > wrote: > > > > > > > On Fri, Jan 29, 2021 at 09:22:47AM -0700, Alan Somers wrote: > > > > > > > > > The short story is: SGPIO sucks. It doesn't detect drive presence, > > much > > > > > less provide physical path information. The only thing you can do > > with > > > > it > > > > > is control the fault LEDs. But doing that usefully requires you to > > have > > > > > some extra source of information about what drives are installed in > > what > > > > > slots. Basically, you need to track that kind of information > > offline. > > > > > sesutil ought to be able to control the LEDs, at least, but I've > > never > > > > > personally used it with SGPIO. > > > > > > > > What tool you used with SGPIO? > > > > What additional drivers need? > > > > > > > > > On Fri, Jan 29, 2021 at 9:02 AM Slawa Olhovchenkov > > > > wrote: > > > > > > > > > > > I am have Supermicro MB X9DBU-iF connected to bcakplane > > BPN-SAS-825TQ > > > > > > by T-SGPIO cables. sesutil don't found any SES device. > > > > > > > > > > > > Is this posible to have control to this backplane? > > > > > > ___ > > > > > > freebsd-stable@freebsd.org mailing list > > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > > > To unsubscribe, send any mail to " > > > > freebsd-stable-unsubscr...@freebsd.org" > > > > > > > > > > > ___ > > > > > freebsd-stable@freebsd.org mailing list > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > > To unsubscribe, send any mail to " > > freebsd-stable-unsubscr...@freebsd.org > > > > " > > > > > > > ___ > > > freebsd-stable@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > > " > > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-21:02.extattr
On Jan 29, 2021, at 4:09 AM, Martin Simmons wrote: > >> On Fri, 29 Jan 2021 02:34:06 + (UTC), FreeBSD Errata Notices said: >> >> 2) To update your system via a source code patch: >> >> The following patches have been verified to apply to the applicable >> FreeBSD release branches. >> >> a) Download the relevant patch from the location below, and verify the >> detached PGP signature using your PGP utility. >> >> [FreeBSD 11.4] >> # fetch >> https://www.google.com/url?q=https://security.FreeBSD.org/patches/EN-12:02/extattr.patch&source=gmail-imap&ust=161255012400&usg=AOvVaw3tedBjh5jzyUuP3xiGTtZQ >> # fetch >> https://www.google.com/url?q=https://security.FreeBSD.org/patches/EN-12:02/extattr.patch.asc&source=gmail-imap&ust=161255012400&usg=AOvVaw3t5fFBc0ZeO4PkEwhRNHS9 >> # gpg --verify extattr.patch.asc > > There is a typo in the URLs (12 instead of 21). Thanks for the report. I've published an updated URI. Apologies! Gordon ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: [FreeBSD-Announce] FreeBSD Errata Notice FreeBSD-EN-21:02.extattr
> On Fri, 29 Jan 2021 02:34:06 + (UTC), FreeBSD Errata Notices said: > > 2) To update your system via a source code patch: > > The following patches have been verified to apply to the applicable > FreeBSD release branches. > > a) Download the relevant patch from the location below, and verify the > detached PGP signature using your PGP utility. > > [FreeBSD 11.4] > # fetch https://security.FreeBSD.org/patches/EN-12:02/extattr.patch > # fetch https://security.FreeBSD.org/patches/EN-12:02/extattr.patch.asc > # gpg --verify extattr.patch.asc There is a typo in the URLs (12 instead of 21). __Martin ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ses device over T-SGPIO
What does "camcontrol devlist" show? On Fri, Jan 29, 2021 at 10:06 AM Slawa Olhovchenkov wrote: > On Fri, Jan 29, 2021 at 09:51:33AM -0700, Alan Somers wrote: > > > I've never used any tool with SGPIO. The hardware simply isn't powerful > > enough to be useful. sesutil works, in theory, to control the LEDs. But > > it's of limited usefulness since there's no way to tell which drives are > > installed in which slots. > > For me sesutil failed w/ "No SES device found" > > > > > On Fri, Jan 29, 2021 at 9:44 AM Slawa Olhovchenkov > wrote: > > > > > On Fri, Jan 29, 2021 at 09:22:47AM -0700, Alan Somers wrote: > > > > > > > The short story is: SGPIO sucks. It doesn't detect drive presence, > much > > > > less provide physical path information. The only thing you can do > with > > > it > > > > is control the fault LEDs. But doing that usefully requires you to > have > > > > some extra source of information about what drives are installed in > what > > > > slots. Basically, you need to track that kind of information > offline. > > > > sesutil ought to be able to control the LEDs, at least, but I've > never > > > > personally used it with SGPIO. > > > > > > What tool you used with SGPIO? > > > What additional drivers need? > > > > > > > On Fri, Jan 29, 2021 at 9:02 AM Slawa Olhovchenkov > > > wrote: > > > > > > > > > I am have Supermicro MB X9DBU-iF connected to bcakplane > BPN-SAS-825TQ > > > > > by T-SGPIO cables. sesutil don't found any SES device. > > > > > > > > > > Is this posible to have control to this backplane? > > > > > ___ > > > > > freebsd-stable@freebsd.org mailing list > > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > > To unsubscribe, send any mail to " > > > freebsd-stable-unsubscr...@freebsd.org" > > > > > > > > > ___ > > > > freebsd-stable@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > To unsubscribe, send any mail to " > freebsd-stable-unsubscr...@freebsd.org > > > " > > > > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ses device over T-SGPIO
On Fri, Jan 29, 2021 at 09:51:33AM -0700, Alan Somers wrote: > I've never used any tool with SGPIO. The hardware simply isn't powerful > enough to be useful. sesutil works, in theory, to control the LEDs. But > it's of limited usefulness since there's no way to tell which drives are > installed in which slots. For me sesutil failed w/ "No SES device found" > > On Fri, Jan 29, 2021 at 9:44 AM Slawa Olhovchenkov wrote: > > > On Fri, Jan 29, 2021 at 09:22:47AM -0700, Alan Somers wrote: > > > > > The short story is: SGPIO sucks. It doesn't detect drive presence, much > > > less provide physical path information. The only thing you can do with > > it > > > is control the fault LEDs. But doing that usefully requires you to have > > > some extra source of information about what drives are installed in what > > > slots. Basically, you need to track that kind of information offline. > > > sesutil ought to be able to control the LEDs, at least, but I've never > > > personally used it with SGPIO. > > > > What tool you used with SGPIO? > > What additional drivers need? > > > > > On Fri, Jan 29, 2021 at 9:02 AM Slawa Olhovchenkov > > wrote: > > > > > > > I am have Supermicro MB X9DBU-iF connected to bcakplane BPN-SAS-825TQ > > > > by T-SGPIO cables. sesutil don't found any SES device. > > > > > > > > Is this posible to have control to this backplane? > > > > ___ > > > > freebsd-stable@freebsd.org mailing list > > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > > To unsubscribe, send any mail to " > > freebsd-stable-unsubscr...@freebsd.org" > > > > > > > ___ > > > freebsd-stable@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > > " > > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ses device over T-SGPIO
I've never used any tool with SGPIO. The hardware simply isn't powerful enough to be useful. sesutil works, in theory, to control the LEDs. But it's of limited usefulness since there's no way to tell which drives are installed in which slots. -Alan On Fri, Jan 29, 2021 at 9:44 AM Slawa Olhovchenkov wrote: > On Fri, Jan 29, 2021 at 09:22:47AM -0700, Alan Somers wrote: > > > The short story is: SGPIO sucks. It doesn't detect drive presence, much > > less provide physical path information. The only thing you can do with > it > > is control the fault LEDs. But doing that usefully requires you to have > > some extra source of information about what drives are installed in what > > slots. Basically, you need to track that kind of information offline. > > sesutil ought to be able to control the LEDs, at least, but I've never > > personally used it with SGPIO. > > What tool you used with SGPIO? > What additional drivers need? > > > On Fri, Jan 29, 2021 at 9:02 AM Slawa Olhovchenkov > wrote: > > > > > I am have Supermicro MB X9DBU-iF connected to bcakplane BPN-SAS-825TQ > > > by T-SGPIO cables. sesutil don't found any SES device. > > > > > > Is this posible to have control to this backplane? > > > ___ > > > freebsd-stable@freebsd.org mailing list > > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > > To unsubscribe, send any mail to " > freebsd-stable-unsubscr...@freebsd.org" > > > > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org > " > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ses device over T-SGPIO
On Fri, Jan 29, 2021 at 09:22:47AM -0700, Alan Somers wrote: > The short story is: SGPIO sucks. It doesn't detect drive presence, much > less provide physical path information. The only thing you can do with it > is control the fault LEDs. But doing that usefully requires you to have > some extra source of information about what drives are installed in what > slots. Basically, you need to track that kind of information offline. > sesutil ought to be able to control the LEDs, at least, but I've never > personally used it with SGPIO. What tool you used with SGPIO? What additional drivers need? > On Fri, Jan 29, 2021 at 9:02 AM Slawa Olhovchenkov wrote: > > > I am have Supermicro MB X9DBU-iF connected to bcakplane BPN-SAS-825TQ > > by T-SGPIO cables. sesutil don't found any SES device. > > > > Is this posible to have control to this backplane? > > ___ > > freebsd-stable@freebsd.org mailing list > > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > > > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: ses device over T-SGPIO
The short story is: SGPIO sucks. It doesn't detect drive presence, much less provide physical path information. The only thing you can do with it is control the fault LEDs. But doing that usefully requires you to have some extra source of information about what drives are installed in what slots. Basically, you need to track that kind of information offline. sesutil ought to be able to control the LEDs, at least, but I've never personally used it with SGPIO. -Alan On Fri, Jan 29, 2021 at 9:02 AM Slawa Olhovchenkov wrote: > I am have Supermicro MB X9DBU-iF connected to bcakplane BPN-SAS-825TQ > by T-SGPIO cables. sesutil don't found any SES device. > > Is this posible to have control to this backplane? > ___ > freebsd-stable@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org" > ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
ses device over T-SGPIO
I am have Supermicro MB X9DBU-iF connected to bcakplane BPN-SAS-825TQ by T-SGPIO cables. sesutil don't found any SES device. Is this posible to have control to this backplane? ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
Re: `clang -pg` generates binary which coredumps on start
On 29.01.2021 10:47, Dimitry Andric wrote: I'm trying to profile my user-level program on FreeBSD 12-STABLE (amd64). When I build it with `cc -g -pg -O3` it coredumps on start. What do I do wrong? (lldb) bt * thread #1, name = 'mergenets', stop reason = signal SIGSEGV * frame #0: 0x frame #1: 0x0028ebbf mergenets`__vdso_gettc(th=0x7270, tc=0x7fffddbc) at __vdso_gettc.c:0 frame #2: 0x0028e8c3 mergenets`binuptime [inlined] tc_delta(th=) at __vdso_gettimeofday.c:46:10 frame #3: 0x0028e8ba mergenets`binuptime(bt=0x7fffde08, tk=0x71b0, abs=0) at __vdso_gettimeofday.c:78 frame #4: 0x0028ea73 mergenets`__vdso_clock_gettime(clock_id=4, ts=0x7fffde68) at __vdso_gettimeofday.c:165:10 frame #5: 0x00281efb mergenets`__clock_gettime(clock_id=4, ts=0x7fffde68) at clock_gettime.c:48:11 frame #6: 0x0024339f mergenets`nstime_update_impl [inlined] nstime_get(time=0x000800403a88) at jemalloc_nstime.c:128:2 frame #7: 0x00243395 mergenets`nstime_update_impl(time=0x000800403a88) at jemalloc_nstime.c:160 frame #8: 0x00234b6d mergenets`__je_arena_new [inlined] arena_decay_reinit(decay=0x000800403a20, decay_ms=) at jemalloc_arena.c:572:2 frame #9: 0x00234b21 mergenets`__je_arena_new [inlined] arena_decay_init(decay=0x000800403a20, decay_ms=, stats=0x0008004009a0) at jemalloc_arena.c:593 frame #10: 0x00234b1a mergenets`__je_arena_new(tsdn=0x, ind=0, extent_hooks=) at jemalloc_arena.c:1858 frame #11: 0x002239c0 mergenets`__je_arena_init [inlined] arena_init_locked(tsdn=0x, ind=0, extent_hooks=0x00205778) at jemalloc_jemalloc.c:338:10 frame #12: 0x002239b2 mergenets`__je_arena_init(tsdn=0x, ind=0, extent_hooks=0x00205778) at jemalloc_jemalloc.c:366 frame #13: 0x0022f946 mergenets`malloc_init_hard_a0_locked at jemalloc_jemalloc.c:1328:6 frame #14: 0x00222cf5 mergenets`a0ialloc [inlined] malloc_init_hard_a0 at jemalloc_jemalloc.c:1343:8 frame #15: 0x00222caa mergenets`a0ialloc [inlined] malloc_init_a0 at jemalloc_jemalloc.c:214 frame #16: 0x00222caa mergenets`a0ialloc(size=6223, zero=false, is_internal=false) at jemalloc_jemalloc.c:234 frame #17: 0x002225fc mergenets`__libc_allocate_tls [inlined] malloc_aligned(size=6200, align=16) at tls.c:135:8 frame #18: 0x002225e2 mergenets`__libc_allocate_tls(oldtls=0x, tcbsize=, tcbalign=) at tls.c:359 frame #19: 0x002227d0 mergenets`_init_tls at tls.c:469:8 frame #20: 0x0021f234 mergenets`_start(ap=, cleanup=) at crt1.c:66:3 Likely https://bugs.freebsd.org/249121 (and maybe https://bugs.llvm.org/show_bug.cgi?id=48165). I have r367937, and 249121 was fixed in r365654... -- // Lev Serebryakov ___ freebsd-stable@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
