Bug 1202244 - Battery charging even though there is not charger
Summary: Battery charging even though there is not charger
Status: REOPENED
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Basesystem (show other bugs)
Version: Current
Hardware: x86-64 openSUSE Tumbleweed
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: openSUSE Kernel Bugs
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-08 18:48 UTC by Cosmin Tanczel
Modified: 2023-04-28 10:34 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---
tiwai: needinfo? (cosmin.tanczel)


Attachments
battery_applet (55.73 KB, image/png)
2022-08-08 18:48 UTC, Cosmin Tanczel
Details
hwinfo (2.22 MB, text/plain)
2023-04-24 14:09 UTC, Cosmin Tanczel
Details
dmesg (100.29 KB, text/plain)
2023-04-24 14:10 UTC, Cosmin Tanczel
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cosmin Tanczel 2022-08-08 18:48:41 UTC
Created attachment 860675 [details]
battery_applet

I've noticed that my laptop does not enter standby while there is no power source connected, even though it's configured accordingly.

When I hover the mouse over the kde battery applet, it says the battery is charging but there is not enough power, even though there is no charger connected.
Comment 1 Cosmin Tanczel 2022-08-08 19:04:36 UTC
Maybe related to this? Lots of them in dmesg:

Aug 08 22:01:10 kernel: ucsi_acpi USBC000:00: possible UCSI driver bug 2
Aug 08 22:01:10 kernel: ucsi_acpi USBC000:00: con42: failed to get status
Aug 08 22:01:20 kernel: ucsi_acpi USBC000:00: possible UCSI driver bug 2
Aug 08 22:01:20 kernel: ucsi_acpi USBC000:00: con43: failed to get status
Aug 08 22:01:30 kernel: ucsi_acpi USBC000:00: possible UCSI driver bug 2
Aug 08 22:01:30 kernel: ucsi_acpi USBC000:00: con44: failed to get status
Aug 08 22:01:40 kernel: ucsi_acpi USBC000:00: possible UCSI driver bug 2
Aug 08 22:01:40 kernel: ucsi_acpi USBC000:00: con45: failed to get status
Aug 08 22:01:50 kernel: ucsi_acpi USBC000:00: possible UCSI driver bug 2
Comment 2 Takashi Iwai 2022-08-09 13:22:04 UTC
We need more details of your hardware.

Please give the output of hwinfo, as well as the output of dmesg at first.  Please upload to Bugzilla as attachments.
Comment 3 Cosmin Tanczel 2022-11-01 14:51:50 UTC
Not sure what update solved the problem, but seems to be working as expected now.
The only somehow related thing I did was changing from tlp to power-profiles-daemon.
Comment 4 Cosmin Tanczel 2023-04-24 13:56:31 UTC
Did some more investigation on this one and it seems that nano Yubikey presence makes the system think it has a power charger plugged in.

If I remove the Yubikey from the laptop, the system runs fine, otherwise it things a charger is connected but the delivered power is not enough.

Since I configured the power-profile to change to/from Performance and Balanced depending on the charger presence, this affects the battery performance since the system will never switch to/from Performance/Balance while the Yubikey is inserted.
Comment 5 Takashi Iwai 2023-04-24 14:02:50 UTC
Then please provide the information requested in comment 2.
Comment 6 Cosmin Tanczel 2023-04-24 14:09:54 UTC
Created attachment 866537 [details]
hwinfo
Comment 7 Cosmin Tanczel 2023-04-24 14:10:15 UTC
Created attachment 866538 [details]
dmesg
Comment 8 Takashi Iwai 2023-04-24 14:38:09 UTC
Thanks.  Could you try to blacklist ucsi_acpi module?
Comment 9 Takashi Iwai 2023-04-24 14:45:17 UTC
Also, is this a regression from earlier versions?
Comment 10 Cosmin Tanczel 2023-04-27 22:21:46 UTC
Sorry for the late reply... traveling a lot these days.

I blacklisted the module and the issue is gone.
Also, yes, a regression.
Comment 11 Takashi Iwai 2023-04-28 06:28:25 UTC
(In reply to Cosmin Tanczel from comment #10)
> Sorry for the late reply... traveling a lot these days.
> 
> I blacklisted the module and the issue is gone.
> Also, yes, a regression.

OK, and which version did it work?  Some old kernels are found in OBS TW history repo
  http://download.opensuse.org/history/
Also there are a few older kernels in my OBS repos, e.g. home:tiwai:kernel:6.1, home:tiwai:kernel:6.0, etc.
Comment 12 Cosmin Tanczel 2023-04-28 07:58:38 UTC
To be honest I don't remember which version was working, i only remembered that I create a bug report and then later close it because it was working fine. Might be the following release after the I created the first bug report. I will check the dates and will try to compare it, but I'm not sure I will be able to provide a correct answer.
Comment 13 Takashi Iwai 2023-04-28 10:34:31 UTC
As mentioned in the above, some old kernel packages are available, and you can try to install and retest with those to figure out which old kernel works.
It's not necessarily to point out the exact version, but narrowing down the regression range would be helpful.