FreeBSD 13.0-BETA2 and slow IO

2021-02-16 Thread Christos Chatzaras
I build a test system with 13.0-BETA2 and it's very slow with at least IO.

Doing "portsnap auto" takes much more time than 12.2.

Also when I do "rm -fr /usr/ports" with 12.2 takes 5 seconds and the same 
command with 13.0-BETA2 takes 100 seconds.

The disks are similar 4TB HDD drives on both systems.

Is this related to debug enabled in 13.0-BETA2?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD 13.0-BETA2 and slow IO

2021-02-16 Thread Christos Chatzaras


> On 16 Feb 2021, at 12:20, Christos Chatzaras  wrote:
> 
> I build a test system with 13.0-BETA2 and it's very slow with at least IO.
> 
> Doing "portsnap auto" takes much more time than 12.2.
> 
> Also when I do "rm -fr /usr/ports" with 12.2 takes 5 seconds and the same 
> command with 13.0-BETA2 takes 100 seconds.
> 
> The disks are similar 4TB HDD drives on both systems.
> 
> Is this related to debug enabled in 13.0-BETA2?

I install 12.2 in the same system and "rm -fr /usr/ports" was fast. So it's not 
related to hardware.

If I upgrade it to 13.0-BETA2 the same command is slow again.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD 13.0-BETA2 and slow IO

2021-02-16 Thread Konstantin Belousov
On Tue, Feb 16, 2021 at 12:54:55PM +0200, Christos Chatzaras wrote:
> 
> > On 16 Feb 2021, at 12:20, Christos Chatzaras  wrote:
> > 
> > I build a test system with 13.0-BETA2 and it's very slow with at least IO.
> > 
> > Doing "portsnap auto" takes much more time than 12.2.
> > 
> > Also when I do "rm -fr /usr/ports" with 12.2 takes 5 seconds and the same 
> > command with 13.0-BETA2 takes 100 seconds.
> > 
> > The disks are similar 4TB HDD drives on both systems.
> > 
> > Is this related to debug enabled in 13.0-BETA2?
> 
> I install 12.2 in the same system and "rm -fr /usr/ports" was fast. So it's 
> not related to hardware.
> 
> If I upgrade it to 13.0-BETA2 the same command is slow again.

Are you using UFS+SU or SU+J?  If yes, this is known and fix is planned
for BETA3 or BETA4.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD 13.0-BETA2 and slow IO

2021-02-16 Thread Christos Chatzaras


> On 16 Feb 2021, at 13:06, Konstantin Belousov  wrote:
> 
> Are you using UFS+SU or SU+J?  If yes, this is known and fix is planned
> for BETA3 or BETA4.
> 

Thank you for your reply. I use UFS+SU. I will do the test again after the 
commit that fixes the issue.
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: FreeBSD 13.0-BETA2 Now Available

2021-02-16 Thread Jason Tubnor
On Sat, 13 Feb 2021 at 09:52, Glen Barber  wrote:

> The second BETA build of the 13.0-RELEASE release cycle is now available.
>
>
> === Upgrading ===
>
> The freebsd-update(8) utility supports binary upgrades of amd64, i386
> and aarch64 systems running earlier FreeBSD releases.  Systems running
> earlier FreeBSD releases can upgrade as follows:
>
> # freebsd-update upgrade -r 13.0-BETA2
>
> During this process, freebsd-update(8) may ask the user to help by
> merging some configuration files or by confirming that the automatically
> performed merging was done correctly.
>
> # freebsd-update install
>
> The system must be rebooted with the newly installed kernel before
> continuing.
>
> # shutdown -r now
>
> After rebooting, freebsd-update needs to be run again to install the new
> userland components:
>
> # freebsd-update install
>

If your host is only trunked to VLANs and not on a PVID, this step will not
work if you are upgrading from 11.4 or 12.2.  After reboot, ifconfig will
not be able to configure network interfaces for VLAN tagging.  It appears
to be set correctly after reboot but packets will not be tagged thus
dropped on the switch.  Once the above freebsd-update install has
completed, ifconfig will work correctly and the host will have network
access again.

Workaround:

1. Using IPMI/LOM access, login as root and issue freebsd-update install
(not desirable for non-IPMI access on a remote host)
2. Allowing sufficient time for a reboot, put a future cron job in place
that executes freebsd-update install && shutdown -r now


> It is recommended to rebuild and install all applications if possible,
> especially if upgrading from an earlier FreeBSD release, for example,
> FreeBSD 11.x.  Alternatively, the user can install misc/compat11x and
> other compatibility libraries, afterwards the system must be rebooted
> into the new userland:
>
> # shutdown -r now
>
> Finally, after rebooting, freebsd-update needs to be run again to remove
> stale files:
>
> # freebsd-update install
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: 13-stable default boot options problem

2021-02-16 Thread Alex V. Petrov
I found my problem. I tryed latest snapshot version of 13 (
https://download.freebsd.org/ftp/snapshots/ISO-IMAGES/13.0/FreeBSD-13.0-ALPHA3-amd64-20210129-40cb0344eb2-256214-disc1.iso
).
In time boot I see:
On modern notebook with hibryd graphic: modern graphicaly boot menu with
option "Cons - Video" as default.
On my desktop with NVidia GF GTX1070: textly menu with option "Cons -
Serial".
My question: As in my case set option "Cons - Video" as default?

ср, 10 февр. 2021 г. в 14:37, Alex V. Petrov :

