Public bug reported:
[Impact]
TGL systems wake up automatically from s2idle when connecting to a docking
station with a monitor. The wake-up events are generated when BIOS sets
ALL_MONITOR_OFF for power-saving on TGL systems.
[Fix]
A BIOS workaround is used to skip ALL_MONITOR_OFF with an _OSI
You can also try Ubuntu OEM kernel:
https://wiki.ubuntu.com/Kernel/OEMKernel
--
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/1900377
Title:
System froze after wake from sleep
Status in
There are many i915 warnings in dmesg.txt
Oct 19 14:33:05 kernel: [ cut here ]
Oct 19 14:33:05 kernel: WARN_ON(is_mst && (port == PORT_A || port == PORT_E))
Oct 19 14:33:05 kernel: WARNING: CPU: 3 PID: 2246 at
drivers/gpu/drm/i915/display/intel_ddi.c:3179
You can also try to use s3 (deep) instead of s2idle: echo deep | sudo
tee /sys/power/mem_sleep
to change back, simply reboot or "echo s2idle | sudo tee
/sys/power/mem_sleep"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
The number of IRQ 9 (acpi) seems to be unreasonably high, i.e. 10 in
ProcInterrupts.txt
I tried on my laptop (command: "uptime ; cat /proc/interrupts | grep
acpi"), and it is 15859 after 13 mins (~8000 when uptime = 0 min). If
you see 10 right after booting, the hardware / firmware may be
The below is likely the reason that fn keys do not work, i.e. irq 9
(acpi) are disabled because it is not handled.
[9.932829] irq 9: nobody cared (try booting with the "irqpoll" option)
[9.932832] CPU: 1 PID: 0 Comm: swapper/1 Not tainted 5.4.0-48-generic
#52-Ubuntu
[9.932833]
Hui Wang also provided some workaround for touchpad at LP:1899258. If
kernel updates do not fix touchpad problem, you can also try the kernel
parameters.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The id ELAN0633 has been added since Ubuntu-5.4.0-34.38. Please update
kernel (sudo apt update && sudo apt upgrade -y) and verify whether the
touchpad works.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
I don't think amdgpu's actual_brightness works in the first place.
Did you try any of the following kerenl parameters?
acpi_backlight= [HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
A post at Dell's forum has a workaround solution using a kernel
parameter "snd_hda_intel.dmic_detect=0".
https://www.dell.com/community/Linux-General/Freezing-boot-
Ubuntu-20-04-Dell-G3-3590/m-p/7667770/highlight/true#M17469
--
You received this bug notification because you are a member of
@azis-naufal,
#15 is where _PRW goes indeed, but my guess was wrong...
** Changed in: linux (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You can force to use s2idle instead of deep (s3). This might force the
system as in #5.
command: $ echo s2idle | sudo tee /sys/power/mem_sleep
If this works for you, this is a better solution than patching DSDT.
--
You received this bug notification because you are a member of Kernel
Packages,
_PRW requires knowledge of the hardware pin used for wake-up by lid, and
this is not available outside vendor themselves. We can, however, just
make a guess such as below
Method (_PRW, 3, NotSerialized)
{
Return (Package () {9, 3})
}
The attached is a patch for
Did you try "systemd-analyze time" or "systemd-analyze blame" to
identify the boot-time's bottleneck?
--
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/1898878
Title:
Ubuntu slow boot
This is a BIOS issue and a fix is required from OEM and is not from
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/1898949
Title:
ThinkBook 14-IIL can't wake from sleep by
The ACPI's lid device "LID0" is not listed in /proc/acpi/wakeup, and it
can be the result of missing "_PRW" object in ACPI BIOS. It has only
_HID, _LID and _DSW objects such as below (extracted from acpidump.txt).
Device (LID0)
{
Name (_HID, EisaId ("PNP0C0D")
Method (_LID, 0,
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
--
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/1894667
Title:
[HP 635] Radeon 6310 brightness cont
** 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
+
That's great. Let's wait for the good news!
--
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/1895615
Title:
Backlight adjustment doesn't work on Google Pixel Slate
Status in linux
Information updates: the patch is now queued in 5.10.
--
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/1894667
Title:
[HP 635] Radeon 6310 brightness control does not work
Status in
@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
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.
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
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
@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)
-
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
It is a good idea to send your patch to below kernel's mailing lists so
this can be reviewed by broader audiences to confirm it will work in all
scenario.
INTEL DRM DRIVERS (excluding Poulsbo, Moorestown and derivative chipsets)
M: Jani Nikula
M: Joonas Lahtinen
M: Rodrigo Vivi
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
@afsverissimo,
You may want to file another bug for your brightness problem which may
have different root cause and thus different required information.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of
dmesg shows nothing of ath10k_pci (wifi driver).
Please run "sudo modprobe -r ath10k_pci ; sudo modprobe ath10k_pci" to
check whether wifi driver can be re-initialized?
You may want to download and run live session of Ubuntu 20.04.1 ISO to
verify whether Qualcomm Atheros QCA9377 works.
**
** Summary changed:
- cpu frequency stuck to max when pugging USB device
+ cpu frequency stuck to max when plugging USB device
** Summary changed:
- cpu frequency stuck to max when plugging USB device
+ cpu frequency stuck to max when plugging USB devices
--
You received this bug notification
You can try the following utilities to see whether CPUs are occupied
before and after USB devices are plugged in
1. top - check whether any processes is running
2. watch -n1 cat /proc/interrupts - check whether any interrupts are generated
at abnormal rates
3. powertop - more details of power
#5 simply complains that ACPI BIOS can directly access I/O ports and
Linux kernel is not fond of it. The warnings are very often harmless.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The error messages are caused by BIOS bugs, and they cannot be fixed in
Ubuntu.
OC07 error in descriptions is declared but not defined in ACPI DSDT,
i.e. External (OC07, UnknownObj).
The OEMB in #6 has a checksum (i.e. one of OEMx) is a OEM-specific table and
that's probably used in Windows
Sure I will update the information here.However, this will take a while,
i.e. patch review -> mainline kernel -> stable kernel -> Ubuntu focal
kernel.
It is the same as using the kernel parameter, and the patch will not
conflict with kernel parameter either.
--
You received this bug
A patch was sent to upstream for review
--
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/1894667
Title:
[HP 635] Radeon 6310 brightness control does not work
Status in linux package in
Please try the kernel @
https://people.canonical.com/~alexhung/LP1894667/
1. remove kernel parameter "acpi_backlight=video"
2. download all deb
3. install kernel by "sudo dpkg -i *.deb"
4. reboot
This should be the same as "acpi_backlight=video"
1. run "ls /sys/class/backlight"
2. verify
This is kind of expected since it is common that systems from 2011 use
ACPI video interface. You can add the kernel into /etc/default/grub to
make it consist across boots.
I will compile a linux kernel with a workaround of
"acpi_backlight=video" for testing. If this work I can submit to linux
Let's try manually whether backlight interfaces work.
cd /sys/class/backlight/radeon_bl0
# get max brightness
cat max_brightness
# get current brightness
cat brightness
# change current brightness, assuming max=12
echo 12 | sudo tee brightness
echo 6 | sudo tee brightness
Once done,
For modifying / adding kernel parameters, please refer to
https://wiki.ubuntu.com/Kernel/KernelBootParameters
--
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/1894667
Title:
[HP 635]
Please run "ls /sys/class/backlight/" to see what backlight interfaces
are available.
You may also want to try the kernel parameter for backlight such as
below
acpi_backlight= [HW,ACPI]
{ vendor | video | native | none }
If set to vendor,
Did you try to remove the kernel parameter "acpi_osi=linux"?
Please run "ls /sys/class/backlight/" to see what backlight interfaces
are available.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
The fix is included in Ubuntu-5.4.0-43.47 and later
** 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/1882823
Title:
You can use apt purge to remove installed kernel: sudo apt purge linux-
image-... linux-header-..., where ... is the version you want to remove.
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Kernel
Packages,
Linux 5.8.5-050805, or any kernels on https://kernel.ubuntu.com/~kernel-
ppa/mainline/, is not a supported kernel version.
Kernel 5.8 is also used on groovy. Please download and install deb @
https://people.canonical.com/~alexhung/LP1893624/
Once installed, please verify errors and update bug
These object names look like "PCI Interrupt Link Device" but they are
not declared (further analysis requires acpidump log - sudo acpidump >
acpi.log). This is a BIOS bug which kernel can do little to help.
Fortunately, if you don't observe any obvious failures, these errors can
be ignored
--
You can use the GUI app "keyboard shortcuts" to setup custom keys, or
you can manually modify hwdb files (ex.
/lib/udev/hwdb.d/60-keyboard.hwdb).
The following tutorials may provide some help.
== Modify keymap ==
* cd /lib/udev/hwdb.d/
* edit keymap file (60-keyboard.hwdb)
* add a change, ex
You can also try the unload & reload Bluetooth driver by "sudo modprobe
-r btusb ; sudo modprobe btusb". It may save you some time.
--
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/1892012
Perhaps vicamo's comments #19 on LP:1891405 will help
--
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/1872351
Title:
Qualcomm Atheros QCA6174 [168c:003e] Subsystem: Killer 1435 Wireless-
vicamo posted a probable solution @
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891405. See #19
for more details
--
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/1886588
Title:
This sounds like Bluetooth hardware malfunctions until a full reset (or
completely powered off).
--
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/1892012
Title:
Bluetooth doesn't turn on
This should be an ACPI BIOS bug, and there is not much to be done in
Linux.
An acpidump log (sudo acpidump > acpi.log) is required for more analysis
of what functions are impacted.
** Changed in: linux (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug notification
0. install acpidbg - sudo apt install linux-tools-`uname -r` linux-
tools-generic
trigger and check which of the following cause screen freeze
1. sudo acpidbg -b "e EV5 1 0" ("2 0" for brightness down)
2. sudo acpidbg -b "e \_SB.PCI0.GFX0.BRT6 1 0" ("2 0" for brightness down)
3. sudo acpidbg -b
please refer to https://wiki.archlinux.org/index.php/backlight for more
info on /sys/class/backlight/ interfaces
--
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/1891032
Title:
Brightness
The flow of brightness hotkey is as follows
key pressed -> ec triggers events -> bios/os performs a series of
following functions -> ... -> ACPI EV5 -> ACPI BRT6 -> ACPI Notify LCD
0x86/0x87 -> ACPI VGA driver generates keycodes -> userspace write to
** 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/1890873
Title:
no intel_backlight file
Status in linux package in
This can be related to BIOS or to kernel driver.
Could you please run "ls /sys/class/backlight/" for backlight sysfs, and
attach output of "sudo acpidump > acpi.log" for BIOS analysis.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to
Since this system is upgraded from 18.04, it is also worthwhile to boot
20.04.1 USB and verify this issue. Suspend and resume can be tested in
live session as well.
** Summary changed:
- unable to coonect to wifi
+ unable to connect to wifi
--
You received this bug notification because you
Additional information with kaihengfeng's comment.
dmesg shows wifi stops working after suspend and resume. wifi driver
also tried to restart hardware but failed:
[ 459.548998] e1000e: enp0s25 NIC Link is Down
[ 461.601935] iwlwifi :03:00.0: Error sending REPLY_SCAN_ABORT_CMD: time
out
dmesg shows "video.use_native_backlight=1" is used. This kernel
parameter is no longer available. You can replace with "acpi_video"
acpi_backlight= [HW,ACPI]
acpi_backlight=vendor
acpi_backlight=video
If set to vendor, prefer vendor specific driver
(e.g.
Do you mean you cannot adjust brightness with either hotkeys or GUI?
intel_backlight is one of possible backlight interfaces. You can run "ls
/sys/class/backlight" to find out what your system has.
--
You received this bug notification because you are a member of Kernel
Packages, which is
** Changed in: linux (Ubuntu)
Status: Confirmed => Won't Fix
** Changed in: linux (Ubuntu)
Status: Won't Fix => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You can try "sync" to force writing cache to USB drive. It is easier to
remember.
--
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/1890467
Title:
wmi_bus wmi_bus-PNP0C14:00: WQBC data
You can also try to verify sysfs interfaces such as below example
$ ls /sys/class/backlight/
intel_backlight
$ cd /sys/class/backlight/intel_backlight
$ cat max_brightness
12
$echo 12 | sudo tee brightness
$echo 6 | sudo tee brightness
If this does not change brightness, something
For waking up unexpected issues, you can try to disable wakeup devices
via /proc/acpi/wakeup interfaces.
See examples @ https://askubuntu.com/questions/148481/how-do-i-prevent-
immediate-wake-up-from-suspend-and-or-hibernation
--
You received this bug notification because you are a member of
These ACPI warnings are harmless most of time, but that also depends on what
ACPI BIOS does on your systems.
=
[ 0.659825] wmi_bus wmi_bus-PNP0C14:00: WQBC data block query control method
not found
WQBC is required according to WMI spec and implementation on
Ubuntu 20.04.1 is going to be released on Aug 06 (tomorrow). You can
also give it a try too.
--
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/1888570
Title:
poweroff not working after apt
** 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/194
Title:
Qualcomm Atheros QCA9377 [168c:0042] Subsystem
A fresh install would certainly help. It is also possible that
additional drivers can cause this; NV proprietary driver can be an
example of it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Performance degrades can also related to power saving. Try kernel
parameter "pcie_aspm=off" to verify whether it improves
--
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/194
Title:
#19 and forward assume kernel 5.3.0-61 is good, according to bug
description; however, it may worthwhile to give it:
https://people.canonical.com/~alexhung/LP1888570/Ubuntu-5.3.0-61.55/
Especially, all tries were bad kind of worrying...
If it is good, the next one is
@gneisss,
I forgot to remove to *tool*.deb. They aren't needed.
next one: https://people.canonical.com/~alexhung/LP1888570/115f51d0fa11/
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Thanks. Next one is
https://people.canonical.com/~alexhung/LP1888570/0affe1fa22b2/
--
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/1888570
Title:
poweroff not working after apt upgrade
You can also update linux-firmware (from
http://security.ubuntu.com/ubuntu/pool/main/l/linux-firmware/) and / or
update system BIOS (do it with cautions).
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
It is odd that lspci shows you have a Qualcomm Atheros QCA9377 with
driver ath10k_pci, but dmesg shows nothing about ath10k as QCA9377 never
exists.
Can you run lspci -v to confirm QCA9377 and run "sudo modprobe -r
ath10k_pci ; sudo modprobe ath10k_pci" to unload and reload wifi driver.
Also run
@gneiss,
Thanks. Next one is
https://people.canonical.com/~alexhung/LP1888570/d37a638086c1/
--
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/1888570
Title:
poweroff not working after apt
*** This bug is a duplicate of bug 1810183 ***
https://bugs.launchpad.net/bugs/1810183
You may need to report this to upstream or even to ASUS to support this
device. Vendor may decide to support it on Linux with enough request.
** This bug has been marked a duplicate of bug 1810183
Correction to #19. The kernel is available @
https://people.canonical.com/~alexhung/LP1888570/19357b3b0835/
--
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/1888570
Title:
poweroff not
Thanks for reporting this, and your help is needed to identify the patch
that causes this regression.
There are 260 patches between 5.3.0-61 & 5.3.0-62, and it requires some
testing with bisects (see below).
$ git bisect start
$ git bisect good Ubuntu-5.3.0-61.55
$ git bisect bad
Please try mainline kernels (https://kernel.ubuntu.com/~kernel-
ppa/mainline/), for example, 5.8rc6.
If it works, please try 5.6 and then repeat bisecting.
This can help identify whether fixes are available and what fix is.
--
You received this bug notification because you are a member of
The errors comes from physical layer so they likely comes from the root
port (00:1d.0) or the device attaches to it. Also, PCIe correctable
errors are handled by hardware, so one can turn off some hardware-
related features, such as apsm (pcie_aspm=off) or msi (pci=nomsi), to
verify whether there
When a PCIe AER error is captured, an error message will be output to
console. If it's a correctable error, it is output as a warning.
Otherwise, it is printed as an error. So users could choose different
log level to filter out correctable error messages.
PCI(e) is capable of correcting errors whenever possible. From your logs
all of the errors are corrected and therefore nothing to worry about.
If you see incorrectable errors you may observed device failures, or
system failures in some cases.
--
You received this bug notification because you
A test kernel, based on UBUNTU: Ubuntu-5.4.0-42.46, is available @
https://people.canonical.com/~alexhung/LP1887218/ver1/
If this solves this bug, we can keep bisecting. If not, we can try other
patches.
The following commits are excluded:
== merges ==
1daa56bcfd8b329447e0c1b1e91c3925d08489b7
Since the workaround involves amd's iommu and kernel 5.5, we may be able
to find a patch that fixes this by cherry-pikcy: git log --pretty=short
v5.4..v5.5 -- drivers/iommu/amd_iommu.c
commit 1daa56bcfd8b329447e0c1b1e91c3925d08489b7
Merge: a5255bc31673 9b3a713feef8
Author: Linus Torvalds
It shouldn't be long that Ubuntu 20.04 kernel gets it from upstream.
--
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/1882823
Title:
int3403 thermal INT3403:00
Status in linux package in
The patch was meraged to 5.4 stable 5 hours ago -
=
This is a note to let you know that I've just added the patch titled
thermal: int3403_thermal: Downgrade error message
to the 5.4-stable tree which can be found at:
@bybeu,
USB Emulation: This allows USB devices (keyboard, mouse, USB drives) to
operate in BIOS / DOS.
USB Powershare: This allows USB ports to provide powers in sleep or
power-off, depends on hardware designs. This consumes some battery power
in sleep or power-off
USB Wake Support: This allows
** Description changed:
The Intel x710-TM4 is one of the latest 10GbE controllers from intel
using the i40e driver. This particular 4 port comes in a 2x2
- arrangement: 2x SFP+ and 2x RJ-45. This car is enabled in 5.4 via the
+ arrangement: 2x SFP+ and 2x RJ-45. This card is enabled in 5.4
If this problem only occurs after you upgrade kernel, we may be able to
identify the regression patch by bisecting kernels if a passing kernel
version is shared.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
You can disable USB3 wakeup by modifying "/proc/acpi/wakeup"
1. list all wakeup sources - cat /proc/acpi/wakeup
2. enable or disable by echo device name - for example, my USB3 is XHC
- echo XHC | sudo tee /proc/acpi/wakeup
3. confirm changes - cat /proc/acpi/wakeup
--
You received this bug
@azimcuetcse01,
I believed vicamo meant the procedures in comment #2, such as
1. upload logs by running "apport-collect 1885671"
2. change bug status to "confirm"
Please update to latest packages and kernel (sudo apt update && sudo apt
upgrade -y && sudo reboot) and reproduce the bug before
The log in description clearly points out "firmware crashed", and that
may be something we can forward to the hardware vendor.
--
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/1886588
Do you mean "F6" or the "hotkey" on your F6?
More information will be needed such as what F6 function key (hotkey) is
supposed to do and what laptop you have and so on. Running apport-
collect as in #1 will certainly helps.
Did you try Ubuntu 20.04 USB-live and verify whether this also happens
It would be a great help to list which previous kernel version works,
too.
--
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/1886248
Title:
f6 Function key is not working
Status in linux
I have also a Qualcomm Atheros QCA6174 and can observe it fails from
time to time, not in focal only. More discussion can be found in
LP:1872351
While there aren't solution now, I use "sudo modprobe -r ath10k_pci ;
sudo modprobe ath10k_pci" to avoid rebooting the system.
--
You received this
** Changed in: linux (Ubuntu)
Status: In Progress => Won't Fix
--
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/1879082
Title:
Kernel reporting 100% battery, always
Status in
I also cc'ed stable which includes kernel 5.4. It should be available in
kernel 5.4 automatically when (and if) it lands into mainline kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
#17 looks like correct behavours. I also noticed #13 said battery was
acting without problems anymore. Is it still the case or did you have
problems when running #17?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
201 - 300 of 577 matches
Mail list logo
