I'm in trouble, ArchLabs and Manjaro freeze while loading




My laptop froze in screensaver so I had to force reboot it, now I can’t boot into AL at all.
I restored a timeshift backup from a few days ago, nothing, chrooted into it and upgraded…Same problem with the Manjaro install, I can only boot into it with the fallback image that has kernel 5.7 but it takes a few minutes to boot, and this is on a SSD.
With ArchLabs I managed TWICE to get to the login screen/lightdm but after entering user and pass it freezes, no kbd no mouse after.
The big problem is that booting from a live USB it’s also very slow. I even deleted the esp partition, rebuild grub, updated the fstab with the new esp partition, commented out other partitions in fstab…
I am a bit lost here, I’m still a Linux noob that started using it a few months ago.

FSTAB
UUID=9DDE-776A	/boot/efi	vfat	defaults	0	1
UUID=5a0a57e8-5f35-42cd-b66f-b94b3281e9a0	/	ext4	rw,relatime	0	1
#UUID=3ec94841-f8b5-4053-9a1b-05b8b04f12a7	none	swap	defaults	0	0
#UUID=0082c25d-3c09-455a-a512-ecc74b406b35	/home/x/manjaro	ext4	defaults,noatime	0	1
#UUID=36847B93847B53F9	/home/x/diskD	ntfs	defaults,noatime	0	1
#tmpfs	/tmp	tmpfs	defaults,noatime,mode=1777	0	0
log from the chrooted AL:
[root@x /]# journalctl -p 3
-- Journal begins at Tue 2020-12-15 10:57:15 EET, ends at Tue 2020-12-15 21:16:08 EET. --
Dec 15 11:11:30 x kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Dec 15 11:14:09 x kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
Dec 15 11:14:09 x kernel: rcu:         2-...!: (1 GPs behind) idle=942/1/0x4000000000000000 softirq=1548/1549 fqs=0 last_accelerate: a4dc/5e5a dyntic>
Dec 15 11:14:09 x kernel: rcu: rcu_preempt kthread starved for 47482 jiffies! g-219 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=0
Dec 15 11:14:09 x kernel: rcu:         Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
Dec 15 11:14:09 x kernel: rcu: RCU grace-period kthread stack dump:
-- Boot 57087bf6d4884d5faf85a99fdc3317de --
Dec 15 11:15:10 x kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Dec 15 11:17:38 x kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Dec 15 11:17:38 x kernel: rcu:         2-...!: (3 ticks this GP) idle=946/1/0x4000000000000000 softirq=1299/1299 fqs=1 last_accelerate: a40f/52b7 dyn>
Dec 15 11:17:38 x kernel: watchdog: BUG: soft lockup - CPU#2 stuck for 137s! [kworker/u8:0:7]
-- Boot 3d564918016d44e99a82bc312a95bcea --
Dec 15 18:12:27 x kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Dec 15 18:15:07 x kernel: rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
Dec 15 18:15:07 x kernel: rcu:         Tasks blocked on level-0 rcu_node (CPUs 0-3):
Dec 15 18:15:07 x kernel: rcu: All QSes seen, last rcu_preempt kthread activity 0 (4294926222-4294926222), jiffies_till_next_fqs=2, root ->qsmask 0x0
Dec 15 18:15:07 x kernel: blk_update_request: I/O error, dev sdb, sector 1888522120 op 0x0:(READ) flags 0x80700 phys_seg 2 prio class 0
Dec 15 18:15:07 x kernel: blk_update_request: I/O error, dev sdb, sector 1888521984 op 0x0:(READ) flags 0x80700 phys_seg 4 prio class 0
Dec 15 18:15:07 x kernel: blk_update_request: I/O error, dev sdb, sector 1888521728 op 0x0:(READ) flags 0x80700 phys_seg 5 prio class 0
Dec 15 18:15:07 x kernel: blk_update_request: I/O error, dev sdb, sector 1953522688 op 0x0:(READ) flags 0x80700 phys_seg 23 prio class 0
Dec 15 18:15:08 x kernel: kfd kfd: HAINAN  not supported in kfd
Dec 15 18:15:10 x systemd-backlight[1692]: Failed to get backlight or LED device 'backlight:acpi_video1': No such device
Dec 15 18:15:10 x systemd-backlight[1693]: Failed to get backlight or LED device 'backlight:acpi_video0': No such device
Dec 15 18:15:10 x systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video1.
Dec 15 18:15:10 x systemd[1]: Failed to start Load/Save Screen Backlight Brightness of backlight:acpi_video0.
-- Boot 5285474d401c4008afab98689981f3a6 --
Dec 15 20:25:36 x kernel: sp5100-tco sp5100-tco: Watchdog hardware is disabled
Dec 15 20:28:15 x kernel: rcu: INFO: rcu_preempt self-detected stall on CPU
Dec 15 20:28:15 x kernel: rcu:         0-...!: (1 ticks this GP) idle=b9e/1/0x4000000000000000 softirq=1960/1964 fqs=0 last_accelerate: a4da/5f52 dyn>
Dec 15 20:28:15 x kernel: rcu: rcu_preempt kthread starved for 47633 jiffies! g-367 f0x0 RCU_GP_WAIT_FQS(5) ->state=0x402 ->cpu=1
Dec 15 20:28:15 x kernel: rcu:         Unless rcu_preempt kthread gets sufficient CPU time, OOM is now expected behavior.
Dec 15 20:28:15 x kernel: rcu: RCU grace-period kthread stack dump:
Dec 15 20:28:18 x kernel: kfd kfd: HAINAN  not supported in kfd
Dec 15 20:28:22 x systemd-coredump[1734]: Process 416 (Xorg) of user 0 dumped core.

