increasing max value of rdomain/rtable
Hello, I want to increase the number of rdomain/rtable from 255 to 1024. I will do this at my own risk. I had a look at the kernel code but couldn't figure out how to upgrade it. I would be very grateful if you could guide me on this. Thanks in advance. -- Valdrin
Re: How to rebuild the ports tree?
On 2022-03-31, Eric Thomas wrote:
> --c9bb7b05db88e7ee
> Content-Type: text/plain; charset="UTF-8"
>
> I'm stuck. I need to install the UniFi 6.2.26 port, I used the [FAQ to
> setup the ports tree](https://www.openbsd.org/faq/ports/ports.html).
> This seemed to work just fine. However, the last few messages in the
> `make install` output showed errors. To debug the issue, I decided to
> completely uninstall the UniFi port then pipe the `make install`
> output to a log.txt.
As you mentioned 6.2 and this shows 5.6 you'll want to cd into the
relevant subdirectory of /usr/ports/net/unifi.
Compiling mongodb and java aren't very much fun and may need raised
memory limits, you probably want to install those from packages instead
("make FETCH_PACKAGES= install" should do that - the unifi port would
have displayed a hint about this when you ran "make").
> To uninstall:
>
> - TRIED: `make uninstall`
> - ERROR: `make: don't know how to make uninstall`
This would be "make deinstall", but it isn't installed yet, what you
showed is where it was trying to compile/install the dependencies.
> Content-Type: image/png; name="image.png"
Hopefully that will help, if not please copy the text from a terminal
rather than send a screenshot, it may be helpful to scroll up a bit
to show preceding lines too.
Re: Dell G3 3590 audio and touchpad
On Thu, Mar 31, 2022 at 10:54:17AM -0400, Adriano Barbosa wrote:
> Hi misc
>
> I'm trying to make audio and touchpad work on a Dell laptop.
> I've never played with this kind of stuff and I don't even know how to
> properly start.
> I have no hope on making NVIDIA hardware to work, but I believe
> Realtek ALC295 audio could work as, from what I got, it is supported
> by OpenBSD.
>
> >From FreeBSD (where audio and touchpad work) I get the following information:
>
> hdacc0: at cad 0 on hdac0
> hdaa0: at nid 1 on hdacc0
> pcm0: at nid 7 on hdaa0
>
> hdacc1: at cad 0 on hdac1
> hdaa1: at nid 1 on hdacc1
> pcm1: at nid 20 on hdaa1
> pcm2: at nid 33 on hdaa1
> hdacc2: at cad 2 on hdac1
> hdaa2: at nid 1 on hdacc2
> pcm3: at nid 3 on hdaa2
>
> hms0: on hidbus0
> hms0: 2 buttons and [XY] coordinates ID=1
> hmt0: on hidbus0
> hconf0: on hidbus0
> hmt0: Multitouch touchpad with 0 external buttons, click-pad
> hmt0: 5 contacts with [C] properties. Report range [0:0] - [3211:2431]
>
> On OpenBSD (where audio and touchpad don't work) I can identify the
> following relevant information on dmesg:
>
> "Intel 300 Series cAVS" rev 0x10 at pci0 dev 31 function 3 not configured
does not match as it uses pci subclass audio instead of hd audio
should work with this
Index: sys/dev/pci/azalia.c
===
RCS file: /cvs/src/sys/dev/pci/azalia.c,v
retrieving revision 1.271
diff -u -p -r1.271 azalia.c
--- sys/dev/pci/azalia.c21 Mar 2022 19:22:41 - 1.271
+++ sys/dev/pci/azalia.c31 Mar 2022 23:31:08 -
@@ -494,6 +494,7 @@ azalia_configure_pci(azalia_t *az)
const struct pci_matchid azalia_pci_devices[] = {
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_200SERIES_U_HDA },
+ { PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_300SERIES_CAVS },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_300SERIES_U_HDA },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_400SERIES_CAVS },
{ PCI_VENDOR_INTEL, PCI_PRODUCT_INTEL_500SERIES_LP_HDA },
Re: Multiple wgpeers on single wg(4) interface with same wgaip list
On Thu, Mar 31, 2022 at 06:23:01PM -, Stuart Henderson said: > "The interface will route outbound tunneled traffic to the >peer configured with the most specific matching allowed IP >address range, or drop it if no such match exists" > > It doesn't explicitly say what happens if you try to use duplicates > in wgaip but it seems to follow that configuring them can't work given > the above. Yeah, reading it again that makes sense and once I started to think through how OSPF would work it became really clear that I should have a single wg(4) iface pair for each connection instead of trying to multiplex in this case. Seems like multiplexing only makes sense to connect a remote host not a remote network. Thanks, --Matt -- Matthew Ernisse m...@going-flying.com https://www.going-flying.com/
How to rebuild the ports tree?
I'm stuck. I need to install the UniFi 6.2.26 port, I used the [FAQ to setup the ports tree](https://www.openbsd.org/faq/ports/ports.html). This seemed to work just fine. However, the last few messages in the `make install` output showed errors. To debug the issue, I decided to completely uninstall the UniFi port then pipe the `make install` output to a log.txt. To uninstall: - TRIED: `make uninstall` - ERROR: `make: don't know how to make uninstall` - TRIED: - `make clean` - `pkg_delete -a` - `make clean=dist` - `make clean=packages` - `make install` - ERRORS: MANY (attached) The question is, how to I just rebuild the ports tree and/or get it back in a known good state?
Re: OpenBGPd: fatal in RDE: aspath_get: Cannot allocate memory
Le 29/03/2022 à 12:10, Claudio Jeker a écrit : I doubt it is the filters. You run into some sort of memory leak. Please monitor 'bgpctl show rib mem' output. Also check ps aux | grep bgpd output to see why and when the memory starts to go up. With that information it may be possible to figure out where this leak sits and how to fix it. Cheers Hi Claudio, Please find the output of 'bgpctl show rib mem' just 1 minute before the crash: cat 2022-03-30::15:07:01.mem RDE memory statistics 909685 IPv4 unicast network entries using 34.7M of memory 272248 IPv6 unicast network entries using 14.5M of memory 2363169 rib entries using 144M of memory 14616410 prefix entries using 1.7G of memory 1539060 BGP path attribute entries using 106M of memory and holding 14616410 references 635275 BGP AS-PATH attribute entries using 33.7M of memory and holding 1539060 references 47399 entries for 681150 BGP communities using 15.1M of memory and holding 14616410 references 22139 BGP attributes entries using 865K of memory and holding 3436885 references 22138 BGP attributes using 175K of memory 270121 as-set elements in 249193 tables using 9.7M of memory 452138 prefix-set elements using 19.0M of memory RIB using 2.1G of memory Sets using 28.7M of memory RDE hash statistics path hash: size 131072, 1539060 entries min 0 max 31 avg/std-dev = 11.742/3.623 aspath hash: size 131072, 635275 entries min 0 max 16 avg/std-dev = 4.847/2.123 comm hash: size 16384, 47399 entries min 0 max 12 avg/std-dev = 2.893/1.622 attr hash: size 16384, 22139 entries min 0 max 8 avg/std-dev = 1.351/1.084 Here is the output of 'ps aux | grep bgp' one minute before the crash: _bgpd25479 100.1 40.1 33547416 33620192 ?? Rp/2 Tue09AM 1755:38.49 bgpd: route _bgpd 8696 31.6 0.0 15800 13240 ?? Sp Tue09AM 626:35.66 bgpd: sessio _bgpd46603 0.0 0.0 22728 25876 ?? Ip Tue09AM1:29.11 bgpd: rtr en root 94644 0.0 0.0 196 916 ?? Rp/33:07PM0:00.00 grep bgpd During the crash, bgpctl show rib mem doesn't work. Here is the ps aux | grep bgp output during the crash: _bgpd25479 0.0 0.0 0 0 ?? Zp - 0:00.00 (bgpd) _bgpd46603 0.0 0.0 0 0 ?? Zp - 0:00.00 (bgpd) _bgpd 8696 0.0 0.0 0 0 ?? Zp - 0:00.00 (bgpd) root 76428 0.0 0.0 180 772 ?? R/2 3:08PM0:00.00 grep bgpd Please note /var/log/messages output: Mar 30 15:07:27 bgpgw-004 bgpd[17103]: peer closed imsg connection Mar 30 15:07:27 bgpgw-004 bgpd[17103]: main: Lost connection to RDE Mar 30 15:07:27 bgpgw-004 bgpd[46603]: peer closed imsg connection Mar 30 15:07:27 bgpgw-004 bgpd[46603]: RTR: Lost connection to RDE Mar 30 15:07:27 bgpgw-004 bgpd[46603]: peer closed imsg connection Mar 30 15:07:27 bgpgw-004 bgpd[46603]: fatal in RTR: Lost connection to parent Mar 30 15:07:27 bgpgw-004 bgpd[8696]: peer closed imsg connection Mar 30 15:07:27 bgpgw-004 bgpd[8696]: SE: Lost connection to RDE Mar 30 15:07:27 bgpgw-004 bgpd[8696]: peer closed imsg connection Mar 30 15:07:27 bgpgw-004 bgpd[8696]: SE: Lost connection to RDE control Mar 30 15:07:27 bgpgw-004 bgpd[8696]: peer closed imsg connection Mar 30 15:07:27 bgpgw-004 bgpd[8696]: SE: Lost connection to parent Thanks, Laurent
Re: Multiple wgpeers on single wg(4) interface with same wgaip list
On 2022-03-31, Matthew Ernisse wrote: > I am trying to setup several tunnels into a single wg(4) endpoint. > The first tunnel worked fine however when I add the second one the wgaip > statement moves to the last wgpeer configured. Is this expected behavior? Yes, you can't use these completely overlapping networks in wgaip, it's used as a pseudo-route-table to determine which peer to use when sending packets. "The interface will route outbound tunneled traffic to the peer configured with the most specific matching allowed IP address range, or drop it if no such match exists" It doesn't explicitly say what happens if you try to use duplicates in wgaip but it seems to follow that configuring them can't work given the above. On the machine with multiple connections, if a wg client is a single host then you'd usually want the full /32 in wgaip, otherwise distinct subnets for each. 0.0.0.0/0 is useful on a client side if it's getting internet access across the tunnel but not when there are multiple peers on one wg interface.
Multiple wgpeers on single wg(4) interface with same wgaip list
Hello misc@, I am trying to setup several tunnels into a single wg(4) endpoint. The first tunnel worked fine however when I add the second one the wgaip statement moves to the last wgpeer configured. Is this expected behavior? /etc/hostname.wg0 with a single tunnel: descr "Wireguard Site Tunnels" inet 172.17.33.17 255.255.255.240 wgkey [REDACTED] wgport 13231 wgpeer [ENDPOINT_1_PUBKEY] \ wgendpoint a.b.c.d 51806 \ wgpsk [ENDPOINT_1_PSK] \ wgaip 0.0.0.0/0 up `doas ifconfig wg0` output: wg0: flags=80c3 mtu 1420 description: Wireguard Site Tunnels index 13 priority 0 llprio 3 wgport 13231 wgpubkey [SERVER_PUBLIC_KEY] wgpeer [ENDPOINT_1_PUBKEY] wgpsk (present) wgendpoint a.b.c.d 51806 tx: 124, rx: 180 last handshake: 5 seconds ago groups: wg inet 172.17.33.17 netmask 0xfff0 broadcast 172.17.33.31 The above works as expected, however adding the second peer causes the first peer to fail. /etc/hostname.wg0 descr "Wireguard Site Tunnels" inet 172.17.33.17 255.255.255.240 wgkey [REDACTED] wgport 13231 wgpeer [ENDPOINT_1_PUBKEY] \ wgendpoint a.b.c.d 51806 \ wgpsk [ENDPOINT_1_PSK] \ wgaip 0.0.0.0/0 wgpeer [ENDPOINT_2_PUBKEY] \ wgpsk [ENDPOINT_2_PSK] \ wgaip 0.0.0.0/0 up `doas ifconfig wg0` output: wg0: flags=80c3 mtu 1420 description: Wireguard Site Tunnels index 13 priority 0 llprio 3 wgport 13231 wgpubkey [SERVER_PUBLIC_KEY] wgpeer [ENDPOINT_1_PUBKEY] wgpsk (present) wgendpoint a.b.c.d 51806 tx: 17784, rx: 54632 last handshake: 5 seconds ago wgpeer [ENDPOINT_2_PUBKEY] wgpsk (present) wgendpoint f.g.h.i 51807 tx: 116328, rx: 98008 last handshake: 42 seconds ago wgaip 0.0.0.0/0 groups: wg inet 172.17.33.17 netmask 0xfff0 broadcast 172.17.33.31 This seems to happen reguardless of if I destroy the interface between adding peers or not. It seems to also happen if I try to specify the wg0 interface's network as the wgaip, eg wgaip 172.17.33.16/28 on both peers, only the last one seems to retain it. Once the wgaip stanza switches the other peer still seems to authenticate fine but all traffic is dropped and `doas ifconfig wg0 debug` causes the following to be printed into the kernel ringbuffer: wg0: Packet has unallowed src IP from peer 7 which makes sense, given the default is to have no ip allowed. Is it expected that one cannot assign the same wgaip blocks to more than one peer simultaneously? Thanks, Matt -- Matthew Ernisse m...@going-flying.com https://www.going-flying.com/
Re: Dell G3 3590 audio and touchpad
Here is the pcidump: Domain /dev/pci0: 0:0:0: Intel Core 8G Host 0x: Vendor ID: 8086, Product ID: 3ec4 0x0004: Command: 0006, Status: 2090 0x0008: Class: 06 Bridge, Subclass: 00 Host, Interface: 00, Revision: 07 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 00 0x0010: BAR empty () 0x0014: BAR empty () 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1028 Product ID: 0949 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 00 Line: 00 Min Gnt: 00 Max Lat: 00 0x00e0: Capability 0x09: Vendor Specific 0:1:0: Intel Core 6G PCIE 0x: Vendor ID: 8086, Product ID: 1901 0x0004: Command: 0007, Status: 0010 0x0008: Class: 06 Bridge, Subclass: 04 PCI, Interface: 00, Revision: 07 0x000c: BIST: 00, Header Type: 81, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR empty () 0x0014: BAR empty () 0x0018: Primary Bus: 0, Secondary Bus: 1, Subordinate Bus: 1, Secondary Latency Timer: 00 0x001c: I/O Base: 40, I/O Limit: 40, Secondary Status: 2000 0x0020: Memory Base: 9000, Memory Limit: a300 0x0024: Prefetch Memory Base: fff1, Prefetch Memory Limit: 0001 0x0028: Prefetch Memory Base Upper 32 Bits: 0x002c: Prefetch Memory Limit Upper 32 Bits: 0x0030: I/O Base Upper 16 Bits: , I/O Limit Upper 16 Bits: 0x0038: Expansion ROM Base Address: 0x003c: Interrupt Pin: 01, Line: ff, Bridge Control: 0010 0x0088: Capability 0x0d: PCI-PCI 0x0080: Capability 0x01: Power Management State: D0 0x0090: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: yes 0x00a0: Capability 0x10: PCI Express Max Payload Size: 128 / 256 bytes Max Read Request Size: 128 bytes Link Speed: 5.0 / 8.0 GT/s Link Width: x8 / x8 0x0100: Enhanced Capability 0x02: Virtual Channel Capability 0x0140: Enhanced Capability 0x05: Root Complex Link Declaration 0x0d94: Enhanced Capability 0x19: Secondary PCIe Capability 0:2:0: Intel UHD Graphics 630 0x: Vendor ID: 8086, Product ID: 3e9b 0x0004: Command: 0007, Status: 0010 0x0008: Class: 03 Display, Subclass: 00 VGA, Interface: 00, Revision: 00 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem 64bit addr: 0xa400/0x0100 0x0018: BAR mem prefetchable 64bit addr: 0x8000/0x1000 0x0020: BAR io addr: 0x5000/0x0040 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1028 Product ID: 0949 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00 0x0040: Capability 0x09: Vendor Specific 0x0070: Capability 0x10: PCI Express Max Payload Size: 128 / 128 bytes Max Read Request Size: 128 bytes 0x0100: Enhanced Capability 0x1b: Process Address Space ID 0x0200: Enhanced Capability 0x0f: Address Translation Services 0x0300: Enhanced Capability 0x13: Page Request Interface 0x00ac: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: yes 0x00d0: Capability 0x01: Power Management State: D0 0:4:0: Intel Core 6G Thermal 0x: Vendor ID: 8086, Product ID: 1903 0x0004: Command: , Status: 0090 0x0008: Class: 11 DASP, Subclass: 80 Miscellaneous, Interface: 00, Revision: 07 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 00 0x0010: BAR mem 64bit addr: 0xa551/0x8000 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1028 Product ID: 0949 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00 0x0090: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: no 0x00d0: Capability 0x01: Power Management State: D0 0x00e0: Capability 0x09: Vendor Specific 0:8:0: Intel Core GMM 0x: Vendor ID: 8086, Product ID: 1911 0x0004: Command: , Status: 0010 0x0008: Class: 08 System, Subclass: 80 Miscellaneous, Interface: 00, Revision: 00 0x000c: BIST: 00, Header Type: 00, Latency Timer: 00, Cache Line Size: 10 0x0010: BAR mem 64bit addr: 0xa552b000/0x1000 0x0018: BAR empty () 0x001c: BAR empty () 0x0020: BAR empty () 0x0024: BAR empty () 0x0028: Cardbus CIS: 0x002c: Subsystem Vendor ID: 1028 Product ID: 0949 0x0030: Expansion ROM Base Address: 0x0038: 0x003c: Interrupt Pin: 01 Line: ff Min Gnt: 00 Max Lat: 00 0x0090: Capability 0x05: Message Signalled Interrupts (MSI) Enabled: no 0x00dc: Capability 0x01: Power Management State: D0 0x00f0: Capability 0x13: PCI Advanced Features 0:18:0: Intel 300 Series Thermal 0x: Vendor ID: 8086, Product ID: a379 0x0004: Command: 0006, Status: 0010 0x0008: Class: 11 DASP, Subclass: 80 Miscellaneous, Interface: 00, Revision: 10 0x000c: BIST: 00, Header Type: 80, Latency Tim
Re: Dell G3 3590 audio and touchpad
On 3/31/22 17:54, Adriano Barbosa wrote: Hi misc I'm trying to make audio and touchpad work on a Dell laptop. I've never played with this kind of stuff and I don't even know how to properly start. I have no hope on making NVIDIA hardware to work, but I believe Realtek ALC295 audio could work as, from what I got, it is supported by OpenBSD. [snip] Azalia driver doesnt detect your codecs correctly. On top of that, it may be a Dell specific hardware ID issue. Please post the output of pcidump -v
Dell G3 3590 audio and touchpad
Hi misc I'm trying to make audio and touchpad work on a Dell laptop. I've never played with this kind of stuff and I don't even know how to properly start. I have no hope on making NVIDIA hardware to work, but I believe Realtek ALC295 audio could work as, from what I got, it is supported by OpenBSD. >From FreeBSD (where audio and touchpad work) I get the following information: hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 7 on hdaa0 hdacc1: at cad 0 on hdac1 hdaa1: at nid 1 on hdacc1 pcm1: at nid 20 on hdaa1 pcm2: at nid 33 on hdaa1 hdacc2: at cad 2 on hdac1 hdaa2: at nid 1 on hdacc2 pcm3: at nid 3 on hdaa2 hms0: on hidbus0 hms0: 2 buttons and [XY] coordinates ID=1 hmt0: on hidbus0 hconf0: on hidbus0 hmt0: Multitouch touchpad with 0 external buttons, click-pad hmt0: 5 contacts with [C] properties. Report range [0:0] - [3211:2431] On OpenBSD (where audio and touchpad don't work) I can identify the following relevant information on dmesg: "Intel 300 Series cAVS" rev 0x10 at pci0 dev 31 function 3 not configured vendor "NVIDIA", unknown product 0x2191 (class display subclass VGA, rev 0xa1) at pci1 dev 0 function 0 not configured azalia0 at pci1 dev 0 function 1 vendor "NVIDIA", unknown product 0x1aeb rev 0xa1: msi azalia0: no supported codecs Full dmesg attached. Appreciate any help. Obrigado! -- Adriano Barbosa OpenBSD 7.1 (GENERIC.MP) #452: Wed Mar 30 09:18:07 MDT 2022 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 8359219200 (7971MB) avail mem = 8088596480 (7713MB) random: good seed from bootblocks mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 3.2 @ 0xe (116 entries) bios0: vendor Dell Inc. version "1.16.0" date 12/14/2021 bios0: Dell Inc. G3 3590 acpi0 at bios0: ACPI 6.1 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT FIDT MCFG SSDT BOOT SSDT SSDT HPET SSDT SSDT UEFI LPIT WSMT SSDT SSDT DBGP DBG2 SSDT SSDT MSDM SLIC DMAR SSDT SSDT NHLT BGRT TPM2 SSDT acpi0: wakeup devices PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) PEGP(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) PXSX(S4) RP04(S4) PXSX(S4) RP05(S4) PXSX(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 3990.70 MHz, 06-9e-0a cpu0: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu0: 256KB 64b/line 8-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 24MHz cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 3990.70 MHz, 06-9e-0a cpu1: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu1: 256KB 64b/line 8-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 3990.70 MHz, 06-9e-0a cpu2: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3DNOWP,PERF,ITSC,FSGSBASE,TSC_ADJUST,SGX,BMI1,AVX2,SMEP,BMI2,ERMS,INVPCID,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SRBDS_CTRL,MD_CLEAR,TSXFA,IBRS,IBPB,STIBP,L1DF,SSBD,SENSOR,ARAT,XSAVEOPT,XSAVEC,XGETBV1,XSAVES,MELTDOWN cpu2: 256KB 64b/line 8-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz, 3990.70 MHz, 06-9e-0a cpu3: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,SDBG,FMA3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,x2APIC,MOVBE,POPCNT,DEADLINE,AES,XSAVE,AVX,F16C,RDRAND,NXE,PAGE1GB,RDTSCP,LONG,LAHF,ABM,3
