The generic Ubuntu kernel has dynamic preempt enabled. This allows the
preemption model to be changed at runtime between: none, voluntary (the
default), and full.
It would be super interesting to test what impact this has for latency
sensitive workloads, and whether this can help you make the
My Ubuntu 20.04 which uses the HWE kernel has recently updated to the
following kernel version:
$ uname -a
Linux len 5.8.0-55-generic #62~20.04.1-Ubuntu SMP Wed Jun 2 08:55:04 UTC 2021
x86_64 x86_64 x86_64 GNU/Linux
I can confirm that the Fn Lock LED is working properly now. It looks
like the
A code fix has been identified, and I confirm that it works on my Lenovo
E595 when I build my own kernel with the fix included. See the Kernel
bugzilla for details: https://bugzilla.kernel.org/show_bug.cgi?id=207841
What are the next steps to getting this upstreamed and/or included in
the Ubuntu
kaihengfeng, either it was fixed in Linux kernel v5.8 (like you say), or
it was fixed by the Lenovo BIOS update.
Either way, I haven't seen the hang on boot issue in a long while now.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
Since my last comment my Lenovo E595 laptop has changed configuration
slightly.
1. The BIOS has updated to v1.19.
2. I installed the "linux-image-generic-hwe-20.04-edge" package, which
as I write is an early release of the upcoming HWE kernel from 20.04.2
(kernel v5.8).
With these updates in
Kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=207841
** Bug watch added: Linux Kernel Bug Tracker #207841
https://bugzilla.kernel.org/show_bug.cgi?id=207841
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
So, what are the next steps here (if any)?
To summarize, the regular Ubuntu 20.04 GA kernel (v5.4) works reliably
for me so long as "nomodeset" is provided as a kernel boot parameter.
Without this parameter that kernel and others I was invited to test all
hang occasionally on boot.
Is there
I today experienced a hang using the v5.7 kernel above without the
"nomodeset" kernel parameter.
The hang occurred before the LUKS password prompt. I will attach a
screenshot of the message displayed at the time of the hang.
I will revert to the v5.4 GA kernel and reapply the "nomodeset"
Hang
** Attachment added: "Screenshot of hang from 2020-06-07. (v5.7 without
nomodeset)"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+attachment/5381387/+files/IMG_3217.JPG
--
You received this bug notification because you are a member of Kernel
Packages, which is
I've installed the kernel from that link, and removed the "nomodeset"
kernel parameter. The system has booted fine and Wayland is working
again.
I'll let you know if I see a hang on boot.
---
v5.7 (3d77e6a8804abcc0504c904bd6e5cdf3a5cf8162)
So far so good with me using the standard 5.4 kernel and the nomodeset
parameter.
I wonder if the freezes during usage that viperomega experiences might
be unrelated to the hang on boot issue (that we both saw without
nomodeset).
--
You received this bug notification because you are a member of
Here is some more information that I collected.
I tried toggling fn-lock while at different stages of booting.
* In the grub menu, the light does not toggle.
* If I choose to boot windows, then while windows is booting, the light does
not toggle. (ie, during the "swirling dots" screen.)
* Once
( I also posted this to Ask Ubuntu:
https://askubuntu.com/questions/1243284/how-do-i-get-the-lenovo-fn-lock-
light-to-work-under-ubuntu )
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Public bug reported:
I have a Lenovo E595 running Ubuntu 20.04. The "Fn Lock" feature on the
keyboard works in terms of how it modifies subsequent presses of the
F1-F12 keys, but the little light on the Esc key doesn't show the
current state.
Example:
1. I press F5 a few times, and the screen
@viperomega It's interesting that you mention freezes at times other
than bootup. I've never experienced that problem on this laptop. Only
the hang on boot issue.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I've switched back to the 5.4 kernel and have enabled the 'nomodeset'
parameter. The laptop has booted fine. I'll keep using it like this
and let you know if I see another hang on boot.
I've noticed that Wayland is no longer an option on the login screen. I
presume this is an expected
Which kernel would you like me to test with that parameter? The drm-tip
one, or the regular Ubuntu 20.04 one (v5.4)?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877889
Title:
** Attachment added: "Screenshot of hang from 2020-05-24."
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889/+attachment/5376152/+files/hang.jpg
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1877889
Title:
Intermittent hangs on boot Ubuntu 20.04 on Lenovo E595
Status in linux package in Ubuntu:
Confirmed
Bug description:
I'm afraid to report that I experienced a hang on boot today, using the
drm-tip kernel ("5.7.0-994.202005192206"). This time the hang occurred
before the LUKS password prompt to unlock the root filesystem. There
was a message printed to the screen, which I will attach shortly.
I was able to
The drm-tip directories for the most recent days have missing or failed
amd64 builds, so I had to go back a few days and install the drm-tip
kernel from: https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-
tip/2020-05-20/
With secure boot disabled I have rebooted approximately 15 times and
have
Oh, I see! I had no idea that error was related to secure boot.
Thanks! I'll try that later and get back to you.
The drm-tip download page (
https://kernel.ubuntu.com/~kernel-ppa/mainline/drm-tip/current/ ) links to the
following wiki pages, neither of which mention secure boot in any way.
*
The regular kernel has since updated to 5.4.0-31.35, but I can confirm
that the hang on boot still occurs.
I haven't heard back in a few days on whether there is something else
you would like me to try. Like I said previously the drm-tip kernel
didn't boot at all for me (invalid signature
Thanks for the reply,
I followed the link provided in that bug ( https://kernel.ubuntu.com
/~kernel-ppa/mainline/drm-tip/current/ ) and couldn't find
"5.7.0-994.20200511220" there.
The version there currently is "5.7.0-994.202005132209". I assumed this
is just a few days newer than the one you
I confirm that the hang on boot issue still occurs after the reinstall
of Ubuntu 20.04.
Same kernel as before:
$ cat /proc/version
Linux version 5.4.0-29-generic (buildd@lgw01-amd64-035) (gcc version 9.3.0
(Ubuntu 9.3.0-10ubuntu2)) #33-Ubuntu SMP Wed Apr 29 14:32:27 UTC 2020
$ cat
Since logging this bug entry, I suffered a corrupted root filesystem. I
don't know for sure that the hanging on boot followed by me forcing
reboots was the cause, but I guess it won't have helped. :/ I guess my
SysRq S+U+S+B didn't work quite as well as I'd thought.
I was unable to recover the
While I suspect I'm seeing the same problem, I've submitted my own bug
report too incase it provides useful information or is somehow
different: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877889
--
You received this bug notification because you are a member of Kernel
Packages, which
Public bug reported:
Hello,
I see occasional hangs on boot. The hangs occur after entering the LUKS
decryption password for the root filesystem, and before the login screen is
displayed. The "/boot" filesystem is not encrypted, so the initramfs is
loading fine etc. The hangs are
I see the same problem on my Lenovo E595 (AMD Ryzen 5 3500U). I am
running 20.04 with "5.4.0-29-generic" kernel.
I have not yet tried the "nomodeset" workaround that has been suggested
so cannot confirm that yet.
--
You received this bug notification because you are a member of Kernel
29 matches
Mail list logo
