Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: Kernel 5.16 RC (Release Candidate) series

  1. #1
    Join Date
    Oct 2008
    Location
    ExodusHair<Čubura
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Kernel 5.16 RC (Release Candidate) series

    https://www.phoronix.com/vr.php?view=30686
    Still, waiting it eagerly...
    Update₁: Works nicely on several machines. No slowdown that I notice, just as @Doug_S explained...
    Last edited by zika; November 15th, 2021 at 01:25 PM.
    Ignota nulla curatio morbi.

  2. #2
    Join Date
    Feb 2011
    Location
    Coquitlam, B.C. Canada
    Beans
    3,101
    Distro
    Ubuntu Development Release

    Re: Kernel 5.16 RC (Release Candidate) series

    It's out now at kernel.org, but not yet on the Ubuntu mainline PPA.

    I have been running an "almost" 5.16-rc1 for about an hour, and am compiling the actual -rc1 with it now.

    As for the Phoronix article Zika referred to: Highly serialized single threaded workflows have always been a struggle for schedulers and CPU frequency scaling drivers. I just use a performance type governor or force CPU affinity via taskset for that type of workflow.
    Last edited by Doug S; November 14th, 2021 at 11:50 PM.
    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

  3. #3
    Join Date
    Apr 2019
    Beans
    21

    Re: Kernel 5.16 RC (Release Candidate) series

    Good start for this one.


    Daily kernel wasn't booting here for the last week on 3 occasions, mid-way and last third. Not the case for this one. Our ThinkPad keyboard appears to be cooler with this first release.


    Kick the tires!


    Kernel Version: 5.16.0-051600rc1-generic (64-bit)

  4. #4
    Join Date
    Feb 2011
    Location
    Coquitlam, B.C. Canada
    Beans
    3,101
    Distro
    Ubuntu Development Release

    Re: Kernel 5.16 RC (Release Candidate) series

    Kernel 5.16-rc2 is available.

    I never used the Ubuntu kernel configuration last week, for -rc1. I am using the Ubuntu kernel configuration for -rc2 (lots of differences), which I am compiling now.

    This /var/log/syslog entry seems to be new as of -rc1 (didn't notice until -rc2):
    Code:
    Nov 21 16:20:59 s19 udisksd[858]: failed to load module mdraid: libbd_mdraid.so.2: cannot open shared object file: No such file or directory
    Nov 21 16:20:59 s19 udisksd[858]: Failed to load the 'mdraid' libblockdev plugin
    Last edited by Doug S; November 22nd, 2021 at 01:23 AM.
    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

  5. #5
    Join Date
    Feb 2011
    Location
    Coquitlam, B.C. Canada
    Beans
    3,101
    Distro
    Ubuntu Development Release

    Re: Kernel 5.16 RC (Release Candidate) series

    It seems that since 5.16-rc1, I am unable to change CPU frequency scaling drivers. My system just hangs, with the process blocking. It also takes very long to reboot for the various timeouts to occur. I wonder if anyone reading this knows how to shorten the timeouts so that I can debug faster and/or bisect the kernel faster? Extract from "journalctl --since=today", and was after more than 5 minutes:

    Code:
    Nov 25 14:21:18 s19 systemd[1]: session-1.scope: Stopping timed out. Killing.
    Nov 25 14:21:18 s19 systemd[1]: session-1.scope: Killing process 1192 (sudo) with signal SIGKILL.
    Nov 25 14:21:18 s19 systemd[1]: session-1.scope: Killing process 1193 (tee) with signal SIGKILL.
    Nov 25 14:21:18 s19 systemd[1]: session-1.scope: Failed with result 'timeout'.
    Nov 25 14:21:18 s19 systemd[1]: Stopped Session 1 of user doug.
    Nov 25 14:21:18 s19 systemd[1]: Stopping Login Service...
    By the way I was trying to change from the intel_cpufreq CPU frequency scaling driver (A.K.A. intel_pstate driver in passive mode) to the intel_pstate driver (A.K.A. active mode) via:

    Code:
    $ echo active | sudo tee /sys/devices/system/cpu/intel_pstate/status
    The hang occurs in either direction with or without HWP: passive to active; active to passive;

    I am able to launch a "sudo shutdown -r now" command via another terminal.

    EDIT 1: I will try shorter hung task timeout:
    Code:
    doug@s19:/var/log$ grep . /proc/sys/kernel/hung*
    /proc/sys/kernel/hung_task_all_cpu_backtrace:0
    /proc/sys/kernel/hung_task_check_count:4194304
    /proc/sys/kernel/hung_task_check_interval_secs:0
    /proc/sys/kernel/hung_task_panic:0
    /proc/sys/kernel/hung_task_timeout_secs:120
    /proc/sys/kernel/hung_task_warnings:10
    EDIT 2: "sudo reboot --force" seems to work faster.

    EDIT3: Results from kernel bisection:

    Code:
    # first bad commit: [7a89d7eacf8e84f2afb94db5ae9d9f9faa93f01c] powercap/drivers/dtpm: Simplify the dtpm table
    
    commit 7a89d7eacf8e84f2afb94db5ae9d9f9faa93f01c
    Author: Daniel Lezcano <daniel.lezcano@linaro.org>
    Date:   Fri Mar 12 14:04:09 2021 +0100
    
        powercap/drivers/dtpm: Simplify the dtpm table
    
        The dtpm table is an array of pointers, that forces the user of the
        table to define initdata along with the declaration of the table
        entry. It is more efficient to create an array of dtpm structure, so
        the declaration of the table entry can be done by initializing the
        different fields.
    
        Signed-off-by: Daniel Lezcano <daniel.lezcano@linaro.org>
        Reviewed-by: Lukasz Luba <lukasz.luba@arm.com>
        Link: https://lore.kernel.org/r/20210312130411.29833-3-daniel.lezcano@linaro.org
    
    diff --git a/drivers/powercap/dtpm.c b/drivers/powercap/dtpm.c
    index 58433b8ef9a1..8c032398f6ce 100644
    --- a/drivers/powercap/dtpm.c
    +++ b/drivers/powercap/dtpm.c
    @@ -467,7 +467,7 @@ int dtpm_register(const char *name, struct dtpm *dtpm, struct dtpm *parent)
    ...
    Upstream email thread.

    Tested workarounds : Revert the commit; disable dtpm in the kernel configuration (it's still experimental anyhow, and shouldn't actually be enabled by default); Apply the temporary upstream patch, which missed -rc3, but hopefully will make -rc4.
    Last edited by Doug S; November 29th, 2021 at 12:51 AM.
    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

  6. #6
    Join Date
    Feb 2011
    Location
    Coquitlam, B.C. Canada
    Beans
    3,101
    Distro
    Ubuntu Development Release

    Re: Kernel 5.16 RC (Release Candidate) series

    Kernel 5.16-rc3 is available. The Ubuntu mainline builds seem to have failed. I looked quickly at the log file, but didn't isolate the reason.
    I have been running for just a short time so far:

    Code:
    Linux s19 5.16.0-rc3-stock #986 SMP PREEMPT Sun Nov 28 14:52:02 PST 2021 x86_64 x86_64 x86_64 GNU/Linux
    EDIT: Re: Build failure: Never mind. I think I was looking to soon, and compile was still in progress or something. Seems fine.
    Last edited by Doug S; November 29th, 2021 at 01:01 AM.
    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

  7. #7
    Join Date
    Apr 2019
    Beans
    21

    Re: Kernel 5.16 RC (Release Candidate) series

    When <<failed>> is not visible let say an hour after Linus, it means that work is in progress.

    RC-3 is OK, but splash screen is ain't quite anymore.The two previous ones were rock solid, Arch or Focal.

    Stable edition:

    Code:
    Operating System: KDE neon 5.23
    KDE Plasma Version: 5.23.3
    KDE Frameworks Version: 5.88.0
    Qt Version: 5.15.3
    Kernel Version: 5.16.0-051600rc3-generic (64-bit)
    Graphics Platform: Wayland

  8. #8
    Join Date
    Feb 2011
    Location
    Coquitlam, B.C. Canada
    Beans
    3,101
    Distro
    Ubuntu Development Release

    Re: Kernel 5.16 RC (Release Candidate) series

    Quote Originally Posted by Doug S View Post
    It seems that since 5.16-rc1, I am unable to change CPU frequency scaling drivers. My system just hangs, with the process blocking. It also takes very long to reboot for the various timeouts to occur. ...
    ... the temporary upstream patch, which missed -rc3, but hopefully will make -rc4.
    Kernel 5.16-rc4 is available. It has the fix for the inability to change CPU frequency scaling drivers.

    Code:
    $ uname -a
    Linux s19 5.16.0-rc4-stock #990 SMP PREEMPT Sun Dec 5 16:18:21 PST 2021 x86_64 x86_64 x86_64 GNU/Linux
    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

  9. #9
    Join Date
    Oct 2019
    Beans
    16

    Exclamation Re: Kernel 5.16 RC (Release Candidate) series

    Is anyone having issues with AMD GPU and kernel 5.16 RC series? I just installed 5.16 RC 4 and these are the issues I am having (same issues I had with 5.16 RC3):

    1, Boot up took way longer than usual (90 sec vs 30 sec with kernel 5.15.4)
    2, Extreme lag: Right after the reboot, with no application open, mouse lag is extreme.
    3, Hardware sensors monitor for CPU disappeared from taskbar.
    4, No sound output through HDMI.
    5, Redshift stopped working.

    GPU: AMD Radeon R9 290X

    I have gone through `journalctl -b` and `sudo dmesg` but couldn't figure out the root cause myself.

    So, what should I look for? Many thanks in advance.

  10. #10
    Join Date
    Feb 2011
    Location
    Coquitlam, B.C. Canada
    Beans
    3,101
    Distro
    Ubuntu Development Release

    Re: Kernel 5.16 RC (Release Candidate) series

    Quote Originally Posted by jagsdesai View Post
    Is anyone having issues with AMD GPU and kernel 5.16 RC series? I just installed 5.16 RC 4 and these are the issues I am having (same issues I had with 5.16 RC3):

    1, Boot up took way longer than usual (90 sec vs 30 sec with kernel 5.15.4)
    2, Extreme lag: Right after the reboot, with no application open, mouse lag is extreme.
    3, Hardware sensors monitor for CPU disappeared from taskbar.
    4, No sound output through HDMI.
    5, Redshift stopped working.

    GPU: AMD Radeon R9 290X

    I have gone through `journalctl -b` and `sudo dmesg` but couldn't figure out the root cause myself.

    So, what should I look for? Many thanks in advance.
    Does 5.16-RC2 or -RC1 work? Does mainline 5.15 work? I can only think of kernel bisection to isolate the bad commit. I am a server person and don't know about GPU stuff.
    Any follow-up information on your issue would be appreciated. Please have the courtesy to report back.

Page 1 of 3 123 LastLast

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •