You are not logged in.

#1 2020-06-24 14:16:50

zu0107
Member
From: South Korea
Registered: 2017-05-02
Posts: 4
Website

Samsung Notebook 9 Pro - CPU soft lockup

Hello, all!

I've been using Arch Linux on my Samsung Notebook 9 Pro (about a year ago), switched back to Windows (for school), and now I am attempting to install Arch Linux on this machine once again.

This laptop has:

  • CPU: Intel i7-7500U

  • Graphics: Radeon RX 540

  • RAM: 16GB

I am booting from a microSD card (I know, it is a shitty idea) formatted in F2FS, sharing a single ESP with Windows.

But, even after successful installation, the system refuses to boot, and even if succeeds, the system is almost unusable due to this "watchdog: BUG: soft lockup - CPU#n stuck for 23s!" situation.
The CPU number varies every time, but usually #0 or #1. Once it starts showing that message, it is almost impossible to execute any command.
Even booting from the latest archiso shows the same symptoms, so I had to excavate an older version of the Live ISO from Arch Linux Archive (201905, I believe.)

Initially I was not able to boot in the first place as systemd times out looking for the ESP, and eventually becomes unresponsive (without any emergency shell). The only way out is force shutoff.
I tried disabling Kernel modesetting by setting "nomodeset" kernel parameter. It did allow me through the booting process, but once the login screen shows up, the soft lockup comes back.
Installing i915 and AMDGPU driver and adding respective mkinitcpio hooks does not help. (Gets me through the boot process, though.)

I somewhat suspect that this is a kernel issue, as it worked under previous versions of Arch Linux (it was around 4.18), and even under the old archiso (this one is around 5.0.4).

This is the backtrace retrieved from journalctl.

# journalctl -xb

. . .
Jun 25 03:20:04 RangHo-LAPTOP kernel: watchdog: BUG: soft lockup - CPU#0 stuck for 22s! [kworker/u8:3:164]
Jun 25 03:20:04 RangHo-LAPTOP kernel: Modules linked in: pcc_cpufreq(-) mc crc16 rtsx_usb_ms drm_kms_helper memstick intel_xhci_usb_role_switch intel_lpss_pci roles ucsi_acpi intel_lpss idma64 typec_ucsi intel_gtt processor_thermal_device intel_ish_ipc tpm_crb syscopyarea sysfillrect intel_pch_thermal intel_rapl_common sysimgblt fb_sys_fops intel_ishtp typec intel_soc_dts_iosf i2c_hid battery tpm_tis intel_vbtn tpm_tis_core soc_button_array int3400_thermal tpm evdev sparse_keymap int3403_thermal int340x_thermal_zone acpi_thermal_rel rng_core mac_hid wmi acpi_tad ac nls_iso8859_1 nls_cp437 vfat fat drm agpgart ip_tables x_tables f2fs hid_multitouch hid_generic usbhid hid mmc_block rtsx_usb_sdmmc mmc_core rtsx_usb sd_mod serio_raw atkbd libps2 ahci libahci libata crc32_pclmul scsi_mod xhci_pci xhci_hcd i8042 serio
Jun 25 03:20:04 RangHo-LAPTOP kernel: CPU: 0 PID: 164 Comm: kworker/u8:3 Tainted: G             L    5.4.48-1-lts #1
Jun 25 03:20:04 RangHo-LAPTOP kernel: Hardware name: SAMSUNG ELECTRONICS CO., LTD. 940X5M/NP940X5M-X01US, BIOS P04AGF.048.170731.PS 07/31/2017
Jun 25 03:20:04 RangHo-LAPTOP kernel: Workqueue: efi_rts_wq efi_call_rts
Jun 25 03:20:04 RangHo-LAPTOP kernel: RIP: 0010:0xfffffffefa9b0302
Jun 25 03:20:04 RangHo-LAPTOP kernel: Code: 2f 33 c0 f0 0f b1 3d 31 12 00 00 75 05 ec 3c 77 75 3a 8b 05 28 12 00 00 44 3b d8 74 2f 33 c0 f0 0f b1 3d 15 12 00 00 75 f4 ec <3c> 77 74 ef eb 49 33 c0 f0 0f b1 3d 02 12 00 00 75 05 ec 3c 77 75
Jun 25 03:20:04 RangHo-LAPTOP kernel: RSP: 0018:ffff998f003afc50 EFLAGS: 00000246 ORIG_RAX: ffffffffffffff13
Jun 25 03:20:04 RangHo-LAPTOP kernel: RAX: 0000000000000077 RBX: ffff998f003afdff RCX: ffff998f003afca8
Jun 25 03:20:04 RangHo-LAPTOP kernel: RDX: 00000000000000b3 RSI: 0000000000000001 RDI: 0000000000000000
Jun 25 03:20:04 RangHo-LAPTOP kernel: RBP: ffff915121206000 R08: 0000000000000000 R09: 0000000000000000
Jun 25 03:20:04 RangHo-LAPTOP kernel: R10: 0000000000000000 R11: 0000000000000000 R12: ffff998f004c7e8c
Jun 25 03:20:04 RangHo-LAPTOP kernel: R13: 0000000000000001 R14: ffff915120c3bf9c R15: 0000000000000246
Jun 25 03:20:04 RangHo-LAPTOP kernel: FS:  0000000000000000(0000) GS:ffff915126a00000(0000) knlGS:0000000000000000
Jun 25 03:20:04 RangHo-LAPTOP kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jun 25 03:20:04 RangHo-LAPTOP kernel: CR2: 00007f347ef91421 CR3: 0000000424d7a002 CR4: 00000000003606f0
Jun 25 03:20:04 RangHo-LAPTOP kernel: Call Trace:
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? cpumask_next_wrap+0x24/0x70
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? sched_clock+0x5/0x10
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? sched_clock_cpu+0xc/0xb0
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? __update_load_avg_cfs_rq+0x212/0x2f0
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? __switch_to_asm+0x34/0x70
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? __switch_to_asm+0x34/0x70
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? __switch_to_asm+0x34/0x70
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? __switch_to_asm+0x40/0x70
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? __switch_to_asm+0x40/0x70
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? efi_call+0x58/0x90
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? __switch_to_asm+0x40/0x70
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? efi_call_rts+0x171/0x8e0
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? process_one_work+0x1ea/0x3a0
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? worker_thread+0x50/0x410
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? process_one_work+0x3a0/0x3a0
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? kthread+0x117/0x130
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? __kthread_bind_mask+0x60/0x60
Jun 25 03:20:04 RangHo-LAPTOP kernel:  ? ret_from_fork+0x35/0x40
. . .

