00:25:31 EasyNT: may not be an option on that system. see slide 13 of https://cdrdv2-public.intel.com/783328/Intel%20Xeon-E-2400%20Processor%2030-3-30%20Public.pdf which I believe is for the CPU in the R260 00:26:39 the lanes that terminate in the CPU can either be 1x16+1x4 or 2x8+1x4. doesn't say what the chipset can do. 00:28:22 which one was that? 00:28:41 with a little digging, the PEX8800xx does work 00:32:27 Looks like Intel Xeon E-2400 with "C260 series" chipset. 00:38:14 EasyNT: if the one you're looking at is similar to that one it should see the NVMe disks 00:38:39 just there is a on-board enclosure device that you probably won't be able to see 00:57:43 what does anyone happen to know about ndi flavors? 00:59:17 (also, I wonder how well `NDI_FLAVOR_VANILLA` translates conceptually) 01:02:02 it basically does what I want, but the fasttrack and uses strongly suggest it's really an SCSA specific hack because they can't get out of abusing the driver private data 01:14:40 sommerfeld: Thanks so much for your research! Yes, I was thinking of the E-2468 cpu… 01:15:23 jbk: Thanks, where did you find that about the PEX8800xx? 01:16:26 i was able to find someone with the hardware and they were nice enough to boot an illumos iso and check if it could see the NMVe devices 01:19:17 jbk: Wow, so great. May I ask what hardware that was exactly? 01:19:46 i think it was a PEX880048 01:20:21 But do you know the card/manufacturer also? 01:20:36 i think it's just from broadcom 01:21:45 Ok I’ll check, thanks! 01:33:04 the mgmt device looks like it has a pci id of 1000:00b2 01:38:34 on linux it uses the mpt3sas driver 01:39:15 and looking at it... it _might_ (big emphasis) only require a few bits for our mptsas driver to recognize it 01:39:47 on linux basically for that device id, it's setting 'is_gen35_ioc' 01:39:54 and our driver has a similar setting 01:53:59 But you don’t know if the PEX8747 also works? 02:35:37 no 14:35:27 andyf pmooney looks good with the archive applied! 14:35:44 sjorge: great. thanks for the report 15:46:28 Does anyone here have an i40e on OI or OmniOS? If so, please utter: 15:46:32 ls -lt /devices/pseudo/clone@0:i40e 15:46:35 and share the output here? 17:36:18 danmcd: $ ls -lt /devices/pseudo/clone@0:i40e 17:36:18 crw-rw-rw- 1 root sys 1, 90 Feb 27 09:35 /devices/pseudo/clone@0:i40e 17:43:51 Thanks. 18:32:31 I have, but it’s the cursed one. 18:33:26 crw-rw-rw- 1 root sys 1, 86 Feb 27 19:33 /devices/pseudo/clone@0:i40e 18:45:12 Oh yeah, the 13230 one... so is the one I have on Kebecloud. 18:45:26 fenix illumos#13230 18:45:27 BUG 13230: i40e has duplicate traffic when used with bhyve/snoop running (New) 18:45:27 ↳ https://www.illumos.org/issues/13230 18:46:10 I've noticed X722 no longer shows up on mobos. :shrug: 19:07:08 Pretty sure it’s a hated part 19:10:32 isn't "duplicate traffic when promiscuous" a well known symptom of something? 19:10:41 I swear I've heard of that with other parts 19:53:28 richlowe: If you look at https://kebe.com/~danmcd/webrevs/13230-newtry/ turns out i40e's X722 implementation doesn't honor what works on X710. The Linux i40e driver comment (repeated in my webrev) might suggest inside knowledge from Intel that I (or rmustacc) could not extract? 19:53:55 Testing this across all i40e parts is a nightmare, and why it's remained in stasis. 19:54:38 I'd done an X722 and *one* X710 part a while ago without obvious failures, but there's all sorts of corner cases too (mcast, among others). 19:57:13 mine was on a vendor 0x1022 device 0x15ff "X710 for 10GBASE-T" which so far has been reasonably well behaved. 20:00:51 richlowe: there have been other cases of duplicate traffic in the past, IIRC one of them was reported a long time ago by Theo and I addressed that. There were also issues with aggr that I believe I fixed. This case with the 700-series Intel NICs is more about minor discrepancies in how the various parts want to be programmed. 20:07:59 so a common symptom, not a common cause, got it 20:09:12 Yea the machinery around the promisc path in mac can be a bit tricky and it's also easy to mess up how/when you program promisc mode on a given NIC and how that relates to the mac groups logic (assuming the driver implements mac group support) 20:10:14 In the X722 case it's a problem with different 700 parts wanting slightly different variations on the programming side 22:16:28 sjorge and andyf ==> just approved fenix illumos#17221 22:16:29 BUG 17221: bhyve emulated e1000g fails with TSO (In Progress) 22:16:29 ↳ https://www.illumos.org/issues/17221 | https://code.illumos.org/c/illumos-gate/+/4099 22:28:48 yea.... rzezeski only way to solve that one.... needs a little zig magic. 22:29:19 C is so 1970s 22:30:05 Linux shouldn't be the only project having multi-lang drama in the mailing list :P 22:33:45 sommerfeld: X710 has never been problematic. And oh damn, that's right, `curly` is not 722, but 710. 22:34:28 There are in-MNX-location machines with X722. I swapped them and curly in my head. 22:36:44 Is that something that could be put behind a tunable? 22:37:10 Not ideal but that might mean it can safely go in without testing all flavors under the sun