[SOLVED] Arch stuck at loading after upgrading

zeeking · 2022-08-02 10:37:56

Hi, I upgraded my system last night to linux-5.18.15 and now It won't boot. It is stuck at the loading screen. I boot with a live usb and arch-root into it and then downgraded the kernel to 5.18.7 and also later to 5.18.3 but I'm still getting the same error. Here's a photo of the screen where it stuck.

https://ibb.co/Ln1Stqr

moderator edit -- replaced oversized image with link.
Pasting pictures and code

SOLVED: upgrading to 5.18.16 fix the issue.

Last edited by zeeking (2022-08-04 07:02:41)

seth · 2022-08-02 12:06:23

I upgraded my system last night to linux-5.18.1

The current kernel is 5.18.15?

From the screenshot it doesn't seem to be the retbleed/spectre bug currently hitting AMD systems.
Try to reboot the stuck system w/ ctrl+alt+del and get a system journal from the install iso, but for the installed system, https://wiki.archlinux.org/title/System … al_to_view (use "-b" or "-b-1" isntead of "-e")
You can use the tip in the 1st link below to upload it.

zeeking · 2022-08-02 12:48:17

Hi, thanks for the quick reply.

Here's the link to journalctl -D /var/log/journal/ -b-1
http://ix.io/46ri

About the kernel version I had "5.18.15" I downgraded it to "5.18.13" and also to "5.18.3" but I was still getting the same error So I updated it again to the "5.18.13". So currently I'm using "5.18.13"

seth · 2022-08-02 13:43:27

The journal is from an old boot on 5.18.13,

Jul 31 23:35:23 zorch systemd-journald[213]: Journal stopped

You need to pick a failing boot and you must *not* hard reboot the stalled system - if ctrl+alt+del doesn't work, try https://wiki.archlinux.org/title/Keyboa … el_(SysRq)
Otherwise the journal cannot be written to disk and is lost.

zeeking · 2022-08-02 14:26:38

Hi, I've been trying to setup the magic system request keys but it's not getting applied. I've created a file name /etc/sysctl.d/99-sysctl.conf with this value

kernel.sysrq = 128

but when I tried to reboot it didn't respond at all. Also when I boot from the usb and then arch-root again the value in /proc/sys/kernel/sysrq was set to 16.
Any idea what I am doing wrong here?

seth · 2022-08-02 14:38:46

First off all, "1", "128" won't suffice (as you need to at least also sync)
Second, rather pass "sysrq_always_enabled=1" to the kernel commandline to ensure the sysrq is active immediately.

zeeking · 2022-08-02 14:42:22

sysrq_always_enabled=1

this value should also be in the config file? (/etc/sysctl.d/99-sysctl.conf)

V1del · 2022-08-02 14:44:31

128 would enable only the reboot sysrq, you generally want to invoke the entire REISUB sequence, for this kind of debugging set it to 1 to make sure you can do anything and then invoke REISUB in that order.

/proc is one of the file system paths that gets carried over from a chroot so you can't make assumptions for your actual system based on a chroot.

It's also possible that your sysrq isn't accepted/you might need to press an additional fn key or so.

Whoops I'm late, however sysrq_always_enabled=1 is a kernel parameter you can pass during boot

Last edited by V1del (2022-08-02 14:45:58)

zeeking · 2022-08-02 16:01:29

Hi,

I've added the kernel parameter to grub. By pressing e on grub menu and adding this line

sysrq_always_enabled=1

after the linux line and before echo "Loading initial ramdisk ...'
I tried multiple things like adding the line after a line break adding it after some spaces adding it 1 space.
But none of them seems to work

seth · 2022-08-02 18:55:41

I tried multiple things like adding the line after a line break adding it after some spaces adding it 1 space.

The line that has (likely still) "quiet" in it is the proper one, add the "sysrq_always_enabled=1" token separated w/ a simple blank (no line breaks or commas)

But none of them seems to work

Can you toogle the numlock or caps lock of the keyboard?

Can you boot when you put "nomodeset" there?

xlightwaverx · 2022-08-02 22:04:08

Yes, also have a system that wont start similar to yours after update. Did a 3 partition rewrite (keeping my /home) and the system built out fine but still stuck in exact same area because the latest files from the repo bork the system and get the same screwy kernel.

Here is a pic: https://ibb.co/yhyJ1F7

Last edited by xlightwaverx (2022-08-02 22:11:56)

loqs · 2022-08-03 00:18:25

@xlightwaverx have you looked at https://bugs.archlinux.org/task/75478

zeeking · 2022-08-03 04:45:39

Can you toogle the numlock or caps lock of the keyboard?

No I cannot toggle numlock or caps lock keys.

But when I plug in a usb it will update the content on the screen. It prints something like "kingston usb plugged in".
So from that we can say that it's not completely frozen but the keyboard still isn't responsive.

Can you boot when you put "nomodeset" there?

It had no effect. still stuck at the same place

Last edited by zeeking (2022-08-03 04:52:29)

seth · 2022-08-03 05:51:09

But when I plug in a usb it will update the content on the screen. It prints something like "kingston usb plugged in".

So the kernel isn't halted at all.
Can you switch the TTY (ctrl+alt+F1,F2,F3,F4,…)?
Do you have an external keyboard that you could plug in?

zeeking · 2022-08-03 06:36:16

Do you have an external keyboard that you could plug in?

Yes I did it but it didn't change anything.

seth · 2022-08-03 06:49:15

seth wrote:

