You are not logged in.

#1 2020-05-28 16:11:46

Eliot_Alderson
Member
Registered: 2020-05-28
Posts: 2

Lenovo Yoga 14s freezes for unknow reason

system information:
    OS: Arch Linux x86_64
    Host: 82A8 Yoga 14sARE 2020
    Kernel: 5.6.14-zen1-1-zen
    DE: Plasma
    WM: KWin
    CPU: AMD Ryzen 7 4800U with Radeon Graphics
    GPU: AMD ATI 03:00.0 Renoir

Graphics driver version is xf86-video-amdgpu (19.1.0-2), mesa, lib32-mesa.

I installed Arch Linux on my new laptop a few days ago. I followed the Arch Wiki of VirtualBox, install virtualbox 6.1.8-2、virtualbox-ext-oracle 6.1.8-1、virtualbox-guest-iso 6.1.8-1、virtualbox-host-dkms 6.1.8-2.

And then host and guest all freezes after I use the VirtualBox a while, at first, i think it's the VirtualBox problem, so i followed [Host freezes on virtual machine start] CN version, tried Disabling hardware virtualisation (VT-x/AMD-V) and add nosmap to kernel parameters, still got random freezes.

Here is the log about the above part: dmesg_0526.log journalctl_0527.log

Today I removed nosmap kernel parameters && tried change mesa to mesa-git (20.2.0_devel.124331.01ce7887bf0-1), lib32-mesa-git (20.2.0_devel.124331.01ce7887bf0-1), still got freeze, but the main reason why I got freezes this time is that my telegram got stuck. neutral  hmm

I am new about use Linux on laptop, very confused.

Here is the log about today: dmesg_0528.log journalctl_0528.log

What should i do?

I am sorry for poor English, If you need more info, pls tell me. smile

Last edited by Eliot_Alderson (2020-05-28 16:24:29)

Offline

#2 2020-05-28 17:53:23

Head_on_a_Stick
Member
From: London
Registered: 2014-02-20
Posts: 7,732
Website

Re: Lenovo Yoga 14s freezes for unknow reason

Eliot_Alderson wrote:

    CPU: AMD Ryzen 7 4800U with Radeon Graphics
    GPU: AMD ATI 03:00.0 Renoir

Very nice smile

But also very new. Perhaps try the newer kernel (5.6.15) & amd-ucode (20200519.8ba6fa6-1) packages from [testing] to see if your problem has been fixed yet.

If that doesn't help it may be best to pursue this with the kernel developers, Ryzen 4000 & Renoir support was only added recently and your logs show several kernel stack traces.

Offline

#3 2020-05-29 07:08:17

amonakov
Member
Registered: 2012-09-30
Posts: 32

Re: Lenovo Yoga 14s freezes for unknow reason

The first thing kernel developers will ask is to reproduce the issue with untainted kernel, i.e. without Virtualbox:

[  +0.006159] vboxdrv: loading out-of-tree module taints kernel.
[  +0.000162] vboxdrv: module verification failed: signature and/or required key missing - tainting kernel

Also, this:

[  +0.016656] vboxdrv: TSC mode is Invariant, tentative frequency 1796675766 Hz

may hint at a (possibly unrelated) Virtualbox bug, as Linux TSC sanity checks failed and kernel is using HPET for timekeeping.

The kernel is showing such unholy warnings with scheduling and interrupt delivery that I think it indicates a problem for AMD or laptop manufacturers, not the kernel. Similar issues, including unexplained hangs, were seen on previous Ryzen generations, and in some cases they were fixed with firmware update.

Can you show what dmesg | grep -iE 'tsc|clock' shows after a cold boot (not after a reboot)?

Are hangs reproducible after a cold boot as well?

Offline

#4 2020-05-29 08:08:14

Eliot_Alderson
Member
Registered: 2020-05-28
Posts: 2

Re: Lenovo Yoga 14s freezes for unknow reason

Head_on_a_Stick wrote:

Perhaps try the newer kernel (5.6.15) & amd-ucode (20200519.8ba6fa6-1) packages from [testing] to see if your problem has been fixed yet.

[UTC+8] Today's morning i try to do what does Head_on_a_Stick say, but noticed the kernel (5.6.15) & amd-ucode (20200519.8ba6fa6-1) already release to stable, so i just did pacman -Syu to update them. after this i tried to use the laptop for about 4 hours, no random freezes got. It's seems the problem already gone? (I'm not quite sure.)

amonakov wrote:

Can you show what dmesg | grep -iE 'tsc|clock' shows after a cold boot (not after a reboot)? Are hangs reproducible after a cold boot as well?

Here the dmesg | grep -iE 'tsc|clock' shows after a cold boot (after today I have updated kernel & amd-ucode):

[    0.000000] tsc: Fast TSC calibration using PIT                                              
[    0.000000] tsc: Detected 1796.592 MHz processor                                             
[    0.045479] clocksource: refined-jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1910969940391419 ns                                                                          
[    0.099765] clocksource: hpet: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 133484873504 ns                                                                                         
[    0.202791] clocksource: tsc-early: mask: 0xffffffffffffffff max_cycles: 0x19e59628fb4, max_idle_ns: 440795217416 ns
[    0.524285] clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 1911260446275000 ns
[    0.558920] acpi PNP0A08:00: _OSC: OS supports [ExtendedConfig ASPM ClockPM Segments MSI HPX-Type3]
[    0.571781] PTP clock support registered
[    0.577865] clocksource: Switched to clocksource tsc-early
[    0.594607] clocksource: acpi_pm: mask: 0xffffff max_cycles: 0xffffff, max_idle_ns: 2085701024 ns
[    1.069660] sched_clock: Marking stable (973233773, 96392757)->(1086396179, -16769649)
[    1.082362] rtc_cmos 00:01: setting system clock to 2020-05-29T07:44:15 UTC (1590738255)
[    1.532394] clocksource: timekeeping watchdog on CPU1: Marking clocksource 'tsc-early' as unstable because the skew is too large:
[    1.532396] clocksource:                       'hpet' wd_now: f77578 wd_last: 8b0385 mask: ffffffff
[    1.532397] clocksource:                       'tsc-early' cs_now: 43e1b01f2 cs_last: 3e708c778 mask: ffffffffffffffff
[    1.532401] tsc: Marking TSC unstable due to clocksource watchdog
[    1.532409] TSC found unstable after boot, most likely due to broken BIOS. Use 'tsc=unstable'.
[    1.532410] sched_clock: Marking unstable (1436015763, 96392757)<-(1549178179, -16769649)
[    1.532643] clocksource: Switched to clocksource hpet
[    1.836412] vboxdrv: TSC mode is Invariant, tentative frequency 1796654440 Hz

after use the laptop for about 4 hours, the hangs reproducible seems gone (I'm not quite sure).

If need more info, pls tell me. smile

Offline

#5 2020-05-29 09:01:22

amonakov
Member
Registered: 2012-09-30
Posts: 32

Re: Lenovo Yoga 14s freezes for unknow reason

Thanks. Hope the update did the trick. The watchdog failure matches my experience with TSC check failures on a 4500U Ryzen. I have reached out to AMD about the issue. Hopefully it will be fixed too soon enough.

Offline

Board footer

Powered by FluxBB