On 7/23/21 3:01 AM, Greg KH wrote:
On Thu, Jul 22, 2021 at 05:10:02PM -0400, PGNet Dev wrote:
My servers run Fedora 34, with latest kernels.
Updating to any of minimally- or un- patched 5.12.17 or 5.13.4 hangs/fails, as follows.
Can you use 'git bisect' to find the offending change?
thanks,
greg k-h
unfortunately, not simply.
These are rpm installs, from unpatched builds,
updating to any of minimally- or un- patched,
Fedora (5.12.17-300.fc34.x86_64) 34 (Thirty Four)
https://koji.fedoraproject.org/koji/buildinfo?buildID=1780670
Fedora (5.13.4-200.fc34.x86_64) 34 (Thirty Four)
https://koji.fedoraproject.org/koji/buildinfo?buildID=1782334
Fedora (5.13.4-250.vanilla.1.fc34.x86_64) 34 (Thirty Four)
https://fedoraproject.org/wiki/Kernel_Vanilla_Repositories
https://repos.fedorapeople.org/repos/thl/kernel-vanilla-stable/fedora-34/x86_64/
https://fedorapeople.org/cgit/thl/public_git/kernel.git/tree/?h=kernel-5.13.3-250.vanilla.1.fc34
available at stable release versions, not my own source builds.
and, of course, this issue appears only on this J1900/Celeron hardware *production* server.
Is there a specific set of kernel rd/systemd/etc debug logging flags that would shine more light on the problem?
