00:27:30 <alanc> oh, our libuuid only depends on libc, but that's because we made a system call to generate uuids, so they stay unique across zones without having to do special magic coordination between ngz's
00:31:15 <alanc> since /var/sadm/system/uuid_state had different state in every zone before that 
00:47:20 <jbk> i think i managed to work around it (was trying to build something to go w/ a platform image
00:47:47 <jbk> which uses libuuid
00:48:27 <jbk> and the 36,000+ line autoconf generate makefile (yay!) was incorrectly trying to use bits on the build system
00:48:31 <jbk> which is a bit older
00:49:31 <jbk> but it was confusing gettign a versioning error from libvarpd when that shouldn't be anywhere near this thing
00:50:58 <jbk> i think i managed to find the magic incantation to make it just look at the proto area libs
00:51:34 <jbk> (that it by default tries to be fancy and hide everything it's building with just 'CC <file>' or 'CCLD <library>' wasn't helpful
05:16:55 <jclulow> Ugh, yeah, I hate Makefiles like that
12:26:48 <andyf> alanc that's a nice change, and would address illumos 14571 too! (fenix)
12:26:49 <fenix> BUG 14571: libuuid statefile woes (New)
12:26:50 <fenix> ↳ https://www.illumos.org/issues/14571
12:37:29 <wacki> My new Z4 panics when I start X (independent of the NVIDIA graphics card):
12:37:42 <wacki> > $C
12:37:43 <wacki> fffffe00410466b0 vpanic()
12:37:43 <wacki> fffffe0041046760 hat_devload+0x1f1(fffffe2ca0b0e3f8, fffffe2cba84f000, 1000, 9e, 403, 1)
12:37:43 <wacki> fffffe00410467c0 gfxp_map_kernel_space+0xb8(9e000, 1000, 0)
12:37:43 <wacki> fffffe2cb3f12ea0 _nv041482rm+0x35()
12:37:43 <wacki> fffffe2cb3f12ee0 1()
15:08:55 <rmustacc> wacki: Looks like that's being called from by the nvidia module?
15:10:10 <wacki> Yes, I have used both, an Quadro RTX 5000 and an older Quadro K620 with the same result. 
15:11:18 <rmustacc> What's the panic message?
15:12:07 <wacki> I can't see any. The screen stays empty with a blinking cursor and then after some seconds the machine reboots.
15:13:42 <rmustacc> I have on familiarity with the closed driver, so going to be hard, but probably trying to load a free page or similar would be the most common.
15:13:46 <rmustacc> *have no
19:14:10 <Woodstock> wacki: i had a similar problem recently. the advice i got was to make sure the bios uses efi option rom of the gpu. i don't recall what the setting was called, but once I found it and set it correctly it "just worked".
19:15:15 <wacki> I will look for it. Alas the BIOS settings of the Z4 are quite limited.
20:00:20 <wacki> Ok, after some experiments I found a working configuration. I had to disable legacy and enable uefi boot (with secure boot disabled).