Re: automounter (amd) local file system issue
On 2020-01-15 11:05, Strahil Nikolov wrote: > On January 13, 2020 5:40:06 AM GMT+02:00, Nick Holland > wrote: >>On 2020-01-12 15:39, Antoine Jacoutot wrote: >>> Sounds like something is keeping your fs busy. Could be gio-kqueue, >>do you have glib2 installed? >> >>That would be my first guess, too -- it's not unmounting because it >>shouldn't. But ... this is a VERY single purpose machine (backups >>via rsync --link-dest), and the only third party package is rsync >>and my scripts to do the backups. X is installed, but not running. >> >>$ pkg_info >>intel-firmware-20191115p0v0 microcode update binaries for Intel CPUs >>inteldrm-firmware-20181218 firmware binary images for inteldrm(4) >>driver >>quirks-3.216exceptions to pkg_add rules >>rsync-3.1.3 mirroring/synchronization over low bandwidth links >>vmm-firmware-1.11.0p2 firmware binary images for vmm(4) driver >> >>I was careful to access the amd mounts by ls , while >>sitting in my home directory, which is NOT part of the amd, so I >>didn't have a task under a doas or su camped out on the amd vols. >> >>I've tesed a lot of ways, but I just did an upgrade to -current and >>immediately "looked" at the amd mount, so even my backup scripts >>haven't run. >> >>Plus -- as a control, /v/2 has absolutely nothing on it, and it >>behaves the same way. Not that something couldn't camp out on the >>empty file system, but not much reason for something to do so. >> >>Thanks for looking! >> >>Nick. >> >> >>>  >>> Antoine >>> On 13 Jan 2020, at 06:01, Nick Holland >>wrote: Hiya. I'd like to use amd(8) to automatically mount and dismount local >>file systems. The file systems in question are big, lots of complicated links, lots of files, and take a while to fsck if the power goes out unexpectedly, and are used relatively rarely (maybe an hour a day). Sounds like a perfect job for amd(8)! The file systems in question are mounted to /v/1 and /v/2 I've got the following set up: $ cat /etc/rc.conf.local >> amd_flags=-l syslog -x all -c 10 -w 10 lockd_flags= portmap_flags= $ cat /etc/amd/master >> /v amd.v $ cat /etc/amd/amd.v 1 type:=ufs;dev:=/dev/sd2i 2 type:=ufs;dev:=/dev/sd2j ANDit works! start the system up, I get this: $ df Filesystem 512-blocks Used Avail Capacity Mounted on /dev/sd2a 101167620381275728421%/ /dev/sd2h 1031983648 9803800 0%/home /dev/sd2f 413682820 3929968 0%/tmp /dev/sd2d 8264188 2369920 548106030%/usr /dev/sd2e 2065116 2104 1959760 0%/usr/local /dev/sd2g 4136828 64920 3865068 2%/var amd:365830 0 0 100%/v $ ls /v/1/ [...expected output from files and directories on that file >>system...] $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd2a 505838 8360239694617%/ /dev/sd2h 515991824 4901900 0%/home /dev/sd2f 206841410 1964984 0%/tmp /dev/sd2d 4132094 1280264 264522633%/usr /dev/sd2e 1032558 1052979880 0%/usr/local /dev/sd2g 2068414 32572 1932422 2%/var amd:92953 0 0 0 100%/v /dev/sd2i 2106117872 298739480 170207250415% >>/tmp_mnt/dbu/v/1 Success!! well...no. Seems it never umounts the amd file systems. And that >>is basically the point of this exercise -- to increase the odds that a >>FS isn't mounted when the power goes out. Am I doing something wrong? Do I have inaccurate expectations of what amd(8) does with local file systems? Nick. ... > Hi Nick, > > Can you test removing '-w 10' from the daemon's flags in order to test with > the default 2min timeout. > > I have a vague feeling that 10 seconds is way too short... You are right -- that was something I tried so I quit having to wait 5+ minutes every time I tried something different, so I stuffed absurdly short timeouts in place for testing, but there was no change. I've reverted those changes, and (as I expected), it is still not unmounting. New: $ cat /etc/rc.conf.local amd_flags=-l syslog -x all lockd_flags= portmap_flags= (the -x all was added to see if amd logged any dismount attempts or why they failed...nothing) So thanks, but ... no change. :-/ Nick.
Re: automounter (amd) local file system issue
On January 13, 2020 5:40:06 AM GMT+02:00, Nick Holland wrote: >On 2020-01-12 15:39, Antoine Jacoutot wrote: >> Sounds like something is keeping your fs busy. Could be gio-kqueue, >do you have glib2 installed? > >That would be my first guess, too -- it's not unmounting because it >shouldn't. But ... this is a VERY single purpose machine (backups >via rsync --link-dest), and the only third party package is rsync >and my scripts to do the backups. X is installed, but not running. > >$ pkg_info >intel-firmware-20191115p0v0 microcode update binaries for Intel CPUs >inteldrm-firmware-20181218 firmware binary images for inteldrm(4) >driver >quirks-3.216exceptions to pkg_add rules >rsync-3.1.3 mirroring/synchronization over low bandwidth links >vmm-firmware-1.11.0p2 firmware binary images for vmm(4) driver > >I was careful to access the amd mounts by ls , while >sitting in my home directory, which is NOT part of the amd, so I >didn't have a task under a doas or su camped out on the amd vols. > >I've tesed a lot of ways, but I just did an upgrade to -current and >immediately "looked" at the amd mount, so even my backup scripts >haven't run. > >Plus -- as a control, /v/2 has absolutely nothing on it, and it >behaves the same way. Not that something couldn't camp out on the >empty file system, but not much reason for something to do so. > >Thanks for looking! > >Nick. > > >> — >> Antoine >> >>> On 13 Jan 2020, at 06:01, Nick Holland >wrote: >>> >>> Hiya. >>> >>> I'd like to use amd(8) to automatically mount and dismount local >file >>> systems. The file systems in question are big, lots of complicated >>> links, lots of files, and take a while to fsck if the power goes out >>> unexpectedly, and are used relatively rarely (maybe an hour a day). >>> Sounds like a perfect job for amd(8)! >>> >>> The file systems in question are mounted to /v/1 and /v/2 >>> >>> I've got the following set up: >>> >>> $ cat /etc/rc.conf.local > >>> amd_flags=-l syslog -x all -c 10 -w 10 >>> lockd_flags= >>> portmap_flags= >>> >>> $ cat /etc/amd/master > >>> /v amd.v >>> >>> $ cat /etc/amd/amd.v >>> 1 type:=ufs;dev:=/dev/sd2i >>> 2 type:=ufs;dev:=/dev/sd2j >>> >>> >>> ANDit works! >>> >>> start the system up, I get this: >>> >>> $ df >>> Filesystem 512-blocks Used Avail Capacity Mounted on >>> /dev/sd2a 101167620381275728421%/ >>> /dev/sd2h 1031983648 9803800 0%/home >>> /dev/sd2f 413682820 3929968 0%/tmp >>> /dev/sd2d 8264188 2369920 548106030%/usr >>> /dev/sd2e 2065116 2104 1959760 0%/usr/local >>> /dev/sd2g 4136828 64920 3865068 2%/var >>> amd:365830 0 0 100%/v >>> >>> $ ls /v/1/ >>> [...expected output from files and directories on that file >system...] >>> >>> $ df >>> Filesystem 1K-blocks Used Avail Capacity Mounted on >>> /dev/sd2a 505838 8360239694617%/ >>> /dev/sd2h 515991824 4901900 0%/home >>> /dev/sd2f 206841410 1964984 0%/tmp >>> /dev/sd2d 4132094 1280264 264522633%/usr >>> /dev/sd2e 1032558 1052979880 0%/usr/local >>> /dev/sd2g 2068414 32572 1932422 2%/var >>> amd:92953 0 0 0 100%/v >>> /dev/sd2i 2106117872 298739480 170207250415% >/tmp_mnt/dbu/v/1 >>> >>> Success!! >>> well...no. Seems it never umounts the amd file systems. And that >is >>> basically the point of this exercise -- to increase the odds that a >FS >>> isn't mounted when the power goes out. >>> >>> Am I doing something wrong? Do I have inaccurate expectations of >>> what amd(8) does with local file systems? >>> >>> Nick. >>> >>> OpenBSD 6.6-current (GENERIC.MP) #599: Sat Jan 11 18:52:00 MST 2020 >>> >dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP >>> real mem = 2038652928 (1944MB) >>> avail mem = 1964462080 (1873MB) >>> mpath0 at root >>> scsibus0 at mpath0: 256 targets >>> mainbus0 at root >>> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebd30 (52 entries) >>> bios0: vendor American Megatrends Inc. version "1020" date >12/15/2014 >>> bios0: PowerSpec V400 >>> acpi0 at bios0: ACPI 5.0 >>> acpi0: sleep states S0 S3 S4 S5 >>> acpi0: tables DSDT FACP APIC FPDT MSDM MCFG LPIT SLIC HPET SSDT SSDT >SSDT UEFI >>> acpi0: wakeup devices XHC1(S3) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) >PWRB(S0) >>> 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) Pentium(R) CPU J2900 @ 2.41GHz, 2417.12 MHz, 06-37-08 >>> cpu0:
Re: automounter (amd) local file system issue
On 2020-01-12 15:39, Antoine Jacoutot wrote: > Sounds like something is keeping your fs busy. Could be gio-kqueue, do you > have glib2 installed? That would be my first guess, too -- it's not unmounting because it shouldn't. But ... this is a VERY single purpose machine (backups via rsync --link-dest), and the only third party package is rsync and my scripts to do the backups. X is installed, but not running. $ pkg_info intel-firmware-20191115p0v0 microcode update binaries for Intel CPUs inteldrm-firmware-20181218 firmware binary images for inteldrm(4) driver quirks-3.216exceptions to pkg_add rules rsync-3.1.3 mirroring/synchronization over low bandwidth links vmm-firmware-1.11.0p2 firmware binary images for vmm(4) driver I was careful to access the amd mounts by ls , while sitting in my home directory, which is NOT part of the amd, so I didn't have a task under a doas or su camped out on the amd vols. I've tesed a lot of ways, but I just did an upgrade to -current and immediately "looked" at the amd mount, so even my backup scripts haven't run. Plus -- as a control, /v/2 has absolutely nothing on it, and it behaves the same way. Not that something couldn't camp out on the empty file system, but not much reason for something to do so. Thanks for looking! Nick. > — > Antoine > >> On 13 Jan 2020, at 06:01, Nick Holland wrote: >> >> Hiya. >> >> I'd like to use amd(8) to automatically mount and dismount local file >> systems. The file systems in question are big, lots of complicated >> links, lots of files, and take a while to fsck if the power goes out >> unexpectedly, and are used relatively rarely (maybe an hour a day). >> Sounds like a perfect job for amd(8)! >> >> The file systems in question are mounted to /v/1 and /v/2 >> >> I've got the following set up: >> >> $ cat /etc/rc.conf.local >> amd_flags=-l syslog -x all -c 10 -w 10 >> lockd_flags= >> portmap_flags= >> >> $ cat /etc/amd/master >> /v amd.v >> >> $ cat /etc/amd/amd.v >> 1 type:=ufs;dev:=/dev/sd2i >> 2 type:=ufs;dev:=/dev/sd2j >> >> >> ANDit works! >> >> start the system up, I get this: >> >> $ df >> Filesystem 512-blocks Used Avail Capacity Mounted on >> /dev/sd2a 101167620381275728421%/ >> /dev/sd2h 1031983648 9803800 0%/home >> /dev/sd2f 413682820 3929968 0%/tmp >> /dev/sd2d 8264188 2369920 548106030%/usr >> /dev/sd2e 2065116 2104 1959760 0%/usr/local >> /dev/sd2g 4136828 64920 3865068 2%/var >> amd:365830 0 0 100%/v >> >> $ ls /v/1/ >> [...expected output from files and directories on that file system...] >> >> $ df >> Filesystem 1K-blocks Used Avail Capacity Mounted on >> /dev/sd2a 505838 8360239694617%/ >> /dev/sd2h 515991824 4901900 0%/home >> /dev/sd2f 206841410 1964984 0%/tmp >> /dev/sd2d 4132094 1280264 264522633%/usr >> /dev/sd2e 1032558 1052979880 0%/usr/local >> /dev/sd2g 2068414 32572 1932422 2%/var >> amd:92953 0 0 0 100%/v >> /dev/sd2i 2106117872 298739480 170207250415%/tmp_mnt/dbu/v/1 >> >> Success!! >> well...no. Seems it never umounts the amd file systems. And that is >> basically the point of this exercise -- to increase the odds that a FS >> isn't mounted when the power goes out. >> >> Am I doing something wrong? Do I have inaccurate expectations of >> what amd(8) does with local file systems? >> >> Nick. >> >> OpenBSD 6.6-current (GENERIC.MP) #599: Sat Jan 11 18:52:00 MST 2020 >>dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP >> real mem = 2038652928 (1944MB) >> avail mem = 1964462080 (1873MB) >> mpath0 at root >> scsibus0 at mpath0: 256 targets >> mainbus0 at root >> bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebd30 (52 entries) >> bios0: vendor American Megatrends Inc. version "1020" date 12/15/2014 >> bios0: PowerSpec V400 >> acpi0 at bios0: ACPI 5.0 >> acpi0: sleep states S0 S3 S4 S5 >> acpi0: tables DSDT FACP APIC FPDT MSDM MCFG LPIT SLIC HPET SSDT SSDT SSDT >> UEFI >> acpi0: wakeup devices XHC1(S3) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PWRB(S0) >> 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) Pentium(R) CPU J2900 @ 2.41GHz, 2417.12 MHz, 06-37-08 >> cpu0: >>
Re: automounter (amd) local file system issue
Sounds like something is keeping your fs busy. Could be gio-kqueue, do you have glib2 installed? — Antoine > On 13 Jan 2020, at 06:01, Nick Holland wrote: > > Hiya. > > I'd like to use amd(8) to automatically mount and dismount local file > systems. The file systems in question are big, lots of complicated > links, lots of files, and take a while to fsck if the power goes out > unexpectedly, and are used relatively rarely (maybe an hour a day). > Sounds like a perfect job for amd(8)! > > The file systems in question are mounted to /v/1 and /v/2 > > I've got the following set up: > > $ cat /etc/rc.conf.local > amd_flags=-l syslog -x all -c 10 -w 10 > lockd_flags= > portmap_flags= > > $ cat /etc/amd/master > /v amd.v > > $ cat /etc/amd/amd.v > 1 type:=ufs;dev:=/dev/sd2i > 2 type:=ufs;dev:=/dev/sd2j > > > ANDit works! > > start the system up, I get this: > > $ df > Filesystem 512-blocks Used Avail Capacity Mounted on > /dev/sd2a 101167620381275728421%/ > /dev/sd2h 1031983648 9803800 0%/home > /dev/sd2f 413682820 3929968 0%/tmp > /dev/sd2d 8264188 2369920 548106030%/usr > /dev/sd2e 2065116 2104 1959760 0%/usr/local > /dev/sd2g 4136828 64920 3865068 2%/var > amd:365830 0 0 100%/v > > $ ls /v/1/ > [...expected output from files and directories on that file system...] > > $ df > Filesystem 1K-blocks Used Avail Capacity Mounted on > /dev/sd2a 505838 8360239694617%/ > /dev/sd2h 515991824 4901900 0%/home > /dev/sd2f 206841410 1964984 0%/tmp > /dev/sd2d 4132094 1280264 264522633%/usr > /dev/sd2e 1032558 1052979880 0%/usr/local > /dev/sd2g 2068414 32572 1932422 2%/var > amd:92953 0 0 0 100%/v > /dev/sd2i 2106117872 298739480 170207250415%/tmp_mnt/dbu/v/1 > > Success!! > well...no. Seems it never umounts the amd file systems. And that is > basically the point of this exercise -- to increase the odds that a FS > isn't mounted when the power goes out. > > Am I doing something wrong? Do I have inaccurate expectations of > what amd(8) does with local file systems? > > Nick. > > OpenBSD 6.6-current (GENERIC.MP) #599: Sat Jan 11 18:52:00 MST 2020 >dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP > real mem = 2038652928 (1944MB) > avail mem = 1964462080 (1873MB) > mpath0 at root > scsibus0 at mpath0: 256 targets > mainbus0 at root > bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebd30 (52 entries) > bios0: vendor American Megatrends Inc. version "1020" date 12/15/2014 > bios0: PowerSpec V400 > acpi0 at bios0: ACPI 5.0 > acpi0: sleep states S0 S3 S4 S5 > acpi0: tables DSDT FACP APIC FPDT MSDM MCFG LPIT SLIC HPET SSDT SSDT SSDT UEFI > acpi0: wakeup devices XHC1(S3) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PWRB(S0) > 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) Pentium(R) CPU J2900 @ 2.41GHz, 2417.12 MHz, 06-37-08 > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > cpu0: 1MB 64b/line 16-way L2 cache > cpu0: smt 0, core 0, package 0 > mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges > cpu0: apic clock running at 83MHz > cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE > cpu1 at mainbus0: apid 2 (application processor) > cpu1: Intel(R) Pentium(R) CPU J2900 @ 2.41GHz, 2416.67 MHz, 06-37-08 > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > cpu1: 1MB 64b/line 16-way L2 cache > cpu1: smt 0, core 1, package 0 > cpu2 at mainbus0: apid 4 (application processor) > cpu2: Intel(R) Pentium(R) CPU J2900 @ 2.41GHz, 2416.69 MHz, 06-37-08 > 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN > cpu2: 1MB 64b/line 16-way L2 cache > cpu2:
automounter (amd) local file system issue
Hiya. I'd like to use amd(8) to automatically mount and dismount local file systems. The file systems in question are big, lots of complicated links, lots of files, and take a while to fsck if the power goes out unexpectedly, and are used relatively rarely (maybe an hour a day). Sounds like a perfect job for amd(8)! The file systems in question are mounted to /v/1 and /v/2 I've got the following set up: $ cat /etc/rc.conf.local amd_flags=-l syslog -x all -c 10 -w 10 lockd_flags= portmap_flags= $ cat /etc/amd/master /v amd.v $ cat /etc/amd/amd.v 1 type:=ufs;dev:=/dev/sd2i 2 type:=ufs;dev:=/dev/sd2j ANDit works! start the system up, I get this: $ df Filesystem 512-blocks Used Avail Capacity Mounted on /dev/sd2a 101167620381275728421%/ /dev/sd2h 1031983648 9803800 0%/home /dev/sd2f 413682820 3929968 0%/tmp /dev/sd2d 8264188 2369920 548106030%/usr /dev/sd2e 2065116 2104 1959760 0%/usr/local /dev/sd2g 4136828 64920 3865068 2%/var amd:365830 0 0 100%/v $ ls /v/1/ [...expected output from files and directories on that file system...] $ df Filesystem 1K-blocks Used Avail Capacity Mounted on /dev/sd2a 505838 8360239694617%/ /dev/sd2h 515991824 4901900 0%/home /dev/sd2f 206841410 1964984 0%/tmp /dev/sd2d 4132094 1280264 264522633%/usr /dev/sd2e 1032558 1052979880 0%/usr/local /dev/sd2g 2068414 32572 1932422 2%/var amd:92953 0 0 0 100%/v /dev/sd2i 2106117872 298739480 170207250415%/tmp_mnt/dbu/v/1 Success!! well...no. Seems it never umounts the amd file systems. And that is basically the point of this exercise -- to increase the odds that a FS isn't mounted when the power goes out. Am I doing something wrong? Do I have inaccurate expectations of what amd(8) does with local file systems? Nick. OpenBSD 6.6-current (GENERIC.MP) #599: Sat Jan 11 18:52:00 MST 2020 dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP real mem = 2038652928 (1944MB) avail mem = 1964462080 (1873MB) mpath0 at root scsibus0 at mpath0: 256 targets mainbus0 at root bios0 at mainbus0: SMBIOS rev. 2.8 @ 0xebd30 (52 entries) bios0: vendor American Megatrends Inc. version "1020" date 12/15/2014 bios0: PowerSpec V400 acpi0 at bios0: ACPI 5.0 acpi0: sleep states S0 S3 S4 S5 acpi0: tables DSDT FACP APIC FPDT MSDM MCFG LPIT SLIC HPET SSDT SSDT SSDT UEFI acpi0: wakeup devices XHC1(S3) PXSX(S4) PXSX(S4) PXSX(S4) PXSX(S4) PWRB(S0) 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) Pentium(R) CPU J2900 @ 2.41GHz, 2417.12 MHz, 06-37-08 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu0: 1MB 64b/line 16-way L2 cache cpu0: smt 0, core 0, package 0 mtrr: Pentium Pro MTRR support, 8 var ranges, 88 fixed ranges cpu0: apic clock running at 83MHz cpu0: mwait min=64, max=64, C-substates=0.2.0.0.0.0.3.3, IBE cpu1 at mainbus0: apid 2 (application processor) cpu1: Intel(R) Pentium(R) CPU J2900 @ 2.41GHz, 2416.67 MHz, 06-37-08 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu1: 1MB 64b/line 16-way L2 cache cpu1: smt 0, core 1, package 0 cpu2 at mainbus0: apid 4 (application processor) cpu2: Intel(R) Pentium(R) CPU J2900 @ 2.41GHz, 2416.69 MHz, 06-37-08 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,CX16,xTPR,PDCM,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,RDRAND,NXE,RDTSCP,LONG,LAHF,3DNOWP,PERF,ITSC,TSC_ADJUST,SMEP,ERMS,MD_CLEAR,IBRS,IBPB,STIBP,SENSOR,ARAT,MELTDOWN cpu2: 1MB 64b/line 16-way L2 cache cpu2: smt 0, core 2, package 0 cpu3 at mainbus0: apid 6 (application processor) cpu3: Intel(R) Pentium(R) CPU J2900 @ 2.41GHz, 2416.68 MHz, 06-37-08 cpu3:
