On 6/7/25 21:13, George N. White III wrote:
On Sat, Jul 5, 2025 at 10:07 PM mailto:fed...@eyal.emu.id.au>> wrote:
Today I did the usual 'dnf update' on a VM system.
As part of the update I received kernel-6.15.4-200.fc42.x86_64
"VM System" is too vague: which VM?
QEMU/KVM.
Both the h
On Sat, Jul 5, 2025 at 10:07 PM wrote:
> Today I did the usual 'dnf update' on a VM system.
> As part of the update I received kernel-6.15.4-200.fc42.x86_64
>
"VM System" is too vague: which VM?
>
> However, after the upgrades were done, the last console message was
> >>> Running post-t
On Sun, 2025-07-06 at 08:49 +0100, Barry wrote:
>
> > On 6 Jul 2025, at 02:07, fed...@eyal.emu.id.au wrote:
> >
> > However, after the upgrades were done, the last console message was
> >>>> Running post-transaction scriptlet:
> > kernel-core-0:6.15.4-200.fc42.x86_64
> > after which the syst
> On 6 Jul 2025, at 02:07, fed...@eyal.emu.id.au wrote:
>
> However, after the upgrades were done, the last console message was
>>>> Running post-transaction scriptlet:
> kernel-core-0:6.15.4-200.fc42.x86_64
> after which the system was hard locked (about 45m...).
No one else has reported
Today I did the usual 'dnf update' on a VM system.
As part of the update I received kernel-6.15.4-200.fc42.x86_64
However, after the upgrades were done, the last console message was
>>> Running post-transaction scriptlet:
kernel-core-0:6.15.4-200.fc42.x86_64
after which the system was ha
