[Kernel-packages] [Bug 1941898] Re: ubuntu_kernel_selftests.ftrace timeout on H/riscv
This is because of bug 1940971, autotest timeout is not working as
expected on RISCV kernel.
Workaround is to disable the timeout for this test on RISCV:
https://git.launchpad.net/~canonical-kernel-team/+git/autotest-client-tests/commit/?id=0170e2de7083e6e1d8ca4b3ad92c3f059889b69c
** Changed in: ubuntu-kernel-tests
Status: New => Fix Released
** Changed in: ubuntu-kernel-tests
Assignee: (unassigned) => Po-Hsu Lin (cypressyew)
** Changed in: linux-riscv (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-riscv in Ubuntu.
https://bugs.launchpad.net/bugs/1941898
Title:
ubuntu_kernel_selftests.ftrace timeout on H/riscv
Status in ubuntu-kernel-tests:
Fix Released
Status in linux-riscv package in Ubuntu:
Invalid
Status in linux-riscv source package in Hirsute:
Won't Fix
Bug description:
ubuntu_kernel_selftests.ftrace times out always after the same step
when running on hirsute/linux-riscv on the regression tests
infrastructure (QEMU VM).
Log from the tests running with hirsute/linux-riscv 5.11.0-1018.19:
18:02:56 INFO | START ubuntu_kernel_selftests.ftrace
ubuntu_kernel_selftests.ftrace timestamp=1629568976timeout=1800
localtime=Aug 21 18:02:56
18:02:56 DEBUG| Persistent state client._record_indent now set to 2
18:02:56 DEBUG| Persistent state client.unexpected_reboot now set to
('ubuntu_kernel_selftests.ftrace', 'ubuntu_kernel_selftests.ftrace')
18:02:56 DEBUG| Waiting for pid 29328 for 1800 seconds
18:02:56 WARNI| System python is too old, crash handling disabled
18:02:56 DEBUG| Running 'sudo sh -c 'echo 1 >
/proc/sys/net/ipv4/conf/all/accept_local''
18:02:56 DEBUG| Running 'sudo make -C linux/tools/testing/selftests
TARGETS=ftrace run_tests'
18:02:57 DEBUG| [stdout] make: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests'
18:02:57 DEBUG| [stdout] make --no-builtin-rules ARCH=riscv -C ../../..
headers_install
18:02:57 DEBUG| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18:03:13 DEBUG| [stdout] INSTALL ./usr/include
18:03:14 DEBUG| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux'
18:03:14 DEBUG| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
18:03:14 DEBUG| [stdout] make[1]: Nothing to be done for 'all'.
18:03:14 DEBUG| [stdout] make[1]: Leaving directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
18:03:15 DEBUG| [stdout] make[1]: Entering directory
'/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/ftrace'
18:03:15 DEBUG| [stdout] TAP version 13
18:03:15 DEBUG| [stdout] 1..1
18:03:15 DEBUG| [stdout] # selftests: ftrace: ftracetest
18:03:15 ERROR| [stderr] perl: warning: Setting locale failed.
18:03:15 ERROR| [stderr] perl: warning: Please check that your locale
settings:
18:03:15 ERROR| [stderr] LANGUAGE = (unset),
18:03:15 ERROR| [stderr] LC_ALL = (unset),
18:03:15 ERROR| [stderr] LC_CTYPE = "C.UTF-8",
18:03:15 ERROR| [stderr] LANG = "en_US.UTF-8"
18:03:15 ERROR| [stderr] are supported and installed on your system.
18:03:15 ERROR| [stderr] perl: warning: Falling back to the standard locale
("C").
18:03:16 DEBUG| [stdout] # === Ftrace unit tests ===
18:03:21 DEBUG| [stdout] # [1] Basic trace file check [PASS]
18:03:58 DEBUG| [stdout] # [2] Basic test for tracers [PASS]
18:04:04 DEBUG| [stdout] # [3] Basic trace clock test [PASS]
18:04:10 DEBUG| [stdout] # [4] Basic event tracing check [PASS]
18:04:16 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS]
18:04:21 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS]
18:04:27 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS]
18:04:32 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers
[UNRESOLVED]
18:04:33 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes
[UNSUPPORTED]
18:04:38 DEBUG| [stdout] # [10] Generic dynamic event - add/remove kprobe
events [FAIL]
18:04:39 DEBUG| [stdout] # [11] Generic dynamic event - add/remove synthetic
events [UNSUPPORTED]
18:04:39 DEBUG| [stdout] # [12] Generic dynamic event - selective clear
(compatibility) [UNSUPPORTED]
18:04:40 DEBUG| [stdout] # [13] Generic dynamic event - generic clear event
[UNSUPPORTED]
18:04:46 DEBUG| [stdout] # [14] event tracing - enable/disable with event
level files [PASS]
18:04:54 DEBUG| [stdout] # [15] event tracing - restricts events based on pid
notrace filtering [PASS]
18:05:00 DEBUG| [stdout] # [16] event tracing - restricts events based on pid
[PASS]
18:05:07
[Kernel-packages] [Bug 1926564] Re: An recursive locking in igb and igc drivers
This issue has been fixed by below commit which is included in v5.16 ac8c58f5b535 igb: fix deadlock caused by taking RTNL in RPM resume path -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1926564 Title: An recursive locking in igb and igc drivers Status in HWE Next: Incomplete Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Won't Fix Bug description: [Impact] The rtnl_lock() has been called in rtnetlink_rcv_msg(), and then in __dev_open() it calls pm_runtime_resume() to resume devices, and in some devices' resume function(igb_resum,igc_resume) they calls rtnl_lock() again. That leads to a recursive lock. This issue is introduced by below commit since v5.9-rc1 bd869245a3dc net: core: try to runtime-resume detached device in __dev_open [Fix] This commit currently is still under discussion fixes the issue. https://lkml.org/lkml/2021/4/20/123 [Test] Verified on Dell Precision workstations. [Where problems could occur] The patch is pretty straightforward, no problems could occur by this change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1926564/+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 1987711] Re: [i915] Ubuntu display get shifted after some time.
drm-tip is a test kernel used to tell if a fix already exists upstream, and it sounds like it does. But the fix you need might already exist in a mainline version, so try: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.19.5/amd64/ -- 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/1987711 Title: [i915] Ubuntu display get shifted after some time. Status in linux package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987711/+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 1988620] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613832/+files/Lsusb-v.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported
[Kernel-packages] [Bug 1988620] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613831/+files/Lsusb-t.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported
[Kernel-packages] [Bug 1988620] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613830/+files/Lsusb.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported
[Kernel-packages] [Bug 1988620] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613843/+files/acpidump.txt ** 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported
[Kernel-packages] [Bug 1988620] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613842/+files/WifiSyslog.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is
[Kernel-packages] [Bug 1988620] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613837/+files/ProcInterrupts.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported
[Kernel-packages] [Bug 1988620] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613841/+files/UdevDb.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported
[Kernel-packages] [Bug 1988620] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613838/+files/ProcModules.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is
[Kernel-packages] [Bug 1988620] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613833/+files/PaInfo.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported
[Kernel-packages] [Bug 1988620] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613840/+files/RfKill.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported
[Kernel-packages] [Bug 1988620] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613836/+files/ProcEnviron.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is
[Kernel-packages] [Bug 1988620] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613839/+files/PulseList.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is
[Kernel-packages] [Bug 1988620] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613835/+files/ProcCpuinfoMinimal.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported
[Kernel-packages] [Bug 1988620] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613834/+files/ProcCpuinfo.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is
[Kernel-packages] [Bug 1988620] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613825/+files/CurrentDmesg.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is
[Kernel-packages] [Bug 1988620] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613827/+files/IwConfig.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is
[Kernel-packages] [Bug 1988620] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613824/+files/CRDA.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported
[Kernel-packages] [Bug 1988620] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613828/+files/Lspci.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported
[Kernel-packages] [Bug 1988620] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613829/+files/Lspci-vt.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is
[Kernel-packages] [Bug 1988620] HookError_ubuntu.txt
apport information ** Attachment added: "HookError_ubuntu.txt" https://bugs.launchpad.net/bugs/1988620/+attachment/5613826/+files/HookError_ubuntu.txt -- 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/1988620 Title: Asus n61vn Brightness Control Levels Supported Status in linux package in Ubuntu: Confirmed Bug description: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported
[Kernel-packages] [Bug 1988620] Re: Asus n61vn Brightness Control Levels Supported
apport information ** Tags added: apport-collected vanessa ** Description changed: Hello there. First of all, thank you to all the developers for this package. My computer is laptop asus n61vn. I'm using linux mint 21 (similar to ubuntu 22.04) I did hardware test my computer with "fwts" software and got the following errors. Can these errors be fixed? --- Test 192 of 207: Test _BCL (Query List of Brightness Control Levels Supported). FAILED [CRITICAL] brightness level on full power (15) is not in brightness levels. FAILED [CRITICAL] brightness level on battery (14) is not in brightness levels. Advice\_SB_.PCI0.P0P1.VGA_.LCDD._BCL seems to be misconfigured and is returning incorrect brightness levels.It is worth sanity checking this with the firmware test suite interactive test 'brightness' to see how broken this is. As it is, _BCL is broken and needs to be fixed. Test 1 of 1: Kernel log error check. HIGH Kernel message: [ 0.358575] pci :06:00.0: [Firmware Bug]: disabling VPD access (can't determine size of non-standard VPD format) Test 1 of 1: Validate the System management mode (SMM) locks. Graphics Control register is not locked (GGCLCK != 1). TSEG Memory Base register is not locked. Top of Low Usable DRAM (TOLUD) register is not locked. Test 1 of 5: Test CPU generic MSRs. MSR 0x019b THERM_INTERRUPT has 1 inconsistent values across 2 CPUs (shift: 0 mask: 0x11f). MSR CPU 0 -> 0xe39400 vs CPU 1 -> 0xe49400 Test 1 of 1: ACPI table checksum test. Table ATKG has incorrect checksum, expected 0x2e, got 0xa7. --- The hardware is briefly as follows: ramiz@ramiz-pc:~$ uname -a Linux ramiz-pc 5.15.0-47-generic #51-Ubuntu SMP Thu Aug 11 07:51:15 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux ramiz@ramiz-pc:~$ lspci 00:00.0 Host bridge: Intel Corporation Mobile 4 Series Chipset Memory Controller Hub (rev 07) 00:01.0 PCI bridge: Intel Corporation Mobile 4 Series Chipset PCI Express Graphics Port (rev 07) 00:1a.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #4 (rev 03) 00:1a.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #5 (rev 03) 00:1a.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #6 (rev 03) 00:1a.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #2 (rev 03) 00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 03) 00:1c.0 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 1 (rev 03) 00:1c.1 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 2 (rev 03) 00:1c.2 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 3 (rev 03) 00:1c.5 PCI bridge: Intel Corporation 82801I (ICH9 Family) PCI Express Port 6 (rev 03) 00:1d.0 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #1 (rev 03) 00:1d.1 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #2 (rev 03) 00:1d.2 USB controller: Intel Corporation 82801I (ICH9 Family) USB UHCI Controller #3 (rev 03) 00:1d.7 USB controller: Intel Corporation 82801I (ICH9 Family) USB2 EHCI Controller #1 (rev 03) 00:1e.0 PCI bridge: Intel Corporation 82801 Mobile PCI Bridge (rev 93) 00:1f.0 ISA bridge: Intel Corporation ICH9M LPC Interface Controller (rev 03) 00:1f.2 SATA controller: Intel Corporation 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode] (rev 03) 01:00.0 VGA compatible controller: NVIDIA Corporation GT216M [GeForce GT 240M] (rev a2) 01:00.1 Audio device: NVIDIA Corporation GT216 HDMI Audio Controller (rev a1) 03:00.0 Network controller: Intel Corporation Ultimate N WiFi Link 5300 06:00.0 Ethernet controller: Qualcomm Atheros AR8131 Gigabit Ethernet (rev c0) ramiz@ramiz-pc:~$ # dmidecode 3.3 Getting SMBIOS data from sysfs. SMBIOS 2.5 present. 44 structures occupying 2066 bytes. Table at 0x000FCF90. Handle 0x, DMI type 0, 24 bytes BIOS Information Vendor: American Megatrends Inc. Version: 209 Release Date: 11/04/2009 Address: 0xF Runtime Size: 64 kB ROM Size: 1 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed ESCD support is available Boot from CD is supported Selectable boot is supported EDD is supported 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 3.5"/2.88 MB floppy services are supported (int 13h) Print screen service is supported (int 5h) 8042 keyboard services are
[Kernel-packages] [Bug 1851518] Re: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones
@PowerKiki I'm really sorry for the delay. My computer crashed and I needed to repair it.. I just finished... After a year I reinstalled the latest kernel but the problem seems to persist. Here is the result of the alsa-info.sh: http://alsa-project.org/db/?f=08a95ec89e5a0a02f38d7183cf9b2078fadff751 Do you have any clues? -- 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/1851518 Title: [950SBE/951SBE, Realtek ALC298, Speaker, Internal] No sound on internal speakers, very very quiet on headphones Status in Linux: New Status in linux package in Ubuntu: Fix Released Bug description: I've been googling this issue for 10's of hours and tried many things. Relase of Ubuntu: 19.10 Expected outcome: Music plays on the internal speakers and headphones. Actual outcome: I can barely hear audio using headphones with volume turned up to 150%. Absolutely nothing comes out of the speakers. (The speakers sound great under Windows 10.) Complete alsa-info output is attached, but here are some snippets: !!DMI Information !!--- Manufacturer: SAMSUNG ELECTRONICS CO., LTD. Product Name: 950SBE/951SBE Product Version: P06RES Firmware Version: P06RES.075.190529.SP Board Vendor: SAMSUNG ELECTRONICS CO., LTD. Board Name:NP950SBE-K01US !!Kernel Information !!-- Kernel release:5.3.0-19-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.3.0-19-generic Library version:1.1.9 Utilities version: 1.1.9 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [PCH]: HDA-Intel - HDA Intel PCH HDA Intel PCH at 0x604b118000 irq 177 !!PCI Soundcards installed in the system !!-- 00:1f.3 Multimedia audio controller: Intel Corporation Cannon Point-LP High Definition Audio Controller (rev 11) !!Advanced information - PCI Vendor/Device/Subsystem ID's !!--- 00:1f.3 0401: 8086:9dc8 (rev 11) DeviceName: Onboard - Sound !!HDA-Intel Codec information !!--- --startcollapse-- Codec: Realtek ALC298 Address: 0 AFG Function Id: 0x1 (unsol 1) Vendor Id: 0x10ec0298 Subsystem Id: 0x144dc812 Revision Id: 0x100103 No Modem Function Group found Default PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Default Amp-In caps: N/A Default Amp-Out caps: N/A State of AFG node 0x01: Power states: D0 D1 D2 D3 D3cold CLKSTOP EPSS Power: setting=D0, actual=D0 GPIO: io=8, o=0, i=0, unsolicited=1, wake=0 IO[0]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[1]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[2]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[3]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[4]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[5]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[6]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 IO[7]: enable=0, dir=0, wake=0, sticky=0, data=0, unsol=0 Node 0x02 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Headphone Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Device: name="ALC298 Analog", type="Audio", device=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x00 0x00] Converter: stream=1, channel=0 PCM: rates [0x60]: 44100 48000 bits [0xe]: 16 20 24 formats [0x1]: PCM Power states: D0 D1 D2 D3 EPSS Power: setting=D0, actual=D0 Node 0x03 [Audio Output] wcaps 0x41d: Stereo Amp-Out Control: name="Speaker Playback Volume", index=0, device=0 ControlAmp: chs=3, dir=Out, idx=0, ofs=0 Amp-Out caps: ofs=0x7f, nsteps=0x7f, stepsize=0x01, mute=0 Amp-Out vals: [0x7f 0x7f] Converter: stream=1, channel=0 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-19.20-generic 5.3.1 Uname: Linux 5.3.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1383 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Nov 6 06:20:08 2019 InstallationDate: Installed on 2019-11-03 (3 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64
[Kernel-packages] [Bug 1947162] Re: Bluetooth does not work on ASUS ROG Strix G15 Advantage Edition G513 laptop on Ubuntu 21.10
Confirmed with ROG Strix G713R and Ubuntu 22.04 Bluetooth doesn't even shot up in the dropdown menu in the taskbar. It is still present in the settings but can't turn on due to no adapter recognized -- 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/1947162 Title: Bluetooth does not work on ASUS ROG Strix G15 Advantage Edition G513 laptop on Ubuntu 21.10 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth does not work on ASUS ROG Strix G15 Advantage Edition G513 laptop on Ubuntu 21.10. Bluetooth is visible on the settings menu, but turning Bluetooth on does work. It still shows as "Bluetooth Off". ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-19-generic 5.13.0-19.19 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu70 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: sami 1862 F pulseaudio /dev/snd/controlC1: sami 1862 F pulseaudio /dev/snd/controlC0: sami 1862 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 14 16:43:43 2021 InstallationDate: Installed on 2021-10-12 (1 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Daily amd64 (20211010) MachineType: ASUSTeK COMPUTER INC. ROG Strix G513QY_G513QY ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-19-generic root=UUID=ff964c9b-ce92-4334-8759-9d785a262c60 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-19-generic N/A linux-backports-modules-5.13.0-19-generic N/A linux-firmware 1.201 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2021 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: G513QY.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: G513QY dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 0.68 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrG513QY.306:bd05/07/2021:br5.19:efr0.68:svnASUSTeKCOMPUTERINC.:pnROGStrixG513QY_G513QY:pvr1.0:sku:rvnASUSTeKCOMPUTERINC.:rnG513QY:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: ROG Strix dmi.product.name: ROG Strix G513QY_G513QY dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1947162/+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 1953264] Re: Ubuntu 21.10 Bluetooth adapter not detected
Same problem with Asus ROG G713R and Ubuntu 22.04.1 ** Changed in: linux (Ubuntu) Status: Expired => 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/1953264 Title: Ubuntu 21.10 Bluetooth adapter not detected Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapter not detected on machine running Ubuntu 21.10 with ASUS ROG B550-F. Upon clicking taskbar, bluetooth is shown as OFF. Expanding the bluetooth menu in the taskbar shows the option to turn OFF bluetooth. Going into the bluetooth settings, it says "No bluetooth found. Plugin a dongle to use bluetooth." ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-21-generic 5.13.0-21.21 ProcVersionSignature: Ubuntu 5.13.0-21.21-generic 5.13.18 Uname: Linux 5.13.0-21-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nabeel 2239 F pulseaudio /dev/snd/pcmC1D1p: nabeel 2239 F...m pulseaudio /dev/snd/controlC0: nabeel 2239 F pulseaudio CasperMD5CheckResult: pass Date: Sun Dec 5 23:38:54 2021 InstallationDate: Installed on 2021-09-06 (90 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: ASUS System Product Name ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-21-generic root=/dev/mapper/vgubuntu-root ro quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-21-generic N/A linux-backports-modules-5.13.0-21-generic N/A linux-firmware 1.201.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-15 (51 days ago) dmi.bios.date: 08/10/2021 dmi.bios.release: 5.17 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2423 dmi.board.asset.tag: Default string dmi.board.name: ROG STRIX B550-F GAMING (WI-FI) dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2423:bd08/10/2021:br5.17:svnASUS:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGSTRIXB550-FGAMING(WI-FI):rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: ASUS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1953264/+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 1987269] Re: [5.18.0 mainline] mlx5 deadlock
** Attachment added: "The issue also occurs on the 5.15.0-48.54 kernel currently in -proposed" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987269/+attachment/5613800/+files/apport-bug-1987269.txt -- 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/1987269 Title: [5.18.0 mainline] mlx5 deadlock Status in linux package in Ubuntu: Incomplete Bug description: $ lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04.1 LTS Release: 22.04 Codename: jammy $ uname -a Linux pc1-rb3-n3 5.18.0-051800-generic #202205222030 SMP PREEMPT_DYNAMIC Sun May 22 20:33:46 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.735461] INFO: task ovn-controller:30439 blocked for more than 120 seconds. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.742835] Not tainted 5.18.0-051800-generic #202205222030 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.749051] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757010] task:ovn-controller state:D stack:0 pid:30439 ppid: 1 flags:0x0002 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757019] Call Trace: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757024] Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757031] __schedule+0x246/0x5c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757045] schedule+0x55/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757050] schedule_preempt_disabled+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757057] __mutex_lock.constprop.0+0x2f3/0x4c0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757064] __mutex_lock_slowpath+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757069] mutex_lock+0x35/0x40 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757073] rtnetlink_rcv_msg+0x114/0x3f0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757082] ? rtnl_calcit.isra.0+0x140/0x140 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757087] netlink_rcv_skb+0x56/0x100 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757095] rtnetlink_rcv+0x15/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757099] netlink_unicast+0x236/0x350 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757104] netlink_sendmsg+0x25e/0x4d0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757109] sock_sendmsg+0x66/0x70 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757117] sys_sendmsg+0x24f/0x290 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757123] ? import_iovec+0x1b/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757130] ? sendmsg_copy_msghdr+0x7c/0xa0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757137] ___sys_sendmsg+0x81/0xc0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757143] ? ___sys_recvmsg+0x99/0x110 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757148] ? netdev_name_node_lookup_rcu+0x6b/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757155] ? fput+0x13/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757161] ? __sys_sendmsg+0x98/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757166] ? __fget_light+0xa7/0x130 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757174] __sys_sendmsg+0x62/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757180] __x64_sys_sendmsg+0x1d/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757186] do_syscall_64+0x5c/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757191] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757194] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757200] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757203] ? exit_to_user_mode_prepare+0x37/0xb0 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757210] ? syscall_exit_to_user_mode+0x26/0x50 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757214] ? __x64_sys_write+0x19/0x20 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757220] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757224] ? do_syscall_64+0x69/0x80 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757227] entry_SYSCALL_64_after_hwframe+0x44/0xae Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757232] RIP: 0033:0x7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757239] RSP: 002b:7ffd50fa8ec0 EFLAGS: 0293 ORIG_RAX: 002e Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757246] RAX: ffda RBX: 0001 RCX: 7f571f927b4d Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757252] RDX: RSI: 7ffd50fa8f50 RDI: 0020 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757255] RBP: 7ffd50fa9c40 R08: R09: 55e1a6a66f60 Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757260] R10: 0001 R11: 0293 R12: Aug 22 01:15:02 pc1-rb3-n3 kernel: [200712.757264] R13: 55e1a53bc510 R14:
[Kernel-packages] [Bug 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
I'm closing this, since it's a feature request. Please add a Jira card for it in the product feedback board. ** Changed in: maas Status: New => Invalid -- 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/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: Invalid Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+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 1922910] Re: Unable to deploy HWE kernel with sub-arch set to xgene-uboot
It's not a simple as allowing xgene-uboot for HWE kernels in the MAAS code. If we'd do that, you'd end up with basically a generic subarchitecture. We'd need to change the streams. Currently we overload subarchitecture a bit, so most likely we'd need to add new entries for xgene-uboot+hwe. But that also probably wouldn't be enough, we'd also have to change the MAAS code to cope with the new arhitecture/hwe combination. So to sum it up, this is not a bug, since it was designed to work this way. If we want to add this, we'd need to get it on the roadmap and prioritized, since it's a significant amount of work. ** Changed in: maas Assignee: Björn Tillenius (bjornt) => (unassigned) -- 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/1922910 Title: Unable to deploy HWE kernel with sub-arch set to xgene-uboot Status in MAAS: Invalid Status in linux package in Ubuntu: Expired Bug description: When trying to deploy Moonshot nodes, the sub-arch must be set to xgene-uboot for it to be deployed with GA kernel. However, when trying to deploy it with the HWE kernel it will complain that: Subarchitecture(xgene-uboot) must be generic when setting hwe_kernel. [ deleted the bit about how generic/hwe fails, because that is expected. this machine requires xgene-uboot/hwe ] To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1922910/+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 1987711] Re: [i915] Ubuntu display get shifted after some time.
Hi, I tried new kernel (by link above) with xorg, and pc runs around week and yet no shifting occurred. I also tried on another pc (same hw configuration) (under wayland) use command: MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 and shifting occurred. I think I will give it another week, to see if the shifting occurs on xorg. Question: drm-tip isn't actual kernel version, so if i want to try older but more tested kernel, I have to pick one of older releases? Or this kernel is just fine to use? -- 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/1987711 Title: [i915] Ubuntu display get shifted after some time. Status in linux package in Ubuntu: Incomplete Bug description: It is continuation of this bug: https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1986583 where advised fix was applied. Summay: After ubuntu is turned on, after some time screen gets shifted to side. (and starts to overlap) I setup webcamera to record screen, and video below shows what it looked like. after fix were applied. www.ms.mff.cuni.cz/~krasicei/capture-0231.bug.crop.slow.mp4 (video was cropped, and slowed down 2x) before fix was applied shift looked somehow like this: www.ms.mff.cuni.cz/~krasicei/bug17-50-18-8-2022.c.mp4 (video is also cropped, and slowed down 2x) During shift no one was present on computer. Is there any idea how to enable some more detailed log or something? I probably can pinpoint exact moment in time when shift happened. i tried to read log journalctl, but I found nothing interesting. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xorg 1:7.7+23ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-46.49-generic 5.15.39 Uname: Linux 5.15.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 BootLog: CasperMD5CheckResult: unknown Date: Fri Aug 26 02:31:10 2022 DistUpgraded: 2022-08-02 14:36:41,704 DEBUG Running PostInstallScript: '/usr/lib/ubuntu-advantage/upgrade_lts_contract.py' DistroCodename: jammy DistroVariant: ubuntu ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:1916] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Skylake GT2 [HD Graphics 520] [8086:2015] InstallationDate: Installed on 2022-02-17 (189 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 222a:0001 ILI Technology Corp. Multi-Touch Screen Bus 001 Device 002: ID 1a2c:2d23 China Resource Semico Co., Ltd Keyboard Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Default string Default string ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-46-generic root=UUID=582fb3cc-8ef6-460b-b9ae-a16f81c604a7 ro quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: Upgraded to jammy on 2022-08-02 (23 days ago) dmi.bios.date: 10/07/2021 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GSKU0504.V54 dmi.board.asset.tag: Default string dmi.board.name: SKYBAY dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGSKU0504.V54:bd10/07/2021:br5.12:svnDefaultstring:pnDefaultstring:pvrDefaultstring:rvnDefaultstring:rnSKYBAY:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: Default string dmi.product.name: Default string dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.110-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 22.0.5-0ubuntu0.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:21.1.3-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987711/+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 1987287] Re: [UBUNTU 20.04] mlx5 driver crashes on accessing device attributes during recovery
Many thx, Niklas!
--
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/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on accessing device attributes
during recovery
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification:
--
[Impact]
* If the mlx5 driver is reloading while the recovery flow is happening,
and if it receives new commands before the command interface is up
again, this can lead to null pointer that tries to access non-
initialized command structures.
* So it's required to avoid processing commands before the command
interface is up again.
* This is accomplished by a new cmdif state that helps to avoid
processing commands while cmdif is not ready.
[Fix]
* backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca
"net/mlx5: Avoid processing commands before cmdif is ready"
[Test Plan]
* An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation
is needed that has Mellanox cards (RoCE Express 2.1) assigned,
configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4).
* Now trigger a recovery (guess that can be done at the Support Element)
and reload the driver at the same time.
* Make sure the module/driver mlx5 is loaded and in use
(otherwise it can't be removed/unloaded).
* Now remove/unload the module with:
sudo modprobe -r mlx5
and (re-)load it again with:
sudo modprobe mlx5
* Due to the lack of RoCE Express 2.1 hardware,
IBM needs to do the verification.
[Where problems could occur]
* In case there is an issue with 'cmdif' it might not have the correct
interface state, which:
- either might lead to the fact that commands are not properly blocked
and the situation is similar like before
- or the commands may get always blocked,
which render the hardware useless
- or might block in wrong situation,
which will cause unexpected issues and broken behavior.
* Since the patch got upstream accepted with v5.7-rc7 it's
not new to the kernel, was already part of groovy (and above)
and is therefor already in use by newer Ubuntu releases.
[Other Info]
* Since the patch is upstream since v5.7-rc7,
it's already included in jammy and kinetic.
* Since the upstream patch incl. the line:
Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox
Connect-IB adapters") it looks to me that it was forgotten
to mark the patch for upstream stable updates.
* Such SRUs for focal's 5.4 will automatically land in bionic's
hwe-5.4, too. But since this was especially requested for
bionic's hwe-5.4, I wanted to mention this here.
__
We recently got a bug report for systems running Ubuntu 20.04 that were
crashing with backtraces pointing at the mlx5 driver's handling of
mlx5_ethtool_get_link_ksettings()
when this is called through the sysfs (going through ethtool might have
different checks).
I managed to find a reliable way to reproduce the issue that I believe isn't
tied to IBM Z at all.
The procedure to reproduce is as follows. I created a script to read
the sysfs attributes for the link's speed and duplex mode in a loop:
#!/usr/bin/env bash
if [ $# -lt 1 ]; then
echo "Usage: $0 "
exit 1
fi
while true; do
cat /sys/class/net/$1/duplex > /dev/null
cat /sys/class/net/$1/speed > /dev/null
done
Executed with:
# ./script.sh enP10p0s0
I ran this in one bash session and then in another one I triggered a PCI
reset with
the follwoing command where one needs to replace with the PCI address
of the NIC:
echo 1 > /sys/bus/pci/devices//reset
Then first I got a lot of the following messages:
mlx5_core 0010:00:00.0 enP16p0s0: mlx5e_ethtool_get_link_ksettings:
query port ptys failed: -5
And then as the mlx5 driver's recovery kicks in the oops as below:
[ 659.103947] mlx5_core 0010:00:00.0: wait vital counter value 0x7b399f
after 1 iterations
[ 659.103947] mlx5_core 0010:00:00.0: mlx5_pci_resume was called
[ 659.103966] mlx5_core 0010:00:00.0: firmware version: 14.32.1010
[ 659.104169] Unable to handle kernel pointer dereference in virtual kernel
address space
[ 659.104171] Failing address: TEID: 0483
[ 659.104172] Fault in home space mode while using kernel ASCE.
[ 659.104173] AS:3d29c007 R3:fffd0007 S:fffd5800
P:003d
[ 659.104200] Oops: 0004 ilc:2 [#1] SMP
[ 659.104202] Modules linked in: s390_trng ism smc pnet chsc_sch eadm_sch
vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio sch_fq_codel drm
drm_panel_orientation_quirks i2c_core ip_tables
[Kernel-packages] [Bug 1987287] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2022-09-05 08:55 EDT---
(In reply to comment #16)
> Hello 'nafeiy', we indeed wanted to pick this up in the next days.
> Just notice that this is a development bug, opened at the Launchpad bug
> tracking system, that is mainly used for development.
>
> We will usually produce a patched 20.04/focal/5.4 test kernel, that we make
> a available via a so called PPA (a special repository).
> It will take then some steps in our SRU cycle until this patched kernel gets
> released.
> These are the upcoming kernel Service Release Cycles (SRUs):
> https://kernel.ubuntu.com/
>
> This 5.4 kernel will then be migrated by our kernel team to
> 18.04/bionic/hwe-5.4.
> But in this case we may also create a dedicated hwe-5.4 test kernel for
> bionic for you, to save you some time.
>
> The process for hotfixes is a different.
Hi Frank, I tested the provided PPA kernel "5.4.0-126-generic
#142~lp1987287-Ubuntu" with the reset while reading duplex/speed test from the
original report.
It worked as expected no crash and a clean recovery. Thanks!
--
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/1987287
Title:
[UBUNTU 20.04] mlx5 driver crashes on accessing device attributes
during recovery
Status in Ubuntu on IBM z Systems:
In Progress
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification:
--
[Impact]
* If the mlx5 driver is reloading while the recovery flow is happening,
and if it receives new commands before the command interface is up
again, this can lead to null pointer that tries to access non-
initialized command structures.
* So it's required to avoid processing commands before the command
interface is up again.
* This is accomplished by a new cmdif state that helps to avoid
processing commands while cmdif is not ready.
[Fix]
* backport of f7936ddd35d8 f7936ddd35d8b849daf0372770c7c9dbe7910fca
"net/mlx5: Avoid processing commands before cmdif is ready"
[Test Plan]
* An Ubuntu Server for s390x 18.04 or 20.04 LPAR or z/VM installation
is needed that has Mellanox cards (RoCE Express 2.1) assigned,
configured and enabled and that runs a 5.4 kernel (on bionic hwe-5.4).
* Now trigger a recovery (guess that can be done at the Support Element)
and reload the driver at the same time.
* Make sure the module/driver mlx5 is loaded and in use
(otherwise it can't be removed/unloaded).
* Now remove/unload the module with:
sudo modprobe -r mlx5
and (re-)load it again with:
sudo modprobe mlx5
* Due to the lack of RoCE Express 2.1 hardware,
IBM needs to do the verification.
[Where problems could occur]
* In case there is an issue with 'cmdif' it might not have the correct
interface state, which:
- either might lead to the fact that commands are not properly blocked
and the situation is similar like before
- or the commands may get always blocked,
which render the hardware useless
- or might block in wrong situation,
which will cause unexpected issues and broken behavior.
* Since the patch got upstream accepted with v5.7-rc7 it's
not new to the kernel, was already part of groovy (and above)
and is therefor already in use by newer Ubuntu releases.
[Other Info]
* Since the patch is upstream since v5.7-rc7,
it's already included in jammy and kinetic.
* Since the upstream patch incl. the line:
Fixes: e126ba97dba9 ("mlx5: Add driver for Mellanox
Connect-IB adapters") it looks to me that it was forgotten
to mark the patch for upstream stable updates.
* Such SRUs for focal's 5.4 will automatically land in bionic's
hwe-5.4, too. But since this was especially requested for
bionic's hwe-5.4, I wanted to mention this here.
__
We recently got a bug report for systems running Ubuntu 20.04 that were
crashing with backtraces pointing at the mlx5 driver's handling of
mlx5_ethtool_get_link_ksettings()
when this is called through the sysfs (going through ethtool might have
different checks).
I managed to find a reliable way to reproduce the issue that I believe isn't
tied to IBM Z at all.
The procedure to reproduce is as follows. I created a script to read
the sysfs attributes for the link's speed and duplex mode in a loop:
#!/usr/bin/env bash
if [ $# -lt 1 ]; then
echo "Usage: $0 "
exit 1
fi
while true; do
cat /sys/class/net/$1/duplex > /dev/null
cat /sys/class/net/$1/speed > /dev/null
done
Executed with:
# ./script.sh enP10p0s0
I ran this in one bash session and then in another one I triggered a PCI
reset with
the follwoing command where one needs to replace with the PCI address
of the
[Kernel-packages] [Bug 1973434] Re: massive performance issues since 22.04 upgrade
I'm also still facing the issue with an 16GB HP laptop. Did a fresh install on the SSD and when I open edge and chrome together it consumes a lot of RAM. -- 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/1973434 Title: massive performance issues since 22.04 upgrade Status in linux package in Ubuntu: Confirmed Bug description: Hi, After upgrading to 22.04 i had to fight with massive performance issues. Browsers appeared to hang every other minute, youtube videos being laggy and hang in between, applications in a virtualbox VM where slow and also hanging every other minute to a level of not being useable. On a pretty recent and powerful system just 2 years old. I noticed CPU jumps in top, but also somehow thought it could be a graphics issue so invested some time installing nvidia drivers properly. Also I wondered if it might be the lowlatency kernel I normally use because I do audio stuff, and switched to generic. But nothing helped. ThenI had the idea it could be a kernel/scheduler issue because the system wasn't always slow, but it appeared certain things kept hanging when other processed had a lot of cpu for a few seconds. So I got a recent mainline kernel, configured it with my last running config from 21.10 before the update, made the debs and installed them, and now can tell that a mainline kernel 5.17.7 with all the dkms modules that i had before which got compiled automatically at installation brings back a "normal" performance. I can browse the web, run multiple youtube vids at once, even in another browser, have thunderbird running, and a virtualbox machine open with another browser for some web app testing and everything runs fine and smooth, no lagging. Not sure yet what the real reason is - either the kernel version, or a patch in the ubuntu version, or the 22.04 kernel config so far, or some configuration made in 21.10 that isn't good with 22.04 and it's kernel anymore. I will go ahead tomorrow and see if I can build a vanilla kernel with the config from the ubuntu 22.04 kernel and "make oldconfig", then I will be able to tell if only the config is making the difference. Please let me know of there is anything I should test to further analyze this issue, or any ideas I can try to solve it without having to run a mainline manually installed kernel. Thanks. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-generic 5.15.0.30.33 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: henning6198 F pulseaudio /dev/snd/controlC1: henning6198 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat May 14 23:02:38 2022 InstallationDate: Installed on 2020-04-12 (761 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20QV00CEGE ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-30-generic root=/dev/mapper/vgubuntu-root ro RelatedPackageVersions: linux-restricted-modules-5.15.0-30-generic N/A linux-backports-modules-5.15.0-30-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-28 (15 days ago) dmi.bios.date: 12/06/2021 dmi.bios.release: 1.42 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET55W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QV00CEGE dmi.board.vendor: LENOVO dmi.board.version: SDK0T08861 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.23 dmi.modalias: dmi:bvnLENOVO:bvrN2OET55W(1.42):bd12/06/2021:br1.42:efr1.23:svnLENOVO:pn20QV00CEGE:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00CEGE:rvrSDK0T08861WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd: dmi.product.family: ThinkPad X1 Extreme 2nd dmi.product.name: 20QV00CEGE dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd dmi.product.version: ThinkPad X1 Extreme 2nd dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973434/+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 1932124] Re: Add WWAN framework and drivers support
** Changed in: hwe-next Assignee: (unassigned) => Jian Hui Lee (jianhuilee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel in Ubuntu. https://bugs.launchpad.net/bugs/1932124 Title: Add WWAN framework and drivers support Status in HWE Next: New Status in linux-intel package in Ubuntu: Fix Committed Bug description: [SRU Justification] [Impact] The Quectel SDX24 EM160R-GL 4G LTE CAT16 PCIE Modem and Foxconn SDX55 T99W175 5G sub6 PCIE Modem are not supported in 5.11 kernel yet. The new WWAN framework and driver support are required to be backported to detect and control the new WWAN modules. [Fix] Backport the WWAN framework and drivers support from mainline kernel 5.13. [Test Case] Verify whether the Quectel/Foxconn WWAN module are detected or not. And use either `mmcli` commands or NetworkSettings Panel to test the connection. [Where problem could occur] Since the WWAN framework is totally new which makes use of the existing MHI bus drivers and protocols, it should be compatible with old WWAN modules. The regression can be considered as low. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1932124/+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 1939638] Re: [regression] USB device is not detected during boot
** Changed in: linux-intel (Ubuntu)
Status: Confirmed => Invalid
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-intel-5.13 in Ubuntu.
https://bugs.launchpad.net/bugs/1939638
Title:
[regression] USB device is not detected during boot
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-intel package in Ubuntu:
Invalid
Status in linux-intel-5.13 package in Ubuntu:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-intel source package in Focal:
Confirmed
Status in linux-intel-5.13 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-intel source package in Hirsute:
Invalid
Status in linux-intel-5.13 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
The USB devices (keyboard, storage...) are failed to be detected when
connecting to the problematic root hubs which need longer PowerOn-to-PowerGood
delay than it claims in the hub descriptor. It's caused by the upstream fix
90d28fb53d4a ("usb: core: reduce power-on-good delay time of root hub").
[Fix]
Reverting the upstream fix until a formal fix been placed.
[Test Case]
1. Plug the USB device to the ports of problematic root hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Regression Potential]
Low. The longer delay is proven safe in old kernels.
== Original Bug Description ==
[Summary]
The USB devices (keyboard, storage...) are failed to be detected during boot
after upgrade to UBUNTU focal kernel 5.4.0-78 and hirsute 5.11.0-26. However,
they will be detected and working ok after re-plugging. The kernel output shows
as down below during boot
[ 39.350435] hub 1-0:1.0: USB hub found
[ 39.398835] hub 1-0:1.0: 12 ports detected
[ 39.622744] usb usb1-port3: couldn't allocate usb_device
And when I plug out then plug in the same device, it shows
[57210.794140] usb 1-3: new low-speed USB device number 4 using xhci_hcd
[57210.951289] usb 1-3: New USB device found, idVendor=17ef, idProduct=6099,
bcdDevice= 1.14
[57210.951293] usb 1-3: New USB device strings: Mfr=1, Product=2,
SerialNumber=0
After doing kernel bisecting, we found the upstream commit
https://github.com/torvalds/linux/commit/90d28fb53d4a51299ff324dede015d5cb11b88a2
makes the difference. It indicates that the delay for the root hub from
power_on to power_good is not long enough. There was no problem if the delay is
100 ms. From the Hub Descriptor of the root hub, the value is 10 * 2
milliseconds. And the XHCI spec also says in section 5.4.8
"""
The host is required to have power stable to the port within 20 milliseconds
of the '0' to '1' transition of PP. If PPC = '1', software is responsible for
waiting 20ms.
"""
The commit seems to follow the SPEC but could cause problems on some
hubs.
[Reproduce Steps]
1. Plug the USB device to the physical port #1 and #4 which belongs to
high-speed hub.
2. Power on the machine.
3. Check if the USB device can work or not after boot.
[Results]
Expected:
All usb devices connect to the hub should work OK.
Actual:
USB devices connects to high-speed hub can not be probed.
[Additional Information]
Kernel Version: focal 5.4.0-78 and hirsute 5.11.0-26
[Upstream bug]
https://bugzilla.kernel.org/show_bug.cgi?id=214021
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1939638/+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 1907200] Re: rtwpci driver blocks the system to enter PC10, stuck at PC3
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1907200 Title: rtwpci driver blocks the system to enter PC10, stuck at PC3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] The deepest CPU package C-state is PC3 after rtwpci module is loaded. [Fix] The fix is from Realtek. They will upstream this fix with some other fixes later. [Test] Verified on RTL8723DE [10ec:d723] wifi card, and it enters PC10 during long idle. [Where problems could occur] The fix is pretty simple and small, and just increases the idle/active latency value. Nothing could went wrong in this case. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1907200/+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 1907466] Re: Fix unusable touchpad on TGL laptops
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1907466 Title: Fix unusable touchpad on TGL laptops Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: [Impact] Touchpad doesn't work after boot. kernel: i2c_designware i2c_designware.1: controller timed out [Fix] "Actually disable Tx and Rx buffers on GPIO request". [Test] Bootup a TGL laptop. Touchpad doesn't work. With the fix applied, touchpad always work after boot. [Where problems could occur] Intel pinctrl can change between GPIO mode or IRQ mode, both effect many other devices. So problems can happen all across the board. However, the regression happens in v5.9, so no user really received the change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1907466/+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 1918228] Re: Fix missing HDMI/DP audio on NVidia card after S3
** Changed in: hwe-next Status: New => 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/1918228 Title: Fix missing HDMI/DP audio on NVidia card after S3 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] NVidia DP/HDMI aduio disappears after S3. This is a regression introduced by LP: #1867704. [Fix] Update ELD properly so jack status is correctly reported. [Test] Perform S3 and open Sound Settings. With the fix applied, the DP/HDMI audio is always present after S3. [Where problems could occur] This series changes how ELD gets update. So if device depends on the original behavior, jack status could be wrong after this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1918228/+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 1917843] Re: drm/i915: Drop force_probe requirement for JSL
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1917843
Title:
drm/i915: Drop force_probe requirement for JSL
Status in HWE Next:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Bug description:
[SRU Justification]
[Impact]
JSL i915 PCI ID has been in 5.10 in commit 651cc835d5f6 ("drm/i915: Add
new EHL/JSL PCI ids"), but it is still marked require_force_probe in
commit 24ea098b7c0d ("drm/i915/jsl: Split EHL/JSL platform info and PCI
ids"), and that's still the case in current drm-intel/drm-intel-next
HEAD. Therefore early phase board for assessment board takes an extra
i915.force_probe=4e71 boot parameter to enable i915.
[Fix]
Intel should remove this flag sometime later when JSL drm is stable
enough. But before that, we can simply remove that flag from jsl_info in
drivers/gpu/drm/i915/i915_pci.c.
[Test Case]
i915 should be loaded with patched kernel, so do:
$ lsmod|grep i915
i915
[Where problems could occur]
While this is still an alpha platform in development in OEM projects,
this should not introduce trouble for others. As for JSL, troubles are
expected and to be resolved.
== original bug description ==
JSL i915 PCI ID has been in 5.10 in commit 651cc835d5f6 ("drm/i915:
Add new EHL/JSL PCI ids"), but it is still marked require_force_probe
in commit 24ea098b7c0d ("drm/i915/jsl: Split EHL/JSL platform info and
PCI ids"), and that's still the case in current drm-intel/drm-intel-
next HEAD.
We need drop this requirement from this kernel so that machines being
tested don't need to work around it locally.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1917843/+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 1908366] Re: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1908366 Title: Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Bug description: [SRU Justification] [Impact] It shows the firmware is missing, and runtime power management has been disabled. [ 1.884400] i915 :00:02.0: vgaarb: deactivate vga console [ 1.887078] i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem [ 1.887161] i915 :00:02.0: Direct firmware load for i915/tgl_dmc_ver2_08.bin failed with error -2 [ 1.887164] i915 :00:02.0: [drm] Failed to load DMC firmware i915/tgl_dmc_ver2_08.bin. Disabling runtime power management. [ 1.887165] i915 :00:02.0: [drm] DMC firmware homepage: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 [Fix] cherry picked from linux-firmware bdf8d7a8 i915: Add DMC firmware 2.08 for TGL BTW, groovy has this commit already. [Test] Verified on Dell's machine [Where problems could occur] It's a new firmware for new GPU, not possible to introduce regressions. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908366/+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 1908335] Re: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1908335 Title: [SRU][F/G/H/U/OEM-5.6] Fix i2c report error on elan trackpoint Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Fix Released Status in linux-oem-5.6 source package in Hirsute: Invalid Bug description: [Impact] New elan trackpoint on elan_i2c reports the following error: "failed to read report data: -71" it failed to work. [Fix] Add new report type support and fix protocol errors for some trackpoints in SMBus mode. [Test Case] Touchpad and trackpoint work well. Verified on 3 other models of ThinkPads with elan touchpad loaded. All good. [Where problems could occur] elan touchpad and trackpoint may not work. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908335/+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 1908713] Re: Fix suspend error of SOF driver
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1908713 Title: Fix suspend error of SOF driver Status in HWE Next: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] SOF driver in oem-5.6 kernel tries to access HDA codec register when the codec is already suspended. This may freeze suspend. [Fix] Revert HDA codec PM direct-complete optimization. The same suspend optimization works perfectly on 5.8 and 5.10 kernel, so something's wrong in the SOF driver in oem-5.6. However, SOF in oem-5.6 is in Frankenstein state so we better not touch it. [Test] Suspend a laptop with SOF driver, it can take 30 seconds to suspend, or worse, it freezes. With the patch applied, it can suspend in 1 second. [Regression Risk] For HDA codecs that benefit from this PM optimization, it'll take longer to suspend and resume. Nothing else changes other than that. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1908713/+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 1917829] Re: alsa/hda: the hdmi audio dosn't work on TGL machines
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1917829 Title: alsa/hda: the hdmi audio dosn't work on TGL machines Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] On the TGL machines, we plug a dp mst hub to the thunderbolt port, and plug a hdmi/dp monitor to the dp mst hub, then check the gnome-sound-setting, could not find the hdmi/dp audio device. [Fix] backport a patch from upstream, this patch change to assign the pcm slot dynamically on TGL macines. [Test] On 2 lenovo and dell TGL machines, plug dp mst hub and plug 2 monitors to the hub or to the machine hdmi/dp ports, check the gnome-sound-setting, there are 2 hdmi/dp audio devices. and they all could output sound. [Where problems could occur] After this change, the hdmi audio device number starts from 0, 1, ..., while without this change, the hdmi audio device number is fix mapped, it could be 3 or 5 directly. So if there is some userspace applications depends on the fix mapped hdmi audio device, these applicatons could not work on TGL machines. So far, we don't know if those applications exists or not, but I could confirm the ubuntu audio stack builds on the alsa-lib and pulseaudio, this change will not affect the applications based on the alsa-lib and pulseaudio. And I already tested audio functions under ubuntu on the TGL machines, there is no regression. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917829/+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 1916554] Re: Cirrus Audio Codec CS8409/CS42L42 support
** Changed in: linux (Ubuntu Focal) Status: Confirmed => Won't Fix ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1916554 Title: Cirrus Audio Codec CS8409/CS42L42 support Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] No driver for Cirrus CS8409 HDA bridge/CS42L42 codec, no playback/capture device available. [Fix] Patchset https://lore.kernel.org/alsa-devel/20210306111934.4832-1-vita...@opensource.cirrus.com/ currently in https://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound.git branch for-next. [Test Case] On platform with Cirrus CS8409 HDA bridge: /sys/class/sound/card0/device/$ cat hdaudioC0D0/vendor_* 0x10138409 Cirrus Logic /sys/class/sound/card0/device/$ cat hdaudioC0D0/chip_name Generic Its chip_name should be updated with correct model name and sound system should be working: /sys/class/sound/card0/device/$ cat hdaudioC0D0/chip_name CS8409/CS42L42 APLAY and ARECORD should also list new audio devices: List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CS8409/CS42L42 Analog [CS8409/CS42L42 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 List of CAPTURE Hardware Devices card 0: PCH [HDA Intel PCH], device 0: CS8409/CS42L42 Analog [CS8409/CS42L42 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 [Where problems could occur] New device driver landing, may bring in new issues bound to new driver/device configuration such as suspend/resume issues. == original bug description == $ sudo dmesg|grep hda [ 19.253994] snd_hda_intel :00:1f.3: enabling device ( -> 0002) [ 19.254515] snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [ 19.317386] snd_hda_codec_generic hdaudioC0D0: autoconfig for Generic: line_outs=1 (0x2c/0x0/0x0/0x0/0x0) type:speaker [ 19.317390] snd_hda_codec_generic hdaudioC0D0:speaker_outs=0 (0x0/0x0/0x0/0x0/0x0) [ 19.317392] snd_hda_codec_generic hdaudioC0D0:hp_outs=1 (0x24/0x0/0x0/0x0/0x0) [ 19.317393] snd_hda_codec_generic hdaudioC0D0:mono: mono_out=0x0 [ 19.317395] snd_hda_codec_generic hdaudioC0D0:inputs: [ 19.317397] snd_hda_codec_generic hdaudioC0D0: Internal Mic=0x44 [ 19.317399] snd_hda_codec_generic hdaudioC0D0: Mic=0x34 Vendor driver in progress: https://github.com/CirrusLogic/product-support/tree/cs8409_hda Upstream submission: https://patchwork.kernel.org/project/alsa-devel/list/?series=441331 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.10.0-1013-oem 5.10.0-1013.14 ProcVersionSignature: Ubuntu 5.10.0-1013.14-oem 5.10.6 Uname: Linux 5.10.0-1013-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip Date: Mon Feb 22 22:13:32 2021 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-beric-icl+X44 InstallationDate: Installed on 2021-02-04 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oem-5.10 UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1673 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85+fossa-beric-icl+X44 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-04 (18 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation
[Kernel-packages] [Bug 1916467] Re: [Intel Maple Ridge] system cannot enter S3 the first time while connecting to TBT4 storage
** Changed in: hwe-next
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1916467
Title:
[Intel Maple Ridge] system cannot enter S3 the first time while
connecting to TBT4 storage
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Won't Fix
Status in linux-oem-5.10 source package in Focal:
Fix Released
Status in linux source package in Hirsute:
Fix Released
Status in linux-oem-5.10 source package in Hirsute:
Invalid
Bug description:
[SRU Justification]
[Impact]
Systems with Intel Maple Ridge addon card with tbt devices attached may
fail to suspend/resume.
[Fix]
Commit 319696aa80 ("xhci: Fix repeated xhci wake after suspend due to
uncleared internal wake state") currently landed in
https://git.kernel.org/pub/scm/linux/kernel/git/mnyman/xhci.git branch
for-usb-linus.
[Test Case]
When booted from unpatched kernel, starting from oem-5.10 that has
received Intel Maple Ridge enablement fixes, XHCI port on Maple Ridge
card may wake itself unsolicitedly when performing runtime/deep suspend:
kernel: [326] pci_pme_active:2422: xhci_hcd :37:00.0: PME# disabled
kernel: [326] __pci_set_master:4219: xhci_hcd :37:00.0: enabling bus
mastering
kernel: [326] pci_save_state:1553: xhci_hcd :37:00.0: saving config
space at offset 0x0 (reading 0x11388086)
...
kernel: [326] pci_pme_active:2422: xhci_hcd :37:00.0: PME# enabled
The suspend resume process will stuck forever.
[Where problems could occur]
Tried on a few more platforms, didn't found possible regression.
== original bug description ==
[Reproduce Steps]
1. install TBT4 card
2. Boot into Ubuntu X68
3. suspend and wake up to confirm S3 function
3. Connect TBT storage
4. suspend
5. system cannot enter S3
[Results]
Expected Result: system enters suspend
Actual Result: 1st attempt fails, screen will be turned off but power & fan
won't. system can only enter s3 afterwards
Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=211377
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1916467/+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 1917842] Re: Fix Lenovo ThinkStation P620 rear audio
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1917842 Title: Fix Lenovo ThinkStation P620 rear audio Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Won't Fix Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: [Impact] Rear audio on Lenovo ThinkStation P620 stops working on newer kernel. [Fix] Use helper to the correct way to disable USB autosuspend. [Test] With the patch applied, the rear audio on Lenovo ThinkStation P620 works again. [Where problems could occur] In a rather unlikely case, if any USB audio wrongly shared same device ID with P620' USB audios, this patch will disable autosuspend on it. However, it won't bring any functional impact. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1917842/+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 1919123] Re: Dell Precision 5550 takes up to 10 seconds to respond when coming out of sleep
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1919123 Title: Dell Precision 5550 takes up to 10 seconds to respond when coming out of sleep Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Released Bug description: [Impact] On some platforms, the EC doesn't support the register reading sequence for sentelic[1], and then make the EC can't respond commands for a while when probing. It leads to the keyboard is non-responsive for around 10 seconds while waking up from s2idle. [ 44.304488] i8042: [9804] d4 -> i8042 (command) [ 44.304634] i8042: [9804] f3 -> i8042 (parameter) [ 44.304787] i8042: [9804] fa <- i8042 (interrupt, 1, 12) [ 44.304855] i8042: [9804] d4 -> i8042 (command) [ 44.304938] i8042: [9804] 66 -> i8042 (parameter) [ 44.337698] i8042: [9813] d4 -> i8042 (command) [ 44.905695] i8042: [9942] 88 -> i8042 (parameter) [ 45.497478] i8042: [10102] d4 -> i8042 (command) [ 46.098041] i8042: [10253] f3 -> i8042 (parameter) [ 46.098070] i8042: [10253] fe <- i8042 (interrupt, 1, 12) [ 46.718154] i8042: [10386] d4 -> i8042 (command) [ 47.309915] i8042: [10386] f4 -> i8042 (parameter) [ 47.918961] i8042: [10556] d4 -> i8042 (command) [ 48.402624] i8042: [10556] f6 -> i8042 (parameter) [Fix] A DMI quirk to mark this platform doesn't have aux device could avoid those commands to be sent. And the system could still using i2c interface to communicate with the touchpad. https://lkml.org/lkml/2021/3/15/126 [Test] Verified on Dell Precision 5550 [Where problem could occur] The quirk only affects the listed platform, there is no regression could occur. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919123/+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 1919952] Re: micmute led init state is not correct on a lenovo machine
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1919952 Title: micmute led init state is not correct on a lenovo machine Status in HWE Next: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: Since this patch cced to stable and only oem project needs this fix urgently, only send the sru to oem-5.10 kernel, other ubuntu kernels will merge this patch with stable update. [Impact] On a lenovo machine, the micmute led init state is not correct, after freshly installing the os and boot up, the mic is not muted, but the micmute led is on. [Fix] backport a patch from upstream. [Test] Booting the system with patched kernel, the micmute led init state is correct. If mic is mute, the led is on, if the mic is not mute, the led is off. [Where problems could occur] This could introduce the micmute led wrong init state on other machines, we tested this patch on many lenovo machines, no regression found so far. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1919952/+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 1920777] Re: [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-hwe-5.8 (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu) Status: In Progress => Fix Released ** Changed in: linux-hwe-5.8 (Ubuntu Focal) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.8 in Ubuntu. https://bugs.launchpad.net/bugs/1920777 Title: [SRU][G][HWE-5.8] Fix compatibility issue on some external monitors Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-hwe-5.8 package in Ubuntu: Invalid Status in linux-hwe-5.8 source package in Focal: Won't Fix Status in linux source package in Groovy: Won't Fix Bug description: [Impact] Some external monitors got black screen via HDMI on laptops with Intel GPU. [Fix] Reading more of the port caps and dealing with various clock/bpc limitations. Patchset: https://patchwork.freedesktop.org/series/72928/ [Test Case] Verified on the target platform and other 2 laptops include workstation, Tested on LG/ThinkVision 4k monitors and Dell 1080p monitor, include dock station. All good. [Where problems could occur] Intel GPU may lose or mess the output. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1920777/+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 1920747] Re: alsa/realtek: extend the delay time in the determine_headset_type for a Dell AIO
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1920747 Title: alsa/realtek: extend the delay time in the determine_headset_type for a Dell AIO Status in HWE Next: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Bug description: [Impact] Users plug a headset to this AIO and select headset-mic from UI, but can't record any sound from the headset-mic. [Fix] The root cause is the driver return a wrong type of the headset, need to add more delay in the determine_headset_type(), so backport that patch to ubuntu kernel. [Test] Booting the system with patched kernel, plug headset and select headset-mic from UI, could record sound from headset-mic, we tested more than 10 times, all worked well. [Where problems could occur] This could make the user experience a small delay from pop-up dialogue when plugging a headset, but the delay is less than 1s and the delay is not much longer than other codecs, QA think it is acceptable. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1920747/+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 1920874] Re: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.10 in Ubuntu. https://bugs.launchpad.net/bugs/1920874 Title: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+ Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] Memory card removal event can not be reflected via uevent on some card readers Ex. Realtek card readers 0bda:0328 and 0bda:0158. Thus the file browser still see the ghost disk even it's already removed. [Fix] Found the commit 6540fbf6b643 in 5.9.0-rc3 introduce this regression. Fix it by making sure the partition scan will never be skipped for each vfs_open until the partition scan is really done [Test] Verified on the Realtek card reader 0bda:0328 on Dell Precision 7820 and the external Realtek usb interface card reader 0bda:0158. Insert the SD card in the card reader $ udevadm monitor Remove the SD card and check the udevadm monitor output KERNEL[188.377042] change /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.383261] remove /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) KERNEL[188.390887] change /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.396012] remove /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) The remove event should be observed from the output messages. On the affected card reader, only change event would be observed. [Where problem could occur] These kind of card readers doesn't send remove event of scsi_disk and scsi_device like others so they only depend on the block subsystem to detect the media change and relect the removal event by partition scan. The behavior related to media removal is changed after 5.9.0-rc3. The remove event is not able to be correcly reflected since then, the device node of the media will remain there until next card insertion. == Original Bug Description == Ubuntu version: 20.10 Kernel: 5.10.0-1013-oem Card reader: Realtek Card Reader (0bda:0328 and 0bda:0158) Summary === After upgrading to kernel 5.9.0-rc3 or later, the device node for the partitions on the memory cards will not disappear after removing the memory cards. This is confusing to the user level applications like File Browser since the partition label will remain there for a long time. Steps to reproduce == 1. Upgrade to kernel later than 5.9.0-rc3 2. Plug the external card reader and insert the formatted memory card 3. Verify if the memory card mounted and visible on File Browser 4. Remove the memory card from the card reader 5. Verify if the mounted memory card removed from the File Browser Expected results The mounted memory card identifier should be disappear after remove the memory card Actual results == The partition label of the memory card exists for a long time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dev1443 F pulseaudio /dev/snd/controlC0: dev1443 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_UX434IQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=ac0e9628-3402-4892-84ab-a1dfb21be15a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.190 Tags: groovy Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2020 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX434IQ_UX434IQ.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX434IQ
[Kernel-packages] [Bug 1868217] Re: Make Dell WD19 dock more reliable after suspend
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1868217 Title: Make Dell WD19 dock more reliable after suspend Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When Dell WD19 dock connects multiple USB3 storage devices, the USB Hub used internally may stop working after suspend. [Fix] Disable LPM on the Realtek USB Hub, and let xHCI controller make sure the link state transition is completed. [Test] After applying the patches, the Dell WD19 works reliably after thousand times for suspend/resume cycle. [Regression Potential] Low. This replaces the currently "msleep" way with more robust mechanism. I also test other systems and nothing breaks. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868217/+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 1868510] Re: Dell OptiPlex 7070 Ultra cannot detect external mic after S3
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1868510 Title: Dell OptiPlex 7070 Ultra cannot detect external mic after S3 Status in HWE Next: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] After upgrading to Ubuntu-oem-4.15.0-1076.86, the system can't detect external mic after S3. It's an regression. [Fix] The newly introduce patches lead to the issue, so have to revert them. fe1df22843c1 UBUNTU: SAUCE: ALSA: hda - chain the headset fix to an existing quirk 7c6fd532f7b6 UBUNTU: SAUCE: ALSA: hda - don't forcibly resume the codec on two DELL machines [Test] Verified on Dell OptiPlex 7070 Ultra and confirmed the mic keeps working after several S3. [Regression] The 2 commits are for bug 1858156 and bug 1845140, we need to find other solution for the 2 issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1868510/+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 1869642] Re: No audio output from Dell WD19 HDMI/DP after resumed from S3 or s2idle
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1869642 Title: No audio output from Dell WD19 HDMI/DP after resumed from S3 or s2idle Status in HWE Next: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] Plug-in HDMI/DP cable onto docking station after system resumed from S3/s2idle, there is no audio output from HDMI/DP even if you select the HDMI/DP audio output manually from sound settings. It shows this in dmesg when try testing speakers from sound settings [ 2052.030247] snd_hda_codec_hdmi hdaudioC0D2: Unable to sync register 0x2f0d00. -5 [Fix] This issue has been fixed in 4.16-rc1 by below commit 4918e1f87c5f PM / runtime: Rework pm_runtime_force_suspend/resume() [Test] Verified on Dell Latitude 3310 + Dell WD19 docking station [Regression Potential] Low, it fixes the device usage counter, and should also fix some other runpm issues. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1869642/+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 1874698] Re: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1874698 Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in alsa-ucm-conf package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in alsa-ucm-conf source package in Focal: Fix Released Status in linux source package in Focal: Fix Released Status in alsa-ucm-conf source package in Groovy: Fix Released Bug description: This is for alsa-ucm-conf: The patches are already in the mainline alsa-ucm-conf, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] After fixing the kernel, we also need to change the ucm2 to make it support the machine without Intel hdmi audio. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline alsa-ucm-conf. And we already tested them on 4 HP machines. This is for linux kernel: The patch is already in the oem-5.6 kernel and unstable kernel, so only sent the SRU for focal [Impact] On the machines without Intel HDMI, the sof driver will fail to initialize. [Fix] Intel upstream 2 patches in the kernel to fix it. [Test Case] Boot the kernel on the machines without Intel HDMI audio, everything works well including the audio. [Regression Risk] Low, these 2 patches are already in the mainline kernel. On Ubuntu 20.04, by default, sof-audio-pci is used. I only have "Dummy output" in pavucontrol. To fix this, I modified /etc/modprobe.d/alsa- base.conf and added "options snd-intel-dspcfg dsp_driver=1" so that now "snd-hda-intel" is loaded instead of sof-audio-pci. While the speakers are working fine, I do not have the internal microphone working (suspect a digital array). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: wittawat 2063 F pulseaudio /dev/snd/controlC0: wittawat 2063 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 24 12:42:32 2020 InstallationDate: Installed on 2020-04-23 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaRecordingTest: ALSA recording test through plughw:PCH failed Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_Jack: Black Mic, Left Symptom_Type: None of the above Title: [OMEN by HP Laptop 15-dh0xxx, Realtek ALC285, Black Mic, Left] Recording problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/09/2019 dmi.bios.vendor: AMI dmi.bios.version: F.22 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8600 dmi.board.vendor: HP dmi.board.version: 44.41 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.22:bd12/09/2019:svnHP:pnOMENbyHPLaptop15-dh0xxx:pvr:rvnHP:rn8600:rvr44.41:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dh0xxx dmi.product.sku: 7JX54EA#ABD dmi.sys.vendor: HP mtime.conffile..etc.modprobe.d.alsa-base.conf: 2020-04-24T12:32:21.613996 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874698/+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 1874008] Re: Add support TGL thermal sensor
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1874008 Title: Add support TGL thermal sensor Status in HWE Next: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: [Impact] Intel TGL systems may overheat and trigger a shutdown when doing CPU stress test. It's because the CPU thermal zone is missing. [Fix] Add missing ID to let int340x device work. [test] With the patch, the thermal zone "TCPU" is corretly created. [Regression Potential] Minimal. This patch only adds a missing ID, no functional change. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1874008/+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 1875254] Re: Intermittent display blackouts on event
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-osp1 in Ubuntu.
https://bugs.launchpad.net/bugs/1875254
Title:
Intermittent display blackouts on event
Status in HWE Next:
Fix Released
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-osp1 package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Invalid
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Status in linux-oem-osp1 source package in Focal:
Invalid
Bug description:
[Impact]
When audio device enters runpm D3(idle for 7 seconds) and then wakes it up to
make a sound, it flicks the screen.
This behavior could be observed while plug/remove AC cable or USB disk, or
open a terminal and press backsapce key.
[Fix]
This issue could be fixed by this commit, it fixes the flicker during
boot-time, but it also fixes the flicker during rumtime wakeup.
1ee48a61aa57 drm/i915: Limit audio CDCLK>=2*BCLK constraint back to GLK only
Audio drivers communicate with i915 over HDA bus multiple times during system
boot-up and each of these transactions result in matching
get_power/put_power calls to i915, and depending on the platform,
a modeset change causing visible flicker.
GLK is the only platform with minimum CDCLK significantly lower
than BCLK, and thus for GLK setting a higher CDCLK is mandatory.
For other platforms, minimum CDCLK is close but below 2*BCLK
(e.g. on ICL, CDCLK=176.4kHz with BCLK=96kHz). Spec-wise the constraint
should be set, but in practise no communication errors have been
reported and the downside if set is the flicker observed at boot-time.
[Test]
Verified on Dell XPS 13 9300
[Regression Potential]
Low, it fixes below commit which contains in ubuntu kernel and should have
been applied on ubuntu kernel, too.
Fixes: f6ec9483091f ("drm/i915: extend audio CDCLK>=2*BCLK constraint to more
platforms")
=
Issues with the screen going black for a second on certain events on a dell
XPS 9370 2 in 1, especially when on battery.
Seems to be a known bug in arch
(https://wiki.archlinux.org/index.php/Dell_XPS_13_2-in-1_(7390)).
Last 5.6.7 kernel tested and the issues has disappears but pb with sound card.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: lucie 2232 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: GNOME
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-25 (1 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Dell Inc. XPS 13 7390 2-in-1
Package: linux (not installed)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic
root=UUID=056fd229-d014-4b3b-a581-1b646105d1ed ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
Tags: focal
Uname: Linux 5.4.0-26-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 03/02/2020
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.3.1
dmi.board.name: 06CDVY
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 31
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.3.1:bd03/02/2020:svnDellInc.:pnXPS1373902-in-1:pvr:rvnDellInc.:rn06CDVY:rvrA00:cvnDellInc.:ct31:cvr:
dmi.product.family: XPS
dmi.product.name: XPS 13 7390 2-in-1
dmi.product.sku: 08B0
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1875254/+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 1875519] Re: alsa: front mics could not work on a Lonovo ThinkCenter
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1875519 Title: alsa: front mics could not work on a Lonovo ThinkCenter Status in HWE Next: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Bug description: Only send this patch to oem-5.6 kernel, and after this patch is merged to stable kernel, this patch will be merged to the rest ubutnu kernels. [Impact] On a Lenovo ThinkCenter, there are 2 front mics, but the pulseaudio could handle it, so the front mics could not work. [Fix] Apply an existing quirk to change the location for one of the mics. [Test Case] Plug the mic or headset to either front mic jacks, all work well. [Regression Risk] Low, it is specific to a lenovo machine. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1875519/+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 1876844] Re: Speed up the process of s3 resume
** Changed in: linux (Ubuntu) Status: Invalid => Fix Released ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1876844 Title: Speed up the process of s3 resume Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Invalid Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] Process of s3 resume take 7s and it's too long which is over 5s. [Fix] Instead of using the supported speeds to determine whether to wait for Link training, check whether the port supports DLL Link Active reporting. The ports in question do not, so we'll wait only the 100 ms required for Ports that support Link speeds <= 5 GT/s. This of course assumes these Ports always train the Link within 100 ms even if they are operating at > 5 GT/s, which is not required by the spec. [test] With the patch, the total time s3 resume is 4454.244 ms which is smaller than 5s. [Regression Potential] Low. Follow the PCI spec to check whether the device supports DLL Link Active reporting, then choose the time of delay. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1876844/+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 1877013] Re: Dell XPS 13 9300 mirror mode doesn't work sometimes with WD19TB
** Changed in: hwe-next Status: New => Fix Committed ** Changed in: hwe-next Status: Fix Committed => 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/1877013 Title: Dell XPS 13 9300 mirror mode doesn't work sometimes with WD19TB Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Connect HDMI monitor on WD19TB dock and connect WD19TB to Dell XPS 13 9300, toggling the display mode to mirror sometimes got a blank screen on external monitor. [Fix] After bisect kernel and found below commit(from v5.7-rc2) improves the stability bcad588dea53 drm/i915/perf: Do not clear pollin for small user read buffers [Test] Verified on Dell XPS 13 9300 with WD19TB docking station, the fail rate becomes from 1/2 to 1/30 [Regression Potential] Low, this commit has been CC'd to stable, so we will have this soon. [Misc] OEM-5.6 has this commit from v5.6.6 stable update To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1877013/+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 1905663] Re: Add dpcd backlight control for 0x4c83 0x4f41
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1905663 Title: Add dpcd backlight control for 0x4c83 0x4f41 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] There is a new OLED panel that is required to be listed in the EDID quirk to make its backlight work. [Fix] The commit adds its EDID to the quirk. https://lkml.org/lkml/2020/11/19/1564 [Test] Verified on Dell's platform with this panel. [Where problems could occur] Only if this panel switches to use PWM mode only, and doesn't support DPCD backlight. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1905663/+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 1876859] Re: Support DMIC micmute LED on HP platforms
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1876859 Title: Support DMIC micmute LED on HP platforms Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Fix Released Bug description: [Impact] DMIC micmute LED on HP platforms doesn't work. [Fix] Add LED class support from HDA codec, so DMIC can use LEDS_TRIGGER_AUDIO to control micmute. [Test] After applying the fix, micmute LED can correctly indicate the status of micmute. [Regression Potential] Low. For now it only affects one platform, and it doesn't touch any core part of the subsystem. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1876859/+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 1878554] Re: alsa/hdmi: restore the component support patch_nvhdmi
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu Groovy) Status: Incomplete => Won't Fix ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1878554 Title: alsa/hdmi: restore the component support patch_nvhdmi Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Bug description: BugLink: https://bugs.launchpad.net/bugs/1878554 The reverted patch was introduced by stable-patches, and this SRU plans to revert the patch, the commit id is from oem-5.6 kernel, so maybe in the Groovy and unstable kernel, the commit id is not same as this one. [Impact] On Lenovo P520 with Nvida P4000 grahic card, the hdmi audio doesn't work. [Fix] revert an existing patch to let patch_nvhdmi support component. [Test Case] boot the system, plug the hdmi/dp monitor, the hdmi audio could work, wait for 10 mins until the screen become black, wake up the screen and check the audio, still work well. [Regression Risk] Low, after reverting the patch, it is aligned to mainline kernel To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1878554/+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 1872383] Re: blk_update_request error when mount nvme partition
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1872383 Title: blk_update_request error when mount nvme partition Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Bug description: [Impact] Got below error message after upgraded Focal kernel(v5.4) [ 576.793852] blk_update_request: operation not supported error, dev nvme1n1, sector 4218887 op 0x9:(WRITE_ZEROES) flags 0x0 phys_seg 0 prio class 0 This issue was introduced by below commit which added write zeros command 6e02318eaea5 nvme: add support for the Write Zeroes command SK hynix firmware has a bug that it treats NLB as max value instead of a range, so the NLB passed isn't a valid value to the firmware. [Fix] Add a quirk to disable write zeros support [Test] Verified on the machine with SK hynix PC400 nvme machine. [Regression Potential] Low, it's a quirk to a specific PCI ID. == Can't install on this nvme with a focal server installer. As mount a nvme partition with kernel with focal 5.4.0-21-generic kernel endless blk_update_request error will exists in kernel dmesg. the nvme module: PC400 NVMe SK hynix 512GB While mount nvme module: PC SN720 NVMe WDC 256GB, there is no such issue. --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-21-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (11 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200330) IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06c4:c401 Bizlink International Corp. DisplayPort ALT mode device Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/10p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/16p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=, 12M MachineType: Dell Inc. Precision 3930 Rack Package: linux-generic 5.4.0.21.25 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=2b73a661-f0a8-453a-ac0d-b93c5eb97f8d ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 02/05/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 2.5.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr2.5.0:bd02/05/2020:svnDellInc.:pnPrecision3930Rack:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct23:cvr: dmi.product.family: Precision dmi.product.name: Precision 3930 Rack dmi.product.sku: 0873 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1872383/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1872569] Re: alsa/sof: external mic can't be deteced on Lenovo and HP laptops
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1872569 Title: alsa/sof: external mic can't be deteced on Lenovo and HP laptops Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] When users plug a headset into the audio jack, the driver can't detect the mic, only can detect the headhpone. If users open the gnome-sound-setting, the mic could be detected. [Fix] Need to set auto_suspend_delay to the codec driver [Test Case] boot the kenrel, plug/unplug the headset, run amixer contents to check the "Jack Mic" state [Regression Risk] Low, this patch comes from intel sof kernel, I have tested this patch on HP and Lenovo machine, they all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1872569/+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 1879321] Re: Fix Pericom USB controller OHCI/EHCI PME# defect
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1879321 Title: Fix Pericom USB controller OHCI/EHCI PME# defect Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem-5.6 source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] Pericom EHCI/OHCI USB Controller can't detect hotplug event when it's runtime-suspended, due to its unreliable PME#. [Fix] Disable PME for all its power state since all of them don't work reliably. [Test] Hotplugging event can be reliably detected by the device, after the fix gets applied. [Regression Potentia] Low. This targets specific device, without touching any logic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1879321/+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 1906168] Re: Prevent thermal shutdown during boot process
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1906168 Title: Prevent thermal shutdown during boot process Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Bug description: [Impact] Surprising thermal shutdown at boot on Intel based mobile workstations. [Fix] Since these thermal devcies are not in ACPI ThermalZone, OS shouldn't shutdown the system. These critial temperatures are for usespace to handle, so let kernel know it shouldn't handle it. SRU for stable kernels will be sent after the fix is in upstream. [Test] Use reboot stress as a reproducer. 5% chance to see a surprising shutdown at boot. With the fix applied, the thermal shutdown is no longer reproducible. [Where problems could occur] For ACPI based platforms, we still have "acpitz" to protect systems from overheating. If these acpitz sensors don't work, then the system could face real overheating issue. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906168/+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 1906229] Re: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1906229 Title: Refresh ACPI wakeup power to make Thunderbolt hotplug detection work Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-oem-5.6 source package in Groovy: Invalid Bug description: [Impact] Dell Precision 5550 cannot detect Thunderbolt device hotplug. [Fix] Refresh ACPI wakeup power if it's already enabled to make GPE work. [Test] Make sure the root port of TBT hierachy is in D3cold. Plug a Thunderbolt Dock or Thunderbolt Disk, the system cannot detect anything. With the patch applied, OS can always detect hotplugged Thunderbolt devices. [Where problems could occur] Though we refresh the wakeup device power, we didn't disable/enable ACPI GPEs, so we won't miss any GPE event from this fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906229/+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 1906839] Re: Use INTx for Pericom USB controllers
** Changed in: hwe-next
Status: New => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.10 in Ubuntu.
https://bugs.launchpad.net/bugs/1906839
Title:
Use INTx for Pericom USB controllers
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux-oem-5.10 package in Ubuntu:
Won't Fix
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.10 source package in Focal:
Fix Released
Bug description:
[Impact]
Pericom EHCI/OHCI controller cannot detect USB hotplug after using MSI.
[Fix]
Disable MSI and fallback to INTx.
[Test]
Hotplug any USB device and nothing gets detected.
With the fix applied the issue is gone.
[Where problems could occur]
Nothing wrong can happen. It was already using INTx before 306c54d0edb6
("usb: hcd: Try MSI interrupts on PCI devices"), and now it goes back to
use INTx again.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1906839/+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 1906851] Re: Fix reading speed and duplex sysfs on igc device
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-oem-5.6 (Ubuntu Focal) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1906851 Title: Fix reading speed and duplex sysfs on igc device Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Won't Fix Status in linux source package in Groovy: Fix Released Status in linux-oem-5.10 source package in Groovy: Won't Fix Status in linux-oem-5.6 source package in Groovy: Won't Fix Bug description: [Impact] Reading speed and duplex sysfs on igc device when it's runtime suspended will make it stops working. Even kernel panic sometimes. [Fix] If igc device is runtime suspended, it means link isn't up, so we can just report speed as -1 and duplex as unknown. [Test] $ cat /sys/class/net/*/speed Then we'll see: [ 123.449883] igc :03:00.0 enp3s0: PCIe link lost, device now detached [ 123.450052] BUG: kernel NULL pointer dereference, address: 0008 With the fix applied, $ cat /sys/class/net/*/speed -1 [Where problems could occur] Not at all. Reading register when device is runtime suspended is just wrong. The fix prevents it from happening. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1906851/+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 1953058] Re: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion even
** Summary changed: - Kernel "BUG: soft lockup" with 5.4 kernels on appleton node (arm64) + Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") ** Tags added: sru-20220808 -- 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/1953058 Title: Kernel "BUG: soft lockup" with 5.4 kernels on arm64 node appleton node (dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9") Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: Confirmed Bug description: The regression boot test running with bionic:linux-hwe-5.4 5.4.0-92.103~18.04.2 failed because of the following hung task: Dec 2 12:17:12 appleton-kernel kernel: [ 64.281447] watchdog: BUG: soft lockup - CPU#16 stuck for 22s! [swapper/16:0] Dec 2 12:17:12 appleton-kernel kernel: [ 64.288573] Modules linked in: ipmi_ssif nls_iso8859_1 joydev input_leds ipmi_si ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx5_ib hid_generic ses usbhid enclosure hid ib_uverbs ib_core marvell hibmc_drm drm_vram_helper ttm drm_kms_helper crct10dif_ce ghash_ce syscopyarea sysfillrect sha2_ce mlx5_core sysimgblt sha256_arm64 ixgbe hisi_sas_v2_hw fb_sys_fops nvme sha1_ce hisi_sas_main tls xfrm_algo drm megaraid_sas nvme_core mdio mlxfw libsas ehci_platform scsi_transport_sas hns_dsaf hns_enet_drv hns_mdio hnae aes_neon_bs aes_neon_blk aes_ce_blk crypto_simd cryptd aes_ce_cipher Dec 2 12:17:12 appleton-kernel kernel: [ 64.288629] CPU: 16 PID: 0 Comm: swapper/16 Not tainted 5.4.0-91-generic #102~18.04.1-Ubuntu Dec 2 12:17:12 appleton-kernel kernel: [ 64.288630] Hardware name: Hisilicon D05/BC11SPCD, BIOS 1.50 06/01/2018 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288632] pstate: 4045 (nZcv daif +PAN -UAO) Dec 2 12:17:12 appleton-kernel kernel: [ 64.288640] pc : __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288644] lr : irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288645] sp : 800011ee3ef0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288646] x29: 800011ee3ef0 x28: 002fb71a2d00 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288649] x27: x26: 800011ee4000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288650] x25: 800011ee x24: 001fba073600 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288652] x23: 80001234bdb0 x22: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288654] x21: 0282 x20: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288656] x19: 8000116b3000 x18: 800011267510 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288658] x17: x16: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288659] x15: 0001 x14: 002fbb9f21c8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288661] x13: 0004 x12: 0002 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288663] x11: x10: 0040 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288665] x9 : 800011bbf228 x8 : 800011bbf220 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288666] x7 : 001fb9002270 x6 : 0002c07fa07f Dec 2 12:17:12 appleton-kernel kernel: [ 64.288668] x5 : 00c1 x4 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288670] x3 : 8000116b3780 x2 : 802faa352000 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288672] x1 : 00e0 x0 : 8000116b3780 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288675] Call trace: Dec 2 12:17:12 appleton-kernel kernel: [ 64.288677] __do_softirq+0x98/0x350 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288679] irq_exit+0xc0/0xc8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288683] __handle_domain_irq+0x6c/0xc0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288685] gic_handle_irq+0x84/0x2c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288687] el1_irq+0x104/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288690] arch_cpu_idle+0x34/0x1c0 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288694] default_idle_call+0x24/0x60 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288696] do_idle+0x1d8/0x2b8 Dec 2 12:17:12 appleton-kernel kernel: [ 64.288699] cpu_startup_entry+0x28/0xb0 Dec 2 12:17:12 appleton-kernel
[Kernel-packages] [Bug 1958952] Re: ARM64 node appleton-kernel dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9"
*** This bug is a duplicate of bug 1953058 *** https://bugs.launchpad.net/bugs/1953058 ** This bug has been marked a duplicate of bug 1953058 Kernel "BUG: soft lockup" with 5.4 kernels on appleton node (arm64) -- 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/1958952 Title: ARM64 node appleton-kernel dmesg spammed with "mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9" Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Bug description: While investigating the SRU deployment failure, I noticed the dmesg will be spammed with: Jan 25 07:48:36 appleton-kernel kernel: [ 22.885627] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885628] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1218): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885629] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Jan 25 07:48:36 appleton-kernel kernel: [ 22.885631] mlx5_core 0005:01:00.0: mlx5_eq_comp_int:159:(pid 1180): Completion event for bogus CQ 0x5a5aa9 Issue found with Focal 5.4.0-96-generic Please find attachment for the syslog. Not sure if this is cause of our deployment issue, but it seems odd to me. And here is our deployment issue: 1. System successfully deployed with Focal 2. Deployment process hangs with "Enabling PPA" stage 3. I cannot connect to this system manually, ssh hangs (soft lockup maybe?) after: Warning: Permanently added '10.229.50.13' (ECDSA) to the list of known hosts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-96-generic 5.4.0-96.109 ProcVersionSignature: Ubuntu 5.4.0-96.109-generic 5.4.157 Uname: Linux 5.4.0-96-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 25 07:48 seq crw-rw 1 root audio 116, 33 Jan 25 07:48 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.21 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Tue Jan 25 07:53:33 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 004: ID 12d1:0003 Huawei Technologies Co., Ltd. Bus 001 Device 003: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 002: ID 0424:2514 Microchip Technology, Inc. (formerly SMSC) USB 2.0 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-platform/2p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 2: Dev 3, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 1: Dev 4, If 1, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 1: Dev 4, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Hisilicon D05 PciMultimedia: ProcFB: 0 hibmcdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-96-generic root=UUID=3abb8e5a-2f46-4221-b664-cb02a273a249 ro sysrq_always_enabled RelatedPackageVersions: linux-restricted-modules-5.4.0-96-generic N/A linux-backports-modules-5.4.0-96-generic N/A linux-firmware1.187.25 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/01/2018 dmi.bios.vendor: Huawei dmi.bios.version: 1.50 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: BC11SPCD dmi.board.vendor: Huawei dmi.board.version: VER.A dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 17 dmi.chassis.vendor: Hisilicon dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnHuawei:bvr1.50:bd06/01/2018:svnHisilicon:pnD05:pvrV100R001C00:rvnHuawei:rnBC11SPCD:rvrVER.A:cvnHisilicon:ct17:cvrTobefilledbyO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: D05 dmi.product.sku: To be filled by O.E.M. dmi.product.version: V100R001C00 dmi.sys.vendor: Hisilicon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1958952/+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 1857883] Re: i915 DMS firmware kbl_dmc_ver1_{01, 04}.bin hang system during suspend
assuming fixed since
** Changed in: linux-firmware (Ubuntu)
Status: Incomplete => Invalid
** Changed in: hwe-next
Status: New => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-firmware in Ubuntu.
https://bugs.launchpad.net/bugs/1857883
Title:
i915 DMS firmware kbl_dmc_ver1_{01,04}.bin hang system during suspend
Status in HWE Next:
Invalid
Status in OEM Priority Project:
Triaged
Status in linux-firmware package in Ubuntu:
Invalid
Bug description:
steps I done:
- install stock Bionic
- full update and reboot
- suspend system => Failed with dark screen
- install linux-oem-osp1 and reboot
- suspend system => Failed with dark screen
tests I tried:
- pm_test failed in processors with dark screen
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-oem-osp1 5.0.0.1030.34
ProcVersionSignature: Ubuntu 5.0.0-1030.34-oem-osp1 5.0.21
Uname: Linux 5.0.0-1030-oem-osp1 x86_64
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Dec 30 16:59:36 2019
InstallationDate: Installed on 2019-12-30 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
SourcePackage: linux-meta-oem-osp1
UpgradeStatus: No upgrade log present (probably fresh install)
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: u 1401 F pulseaudio
CurrentDesktop: ubuntu:GNOME
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2019-12-30 (0 days ago)
InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64
(20190805)
MachineType: Dell Inc. Latitude 5590
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1030-oem-osp1
root=UUID=d065cd98-cc0b-4711-bcab-74f3e677de3a ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.0.0-1030.34-oem-osp1 5.0.21
RelatedPackageVersions:
linux-restricted-modules-5.0.0-1030-oem-osp1 N/A
linux-backports-modules-5.0.0-1030-oem-osp1 N/A
linux-firmware 1.173.14
Tags: bionic
Uname: Linux 5.0.0-1030-oem-osp1 x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 09/19/2019
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.11.1
dmi.board.name: 0083K0
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias:
dmi:bvnDellInc.:bvr1.11.1:bd09/19/2019:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn0083K0:rvrA00:cvnDellInc.:ct10:cvr:
dmi.product.family: Latitude
dmi.product.name: Latitude 5590
dmi.product.sku: 0817
dmi.sys.vendor: Dell Inc.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1857883/+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 1858159] Re: enable realtek ethernet EEE function
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1858159 Title: enable realtek ethernet EEE function Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Bug description: [Impact] Energy Start 8 requires EEE(Energy Efficient Ethernet) feature, so we need to backport this from v5.1 kernel. [Fix] This feature is already in v5.1 mainline kernel, just backport some commits to enable it. [Test] Verified on the target machine, and confirm "ethtool --show-eee" shows this feature is enabled [Regression Potential] Medium. It's hard to evaluate the impact since the code changes a lot. Only one commit is backported, and others are clear cherry picked, so the quality of the code should be good enough. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858159/+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 1858988] Re: USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2 card [1b21:2142]
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1858988 Title: USB key cannot be detected by hotplug on Sunix USB Type-A 3.1 Gen 2 card [1b21:2142] Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Won't Fix Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Fix Released Bug description: [Impact] Hotplug USB key to Sunix USB Type-A 3.1 Gen 2 card can't be detected [Fix] ASMedia XHCI USB controller PME# doesn't work under D0, so remove its cap by quirk. [Test] Verified on the target machine, USB 3 storage works. [Regression Potential] Low, it only affects target chip. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858988/+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 1858751] Re: Fix throttled clock on AMD Oland
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1858751 Title: Fix throttled clock on AMD Oland Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Eoan: Fix Released Status in linux-firmware source package in Focal: Fix Released Bug description: [Impact] Running simple 3D apps like glxgears in 4K becomes really sluggish. [Fix] Update rlc microcode to its latest version. [Test] Run `glxgears -fullscreen` on 4K monitor. The issue disappears after this firmware update. [Regression Potential] Low. The firmware is already used by amdgpu.ko for a while, now we also use it for radeon.ko. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1858751/+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 1853246] Re: [SRU][B/OEM-B/OEM-OSP1/D] Enable new Elan touchpads which are not in current whitelist
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1853246 Title: [SRU][B/OEM-B/OEM-OSP1/D] Enable new Elan touchpads which are not in current whitelist Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: SRU justification: [Impact] New touchpads are ignored by hid driver because of IDs are missed in the whitelist. [Fix] Only 2 Elan touchpad IDs are allowed to be loaded in hid driver. Change to the blacklist of elan touchpads supported by elan_i2c, so others can be enabled by hid. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. keep current IDs of elan_i2c, loads those touchpads ID those weren't supported. Those patches are already in 5.3+ kernel, only bionic and disco kernel need them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853246/+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 1859126] Re: Reduce s2idle power consumption when ethernet cable is connected on e1000e
** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Invalid ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1859126 Title: Reduce s2idle power consumption when ethernet cable is connected on e1000e Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When ethernet cable is connected, power consumption is quite high under suspend-to-idle. [Fix] Enable s0ix support for e1000e. [Test] When ethernet cable is connected, the power consumption is ~2.5w. After applying the patch, it can be lowered to ~1.8w. [Regression Potential] Low. This fix is limited to fairly recent I219 hardwares. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859126/+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 1853791] Re: External microphone can't work on some dell machines with the codec alc256 or alc236
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1853791 Title: External microphone can't work on some dell machines with the codec alc256 or alc236 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] The external microphone can't work on some dell machines with the codec alc256 or alc236 [Fix] Need to apply the ALC255_FIXUP_DELL1_MIC_NO_PRESENCE, instead of adding a new pintbl in the quirk table, we use fallback table this time. [Test Case] tested the kernel with these patches, the external mic worked well. [Regression Risk] Low, just make the quirk applying more generic. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853791/+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 1854401] Re: headphone has noise as not mute on dell machines with alc236/256
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1854401 Title: headphone has noise as not mute on dell machines with alc236/256 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] There is noise in the headphone on some dell machines with the codec alc256 or alc236 [Fix] Realtek provide a patch to disable PCBEEP_IN to heapdhone. [Test Case] tested the kernel with this patch, the noise disappeared. [Regression Risk] Low, Realtek provided the patch, and it is limited to apply to alc236 and 256, and just disable the PCBEEP_IN to headphone.. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854401/+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 1854432] Re: Fix MST support on Ice Lake
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1854432 Title: Fix MST support on Ice Lake Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] Some HDMI and DP doesn't count as external monitor on ICL MST. [Fix] Fix external port MST check on Ice Lake. [Test] DP and HDMI ports can only mirror display. After applying this patch bot DP and HDMI ports can drive its own external display. [Regression Potential] Low. This fix targets Gen 11 and Gen 12 Intel graphics, older systems are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854432/+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 1859538] Re: Harrison Peak wifi / BT support
** Changed in: hwe-next Status: New => 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/1859538 Title: Harrison Peak wifi / BT support Status in HWE Next: Fix Released Status in intel: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: Description: HrP2 will be supported in CML/TGL platform. Target Release: 20.04 Target Kernel: 5.4 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859538/+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 1854971] Re: Fix resume freeze on S2I
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1854971 Title: Fix resume freeze on S2I Status in HWE Next: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Bug description: [Impact] Some Laptops use suspend-to-idle freeze at resume. [Fix] Delay after PCI power transition completion on suspend-to-idle, just like runtime resume. [Test] With the patch applied, the system can pass suspend stress test. [Regression Potential] Low. It's a stable patch that's already in Eoan/Focal kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1854971/+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 1855666] Re: alsa/sof: change to use hda hdmi codec driver to make hdmi audio on the docking station work
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1855666 Title: alsa/sof: change to use hda hdmi codec driver to make hdmi audio on the docking station work Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] We have integrated the alsa sof driver in the oem-osp1 kernel, and when we tested the hdmi audio function on the docking station, we found if the machine use sof driver, the hdmi audio on the docking station can't work. [Fix] Intel wrote patches to let sof driver to choose hda hdmi codec driver, then both hdmi on the laptop and on the docking station worked. [Test Case] ran the kernel with these patches, and in the userspace, we used the intel updated ucm, then the hdmi audio on the docking station worked. [Regression Risk] Low, Intel wrote the patches and told us to backport these patches. In addition, we already tested these patches with 4 oem project bugs, all worked well. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855666/+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 1860248] Re: No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof
** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1860248 Title: No sof soundcard for 'ASoC: CODEC DAI intel-hdmi-hifi1 not registered' after modprobe sof Status in HWE Next: Fix Released Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] When we boot the kernel on a Dell machchine which has a discrete nvidia graphic card, the sof driver will fail to initialize sometimes, and after investigation, we found if let nvidia hdmi audio load the codec driver first, the sof driver will fail to initialize 100%. [Fix] Intel release a patch to fix this issue, after applying this patch, the sof driver could work even the nividia hdmi audio initializes first. [Test Case] We test this patch, the issue could be reproduced anymore in 100 times reboot. [Regression Risk] Low, Intel released the patch to us, and we already did large numbers of audio test in the oem project. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1860248/+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 1864606] Re: CPU package state stuck at PC3 with nvidia dGPU in power saving mode
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1864606 Title: CPU package state stuck at PC3 with nvidia dGPU in power saving mode Status in HWE Next: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Bug description: [Impact] On a certain Dell laptop which comes with nvidia dGPU, the CPU package state stuck at PC3 in power saving mode(uses iGPU) [Fix] It requires below commit(from v5.3-rc1) for runtime pm to work, and to avoid conflict, have to introduce another refactor commit. d4a4f927e4dd i2c: nvidia-gpu: add runtime pm support cb7302fbe365 i2c: nvidia-gpu: refactor master_xfer [Test] Verified on the target laptop, it enters PC10 during long idle. [Regression Potential] Low, the commit simply adds runtime pm support. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1864606/+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 1864005] Re: Fix AMD Stoney Ridge screen flickering under 4K resolution
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Won't Fix ** Changed in: hwe-next Status: New => 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/1864005 Title: Fix AMD Stoney Ridge screen flickering under 4K resolution Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: [Impact] Screen flickering/tearing when AMD Stoney Ridge outputs to 4K display. [Fix] Disable IOMMU on Stoney Ridge. [Test] Connect to 4K screen through DP or HDMI. Heavy flickering/tearing can be observed. The flickering/tearing is gone once the patch is applied. [Regression Potential] Low. This fix limits to one specific SoC. According to AMD, IOMMU isn't enabled for this SoC under Windows. So it's expected behavior. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1864005/+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 1865402] Re: Stop using get_scalar_status command in Dell AIO uart backlight driver
** Changed in: hwe-next Status: New => Fix Released ** Changed in: linux (Ubuntu Focal) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1865402 Title: Stop using get_scalar_status command in Dell AIO uart backlight driver Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Won't Fix Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux source package in Groovy: Won't Fix Status in linux source package in Hirsute: Fix Released Bug description: [Impact] The get_scalar_status command was provided by ODM engineer and was newly introduced to determinate whether scalar is responsible for the backlight adjustment. That guy asked the scalar vendor to add this command and the command works as expected. But there is already a command in the Dell AIO scalar UART command spec. which can do the same thing since 2015, and the newly introduced get_scalar_status command is undocumented. To prevent from introducing regression in the future and to align with what Windows uses, replace this command with get_display_mode command. [Fix] Replace get_scalar_status command with get_display_mode command. [Test] Verified on new Dell AIO platforms. [Regression Potential] Low, the command is already in the spec. since 2015. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1865402/+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 1866581] Re: The voice recording function cannot work while connecting a headset on a Dell machine
** Changed in: linux (Ubuntu Focal) Status: Incomplete => Fix Released ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1866581 Title: The voice recording function cannot work while connecting a headset on a Dell machine Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [Impact] The headset mic can't record any sound on this machine. [Fix] The headset-mic is set to ctia mode by hardware. we need to apply an existing quirk. [Test Case] boot the system, plug the headset, it could record the sound via headset mic. [Regression Risk] Low, this patch is specific to 2 dell machines. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1866581/+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 1866309] Re: i915 kernel call trace dumped randomly
** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Won't Fix ** Changed in: oem-priority Status: New => Invalid ** Changed in: hwe-next Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1866309 Title: i915 kernel call trace dumped randomly Status in HWE Next: Invalid Status in OEM Priority Project: Invalid Status in linux-oem-osp1 package in Ubuntu: Won't Fix Bug description: The i915 kernel call traced is dumping into dmesg randomly consistently. Solution I tried: 1. dist-upgrade : no work 2. mainline kernel 5.4 : works , no i915 call trace for a while ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-oem-osp1 5.0.0.1040.45 ProcVersionSignature: Ubuntu 5.0.0-1040.45-oem-osp1 5.0.21 Uname: Linux 5.0.0-1040-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1731 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Mar 6 15:00:50 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-melisa+X31 InstallationDate: Installed on 2020-03-06 (0 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 IwConfig: lono wireless extensions. enx00e04c000af0 no wireless extensions. MachineType: Dell Inc. XPS 13 9300 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1040-oem-osp1 root=UUID=72d9f512-8581-4d1c-aa63-d3eb2a12426c ro debug-oem-config automatic-oem-config quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-1040-oem-osp1 N/A linux-backports-modules-5.0.0-1040-oem-osp1 N/A linux-firmware 1.173.15 RfKill: SourcePackage: linux-oem-osp1 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/26/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.7 dmi.board.name: 019A14 dmi.board.vendor: Dell Inc. dmi.board.version: X02 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.7:bd02/26/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn019A14:rvrX02:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1866309/+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 1833484] Re: Sometimes touchpad automatically trigger double click
** Changed in: linux (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: hwe-next Status: Triaged => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1833484 Title: Sometimes touchpad automatically trigger double click Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux-oem-osp1 source package in Disco: Fix Released Bug description: [Impact] Dell machines which uses goodix touchpad IC emit double click event while touching the touchpad if designware i2c adapter is in runtime suspend. Goodix re-assert the interrupt if host doesn't read the data within 100ms and designware takes a longer time to wake up from runtime suspend. In the case, it got a second interrupt during resuming, so it thinks it's a double click. [Fix] There is no simple way to fix this, it's a firmware issue and goodix agrees to fix this in their firmware on next release, but this issue is still affects the machines that don't come with an updated firmware. So, add a quirk to mark those machines and avoid the designware from entering runtime suspend. [Regression Potential] Low, it only affects the listed machines, and prevent designware from entering runtime suspend impacts the power consumption little or none during short or long idle. [MISC] This patch contains on going product name, so set it as SAUCE patch, will submit it to upstream and to Bionic kernel later. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1833484/+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 1855978] Re: linux-firmware updates breaks Intel 9260 on Bionic
I'm guessing this has been fixed since ** Changed in: linux-firmware (Ubuntu) Status: Triaged => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1855978 Title: linux-firmware updates breaks Intel 9260 on Bionic Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Bug description: Bug 1852512 pulls new firmware blobs for 5.3 hwe kernel upgrade, and iwlwifi-9260-th-b0-jf-b0-46.ucode is included. This new version doesn't seem to be compatible with Bionic OEM kernels, and will fail WiFi initialization leaving the system booted without wireless connection. The previous version (1.173.12) has iwlwifi-9260-th-b0-jf-b0-43.ucode instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.13 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Dec 11 14:18:01 2019 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 InstallationDate: Installed on 2019-07-11 (152 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855978/+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 1855999] Re: alsa/hda/realtek: the line-out jack doens't work on a dell AIO
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1855999 Title: alsa/hda/realtek: the line-out jack doens't work on a dell AIO Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] This is from an OEM bug, the line-out jack doesn't work on a Dell AIO machine. [Fix] apply the fixup ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, and make the matching more generic. [Test Case] Booting the kernel with this patch, the line-out jack worked well. [Regression Risk] Low, just apply an existing fixup to a specific machine (dell with alc274 codec, and the pin 0x19 and 0x1a has the 0x4000 configuration). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855999/+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 1857496] Re: usb-audio: the mic can't record any sound after resume on Dell Dock WD19
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1857496 Title: usb-audio: the mic can't record any sound after resume on Dell Dock WD19 Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Bug description: [Impact] There is a heaset jack on the dock, after resume, the mic on that jack can't record sound anymore, need to close the recording app then reopen that app to workaround this issue. [Fix] set the interface and EP, then the mic can record sound again. [Test Case] test the kernel with this patch, the mic can record sound after resume. [Regression Risk] Low, this quirk is specific to WD19 (usb vednor and device id). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857496/+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 1857541] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1857541 Title: [SRU][B/OEM-B/OEM-OSP1/D/E/F] Add LG I2C touchscreen multitouch support Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-oem source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: SRU justification: [Impact] The current kernel didn't support multitouch for LG I2C touchscreen. [Fix] Add LG I2C id to hid-multitouch to support it. [Test] Verified on hardware with a positive result. [Regression Potential] Low. Add new I2C id with positive verification. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857541/+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 1856517] Re: X crashes if set to external monitor only and then remove HDMI cable during suspend
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1856517 Title: X crashes if set to external monitor only and then remove HDMI cable during suspend Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Bug description: [Impact] Connect a type-c to HDMI converter to the machine and set the display to external monitor only, the X crashes when resumed if you unplug the cable during suspend(s2idle). [Fix] The fix is provided by upstream https://github.com/djdeath/linux/commit/896d4375e8e986e9f70173ac2d2463ecfa92fad8 [Test] Verified on Dell machine, can't reproduce this issue and not visible regression can be observed. [Regression Potential] Low, it pass fwts suspend test 30 times, and no any regression can be observed. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1856517/+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 1856079] Re: Fix Realtek Bluetooth firmware download
** Changed in: linux (Ubuntu) Status: Triaged => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-osp1 in Ubuntu. https://bugs.launchpad.net/bugs/1856079 Title: Fix Realtek Bluetooth firmware download Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-osp1 source package in Eoan: Fix Released Bug description: [Impact] Realtek Bluetooth controller failed to download firmware larger than 32K. [Fix] Update btrtl firmware downloading logic to match the hardware behavior. [Test] Several cold boots to force load firmware, and it never fails after the fix. [Regression Potential] Low. It's a trivial fix and we've verified it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1856079/+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 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
Nice post. I used to be checking constantly this blog and I am impressed! Extremely useful info particularly the ultimate section I take care of such information a lot. I was seeking this certain information for a long time. Thank you and best of luck. https://technologycounter.com/hr-software/india https://technologycounter.com/crm-software/india -- 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/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64 UnreportableReason:
[Kernel-packages] [Bug 1834464] Re: Missing bluetooth firmware for Intel Wireless-AC 9462/9560
** Changed in: linux-firmware (Ubuntu Cosmic) Status: Fix Committed => Won't Fix ** Changed in: linux-firmware (Ubuntu Eoan) Status: In Progress => Won't Fix ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Released ** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1834464 Title: Missing bluetooth firmware for Intel Wireless-AC 9462/9560 Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Released Status in linux-firmware source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: Fix Released Status in linux-firmware source package in Eoan: Won't Fix Bug description: [Impact] Bluetooth on Intel Wireless-AC 9462/9560 requires new firmware blobs to be enabled. [Fix] Backport newly released firmware blobs from linux-firmware. This will also requires minor change to the WHENCE file to resolve cherry-pick conflicts. B/C/D would requires this explicitly and Eoan should be rebased onto linux-firmware master branch HEAD as usual. [Test Case] Verified with hardware platforms with corresponding devices. Completely power off and power on to trigger firmware reload, check from dmesg to see if Bluetooth firmware has been correctly loaded. [Regression Risk] Low. This adds new binary firmware blobs that are only loaded by targeting hardware. == original bug description == On systems with Intel Wireless-AC 9462/9560 cards, following failed- to-load-firmware kernel messages found: bluetooth hci0: Direct firmware load for intel/ibt-19-32-1.sfi failed with error -2 See also Bug #1833065 for wireless firmware & driver fix. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1834464/+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
