[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
This bug was fixed in the package linux - 4.18.0-17.18
---
linux (4.18.0-17.18) cosmic; urgency=medium
* linux: 4.18.0-17.18 -proposed tracker (LP: #1819624)
* Packaging resync (LP: #1786013)
- [Packaging] resync getabis
- [Packaging] update helper scripts
* C++ demangling support missing from perf (LP: #1396654)
- [Packaging] fix a mistype
* arm-smmu-v3 arm-smmu-v3.3.auto: CMD_SYNC timeout (LP: #1818162)
- iommu/arm-smmu-v3: Fix unexpected CMD_SYNC timeout
* Crash in nvme_irq_check() when using threaded interrupts (LP: #1818747)
- nvme-pci: fix out of bounds access in nvme_cqe_pending
* CVE-2019-9003
- ipmi: fix use-after-free of user->release_barrier.rda
* CVE-2019-9162
- netfilter: nf_nat_snmp_basic: add missing length checks in ASN.1 cbs
* CVE-2019-9213
- mm: enforce min addr even if capable() in expand_downwards()
* CVE-2019-3460
- Bluetooth: Check L2CAP option sizes returned from l2cap_get_conf_opt
* tun/tap: unable to manage carrier state from userland (LP: #1806392)
- tun: implement carrier change
* CVE-2019-8980
- exec: Fix mem leak in kernel_read_file
* [Packaging] Allow overlay of config annotations (LP: #1752072)
- [Packaging] config-check: Add an include directive
* amdgpu with mst WARNING on blanking (LP: #1814308)
- drm/amd/display: Fix MST dp_blank REG_WAIT timeout
* CVE-2019-7308
- bpf: move {prev_,}insn_idx into verifier env
- bpf: move tmp variable into ax register in interpreter
- bpf: enable access to ax register also from verifier rewrite
- bpf: restrict map value pointer arithmetic for unprivileged
- bpf: restrict stack pointer arithmetic for unprivileged
- bpf: restrict unknown scalars of mixed signed bounds for unprivileged
- bpf: fix check_map_access smin_value test when pointer contains offset
- bpf: prevent out of bounds speculation on pointer arithmetic
- bpf: fix sanitation of alu op with pointer / scalar type from different
paths
- bpf: add various test cases to test_verifier
- bpf: add various test cases to selftests
* CVE-2017-5753
- bpf: fix inner map masking to prevent oob under speculation
* Use memblock quirk instead of delayed allocation for GICv3 LPI tables
(LP: #1816425)
- efi/arm: Revert "Defer persistent reservations until after paging_init()"
- arm64, mm, efi: Account for GICv3 LPI tables in static memblock reserve
table
* efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted (LP: #1814982)
- efi/arm/arm64: Allow SetVirtualAddressMap() to be omitted
* Update ENA driver to version 2.0.3K (LP: #1816806)
- net: ena: update driver version from 2.0.2 to 2.0.3
- net: ena: fix race between link up and device initalization
- net: ena: fix crash during failed resume from hibernation
* Silent "Unknown key" message when pressing keyboard backlight hotkey
(LP: #1817063)
- platform/x86: dell-wmi: Ignore new keyboard backlight change event
* CVE-2018-19824
- ALSA: usb-audio: Fix UAF decrement if card has no live interfaces in
card.c
* CVE-2019-3459
- Bluetooth: Verify that l2cap_get_conf_opt provides large enough buffer
* CONFIG_TEST_BPF is disabled (LP: #1813955)
- [Config]: Reenable TEST_BPF
* installer does not support iSCSI iBFT (LP: #1817321)
- d-i: add iscsi_ibft to scsi-modules
* CVE-2019-7222
- KVM: x86: work around leak of uninitialized stack contents (CVE-2019-7222)
* CVE-2019-7221
- KVM: nVMX: unconditionally cancel preemption timer in free_nested
(CVE-2019-7221)
* CVE-2019-6974
- kvm: fix kvm_ioctl_create_device() reference counting (CVE-2019-6974)
* hns3 nic speed may not match optical port speed (LP: #1817969)
- net: hns3: Config NIC port speed same as that of optical module
* [Hyper-V] srcu: Lock srcu_data structure in srcu_gp_start() (LP: #1802021)
- srcu: Lock srcu_data structure in srcu_gp_start()
* libsas disks can have non-unique by-path names (LP: #1817784)
- scsi: libsas: Fix rphy phy_identifier for PHYs with end devices attached
* Bluetooth not working (Intel CyclonePeak) (LP: #1817518)
- Bluetooth: btusb: Add support for Intel bluetooth device 8087:0029
* CVE-2019-8912
- net: crypto set sk to NULL when af_alg_release.
- net: socket: set sock->sk to NULL after calling proto_ops::release()
* 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable (LP: #1812099)
- platform/x86: thinkpad_acpi: Fix multi-battery bug
* [ALSA] [PATCH] System76 darp5 and oryp5 fixups (LP: #1815831)
- ALSA: hda/realtek - Headset microphone support for System76 darp5
- ALSA: hda/realtek - Headset microphone and internal speaker support for
System76 oryp5
* CVE-2019-8956
- sctp: walk the list of asoc safely
* Constant noise in the headphone on Lenovo X1 machines (LP: #1817263)
- ALSA: hda/realtek: Disable PC beep in passthrough on
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
tags:changed: verification-done-cosmic -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
Work well. Thank you. ** Tags removed: verification-needed-cosmic ** Tags added: verification-done-cosmic -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
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- cosmic' to 'verification-done-cosmic'. If the problem still exists, change the tag 'verification-needed-cosmic' to 'verification-failed- cosmic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-cosmic -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
** Changed in: linux (Ubuntu Cosmic) Status: New => 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: Fix Committed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
** Changed in: linux (Ubuntu Cosmic) Importance: Undecided => Medium -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: New Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
** Also affects: linux (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Fix Released Status in linux source package in Cosmic: New Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
Works flawless. Thank you very much. -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Confirmed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
Please test this kernel: https://people.canonical.com/~khfeng/lp1812099/ -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Confirmed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
> Is commit 6640ee6289b9974334e36d8283fc07f37f3b235d also needed? ps. I guess all the 3 changes by Jouke Witteveen would be needed and that's beyond the scope of this bug: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/log/drivers/platform/x86/thinkpad_acpi.c -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Confirmed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
** Tags added: patch -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Confirmed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
> Is commit 6640ee6289b9974334e36d8283fc07f37f3b235d also needed? No, this is not related. I have noticed that the original patch does not fit for 4.18. An adapted version is attached. apport data doesn't make sense here. -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Confirmed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
** Patch added: "Patch for 4.18" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+attachment/5240530/+files/0001-platform-x86-thinkpad_acpi-Fix-multi-battery-bug-4.18.patch ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: Confirmed Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812099] Re: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable
Is commit 6640ee6289b9974334e36d8283fc07f37f3b235d also needed? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-hwe (Ubuntu) -- 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/1812099 Title: 4.18.0 thinkpad_acpi : thresholds for BAT1 not writable Status in linux package in Ubuntu: New Bug description: [Problem description] Kernel 4.17 introduced a new interface to set charge thresholds: The interface remained unchanged with 4.18. There's a bug preventing writing the charge thresholds for the secondary battery (BAT1). [Impact] ThinkPads with two batteries (ThinkPad "power bridge") e.g. X240, T440(s), X250, T450(s), X260, T460(s), X270, T470(s) et al. [Steps to reproduce] echo 42 > /sys/class/power_supply/BAT1/charge_start_threshold bash: echo: write error: No such device echo 42 > /sys/class/power_supply/BAT0/charge_start_threshold -- primary battery works! [Fix] Problem was fixed in 4.19: https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/drivers/platform/x86/thinkpad_acpi.c?h=v4.19.15=d22296d9c38fd29a96bb5079fb8d17cee278f40e I propose to cherry-pick the patch for 4.18. [Test Case] See above, a patched 4.18 works for T450s. [Regression Potential] Low. This patch only applies to several ThinkPad machines, and after applying this patch, charge_start/stop_threshold work for BAT0 and BAT. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1812099/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