Can you switch the TTY (ctrl+alt+F1,F2,F3,F4,…)?

Can you boot the rescue.target or the mutli-user.target? (2nd link below)

zeeking · 2022-08-03 08:21:28

seth wrote:

seth wrote:
Can you switch the TTY (ctrl+alt+F1,F2,F3,F4,…)?
Can you boot the rescue.target or the mutli-user.target? (2nd link below)

No I cannot switch TTY. Also rescut.target and multi-user.target isn't doing anything too.

I also delete my whole SSD even swap parition and boot partion along with root.
And then I also made a new installation medium by downloading the latest iso. and try to install it. First I was getting some signature error after solving that by

pacman -Syy

pacman -S archlinux-keyring

After that I successfully installed the new inux. But it still stuck at the same screen

seth · 2022-08-03 12:09:54

Boot the rescue.target along "nomodeset" and "debug", "ignore_loglevel", "earlyprintk=vga,keep" and "boot_delay=20" and film the boot process and upload the video somewhere.

zeeking · 2022-08-03 16:27:06

Here's a video

https://www.youtube.com/watch?v=pgdwATiNMso

Scimmia · 2022-08-03 16:34:51

loqs wrote:

@xlightwaverx have you looked at https://bugs.archlinux.org/task/75478

I think you missed this post, zeeking.

zeeking · 2022-08-03 17:11:33

Scimmia wrote:

loqs wrote:
@xlightwaverx have you looked at https://bugs.archlinux.org/task/75478
I think you missed this post, zeeking.

@Scimmia Thank you, yes you were right I missed that post. And the option where putting this kernel parameter spectre_v2=off works.

seth · 2022-08-03 18:50:27

zeeking wrote:

Hi, I upgraded my system last night to linux-5.18.1 and now It won't boot. It is stuck at the loading screen. I boot with a live usb and arch-root into it and then downgraded the kernel to 5.15 and also later to 5.3 but I'm still getting the same error.

The spectre problem wasn't present in any of those kernels…

zeeking later wrote:

About the kernel version I had "5.18.15" I downgraded it to "5.18.13" and also to "5.18.3" but I was still getting the same error So I updated it again to the "5.18.13". So currently I'm using "5.18.13"

Not even if we take "5.18.1" as typo.

Please always remember to mark resolved threads by editing your initial posts subject - so others will know that there's no task left, but maybe a solution to find.
Thanks.

Last edited by seth (2022-08-03 18:52:53)

zeeking · 2022-08-04 06:58:45

I was gonna downgrade my kernel to 5.18.14 for a "permanent" solution as I don't want to type kernel parameter everytime i boot. But then a new patch came 5.18.16 I udpated to it and it solves the issue.

@seth thank you for your support.

dogknowsnx · 2022-08-04 08:33:44

zeeking wrote:

I don't want to type kernel parameter everytime i boot

You don't have to... (for future endeavors to make changes in the kernel command line persistent using grub)

Last edited by dogknowsnx (2022-08-04 08:37:51)

Arch Linux

#1 2022-08-02 10:37:56

[SOLVED] Arch stuck at loading after upgrading

#2 2022-08-02 12:06:23

Re: [SOLVED] Arch stuck at loading after upgrading

#3 2022-08-02 12:48:17

Re: [SOLVED] Arch stuck at loading after upgrading

#4 2022-08-02 13:43:27

Re: [SOLVED] Arch stuck at loading after upgrading

#5 2022-08-02 14:26:38

Re: [SOLVED] Arch stuck at loading after upgrading

#6 2022-08-02 14:38:46

Re: [SOLVED] Arch stuck at loading after upgrading

#7 2022-08-02 14:42:22

Re: [SOLVED] Arch stuck at loading after upgrading

#8 2022-08-02 14:44:31

Re: [SOLVED] Arch stuck at loading after upgrading

#9 2022-08-02 16:01:29

Re: [SOLVED] Arch stuck at loading after upgrading

#10 2022-08-02 18:55:41

Re: [SOLVED] Arch stuck at loading after upgrading

#11 2022-08-02 22:04:08

Re: [SOLVED] Arch stuck at loading after upgrading

#12 2022-08-03 00:18:25

Re: [SOLVED] Arch stuck at loading after upgrading

#13 2022-08-03 04:45:39

Re: [SOLVED] Arch stuck at loading after upgrading

#14 2022-08-03 05:51:09

Re: [SOLVED] Arch stuck at loading after upgrading

#15 2022-08-03 06:36:16

Re: [SOLVED] Arch stuck at loading after upgrading

#16 2022-08-03 06:49:15

Re: [SOLVED] Arch stuck at loading after upgrading

#17 2022-08-03 08:21:28

Re: [SOLVED] Arch stuck at loading after upgrading

#18 2022-08-03 12:09:54

Re: [SOLVED] Arch stuck at loading after upgrading

#19 2022-08-03 16:27:06

Re: [SOLVED] Arch stuck at loading after upgrading

#20 2022-08-03 16:34:51

Re: [SOLVED] Arch stuck at loading after upgrading

#21 2022-08-03 17:11:33

Re: [SOLVED] Arch stuck at loading after upgrading

#22 2022-08-03 18:50:27

Re: [SOLVED] Arch stuck at loading after upgrading

#23 2022-08-04 06:58:45

Re: [SOLVED] Arch stuck at loading after upgrading

#24 2022-08-04 08:33:44

Re: [SOLVED] Arch stuck at loading after upgrading

Board footer