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
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:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882823
Title:
int3403 thermal INT3403:00
To manage notifications about this bug
@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 Ubuntu
Bugs, which is subscribed to 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886588
Title:
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1886248
Title:
f6 Function key is not working
To manage notifications about
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
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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879082
Title:
Kernel reporting 100% battery, always
To manage notifications
Proposed package is tested (version below) and this fixes
dump_acpi_tables.py.
~$ lsb_release -c ; apt-cache policy apport
Codename: focal
apport:
Installed: 2.20.11-0ubuntu27.4
Candidate: 2.20.11-0ubuntu27.4
** Tags removed: verification-needed verification-needed-focal
** Tags
@brian-murray,
Bug description is updated. Please keep me posted if it needs more
information. Thanks
** Description changed:
+ [Impact]
+
+ dump_acpi_tables.py does not always generate 4-char table names (which
+ is defined by ACPI spec) and can miss or duplicate data of ACPI tables
+ 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 Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882823
** Also affects: apport (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1883027
Title:
dump_acpi_tables.py: fix incorrect output and change format
#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 Ubuntu
Bugs, which is subscribed to Ubuntu.
A patch was sent for reviews: https://marc.info/?l=linux-
pm=159226080621530=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882823
Title:
int3403 thermal INT3403:00
To manage notifications about
I sent an email asking about 0x91 to mailing list. I will update here
when information is available.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882823
Title:
int3403 thermal INT3403:00
To
https://marc.info/?l=linux-pm=159199577712570=2
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1882823
Title:
int3403 thermal INT3403:00
To manage notifications about this bug go to:
@junocomp,
These mailing lists don't like HTML-formated emails. You need to send
emails in text, and this depends on the email client program you are
using.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is not related to audio driver but is related to thermal driver
"int3403_thermal.c". It supports upto event 0x90 (See line 21 & line 64
@
https://elixir.bootlin.com/linux/v5.7.1/source/drivers/thermal/intel/int340x_thermal/int3403_thermal.c).
Intel may have added a new event that is yet
In fact I suspect EC firmware may be mis-behaving. You can try to remove
all power sources (AC & battery) for a min to reset EC.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1879082
Title:
Kernel
BAT1 is the correct one according to acpi.log in #12.
There are no obvious code error in BIOS, but let's try to see whether
kernel correct reports what BIOS reports.
When AC is connected:
kernel's battery status: $ cat /sys/class/power_supply/BAT0/status
BIOS battery status: sudo acpidbg -b
When my wifi card has issues after long usage, I re-init wifi driver
like "modprobe -r iwlwifi ; modprobe iwlwifi", and it may save some
troubles rebooting.
I don't have Intel wifi but this works on my Qualcomm Atheros QCA6174
(which uses ath10k_pci).
You may also clear the logs in /var/log/
It looks like OS is picking up the virtual (i.e. dummy) battery from
BIOS. Do you also observe this bug when booting with Ubuntu live on a
USB drive?
Can you run "ls /sys/class/power_supply/" to check whether there are
other batteries found by kernel? Usually BIOS likes starting names from
BAT0.
ACPI consists of many tables. Two types of them are DSDT and SSDT.
DSDT is mandatory, and SSDTs are addon to DSDT and are optional. SSDT is
/ can be loaded according to hardware config during boot time. In the
case of this system, the ACPI objects that are erroneous are both
declared in DSDT and
You can disable wakeup by modifying "/proc/acpi/wakeup" in Linux
1. get all wakeup sources - "cat /proc/acpi/wakeup"
The results are something like
Device S-state Status Sysfs node
PEG0 S4*enabled pci::00:01.0
PEGP S4*disabled pci::01:00.0
PEG1 S4
This is usually the result of duplicated name declaration in ACPI BIOS,
and there are usually no harms.
An ACPI dump (sudo acpidump > acpi.log) will be helpful for further
analysis.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@esanya,
Thanks for updating the results. Hopefully the HW failure is the root
cause of the brightness problem that acer can fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861925
Title:
This can be similar to LP:1872351
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875437
Title:
Qualcomm Atheros QCA6174 [168c:003e] subsystem [1a56:1535] WIFI stops
working and system breaks
To
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875672
Title:
lubuntu 20.04 lts can't find touchpad
To manage notifications about
Try to reinitialize wifi driver: "sudo modprobe -r iwlwifi ; sudo
modprobe iwlwifi" after sleep and resume.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1875921
Title:
Wifi doesnt connect when I
** Description changed:
+ [Impact]
+
+ amdgpu generates assert warning messages when retimer is not supported.
+ This behaviour can cause confusions to users.
+
+ [Fix]
+
+ This is fixed by commit a0e40018dcc3f59a. It silences ASSERTs by
+ outputing a debug message and exiting when retimer is
It may worth a shot to ask on Lenovo's forum
(https://forums.lenovo.com/t5/English-Community/ct-p/Community-EN).
Perhaps they will forward this to developers who can take a look and
release a fix for everybody.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which
** Changed in: fwts (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
No ACPI interrupts means either BIOS is broken or system is using other
mechanism like scancode from KBC/EC.
Checking scancode is easy: sudo showkey -s
Also checking interrupts: watch -n1 cat /proc/interrupts <-- usually IRQ 1
If there aren't events from KBC/EC, this is a BIOS or a KBC/EC bug.
The patch was intended to fix Intel RC6 power saving that failed after a
security fix. That implies that zoom may have issues with Intel RC6.
I manually built Ubuntu-5.4.0-21.25
(https://people.canonical.com/~alexhung/LP1873179/focal/) for testing.
The i915 RC6 fix are different. Let's see if
i915.enable_rc6 has been removed since kernel 4.16
See https://patchwork.freedesktop.org/patch/191386/ or commit
fb6db0f5bf1d4d3a4a for more details
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ent in
execlists_user_end()
BugLink: https://bugs.launchpad.net/bugs/1853044
Link: https://gitlab.freedesktop.org/drm/intel/issues/614
Signed-off-by: Seth Forshee
Acked-by: Alex Hung
Acked-by: Colin Ian King
Signed-off-by: Khalid Elmously
---
** Bug watch added: gitlab.freedesktop.org/drm/intel/issues #
"sudo echo "disabled" > /sys/class/thermal/thermal_zone0/mode" is not
correct.
Try
echo "disabled" | sudo tee /sys/class/thermal/thermal_zone0/mode
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
There are four patches added to i915 from Ubuntu-5.3.0-45.37 to
Ubuntu-5.3.0-46.38, like in
https://people.canonical.com/~alexhung/LP1873179/patches/
I built four kernels, each with one patch removed:
https://people.canonical.com/~alexhung/LP1873179/
For example,
p-1 = Ubuntu-5.3.0-46.38 with
If ACPI approach is used, there are also two different approaches used -
ACPI standard or OEM-specific .
ACPI defines events from brightness up and down, and it is
video/brightnessdown BRTDN 0087 & video/brightnessup BRTUP 0086.
The can be checked by running "acpi_listen" and pressing
The brightness interface (/sys/class/backlight/intel_backlight) is
working, so it must be the missing events that cause your problem.
Ubuntu needs keycodes (KEY_BRIGHTNESSDOWN 224 & KEY_BRIGHTNESSUP 225),
and this can be from either scancode or ACPI events. Laptops usually use
ACPI for
The same wifi used on one of the system I have, and I was able to
reproduce the same error once a while. When this warning message
occurred, the system wouldn't connect to my router, either.
I was able to workaround this by "sudo modprobe -r ath10k_pci ; sudo
modprobe ath10k_pci"
I compared
try "rfkill list" to list all radio devices, such as
$ rfkill list
0: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
2: phy0: Wireless LAN
Soft blocked: no
Hard blocked: no
run "rfkill block 2" to disable it, and "run kill unblock 2" to enable
it, assuming your
** Changed in: linux (Ubuntu)
Status: Triaged => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864895
Title:
dmseg report multiple "ACPI Error" and "ACPI BIOS Error"
To manage
This is a warning message generated by sta_info.c (See details @
https://elixir.bootlin.com/linux/v5.4.32/source/net/mac80211/sta_info.c#L1059)
Does your wifi return to normal after disabling and enabling?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
@moreje,
Did you try re-initialize the NIC driver with following commands?
sudo modprobe -r e1000e && sudo modprobe e1000e
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872408
Title:
Network
If you still have older kernels, it would be helpful to identify which
previous kernel does not have this problem. See
https://askubuntu.com/questions/82140/how-can-i-boot-with-an-older-
kernel-version/584738#584738
--
You received this bug notification because you are a member of Ubuntu
Bugs,
A SRU was sent for reviewing. Your help will be needed to test proposed
kernel before next kernel updates later.
This patch is contained in kernel 5.7 rc1 and it is likely to be
included in next Ubuntu release without backporting.
--
You received this bug notification because you are a member
Kernel 5.7rc1 is released, and it can be downloaded @
https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.7-rc1/
There are some changes related to amd backlight from 5.6 to 5.7rc1 such
as the following (list may be not completed), and it surely worthwhile
to give 5.7rc1 a try.
A kernel, based on Ubuntu-5.4.0-21.25 + a0e40018dcc3f, is available for
testing @ https://people.canonical.com/~alexhung/LP1871248/
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1871248
Title:
The errors (or warnings) are generated by ASSERT like the following
statement.
if (!i2c_success)
/* Write failure */
ASSERT(i2c_success);
Details @
https://elixir.bootlin.com/linux/v5.4.31/source/drivers/gpu/drm/amd/display/dc/core/dc_link.c#L1737
I am not an amdgpu expert but I don't
** Tags removed: verification-needed-eoan
** Tags added: verification-done-eoan
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1869235
Title:
Ryzen 3rd gen (3900X) ECC support missing from kernel
@araemo,
Thanks for reporting.
I will prepare a SRU for eoan kernel (5.3). Can you try the below kernel
(Ubuntu-5.3.0-42.34 + cherry-picked e53a3b267fb0 & 3e443eb353ed). If
your problem goes away I will send the patches for SRU reviews.
https://people.canonical.com/~alexhung/LP1869235/
We may
Thanks for opening a bug and testing. Let's mark it fix released. Please
re-open if you have found it fails again.
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
** Changed in: gnome-session (Ubuntu)
Status: New => Fix Released
--
You received this bug
Please try latest mainline kernel (https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.6-rc7/)
If this still fails, please upload log file from acpidump (sudo acpidump
> acpi.log). Usually ACPI battery are named BAT"0" (just a convention).
Let's check whether BIOS has more than one batteries in
It looks like BIOS issue. An acpidump log will help (sudo acpidump >
acpi.log)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1865170
Title:
lid close simply turns off laptop screen
To manage
** Changed in: fwts (Ubuntu)
Status: New => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
It seems that controller_id and use_smooth_brightness are from atombios
(vbios?) and hardware itself; especially atombios (vbios?) are
responsible for many VGA settings and it's a black box.
Good news is that kernel 5.7 will include some backlight enhancement
Does this system have two AMD graphic cards? can you please upload the
output of "lspci -vvnn"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1861925
Title:
BrightnessOutofRange: Actual brightness
I tried Ubuntu Mate 19.10 live on my testing system (AMD Ryzen 5 2500U
with Radeon Vega Graphics - seems to be the same AMD CPU on your Acer),
and brightness control works without any problems even though
actual_brightness has a fixed and higher value.
The below is the latest function can be
I tried 19.10 and 20.04 (daily build) on an AMD platform (AMD Ryzen 5
2500U with Radeon Vega Graphics), and the backlight works without
problems.
This platform has the same symptom as described in the bug description -
actual_brightness is a fixed and higher value, and it does not change
with
In theory, max_brightness and brightness are all needed for backlight
control. I am using stock Ubuntu 19.10 & 20.04 with gnome desktop. Are
you using anything special?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Some system does not work well with s2idle, but they might work with
regular suspend (s3).
Please try "echo deep | sudo tee /sys/power/mem_sleep" to switch to s3,
and verify whether this is s2idle related or a power management issue
with e1000e driver.
--
You received this bug notification
There are a few s2idle fixes and workaround in mainline kernel, and it
may worth a try. If it can fix your problem, fixes can be backported to
bionic
latest mainline kernel: https://kernel.ubuntu.com/~kernel-
ppa/mainline/v5.6-rc4/
instructions:
Fortunately, all of the failing ACPI methods are optional, and there are
good chances that Linux / Ubuntu will work without them. There are three
types of devices *might* be affected according to the error messages:
1. USB (\_SB.PCI0.XHC.RHUB...)- but USB ports and devices should just-
work
There are two types of ACPI errors observed: AE_ALREADY_EXISTS and
AE_NOT_FOUND
The former, AE_ALREADY_EXISTS, usually happens
1) when BIOS loads multiple SSDTs (in /sys/firmware/acpi/tables) that
contains the objects with the same names (and usually the same functions
too). Naming conflicts
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864895
Title:
dmseg report multiple "ACPI Error" a
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Alex Hung (alexhung)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
Title:
CPU0 is busy after S3 in Dell Precision 3
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
Title:
CPU0 is busy after S3 in Dell Precision 3530
To manage
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330673/+files/Lsusb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
Title:
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330678/+files/ProcModules.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330677/+files/ProcInterrupts.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330674/+files/ProcCpuinfo.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330669/+files/CRDA.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
Title:
CPU0
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330671/+files/IwConfig.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330676/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330675/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "PulseList.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330679/+files/PulseList.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
apport information
** Tags added: apport-collected bionic
** Description changed:
CPU0 (and sometimes other cores too) is not entering C10 half of the
time when system is idle. "top" shows a touchpad driver takes 5%~6% of
CPU usage, and "/proc/interrupts" reveals considerable interrupts
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330681/+files/UdevDb.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
Title:
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330672/+files/Lspci.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
Title:
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330670/+files/CurrentDmesg.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330680/+files/RfKill.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
Title:
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1864527/+attachment/5330682/+files/WifiSyslog.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1864527
Public bug reported:
CPU0 (and sometimes other cores too) is not entering C10 half of the
time when system is idle. "top" shows a touchpad driver takes 5%~6% of
CPU usage, and "/proc/interrupts" reveals considerable interrupts from
the touchpad device. This results in additional 4~5 watt power
** Changed in: oem-priority
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
** Changed in: fwts (Ubuntu)
Importance: Undecided => Wishlist
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1855420
Title:
dmicheck Type 41 result doesn't reflect real condition
To manage
There is only one other check can be done for type 41 - Device Type
Instance must be unique for a device type.
However, it's going to be ugly code to support this in the current fwts
dmicheck implementation. I am not sure whether this is worthwhile as it
is a small feature and there aren't any
@dimitri,
Does the patch solve your problem? It is included in fwts 19.12.00
release.
commit 4ab38cf18a5abf3264cd6ac1b12f23eaa012848e
Author: Colin Ian King
Date: Thu Nov 21 19:37:41 2019 +
efi_runtime: don't build dkms module for kernels 4.8.0 and above (LP:
#1853090)
There are a few things can be checked to type 41 in fwts. I am looking
into it. It may not be solve this bug but it is still worthwhile to add
more sanity checks.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@cktenn,
fwts has no way to know it is an onboard device unless it is reported to
be so. A computer can has a PCIe inserted without having a antry in
table 41. From fwts's (or spec's) viewpoint, there is nothing wrong
here.
--
You received this bug notification because you are a member of
301 - 400 of 860 matches
Mail list logo
