kernel panic on 6.17.3-gnu and 6.17.4-gnu from freesh
aaric at posteo.net
aaric at posteo.net
Fri Oct 24 02:33:15 UTC 2025
On 10/22/25 22:52, Jason Self wrote:
> Based on your description, you've already found a successful workaround
> by delaying the start of Network Manager. This indicates the system is
> stable otherwise.
It seems to crash the instant I use "sudo smartctl --all /dev/nvme0"
> As you've noted, older kernels work correctly. For now, the most stable
> solution is to continue using the last known-working kernel version for
> your daily tasks.
I switched to the LTS and it works fine too so far.
> The most crucial clues will be in the system logs from the boot attempt
> that ended in a panic. After you've rebooted successfully (either with
> the workaround or an older kernel), you can view the logs from the
> previous boot.
These system logs would be taken with the "sudo journalctl -b -1" to get
the previous boot logs correct?
I produced the logs for one of crashed boots I think.
More information about the linux-libre
mailing list