You are not logged in.
Pages: 1
I updated these packages and then rebooted, seeing that there was a new kernel version:
cryptsetup (2.4.3-2 -> 2.5.0-1)
freerdp (2:2.7.0-1 -> 2:2.8.0-1)
linux (5.18.14.arch1-1 -> 5.18.15.arch1-1)
linux-headers (5.18.14.arch1-1 -> 5.18.15.arch1-1)
nvidia (515.57-9 -> 515.57-10)
pass (1.7.4-2 -> 1.7.4-3)
virtualbox-host-modules-arch (6.1.36-4 -> 6.1.36-5)
wine-staging (7.13-1 -> 7.14-1)
When booting up, my system now hangs with this message:
https://i.imgur.com/RQ44PZl.jpeg
The line cropped in the image ends with
max_idle_ns: 440795320847 ns
I have already tried:
reinstalling pacman
downgrading the packages listed above to their previous versions
neither of which changed the behavior.
Logs:
pacman logs: http://0x0.st/oeKx.txt
journalctl from the last successful shotdown: http://0x0.st/oeKI.txt
journalctl does not show any output from these unsuccessful boots.
moderator edit -- replaced oversized image with link.
Pasting pictures and code
Last edited by 2ManyDogs (2022-07-31 16:00:57)
Offline
I have this exact same issue. The issue also persists with linux-zen 5.18.15.zen1-1. The linux-lts 5.15.55-2 kernel still works, suggesting this is not a hardware issue.
Offline
There's an oops above which is (likely) the relevant error, but you've to scroll up a bit to see it.
Otherwise it's not clear from either the screenshot or the journal tail that you posted (don't copy out of the pager) whether the link is actually supposed to be active.
Looks *very* suspiciously like https://bbs.archlinux.org/viewtopic.php?id=278520
Offline
Hey Seth,
Thanks for the reply! Earlier, it looks like this:
https://imgur.com/a/ilwt1Ur
This is as far up as I can go.
Thank you.
Offline
There's an oops above which is (likely) the relevant error, but you've to scroll up a bit to see it.
Shift+PageUp doesn't do anything, and the output doesn't reach the bottom of the screen, nor do I see anything flash by when booting up.
However, I noticed that my keyboard's caps lock and nums lock LEDs don't respond, nor do the backlighting features, leading me to believe that my keyboard isn't getting power.
Offline
The kernel halted (or the keyboard does't work)
@jhm, that's the same portion as in nonoesimposible's original screenshot.
Try to boot "nomodeset" and maybe add some debug variables, https://wiki.archlinux.org/title/Genera … bug_output
Also "boot_delay=50" might help to slow the output down so much that you can see something.
In any event, please post the complete journal of a funtional boot to get an idea whether there's actually supposed to be a sata link on thos ports (or it's a red herring) and generally what kind of HW we're dealing with.
Offline
Thanks! I will trying messing around with some kernel params to see if I can get more useful output. In the meantime, here's the most recent succesful boot: http://0x0.st/oeZR.txt
I see a few "SATA link down"s, so you're probably right that that isn't the cause of the problem.
Offline
Here is the journalctl output from a successful shutdown and startup into the linux-lts kernel (as I mentioned, the lts kernel works while the zen and regular kernels do not).
https://github.com/jack-mueller/journalctl-output.git
https://github.com/jack-mueller/journalctl-output
Offline
Frm the context and because it's generally a good idea:
https://wiki.archlinux.org/title/Microc … ly_loading
Offline
@seth, my microcode should be loaded already. If I regenerate the file using the link you posted, I get the following output:
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-linux-zen
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-zen.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-zen-fallback.img
Found linux image: /boot/vmlinuz-linux-lts
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux-lts.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-lts-fallback.img
Found linux image: /boot/vmlinuz-linux
Found initrd image: /boot/amd-ucode.img /boot/initramfs-linux.img
Found fallback initrd image(s) in /boot: amd-ucode.img initramfs-linux-fallback.img
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Adding boot menu entry for UEFI Firmware Settings ...
done
My sincerest apologies if your message was not intended for me. I hope I'm not hijacking this thread.
Last edited by jhm (2022-07-31 21:44:17)
Offline
@nonoesimposible @jhm bringing this from https://bbs.archlinux.org/viewtopic.php … 6#p2049636
Try with adding "spectre_v2=off" to the kernel parameter list, at least in my case the issue comes from a wrong combination of AMD + no IBPB + retbleed fixes and seems to be already fixed upstream.
Last edited by uka (2022-08-01 01:17:45)
Offline
Edt: that tab was open way too long …
Last edited by seth (2022-08-01 06:24:22)
Offline
Yesterday my system didn't boot anymore after updating the system. I got a lot of sata errors. Then I looked into my bios setup and last bios update was 2018 (shame on me). I updated my bios and the system booted again.
Last edited by Mampfi (2022-08-02 08:30:56)
Offline
@Mampfi, the subject of the thread is misleading, see #7 - the common boot preventing issue right now is AMD sv. spectre.
Offline
Pages: 1