And here is the full output of journalctl -xb.

Many thanks in advance!

P.S. I just tried enabling CSM support (because of that "efi_call_rts" in stacktrace), but the problem still occurs. I still need Windows for some Visual Studio works, so I would like to avoid disabling EFI entirely...

Offline

#2 2020-06-26 09:31:28

C0n57an71n
Member
Registered: 2020-06-25
Posts: 1

Re: Samsung Notebook 9 Pro - CPU soft lockup

I have almost a similar problem, but mine occurs when I am trying to install i686 image for a 32 system. I have no issue until i run the command  "pacstrap -i /mnt base". It runs ok until job 11/11 "Rebuilding certificates stores". It stays like this doing nothing. Pressing short the power button will make the things "run again", but shortly after, will show an output similar with what you have.

Offline

#3 2020-06-26 10:04:05

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 9,995

Re: Samsung Notebook 9 Pro - CPU soft lockup

Make sure you install and properly apply your microcode updates there have been quite a few changes here you should have, and the BIOS version is quite old so it might lack something a newer kernel expects to have.

Offline

#4 2020-06-27 06:18:00

zu0107
Member
From: South Korea
Registered: 2017-05-02
Posts: 4
Website

Re: Samsung Notebook 9 Pro - CPU soft lockup

Thank you for your reply.

V1del wrote:

Make sure you install and properly apply your microcode updates

When I install the bootloader I did fetch intel-ucode package and added the initrd image to systemd-boot argument. Correct me if this is not the right way to do so.

V1del wrote:

the BIOS version is quite old so it might lack something a newer kernel expects to have.

Unfortunately this is the latest revision of BIOS firmware provided by Samsung. This model is relatively new (came out in 2018) so I don't think this system is missing crucial features as well.

I posted similar thread on r/archlinux forum, and got some insights there.

Additional things I tried are:

  • changing kernel.watchdog_thresh to 10 minutes to see if this system call ever finishes,

  • blacklisting efi_rts_wq and efi_call_rts kernel module via bootloader arguments,

  • blacklisting gsmi kernel module as per this post,

  • setting acpi=off kernel parameter.

None of them worked, and produced the same journalctl log and/or system freeze. Dropping myself into a rescue terminal was not successful too. (I did get a shell, but those soft lockup made executing command virtually impossible.)

I did find the source code responsible for those efi_call_rts procedure, but I am not knowledgeable enough to try debugging the code. My next plan is manually building previous LTS kernel and see if that works.

Offline

Board footer

Powered by FluxBB