freebsd 13 ryzen micro stutter

[monochrome]

After about 8 months of struggling to narrow this down I did another 
search and saw this:


https://www.reddit.com/r/freebsd/comments/lc8fwo/freebsd_13_vega_64_micro_stutter_in_x/

I haven't seen this come up here so I thought I would bring it up.

My story started sometime before around August last year when synergy 
started getting really annoying with stuttering. Pretty sure it wasn't 
like that when I first started tracking 13-current in around May 2020 (I 
was on 12 with scfb for a long time before that with no issues), but 
since then I have tried to eliminate as many variables as possible. 
First I switched to barrier instead of synergy. Shortly after that I 
realized it was happening all the time and not just a network problem, I 
started using foobillard to verify during tests. I tried different RAM 
combinations, different network cards, a variety of RAM timings, 
stripping rc.conf etc, powerd settings, also scfb, with no effect. It is 
observable with ping -f, a dot or two appears every time it glitches. It 
seemed much better with RC2, but now with RC3 it seems to be back with a 
vengeance, and since its my main workstation and barrier/synergy server 
host for several machines, it is unbearable to use. Both Win10 and 
devuan3 on the same machine are smooth with no issues. Any feedback or 
info would be appreciated.


Hardware:
ASRock B450M Pro4
Ryzen 2400G, no OC
32M DDR4-2933
Onboard Vega GPU, drm-fbsd13-kmod
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

[Bug 254395] bsdinstall: fail script install after BETA3

[bugzilla-noreply]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=254395

--- Comment #12 from Nathan Whitehorn  ---
Related things:

https://reviews.freebsd.org/D29380 <- patch in review here
https://github.com/libarchive/libarchive/issues/1516 <- libarchive issue here

-- 
You are receiving this mail because:
You are on the CC list for the bug.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: Getting started with ktls

[John Baldwin]

On 3/18/21 8:31 AM, tech-lists wrote:

On Wed, Mar 17, 2021 at 08:39:02PM +, Rick Macklem wrote:


Make sure you've done the following:
ktls_ocf - is loaded
these sysctls are set to 1
kern.ipc.tls.enable
kern.ipc.mb_use_ext_pgs


[on stable/13]

% sysctl kern.ipc.tls.enable kern.ipc.mb_use_ext_pgs
kern.ipc.tls.enable: 1
kern.ipc.mb_use_ext_pgs: 1

% kldstat | grep ktls
71 0x0135300025520 ktls_ocf.ko
%

% sysctl -a | fgrep kern.ipc.tls.stats
kern.ipc.tls.stats.ocf.retries: 0
kern.ipc.tls.stats.ocf.separate_output: 0
kern.ipc.tls.stats.ocf.inplace: 0
kern.ipc.tls.stats.ocf.tls13_gcm_crypts: 0
kern.ipc.tls.stats.ocf.tls12_gcm_crypts: 0
kern.ipc.tls.stats.ocf.tls11_cbc_crypts: 0
kern.ipc.tls.stats.ocf.tls10_cbc_crypts: 0
kern.ipc.tls.stats.switch_failed: 0
kern.ipc.tls.stats.switch_to_sw: 0
kern.ipc.tls.stats.switch_to_ifnet: 0
kern.ipc.tls.stats.failed_crypto: 0
kern.ipc.tls.stats.corrupted_records: 0
kern.ipc.tls.stats.active: 0
kern.ipc.tls.stats.enable_calls: 535
kern.ipc.tls.stats.offload_total: 0
kern.ipc.tls.stats.sw_rx_inqueue: 0
kern.ipc.tls.stats.sw_tx_inqueue: 0
kern.ipc.tls.stats.threads: 4
%


FYI, you can do this a bit more efficiently with just 'sysctl 
kern.ipc.tls.stats'

The 'enable_calls' means that OpenSSL is trying to offload connections,
but those attempts are all failing (offload_total is a count of how many
of those setsockopt() calls succeed).  If you are familiar with dtrace,
you can use some DTrace probes to see why 'ktls_enable_tx' and 'ktls_enable_rx'
are failing, or barring that printf.  For example, does ktls_create_session()
fail, or does ktls_try_sw() fail?  It is probably easiest to debug this using
a userland application using openssl than trying NFS over TLS.

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

Re: On 14-CURRENT: no ports options anymore?

[John Baldwin]

On 3/13/21 12:58 PM, Guido Falsi via freebsd-current wrote:

On 13/03/21 20:17, Hartmann, O. wrote:

Since I moved on to 14-CURRENT, I face a very strange behaviour when trying to 
set
options via "make config" or via poudriere accordingly. I always get "===> 
Options
unchanged" (when options has been already set and I'd expect a dialog menu).
This misbehaviour is throughout ALL 14-CURRENT systems (the oldest is at FreeBSD
14.0-CURRENT #49 main-n245422-cecfaf9bede9: Fri Mar 12 16:08:09 CET 2021 amd64).

I do not see such a behaviour with 13-STABLE, 12-STABLE, 12.2-RELENG.

How to fix this? What happened?


I encountered something similar, some base shared library has changed,
guess this is related with the ncurses changes in base.

If I remember correctly force reinstalling dialog4ports package fixed
it. Make sure you reinstall a freshly rebuilt one.

Most probably anything using ncurses will require rebuild/reinstall.

The cause is dialog4ports failing to start and the system sees no option
changed.

If that's not enough try

# ldd -v /usr/local/bin/dialog4ports

And see if it reports some useful information.


There was an ABI breakage for ncurses that broke 12.x dialog4ports binaries.
The shared library versions for everything that depended on ncurses were bumped
for 13 and 14 after the branch of stable/13.0 (commit 6e1fe6d26ea2).  After
that commit, if you upgraded from 12 to 13 you should have been fine, but if
you had updated before that, the 12.x dialog4ports was still going to fail
as the 12.x version of those libraries were already broken.  I haven't checked
to see if the affected libraries have been added to misc/compat12x.

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

Re: FreeBSD 13.0-RC3 Now Available

[Glen Barber]

On Mon, Mar 22, 2021 at 01:39:06PM +0100, Goran Mekić wrote:
> Hello,
> 
> I see the RC3 in the "Latest News" but not here: 
> https://www.freebsd.org/releases/13.0R/schedule/
> I hope I'm writing to the proper channels/list about this.
> 

Fixed.  Thank you for the report.

Glen



signature.asc
Description: PGP signature

Re: Random freeze with 13.0-RC3

[Stephane D'Alu]

On 3/22/21 1:34 PM, Dries Michiels wrote:
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248659 



Thanks, I'm trying the suggested:
hint.hwpstate_intel.0.disabled="1"

(I've also updated the bios, just in case)




Get Outlook for iOS 

*From:* owner-freebsd-curr...@freebsd.org 
 on behalf of Stephane D'Alu 


*Sent:* Monday, March 22, 2021 1:30:34 PM
*To:* freebsd-current@freebsd.org 
*Subject:* Random freeze with 13.0-RC3
Hi

I upgraded a ThinkPad T490 laptop from 12.2 to 13.0-RC3, on now I have
some random freeze, they seem to occur more when I'm using the laptop
screen instead of an external display (?!).

When it happens, I don't have a kernel panic, and I'm not able to break
to the debugger. Any hint on what should I try to get some debug
information  ?

--
Stephane D'Alu
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current 


To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"



--
Stephane D'Alu
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD 13.0-RC3 Now Available

[Goran Mekić]

Hello,

I see the RC3 in the "Latest News" but not here: 
https://www.freebsd.org/releases/13.0R/schedule/
I hope I'm writing to the proper channels/list about this.

Regards,
meka


signature.asc
Description: PGP signature

Re: Random freeze with 13.0-RC3

[Dries Michiels]

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=248659

Get Outlook for iOS

From: owner-freebsd-curr...@freebsd.org  on 
behalf of Stephane D'Alu 
Sent: Monday, March 22, 2021 1:30:34 PM
To: freebsd-current@freebsd.org 
Subject: Random freeze with 13.0-RC3

Hi

I upgraded a ThinkPad T490 laptop from 12.2 to 13.0-RC3, on now I have
some random freeze, they seem to occur more when I'm using the laptop
screen instead of an external display (?!).

When it happens, I don't have a kernel panic, and I'm not able to break
to the debugger. Any hint on what should I try to get some debug
information  ?

--
Stephane D'Alu
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Random freeze with 13.0-RC3

[Stephane D'Alu]

Hi

I upgraded a ThinkPad T490 laptop from 12.2 to 13.0-RC3, on now I have 
some random freeze, they seem to occur more when I'm using the laptop 
screen instead of an external display (?!).


When it happens, I don't have a kernel panic, and I'm not able to break 
to the debugger. Any hint on what should I try to get some debug 
information  ?


--
Stephane D'Alu
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: FreeBSD 13.0-RC3 Now Available

[Jason Tubnor]

On Sun, 21 Mar 2021 at 03:08, Glen Barber  wrote:

> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> The third RC 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-RC3
>
> 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
>
> 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


Hi,

There are two edge cases where the above update instructions will not work.

1) Due to the VLAN re-write in ifconfig(8), if a user is using a host that
is fully utilising VLAN tagging, the machine will not be available on the
network until the second reboot.  The user will either need IPMI/LOM access
to the console to execute the second 'freebsd-update install' command or
have a way of it being executed and automatically rebooting prior to having
access to the host on the network again.

2) If a user has a 12.2 zpool checkpoint in play and booting via BIOS
legacy mode, the machine will hang at next reboot with 'zio_read error: 5'
'ZFS: i/o error - all block copies unavailable' 'ZFS: can not read
checkpoint data.'  The machine will have to be rebooted with a boot ISO and
the checkpoint will need to be discarded and the system will boot correctly
again (rewind has been unsuccessful).  Please note: This does not appear to
be an issue where hosts use UEFI for booting operating systems or if zpool
checkpoints are destroyed prior to the update process.

Cheers,

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