> My loader.conf:
> #console="vidconsole"
> #console="efi,comconsole"
> #console="Video"
> kern.geom.label.disk_ident.enable="0"
> kern.geom.label.gptid.enable="0"
> cryptodev_load="YES"
> zfs_load="YES"
> vfs.zfs.arc_max="8192M"
> sem_load="YES"
> snd_hda_load="YES"
> linux_load="YES"
> net.graph.maxdata=65536
> amdtemp_load="YES"
> cuse_load="YES"
> kern.racct.enable="1"
>
> 08.02.2021 04:26, Paul Mather пишет:
> > On Feb 7, 2021, at 4:33 AM, Alex V. Petrov 
> wrote:
> >
> >> I still don't resolved my problem.
> >> How change default Cons=Serial  to Cons=Video?
> >>
> >> Screenshot: https://imgur.com/SNXUrZH.png
> >>
> >> My system:
> >> FreeBSD 13.0-STABLE #79 stable/13-n244485-6136a10e355: Sat Feb  6
> >> 22:05:30 +07 2021 amd64
> >
> > It's not clear to me what problem you are having or attempting to solve.
> >
> > The "5" option in the boot menu lets you cycle through the different
> console options (all four in total).  In my case, it has no effect because
> I set "comconsole" and "boot_multicons" explicitly in /boot/loader.conf
> (since a long time ago), and no matter what I select via the console
> loader, it is overridden by what is loaded from /boot/loader.conf during
> loading and booting the kernel.
> >
> > Do you similarly have something in /boot/loader.conf that is overriding
> the console setting?
> >
> > Cheers,
> >
> > Paul.
> >
> >
> --
> -
> Alex.
>
>

-- 
--
Alex V. Petrov
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


est and turbo boost

2021-02-16 Thread Eugene Grosbein
Hi!

We use leased server Dell PowerEdge R640 with latest firmware (BIOS/UEFI)
that does not export ACPI _PSS table, so FreeBSD 12.2-RELEASE/amd64 (GENERIC)
est(4) driver does not attach:

est0:  numa-domain 0 on cpu0
est: CPU supports Enhanced Speedstep, but is not recognized.
est: cpu_vendor GenuineIntel, msr 1bc41c00
device_attach: est0 attach returned 6

Hence, no CPU frequency control and no TurboBoost for the CPU:

CPU: Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz (2294.68-MHz K8-class CPU)
  Origin="GenuineIntel"  Id=0x50657  Family=0x6  Model=0x55  Stepping=7
  
Features=0xbfebfbff
  AMD Features2=0x121
  Structured Extended 
Features=0xd39b
  Structured Extended 
Features3=0xbc000400
  XSAVE Features=0xf
  IA32_ARCH_CAPS=0xab
  VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
  TSC: P-state invariant, performance statistics
ACPI APIC Table: 
FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs
FreeBSD/SMP: 2 package(s) x 16 core(s)

Logical processors (hyperthreading) disabled in server's SETUP.

I've tried to use loader prompt to set hw.est.msr_info=1
but then is panices early at boot time with "integer divide fault".
No crashdump generated but a screenshot is available:

http://www.grosbein.net/freebsd/est-panic.jpg

What are options to enable est/TurboBoost in this case?
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: est and turbo boost

2021-02-16 Thread Jack L.
I've noticed for Dells, you have to set the performance setting to
"Custom" and OS Control to be able to change the EST.

On Tue, Feb 16, 2021 at 7:12 PM Eugene Grosbein  wrote:
>
> Hi!
>
> We use leased server Dell PowerEdge R640 with latest firmware (BIOS/UEFI)
> that does not export ACPI _PSS table, so FreeBSD 12.2-RELEASE/amd64 (GENERIC)
> est(4) driver does not attach:
>
> est0:  numa-domain 0 on cpu0
> est: CPU supports Enhanced Speedstep, but is not recognized.
> est: cpu_vendor GenuineIntel, msr 1bc41c00
> device_attach: est0 attach returned 6
>
> Hence, no CPU frequency control and no TurboBoost for the CPU:
>
> CPU: Intel(R) Xeon(R) Gold 5218 CPU @ 2.30GHz (2294.68-MHz K8-class CPU)
>   Origin="GenuineIntel"  Id=0x50657  Family=0x6  Model=0x55  Stepping=7
>   
> Features=0xbfebfbff   
> Features2=0x7ffefbff   AMD Features=0x2c100800
>   AMD Features2=0x121
>   Structured Extended 
> Features=0xd39b   Structured Extended Features2=0x808
>   Structured Extended 
> Features3=0xbc000400
>   XSAVE Features=0xf
>   IA32_ARCH_CAPS=0xab
>   VT-x: PAT,HLT,MTF,PAUSE,EPT,UG,VPID,VID,PostIntr
>   TSC: P-state invariant, performance statistics
> ACPI APIC Table: 
> FreeBSD/SMP: Multiprocessor System Detected: 32 CPUs
> FreeBSD/SMP: 2 package(s) x 16 core(s)
>
> Logical processors (hyperthreading) disabled in server's SETUP.
>
> I've tried to use loader prompt to set hw.est.msr_info=1
> but then is panices early at boot time with "integer divide fault".
> No crashdump generated but a screenshot is available:
>
> http://www.grosbein.net/freebsd/est-panic.jpg
>
> What are options to enable est/TurboBoost in this case?
> ___
> freebsd-stable@freebsd.org mailing list
> https://lists.freebsd.org/mailman/listinfo/freebsd-stable
> To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"
___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"


Re: est and turbo boost

2021-02-16 Thread Eugene Grosbein
17.02.2021 10:40, Jack L. wrote:

> I've noticed for Dells, you have to set the performance setting to
> "Custom" and OS Control to be able to change the EST.

I've already tried numerous variants of BIOS setting including "Maximum 
Performance"
and "Custom" and still, ACPI BIOS does not export _PSS table required for 
est(4).


___
freebsd-stable@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "freebsd-stable-unsubscr...@freebsd.org"