Re: OT: protonmail mail body
Out of curiosity, I just checked what all the fuss is about. It turns out that someone reads mail with a non-RFC compliant client, and thus fails to read mime parts. Screw it, update your client. The other problem seemed to be with the list archive. It turns out that at least one archive has no problem at all (*). If other archives have mime problems, they can update themselves or just delete the mail. http://openbsd-archive.7691.n7.nabble.com/OT-protonmail-mail-body-td322547.html Sent from ProtonMail Mobile On Thu, Jul 13, 2017 at 2:39 PM, Bryan Steele wrote: > On Wed, Jul 12, 2017 at 10:09:11AM +0200, Alarig Le Lay wrote: > Hello, > > > It's just Base64 Content-Transfer-Encoding, and it's part of rfc2045. > > https://tools.ietf.org/html/rfc2045#section-6.8 > > So, the problem is on > marc.info side. Moreover, it's working on > mutt and on mail-archive: > > https://www.mail-archive.com/misc@openbsd.org/msg154853.html > > -- > alarig > The mailing lists have very simple rules, messages should be in English, > plain/text and generally not be MIME. Attachments should be avoided and sent > inline, unless accepted by the list. https://www.openbsd.org/mail.html > "ProtonMail" does not meet these requirements, by defalt. It's not just > marc.info archives, I suspect anyone using mail(1) is ignoring all of your > mails. -Bryan.
Re: vmd: routing problem
On Thu, Jul 20, 2017 at 04:23:40AM +0200, Leo Unglaub wrote: > Hey friends, > i am trying out vmd and I have a little problem getting networking going > inside the guest machine. I am not sure if this is a problem in vmd or > simply my misconfiguration. > > From my datacenter i got the following data: > > Main Server (OpenBSD GENERIC.MP#99 amd64) > # > IP: 144.76.102.204 > Netmask: 255.255.255.224 > Gateway: 144.76.102.193 > > > Virtual Machine (OpenBSD GENERIC.MP#99 amd64) > # > I got an entire subnet from the datacenter. 136.243.186.160/29 So i decided > to use the following IP in it. > > IP: 136.243.186.161 > Netmask: 255.255.255.248 > Gateway: 144.76.102.204 > > > According to there documentation they always route all subnets on the main > IP. In my case 144.76.102.204. > > > On my host I configured the em0 interface according to the datacenter data > and it works fine. The host who runs vmd is connected correctly. In my > /etc/vm.conf i created a switch called "uplink" and added em0 to it. When i > check the current config via ifconfig i get the following. > > > em0: flags=8b43 > > mtu 1500 > > lladdr 90:1b:0e:8b:0f:34 > > description: hetzner-uplink > > index 1 priority 0 llprio 3 > > groups: egress > > media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) > > status: active > > inet 144.76.102.204 netmask 0xffe0 broadcast 144.76.102.223 > > > > > > tap0: flags=8943 mtu 1500 > > lladdr fe:e1:ba:d0:7e:0a > > description: vm1-if0-foobar > > index 5 priority 0 llprio 3 > > groups: tap > > status: active > > > > bridge0: flags=41 > > description: switch1-uplink > > index 7 llprio 3 > > groups: bridge > > priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto > > rstp > > em0 flags=3 > > port 1 ifpriority 0 ifcost 0 > > tap0 flags=3 > > port 5 ifpriority 0 ifcost 0 > > Addresses (max cache: 100, timeout: 240): > > 0c:86:10:ed:35:58 em0 1 flags=0<> > > My /etc/vm.conf looks like this: > > > switch "uplink" { > > add em0 > > } > > > > vm "foobar" { > > memory 2G > > disk "/tmp/1.vdi" > > interface { > > switch "uplink" > > } > > } > > When i start the vm with my current /bsd.rd i start the installer and insert > the following: > > > Available network interfaces are: vio0 vlan0. > > Which network interface do you wish to configure? (or 'done') [vio0] > > IPv4 address for vio0? (or 'dhcp' or 'none') [dhcp] 136.243.186.161 > > Netmask for vio0? [255.255.255.248] IPv6 address for vio0? (or > > 'autoconf' or 'none') [none] Available network interfaces are: vio0 > > vlan0. > > Which network interface do you wish to configure? (or 'done') [done] > > Default IPv4 route? (IPv4 address or none) 144.76.102.204 > > add net default: gateway 144.76.102.204: Network is unreachable > > Can you people see something that i might missed? > Big thanks in advance and greetings > Leo > > sysctl net.inet.ip.forwarding=1 ? I'm not a networking expert but I think your VM's subnet mask is wrong for the gateway you are trying to use. -ml
vmd: routing problem
Hey friends, i am trying out vmd and I have a little problem getting networking going inside the guest machine. I am not sure if this is a problem in vmd or simply my misconfiguration. From my datacenter i got the following data: Main Server (OpenBSD GENERIC.MP#99 amd64) # IP: 144.76.102.204 Netmask: 255.255.255.224 Gateway: 144.76.102.193 Virtual Machine (OpenBSD GENERIC.MP#99 amd64) # I got an entire subnet from the datacenter. 136.243.186.160/29 So i decided to use the following IP in it. IP: 136.243.186.161 Netmask: 255.255.255.248 Gateway: 144.76.102.204 According to there documentation they always route all subnets on the main IP. In my case 144.76.102.204. On my host I configured the em0 interface according to the datacenter data and it works fine. The host who runs vmd is connected correctly. In my /etc/vm.conf i created a switch called "uplink" and added em0 to it. When i check the current config via ifconfig i get the following. em0: flags=8b43 mtu 1500 lladdr 90:1b:0e:8b:0f:34 description: hetzner-uplink index 1 priority 0 llprio 3 groups: egress media: Ethernet autoselect (1000baseT full-duplex,rxpause,txpause) status: active inet 144.76.102.204 netmask 0xffe0 broadcast 144.76.102.223 tap0: flags=8943 mtu 1500 lladdr fe:e1:ba:d0:7e:0a description: vm1-if0-foobar index 5 priority 0 llprio 3 groups: tap status: active bridge0: flags=41 description: switch1-uplink index 7 llprio 3 groups: bridge priority 32768 hellotime 2 fwddelay 15 maxage 20 holdcnt 6 proto rstp em0 flags=3 port 1 ifpriority 0 ifcost 0 tap0 flags=3 port 5 ifpriority 0 ifcost 0 Addresses (max cache: 100, timeout: 240): 0c:86:10:ed:35:58 em0 1 flags=0<> My /etc/vm.conf looks like this: switch "uplink" { add em0 } vm "foobar" { memory 2G disk "/tmp/1.vdi" interface { switch "uplink" } } When i start the vm with my current /bsd.rd i start the installer and insert the following: Available network interfaces are: vio0 vlan0. Which network interface do you wish to configure? (or 'done') [vio0] IPv4 address for vio0? (or 'dhcp' or 'none') [dhcp] 136.243.186.161 Netmask for vio0? [255.255.255.248] IPv6 address for vio0? (or 'autoconf' or 'none') [none] Available network interfaces are: vio0 vlan0. Which network interface do you wish to configure? (or 'done') [done] Default IPv4 route? (IPv4 address or none) 144.76.102.204 add net default: gateway 144.76.102.204: Network is unreachable Can you people see something that i might missed? Big thanks in advance and greetings Leo
Re: Mounting DVD with single file burned onto
Hi Josh! Thanks for caring! Am 07/19/17 um 22:58 schrieb Josh Grosse: > On Wed, Jul 19, 2017 at 09:24:56PM +0200, Stefan Wollny wrote: >> Hi there! >> >> Please excuse if this matter is not strictly OpenBSD-related even though >> I use OpenBSD. > > That's OK, I happen to be the maintainer of archivers/p7zip, and also of > sysutils/shunt, which you may want to experiment with. Way back in the > old days when I backed up to CD and later DVD, I used shunt to split > backups into disc-sized chunks and burn them in the backup pipeline. > I haven't used it in years, but it should work for this purpose. > >> When it comes to backups one usual advice (among others) is to make use >> of different storage types. So I have tar'ed one folder (~32GB) and >> zip'd with p7zip. man p7 explains the '-v{size}bkmg'-switch but I got >> "System ERROR: E_NOTIMPL". > > I am unable to recreate this problem on amd64. I just used > > $ vmctl create 100mb.file -s 100m > $ 7z a test.7z 100mb.file -v5k > > I obtained 4 output files, test.7z.0001 thru test.7z.0004. > This is the actual command and result: $ tar cf - /home/sw/Bilder/Nikon\ Transfer/20170430_Keukenhof/ | 7z a -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=on -v4880m -si Keukenhof_20170430.tar.7z tar: Removing leading / from absolute path names in the archive 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=de_DE.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs x64) System ERROR: E_NOTIMPL tar: Failed write to archive volume: 1: Broken pipe BUT: If I do it seperately like in your example it _does_ work out fine: $ 7z a -v4480m -t7z -m0=lzma -mx=9 -mfb=64 -md=32m -ms=on Keukenhof_20170430.7z Keukenhof_20170430.tar 7-Zip [64] 16.02 : Copyright (c) 1999-2016 Igor Pavlov : 2016-05-21 p7zip Version 16.02 (locale=de_DE.UTF-8,Utf16=on,HugeFiles=on,64 bits,4 CPUs x64) Scanning the drive: 1 file, 35988090880 bytes (34 GiB) Creating archive: Keukenhof_20170430.7z Items to compress: 1 [ ... ] {I am aware that this is not fast but time is not an issue here.} >> ... Using split(1) I ended with several files of >> ~4.5GB each of which got burned to a DVD like so: >> >> $ doas growisofs -dvd-compat -Z /dev/rcd0c= > > This is your key problem. The ISO file in "" needs to be > a CD9660/UFS file system when you use this form of the growisofs(1m) > command. Instead, it contains random compressed bits. This is why you > cannot mount it. > > Practice burning with DVD-RW or DVD+RW media. You can continue to play > with it until you have your procedure correct, usable, and reproducable. > OK - seems I need more patience with mkhybrid-documentation... Thanks again - I will do my best to do my homework! Best, STEFAN
Re: Mounting DVD with single file burned onto
On Wed, Jul 19, 2017 at 09:24:56PM +0200, Stefan Wollny wrote: > Hi there! > > Please excuse if this matter is not strictly OpenBSD-related even though > I use OpenBSD. That's OK, I happen to be the maintainer of archivers/p7zip, and also of sysutils/shunt, which you may want to experiment with. Way back in the old days when I backed up to CD and later DVD, I used shunt to split backups into disc-sized chunks and burn them in the backup pipeline. I haven't used it in years, but it should work for this purpose. > When it comes to backups one usual advice (among others) is to make use > of different storage types. So I have tar'ed one folder (~32GB) and > zip'd with p7zip. man p7 explains the '-v{size}bkmg'-switch but I got > "System ERROR: E_NOTIMPL". I am unable to recreate this problem on amd64. I just used $ vmctl create 100mb.file -s 100m $ 7z a test.7z 100mb.file -v5k I obtained 4 output files, test.7z.0001 thru test.7z.0004. > ... Using split(1) I ended with several files of > ~4.5GB each of which got burned to a DVD like so: > > $ doas growisofs -dvd-compat -Z /dev/rcd0c= This is your key problem. The ISO file in "" needs to be a CD9660/UFS file system when you use this form of the growisofs(1m) command. Instead, it contains random compressed bits. This is why you cannot mount it. Practice burning with DVD-RW or DVD+RW media. You can continue to play with it until you have your procedure correct, usable, and reproducable.
Re: Best place for VM images
On 18/07/2017 17:15, Theo de Raadt wrote: Sure. I don't have a really strong opinion one way or the other. When I mentioned I put mine in a dedicated partition, I use /data/vmm or various places in /home if I've already fully partitioned the machine in question. I don't think a seperate partition is neccessary. However I think this should stop saying /var/anything right away, because that is leading people in the wrong direction. I tend to store vital personal data in $HOME or /home/... in dedicated $HOME users but in my opinion there's nothing wrong to put anything available to all users in /usr/local/share/whathever and stay far away from /var regards, Luca
Mounting DVD with single file burned onto
Hi there! Please excuse if this matter is not strictly OpenBSD-related even though I use OpenBSD. When it comes to backups one usual advice (among others) is to make use of different storage types. So I have tar'ed one folder (~32GB) and zip'd with p7zip. man p7 explains the '-v{size}bkmg'-switch but I got "System ERROR: E_NOTIMPL". Using split(1) I ended with several files of ~4.5GB each of which got burned to a DVD like so: $ doas growisofs -dvd-compat -Z /dev/rcd0c= Burning took some time but finished without issues. NOW: How to get access to the part-file on the DVD? I cannot mount the DVD to get access to the part-file. Following the FAQ I used mkhybrid to produce .iso but this resulted in a significantly smaller file of ~340MB - beside that I doubt that this iso-file is correct it is a waste to burn this onto a DVD. I dd'ed the part-file to .iso which has the very same size and got burned to a DVD having the same result: I cannot mount the DVD to get access to the part-file. I read the applicable man-pages and searched in the archives, stackexchange and Google, but only found explanations on how to get a folder of a movie on _one_ DVD. I instead want to backup raw data. If I can't reassemble the part-files this is not a 'backup' but waste of time and money. Obviously I overlook something - could some kind soul give me hit with the clue stick? TIA. Best, STEFAN
Re: Getting Dell RAID status via SNMP
Darn. Well if you need more testers let me know.
Re: Openbsd 6.1 and Current Console Freezes and lockup Proxmox PVE5.0
Hello Tim, All, Just an Update, (copied from bugs mailing list to keep you in the loop, Proxmox5.0 running on AMD Opteron G2 2435 Based systems are NOT affected by the bug So the Bug seems to only affect Intel systems (well) IvyBridge Xeon e5 2660-v2 or Xeon X5650 based systems the OPenBSD 6.1 Release and OpenBSD Current systems running on proxmox 5.0 ve run fine without the Standard VGA Display...on Intel systems (ie they are operating on serial console only) I hope this helps
Re: AMD64 modern laptop recommendation
On 2017-07-18, Radoslav_Mirza wrote: > To congratulate myself for 2 years of not smoking I want to buy a new medium > to high end laptop and install only OpenBSD on it. > > Does anyone run OpenBSD on a brand new laptop with good support? I recently treated myself to a current (5th gen) Thinkpad X1 Carbon. The principal limitation at the moment, shared by all current laptops with a Kaby Lake CPU, is that there is no inteldrm(4) support yet: * You need to run X11 with wsfb(4). Non-accelerated, but perfectly fine for my use: window manager, xterms, web browser. * No backlight control. * No suspend/resume. Well, suspend works, and resume mostly works, except that there is no video. Beyond that, it just works. In particular, these work: * UEFI boot * nvme(4) for the SSD * em(4), Intel I219-V * iwm(4), 8265; the driver spews various warnings/errors but seems to work in practice * audio, keyboard, trackpoint, trackpad There is so much hardware, I haven't used or tested it all. I don't know about the status of these: * HDMI output * camera, uvideo(4) attaches * LTE modem, umb(4) attaches * fingerprint reader The poorly accessible SD card reader isn't supported. The UEFI BIOS comes with two sets of default settings. The normal ones and "OS Optimized Defaults" for Windows 10. My machine came configured with the latter, so I switched it back to the standard defaults. If you want to disable hyperthreading, you're out of luck: there is no such option. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: octeon packages
On 19 July 2017 at 07:47, Christian Weisgerber wrote: > On 2017-07-19, Predrag Punosevac wrote: > >> I got myself a new toy, Ubiquiti Networks - EdgeRouter Lite. I am a bit >> confused about packages for Octeon. I don't see any neither for 6.1 >> release nor for 6.1 snapshots. > > Use the mips64 packages. It's actually explained in INSTALL.octeon. > Wow! That's awesome, thanks for the pointer! > -- > Christian "naddy" Weisgerber na...@mips.inka.de > -- --- inum: 883510009027723 sip: jungleboo...@sip2sip.info
Re: octeon packages
On 2017-07-19, Predrag Punosevac wrote: > I got myself a new toy, Ubiquiti Networks - EdgeRouter Lite. I am a bit > confused about packages for Octeon. I don't see any neither for 6.1 > release nor for 6.1 snapshots. Use the mips64 packages. It's actually explained in INSTALL.octeon. -- Christian "naddy" Weisgerber na...@mips.inka.de
Re: octeon packages
On 07/19/2017 07:07 AM, Predrag Punosevac wrote: Hi Misc, I got myself a new toy, Ubiquiti Networks - EdgeRouter Lite. I am a bit confused about packages for Octeon. I don't see any neither for 6.1 release nor for 6.1 snapshots. Am I suppose to use only base system on this anemic hardware? I typically add sshguard for example to built in ssh brute force mechanism built in PF and I like to use ldapvi to edit ldap data base. Has anybody tried building any port on this thing? I haven't seen packages available for oceton before. The oceton snapshots are made available at nearly the rate of one a day, so I'm very thankful for that: https://ftp.openbsd.org/pub/OpenBSD/snapshots/octeon/ You can build certain applications on the ERL yourself. sshguard is pretty easy. Best, Predrag P.S. I do see mips64 and mips64el packages but my assumption is that mips64 are SGI packages while mips64el are loongson packages.
octeon packages
Hi Misc, I got myself a new toy, Ubiquiti Networks - EdgeRouter Lite. I am a bit confused about packages for Octeon. I don't see any neither for 6.1 release nor for 6.1 snapshots. Am I suppose to use only base system on this anemic hardware? I typically add sshguard for example to built in ssh brute force mechanism built in PF and I like to use ldapvi to edit ldap data base. Has anybody tried building any port on this thing? Best, Predrag P.S. I do see mips64 and mips64el packages but my assumption is that mips64 are SGI packages while mips64el are loongson packages.
System incredibly slow after resume from sleep/suspend
Hi, I'm running OpenBSD 6.1-current (GENERIC.MP) #99: Mon Jul 17. When I resume the system after sleep or standby (haven't tried hibernate yet) it will become unusably slow. apmd flags are '-A'. This state will persist a reboot and the following boot process will take close to ten minutes (compared to far less than a minute for a regular boot) and I'll have to power down the system to get it to normal performance. This is the first snapshot I've tried since april. At that time the backlight wouldn't light up after resume so I have never used sleep/suspend. Is there anything I should try? Thanks, Bengt OpenBSD 6.1-current (GENERIC.MP) #99: Mon Jul 17 16:53:49 MDT 2017 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP RTC BIOS diagnostic error 80 real mem = 17064067072 (16273MB) avail mem = 16541106176 (15774MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xe6a10 (26 entries) bios0: vendor Insyde Corp. version "V1.02" date 09/25/2015 bios0: Acer Aspire VN7-792G acpi0 at bios0: rev 2 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP TCPA UEFI SSDT SSDT SSDT DBG2 ASPT DBGP LPIT MCFG SSDT SSDT SSDT DMAR FPDT UEFI TPM2 DBGP BOOT APIC SSDT SSDT SSDT ASF! SSDT NHLT MSDM HPET acpi0: wakeup devices PEGP(S4) PEG0(S4) PEGP(S4) PEG1(S4) PEGP(S4) PEG2(S4) GLAN(S4) XHC_(S3) XDCI(S4) HDAS(S4) PXSX(S4) RP01(S4) PXSX(S4) RP02(S4) PXSX(S4) RP03(S4) [...] acpitimer0 at acpi0: 3579545 Hz, 24 bits acpimcfg0 at acpi0 addr 0xe000, bus 0-255 acpimadt0 at acpi0 addr 0xfee0: PC-AT compat cpu0 at mainbus0: apid 0 (boot processor) cpu0: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2592.00 MHz 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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu0: 256KB 64b/line 8-way L2 cache cpu0: TSC frequency 259200 Hz cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges cpu0: apic clock running at 23MHz 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-6700HQ CPU @ 2.60GHz, 2592.00 MHz 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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT 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-6700HQ CPU @ 2.60GHz, 2592.00 MHz 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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT 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-6700HQ CPU @ 2.60GHz, 2592.00 MHz 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,3DNOWP,PERF,ITSC,FSGSBASE,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu3: 256KB 64b/line 8-way L2 cache cpu3: smt 0, core 3, package 0 cpu4 at mainbus0: apid 1 (application processor) cpu4: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2592.00 MHz cpu4: 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,SGX,BMI1,HLE,AVX2,SMEP,BMI2,ERMS,INVPCID,RTM,MPX,RDSEED,ADX,SMAP,CLFLUSHOPT,PT,SENSOR,ARAT cpu4: 256KB 64b/line 8-way L2 cache cpu4: smt 1, core 0, package 0 cpu5 at mainbus0: apid 3 (application processor) cpu5: Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2592.00 MHz cpu5: FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR