linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-usb@vger.kernel.org
Subject: [Bug 217511] HP Pavilion x2 12-b020nr - Charging over USB-C not working
Date: Wed, 21 Aug 2024 02:18:11 +0000	[thread overview]
Message-ID: <bug-217511-208809-B7hYMQYGAr@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-217511-208809@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=217511

gabriel barros (gabrielbarros+k@gmail.com) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |gabrielbarros+k@gmail.com

--- Comment #4 from gabriel barros (gabrielbarros+k@gmail.com) ---
I had this happen to me today, also with an Elitebook, but different model.

Computer bat>95%, plugged to a charger that provides AT LEAST 40W. It charges
normally. I never see the Unknown event_id messages.

Computer bat>95%, plugged to a charger that provides UP TO 40W. Computer do
charge, but at random times:
- `acpi` will alternate between "Battery 0: Not charging, 95%" and "Battery 0:
Discharging, 95%", never "charging"
- KDE or any other battery watcher besides `acpi` command, would just show
"charging" at all times, no variation.
- virtualbox guest (win10enterprise ltsc) would sound the "charger unplugged"
immediately followed by "charger plugged" notification sound.
- kernel would log "kernel: hp_wmi: Unknown event_id - 131073 - 0x0" (never see
the 0x1 event, not once)
- the kernel messages and the windows virtualbox guest sounds were in perfect
sync.

In both cases my battery is indeed charging (the percentage always go up no
matter what of those things are happening). Can't say for speed/healthy to the
battery.

My guess is that is a low power charging mode event that the linux driver
doesn't know. And I don't know how much raw information the virtualbox drivers
do forward, but that old version (2021?) of windows' drivers was clearly seeing
it as a power cable disconnect.

Linux 6.10.4-arch2-1 #1 SMP PREEMPT_DYNAMIC Sun, 11 Aug 2024 16:19:06 +0000
x86_64 GNU/Linux

relevant parts of lshw:

   capabilities: smbios-3.4.0 dmi-3.4.0 smp vsyscall32

     *-firmware
          description: BIOS
          vendor: HP
          physical id: 10
          version: U82 Ver. 01.07.00
          date: 10/05/2023
          size: 64KiB
          capacity: 32MiB
          capabilities: pci pcmcia upgrade shadowing cdboot bootselect edd
int5printscreen int9keyboard int14serial int17printer acpi
biosbootspecification netboot uefi

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2024-08-21  2:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-30 19:39 [Bug 217511] New: HP Pavilion x2 - Charging over USB-C not working bugzilla-daemon
2023-05-30 20:34 ` [Bug 217511] " bugzilla-daemon
2023-06-02  5:42 ` [Bug 217511] HP Pavilion x2 12-b020nr " bugzilla-daemon
2024-01-25  0:09 ` bugzilla-daemon
2024-08-21  2:18 ` bugzilla-daemon [this message]
2024-08-21 18:54 ` bugzilla-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=bug-217511-208809-B7hYMQYGAr@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-usb@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).