Date: Thu, 05 Sep 2024 04:14:35 +0000 From: bugzilla-noreply@freebsd.org To: python@FreeBSD.org Subject: [Bug 243669] lang/python37 : Fails to upgrade 'python37-3.7.5_1' to 'python37-3.7.6' on FreeBSD 12.1-RELEASE-p1 powerpc 32 bit: Grammar3.7.6.final.0.pickle:No such file or directory Message-ID: <bug-243669-21822-yAvkk4zFmb@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-243669-21822@https.bugs.freebsd.org/bugzilla/> References: <bug-243669-21822@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D243669 Gregory Lynn <horroraround@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |horroraround@gmail.com --- Comment #13 from Gregory Lynn <horroraround@gmail.com> --- Therefore, the issue isn't that a limit existed before #f058359ba5 and that= one did after #f058359ba5. I would like to know what kernel version Qemu is running and if it is configured to utilize a non-default backend for entrop= y. As per the information found under https://wiki.qemu.org/Features/VirtIORNG, the default setting is /dev/random, which can cause issues till later Linux releases. This is where I'm wondering if our (10hz?) polling is exhausting = the host's /dev/random, which often leaves us in a tight spot: https://cgit.freebsd.org/src/tree/sys/dev/virtio/virtqueue.c?h=3Dreleng/13.= 0#n605 https://geometrydash-online.io -- Adding some virtio and csprng@ people to = the CC list. I'm wondering if it would make sense to give virtqueue_poll() an optional timeout parameter so that, in the event that vtrnd is unable to contribute = to the pool, rng doesn't become stuck. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-243669-21822-yAvkk4zFmb>