First thing you do is backup all your data and important info.
Second thing to do is test your HDD for errors. It maybe failing. :scream:

1 Like

Yep, happened to me a little while back & as usual I didn t have any backups done.

Edit, had new ssd on hand, saved some time on reinstall.

This is happening on a new SSD that I bought a few months ago. I do have a HDD present in the laptop but the esp and linux partitions are all on the SSD only.

Backup your important data first, then fsck and gsmartcontrol may be helpful.

1 Like

Is possibly a hardware issue rather than a software issue?

Try another OS like Ubuntu or something similar and see if it persists.

Hey is your RAM going bad?

2 Likes

I always thought the problem is with the HDD so I bought a new SSD about 3-4months back and since then I had no other problems(I use the hdd only as storage now). Before I got the new SSD I did an overnight check on the RAM and there were no errors.

Booting from the live USB takes more than 5 minutes but for example today it froze 3-4 times in the booting menu after I pressed F12. I don’t know what the hell is wrong with this system, the laptop is almost 5 years old, thinking to get a new one but I’m still pissed because it was working just fine for me with the new SSD and 8GB of RAM it was enough for my needs.

Is the CPU overclocked?

Nope, except from the new added SSD everything is standard.

Oh, wonder if the ssd s good or was defective.

PROBLEM SOLVED!
So after trying different things without success my next step was to try a BIOS update, remove the HDD, retest SSD and RAM.

I think I swore for 10 minutes continuously :rofl: I wanted to do the BIOS update but the power test was failing and after inspection I realize that the battery was not working at all because was wrongly forced into its slot so I set it in correctly and did the BIOS update, now in 7-10 seconds I’m at the login screen. I can’t be 100% sure if the BIOS update or fixing the battery did the trick, but that doesn’t matter much right now. Everything back to normal! yayyy(paru) :smiley:

2 Likes

Wow, glad that you got it to work @drLobes

1 Like

Thank you, imagine how glad I am :slight_smile: I was seriously thinking on spending some money on a new laptop or desktop, now I can waste those money on food and drinks :laughing:

2 Likes

Well , some spare ssd are always helpfull sometimes,.

Yep, better spent on food as well as some drinks !

1 Like

Glad it’s resolved. It’s always nice to see users coming back to share the solutions. It helps other people in the future.

2 Likes

So I learned that BIOS UPDATES can be VERY important sometimes, that’s something to remember.

2 Likes

Yep, we learn every day right @drLobes

1 Like