** Tags added: focal kernel-bug
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953261
Title:
kernel >= 5.13 BUG: kernel NULL pointer dereference
To manage notifications about this bug go to:
@sttzr :
I'm the Debian package maintainer, I don't maintain the package for
Ubuntu, nor do I have Ubuntu upload rights.
I watch the bug reports for Ubuntu packages and fix them "upstream"
(Debian is Ubuntu's upstream), but that's it.
If you want to learn more about the relationship between
@linrunner: Thanks for the explanation that tlp will mostly work without
acpi-call-dkms and completely without it in the future! Also your
warning hint from the TLP doc might help some people here:
"Warning: On Ubuntu 21.10 and 20.04.4 the acpi-call-dkms packages in the
official repositories are
Hi,
uninstalling TLP is unnecessary, it is not broken either. The best
workaround is to uninstall acpi-call-dkms or use version 1.2.2 from the
TLP PPA.
The charge thresholds will continue to work without acpi-call, because
they are built in since kernel 4.19. You only lose tlp recalibrate. But
Meanwhile, tlp is partially broken because of this on 20.04 with HWE
kernel.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953261
Title:
kernel >= 5.13 BUG: kernel NULL pointer dereference
To
I am seeing in the Arch UEFI documentation:
UEFI Runtime Variables Support (efivarfs filesystem -
/sys/firmware/efi/efivars). This option is important as this is required
to manipulate UEFI runtime variables using tools like
/usr/bin/efibootmgr. The configuration option below has been added
Can someone let us know if we're going to get a backport to 20.04? If
so, I'll just go without tlp until then. Otherwise I'll install the
newer acpi-call-dkms by hand.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I've just been hit with this on a Thinkpad W530 running Ubuntu 20.04.4.
After freaking out, I did succeed in finding my way to a reboot by
entering and saving the BIOS. Then I immediately removed tlp - which is
clearly not a long-term solution. As far as I can tell nothing else is
using
Examining things in detail:
Impish Indri (21.10) and Focal Fossa (21.04) have both been upgraded
from kernel 5.11 to 5.13 but this package has only been updated for
Jammy Jellyfish (22.04). [1] shows acpi-call for Jammy at 1.2.2-1 while
the other two remain at 1.1.0-6 and 1.1.0-5 respectively.
Is this not going to be backported?
It appears to have only been applied to Jammy Jellyfish (22.04) but I'm
still experiencing this problem, with null pointer dereferences and
everything, on 20.04(.4) after moving to the new 5.13 kernel from 5.11,
presumably after a HWE update.
--
You received
Hello,
Thanks for taking the time to update this package with the new upstream.
I'm also being bitten by this bug. (T430 thinkpad)
Is there an ETA for when this will land in the regular update channels?
Thanks,
-Matt
--
You received this bug notification because you are a member of Ubuntu
(I'm on 20.04, btw)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953261
Title:
kernel >= 5.13 BUG: kernel NULL pointer dereference
To manage notifications about this bug go to:
Weird, 5.13 is a fairly recent version, it should have the failsafe.
About the contents of /sys/firmware/efi/efivars, I wouldn't know what to
do with it, I'm just the package maintainer, I didn't write the kernel
module itself, and I'm not a specialist of NVRAM.
I really hope that the store will
Thanks! Unfortunally not possible to switch to legacy boot like this.
Also I think I've read somewhere that efivars can only be accessed from
a uefi boot session.
No I have not set something like "efi_no_storage_paranoia". It was a
standard ubuntu 20.04 installation with tlp installed from the
Sadly, if you can't access BIOS, I have no other idea. My "plan" was to
try to enter the BIOS somehow, then disable UEFI boot (to boot plain old
BIOS compatibility mode) and boot Linux or a live Linux USB key, and see
if you can clear the dump files from there (which may or may not be
possible if
Thanks for your reply raph!
Yes I tried pressing F1 repeatedly after pressing the power button. I also
tried using an external USB keyboard. Also tried F12 for boot menu. But the
error seems to block startup before it checks if F1/F12 are pressed. As
described earlier, the first two/three times
Did you try to press F1 **before** the message appears ?
I'm really surprised that Lenovo didn't foresee any method to access
BIOS when the NVRAM is full.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I could imagine that this error potentially also affects other Thinkpad
models. Of course if they have a larger NVRAM it will take longer for
the dump files to fill it up. Maybe even weeks if only a few dump files
are generated with each restart. At least some newer models like the X1
Yoga seem to
Sadly no. When turning the laptop on, there is the info screen with bios
version etc. visible for two seconds. Then the Error Message appears:
„Error: The non-volatile variable storage is about full. Press F1 to
enter Setup.“ At first it was possible to enter BIOS setup and then exit
the setup to
Bricked how ?
Can you still access BIOS setup and/or boot on a USB key ?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953261
Title:
kernel >= 5.13 BUG: kernel NULL pointer dereference
To manage
Me and my brothers each own a Thinkpad x131e and were running Ubuntu 20.04 with
tlp very smoothly. Until with the recent kernel update 5.13 three weeks ago
each of us encountered the error `Error: The Non-Volatile Variable Storage is
About Full` on boot. At first the error could be ignored by
Can it be backported to the latest LTS?
Using `tlp` to control the laptop charge trigger a reboot every time.
This is quite critical I believe.
Thanks
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This bug was fixed in the package acpi-call - 1.2.2-1
---
acpi-call (1.2.2-1) unstable; urgency=medium
* [e4c61df] Remove '-guest' from Vcs-* URLs
* [022a8aa] Use nix-community repository as new upstream (Closes: #989384)
* [0776fac] New upstream version 1.2.2 (LP: #1953261,
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: acpi-call (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1953261
Title:
** Bug watch added: tlp (upstream) #599
https://github.com/linrunner/TLP/issues/599
** Project changed: tlp-upstream => tlp (Ubuntu)
** No longer affects: tlp (Ubuntu)
** Description changed:
As described here https://blog.monosoul.dev/2021/10/16/ubuntu-21-10-and-
- acpi-call-dkms-bug/
25 matches
Mail list logo
