Date: Wed, 20 Jan 2021 13:58:01 +0000 From: Santiago Martinez <sm@codenetworks.net> To: freebsd-current@freebsd.org Subject: Re: Waiting for bufdaemon Message-ID: <d55fc185-186b-742d-eaf6-1f2a13232817@codenetworks.net> In-Reply-To: <YAg1jCpPQd2K/zfE@kib.kiev.ua> References: <YAO9/cxnbGv5u3Bg@kib.kiev.ua> <adb9d42c-d855-1edf-a57c-9b16aad481b7@gwdg.de> <YAQINMoEi7ysBSD5@kib.kiev.ua> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <YAgDhJ9/YX29kH2a@kib.kiev.ua> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <YAgjOYdVG%2BN4lU0n@kib.kiev.ua> <d25a7608-9e61-0ece-9500-d4a80e79068e@gwdg.de> <YAgsO3AoB5PFhzDq@kib.kiev.ua> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> <YAg1jCpPQd2K/zfE@kib.kiev.ua>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --bjkR96Rl37SlEUWAAWUHSJZAsqDaYUsWd Content-Type: multipart/mixed; boundary="WGDCUzb3ODMOA9cVG0hXe2jsea8gxbbv1"; protected-headers="v1" From: Santiago Martinez <sm@codenetworks.net> To: freebsd-current@freebsd.org Message-ID: <d55fc185-186b-742d-eaf6-1f2a13232817@codenetworks.net> Subject: Re: Waiting for bufdaemon References: <YAO9/cxnbGv5u3Bg@kib.kiev.ua> <adb9d42c-d855-1edf-a57c-9b16aad481b7@gwdg.de> <YAQINMoEi7ysBSD5@kib.kiev.ua> <1d675d77-8bdb-c285-ffa2-28330b839734@alvermark.net> <YAgDhJ9/YX29kH2a@kib.kiev.ua> <60599f75-7206-9269-ac0c-934f8f31ae26@gwdg.de> <YAgjOYdVG+N4lU0n@kib.kiev.ua> <d25a7608-9e61-0ece-9500-d4a80e79068e@gwdg.de> <YAgsO3AoB5PFhzDq@kib.kiev.ua> <3885bc2a-3924-cc3f-6cad-99dc6f803b0d@gwdg.de> <YAg1jCpPQd2K/zfE@kib.kiev.ua> In-Reply-To: <YAg1jCpPQd2K/zfE@kib.kiev.ua> --WGDCUzb3ODMOA9cVG0hXe2jsea8gxbbv1 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Content-Language: en-US Hi Everyone, i have exactly the same behavior as Rainer described. "After a high system load, several programs only react very slowly (e.g. Firefox)......" I will try with the patch and see if it also clear this on my machine (AMD R7). Santiago On 1/20/21 1:52 PM, Konstantin Belousov wrote: > On Wed, Jan 20, 2021 at 02:35:59PM +0100, Rainer Hurling wrote: >> Am 20.01.21 um 14:12 schrieb Konstantin Belousov: >>> On Wed, Jan 20, 2021 at 01:56:57PM +0100, Rainer Hurling wrote: >>>> Am 20.01.21 um 13:34 schrieb Konstantin Belousov: >>>>> On Wed, Jan 20, 2021 at 01:17:51PM +0100, Rainer Hurling wrote: >>>>>> Am 20.01.21 um 11:18 schrieb Konstantin Belousov: >>>>>>> On Wed, Jan 20, 2021 at 11:02:21AM +0100, Jakob Alvermark wrote: >>>>>>>> This patch hides the problem for me. The system seems to work be= tter now. >>>>>>>> >>>>>>>> No waiting on reboot, and the webcam works better. >>>>>>> I am curious what do you mean by the above reference to webcam. >>>>>>> Can you explain it with more details, even if only the impression= s? >>>>>> I should mention, that beside the already discussed timing problem= with >>>>>> bufdaemon, I also have problems with several apps: >>>>>> >>>>>> >>>>>> After a high system load, several programs only react very slowly = (e.g. >>>>>> Firefox). Several dockable apps from WindowMaker, but also e.g. co= nky do >>>>>> not update their windows anymore, they freeze. After some time, Fi= refox >>>>>> updates its screen content only after switching back from another = window ... >>>>>> >>>>>> When such frozen programs are killed and restarted, they run norma= lly >>>>>> again for an indefinite time before they freeze again. >>>>>> >>>>>> These symptoms completely disappeared, after I patched the Ryzen b= ox as >>>>>> suggested on 01/17: >>>>> Do you load latest microcode update from devcpu-data? >>>> Yes, sysutils/devcpu-data is installed and the following to lines ar= e in >>>> /boot/loader.conf >>>> >>>> cpu_microcode_load=3D"YES" >>>> cpu_microcode_name=3D"/boot/firmware/intel-ucode.bin" >>>> >>>> But isn't this just for Intel (i387 and amd64), not AMD cpus? >>> You need microcode_update_enable=3D"YES" in /etc/rc.conf for late mic= rocode >>> update. >>> >>> I think that early boot update should work on AMD, bit for this you n= eed to >>> select and put right blob. It is enough to load late to answer my qu= estion. >> Ah, ok. Thanks for clarification. I also put cpu_microcode_load=3D"YES= " in >> /etc/rc.conf for a late update. >> >> Should I try again without your patch of sys/x86/tsc.c, whether the >> problem still occurs? > Yes. > >> >> And for the early boot update, how do I know about the right blob? > I am not aware of the mechanism. My best suggestion is that you match > the blob against your CPU family/model id manually. > >>>>> It might be not enough, which means that additionally latest BIOS n= eeds >>>>> to be flushed. >>>>> >>>> I am running latest Firmware F31 on a "Gigabyte\ Aorus\ X570\ Elite"= >>>> mainboard. > _______________________________________________ > freebsd-current@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-current > To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.o= rg" --WGDCUzb3ODMOA9cVG0hXe2jsea8gxbbv1-- --bjkR96Rl37SlEUWAAWUHSJZAsqDaYUsWd Content-Type: application/pgp-signature; name="OpenPGP_signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="OpenPGP_signature" -----BEGIN PGP SIGNATURE----- wsF5BAABCAAjFiEEk06QWJzNAs9NTrFjWBFqYkyC55EFAmAINukFAwAAAAAACgkQWBFqYkyC55F0 CQ/9GJQm0YagKdb+Vfrp/Fhb6iQ3e/ZDM6Qgvg3UwvcrOq4XBib+aHekMkTNz+N5oiuaaJBA1tUJ W2m9l3s9oMTdgwn6SyDUrhVRL3bP/luhwegCk2AapDeqU6GpWi1a6xB7NI9GFCnfjY1WsQZw01O3 11qWG0jppJJ0ZFi30YTJLeMMp8Wf7yQU/njMzDMNrNLG9Ways+QPhX99gcP7nlpMfYc5qomUeBcH HSznvraamzHJODx+e3itnlckA+uBdgRcT7aToZ2tjF+jYgyu/R7R3rU6xGxlS1ouhxGJbG3bFXw7 XLdxXXxtWM1hFlMJM80GZdCyftM9elwTw2vf+9WlOGnHtFNKlGnkjM7jjUKpvrRqxFX46izD2KIs lt+W85UIhjAgH2xuU6arULSu7OpXMW9Eykxeob0GR5YzwBdd3gJ86MEkRdqYe27sePfciSj/j4zD 8P8DHqWKn7Xx9QBdRUaQxk7gBSEFucKRofPTO6nLi6ArAcqvQYrZTlVt5svFCwXEwEOXFtTyGU5h tariH8G9RYODgjkjo+t9L+IFi6epgQfgEHVmf9W0quB5q2ociOkQWMG4s/hhdLnv7FB0NvJ1kBGL IXEFmKXb2vUmh5M20xNoG5PGIPpATxOyiGXn5AZTrErSUfo+9qbs9tNA6qz9Fia7Y59VwMHXUTGO vwM= =FHEO -----END PGP SIGNATURE----- --bjkR96Rl37SlEUWAAWUHSJZAsqDaYUsWd--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d55fc185-186b-742d-eaf6-1f2a13232817>