It seems like nobody is paying attention to this since the fix (which
does not work) was released. Maybe we need to post new bug report?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Getting same trace on 5.15.0-18-generic. And besides non-working lid
switch, s2idle is eating way more battery after this trace.
[83424.717757] Call Trace:
[83424.717759]
[83424.717761] ? acpi_os_release_lock+0xe/0x10
[83424.717768] queue_work_on+0x39/0x60
[83424.717772]
I have had this same issue for at least a year. It's still an issue with
kernel 5.11.0. The following lines in the stack trace looks almost
identical:
[292156.350702] ACPI: EC: interrupt blocked
[292180.635315] [ cut here ]
[292180.635318] WARNING: CPU: 1 PID: 297907 at
Hi Alex, just to make sure that I reinstalled one of the kernels that was
supposed to be good (perhaps by accident I reinstalled a bad one), could
you direct me to a good kernel on your ftp site? best, Jim
--
You received this bug notification because you are a member of Kernel
Packages,
Hi Alex,
unfortunately that bug has come back. It just took longer to manifest
itself after booting. It also affects recognition of the power state and
the brightness buttons, which I hadn't noticed before. --Jim
--
You received this bug notification because you are a member of Kernel
damn, wrong again, the patched kernel has just displayed the bug.
no fixed!
--
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/1896482
Title:
acpi event detection crashes
Status in linux
sorry, I retract that. The problem is that ubuntu updated my kernel without my
knowledge,
replacing the correctly patched kernel with the broken one (that both have the
same numbers!)
It would be nice if the patch got incorporated into the distro to save me and
others from this headache!
I
Unfortunately it looks like the bug did not disappear. I have it
starting around 45 minutes after booting in the kernel we thought was
good, 5.4.0-52-generic_5.4.0-52.57. Unless I somehow screwed up and
reinstalled a broken one.
--
You received this bug notification because you are a member of
This bug was fixed in the package linux - 5.4.0-56.62
---
linux (5.4.0-56.62) focal; urgency=medium
* focal/linux: 5.4.0-56.62 -proposed tracker (LP: #1905300)
* CVE-2020-4788
- selftests/powerpc: rfi_flush: disable entry flush if present
- powerpc/64s: flush L1D on
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
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/1896482
Title:
acpi event detection crashes
Status in
This bug is awaiting verification that the kernel in -proposed solves
the problem. Please test the kernel and update this bug with the
results. If the problem is solved, change the tag 'verification-needed-
focal' to 'verification-done-focal'. If the problem still exists, change
the tag
Hi Alex,
I see that I am currently running 5.4.0-48-generic, which I think is the
same version that you originally sent me. But livepatch alters the
running kernel without changing its version number, doesn't it?
That's what makes me still wonder if it is the culprit.
thanks--Jim
On Tue, 3
@jim,
You can check your kernel version by "uname -r".
I also built a rebased one:
https://people.canonical.com/~alexhung/LP1896482/Ubuntu-5.4.0-52.57/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Alex,
my problem came back. Is it possible that livepatch has replaced my
working kernel with the broken one again? --Jim
On Thu, 24 Sep 2020, Alex Hung wrote:
> A test kernel with target patches ready for SRU is available @
> https://people.canonical.com/~alexhung/LP1896482/fixes/
>
>
** Changed in: linux (Ubuntu Focal)
Status: In Progress => Fix Committed
--
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/1896482
Title:
acpi event detection crashes
Status in
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Alex Hung (alexhung)
** Changed in: linux (Ubuntu)
Assignee: Alex Hung (alexhung) => (unassigned)
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
--
You received this bug notification because you are a member of
** Description changed:
+ = SRU Justification =
+
+ [Impact]
+
+ The bug causes the EC driver to fail and ACPI events are no longer
+ handled by Linux kernel, i.e lid close no longer triggers suspends.
+
+ [Fix]
+
+ Upstream commit 03e9a0e05739cf reworks ec_install_handlers to avoid
+
last one you sent with the commit? It is working.
On Fri, 25 Sep 2020, Alex Hung wrote:
> @jcline-physics,
>
> can you give kernel in #24 a try?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
> Title:
>
@jcline-physics,
can you give kernel in #24 a try?
--
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/1896482
Title:
acpi event detection crashes
Status in linux package in Ubuntu:
In
thanks a lot Alex
On Thu, 24 Sep 2020, Alex Hung wrote:
> A test kernel with target patches ready for SRU is available @
> https://people.canonical.com/~alexhung/LP1896482/fixes/
>
> The patch in #23 requires three precedent patches. See SRU.log file for
> more details.
>
> Note it is rebased
A test kernel with target patches ready for SRU is available @
https://people.canonical.com/~alexhung/LP1896482/fixes/
The patch in #23 requires three precedent patches. See SRU.log file for
more details.
Note it is rebased Ubuntu-5.4.0-48.52 now.
--
You received this bug notification because
Bisecting points to the below commit. Ubuntu-5.4.0-47.51 requires more
than it without conflicting. Let me figure out which ones are also
required for SRU and I will build another kernel (and final one
hopefully) for testing
commit 03e9a0e05739cf872fee494b06c75c0469704a21
Author: Rafael J.
that one seems to be fine.
On Thu, 24 Sep 2020, Alex Hung wrote:
> Next one:
> https://people.canonical.com/~alexhung/LP1896482/937d1d5d752513b8/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
> Title:
>
Next one:
https://people.canonical.com/~alexhung/LP1896482/937d1d5d752513b8/
--
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/1896482
Title:
acpi event detection crashes
Status in linux
that one also seems to be good.
On Wed, 23 Sep 2020, Alex Hung wrote:
> Next one is @
> https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1896482
>
>
Next one is @
https://people.canonical.com/~alexhung/LP1896482/c271d18b523bb58e/
--
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/1896482
Title:
acpi event detection crashes
Status in
this one seems to be good
On Wed, 23 Sep 2020, Alex Hung wrote:
> @jcline-physics,
>
> Thanks for testing. The next is available @
> https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/
>
> ** Changed in: linux (Ubuntu)
> Status: Confirmed => In Progress
>
> ** Changed in:
@jcline-physics,
Thanks for testing. The next is available @
https://people.canonical.com/~alexhung/LP1896482/31be3e3551d09f20/
** Changed in: linux (Ubuntu)
Status: Confirmed => In Progress
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
--
You
okay, so that kernel has the problem again.
On Wed, 23 Sep 2020, Alex Hung wrote:
> Thanks mfo for helping out how to disable secure boot and install kernel
>
> I uploaded a test kernel @
> https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/
>
> There are 17 patches so it
ok, that's not such a big problem. I'll keep all the versions' deb
packages in separate directories so I can easily switch back to one of
them if needed.
On Wed, 23 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hi Jim,
>
> You can install on top of the previous ones without removing them
Hi Jim,
You can install on top of the previous ones without removing them first.
The versioning of the test packages used the same 5.4.0-47 number,
so unfortunately they will keep overwriting themselves (including
the original/non-test 5.4.0-47 kernel.)
I'd think this is why you only see two
Hi, if I install this on top of the previous one using dpkg -i * will that
be sufficient? Or do I have to remove the previous packages first?
It seems like my grub configuration is somehow set to keeping only two
kernels in the boot list. It would be nice if it would keep them all so I
don't
Thanks mfo for helping out how to disable secure boot and install kernel
I uploaded a test kernel @
https://people.canonical.com/~alexhung/LP1896482/0a8c35897f60b202/
There are 17 patches so it requires 4 times to identify the fixing
kernel patch. The included patches are listed in
ok, I can do that
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hey Jim,
>
> That's very good news!
>
> I believe Alex should send you more test kernels,
> with different sets of patches included/removed,
> so to bisect/identify which specific patch(es)
> resolve the problem.
>
> If
Hey Jim,
That's very good news!
I believe Alex should send you more test kernels,
with different sets of patches included/removed,
so to bisect/identify which specific patch(es)
resolve the problem.
If you could help with testing that as well,
that would be great, so a smaller patch(set)
can
Looks like it is working! At any rate the old kernel started having the
problem much sooner while this one is still fine. Thanks very much for
your help with this!
> --
> You received this bug notification because you are subscribed to the bug
> report.
>
thanks, I fixed that and will start testing
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> It looks like you have secure boot enabled.
> Unfortunately test kernels are unsigned and thus require it to be disabled in
> your BIOS/EFI menu.
>
> --
> You received this bug notification
It looks like you have secure boot enabled.
Unfortunately test kernels are unsigned and thus require it to be disabled in
your BIOS/EFI menu.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Hi Maricio, I did as you suggested, but cannot boot,
error:/boot/vmlinuz-5.4.0-47-generic has invalid signature
loading initial ramdisk
error: you need to load the kernel first
--Jim
On Tue, 22 Sep 2020, Mauricio Faria de Oliveira wrote:
> Hi Jim,
>
> This is a conflict between the (un)signed
Hi Jim,
This is a conflict between the (un)signed kernel packages; but it's easy
to solve:
Please remove the linux-image-5.4.0-47-generic package and try
installing again; e.g.,
$ sudo apt purge linux-image-5.4.0-47-generic # confirm to remove the running
kernel if asked.
$ sudo dpkg -i *.deb
Hi Alex, thanks for that. I got this error message while installing,
dpkg: regarding
linux-image-unsigned-5.4.0-47-generic_5.4.0-47.51_amd64.deb contntaining
linux-image-unsigned-5.4.0-47-generic:
linux-image-unsigned-5.4.0-47-generic conflicts with
linux-image-5.4.0-47-genereric
The warning messages occurred between "ACPI: EC: interrupt blocked" and
"ACPI: EC: interrupt unblocked". Let's try to apply all (17) mainline
patches to ACPI EC to Ubuntu-5.4.0-47.51.
If this solves the problems we can then bi-select to identify which
patches are the solution and then backport to
43 matches
Mail list logo