Comment 2 for bug 2042706

Thank you for taking the time to report this bug and helping to make Ubuntu better.

Bug reporting is about finding & fixing problems thus preventing future users from hitting the same bug.

I suspect a Support site would be more appropriate, eg. https://answers.launchpad.net/ubuntu. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org, or for more support options please look at https://discourse.ubuntu.com/t/community-support/709

If you upgraded to (k)Ubuntu 23.10 and rebooted & were able to login, then the ubuntu-release-upgrader package this bug has been filed against is no longer involved, and from your description, this reads as a support issue more than a bug report. This report can be converted to a question (making it about support) and even returned to bug report if after support it does look like you've discovered a bug, but I suggest seeking support first. I've thus changed status to "incomplete".

IO error would imply a problem that needs exploration; if you can get SysRq responses then its not a crash/freeze of the base system, maybe free of GUI/or display output only. You can explore systemd logs (journalctl) & look for clues (dmesg being an example of a command only showing details of current boot thus won't be helpful if you've rebooted). This though is support related.

I'll change package to 'linux' due to it working with older 6.2 kernel & reported issue only when using newer 6.5 kernel.

Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 2042706

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.