14:41:39 rmustacc: are there any examples of enumerating a locate LED in fmd for a specific type of card? 14:42:02 there's kinda something for nics, but those are ports, not the card 15:32:25 jbk: What provides the facility? 15:43:02 right now nothing.. that's I guess I'm trying to figure out.. the card (third party driver unfortunately) has an IOCTL to turn an ident light on/off.. it'd be nice to be able to hook that into fmd, but I can't see any obvious way to trigger a module to enumerate anything based off the driver 15:47:10 on a somewhat related note, any thoughts on maybe adding a flag to 'dladm show-phys' (seems most logical place) that could use the fm topo stuff to list a location for a NIC (somewhat analogous do diskadm -P)? 15:47:14 [illumos-gate] 15715 rdsv3: the comparison will always evaluate as 'true' -- Toomas Soome 15:47:31 e.g. I was just dealing with a system w/ 8 instances of mlxcx 15:47:44 where (for reasons) the instance ordering changed 15:48:23 but the PCI slots were labeled, so I could at least use fmtopo to map by hand mlxcx0 -> PCI slot an such 15:49:12 does prtdiag show it? 15:50:23 granted for onboard NICs it's probably less useful w/o a topo map since most would just show up as 'MB' (though even there could help if there's a mix of onboard/cards) 15:50:46 prtdiag shows the slots and if they're occupied 15:51:06 but nothing obvious to tell you how that maps to drivers & instances 16:01:01 yep, oracle also does only this: 16:01:04 ID Status Type Description 16:01:04 --- --------- -------------------- ------------------------ 16:01:04 1 in use PCI Express Gen3 /SYS/MB/RISER1/PCIE1 16:01:04 2 in use PCI Express Gen3 /SYS/MB/RISER2/PCIE2 16:01:04 3 available PCI Express Gen3 /SYS/MB/RISER3/PCIE3 16:21:38 Is it a third party driver you can modify? 16:21:48 yes 16:22:44 So we already do device-class specific logic in the pci enumerator to go off and do things. 16:23:03 So the ways to approach this vary. 16:23:34 Because it's tied to a card and not something else, I presume that we don't want to do something like use static nodes. 16:23:42 That's for example, what I've done for our drive bays and other things. 16:24:12 yeah the card could be in any slot 16:24:15 The topo pci enumerator does allow for PCI class-specific things to happen, but those are also not driver specific or it'd be a bit weird for the driver here. 16:24:41 The simplest path would be to add a custom facility and just enumerate it in the PCI enumerator locally. 16:25:23 If we wanted to avoid encoding that in the PCI enumerator, there are probably some other ways to approach it and add something like ksensors. 16:25:34 But that's a lot of work and I'm not sure if that'd help us a ton. 16:26:20 What's the hardware out of curiosity? Not a datalink by chance? 16:27:21 no 16:27:24 HBA 17:57:15 I missed stuff above, but oracle's CRO stuff jmcp did is lovely. 18:06:29 CRO? 18:07:49 "Chassis, Receptacle, and Occupants" 18:08:20 https://docs.oracle.com/cd/E88353_01/html/E72487/croinfo-8.html 18:08:38 ahh.. so not related to mst3k :P 18:10:42 not officially 18:11:30 but then officially, it's just a coincidence the linker aliens created commands named lari, crle, and moe, and not related to any stooges 18:14:35 i do like the idea of devchassisfs (linux kinda does something vaguely similar) 20:00:33 jbk: I think they did it initially because of the large OPL, where your princess might be in a whole other rack 20:01:08 but even on smaller machines there's been times I would have a much happier and more direct experience if I could refer to things based on where they were (and refer to where they were based on the things that were there) 20:01:47 just outside of OPL, almost always with disks