https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #66 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Hi Lyn,
To see if the problem is the same as the 1xZ90Q models can you follow the
procedure I described in comment 48? Just the part that refers to
ucsi_acpi_old.ko as this is
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Lyn (905002146...@gmail.com) changed:
What|Removed |Added
CC||905002146...@gmail.com
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #64 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Hi Víctor,
If you are seeing the problem then it should work :)
Can you send me an e-mail with the distro you are using and current kernel
version?
Thanks!
--
You may reply to
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #63 from Víctor (victor.ballester.r...@gmail.com) ---
Thank you very much Diogo. My model is 17ZD90Q, with the D in the middle, which
right now I don't remember exactly what was its meaning (maybe without OS by
default?). Let me know
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #62 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Hi Ralph,
That's great, thank you for your time! So this is confirmed working on the
16Z90Q by both me and you.
It would be great if people with the other affected models chimed
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #59 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Hi Ralph,
Thank you for trying the instructions. You can safely ignore the BTF related
stuff, don't worry about it :). Do you have any newer kernels pre-built that
you can try
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #58 from Ralph Martin (ra...@cs.cf.ac.uk) ---
Hi Diogo
When I try to compile the modules following your instructions, I got
Skipping BTF generation for
/home/ralph/Downloads/linux-6.9.1/drivers/usb/typec/ucsi/ucsi_acpi.ko due to
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #57 from Ralph Martin (ra...@cs.cf.ac.uk) ---
Hi Diogo
I followed your instructions (I am using the current testing kernel 6.7.12),
building the module with the 6.9.1 sources, disabling safe boot, and got
insmod: ERROR: could not
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #56 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Created attachment 306315
--> https://bugzilla.kernel.org/attachment.cgi?id=306315=edit
Fix patch
--
You may reply to this email to add a comment.
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #55 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Created attachment 306314
--> https://bugzilla.kernel.org/attachment.cgi?id=306314=edit
Debug patch
--
You may reply to this email to add a comment.
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #54 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Hello,
The updated instructions are:
- Get the kernel source from kernel.org (v6.9.1) and extract it to a folder.
Download both debug.patch and fix.patch as well.
- Extract
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #53 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Hi Ralph,
I guess the only option is to compile the kernel module from source. I'll place
the patches and instructions here soon.
Thanks,
Diogo
--
You may reply to this email
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #52 from Ralph Martin (ra...@cs.cf.ac.uk) ---
Hi Diogo,
any suggestion how I can proceed beyond the error message I reported when
trying to install your patched module?
Thanks
Ralph
--
You may reply to this email to add a comment.
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #51 from Ralph Martin (ra...@cs.cf.ac.uk) ---
I also tried 6.5 and 6.6 series kernels, with the same outcome.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #50 from Ralph Martin (ra...@cs.cf.ac.uk) ---
OK, I used mokutil to turn off secure boot, but when I tried to insert the old
version of your module I got
insmod: ERROR: could not insert module ucsi_acpi_old.ko: Invalid module format
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #49 from Ralph Martin (ra...@cs.cf.ac.uk) ---
Model 16Z90Q-K.AD78A1
Unfortunately, I get the below trying to unload then insert your (old) module:
rmmod: ERROR: Module ucsi_acpi is not currently loaded
insmod: ERROR: could not
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #48 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Ok, I have submitted two versions of the kernel module: ucsi_acpi_old.ko and
ucsi_acpi_fix.ko. Both of them print debug messages to dmesg.
Important:
These should only fix the
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #47 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Created attachment 306278
--> https://bugzilla.kernel.org/attachment.cgi?id=306278=edit
Fixed ucsi_acpi kernel module with debug prints
--
You may reply to this email to add a
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #46 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Created attachment 306277
--> https://bugzilla.kernel.org/attachment.cgi?id=306277=edit
Stock ucsi_acpi kernel module with debug prints
--
You may reply to this email to add a
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #45 from Ralph Martin (ra...@cs.cf.ac.uk) ---
Hi Diogo,
it would probably be easier for many of us if you could provide the module and
instructions on how to use it...
Thanks.
Ralph
--
You may reply to this email to add a comment.
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #44 from Víctor (victor.ballester.r...@gmail.com) ---
Same for me, but I don't know how I can compile the kernel by myself. I usually
use zen kernel.
--
You may reply to this email to add a comment.
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #43 from PinkFromTheFuture (eduardoxfurt...@gmail.com) ---
Great news! But could you also provide instructions on how to easily do
what you are asking us to do? I would be happy to help, but I don't have
time to tinker with it too
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #42 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Hello,
I think I have a fix for this problem and would like your help in confirming
that the fix does indeed work and to collect all of the affected models. For
that I would
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #41 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Yeah, the fix should come from LG but as you said they are not providing BIOS
updates. What happens in these situations is that we accept that the thing is
buggy and add quirks for
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #40 from kte...@ktecho.com ---
(In reply to Diogo Ivo from comment #39)
> I have been investigating this problem and I have found out that the UCSI
> implementation in these laptops does not conform to the UCSI specification
> in
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #39 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
I have been investigating this problem and I have found out that the UCSI
implementation in these laptops does not conform to the UCSI specification in
multiple locations.
I am
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #38 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
This makes sense, when you mask GPE 0x6E during boot the initialization of the
UCSI driver fails with this timeout and then it is safe for us to unmask the
GPE again since the
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #37 from kte...@ktecho.com ---
I forgot to say that it's an Intel i7-1360p and I'm booting with this:
GRUB_CMDLINE_LINUX_DEFAULT="acpi_mask_gpe=0x6E"
--
You may reply to this email to add a comment.
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=217076
kte...@ktecho.com changed:
What|Removed |Added
CC||kte...@ktecho.com
--- Comment #36
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #35 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Yes, sudo dmesg and then check if there is anything regarding ucsi by grepping;
if you can it would be nice to send the full log to this thread.
--
You may reply to this email to
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #34 from PinkFromTheFuture (eduardoxfurt...@gmail.com) ---
(In reply to Cristian Cocos from comment #33)
> (In reply to PinkFromTheFuture from comment #31)
> > Please keep in mind that our solution consists of first masking it with
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #33 from Cristian Cocos (cri...@ieee.org) ---
(In reply to PinkFromTheFuture from comment #31)
> Please keep in mind that our solution consists of first masking it with the
> grub options, but after the system has booted, we unmask it
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #32 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Ok, so when you do that masking and unmasking can you check if something
regarding an UCSI timeout appears in the dmesg?
--
You may reply to this email to add a comment.
You are
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #31 from PinkFromTheFuture (eduardoxfurt...@gmail.com) ---
I am also going to test the solution with rmmod ucsi_acpi, without the masking
of gpe6E.
Please keep in mind that our solution consists of first masking it with the
grub
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #30 from Cristian Cocos (cri...@ieee.org) ---
I can confirm: prima facie, rmmod ucsi_acpi works fine as a substitute for
masking gpe0x6E. If it is proven over time to have less of an impact on the
system as a whole, I think we have a
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #29 from Cristian Cocos (cri...@ieee.org) ---
(In reply to Diogo Ivo from comment #28)
> This fix does not deal with the ACPI flood (in fact on my system I don't see
> that) and only addresses the high CPU usage.
If I remember
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #28 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
This fix does not deal with the ACPI flood (in fact on my system I don't see
that) and only addresses the high CPU usage.
What is happening, at least on my system and I suspect on
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #27 from Cristian Cocos (cri...@ieee.org) ---
(In reply to Diogo Ivo from comment #26)
> Not really, UCSI is used to communicate the state of the USB-C port to the
> OS and also allows for the user to set the state manually, so
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #26 from Diogo Ivo (diogo@tecnico.ulisboa.pt) ---
Not really, UCSI is used to communicate the state of the USB-C port to the OS
and also allows for the user to set the state manually, so nothing critical.
What happens is that when
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #25 from Ralph Martin (ra...@cs.cf.ac.uk) ---
Hi Diogo
thanks for that suggestion.
rmmod ucsi_acpi does indeed seem to fix the problem.
Are there likely to be any unwanted side effects of doing this?
Ralph
--
You may reply to this
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Diogo Ivo (diogo@tecnico.ulisboa.pt) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #23 from Ralph Martin (ra...@cs.cf.ac.uk) ---
Not for me. I have blacklisted int3403_thermal, and get various threads running
as above, causing the fans to start spinning, with or without masking 6E. Seems
worse when not masking,
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Crypt0Keeper (grandspo...@protonmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #21 from Ralph Martin (ra...@cs.cf.ac.uk) ---
The above showing ACPI masking is not working around the problem is on Debian
testing, with kernel 6.5.13-1
--
You may reply to this email to add a comment.
You are receiving this mail
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #20 from Ralph Martin (ra...@cs.cf.ac.uk) ---
Even when masking with acpi_mask_gpe=0x6E, I am still getting around 5% cpu
usage from each of several kworker tasks.
122 root 20 0 0 0 0 D 6.6 0.0 0:12.72
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #19 from PinkFromTheFuture (eduardoxfurt...@gmail.com) ---
The brightness keys are the only easy to spot issue.
Lots of other issues happen because of the workaround.
My computer definitely behaves weirdly and seems crippled.
To the
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #18 from Víctor (victor.ballester.r...@gmail.com) ---
(In reply to Ralph Martin from comment #16)
> As noted in an earlier messge:
> an observed drawback from [masking these interrupts]] is that it breaks the
> functionality of the
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #17 from Cristian Cocos (cri...@ieee.org) ---
(In reply to Ralph Martin from comment #16)
> As noted in an earlier messge:
> an observed drawback from [masking these interrupts]] is that it breaks the
> functionality of the screen
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #16 from Ralph Martin (ra...@cs.cf.ac.uk) ---
As noted in an earlier messge:
an observed drawback from [masking these interrupts]] is that it breaks the
functionality of the screen brightness buttons
--
You may reply to this email
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #15 from Cristian Cocos (cri...@ieee.org) ---
(In reply to Ralph Martin from comment #14)
> Reneabling the interrupts after boot, even with one minute delay, causes the
> problem to come back for me, on Debian testing, with any recent
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Ralph Martin (ra...@cs.cf.ac.uk) changed:
What|Removed |Added
CC||ra...@cs.cf.ac.uk
---
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #13 from Cherrot (cherrot...@gmail.com) ---
(In reply to PinkFromTheFuture from comment #9)
> Here is my elegant workaround to the problem:
> ```
> [Unit]
> Description=...
> # more documentation:
> #
>
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #12 from Cristian Cocos (cri...@ieee.org) ---
(In reply to PinkFromTheFuture from comment #11)
> Could unloading int3403_thermal cause other issues??
I haven't heard of any issues from anybody about that.
> I didn't quite
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #11 from PinkFromTheFuture (eduardoxfurt...@gmail.com) ---
(In reply to Cristian Cocos from comment #10)
> Same workarounds: upon reboot (1) mask gpe0x6E, and (2) unload the
> int3403_thermal module. That does it for both my LGGrams
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #10 from Cristian Cocos (cri...@ieee.org) ---
(In reply to PinkFromTheFuture from comment #8)
> Doesn't happen on my LG gram from 2021.
I can confirm that on my LGGram 2021.
> 1. I didn't find any reports of this issue for the 2023
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #9 from PinkFromTheFuture (eduardoxfurt...@gmail.com) ---
Here is my elegant workaround to the problem:
```
[Unit]
Description=Fixes many issues with the 2022 LG Grams running linux and sets
charging limit to 80
# save this script to
https://bugzilla.kernel.org/show_bug.cgi?id=217076
PinkFromTheFuture (eduardoxfurt...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=217076
e...@stlo.name changed:
What|Removed |Added
CC||e...@stlo.name
--- Comment #7 from
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #6 from Víctor (victor.ballester.r...@gmail.com) ---
I found a similar but different workaround.
1- Boot into your linux as always (plugged-in or not, I think it doesn't
matter).
2- Immediately after logging into your desktop,
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #5 from Cherrot (cherrot...@gmail.com) ---
... I have a LG Gram 16Z90Q-G.CD78C, which runs Arch Linux with kernel
6.3.3-arch1-1
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching
https://bugzilla.kernel.org/show_bug.cgi?id=217076
--- Comment #4 from Cherrot (cherrot...@gmail.com) ---
(In reply to Pixel from comment #2)
> Rather, I have noticed the following pattern:
>
> 1. Plug In USB-C cable (charging/HDMI)
> 2. Run "top" to verify that 3 kworker threads appear with
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Denis (rokiden3...@gmail.com) changed:
What|Removed |Added
CC||rokiden3...@gmail.com
--
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Víctor (victor.ballester.r...@gmail.com) changed:
What|Removed |Added
CC|
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Pixel (madebypixe...@proton.me) changed:
What|Removed |Added
CC||madebypixe...@proton.me
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Cherrot (cherrot...@gmail.com) changed:
What|Removed |Added
CC||cherrot...@gmail.com
--
https://bugzilla.kernel.org/show_bug.cgi?id=217076
Cristian Cocos (cri...@ieee.org) changed:
What|Removed |Added
CC||cri...@ieee.org
---
66 matches
Mail list logo
