[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Same for me. root@hpbo:~# inxi -SCGxxxz System:Host: hpbo Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Console: tty 1 wm: kwin_x11 dm: SDDM Distro: Ubuntu 19.10 (Eoan Ermine) CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP arch: Kaby Lake rev: C L1 cache: 256 KiB L2 cache: 8192 KiB L3 cache: 8192 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 31999 Speed: 969 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 969 2: 824 3: 825 4: 742 5: 743 6: 786 7: 822 8: 732 Graphics: Device-1: Intel UHD Graphics 620 vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 resolution: 1920x1080~60Hz, 2560x1440~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes root@hpbo:~# journalctl -b | grep i915 apr 10 10:57:00 hpbo kernel: i915 :00:02.0: vgaarb: deactivate vga console apr 10 10:57:00 hpbo kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem apr 10 10:57:00 hpbo kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) apr 10 10:57:00 hpbo kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 apr 10 10:57:00 hpbo kernel: fbcon: i915drmfb (fb0) is primary device apr 10 10:57:00 hpbo kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device apr 10 10:57:00 hpbo kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) apr 10 16:22:09 hpbo kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 apr 10 16:22:09 hpbo kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiro
[Kernel-packages] [Bug 1872108] [NEW] Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
Public bug reported: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: alsa-ucm-conf (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal ** Description changed: - Related to last comment on this issue - https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677 + Related to + https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: - + InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: linux PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1872108] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1872108 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: linux PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
apport information ** Tags added: apport-collected ** Description changed: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu26 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + Dependencies: + + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-08 (1 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) + Package: linux + PackageArchitecture: all + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 + Tags: focal + Uname: Linux 5.4.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1872108/+attachment/5351447/+files/ProcCpuinfoMinimal.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 alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: linux PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+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 1871651] Re: Focal update: v5.4.31 upstream stable release
Correction to Comment 1. The commit which requires the new dependency is: UBUNTU: [Packaging] add libcap-dev dependency Required to support the commit: fcaa681c03ea "tools/power turbostat: Fix 32-bit capabilities warning" -- 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/1871651 Title: Focal update: v5.4.31 upstream stable release Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.31 upstream stable release from git://git.kernel.org/ nvme-rdma: Avoid double freeing of async event data kconfig: introduce m32-flag and m64-flag drm/amd/display: Add link_rate quirk for Apple 15" MBP 2017 drm/bochs: downgrade pci_request_region failure from error to warning initramfs: restore default compression behavior drm/amdgpu: fix typo for vcn1 idle check tools/power turbostat: Fix gcc build warnings tools/power turbostat: Fix missing SYS_LPI counter on some Chromebooks tools/power turbostat: Fix 32-bit capabilities warning net/mlx5e: kTLS, Fix TCP seq off-by-1 issue in TX resync flow XArray: Fix xa_find_next for large multi-index entries padata: fix uninitialized return value in padata_replace() brcmfmac: abort and release host after error misc: rtsx: set correct pcr_ops for rts522A misc: pci_endpoint_test: Fix to support > 10 pci-endpoint-test devices misc: pci_endpoint_test: Avoid using module parameter to determine irqtype PCI: sysfs: Revert "rescan" file renames coresight: do not use the BIT() macro in the UAPI header mei: me: add cedar fork device ids nvmem: check for NULL reg_read and reg_write before dereferencing extcon: axp288: Add wakeup support power: supply: axp288_charger: Add special handling for HP Pavilion x2 10 Revert "dm: always call blk_queue_split() in dm_process_bio()" ALSA: hda/ca0132 - Add Recon3Di quirk to handle integrated sound on EVGA X99 Classified motherboard soc: mediatek: knows_txdone needs to be set in Mediatek CMDQ helper net/mlx5e: kTLS, Fix wrong value in record tracker enum iwlwifi: consider HE capability when setting LDPC iwlwifi: yoyo: don't add TLV offset when reading FIFOs iwlwifi: dbg: don't abort if sending DBGC_SUSPEND_RESUME fails rxrpc: Fix sendmsg(MSG_WAITALL) handling IB/hfi1: Ensure pq is not left on waitlist tcp: fix TFO SYNACK undo to avoid double-timestamp-undo watchdog: iTCO_wdt: Export vendorsupport watchdog: iTCO_wdt: Make ICH_RES_IO_SMI optional i2c: i801: Do not add ICH_RES_IO_SMI for the iTCO_wdt device net: Fix Tx hash bound checking padata: always acquire cpu_hotplug_lock before pinst->lock mm: mempolicy: require at least one nodeid for MPOL_PREFERRED Linux 5.4.31 UBUNTU: upstream stable to v5.4.31 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871651/+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 1871874] Re: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure
Ryan, We believe this is a bug as we expect curtin to wipe the disks. In this case it's failing to wipe the disks and occasionally that causes issues with our automation deploying ceph on those disks. This may be more of an issue with LVM and a race condition trying to wipe all of the disks sequentially simply with the large number of disks/vgs/lvs. To clarify from my previous testing, I was mistaken, I thought MAAS used the commissioning OS as the ephemeral OS from which to deploy from, this is not the case. MAAS uses the specified deployment OS as the ephemeral image to deploy from. Based on this all of my previous testing was done with Bionic using the 4.15 kernel. This proves it is a race condition somewhere as sometimes this error does not reproduce and it was just a coincidence that I was changing the commissioning OS. I have tested this morning and have been able to reproduce the issue with bionic 4.15 and xenial 4.4 however I have yet to reproduce it using either bionic or xenial hwe kernels. I will upload the curtin logs and config from my reproducer now. -- 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/1871874 Title: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure Status in curtin package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: For example: Wiping lvm logical volume: /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi wiping 1M on /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi at offsets [0, -1048576] using "lvremove" on ceph-db-wal-dev-sdc/ceph-db-dev-sdi Running command ['lvremove', '--force', '--force', 'ceph-db-wal-dev-sdc/ceph-db-dev-sdi'] with allowed return codes [0] (capture=False) device-mapper: remove ioctl on (253:14) failed: Device or resource busy Logical volume "ceph-db-dev-sdi" successfully removed On a node with 10 disks configured as follows: /dev/sda2 / /dev/sda1 /boot /dev/sda3 /var/log /dev/sda5 /var/crash /dev/sda6 /var/lib/openstack-helm /dev/sda7 /var /dev/sdj1 /srv sdb and sdc are used for BlueStore WAL and DB sdd, sde, sdf: ceph OSDs, using sdb sdg, sdh, sdi: ceph OSDs, using sdc across multiple servers this happens occasionally with various disks. It looks like this maybe a race condition maybe in lvm as curtin is wiping multiple volumes before lvm fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+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 1871874] Re: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure
** Attachment added: "curtin-install.log" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+attachment/5351448/+files/curtin-install.log -- 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/1871874 Title: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure Status in curtin package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: For example: Wiping lvm logical volume: /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi wiping 1M on /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi at offsets [0, -1048576] using "lvremove" on ceph-db-wal-dev-sdc/ceph-db-dev-sdi Running command ['lvremove', '--force', '--force', 'ceph-db-wal-dev-sdc/ceph-db-dev-sdi'] with allowed return codes [0] (capture=False) device-mapper: remove ioctl on (253:14) failed: Device or resource busy Logical volume "ceph-db-dev-sdi" successfully removed On a node with 10 disks configured as follows: /dev/sda2 / /dev/sda1 /boot /dev/sda3 /var/log /dev/sda5 /var/crash /dev/sda6 /var/lib/openstack-helm /dev/sda7 /var /dev/sdj1 /srv sdb and sdc are used for BlueStore WAL and DB sdd, sde, sdf: ceph OSDs, using sdb sdg, sdh, sdi: ceph OSDs, using sdc across multiple servers this happens occasionally with various disks. It looks like this maybe a race condition maybe in lvm as curtin is wiping multiple volumes before lvm fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+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 1871874] Re: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure
** Attachment added: "curtin-install-cfg.yaml" https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+attachment/5351450/+files/curtin-install-cfg.yaml -- 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/1871874 Title: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure Status in curtin package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: For example: Wiping lvm logical volume: /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi wiping 1M on /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi at offsets [0, -1048576] using "lvremove" on ceph-db-wal-dev-sdc/ceph-db-dev-sdi Running command ['lvremove', '--force', '--force', 'ceph-db-wal-dev-sdc/ceph-db-dev-sdi'] with allowed return codes [0] (capture=False) device-mapper: remove ioctl on (253:14) failed: Device or resource busy Logical volume "ceph-db-dev-sdi" successfully removed On a node with 10 disks configured as follows: /dev/sda2 / /dev/sda1 /boot /dev/sda3 /var/log /dev/sda5 /var/crash /dev/sda6 /var/lib/openstack-helm /dev/sda7 /var /dev/sdj1 /srv sdb and sdc are used for BlueStore WAL and DB sdd, sde, sdf: ceph OSDs, using sdb sdg, sdh, sdi: ceph OSDs, using sdc across multiple servers this happens occasionally with various disks. It looks like this maybe a race condition maybe in lvm as curtin is wiping multiple volumes before lvm fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+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 1867983] Re: Computer is freezed after suspend
I had time to bisect kernel: # bad: [af7acadc09d232b50ef83011d9c6368c925ef32f] UBUNTU: Ubuntu-5.3.0-40.32 # good: [1ecdc2a4b15cf2032094966a30bc79992968beb2] UBUNTU: Ubuntu-5.3.0-29.31 git bisect start 'Ubuntu-5.3.0-40.32' 'Ubuntu-5.3.0-29.31' # good: [ec8e731b6b8941cd561eb4cd5f987dbf0268edcb] md/raid0: avoid RAID0 data corruption due to layout confusion. git bisect good ec8e731b6b8941cd561eb4cd5f987dbf0268edcb # bad: [fb787b4169ee66faf0a78488476e0398f5e283a1] spi: gpio: prevent memory leak in spi_gpio_probe git bisect bad fb787b4169ee66faf0a78488476e0398f5e283a1 # good: [b9a9d432b09d1100c8fe3982b4a53b9307f03466] x86/mce: Lower throttling MCE messages' priority to warning git bisect good b9a9d432b09d1100c8fe3982b4a53b9307f03466 # bad: [b268b5877901fa69f4a34e94643108c0bb9112e0] tun: fix data-race in gro_normal_list() git bisect bad b268b5877901fa69f4a34e94643108c0bb9112e0 # bad: [67e07f18209160bbabaf112cfefa4454d299949b] perf jevents: Fix resource leak in process_mapfile() and main() git bisect bad 67e07f18209160bbabaf112cfefa4454d299949b # good: [b5c04c65cafa25745356b85ace1c3b80b8ac5d58] s390/mm: add mm_pxd_folded() checks to pxd_free() git bisect good b5c04c65cafa25745356b85ace1c3b80b8ac5d58 # bad: [99226e3d1768352047769426058c6fb922d05c89] media: rcar_drif: fix a memory disclosure git bisect bad 99226e3d1768352047769426058c6fb922d05c89 # bad: [03edfe2eecb66a0b664f344df9478b0179733ba5] iio: dln2-adc: fix iio_triggered_buffer_postenable() position git bisect bad 03edfe2eecb66a0b664f344df9478b0179733ba5 # bad: [2535c05ffda6d344eb4917178a8ecdf7835e87c2] libata: Ensure ata_port probe has completed before detach git bisect bad 2535c05ffda6d344eb4917178a8ecdf7835e87c2 # good: [be64fadc7c51317046112a4b4c9895575343ced3] net: hns3: add struct netdev_queue debug info for TX timeout git bisect good be64fadc7c51317046112a4b4c9895575343ced3 # first bad commit: [2535c05ffda6d344eb4917178a8ecdf7835e87c2] libata: Ensure ata_port probe has completed before detach It seems that the first bad commit just force ata synchronization. I have no idea how I can test this more for now, but I am available for testing. -- 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/1867983 Title: Computer is freezed after suspend Status in linux package in Ubuntu: Confirmed Bug description: I am using an old HP EliteBook 6930p with current Ubuntu. When the computer is suspended, even after a fresh boot, it does not wake up: the power comes back, but the laptop is frozen, and does not respond to ping. It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42. I am holding kernel purge for now, but this is annoying. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isabelle 1010 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 20:46:35 2020 HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c InstallationDate: Installed on 2015-03-15 (1830 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" 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.3.0-29-generic root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.12 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.27 dmi.chassis.asset.tag: CZC939161W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 6930p dmi.product.sku: J1610781 dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867983/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@li
[Kernel-packages] [Bug 1821564] Re: b44 Ethernet driver null pointer during initialization
iommu=soft does not help, and I don't understand why it would help theoretically when the Core 2 Duo T7400 CPU doesn't have a hardware IOMMU. The problem seems to be that the 64 MB buffer is allocated beyond 1 GB. One theoretical good workaround would be to boot up with only 1 GB and then enable the rest of memory. But I'm not sure how to do that. -- 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/1821564 Title: b44 Ethernet driver null pointer during initialization Status in linux package in Ubuntu: Confirmed Bug description: This problem started after upgrading to Ubuntu 19.04. It was not present with 4.18.0-16-generic kernel and is present in the 4.18.0-15-generic kernel. Ever time during boot there is a null pointer dereference in the b44 driver for the on-board Ethernet on this Dell Inspiron 6400. After that I can log in but networking related commands hang and the computer eventually locks up. Blacklisting the b44 module so it doesn't load works as a workaround, though of course the on board Ethernet can't be used that way. The b43 WiFi still works then. The following is pasted from the log of one crash: 6.483003] BUG: unable to handle kernel NULL pointer dereference at 6.483052] #PF error: [normal kernel read fault] 6.483093] PGD 0 P4D 0 6.483133] Oops: [#1] SMP PTI 6.483175] CPU: 0 PID: 725 Comm: NetworkManager Tainted: GW 5.0.0-7-generic #8-Ubuntu 6.483217] Hardware name: Dell Inc. MM061 /0XD720, BIOS A17 06/13/2007 6.483267] RIP: 0010:swiotlb_tbl_map_single+0x120/0x310 6.483310] Code: 4c 8b 45 a8 4c 8b 1d 0f b2 a9 01 89 d3 45 31 d2 44 8b 4d a4 44 89 c7 41 89 dc 4b 8d 44 25 00 48 21 f0 48 01 f8 49 39 c7 72 0a <47> 39 0c a3 0f 83 cb 00 00 00 42 8d 04 33 48 89 c3 48 39 c1 41 0f 6.483368] RSP: 0018:bc7040c7f3c0 EFLAGS: 00010016 6.483416] RAX: 0001 RBX: RCX: 6.483467] RDX: RSI: 001f RDI: 0001 6.483521] RBP: bc7040c7f420 R08: 0001 R09: 0001 6.483572] R10: R11: R12: 6.483621] R13: R14: 0001 R15: 0020 6.483670] FS: 7f2cb49ccbc0() GS:9d8a4c40() knlGS: 6.483726] CS: 0010 DS: ES: CR0: 80050033 6.483773] CR2: CR3: c72ce000 CR4: 06f0 6.483820] Call Trace: 6.483869] swiotlb_map+0x6c/0x1c0 6.483915] dma_direct_map_page+0xc5/0x160 6.483965] b44_alloc_rx_skb+0x18e/0x3f0 [b44] 6.484013] b44_init_rings+0xbe/0x1b0 [b44] 6.484060] b44_open+0xfc/0x3f0 [b44] 6.484107] __dev_open+0xd4/0x170 6.484153] __dev_change_flags+0x18f/0x200 6.484199] dev_change_flags+0x27/0x60 6.484246] do_setlink+0x31c/0xe30 6.484292] ? __nla_parse+0xf1/0x120 6.484340] ? cpumask_next+0x1b/0x20 6.484388] ? __snmp6_fill_stats64.isra.57+0xf6/0x120 6.484439] ? __nla_parse+0x38/0x120 6.484488] __rtnl_newlink+0x531/0x910 6.484535] ? __nla_put+0x20/0x30 6.484586] ? __kmalloc_node_track_caller+0x1e6/0x2b0 6.484636] ? pskb_expand_head+0x70/0x2e0 6.484693] ? __kmalloc_reserve.isra.53+0x31/0x90 6.484751] ? apparmor_inet_conn_request+0x40/0x40 6.484822] ? security_sock_rcv_skb+0x2f/0x50 6.484879] ? skb_queue_tail+0x43/0x50 6.484934] ? __netlink_sendskb+0x53/0x70 6.484992] ? syscall_return_via_sysret+0xf/0x7f 6.485043] ? __switch_to_asm+0x40/0x70 6.485097] ? syscall_return_via_sysret+0xf/0x7f 6.485153] ? _cond_resched+0x19/0x30 6.485204] ? kmem_cache_alloc_trace+0x153/0x1d0 6.485253] rtnl_newlink+0x48/0x70 6.485301] rtnetlink_rcv_msg+0x213/0x300 6.485348] ? __d_lookup+0x126/0x140 6.485393] ? rtnl_calcit.isra.31+0x100/0x100 6.485440] netlink_rcv_skb+0x4f/0x120 6.485485] rtnetlink_rcv+0x15/0x20 6.485518] netlink_unicast+0x1a1/0x260 6.485518] netlink_sendmsg+0x20d/0x3c0 6.485518] sock_sendmsg+0x3e/0x50 6.485518] ___sys_sendmsg+0x295/0x2f0 6.485518] ? rtnl_unlock+0xe/0x10 6.485518] ? addrconf_sysctl_forward+0x114/0x280 6.485518] ? dev_forward_change+0x140/0x140 6.485518] ? __fget_light+0x54/0x60 6.485518] __sys_sendmsg+0x5c/0xa0 6.485518] __x64_sys_sendmsg+0x1f/0x30 6.485518] do_syscall_64+0x5a/0x110 6.485518] entry_SYSCALL_64_after_hwframe+0x44/0xa9 6.485518] RIP: 0033:0x7f2cb6153cb7 6.485518] Code: 44 00 00 41 54 41 89 d4 55 48 89 f5 53 89 fb 48 83 ec 10 e8 3b ed ff ff 44 89 e2 48 89 ee 89 df 41 89 c0 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 35 44 89 c7 48 89 44 24 08 e8 74 ed ff ff 48 6.485518] RSP: 002b:7ffe93a35c80 EFLAGS: 0293 ORIG_RAX: 002e 6.485518] RAX: ffda RBX: 0008 RCX: 7f2cb6153cb7 6.485518] RDX: RSI:
[Kernel-packages] [Bug 1866319] Re: [focal] fail to reboot when installing focal daily live iso (200227)
Definitely looks like a kernel bug, assigning to linux. @Tai: do you have the version of the kernel that this version of the installer was running? ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Summary changed: - [focal] fail to reboot when installing focal daily live iso (200227) + reboot crash in qla2x00_shutdown() -- 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/1866319 Title: reboot crash in qla2x00_shutdown() Status in subiquity: New Status in linux package in Ubuntu: New Bug description: focal daily live iso (200227) d06 [Steps to Reproduce] 1. Download the daily live iso over http://www.cdimage.ubuntu.com/ubuntu-server/daily-live/20200227/focal-live-server-arm64.iso and boot from the iso 2. Boot into the installation process by selecting "Install Ubuntu Server" 3. Follow the subiquity instruction and update subiquity at the very beginning of the installation[1] 4. Follow the subiquity instruction to complete the installation on reboot. [1] If you don't update it, it will be this bug LP: #1866318 . Prompt of subiquity installation Version 19.12.2+git49.436ee1d7 of the installer is now available (19.10.2 is currently running). [Expected Result] The system reboots and get ready to use. [Actual Result] The system hangs on reboot. Show some of the messages: [FAILED] Failed unmounting /cdrom. [ 790.782440] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [ 790.790955] pstate: 6049 (nZCv daif +PAN -UAO) [ 790.795747] pc : __free_pages+0x28/0x68 [ 790.799578] lr : __iommu_dma_free_pages+0x38/0x58 [ 790.804271] sp : 11eabb00 [ 790.807575] x29: 11eabb00 x28: 803f7abf8ec0 [ 790.812878] x27: x26: 8a3f7b88e130 [ 790.818180] x25: 11156100 x24: 10e10908 [ 790.823481] x23: x22: 803f515ebc80 [ 790.828783] x21: 0010 x20: [ 790.834084] x19: x18: 0010 [ 790.839386] x17: 8158135c x16: db594df8 [ 790.844688] x15: 803f7abf93e8 x14: [ 790.849989] x13: 91eab827 x12: 11eab82f [ 790.855291] x11: 118ef000 x10: [ 790.860592] x9 : 11ae9000 x8 : 07ad [ 790.865894] x7 : 0017 x6 : 11ae8995 [ 790.871196] x5 : 0007 x4 : [ 790.876497] x3 : 11ae8930 x2 : [ 790.881798] x1 : 0034 x0 : [ 790.887101] Call trace: [ 790.889540] __free_pages+0x28/0x68 [ 790.893020] __iommu_dma_free_pages+0x38/0x58 [ 790.897366] __iommu_dma_free+0xb8/0xf8 [ 790.901192] iommu_dma_free+0x48/0x58 [ 790.904848] dma_free_attrs+0xd4/0xf0 [ 790.908546] qla2x00_free_fw_dump+0x58/0xb8 [qla2xxx] [ 790.913616] qla2x00_shutdown+0xd4/0x160 [qla2xxx] [ 790.918402] pci_device_shutdown+0x44/0x88 [ 790.922494] device_shutdown+0x134/0x240 [ 790.926414] kernel_restart_prepare+0x44/0x50 [ 790.930761] kernel_restart+0x20/0x68 [ 790.934414] __do_sys_reboot+0x100/0x228 [ 790.938327] __arm64_sys_reboot+0x2c/0x38 [ 790.942328] el0_svc_common.constprop.0+0xdc/0x1d8 [ 790.947109] el0_svc_handler+0x34/0x90 [ 790.950847] el0_svc+0x10/0x14 [ 790.953898] Code: d503201f 9100d261 52800020 4b0003e0 (b8e0003e) [ 790.960151] ---[ end trace 37539b75957dd46c ]--- [ 790.970536] Unable to handle kernel paging request at virtual address 10075034 [ 790.978440] Mem abort info: [ 790.981223] ESR = 0x9661 [ 790.984267] Exception class = DABT (current EL), IL = 32 bits [ 790.990175] SET = 0, FnV = 0 [ 790.993218] EA = 0, S1PTW = 0 [ 790.996347] Data abort info: [ 790.999217] ISV = 0, ISS = 0x0061 [ 791.003041] CM = 0, WnR = 1 [ 791.005999] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0125b000 [ 791.012689] [10075034] pgd=0a5ff003, pud=0a5fe003, pmd=0a5fd003, pte=00e894110703 [ 850.657602] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 850.663528] rcu: 61-...0: (7 ticks this GP) idle=33a/1/0x4000 softirq=5287/5287 fqs=5638 [ 850.672833] (detected by 3, t=15005 jiffies, g=81461, q=101) [ 850.678569] Task dump for CPU 61: [ 850.681872] shutdown R running task 0 1 0 0x002a [ 850.688909] Call trace: [ 850.691347] __switch_to+0xe4/0x148 [ 850.694823] 0x25 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866319/+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 1866319] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1866319 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1866319 Title: reboot crash in qla2x00_shutdown() Status in subiquity: New Status in linux package in Ubuntu: Incomplete Bug description: focal daily live iso (200227) d06 [Steps to Reproduce] 1. Download the daily live iso over http://www.cdimage.ubuntu.com/ubuntu-server/daily-live/20200227/focal-live-server-arm64.iso and boot from the iso 2. Boot into the installation process by selecting "Install Ubuntu Server" 3. Follow the subiquity instruction and update subiquity at the very beginning of the installation[1] 4. Follow the subiquity instruction to complete the installation on reboot. [1] If you don't update it, it will be this bug LP: #1866318 . Prompt of subiquity installation Version 19.12.2+git49.436ee1d7 of the installer is now available (19.10.2 is currently running). [Expected Result] The system reboots and get ready to use. [Actual Result] The system hangs on reboot. Show some of the messages: [FAILED] Failed unmounting /cdrom. [ 790.782440] Hardware name: Huawei D06 /D06, BIOS Hisilicon D06 UEFI RC0 - V1.20.01 04/26/2019 [ 790.790955] pstate: 6049 (nZCv daif +PAN -UAO) [ 790.795747] pc : __free_pages+0x28/0x68 [ 790.799578] lr : __iommu_dma_free_pages+0x38/0x58 [ 790.804271] sp : 11eabb00 [ 790.807575] x29: 11eabb00 x28: 803f7abf8ec0 [ 790.812878] x27: x26: 8a3f7b88e130 [ 790.818180] x25: 11156100 x24: 10e10908 [ 790.823481] x23: x22: 803f515ebc80 [ 790.828783] x21: 0010 x20: [ 790.834084] x19: x18: 0010 [ 790.839386] x17: 8158135c x16: db594df8 [ 790.844688] x15: 803f7abf93e8 x14: [ 790.849989] x13: 91eab827 x12: 11eab82f [ 790.855291] x11: 118ef000 x10: [ 790.860592] x9 : 11ae9000 x8 : 07ad [ 790.865894] x7 : 0017 x6 : 11ae8995 [ 790.871196] x5 : 0007 x4 : [ 790.876497] x3 : 11ae8930 x2 : [ 790.881798] x1 : 0034 x0 : [ 790.887101] Call trace: [ 790.889540] __free_pages+0x28/0x68 [ 790.893020] __iommu_dma_free_pages+0x38/0x58 [ 790.897366] __iommu_dma_free+0xb8/0xf8 [ 790.901192] iommu_dma_free+0x48/0x58 [ 790.904848] dma_free_attrs+0xd4/0xf0 [ 790.908546] qla2x00_free_fw_dump+0x58/0xb8 [qla2xxx] [ 790.913616] qla2x00_shutdown+0xd4/0x160 [qla2xxx] [ 790.918402] pci_device_shutdown+0x44/0x88 [ 790.922494] device_shutdown+0x134/0x240 [ 790.926414] kernel_restart_prepare+0x44/0x50 [ 790.930761] kernel_restart+0x20/0x68 [ 790.934414] __do_sys_reboot+0x100/0x228 [ 790.938327] __arm64_sys_reboot+0x2c/0x38 [ 790.942328] el0_svc_common.constprop.0+0xdc/0x1d8 [ 790.947109] el0_svc_handler+0x34/0x90 [ 790.950847] el0_svc+0x10/0x14 [ 790.953898] Code: d503201f 9100d261 52800020 4b0003e0 (b8e0003e) [ 790.960151] ---[ end trace 37539b75957dd46c ]--- [ 790.970536] Unable to handle kernel paging request at virtual address 10075034 [ 790.978440] Mem abort info: [ 790.981223] ESR = 0x9661 [ 790.984267] Exception class = DABT (current EL), IL = 32 bits [ 790.990175] SET = 0, FnV = 0 [ 790.993218] EA = 0, S1PTW = 0 [ 790.996347] Data abort info: [ 790.999217] ISV = 0, ISS = 0x0061 [ 791.003041] CM = 0, WnR = 1 [ 791.005999] swapper pgtable: 4k pages, 48-bit VAs, pgdp=0125b000 [ 791.012689] [10075034] pgd=0a5ff003, pud=0a5fe003, pmd=0a5fd003, pte=00e894110703 [ 850.657602] rcu: INFO: rcu_sched detected stalls on CPUs/tasks: [ 850.663528] rcu: 61-...0: (7 ticks this GP) idle=33a/1/0x4000 softirq=5287/5287 fqs=5638 [ 850.672833] (detected by 3, t=15005 jiffies, g=81461, q=101) [ 850.678569] Task dump for CPU 61: [ 850.681872] shutdown R running task 0 1 0 0x002a [ 850.688909] Call trace: [ 850.691347] __switch_to+0xe4/0x148 [ 850.694823] 0x25 To manage notifications about this bug go to: https://bugs.launchpad.net/subiquity/+bug/1866319/+subscriptions -- Mailing list: https://launch
[Kernel-packages] [Bug 1871874] Re: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure
> > Ryan, > We believe this is a bug as we expect curtin to wipe the disks. In this > case it's failing to wipe the disks and occasionally that causes issues > with our automation deploying ceph on those disks. I'm still confused about what the actual error you believe is happening. Note that lvremove is not a fatal error from curtin's perspective because we will be destroying data on the underlying physical disk or partition. Looking at your debug info: 1) your curtin-install.log does not show any failures of lvmremove command 2) if the curtin-install-cfg.yaml is correct, then you've marked wipe: superblock on all of the devices on top of which you build logical volumes. With this setting curtin wipes the logical volume *and* the underlying device. Even if the writes to the lv fail, or if lvremove fails, as long as the underying disk/partition succeed then the LVM metadata and partition table on the disk will be cleared redering the content unusable. Look at sda1 which olds the lv_root LV: shutdown running on holder type: 'lvm' syspath: '/sys/class/block/dm-24' Running command ['dmsetup', 'splitname', 'vgroot-lvroot', '-c', '--noheadings', '--separator', '=', '-o', 'vg_name,lv_name'] with allowed return codes [0] (capture=True) # here we start wiping the logical device by writing 1M of zeros at the # start of the device and at the end of the device Wiping lvm logical volume: /dev/vgroot/lvroot wiping 1M on /dev/vgroot/lvroot at offsets [0, -1048576] # now we remove the lv device and then the vg if it's empty using "lvremove" on vgroot/lvroot Running command ['lvremove', '--force', '--force', 'vgroot/lvroot'] with allowed return codes [0] (capture=False) Logical volume "lvroot" successfully removed Running command ['lvdisplay', '-C', '--separator', '=', '--noheadings', '-o', 'vg_name,lv_name'] with allowed return codes [0] (capture=True) Running command ['pvdisplay', '-C', '--separator', '=', '--noheadings', '-o', 'vg_name,pv_name'] with allowed return codes [0] (capture=True) Running command ['vgremove', '--force', '--force', 'vgroot'] with allowed return codes [0, 5] (capture=False) Volume group "vgroot" successfully removed # now the vg was created from /dev/sda1, here curtin wipes the device with # 1M of zeros at the start and end of this partition Wiping lvm physical volume: /dev/sda1 wiping 1M on /dev/sda1 at offsets [0, -1048576] In the scenario where you see the lvremove command fail, what is the outcome on the system. Does curtin fail the install? Does the install succeed by something after booting into the new system fail? If the latter, what commands fail and can you show the output? -- 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/1871874 Title: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure Status in curtin package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: For example: Wiping lvm logical volume: /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi wiping 1M on /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi at offsets [0, -1048576] using "lvremove" on ceph-db-wal-dev-sdc/ceph-db-dev-sdi Running command ['lvremove', '--force', '--force', 'ceph-db-wal-dev-sdc/ceph-db-dev-sdi'] with allowed return codes [0] (capture=False) device-mapper: remove ioctl on (253:14) failed: Device or resource busy Logical volume "ceph-db-dev-sdi" successfully removed On a node with 10 disks configured as follows: /dev/sda2 / /dev/sda1 /boot /dev/sda3 /var/log /dev/sda5 /var/crash /dev/sda6 /var/lib/openstack-helm /dev/sda7 /var /dev/sdj1 /srv sdb and sdc are used for BlueStore WAL and DB sdd, sde, sdf: ceph OSDs, using sdb sdg, sdh, sdi: ceph OSDs, using sdc across multiple servers this happens occasionally with various disks. It looks like this maybe a race condition maybe in lvm as curtin is wiping multiple volumes before lvm fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+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 1870837] [NEW] BLE not working; hcitool lescan says 'Set scan parameters failed: Input/output error'; Ubuntu 20.04 kernel
You have been subscribed to a public bug: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 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: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 ** Affects: linux (Ubuntu) Importance: Undecided Status: Won't Fix ** Tags: apport-collected focal -- BLE not working; hcitool lescan says 'Set scan parameters failed: Input/output error'; Ubuntu 20.04 kernel https://bugs.launchpad.net/bugs/1870837 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1872122] [NEW] Kernel 4.19+: Bluetooth not working; Ubuntu 20.04
You have been subscribed to a public bug: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 https://bugs.launchpad.net/bugs/1872122 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- 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 1872122] Re: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: New Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1870837] Re: BLE not working; hcitool lescan says 'Set scan parameters failed: Input/output error'; Ubuntu 20.04 kernel
** Package changed: kernel-package (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1870837 Title: BLE not working; hcitool lescan says 'Set scan parameters failed: Input/output error'; Ubuntu 20.04 kernel Status in linux package in Ubuntu: Won't Fix Bug description: Hi, after some testing with Ubuntu 20.04 beta I couldn't get hcitool lescan working. I get the following error: hcitool lescan Set scan parameters failed: Input/output error Bluetooth hardware: hci0: Type: Primary Bus: USB BD Address: 04:EA:56:21:xx:xx ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:1605 acl:0 sco:0 events:123 errors:0 TX bytes:5801 acl:0 sco:0 commands:123 errors:0 Features: 0xbf 0xfe 0x0f 0xfe 0xdb 0xff 0x7b 0x87 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 Link policy: RSWITCH SNIFF Link mode: SLAVE ACCEPT Name: 'xx' Class: 0x200104 Service Classes: Audio Device Class: Computer, Desktop workstation HCI Version: 5.1 (0xa) Revision: 0x100 LMP Version: 5.1 (0xa) Subversion: 0x100 Manufacturer: Intel Corp. (2) It is not hardware related, since I get the same error with a USB bluetooth dongle: hcitool -i hci1 lescan Set scan parameters failed: Input/output error hcitool scan is working fine on both devices; bluetoothctl is also working and able to find ble devices. I would normally prefer bluetoothctl, but I got a software which is based on hcitool. dmesg shows this errors: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! Bluez version: bluez 5.53-0ubuntu2 amd64 System: Distributor ID: Ubuntu Description:Ubuntu Focal Fossa (development branch) Release:20.04 Codename: focal --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu22 Architecture: amd64 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 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: 10/23/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0075.2019.1023.1448 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0075.2019.1023.1448:bd10/23/2019:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems hciconfig: hci0:Type: Primary Bus: USB BD Address: 04:EA:56:21:1E:D3 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17030 acl:0 sco:0 events:2764 errors:0 TX bytes:677849 acl:0 sco:0 commands:2757 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1870837/+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 1872128] [NEW] Broken QCA9377 firmware, no 802.11n support
Public bug reported: /lib/firmware/ath10k/QCA9377/hw1.0/firmware_6.bin Results in no support for 5GHz bands at all, speed limited to about 25 MBit/s /lib/firmware/ath10k/QCA9377/hw1.0/firmware_5.bin Seems to support 5GHz bands, but speed is still stuck at about 25 MBit/s Downloading and installing as firmware_5.bin (and deleting firmware_6.bin): https://github.com/kvalo/ath10k-firmware/blob/master/QCA9377/hw1.0/CNSS.TF.1.0/firmware-5.bin_CNSS.TF.1.0-00267-QCATFSWPZ-1?raw=true speed easily reaches 250MBit/s Firmware tip found on https://www.reddit.com/r/linuxmint/comments/fjkg4x/qualcomm_atheros_qca9377_5ghz_issue/ Router in use is Synology MR2200ac ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 [modified: lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin] ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Apr 10 21:07:20 2020 Dependencies: InstallationDate: Installed on 2017-05-28 (1048 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to focal on 2020-04-04 (6 days ago) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- 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/1872128 Title: Broken QCA9377 firmware, no 802.11n support Status in linux-firmware package in Ubuntu: New Bug description: /lib/firmware/ath10k/QCA9377/hw1.0/firmware_6.bin Results in no support for 5GHz bands at all, speed limited to about 25 MBit/s /lib/firmware/ath10k/QCA9377/hw1.0/firmware_5.bin Seems to support 5GHz bands, but speed is still stuck at about 25 MBit/s Downloading and installing as firmware_5.bin (and deleting firmware_6.bin): https://github.com/kvalo/ath10k-firmware/blob/master/QCA9377/hw1.0/CNSS.TF.1.0/firmware-5.bin_CNSS.TF.1.0-00267-QCATFSWPZ-1?raw=true speed easily reaches 250MBit/s Firmware tip found on https://www.reddit.com/r/linuxmint/comments/fjkg4x/qualcomm_atheros_qca9377_5ghz_issue/ Router in use is Synology MR2200ac ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 [modified: lib/firmware/ath10k/QCA9377/hw1.0/firmware-5.bin] ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Fri Apr 10 21:07:20 2020 Dependencies: InstallationDate: Installed on 2017-05-28 (1048 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: Upgraded to focal on 2020-04-04 (6 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872128/+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 1867983] Re: Computer is frozen after suspend
** Summary changed: - Computer is freezed after suspend + Computer is frozen after suspend -- 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/1867983 Title: Computer is frozen after suspend Status in linux package in Ubuntu: Confirmed Bug description: I am using an old HP EliteBook 6930p with current Ubuntu. When the computer is suspended, even after a fresh boot, it does not wake up: the power comes back, but the laptop is frozen, and does not respond to ping. It is working fine with 5.3.0-29, but not with 5.3.0-40 nor 5.3.0-42. I am holding kernel purge for now, but this is annoying. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isabelle 1010 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Mar 18 20:46:35 2020 HibernationDevice: RESUME=UUID=f606f815-8935-4921-9b8b-e0d8030bb18c InstallationDate: Installed on 2015-03-15 (1830 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: Hewlett-Packard HP EliteBook 6930p PccardctlStatus: Socket 0: 3.3V 16-bit PC Card Subdevice 0 (function 0) bound to driver "pata_pcmcia" 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.3.0-29-generic root=UUID=34085e95-4240-40e4-87fe-18dc9b60b1c1 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-29-generic N/A linux-backports-modules-5.3.0-29-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-11-03 (136 days ago) dmi.bios.date: 07/31/2009 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: 68PCU Ver. F.12 dmi.board.name: 30DB dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 87.27 dmi.chassis.asset.tag: CZC939161W dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCUVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DB:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr: dmi.product.family: 103C_5336AN dmi.product.name: HP EliteBook 6930p dmi.product.sku: J1610781 dmi.product.version: F.12 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867983/+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 1872122] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1872122 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- 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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Incomplete Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1860754] Re: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error]
keep having the same modinfo error on all kernels 5.6.x , running Ubuntu 20.04. modinfo: ERROR: could not get modinfo from 'da903x': No such file or directory On kernel 5.5.16 this modinfo error does not appear. Since the report also have this same message, maybe someone knows something ? -- 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/1860754 Title: ASUS T100HAN boots to a blank screen with a cursor [i965: Failed to submit batchbuffer: Input/output error] Status in linux package in Ubuntu: Incomplete Status in mesa package in Ubuntu: Incomplete Bug description: - After installed Ubuntu 19.10 with nomodeset i915.modeset=0, it won't recognize graphic driver. - run udo apt-get install xserver-xorg-video-intel 0 upgraded, 0 newly installed, 0 to remove and 144 not upgraded. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 14:29:01 2020 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [8086:22b0] (rev 20) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Series PCI Configuration Registers [1043:1bdd] InstallationDate: Installed on 2020-01-24 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0b05:1807 ASUSTek Computer, Inc. USB2.0 Hub Bus 001 Device 002: ID 05e3:0610 Genesys Logic, Inc. 4-port hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. T100HAN ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-26-generic root=/dev/mapper/vgubuntu-root ro nomodeset i915.modeset=0 quiet splash vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/18/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: T100HAN.221 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: T100HAN 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.modalias: dmi:bvnAmericanMegatrendsInc.:bvrT100HAN.221:bd05/18/2016:svnASUSTeKCOMPUTERINC.:pnT100HAN:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnT100HAN:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: T dmi.product.name: T100HAN dmi.product.sku: ASUS-TabletSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860754/+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 1872122] Re: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04
5.6 mainline kernel also does not work. ** Tags added: apport-collected focal ** Description changed: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu26 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: lightdm5081 F pulseaudio + CasperMD5CheckResult: skip + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-04-01 (8 days ago) + InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) + Lsusb: + Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Bus 001 Device 003: ID 0463: MGE UPS Systems UPS + Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB + Bus 001 Device 004: ID 8087:0aaa Intel Corp. + Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + MachineType: Intel(R) Client Systems NUC8i3BEH + Package: linux (not installed) + ProcFB: + + ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 + 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: 03/09/2020 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 + dmi.board.name: NUC8BEB + dmi.board.vendor: Intel Corporation + dmi.board.version: J72693-306 + dmi.chassis.type: 35 + dmi.chassis.vendor: Intel Corporation + dmi.chassis.version: 2.0 + dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: + dmi.product.family: Intel NUC + dmi.product.name: NUC8i3BEH + dmi.product.sku: BOXNUC8i3BEH + dmi.product.version: J72753-305 + dmi.sys.vendor: Intel(R) Client Systems -- 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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip Dist
[Kernel-packages] [Bug 1872122] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351518/+files/AlsaInfo.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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351525/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351523/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351522/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351532/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351529/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351528/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351533/+files/WifiSyslog.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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351530/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351519/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351521/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351527/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351524/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351520/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351526/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1872122] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1872122/+attachment/5351531/+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/1872122 Title: Kernel 4.19+: Bluetooth not working; Ubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: New bug report for kernel: After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports: hcitool lescan Set scan parameters failed: Input/output error When the error occurs, btmon is reporting: > HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058 LE Set Scan Enable (0x08|0x000c) ncmd 1 Status: Command Disallowed (0x0c) Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell: [ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present! [ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present! After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel). The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lightdm5081 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-01 (8 days ago) InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0463: MGE UPS Systems UPS Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Intel(R) Client Systems NUC8i3BEH Package: linux (not installed) ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root 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 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: 03/09/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: BECFL357.86A.0078.2020.0309.1538 dmi.board.name: NUC8BEB dmi.board.vendor: Intel Corporation dmi.board.version: J72693-306 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: Intel NUC dmi.product.name: NUC8i3BEH dmi.product.sku: BOXNUC8i3BEH dmi.product.version: J72753-305 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872122/+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 1871874] Re: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure
Ryan, From the logs the concern is the device or resource busy from meesage: Running command ['lvremove', '--force', '--force', 'vgk/sdklv'] with allowed return codes [0] (capture=False) device-mapper: remove ioctl on (253:5) failed: Device or resource busy Logical volume "sdklv" successfully removed Running command ['lvdisplay', '-C', '--separator', '=', '--noheadings', '-o', 'vg_name,lv_name'] with allowed return codes [0] (capture=True) Curtin does not fail and the node successfully deploys. This is in an integration lab so these hosts (including maas) are stopped, MAAS is reinstalled, and the systems are redeployed without any release or option to wipe during a MAAS release. Then MAAS deploys Bionic on these hosts thinking they are completely new systems but in reality they still have the old volumes configured. MAAS configures the root disk but nothing to the other disks which are provisioned through other automation later. The customer has correlated these to problems configuring ceph after deployment. I have requested further information about exactly the state of the system when it ends up in this case. -- 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/1871874 Title: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure Status in curtin package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: For example: Wiping lvm logical volume: /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi wiping 1M on /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi at offsets [0, -1048576] using "lvremove" on ceph-db-wal-dev-sdc/ceph-db-dev-sdi Running command ['lvremove', '--force', '--force', 'ceph-db-wal-dev-sdc/ceph-db-dev-sdi'] with allowed return codes [0] (capture=False) device-mapper: remove ioctl on (253:14) failed: Device or resource busy Logical volume "ceph-db-dev-sdi" successfully removed On a node with 10 disks configured as follows: /dev/sda2 / /dev/sda1 /boot /dev/sda3 /var/log /dev/sda5 /var/crash /dev/sda6 /var/lib/openstack-helm /dev/sda7 /var /dev/sdj1 /srv sdb and sdc are used for BlueStore WAL and DB sdd, sde, sdf: ceph OSDs, using sdb sdg, sdh, sdi: ceph OSDs, using sdc across multiple servers this happens occasionally with various disks. It looks like this maybe a race condition maybe in lvm as curtin is wiping multiple volumes before lvm fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+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 1834085] Re: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes
Definitely still seeing this, but over 12 hours later I can immediately use the devices again in mainline 5.6.3. dmesg | grep 'magic\|apple' [68065.162639] apple *:*:*.*: unknown main item tag 0x0 [68065.163407] apple *:*:*.*: input,hidraw5: BLUETOOTH HID v0.50 Keyboard [satadru’s keyboard] on *:*:*:*:*:* [68086.650551] magicmouse *:*:*.*: unknown main item tag 0x0 [68086.650753] magicmouse *:*:*.*: input,hidraw6: BLUETOOTH HID v1.60 Mouse [satadru's Trackpad] on *:*:*:*:*:* -- 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/1834085 Title: Bluetooth touchpad (Apple Magic Trackpad) disconnects every few minutes Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got an Apple's Magic Trackpad. I paired it with Ubuntu 18.04.2 LTS and worked out of the box, no special drivers needed. However, I experience frequent disconnections that last a few seconds (5-15 seconds usually), which are quite annoying, as the cursor stops responding during that interval. The trackpad connects by itself after that period. That usually happens every 20-40 minutes. I use the onboard bluetooth device of my laptop. I also have, at the same time, two more bluetooth devices (keyboard and mouse) and they do not experience that issue, just the trackpad. On ocassion I use bluetooth headphones which work just fine. First of all: Using the command "bluetoothctl" I get the following every time I experience a disconnection: [CHG] Device F4:1B:A1:33:F9:8D Connected: no [CHG] Device F4:1B:A1:33:F9:8D Connected: yes Checking "dmesg" I can see more information: (if I am not mistaken, this shows 4 disconnections) [ 1609.070538] magicmouse 0005:05AC:030E.0007: unknown main item tag 0x0 [ 1609.070797] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0007/input/input23 [ 1609.071460] magicmouse 0005:05AC:030E.0007: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 1676.917377] NET: Registered protocol family 38 [ 1872.815348] magicmouse 0005:05AC:030E.0008: unknown main item tag 0x0 [ 1872.815559] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008/input/input24 [ 1872.816248] magicmouse 0005:05AC:030E.0008: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3101.682671] magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 [ 3101.683100] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 [ 3101.683673] magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 [ 3110.683360] magicmouse 0005:05AC:030E.000A: unknown main item tag 0x0 [ 3110.683929] input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:1024/0005:05AC:030E.000A/input/input26 [ 3110.684487] magicmouse 0005:05AC:030E.000A: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 And this is what journalctl -b shows at the moment of the disconnection/reconnection: de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: removing device Apple Wireless Trackpad de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (**) Option "fd" "64" (1,63 m)˜ de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) event16 - Apple Wireless Trackpad: device removed de juny 13 21:37:49 TM1703 gnome-shell[5071]: g_array_unref: assertion 'array' failed de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) UnloadModule: "libinput" de juny 13 21:37:49 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) systemd-logind: releasing fd for 13:80 de juny 13 21:37:49 TM1703 upowerd[1271]: unhandled action 'unbind' on /sys/devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0008 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: unknown main item tag 0x0 de juny 13 21:37:50 TM1703 kernel: input: Apple Wireless Trackpad as /devices/pci:00/:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:05AC:030E.0009/input/input25 de juny 13 21:37:50 TM1703 kernel: magicmouse 0005:05AC:030E.0009: input,hidraw1: BLUETOOTH HID v1.60 Mouse [Apple Wireless Trackpad] on 64:5d:86:86:3f:98 de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) config/udev: Adding input device Apple Wireless Trackpad (/dev/input/mouse1) de juny 13 21:37:50 TM1703 /usr/lib/gdm3/gdm-x-session[4882]: (II) No input driver specified, ignoring this device. de juny 13 21:37:50 TM1703 /usr/lib/gdm3
[Kernel-packages] [Bug 1866909] Comment bridged from LTC Bugzilla
--- Comment From naynj...@ibm.com 2020-04-10 16:15 EDT---
The upstream patch has an additional fix but it?s not critical for GA. It can
get included as part of bug fixes. It also affects only power. The
patch("powerpc/ima: fix secure boot rules in ima arch policy") is posted to
linux-integrity and linuxppc-dev mailing list
(https://lore.kernel.org/linux-integrity/1586549618-6106-1-git-send-email-na...@linux.ibm.com/T/#u)
If there are any issues identified during further testing, they will get
opened as separate issue to be addressed later.
Thanks & Regards,
- Nayna
--
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/1866909
Title:
Ubuntu Kernel Support for OpenPOWER NV Secure & Trusted Boot
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Bug description:
== Comment: #0 - George C. Wilson - 2020-02-25 18:40:44
==
- sysfs enablement: TBD
- ima: arch specific policy support 6191706246de
- platform keyring changes for powerpc: TBD
- Appended signatures support for IMA appraisal
39b07096364a42c516415d5f841069e885234e61
- integrity: Define a trusted platform keyring: 9dc92c45177a
- ima: Support platform keyring for kernel appraisal: d7cecb676dd3
- TPM 2.0 Multibank extend support: c1f92b4b04ad
- TPM 2.0 Eventlog support: 4d23cc323cdb
- ima: carry the measurement list across kexec: d68a6fe9fccf
- kexec_file_load system call support: 500c7ab1a9db
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1866909/+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 1871874] Re: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure
> This is in an integration lab so these hosts (including maas) are stopped, > MAAS is reinstalled, and the systems are redeployed without any release > or option to wipe during a MAAS release. > Then MAAS deploys Bionic on these hosts thinking they are completely new > systems but in reality they still have the old volumes configured. MAAS > configures the root disk but nothing to the other disks which are > provisioned through other automation later. Even with a system as you describe, curtin will erase all metadata as configured. I do not believe that after deployment that any LVM devices will be present on the booted system or found with LVM scan tools. I very much would like to see the curtin install log from the scenario you describe and any "old volumes" that appear configured after the install. If some post-deployment script starts creating VGs and LVs, it's possible the could find some metadata that curtin did not detect (offsets further into the disk. MAAS and curtin aren't responsible for wiping the entire contents of the disk *unless* told to do so. Curtin accepts config like: wipe: zero Which will zero out the entire device (disk, partition, etc). However such wipes may take very long. I do not think this is a useful setting. Instead the post-deployment scripts should be using best-practices, just like curtin does when dealing with reused storage. Note that: 1) LVM tools *warn* when it finds existing metadata 2) All lvm tools include a --zero flag which will remove existing metadata before creating; this is best practice when re-using existing storage. Curtin also pre-wipes disks and partitions at their location in the disk before creating things on top specifically to prevent buried metadata from causing issues when creating new composed devices. So please do find out more details about the post-install deployment. -- 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/1871874 Title: lvremove occasionally fails on nodes with multiple volumes and curtin does not catch the failure Status in curtin package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: For example: Wiping lvm logical volume: /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi wiping 1M on /dev/ceph-db-wal-dev-sdc/ceph-db-dev-sdi at offsets [0, -1048576] using "lvremove" on ceph-db-wal-dev-sdc/ceph-db-dev-sdi Running command ['lvremove', '--force', '--force', 'ceph-db-wal-dev-sdc/ceph-db-dev-sdi'] with allowed return codes [0] (capture=False) device-mapper: remove ioctl on (253:14) failed: Device or resource busy Logical volume "ceph-db-dev-sdi" successfully removed On a node with 10 disks configured as follows: /dev/sda2 / /dev/sda1 /boot /dev/sda3 /var/log /dev/sda5 /var/crash /dev/sda6 /var/lib/openstack-helm /dev/sda7 /var /dev/sdj1 /srv sdb and sdc are used for BlueStore WAL and DB sdd, sde, sdf: ceph OSDs, using sdb sdg, sdh, sdi: ceph OSDs, using sdc across multiple servers this happens occasionally with various disks. It looks like this maybe a race condition maybe in lvm as curtin is wiping multiple volumes before lvm fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/curtin/+bug/1871874/+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 1867916] Re: Regression in kernel 4.15.0-91 causes kernel panic with Bcache
Hi Ryan, that's really great findings, thanks. I'm out on holiday, and will check it next week. -- 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/1867916 Title: Regression in kernel 4.15.0-91 causes kernel panic with Bcache Status in linux package in Ubuntu: In Progress Bug description: After upgrading from kernel 4.15.0-88 to 4.15.0-91 one of our systems does not boot any longer. It always crashes during boot with a kernel panic. I suspect that this crash might be related to Bcache because this is the only one of our systems where we use Bcache and the kernel panic appears right after Bcache initialization. I already checked that this bug still exists in the 4.15.0-92.93 kernel from proposed. Unfortunately, I cannot do a bisect because this is a critical production system and we do not have any other system with a similar configuration. I attached a screenshot with the trace of the kernel panic. The last message that appears before the kernel panic (or rather the last one that I can see - there is a rather long pause between that message and the panic and I cannot scroll up far enough to ensure that there are no other messages in between) is: bcache: register_bcache() error /dev/dm-0: device already registered When booting with kernel 4.15.0-88 that does not have this problem, the next message is bcache: register_bcache() error /dev/dm-12: device already registered (emitting change event) After that the next message is: Begin: Loading essential drivers ... done This message also appears after the kernel panic, but the boot process stalls and the system can only be recovered by doing a hardware reset. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-88-generic 4.15.0-88.88 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Mar 17 21:08 seq crw-rw 1 root audio 116, 33 Mar 17 21:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Wed Mar 18 12:55:18 2020 HibernationDevice: RESUME=UUID=40512ea2-9fce-40f5-8362-5daf955cc26a InstallationDate: Installed on 2013-07-02 (2450 days ago) InstallationMedia: Ubuntu-Server 12.04.2 LTS "Precise Pangolin" - Release amd64 (20130214) MachineType: HP ProLiant DL160 G6 PciMultimedia: ProcFB: 0 mgadrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-88-generic root=/dev/mapper/vg0-root ro nosmt nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw nomdmonddf nomdmonisw RelatedPackageVersions: linux-restricted-modules-4.15.0-88-generic N/A linux-backports-modules-4.15.0-88-generic N/A linux-firmware 1.173.16 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-23 (541 days ago) dmi.bios.date: 11/06/2009 dmi.bios.vendor: HP dmi.bios.version: O33 dmi.chassis.asset.tag: 0191525 dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrO33:bd11/06/2009:svnHP:pnProLiantDL160G6:pvr:cvnHP:ct23:cvr: dmi.product.name: ProLiant DL160 G6 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867916/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Got identical issue on other PC with same kernel version and onboard graphics (i915), also HP. root@gromk:~# inxi -SCGxxxz System:Host: gromk Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Console: tty 4 wm: kwin_x11 dm: SDDM Distro: Ubuntu 19.10 (Eoan Ermine) CPU: Topology: 6-Core model: Intel Core i7-8700 bits: 64 type: MT MCP arch: Kaby Lake rev: A L1 cache: 384 KiB L2 cache: 12.0 MiB L3 cache: 12.0 MiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 76799 Speed: 1539 MHz min/max: 800/4600 MHz Core speeds (MHz): 1: 1539 2: 883 3: 2930 4: 1633 5: 1548 6: 1075 7: 1081 8: 2129 9: 2623 10: 2214 11: 1257 12: 1777 Graphics: Device-1: Intel UHD Graphics 630 vendor: Hewlett-Packard driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3e92 Display: server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa compositor: kwin_x11 resolution: 2560x1440~60Hz, 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes root@gromk:~# > apr 10 23:03:45 gromk kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 apr 10 23:03:45 gromk kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m
[Kernel-packages] [Bug 1847786] Re: Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels
Daniel Monteiro, [10.04.20 21:39] Updating lib/firmware with the ones over https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/i915 makes all the warning go away. -- 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/1847786 Title: Update linux-firmware in bionic for 19.04 and 19.10 hwe kernels Status in linux-firmware package in Ubuntu: Confirmed Bug description: It looks like the hwe kernels need the linux-firmware revved again. update-initramfs: Generating /boot/initrd.img-5.3.0-12-generic W: Possible missing firmware /lib/firmware/i915/icl_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/kbl_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/skl_guc_32.0.3.bin for module i915 W: Possible missing firmware /lib/firmware/i915/icl_huc_ver8_4_3238.bin for module i915 W: Possible missing firmware /lib/firmware/i915/glk_huc_ver03_01_2893.bin for module i915 W: Possible missing firmware /lib/firmware/i915/bxt_huc_ver01_8_2893.bin for module i915 I have a feeling those with broadcom cards will also need a revved firmware in order to acquire bnx2x/bnx2x-e2-7.13.11.0.fw as they will not be able to be used with the 5.3 kernel without it. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1847786/+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 1848771]
The patch should only give more debug output - did you capture anything? -- 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/1848771 Title: Reboot after resume from suspend (deep) Status in linux package in Ubuntu: Incomplete Status in ubuntu-release-upgrader package in Ubuntu: Invalid Bug description: After upgrading to Kubuntu Eoan (19.10) yesterday, my laptop crashes after resume from suspending. This is regardless the way of suspending (closing lid, selecting suspend from sddm, systemctl suspend). The journal shows: ferry@chromium:~$ journalctl -b -1 -e .. sddm[1106]: Message received from greeter: Suspend NetworkManager[836]: manager: sleep: sleep requested (sleeping: no enabled: yes) NetworkManager[836]: device (60:73:BC:BA:B8:68): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (60:73:BC:23:8F:3E): state change: disconnected -> unmanaged (reason ' NetworkManager[836]: device (p2p-dev-wlp1s0): state change: disconnected -> unmanaged (reason 'sle NetworkManager[836]: manager: NetworkManager state is now ASLEEP systemd[1]: Reached target Sleep. systemd[1]: Starting Suspend... systemd-sleep[1238]: Suspending system... kernel: PM: suspend entry (deep) On resume (keypress, open lid) resume starts but immediately crashes and reboots. The laptop is an Acer 720p Chromebook with Chromium replaced and working fine with Kubuntu since 5 years or so. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: ubuntu-release-upgrader-core 1:19.10.15 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: KDE Date: Fri Oct 18 18:45:53 2019 InstallationDate: Installed on 2017-07-13 (826 days ago) InstallationMedia: Kubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: ubuntu-release-upgrader UpgradeStatus: Upgraded to eoan on 2019-10-17 (0 days ago) VarLogDistupgradeTermlog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848771/+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 1869948] Re: Multiple Kexec in AWS Nitro instances fail
I've verified this LP using AWS instances, so the kernel versions I
tested were -aws flavored; this was necessary given the patch proposed
here is related to the ena driver, which manages an AWS exclusive
virtual NIC.
The versions tested were:
4.4.0.1105 xenial-updates
4.4.0.1106 xenial-proposed
4.15.0.1065 bionic-updates
4.15.0.1066 bionic-proposed
5.3.0.1016 eoan-updates (tested with Bionic-HWE analog)
5.3.0.1017 eoan-proposed (tested with Bionic-HWE analog)
The test was based in the [Test] section / comment #3, and I've managed
to reproduce the issue in all versions on -updates, whereas no version
in -proposed showed the issue (20 kexecs succeeded). In the failure
case, in the 2nd or at most 3rd kexec, we've noticed the crash on boot,
initrd corruption. In Xenial (kernel 4.4), due to the "small" size of
initrd, it was needed to install linux-modules-extra to increase the
size of the file and hence expose the memory corruption.
Also, I've checked in all kernels if the symbols added by the patch were
there, with the following command:
# grep "ena_remov\|ena_shut" /proc/kallsyms
c0005690 t __ena_shutoff[ena]
c0005770 t ena_shutdown [ena]
c0005790 t ena_remove [ena]
The above output is from a -proposed kernel; kernels in -updates only
show ena_remove() symbol. Finally, I checked the patch in the generic
flavors trees, for X/B/E/F, and they are present in the latest tag
(corresponding to kernels in -proposed and tag Ubuntu-5.4.0-22.26 for
Focal).
So, I'm hereby marking this LP as verified for all releases. See next comment
for a note about Disco kernel.
Thanks,
Guilherme
** Tags removed: verification-needed-bionic verification-needed-eoan
verification-needed-xenial
** Tags added: verification-done verification-done-bionic
verification-done-eoan verification-done-xenial
--
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/1869948
Title:
Multiple Kexec in AWS Nitro instances fail
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Disco:
Opinion
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
* Currently, users cannot perform multiple kernel kexec loads on AWS Nitro
instances (KVM-based); after the 2nd or 3rd kexec, an initrd corruption is
observed, with the following signature:
Initramfs unpacking failed: junk within compressed archive
[...]
Kernel panic - not syncing: No working init found.
Try passing init= option to kernel. See Linux
Documentation/admin-guide/init.rst for guidance.
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.5.0-rc7-gpiccoli+ #26 Hardware
name: Amazon EC2 t3.large/, BIOS 1.0 10/16/2017
Call Trace:
dump_stack+0x6d/0x9a
? csum_partial_copy_generic+0x150/0x170
panic+0x101/0x2e3
? do_execve+0x25/0x30
? rest_init+0xb0/0xb0
kernel_init+0xfb/0x100
ret_from_fork+0x35/0x40
* After investigation (see comment 2), it was noticed the Amazon ena
network driver doesn't provide a shutdown() handler, hence it could be
performing a DMA transaction to a previous valid address during boot,
which would then corrupt kernel memory. The following patch was
proposed and fixed the issue, allowing 1000 kexecs to be executed
successfully with no issues observed: 428c491332bc("net: ena: Add PCI
shutdown handler to allow safe kexec") [
git.kernel.org/linus/428c491332bc ].
* Hence, we are hereby requesting SRU for this patch. It was tested in
all supported series (4.4, 4.15 and 5.3) in Amazon Nitro instances
with success, and reviewed/acked by ena driver team and a kexec
developer from other distro. Worth mentioning that we proposed an
upstream multi-vendor discussion about this issue:
marc.info/?l=kexec&m=158299605013194
[Test case]
* The basic test procedure is about performing multiple kexecs
sequentially; AWS does not provide a full console, so in case of
failures one could check the instance screenshot or use pstore/ramoops
in order to collect dmesg after a crash in a preserved memory area.
The commands used to perform kexec are:
kexec -l --initrd --reuse-cmdline
systemctl kexec
Alternatively, one could user "--append=" instead of "--reuse-cmdline"
if a change in kexec command-line is desired; also, to execute the
kexec-loaded kernel both "kexec -e" and "systemctl kexec" are equally
valid.
* On comment 3 we proposed a script/approach to auto-test kexecs, used
here to perform 1000 kexecs with the proposed patch.
[Regression Potential]
* Although the patch proposed here introduce a PCI handler, it kept
the remove handler identical and based shutdown strongly on
ena_remove(), changing just netdev handli
[Kernel-packages] [Bug 1869948] Re: Multiple Kexec in AWS Nitro instances fail
Regarding Disco, despite the "Fix Committed" status I didn't find the
patch in the latest tags from generic tree (Ubuntu-5.0.0-46.50) nor AWS
tree (Ubuntu-aws-5.0.0-1024.27), so I think the patch wasn't merged
(which is not a big deal, given Bionic HWE is now based on 5.3).
I've reverted the "Fix Committed" status, let me know if we should de-
nominate Disco.
Thanks,
Guilherme
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Opinion
--
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/1869948
Title:
Multiple Kexec in AWS Nitro instances fail
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Disco:
Opinion
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
* Currently, users cannot perform multiple kernel kexec loads on AWS Nitro
instances (KVM-based); after the 2nd or 3rd kexec, an initrd corruption is
observed, with the following signature:
Initramfs unpacking failed: junk within compressed archive
[...]
Kernel panic - not syncing: No working init found.
Try passing init= option to kernel. See Linux
Documentation/admin-guide/init.rst for guidance.
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.5.0-rc7-gpiccoli+ #26 Hardware
name: Amazon EC2 t3.large/, BIOS 1.0 10/16/2017
Call Trace:
dump_stack+0x6d/0x9a
? csum_partial_copy_generic+0x150/0x170
panic+0x101/0x2e3
? do_execve+0x25/0x30
? rest_init+0xb0/0xb0
kernel_init+0xfb/0x100
ret_from_fork+0x35/0x40
* After investigation (see comment 2), it was noticed the Amazon ena
network driver doesn't provide a shutdown() handler, hence it could be
performing a DMA transaction to a previous valid address during boot,
which would then corrupt kernel memory. The following patch was
proposed and fixed the issue, allowing 1000 kexecs to be executed
successfully with no issues observed: 428c491332bc("net: ena: Add PCI
shutdown handler to allow safe kexec") [
git.kernel.org/linus/428c491332bc ].
* Hence, we are hereby requesting SRU for this patch. It was tested in
all supported series (4.4, 4.15 and 5.3) in Amazon Nitro instances
with success, and reviewed/acked by ena driver team and a kexec
developer from other distro. Worth mentioning that we proposed an
upstream multi-vendor discussion about this issue:
marc.info/?l=kexec&m=158299605013194
[Test case]
* The basic test procedure is about performing multiple kexecs
sequentially; AWS does not provide a full console, so in case of
failures one could check the instance screenshot or use pstore/ramoops
in order to collect dmesg after a crash in a preserved memory area.
The commands used to perform kexec are:
kexec -l --initrd --reuse-cmdline
systemctl kexec
Alternatively, one could user "--append=" instead of "--reuse-cmdline"
if a change in kexec command-line is desired; also, to execute the
kexec-loaded kernel both "kexec -e" and "systemctl kexec" are equally
valid.
* On comment 3 we proposed a script/approach to auto-test kexecs, used
here to perform 1000 kexecs with the proposed patch.
[Regression Potential]
* Although the patch proposed here introduce a PCI handler, it kept
the remove handler identical and based shutdown strongly on
ena_remove(), changing just netdev handling following other upstream
drivers. It was extensively tested and presented no issue. Also, it's
self-contained and affect only one driver, so any other cloud
providers or non-cloud environment wouldn't be even affected by the
patch.
* In case of a potential regression, it could manifest as a delay or
issue on reboot/shutdown path, only if ena driver is in use.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869948/+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 1864061] Re: PCI/internal sound card not detected
For what it's worth, my audio devices all still appear as "dummy output" on my Dell G3 15 3590 running 5.3.0-46-generic. Sound works perfectly on 5.3.0-40 and before. I have not applied any workarounds to the system. Please let me know what I can do to help debug. -- 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/1864061 Title: PCI/internal sound card not detected Status in linux package in Ubuntu: Invalid 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: The sof-pci-dev and snd-soc-skl all contains the same pciid, if the soc-skl is loaded ahead of sof-pci-dev, the sof driver will not work anymore, in the oem project, we manually put the soc-skl in the blacklist. From kernel-5.4 (focal kernel), the driver soc-skl is disabled by default, and there is no users report any issues on it. So let us disable soc-skl in the eoan and osp1 kernel too. The patch for eoan kernel doesn't remove the modules because looks like the abi folder are not controlled by git. This will break the modulecheck, so if this patch could be merged, please help remove those modules: snd-soc-skl snd-soc-skl-ipc snd-soc-skl-ssp-clk [Impact] If soc-skl driver is loaded ahead of sof driver, the sof could not work anymore, we need to blacklist the soc-skl manually [Fix] Like the focal kernel, we disable the soc_skl driver in the kernel config [Test Case] Tested on Lenovo and Dell machines which has dmic, the sof driver could be loaded successfully. Tested on the machinces without the dmic, the legacy hda driver worked well as before. [Regression Risk] Low, Focal kernel and mainine-5.5, 5.6-rc kernel all disabled this dirver; and We have not met a machine need the soc_skl driver yet; and Intel claim that the sof could replace the soc_skl driver. In the -41 kernel, we introduced a patch from stable kernel, that make the sof driver crash, and there is a fix patch in the 5.6-rc1, and this fix patch is already in the stable and is merged to focal kernel, now we backport this patch to Eoan kernel if -42 doesn't introduce this fix patch from stable. The patch introduced the crash: commit 063821115e02229d5fd3de31bad270d5e30aeb41 Author: Dragos Tarcatu Date: Mon Dec 9 18:39:38 2019 -0600 ASoC: topology: Check return value for snd_soc_add_dai_link() BugLink: https://bugs.launchpad.net/bugs/1861929 [ Upstream commit 76d2703649321c296df7ec0dafd50add96215de4 ] snd_soc_add_dai_link() might fail. This situation occurs for instance in a very specific use case where a PCM device and a Back End DAI link are given identical names in the topology. When this happens, soc_new_pcm_runtime() fails and then snd_soc_add_dai_link() returns -ENOMEM when called from soc_tplg_fe_link_create(). Because of that, the link will not get added into the card list, so any attempt to remove it later ends up in a panic. Fix that by checking the return status and free the memory in case of an error. Reviewed-by: Ranjani Sridharan Signed-off-by: Dragos Tarcatu Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191210003939.15752-2-pierre-louis.boss...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Kamal Mostafa Signed-off-by: Khalid Elmously [Impact] During the boot, the sof driver crash because the hdmi_pcm_list is not initialized before it is used. [Fix] This bug is fixed in the mainline kernel v5.6-rc1, now backport this patch to ubuntu kernel [Test Case] Boot the -41 kernel with this patch added. blacklist the snd_soc_skl the kernel can boot successfully, and sof driver worked well [Regression Risk] Low, the patches are backported from upstream kernel, and I tested this patch on Lenovo and Dell dmic machines. Focal kernel already has this patch and works well. Probably a kernel bug. The sound card isn't detected in 5.3.0-41-generic Booting 5.3.0-40-generic does work. The relevant dmesg message is: [9.845441] skl_hda_dsp_generic skl_hda_dsp_generic: Unsupported HDAudio/iDisp configuration found [9.845447] skl_hda_dsp_generic: probe of skl_hda_dsp_generic failed with error -22 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-41.33-generic 5.3.18 Uname: Linux 5.3.0-41-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/d
[Kernel-packages] [Bug 1518408] Re: Interrupt audio on bluetooth headset when wifi is on
I have symptoms of this same problem in Pop!_OS 19.10. Bluetooth audio connections stutter, skip or disconnect entirely during moderate to heavy wifi use. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1518408 Title: Interrupt audio on bluetooth headset when wifi is on Status in bcmwl package in Ubuntu: Expired Status in broadcom-sta package in Ubuntu: Expired Bug description: When WiFi and Bluetooth is on, this have conflict! Sound on bluetooth headset is interrupted, ping is high. In syslog: Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology Corp. ) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 20 20:55:20 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1518408/+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 1518408] Re: Interrupt audio on bluetooth headset when wifi is on
However, my problem involves Intel 9650 Wifi/BT adapter not a Broadcom adapter. If it is the same bug, then perhaps it is a configuration issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1518408 Title: Interrupt audio on bluetooth headset when wifi is on Status in bcmwl package in Ubuntu: Expired Status in broadcom-sta package in Ubuntu: Expired Bug description: When WiFi and Bluetooth is on, this have conflict! Sound on bluetooth headset is interrupted, ping is high. In syslog: Nov 20 20:28:22 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 3939657 us (= 694952 bytes) in audio stream Nov 20 20:28:30 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 90008 us (= 15876 bytes) in audio stream Nov 20 20:28:33 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1229297 us (= 216844 bytes) in audio stream Nov 20 20:28:36 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1114638 us (= 196620 bytes) in audio stream Nov 20 20:28:47 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 888216 us (= 156680 bytes) in audio stream Nov 20 20:28:51 Photonix-Laptop pulseaudio[1250]: [bluetooth] module-bluez5-device.c: Skipping 1772705 us (= 312704 bytes) in audio stream Chip Broadcom 43142 Combo with Bluetooth (ID 04ca:2009 Lite-On Technology Corp. ) ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: bcmwl-kernel-source 6.30.223.248+bdcom-0ubuntu7 ProcVersionSignature: Ubuntu 4.2.0-18.22-generic 4.2.3 Uname: Linux 4.2.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: Unity Date: Fri Nov 20 20:55:20 2015 InstallationDate: Installed on 2015-11-20 (0 days ago) InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) SourcePackage: bcmwl UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1518408/+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 1850654] Re: update-initramfs complains of missing amdgpu firmware files
Hello, I have just installed a fresh Kubuntu 18.04.4 on a Dell Laptop 5575, with a AMD Ryzen 7 2700U with Radeon Vega Mobile Gfx running Kernel 5.3.0-46-generic. I was update-ing the initramfs. update-initramfs: Generating /boot/initrd.img-5.3.0-46-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1872161] [NEW] watchdog: BUG: soft lockup - CPU#4 stuck for 28s! [modprobe:2860]
Public bug reported: Bug report pop up. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js 1094 F pulseaudio CasperMD5CheckResult: skip Date: Sat Apr 11 00:53:06 2020 Failure: oops InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp0s1no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=945abbf8-e4ff-4314-b4cd-6678479836c5 ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#4 stuck for 28s! [modprobe:2860] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.0 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.0:cvnQEMU:ct1:cvrpc-q35-5.0: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.0 dmi.sys.vendor: QEMU ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-kerneloops focal kernel-driver-raid6.pq kernel-oops -- 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/1872161 Title: watchdog: BUG: soft lockup - CPU#4 stuck for 28s! [modprobe:2860] Status in linux package in Ubuntu: New Bug description: Bug report pop up. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js 1094 F pulseaudio CasperMD5CheckResult: skip Date: Sat Apr 11 00:53:06 2020 Failure: oops InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp0s1no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=945abbf8-e4ff-4314-b4cd-6678479836c5 ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#4 stuck for 28s! [modprobe:2860] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.0 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.0:cvnQEMU:ct1:cvrpc-q35-5.0: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872161/+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 1872161] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1872161 Title: watchdog: BUG: soft lockup - CPU#4 stuck for 28s! [modprobe:2860] Status in linux package in Ubuntu: Confirmed Bug description: Bug report pop up. ProblemType: KernelOops DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-21-generic 5.4.0-21.25 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 Annotation: Your system might become unstable now and might need to be restarted. ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: js 1094 F pulseaudio CasperMD5CheckResult: skip Date: Sat Apr 11 00:53:06 2020 Failure: oops InstallationDate: Installed on 2020-04-10 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) IwConfig: lono wireless extensions. enp0s1no wireless extensions. Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (Q35 + ICH9, 2009) ProcFB: 0 virtio_gpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-21-generic root=UUID=945abbf8-e4ff-4314-b4cd-6678479836c5 ro quiet splash noibrs noibpb nopti nospectre_v2 nospectre_v1 l1tf=off nospec_store_bypass_disable no_stf_barrier mds=off mitigations=off vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: kerneloops-daemon N/A RfKill: SourcePackage: linux Title: watchdog: BUG: soft lockup - CPU#4 stuck for 28s! [modprobe:2860] UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: rel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-q35-5.0 dmi.modalias: dmi:bvnSeaBIOS:bvrrel-1.13.0-0-gf21b5a4aeb02-prebuilt.qemu.org:bd04/01/2014:svnQEMU:pnStandardPC(Q35+ICH9,2009):pvrpc-q35-5.0:cvnQEMU:ct1:cvrpc-q35-5.0: dmi.product.name: Standard PC (Q35 + ICH9, 2009) dmi.product.version: pc-q35-5.0 dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872161/+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 1872009] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: eoan -- 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/1872009 Title: System Freeze with "Resetting rcs0 for hang on rcs0" Status in linux package in Ubuntu: Confirmed Bug description: * The problem started with linux kernel 5.3.0-46 * When the screen (GPU?) is used intensively, I can hear coil noise from my laptop (Dell XPS 13) and then the whole system will freeze during 5-6 seconds. During freeze I can move the mouse cursor, but nothing else is responding. During freeze, the noise stops. Then the systems comes back to normal for a few seconds (randomly from 10sec to 1 minute), and then the freeze repeats again and again. * According to my experience, I would strongly bet that the coil noise is due to graphics. * The hang is reported in the dmesg log: [ 64.369654] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 64.370664] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 162.345195] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 192.360856] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 206.312567] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 230.343937] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 254.343235] i915 :00:02.0: Resetting rcs0 for hang on rcs0 * I have a small demo which uses the GPU intensively (via the SDL library) and I can repeat the freeze easily by running it. * The problem does *not* occur with 5.3.0-45-generic (no noise, no freeze) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872009/+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 1871867] Re: i915: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
Using the `mainline` utility from https://launchpad.net/~cappelikan/+archive/ubuntu/ppa I now installed a mainline kernel version 5.4.28-050428-generic - the latest currently available in the 5.4 series. Using this kernel, I don't experience this issue at all - no hangs, not even during the use of IntelliJ. I tested it for a couple of hours in which I normally had dozens of hangs. If it helps diagnosing this issue, I'm willing to bisect the issue with various mainline versions between 5.3.0-47 and 5.4.28. Let me know if this has any value. For now I'm sticking with this new kernel version. Not sure if related - I did have an additional issue with the graphics. Directly after boot, but also after suspend, during connecting to wifi, I'd get loads of the `iwlwifi :3b:00.0: Unhandled alg: 0x71b` messages and the display would also freeze for couple of seconds (10 - 20). During this specific freeze, the mouse pointer would also be unresponsive. This would be accompanied by loads of messages in the kernel log like: nouveau :01:00.0: fifo: SCHED_ERROR 08 [] I managed to fix this by adding nouveau.modeset=0 to the kernel command line. Like I said, I don't know if these are related. Does the i915 GPU hang also occur on laptops without a nvidia gpu? -- 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/1871867 Title: i915: GPU HANG: ecode 9:0:0x, hang on rcs0 Status in linux package in Ubuntu: Confirmed Bug description: I just installed Kubuntu 19.10 on my brand new Dell XPS 15 7590 laptop. The display freezes quite regularly for a couple of seconds. In that period, the mouse pointer does move, but nothing else happens: I cannot interact, move windows, scroll, type or whatever. Afterwards the system becomes responsive again. In the kernel log I see messages like: [ 2110.867998] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 [ 2110.869007] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 2120.523573] iwlwifi :3b:00.0: Unhandled alg: 0x71b [ 2146.443128] iwlwifi :3b:00.0: Unhandled alg: 0x71b [ 2173.551329] iwlwifi :3b:00.0: Unhandled alg: 0x71b [ 2204.008717] iwlwifi :3b:00.0: Unhandled alg: 0x71b [ 4404.960469] i915 :00:02.0: Resetting rcs0 for hang on rcs0 [ 6020.935285] i915 :00:02.0: Resetting rcs0 for hang on rcs0 I found that this problem occurs significantly more frequent when I'm using Jetbrains IntelliJ IDE, but I did experience it in several other occassions as well. I found similar reports both in UBuntu as other places that seem to be related: https://bugs.launchpad.net/ubuntu/+source/linux-signed-5.4/+bug/1863087 https://bugs.freedesktop.org/show_bug.cgi?id=111805 https://bugs.archlinux.org/task/64725 https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1862865 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395 The ones on Launchpad are marked as invalid for Eoan and only apply for Focal. The XPS 7590 has a Intel chip and nvidia chip, I'm experiencing the problem both with and without the nvidia driver loaded. I ran apport when it wasn't loaded to make sure the kernel isn't tainted with it. Based on the feedback I see that this may be fixed in the most recent releases of kernel 5.4 (>= 5.4.0-17) but I don't see a proper way to install this in Eoan. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-47-generic 5.3.0-47.39 ProcVersionSignature: Ubuntu 5.3.0-47.39-generic 5.3.18 Uname: Linux 5.3.0-47-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: evdwal 1280 F pulseaudio CurrentDesktop: KDE Date: Thu Apr 9 17:25:04 2020 InstallationDate: Installed on 2020-04-06 (2 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcFB: 0 i915drmfb ProcKernelCmdLine: \\vmlinuz-5.3.0-47-generic root=/dev/mapper/vgkubuntu-root ro quiet splash net.ifnames=0 biosdevname=0 vt.handoff=7 initrd=\initrd.img-5.3.0-47-generic RelatedPackageVersions: linux-restricted-modules-5.3.0-47-generic N/A linux-backports-modules-5.3.0-47-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.5.0 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.5.0:bd12/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. To manag
[Kernel-packages] [Bug 1865570] Re: suspend only works once on ThinkPad X1 Carbon gen 7
** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1865570 Title: suspend only works once on ThinkPad X1 Carbon gen 7 Status in linux package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Eoan: Fix Committed 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: Won't Fix Bug description: === SRU Justification Fix=== [Impact] Some ThinkPads failed to suspend to s2idle when ethernet disconnected. [Fix] I219 chip of some platforms is controlled by ME, which needs more time when setting ULP mode. Wait for ME to finish setting ULP mode. [Test] Verified on hw, and user reported s2idle works. [Regression Potential] Low, Increase timeout and breaks with condition, no impacts for who don't need this long wait. Bionic doesn't introduce the commit f15bb6dde738cc8fa0, no need for this. === SRU Justification === [Impact] Lenovo X1 Carbon 7th can only susped (s2idle) once, subsquent suspends are blocked by failed e1000e resume routine. [Fix] It's not root caused yet by Intel, so disable the s0ix flow on X1 Carbon 7th as a temporary workaround. [Test] After applying the DMI quirk patch, e1000e keeps working, so it doesn't block s2idle anymore. User also confimred the workaround works. [Regression Potential] Low. It limits to a specific model, and I can confirm s0ix can still be reached withouth this feature. === Original Bug Report === 5.4.0-16 and 5.4.0-17 go to suspend when the lid is closed, but *only once* after boot. On subsequent attempts, when the lid it closed, backlight and wifi are turned off, but system does not suspend. First successful suspend: [ 147.413295] PM: suspend entry (s2idle) [ 147.416601] Filesystems sync: 0.003 seconds [ 147.419371] Freezing user space processes ... (elapsed 0.001 seconds) done. [ 147.421210] OOM killer disabled. [ 147.421210] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [ 147.422375] printk: Suspending console(s) (use no_console_suspend to debug) [ 147.422630] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 147.527810] e1000e: EEE TX LPI TIMER: 0011 [ 150.246317] ACPI: EC: interrupt blocked [ 881.134544] ACPI: EC: interrupt unblocked [ 883.933255] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.047802] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 884.112730] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 886.815475] e1000e :00:1f.6 enp0s31f6: PHY Wakeup cause - Unicast Packet [ 887.485832] e1000e :00:1f.6 enp0s31f6: Hardware Error [ 888.016931] OOM killer enabled. [ 888.016932] Restarting tasks ... done. [ 888.060613] PM: suspend exit Second unsuccessful suspend: [ 907.584802] PM: suspend entry (s2idle) [ 907.589779] Filesystems sync: 0.004 seconds [ 907.591416] Freezing user space processes ... (elapsed 0.002 seconds) done. [ 907.593518] OOM killer disabled. [ 907.593518] Freezing remaining freezable tasks ... (elapsed 0.328 seconds) done. [ 907.921560] printk: Suspending console(s) (use no_console_suspend to debug) [ 907.922127] wlp0s20f3: deauthenticating from 18:d6:c7:61:95:c2 by local choice (Reason: 3=DEAUTH_LEAVING) [ 908.024438] e1000e: EEE TX LPI TIMER: 0011 [ 909.916364] PM: pci_pm_suspend(): e1000e_pm_suspend+0x0/0x80 [e1000e] returns -2 [ 909.916367] PM: dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -2 [ 909.916369] PM: Device :00:1f.6 failed to suspend async: error -2 [ 911.183052] PM: Some devices failed to suspend, or early wake event detected [ 911.197091] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.314903] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 911.382438] iwlwifi :00:14.3: FW already configured (0) - re-configuring [ 911.413624] OOM killer enabled. [ 911.413625] Restarting tasks ... done. [ 911.462021] PM: suspend exit It looks like Ethernet driver prevents suspend. Ethernet is not connected (I do not have the adaptor). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1865570/+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 1871300] Re: Fix authentication fail on Realtek WiFi 8723de
** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871300 Title: Fix authentication fail on Realtek WiFi 8723de Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Committed Status in linux source package in Focal: Incomplete Status in linux-oem-osp1 source package in Focal: Won't Fix Bug description: [Impact] When Realtek WiFi 8723de tries to authenticate, the AP may return the exchanged key is wrong, either by "Reason 2" or "Reason 23". [Fix] 8723de specific fix to make sure auth TX is sent out and can be received by AP. [Test] Loop to connect/disconnect as a reproducer. After applying the fix, it can re-connect just fine over 1 times. [Regression Potential] Low. It's tested by Realtek internally, and they also made sure the other two supported chip, 8822BE and 8822CE, work correctly. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1871300/+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 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Experiencing the exact same problem on a Dell XPS 13 9630 since upgrade to kernel 5.3.0-46. When problem is triggered, I can still move the mouse pointer for 2-3 seconds but can't interact with the desktop or any apps (clicking or typing does nothing). After that the mouse pointer stops for about a second. And then it all comes back; the clicks and keys that I types during the freeze comes flushing back... Also noticed that when I'm on a telco, sound and video is completely unaffected throughout the freeze. System info --> inxi -SCGxxxz System: Host: Dinky Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 9.2.1 Desktop: Gnome 3.34.3 wm: gnome-shell dm: GDM3 3.34.1 Distro: Ubuntu 19.10 (Eoan Ermine) CPU: Topology: Dual Core model: Intel Core i7-7500U bits: 64 type: MT MCP arch: Kaby Lake rev: 9 L2 cache: 4096 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 23199 Speed: 600 MHz min/max: 400/3500 MHz Core speeds (MHz): 1: 600 2: 600 3: 600 4: 600 Graphics: Device-1: Intel HD Graphics 620 vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:5916 Display: x11 server: X.Org 1.20.5 driver: i915 compositor: gnome-shell resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel HD Graphics 620 (Kaby Lake GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes >From kernel.log: Apr 10 09:21:50 Dinky kernel: [40438.893463] i915 :00:02.0: Resetting rcs0 for hang on rcs0 -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USER
[Kernel-packages] [Bug 1853969] Re: usbhid 1-3.1:1.1: can't add hid device: -32
apport information
** Tags added: apport-collected
** Description changed:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
+ ---
+ ProblemType: Bug
+ ApportVersion: 2.20.11-0ubuntu8.8
+ Architecture: amd64
+ AudioDevicesInUse:
+ USERPID ACCESS COMMAND
+ /dev/snd/controlC1: juergh 3461 F pulseaudio
+ /dev/snd/controlC0: juergh 3461 F pulseaudio
+ DistroRelease: Ubuntu 19.10
+ InstallationDate: Installed on 2017-05-25 (1050 days ago)
+ InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
+ MachineType: HP HP Pavilion Desktop PC 570-p0XX
+ Package: linux (not installed)
+ ProcFB: 0 i915drmfb
+ ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
+ ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
+ 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.3.0-46-generic N/A
+ linux-backports-modules-5.3.0-46-generic N/A
+ linux-firmware1.183.5
+ Tags: eoan
+ Uname: Linux 5.3.0-46-generic x86_64
+ UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
+ UserGroups:
+
+ _MarkForUpload: True
+ dmi.bios.date: 07/01/2019
+ dmi.bios.vendor: AMI
+ dmi.bios.version: F.43
+ dmi.board.asset.tag: CNV7030RH4
+ dmi.board.name: 82F2
+ dmi.board.vendor: HP
+ dmi.board.version: 00
+ dmi.chassis.asset.tag: CNV7030RH4
+ dmi.chassis.type: 3
+ dmi.chassis.vendor: HP
+ dmi.modalias:
dmi:bvnAMI:bvrF.43:bd07/01/2019:svnHP:pnHPPavilionDesktopPC570-p0XX:pvr:rvnHP:rn82F2:rvr00:cvnHP:ct3:cvr:
+ dmi.product.family: 10
[Kernel-packages] [Bug 1853969] CRDA.txt
apport information
** Attachment added: "CRDA.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351072/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
UserGroups:
[Kernel-packages] [Bug 1853969] Lspci.txt
apport information
** Attachment added: "Lspci.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351075/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
UserGroups
[Kernel-packages] [Bug 1853969] ProcEnviron.txt
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351079/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
[Kernel-packages] [Bug 1853969] ProcCpuinfoMinimal.txt
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351078/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25
[Kernel-packages] [Bug 1853969] ProcModules.txt
apport information
** Attachment added: "ProcModules.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351081/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
[Kernel-packages] [Bug 1853969] Lsusb.txt
apport information
** Attachment added: "Lsusb.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351076/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
UserGroups
[Kernel-packages] [Bug 1853969] IwConfig.txt
apport information
** Attachment added: "IwConfig.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351074/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
Use
[Kernel-packages] [Bug 1853969] ProcCpuinfo.txt
apport information
** Attachment added: "ProcCpuinfo.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351077/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
[Kernel-packages] [Bug 1853969] ProcInterrupts.txt
apport information
** Attachment added: "ProcInterrupts.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351080/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 day
[Kernel-packages] [Bug 1853969] CurrentDmesg.txt
apport information
** Attachment added: "CurrentDmesg.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351073/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ag
[Kernel-packages] [Bug 1853969] WifiSyslog.txt
apport information
** Attachment added: "WifiSyslog.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351084/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
[Kernel-packages] [Bug 1853969] UdevDb.txt
apport information
** Attachment added: "UdevDb.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351083/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
UserGrou
[Kernel-packages] [Bug 1853969] RfKill.txt
apport information
** Attachment added: "RfKill.txt"
https://bugs.launchpad.net/bugs/1853969/+attachment/5351082/+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/1853969
Title:
usbhid 1-3.1:1.1: can't add hid device: -32
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Eoan:
Confirmed
Status in linux source package in Focal:
Confirmed
Bug description:
A keyboard behind an USB hub no longer works after upgrading to Eoan
5.3.
Linux gollum 5.3.0-24-generic #26-Ubuntu SMP Thu Nov 14 01:33:18 UTC
2019 x86_64 x86_64 x86_64 GNU/Linux
Nov 18 07:48:34 gollum kernel: [9.144253] usb 1-3: new high-speed USB
device number 8 using xhci_hcd
Nov 18 07:48:34 gollum kernel: [9.292393] usb 1-3: New USB device found,
idVendor=058f, idProduct=6254, bcdDevice= 1.00
Nov 18 07:48:34 gollum kernel: [9.292395] usb 1-3: New USB device
strings: Mfr=0, Product=0, SerialNumber=0
Nov 18 07:48:34 gollum kernel: [9.293996] hub 1-3:1.0: USB hub found
Nov 18 07:48:34 gollum kernel: [9.294046] hub 1-3:1.0: 4 ports detected
Nov 18 07:48:35 gollum kernel: [9.588233] usb 1-3.1: new low-speed USB
device number 9 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [9.656137] rfkill: input handler disabled
Nov 18 07:48:35 gollum kernel: [9.721913] usb 1-3.1: New USB device
found, idVendor=03f0, idProduct=034a, bcdDevice= 1.21
Nov 18 07:48:35 gollum kernel: [9.721914] usb 1-3.1: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [9.721915] usb 1-3.1: Product: HP Elite
USB Keyboard
Nov 18 07:48:35 gollum kernel: [9.721916] usb 1-3.1: Manufacturer: Chicony
Nov 18 07:48:35 gollum kernel: [9.738116] input: Chicony HP Elite USB
Keyboard as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.1/1-3.1:1.0/0003:03F0:034A.0002/input/input19
Nov 18 07:48:35 gollum kernel: [9.796473] hid-generic
0003:03F0:034A.0002: input,hidraw1: USB HID v1.10 Keyboard [Chicony HP Elite
USB Keyboard] on usb-:00:14.0-3.1/input0
Nov 18 07:48:35 gollum kernel: [9.798157] usbhid 1-3.1:1.1: can't add hid
device: -32
Nov 18 07:48:35 gollum kernel: [9.798163] usbhid: probe of 1-3.1:1.1
failed with error -32
Nov 18 07:48:35 gollum kernel: [9.900252] usb 1-3.2: new low-speed USB
device number 10 using xhci_hcd
Nov 18 07:48:35 gollum kernel: [ 10.026058] usb 1-3.2: New USB device
found, idVendor=0458, idProduct=0133, bcdDevice= 0.00
Nov 18 07:48:35 gollum kernel: [ 10.026060] usb 1-3.2: New USB device
strings: Mfr=1, Product=2, SerialNumber=0
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Product: Laser Mouse
Nov 18 07:48:35 gollum kernel: [ 10.026061] usb 1-3.2: Manufacturer: Mouse
Nov 18 07:48:35 gollum kernel: [ 10.031943] input: Mouse Laser Mouse as
/devices/pci:00/:00:14.0/usb1/1-3/1-3.2/1-3.2:1.0/0003:0458:0133.0003/input/input20
Nov 18 07:48:35 gollum kernel: [ 10.032031] hid-generic
0003:0458:0133.0003: input,hidraw2: USB HID v1.10 Mouse [Mouse Laser Mouse] on
usb-:00:14.0-3.2/input0
Nov 18 07:48:35 gollum kernel: [ 10.112241] usb 1-3.3: new high-speed USB
device number 11 using xhci_hcd
Nov 18 07:48:36 gollum kernel: [ 10.457643] usb 1-3.3: New USB device
found, idVendor=046d, idProduct=081b, bcdDevice= 0.12
Nov 18 07:48:36 gollum kernel: [ 10.457649] usb 1-3.3: New USB device
strings: Mfr=0, Product=0, SerialNumber=2
Nov 18 07:48:36 gollum kernel: [ 10.457652] usb 1-3.3: SerialNumber:
D1C29B20
Preliminary investigation shows that the following commit seems to cause
issues:
ef513be0a905 ("usb: xhci: Add Clear_TT_Buffer")
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu8.8
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC1: juergh 3461 F pulseaudio
/dev/snd/controlC0: juergh 3461 F pulseaudio
DistroRelease: Ubuntu 19.10
InstallationDate: Installed on 2017-05-25 (1050 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Release amd64 (20170412)
MachineType: HP HP Pavilion Desktop PC 570-p0XX
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic
root=UUID=0f572e1f-1887-4e72-8c0a-0f3d2116df2b ro quiet "dyndbg=file
drivers/usb/* +pt" hid.debug=1
ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18
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.3.0-46-generic N/A
linux-backports-modules-5.3.0-46-generic N/A
linux-firmware1.183.5
Tags: eoan
Uname: Linux 5.3.0-46-generic x86_64
UpgradeStatus: Upgraded to eoan on 2019-10-25 (168 days ago)
UserGrou
[Kernel-packages] [Bug 1850654] Re: update-initramfs complains of missing amdgpu firmware files
Same here, 20.04 beta, AMD Ryzen 7 PRO 3700U w/ Radeon Vega Mobile (Thinkpad t495s), upgraded from 19.10. I have the same list of 24 missing amdgpu modules as the previous poster. This bug really needs re-working and yet it's status is set to "Fix Released" (which I can't seem to be able to change). Also someone with the powers should mark it as affecting Focal. -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1869799] Re: no sound driver since 5.3.0.42 kernel
@Hui Wang it looks like kernel isn't a problem, 'cause it isn't relevant wich kernel I load, I've this problem since I install this packages - post #11. So maybe not your code section -- 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/1869799 Title: no sound driver since 5.3.0.42 kernel Status in linux package in Ubuntu: Incomplete Bug description: no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the problem. i have only a dummy soundcard. no sound. 5.3.0.42 kernel works fine. my sound card is intel 100 / c230 hd audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/+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 1850654] Re: update-initramfs complains of missing amdgpu firmware files
Moreover, the firmware files are missing at the linux-firmware git: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/amdgpu The solution below suggested to copy it from the link above, but I can't. https://askubuntu.com/a/1124256 I have just now fetched some updates for my Ubuntu 20.04 Focal Fossa LTS, but the issue still persists. I think the issue are missing drivers for some really new Radeon cards in the linux-firmware upstream. My RX550 is using the amdgpu driver apparently (see the listings in my post above) and the graphic performance seems to be alright for watching 4k video. Probably the RX550 is unaffected, but one is unable to use the new Radeon cards. There are a few strange issues, though. There are no "restricted drivers" listed at the "Software & Updates >> Additional Drivers". This is strange, since the RX550 should be able to use either the open amdgpu or the restricted amdgpu-pro. Also note I seem to have some video quality issues with the VLC (absent in Videos), but it might be a codec issue. -- 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/1850654 Title: update-initramfs complains of missing amdgpu firmware files Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: Fix Released Status in linux source package in Bionic: Invalid Status in linux-firmware source package in Bionic: Fix Released Status in linux source package in Eoan: Confirmed Status in linux-firmware source package in Eoan: Fix Released Bug description: SRU Justification Impact: With 5.3 update-initramfs reports several missing amdgpu firmware files: update-initramfs: Generating /boot/initrd.img-5.3.0-19-generic W: Possible missing firmware /lib/firmware/amdgpu/vega20_ta.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/raven_kicker_rlc.bin for module amdgpu W: Possible missing firmware /lib/firmware/amdgpu/navi10_mes.bin for module amdgpu Of these, only raven_kicker_rlc.bin has been added to upstream linux- firmware. Fix: Add raven_kicker_rlc.bin to linux firmware, and remove the other files from modinfo for amdgpu. Test Case: Once fixed, the warnings from update-initramfs should be gone. Regression Potential: Adding a missing firmware is unlikely to break any working hardware. Removing the other missing files from modinfo will not cause regressions either, however if the firmware is added later update-initramfs will not add the files to the initramfs until the firmware is added back to modinfo. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850654/+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 1809274] Re: Secure boot MOK password requested for every kernel update even when booting in insecure mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: update-manager (Ubuntu) Status: New => 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/1809274 Title: Secure boot MOK password requested for every kernel update even when booting in insecure mode Status in linux package in Ubuntu: Incomplete Status in mokutil package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: To reproduce: - Disable kernel secure boot (booting in insecure mode). System secure boot still enabled - Update kernel with update-manager On every kernel update, a dialog appears asking me to enter a MOK secure boot password for temporarily disabling secure boot. See screenshot When I reboot, the MOK config screen appears, but I can just ignore it and it boots fine, since secure boot is already disabled in the kernel. Which makes me wonder why it even needs to ask me to enter a secure boot password every time I update the kernel. Expected: only ask for a secure boot password on update if it actually needs to disable kernel secure boot, and kernel secure boot is not already disabled. Note that the output of mokutil --sb-state SecureBoot enabled However, kernel secure boot is disabled and the system GRUB bootloader prints a message "Booting in insecure mode" on startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-headers-generic 4.15.0.43.45 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1672 F pulseaudio /dev/snd/controlC0: ubuntu 1672 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 10:49:48 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=none InstallationDate: Installed on 2018-09-12 (98 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Dell Inc. Latitude 3340 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=1c6a1916-ac97-4bdf-8f15-14d986e621a2 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-28 (82 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd07/09/2018:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809274/+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 1809274] Re: Secure boot MOK password requested for every kernel update even when booting in insecure mode
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: mokutil (Ubuntu) Status: New => 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/1809274 Title: Secure boot MOK password requested for every kernel update even when booting in insecure mode Status in linux package in Ubuntu: Incomplete Status in mokutil package in Ubuntu: Confirmed Status in update-manager package in Ubuntu: Confirmed Bug description: To reproduce: - Disable kernel secure boot (booting in insecure mode). System secure boot still enabled - Update kernel with update-manager On every kernel update, a dialog appears asking me to enter a MOK secure boot password for temporarily disabling secure boot. See screenshot When I reboot, the MOK config screen appears, but I can just ignore it and it boots fine, since secure boot is already disabled in the kernel. Which makes me wonder why it even needs to ask me to enter a secure boot password every time I update the kernel. Expected: only ask for a secure boot password on update if it actually needs to disable kernel secure boot, and kernel secure boot is not already disabled. Note that the output of mokutil --sb-state SecureBoot enabled However, kernel secure boot is disabled and the system GRUB bootloader prints a message "Booting in insecure mode" on startup ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-headers-generic 4.15.0.43.45 ProcVersionSignature: User Name 4.15.0-42.45-generic 4.15.18 Uname: Linux 4.15.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: ubuntu 1672 F pulseaudio /dev/snd/controlC0: ubuntu 1672 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 20 10:49:48 2018 EcryptfsInUse: Yes HibernationDevice: RESUME=none InstallationDate: Installed on 2018-09-12 (98 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) MachineType: Dell Inc. Latitude 3340 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-42-generic root=UUID=1c6a1916-ac97-4bdf-8f15-14d986e621a2 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-42-generic N/A linux-backports-modules-4.15.0-42-generic N/A linux-firmware 1.173.2 SourcePackage: linux UpgradeStatus: Upgraded to bionic on 2018-09-28 (82 days ago) dmi.bios.date: 07/09/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd07/09/2018:svnDellInc.:pnLatitude3340:pvr00:rvnDellInc.:rn:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude 3340 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1809274/+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 1855399] Re: [TGL] graphics kernel support
correct, it's only for the oem kernel ** Package changed: linux (Ubuntu) => linux-oem-5.6 (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855399 Title: [TGL] graphics kernel support Status in intel: New Status in linux-oem-5.6 package in Ubuntu: Confirmed Bug description: Description: This feature tracks the updates TGL graphics updates. We will submit the commit id lists since 5.4. 20.04 will use v5.4 as a base, (2109/11/25) first commit lists will be provided in 2020/01, if you need more before that, please let us know. Target Release: 20.10 Target Kernel: v5.8 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1855399/+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 1872047] [NEW] kselftest: seccomp kill_after_ptrace() timeout
Public bug reported: [Impact] While running seccomp_bpf, kill_after_ptrace() gets stuck if we run it via /usr/bin/timeout (that is the default), until the timeout expires. This is because /usr/bin/timeout is preventing to properly deliver signals to ptrace'd children (SIGSYS in this case). [Test case] This problem can be easily reproduced by running: $ sudo make TARGETS=seccomp kselftest ... # [ RUN ] TRACE_syscall.skip_a# not ok 1 selftests: seccomp: seccomp_bpf # TIMEOUT The test is hanging at this point until the timeout expires and then it reports the timeout error. [Fix] This problem can be prevented by passing --foreground to /usr/bin/timeout, allowing to properly deliver signals to children processes. [Regression potential] Not an upstream fix (patch has been sent to the lkml https://lkml.org/lkml/2020/4/10/153), but the fix is trivial and it's only affecting the selftests, not the kernel, so regression potential is minimal. ** Affects: linux (Ubuntu) Importance: Medium Assignee: Andrea Righi (arighi) Status: New ** Affects: linux (Ubuntu Eoan) Importance: Medium Assignee: Andrea Righi (arighi) Status: New ** Affects: linux (Ubuntu Focal) Importance: Medium Assignee: Andrea Righi (arighi) Status: New ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andrea Righi (arighi) ** Also affects: linux (Ubuntu Focal) Importance: Medium Assignee: Andrea Righi (arighi) Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Andrea Righi (arighi) -- 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/1872047 Title: kselftest: seccomp kill_after_ptrace() timeout Status in linux package in Ubuntu: New Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: [Impact] While running seccomp_bpf, kill_after_ptrace() gets stuck if we run it via /usr/bin/timeout (that is the default), until the timeout expires. This is because /usr/bin/timeout is preventing to properly deliver signals to ptrace'd children (SIGSYS in this case). [Test case] This problem can be easily reproduced by running: $ sudo make TARGETS=seccomp kselftest ... # [ RUN ] TRACE_syscall.skip_a# not ok 1 selftests: seccomp: seccomp_bpf # TIMEOUT The test is hanging at this point until the timeout expires and then it reports the timeout error. [Fix] This problem can be prevented by passing --foreground to /usr/bin/timeout, allowing to properly deliver signals to children processes. [Regression potential] Not an upstream fix (patch has been sent to the lkml https://lkml.org/lkml/2020/4/10/153), but the fix is trivial and it's only affecting the selftests, not the kernel, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872047/+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 1872047] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1872047 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Eoan) Status: New => Incomplete -- 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/1872047 Title: kselftest: seccomp kill_after_ptrace() timeout Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Status in linux source package in Focal: Incomplete Bug description: [Impact] While running seccomp_bpf, kill_after_ptrace() gets stuck if we run it via /usr/bin/timeout (that is the default), until the timeout expires. This is because /usr/bin/timeout is preventing to properly deliver signals to ptrace'd children (SIGSYS in this case). [Test case] This problem can be easily reproduced by running: $ sudo make TARGETS=seccomp kselftest ... # [ RUN ] TRACE_syscall.skip_a# not ok 1 selftests: seccomp: seccomp_bpf # TIMEOUT The test is hanging at this point until the timeout expires and then it reports the timeout error. [Fix] This problem can be prevented by passing --foreground to /usr/bin/timeout, allowing to properly deliver signals to children processes. [Regression potential] Not an upstream fix (patch has been sent to the lkml https://lkml.org/lkml/2020/4/10/153), but the fix is trivial and it's only affecting the selftests, not the kernel, so regression potential is minimal. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872047/+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 1872055] [NEW] Ubuntu 19.10 says no wifi adapter found
Public bug reported: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anu2180 F pulseaudio /dev/snd/controlC0: anu2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp0s16u3 no wireless extensions. enp1s0no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.product.name: 81FS dmi.product.sku: LENOVO_MT_81FS_BU_idea_FM_E41-25 dmi.product.version: Lenovo E41-25 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug eoan -- 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/1872055 Title: Ubuntu 19.10 says no wifi adapter found Status in linux package in Ubuntu: New Bug description: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anu2180 F pulseaudio /dev/snd/controlC0: anu2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp0s16u3 no wireless extensions. enp1s0no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.
[Kernel-packages] [Bug 1872059] [NEW] missing hardware/runtime info when reporing linux-firmware bugs via apport
Public bug reported: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Eoan) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Focal) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: In Progress ** Tags: amd64 apport-bug focal ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Eoan) Importance: Undecided Status: New -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) 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/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872055] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => 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/1872055 Title: Ubuntu 19.10 says no wifi adapter found Status in linux package in Ubuntu: Confirmed Bug description: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anu2180 F pulseaudio /dev/snd/controlC0: anu2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp0s16u3 no wireless extensions. enp1s0no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.product.name: 81FS dmi.product.sku: LENOVO_MT_81FS_BU_idea_FM_E41-25 dmi.product.version: Lenovo E41-25 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872055/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
https://lists.ubuntu.com/archives/kernel-team/2020-April/108960.html ** Changed in: linux-firmware (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Focal) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Tags added: apport-collected ** Description changed: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu26 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: KDE + Dependencies: + + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-09-28 (194 days ago) + InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) + MachineType: Apple Inc. MacBookPro11,1 + NonfreeKernelModules: wl + Package: linux-firmware + PackageArchitecture: all + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-21-generic N/A + linux-backports-modules-5.4.0-21-generic N/A + linux-firmware1.187 + Tags: focal + Uname: Linux 5.4.0-21-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 06/13/2019 + dmi.bios.vendor: Apple Inc. + dmi.bios.version: 156.0.0.0.0 + dmi.board.asset.tag: Base Board Asset Tag# + dmi.board.name: Mac-189A3D4F975D5FFC + dmi.board.vendor: Apple Inc. + dmi.board.version: MacBookPro11,1 + dmi.chassis.type: 10 + dmi.chassis.vendor: Apple Inc. + dmi.chassis.version: Mac-189A3D4F975D5FFC + dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: + dmi.product.family: Mac + dmi.product.name: MacBookPro11,1 + dmi.product.sku: System SKU# + dmi.product.version: 1.0 + dmi.sys.vendor: Apple Inc. -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-88
[Kernel-packages] [Bug 1872059] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1872059/+attachment/5351282/+files/CRDA.txt -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872059] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1872059/+attachment/5351284/+files/IwConfig.txt -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872059] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1872059/+attachment/5351286/+files/Lspci-vt.txt -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872059] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1872059/+attachment/5351283/+files/CurrentDmesg.txt -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872059] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1872059/+attachment/5351285/+files/Lspci.txt -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
Triggered `apport-collect 1872059` when source_linux-firmware.py symlink was manually created. -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872059] AlsaInfo.txt
apport information ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1872059/+attachment/5351280/+files/AlsaInfo.txt -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872059] AudioDevicesInUse.txt
apport information ** Attachment added: "AudioDevicesInUse.txt" https://bugs.launchpad.net/bugs/1872059/+attachment/5351281/+files/AudioDevicesInUse.txt -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1872059/+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 1872055] Re: Qualcomm Atheros QCA9377 [168c:0042] subsystem [17aa:0901] not available in Ubuntu 19.10
** Summary changed: - Ubuntu 19.10 says no wifi adapter found + Qualcomm Atheros QCA9377 [168c:0042] subsystem [17aa:0901] not available in Ubuntu 19.10 ** Tags added: hwe-networking-wifi -- 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/1872055 Title: Qualcomm Atheros QCA9377 [168c:0042] subsystem [17aa:0901] not available in Ubuntu 19.10 Status in linux package in Ubuntu: Confirmed Bug description: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anu2180 F pulseaudio /dev/snd/controlC0: anu2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp0s16u3 no wireless extensions. enp1s0no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.product.name: 81FS dmi.product.sku: LENOVO_MT_81FS_BU_idea_FM_E41-25 dmi.product.version: Lenovo E41-25 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872055/+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 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels
** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-gcp (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-signed-oracle-5.0 (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) ** Description changed: + [Impact] + Running seccomp kernel selftests will fail. + + [Test case] + Run linux/tools/testing/selftests/seccomp/seccomp_bpf. + + On failure: + seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) + seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) + global.user_notification_basic: Test failed at step #3 + [ FAIL ] global.user_notification_basic + + On success: + + [Regression potential] + The test is checking that the given structure which the kernel will write to is all zeroes. It's doing it because it wants userspace to have the possibility in the future to give data there indicating support for an extension that might be developed in the future. As the test is there right now, not applying the breaking uABI fix might cause us to miss applications that would break in future kernels. As the backport for that is prone for more regression potential, we are deciding to revert the new test. + + + == + Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64) [ RUN ] global.user_notification_basic seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic - - This cannot be reproduced with the kselftest in older kernel, probably a test case issue. + This cannot be reproduced with the kselftest in older kernel, probably a + test case issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16 ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21 Uname: Linux 5.0.0-1011-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Mon Feb 10 05:17:54 2020 ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=C.UTF-8 + SHELL=/bin/bash SourcePackage: linux-signed-oracle-5.0 UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862588 Title: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-signed-oracle-5.0 package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-signed-oracle-5.0 source package in Bionic: New Status in linux source package in Disco: Incomplete Status in linux-aws source package in Disco: New Status in linux-gcp source package in Disco: New Status in linux-signed-oracle-5.0 source package in Disco: New Status in linux source package in Eoan: Confirmed Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Status in linux-signed-oracle-5.0 source package in Eoan: New Bug description: [Impact] Running seccomp kernel selftests will fail. [Test case] Run linux/tools/testing/selftests/seccomp/seccomp_bpf. On failure: seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic On success: [ RUN ] global.user_notification_basic [ OK ] global.user_notification_basic [Regression potential] The test is checking that the given structure which the kernel will write to is all zeroes. It's doing it because it wants userspace to have the possibility in the future to give data there indicating support for an extension that might be developed
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Same for me. inxi -SCGxxxz System:Host: viktorz Kernel: 5.3.0-46-generic x86_64 bits: 64 gcc: 7.5.0 Desktop: Gnome 3.28.4 (Gtk 3.22.30-1ubuntu4) info: gnome-shell dm: gdm3 Distro: Ubuntu 18.04.4 LTS CPU: Quad core Intel Core i5-9400H (-MT-MCP-) arch: Skylake rev.13 cache: 8192 KB flags: (lm nx sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx) bmips: 1 clock speeds: min/max: 800/4300 MHz 1: 900 MHz 2: 900 MHz 3: 900 MHz 4: 900 MHz 5: 900 MHz 6: 900 MHz 7: 900 MHz 8: 900 MHz Graphics: Card: Intel Device 3e9b bus-ID: 00:02.0 chip-ID: 8086:3e9b Display Server: x11 (X.Org 1.20.5 ) driver: i915 Resolution: 1920x1080@60.00hz, 1920x1080@60.00hz OpenGL: renderer: Mesa DRI Intel UHD Graphics 630 (Coffeelake 3x8 GT2) version: 4.5 Mesa 19.2.8 (compat-v: 3.0) Direct Render: Yes syslog: Apr 10 14:56:25 viktorz kernel: [18006.588904] i915 :00:02.0: Resetting rcs0 for hang on rcs0 -- 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/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic roo
[Kernel-packages] [Bug 1872059] Re: missing hardware/runtime info when reporing linux-firmware bugs via apport
** Also affects: apport (Ubuntu) Importance: Undecided Status: New ** No longer affects: apport (Ubuntu Eoan) ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => Yuan-Chen Cheng (ycheng-twn) ** Changed in: oem-priority Importance: Undecided => High ** Changed in: oem-priority Status: New => Confirmed ** No longer affects: apport (Ubuntu Bionic) -- 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/1872059 Title: missing hardware/runtime info when reporing linux-firmware bugs via apport Status in OEM Priority Project: Confirmed Status in apport package in Ubuntu: New Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-firmware source package in Eoan: New Status in apport source package in Focal: New Status in linux-firmware source package in Focal: In Progress Bug description: linux-firmware doesn't install any package hooks for apport, so it will only carry some default items leaving hardware list, kernel messages unattached. Suggest symlink /usr/share/apport/package-hooks /source_linux-firmware.py to source_linux.py as other linux image debs do in bug 1847967. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip Date: Fri Apr 10 19:15:15 2020 Dependencies: InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-09-28 (194 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Alpha amd64 (20190923) MachineType: Apple Inc. MacBookPro11,1 NonfreeKernelModules: wl Package: linux-firmware PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.4.0-21-generic root=UUID=38c16714-8883-4c88-baae-df71ffa89972 ro rootflags=subvol=@ quiet splash acpi_enforce_resources=lax crashkernel=512M-:192M vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 RelatedPackageVersions: linux-restricted-modules-5.4.0-21-generic N/A linux-backports-modules-5.4.0-21-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip docker lpadmin lxd microk8s plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/13/2019 dmi.bios.vendor: Apple Inc. dmi.bios.version: 156.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-189A3D4F975D5FFC dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,1 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-189A3D4F975D5FFC dmi.modalias: dmi:bvnAppleInc.:bvr156.0.0.0.0:bd06/13/2019:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC: dmi.product.family: Mac dmi.product.name: MacBookPro11,1 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1872059/+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 1871917] Re: Unable to boot 20.04 installer on Dell XPS 15 9560
** 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/1871917 Title: Unable to boot 20.04 installer on Dell XPS 15 9560 Status in linux package in Ubuntu: Confirmed Bug description: I tried to boot the 20.04 nightly image (focal-desktop-amd64.iso 2020-04-05 11:06 ) as well as an older one (a week ago) on my Dell XPS 15 9560, and I got the same error message each time. The live system performs a filesystem check while showing a progress bar on a screen with dell and ubuntu logo, then the linux console shows with following error: sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Buffer I/O error on dev sda, logical block 3816176 async page read This happens with two different 16GB usb sticks on the Dell XPS 15. They both worked fine on an old samsung netbook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871917/+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 1872055] Re: Qualcomm Atheros QCA9377 [168c:0042] subsystem [17aa:0901] not available in Ubuntu 19.10
[0.290807] pci :02:00.0: can't claim BAR 0 [mem 0xf000-0xf01f 64bit]: no compatible bridge window [0.321843] pci :02:00.0: BAR 0: no space for [mem size 0x0020 64bit] [0.321845] pci :02:00.0: BAR 0: trying firmware assignment [mem 0xf000-0xf01f 64bit] [0.321847] pci :02:00.0: BAR 0: [mem 0xf000-0xf01f 64bit] conflicts with PCI Bus :00 [mem 0xe800-0xf7ff window] [0.321848] pci :02:00.0: BAR 0: failed to assign [mem size 0x0020 64bit] [ 14.795108] ath10k_pci :02:00.0: failed to iomap BAR0 [ 14.795165] ath10k_pci :02:00.0: failed to claim device: -5 [ 14.795331] ath10k_pci: probe of :02:00.0 failed with error -5 -- 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/1872055 Title: Qualcomm Atheros QCA9377 [168c:0042] subsystem [17aa:0901] not available in Ubuntu 19.10 Status in linux package in Ubuntu: Confirmed Bug description: I have installed the ubuntu 19.10 and since the installation it says no wifi adpter found but the wifi was working with Windows perfectly but since I switch to ubuntu I am not able to use the wifi. I have tried lots of different methods to fix this issue on the internet and also asked on Ubuntu community for help but none worked for me. It seems there's some bug on the os because during the installation the wifi was working but after the installation has completed the wifi stoped working and says No wifi adapter found. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-46-generic 5.3.0-46.38 ProcVersionSignature: Ubuntu 5.3.0-46.38-generic 5.3.18 Uname: Linux 5.3.0-46-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: anu2180 F pulseaudio /dev/snd/controlC0: anu2180 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 16:31:11 2020 InstallationDate: Installed on 2020-04-09 (1 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. enp0s16u3 no wireless extensions. enp1s0no wireless extensions. MachineType: LENOVO 81FS ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=9462d35f-9a18-4b4c-8372-6429117b7939 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.183.5 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/14/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 7UCN28WW(V2.02) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo E41-25 dmi.modalias: dmi:bvnLENOVO:bvr7UCN28WW(V2.02):bd11/14/2019:svnLENOVO:pn81FS:pvrLenovoE41-25:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoE41-25: dmi.product.family: E41-25 dmi.product.name: 81FS dmi.product.sku: LENOVO_MT_81FS_BU_idea_FM_E41-25 dmi.product.version: Lenovo E41-25 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872055/+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
