[Kernel-packages] [Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I just received an update which seems to have solved the problem on my laptop (tried suspend and resume -> no weird screen). According to /var/log/apt/history.log the latest updates are: Install: linux-modules-extra-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-modules-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-headers-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic), linux-hwe-5.13-headers-5.13.0-30:amd64 (5.13.0-30.33~20.04.1, automatic), linux-image-5.13.0-30-generic:amd64 (5.13.0-30.33~20.04.1, automatic) Upgrade: linux-headers-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), linux-libc-dev:amd64 (5.4.0-99.112, 5.4.0-100.113), snapd:amd64 (2.54.2+20.04ubuntu2, 2.54.3+20.04.1), libarchive13:amd64 (3.4.0-2ubuntu1, 3.4.0-2ubuntu1.1), language-pack-en:amd64 (1:20.04+20210802, 1:20.04+20220211), linux-image-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), linux-generic-hwe-20.04:amd64 (5.13.0.28.31~20.04.15, 5.13.0.30.33~20.04.17), language-pack-en-base:amd64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2
[Kernel-packages] [Bug 1961375] Re: nvidia-settings didn't install by default with third-party pkgs on Jammy
** Attachment added: "/var/log/installer/syslog" https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/1961375/+attachment/5561732/+files/syslog ** Description changed: Using Jammy daily build 2022-02-02 on I+N desktop. Boot_vga is dGPU (nvidia) with RTD3 supports. + Installation from USB without connecting network. Feb 18 05:26:52 ubuntu ubiquity: Unpacking nvidia-settings (470.57.01-0ubuntu3) ...#015 Feb 18 05:26:52 ubuntu tracker-miner-f[2212]: Error executing batch: Unable to insert multiple values for subject `file:///usr/share/applications/nvidia-settings.desktop.dpkg-new' and single valued property `nfo:fileLastAccessed' (old_value: '', new value: '') Feb 18 05:26:52 ubuntu tracker-miner-f[2212]: g_hash_table_contains: assertion 'hash_table != NULL' failed + + --- + + After installation, manually install nvidia-settings works. + `apt install nvidia-settings` -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1961375 Title: nvidia-settings didn't install by default with third-party pkgs on Jammy Status in nvidia-settings package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: Using Jammy daily build 2022-02-02 on I+N desktop. Boot_vga is dGPU (nvidia) with RTD3 supports. Installation from USB without connecting network. Feb 18 05:26:52 ubuntu ubiquity: Unpacking nvidia-settings (470.57.01-0ubuntu3) ...#015 Feb 18 05:26:52 ubuntu tracker-miner-f[2212]: Error executing batch: Unable to insert multiple values for subject `file:///usr/share/applications/nvidia-settings.desktop.dpkg-new' and single valued property `nfo:fileLastAccessed' (old_value: '', new value: '') Feb 18 05:26:52 ubuntu tracker-miner-f[2212]: g_hash_table_contains: assertion 'hash_table != NULL' failed --- After installation, manually install nvidia-settings works. `apt install nvidia-settings` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1961375/+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 1961375] [NEW] nvidia-settings didn't install by default with third-party pkgs on Jammy
Public bug reported: Using Jammy daily build 2022-02-02 on I+N desktop. Boot_vga is dGPU (nvidia) with RTD3 supports. Installation from USB without connecting network. Feb 18 05:26:52 ubuntu ubiquity: Unpacking nvidia-settings (470.57.01-0ubuntu3) ...#015 Feb 18 05:26:52 ubuntu tracker-miner-f[2212]: Error executing batch: Unable to insert multiple values for subject `file:///usr/share/applications/nvidia-settings.desktop.dpkg-new' and single valued property `nfo:fileLastAccessed' (old_value: '', new value: '') Feb 18 05:26:52 ubuntu tracker-miner-f[2212]: g_hash_table_contains: assertion 'hash_table != NULL' failed --- After installation, manually install nvidia-settings works. `apt install nvidia-settings` ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Status: New ** Affects: ubiquity (Ubuntu) Importance: Undecided Status: New ** Also affects: ubiquity (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1961375 Title: nvidia-settings didn't install by default with third-party pkgs on Jammy Status in nvidia-settings package in Ubuntu: New Status in ubiquity package in Ubuntu: New Bug description: Using Jammy daily build 2022-02-02 on I+N desktop. Boot_vga is dGPU (nvidia) with RTD3 supports. Installation from USB without connecting network. Feb 18 05:26:52 ubuntu ubiquity: Unpacking nvidia-settings (470.57.01-0ubuntu3) ...#015 Feb 18 05:26:52 ubuntu tracker-miner-f[2212]: Error executing batch: Unable to insert multiple values for subject `file:///usr/share/applications/nvidia-settings.desktop.dpkg-new' and single valued property `nfo:fileLastAccessed' (old_value: '', new value: '') Feb 18 05:26:52 ubuntu tracker-miner-f[2212]: g_hash_table_contains: assertion 'hash_table != NULL' failed --- After installation, manually install nvidia-settings works. `apt install nvidia-settings` To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1961375/+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 1961369] [NEW] iwlwifi: mvm: read 6E enablement flags from DSM and pass to FW
Public bug reported: [Impact] [Fix] [Test] [Where problems could occur] ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Invalid ** Affects: linux-oem-5.14 (Ubuntu Focal) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-5.14 (Ubuntu Jammy) Importance: Undecided Status: Invalid ** Tags: oem-priority originate-from-1955412 somerville ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.14 (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.14 (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-5.14 (Ubuntu Focal) Assignee: (unassigned) => AceLan Kao (acelankao) ** Tags added: oem-priority originate-from-1955412 somerville -- 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/1961369 Title: iwlwifi: mvm: read 6E enablement flags from DSM and pass to FW Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.14 source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: [Impact] [Fix] [Test] [Where problems could occur] To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961369/+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 1961120] Re: SFH sensors are not working on some AMD platforms
** Description changed: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). + Here is the monitor sensors output, which doesn't change. - Here is the monitor sensors output, which doesn't change. - - $ sudo monitor-sensor + $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear - +++ iio-sensor-proxy appeared - === No accelerometer - === Has ambient light sensor (value: 0.00, unit: lux) + +++ iio-sensor-proxy appeared + === No accelerometer + === Has ambient light sensor (value: 0.00, unit: lux) [Fix] + The SRU contains two fixes: + 1. increasing sensor command timeout from from 80 to 160. + 2. using first valid 15 bits only ALS max illuminance values. + + [Test] + This is requested by AMD. This was also verified by an AMD's engineer + on CRB. + [Where problems could occur] + + Low. The patches only increase timeout value and discard an invalid + bit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961120 Title: SFH sensors are not working on some AMD platforms Status in HWE Next: In Progress Status in linux-oem-5.14 package in Ubuntu: New Status in linux-oem-5.14 source package in Focal: New Bug description: [Impact] When amd-sfh is loaded the sensors connected do not change values at all (ALS sensor). Here is the monitor sensors output, which doesn't change. $ sudo monitor-sensor Waiting for iio-sensor-proxy to appear +++ iio-sensor-proxy appeared === No accelerometer === Has ambient light sensor (value: 0.00, unit: lux) [Fix] The SRU contains two fixes: 1. increasing sensor command timeout from from 80 to 160. 2. using first valid 15 bits only ALS max illuminance values. [Test] This is requested by AMD. This was also verified by an AMD's engineer on CRB. [Where problems could occur] Low. The patches only increase timeout value and discard an invalid bit. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1961120/+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 1786013] Autopkgtest regression report (linux-meta-oracle-5.13/5.13.0.1018.22~20.04.1)
All autopkgtests for the newly accepted linux-meta-oracle-5.13 (5.13.0.1018.22~20.04.1) for focal have finished running. The following regressions have been reported in tests triggered by the package: jool/unknown (arm64) zfs-linux/unknown (arm64) iptables-netflow/unknown (arm64) linux-oracle-5.13/unknown (arm64) v4l2loopback/unknown (arm64) langford/unknown (arm64) snapd/unknown (arm64) wireguard-linux-compat/unknown (arm64) xtables-addons/unknown (arm64) lime-forensics/unknown (arm64) gost-crypto/unknown (arm64) bbswitch/unknown (arm64) r8168/unknown (arm64) openafs/unknown (arm64) mali-midgard/unknown (arm64) glibc/unknown (arm64) ddcci-driver-linux/unknown (arm64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oracle-5.13 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1961119] Re: Lower the volume of expected s0i3 WARN_ON
** Description changed: [Impact] AMD has a known BIOS bug right now that leads to the following WARN traceback during s0i3 resume (see below). This doesn't have (measurable) functional impact to the system or GPU, but it is an ugly message to have in place and makes it look like a potentially major problem. AMD is working on fixing this in BIOS, but it may not be ready by the time the first platforms launch. [Fix] + Print a shorter message warning instead: "Watermarks table not configured properly by SMU". + + The fixed was cherry-picked from mainline kernel v5.17-rc4. [Test] + This is requested by AMD, and tested and verified on the AMD CRB. [Where problems could occur] + Low. This only changes the behavors of message printing There are no + functional changes. --- WARN_ON messages --- [ cut here ] WARNING: CPU: 8 PID: 60399 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dcn31/dcn31_smu.c:123 dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Modules linked in: btrfs blake2b_generic xor zstd_compress raid6_pq ufs qnx4 hfsplus hfs minix ntfs msdos jfs xfs libcrc32c cpuid michael_mic hid_logitech_hidpp snd_usb_audio snd_usbmidi_lib hid_logitech_dj usbhid cdc_ether usbnet r8152 mii qrtr_mhi joydev intel_rapl_msr intel_rapl_common bnep snd_soc_dmic snd_acp6x_pdm_dma snd_soc_acp6x_mach snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine edac_mce_amd amdgpu snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi nls_iso8859_1 kvm_amd kvm snd_hda_intel qrtr snd_intel_dspcfg ns snd_intel_sdw_acpi snd_hda_codec ath11k_pci crct10dif_pclmul input_leds snd_pci_acp6x ghash_clmulni_intel ath11k snd_hda_core snd_hwdep qmi_helpers aesni_intel snd_pcm uvcvideo crypto_simd videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 iommu_v2 cryptd platform_profile btusb snd_seq_midi gpu_sched rapl mac80211 serio_raw snd_seq_midi_event videobuf2_common sparse_keymap drm_ttm_helper btrtl snd_rawmidi btbcm videodev - btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid + btintel ttm efi_pstore wmi_bmof hid_multitouch mc bluetooth snd_seq drm_kms_helper snd_seq_device ecdh_generic cfg80211 ecc snd_timer cec rc_core i2c_algo_bit snd fb_sys_fops syscopyarea sysfillrect mhi sysimgblt libarc4 soundcore snd_rn_pci_acp3x snd_pci_acp3x ccp ucsi_acpi typec_ucsi amd_pmc wireless_hotkey mac_hid typec acpi_tad sch_fq_codel msr parport_pc ppdev lp parport drm ip_tables x_tables autofs4 hid_generic crc32_pclmul thunderbolt nvme i2c_piix4 xhci_pci xhci_pci_renesas nvme_core iosm wmi i2c_hid_acpi video i2c_hid hid Workqueue: events_unbound async_run_entry_fn RIP: 0010:dcn31_smu_send_msg_with_param+0xec/0x130 [amdgpu] Code: 00 e8 38 60 fc ff 48 8b 3b 4c 89 ea be 9b 62 01 00 e8 c8 60 fc ff 85 c0 75 40 bf c6 a7 00 00 e8 aa da 0c c6 41 83 ec 01 75 dc <0f> 0b 48 8b 3b b9 80 84 1e 00 44 89 fa 44 89 f6 e8 af 9c fc ff 48 RSP: 0018:b76d03167bc8 EFLAGS: 00010202 RAX: 00ff RBX: 9dc54f492800 RCX: 0008 RDX: RSI: 0001629b RDI: 9dc548bc RBP: b76d03167bf8 R08: 0009 R09: 0320 R10: 0191 R11: 04451a00 R12: 00030b48 R13: c1717d90 R14: 0011 R15: 0001 FS: () GS:9dcc7e80() knlGS: CS: 0010 DS: ES: CR0: 80050033 CR2: 55f79ba89f68 CR3: 00052681 CR4: 00750ee0 PKRU: 5554 Call Trace: - - dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] - dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] - dcn31_init_hw+0x465/0x8e0 [amdgpu] - dc_set_power_state+0x113/0x160 [amdgpu] - dm_resume+0x2b5/0x610 [amdgpu] - amdgpu_device_ip_resume_phase2+0x58/0xc0 [amdgpu] - amdgpu_device_resume+0xd9/0x210 [amdgpu] - amdgpu_pmops_resume+0x1d/0x40 [amdgpu] - pci_pm_resume+0x5b/0x90 - ? pci_pm_thaw+0x80/0x80 - dpm_run_callback+0x52/0x160 - device_resume+0xdd/0x1e0 - async_resume+0x1f/0x60 - async_run_entry_fn+0x33/0x120 - process_one_work+0x236/0x420 - worker_thread+0x34/0x410 - ? process_one_work+0x420/0x420 - kthread+0x12f/0x150 - ? set_kthread_struct+0x40/0x40 - ret_from_fork+0x22/0x30 - + + dcn31_smu_transfer_wm_table_dram_2_smu+0x23/0x30 [amdgpu] + dcn31_notify_wm_ranges+0x145/0x180 [amdgpu] + dcn31_init_hw+0x465/0x8e0 [amdgpu] + dc_set_power_state+0x113/0x160 [amdgpu] +
[Kernel-packages] [Bug 1959085] Re: Ubuntu 21.10 boot stuck in initramfs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: zfs-linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1959085 Title: Ubuntu 21.10 boot stuck in initramfs Status in initramfs-tools package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Confirmed Bug description: Hi, I just installed the latest Ubuntu desktop from iso file ubuntu-21.10-desktop-amd64.iso inside of VMWare workstation. I chose ZFS and native ZFS encryption of the filesystem. The installation went fine. Everything worked as expected. Then I upgraded the packages to the latest version via the Software updater. After reboot I'm stuck in the initramfs prompt. The following command fails: mount -o zfsutil -t zfs rpool/ROOT/ubuntu_gtw63h /root// Permission denied. And the system never asks me for the password to unlock the root fs. So, I'm guessing that there is something wrong with the new initramfs disk: initrd.img-5.13.0-27-generic When I reboot and select the previous version in grub: initrd.img-5.13.0-27-generic, the system asks for the password and boots without a problem. Thanks. To summarize: 1. Installed new VM using the Ubuntu iso image. Chose ZFS native encryption. Minimal install. 2. As soon as the system came up, I hit the update/upgrade prompt. Rebooted and failed to boot the new version. I didn't customize anything or installed anything extra. root@ubud01:/var# lsb_release -rd Description: Ubuntu 21.10 Release: 21.10 root@ubud01:/var# dpkg -l | grep zfs ii libzfs4linux 2.0.6-1ubuntu2 amd64OpenZFS filesystem library for Linux ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs ii zfs-zed2.0.6-1ubuntu2 amd64OpenZFS Event Daemon ii zfsutils-linux 2.0.6-1ubuntu2 amd64command-line tools to manage OpenZFS filesystems root@ubud01:/var# dpkg -l | grep init ii busybox-initramfs 1:1.30.1-6ubuntu3.1 amd64Standalone shell setup for initramfs ii cryptsetup-initramfs 2:2.3.6-0ubuntu1 all disk encryption support - initramfs integration ii gnome-initial-setup40.4-1ubuntu1 amd64Initial GNOME system setup helper ii init 1.60build1 amd64metapackage ensuring an init system is installed ii init-system-helpers1.60build1 all helper tools for all init systems ii initramfs-tools0.140ubuntu6 all generic modular initramfs generator (automation) ii initramfs-tools-bin0.140ubuntu6 amd64binaries used by initramfs-tools ii initramfs-tools-core 0.140ubuntu6 all generic modular initramfs generator (core tools) ii libatopology2:amd641.2.4-1.1ubuntu3.1 amd64shared library for handling ALSA topology definitions ii libklibc:amd64 2.0.8-6.1ubuntu2 amd64minimal libc subset for use with initramfs ii lsb-base 11.1.0ubuntu3 all Linux Standard Base init script functionality ii ncurses-base 6.2+20201114-2build1 all basic terminal type definitions ii sysvinit-utils 2.96-7ubuntu1 amd64System-V-like utilities ii xinit 1.4.1-0ubuntu3 amd64X server initialisation tool ii zfs-initramfs 2.0.6-1ubuntu2 amd64OpenZFS root filesystem capabilities for Linux - initramfs root@ubud01:/var# zfs list NAME USED AVAIL REFER MOUNTPOINT bpool 290M 542M 96K /boot bpool/BOOT 289M 542M 96K none bpool/BOOT/ubuntu_gtw63h 288M 542M 156M /boot rpool
[Kernel-packages] [Bug 1961329] [NEW] linux-azure: Update HV support to 5.17
Public bug reported: SRU Justification [Impact] Microsoft has requested these commits be present in all Azure tuned kernels: ac0f7d42584125dab8039e60ab4ade48cc2db61c Drivers: hv: copy from message page only what's needed a276463b7aeb6186e7e4315cccb032773fb31b5d Drivers: hv: allocate the exact needed memory for messages 5cc415001bca8fe0e3f0ee6d58a953a314dd9751 Drivers: hv: avoid passing opaque pointer to vmbus_onmessage() b0a284dc65b401a508dc2c5ed7d465884220f607 Drivers: hv: make sure that 'struct vmbus_channel_message_header' compiles correctly 52c7803f9bd4b1f0ac6e2e3e6051415198cc06bd Drivers: hv: check VMBus messages lengths 06caa778d8b2fbcb4ac3878751e39d116424ba9b hv_utils: Add validation for untrusted Hyper-V values e99c4afbee07e9323e9191a20b24d74dbf815bdf Drivers: hv: vmbus: Initialize memory to be sent to the host fe8c1b18a27de4d6ca5d99b3ffb3125dc69a5b76 Drivers: hv: vmbus: Copy the hv_message in vmbus_on_msg_dpc() e3fa4b747f085d2cda09bba0533b86fa76038635 Drivers: hv: vmbus: Avoid use-after-free in vmbus_onoffer_rescind() e4d221b42354b2e2ddb9187a806afb651eee2cda Drivers: hv: vmbus: Resolve race condition in vmbus_onoffer_rescind() adae1e931acd8b430d31141a283ea06d4b705417 Drivers: hv: vmbus: Copy packets sent by Hyper-V out of the ring buffer 9d68cd9120e4e3af38f843e165631c323b86b4e4 hv_utils: Set the maximum packet size for VSS driver to the length of the receive buffer f1940d4e9cbe6208e7e77e433c587af108152a17 Drivers: hv: vmbus: Fix kernel crash upon unbinding a device from uio_hv_generic driver 007faec014cb5d26983c1f86fd08c6539b41392e x86/sev: Expose sev_es_ghcb_hv_call() for use by HyperV 0cc4f6d9f0b9f20f3f1e1149bdb6737c0b4e134a x86/hyperv: Initialize GHCB page in Isolation VM af788f355e343373490b7d2e361016e7c24a0ffa x86/hyperv: Initialize shared memory boundary in the Isolation VM. 810a521265023a1d5c6c081ea2d216bc63d422f5 x86/hyperv: Add new hvcall guest address host visibility support d4dccf353db80e209f262e3973c834e6e48ba9a9 Drivers: hv: vmbus: Mark vmbus ring buffer visible to host in Isolation VM faff44069ff538ccdfef187c4d7ec83d22dfb3a4 x86/hyperv: Add Write/Read MSR registers via ghcb page 20c89a559e00dfe352b73e867211a669113ae881 x86/hyperv: Add ghcb hvcall support for SNP VM f2f136c05fb6093818a3b3fefcba46231ac66a62 Drivers: hv: vmbus: Add SNP support for VMbus channel initiate message 9a8797722e4239242d0cb4cc4baa805df6ac979e Drivers: hv: vmbus: Initialize VMbus ring buffer for Isolation VM 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9 swiotlb: Add swiotlb bounce buffer remap function for HV IVM c789b90a69045d1924bc0802ae0dce2bba05a04e x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has() 062a5c4260cdb734a4727230c58e38accf413315 hyper-v: Enable swiotlb bounce buffer for Isolation VM 743b237c3a7b0f5b44aa704aae8a1058877b6322 scsi: storvsc: Add Isolation VM support for storvsc driver 846da38de0e8224f2f94b885125cf1fd2d7b0d39 net: netvsc: Add Isolation VM support for netvsc driver 2deb55d9f57bb7a877c0d77115cc4077e1e974ff swiotlb: Add CONFIG_HAS_IOMEM check around swiotlb_mem_remap() 6a27e396ebb149fc47baccc1957a7a9dd70049a7 Drivers: hv: vmbus: Initialize request offers message for Isolation VM 4eea5332d67d8ae6ba5717ec0f4e671fdbd222e7 scsi: storvsc: Fix storvsc_queuecommand() memory leak 96d9d1fa5cd505078534113308ced0aa56d8da58 Drivers: hv: balloon: account for vmbus packet header in max_pkt_size [Test Plan] Microsoft tested [Where things could go wrong] Hyper-V guests may not work correctly. [Other Info] SF: #00323683 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Description changed: SRU Justification [Impact] - Microsoft has requested these Azure updates: + Microsoft has requested these Azure commits be present in all Azure + tuned kernels: - v5.17-rc2~23^2~1 96d9d1fa5cd505078534113308ced0aa56d8da58 Drivers: hv: balloon: account for vmbus packet header in max_pkt_size - v5.17-rc1~70^2 4eea5332d67d8ae6ba5717ec0f4e671fdbd222e7 scsi: storvsc: Fix storvsc_queuecommand() memory leak - v5.17-rc1~70^2~2 6a27e396ebb149fc47baccc1957a7a9dd70049a7 Drivers: hv: vmbus: Initialize request offers message for Isolation VM - v5.17-rc1~70^2~4 2deb55d9f57bb7a877c0d77115cc4077e1e974ff swiotlb: Add CONFIG_HAS_IOMEM check around swiotlb_mem_remap() - v5.17-rc1~70^2~7 846da38de0e8224f2f94b885125cf1fd2d7b0d39 net: netvsc: Add Isolation VM support for netvsc driver - v5.17-rc1~70^2~8 743b237c3a7b0f5b44aa704aae8a1058877b6322 scsi: storvsc: Add Isolation VM support for storvsc driver - v5.17-rc1~70^2~9 062a5c4260cdb734a4727230c58e38accf413315 hyper-v: Enable swiotlb bounce buffer for Isolation VM - v5.17-rc1~70^2~10 c789b90a69045d1924bc0802ae0dce2bba05a04e x86/hyper-v: Add hyperv Isolation VM check in the cc_platform_has() - v5.17-rc1~70^2~11 1a5e91d8375fc8369207cc0b9894a324f2bbf1d9 swiotlb: Add swiotlb bounce buffer remap function for HV IVM - v5.16-rc1~154^2~5 9a8797722e4239242d0cb4cc4baa805df6ac979e Drivers:
[Kernel-packages] [Bug 1951289] Re: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3, 9, 11, 17, 19, 25 report incorrect sched domain for cpu#32
** Changed in: kunpeng920 Importance: Undecided => Low ** Changed in: kunpeng920 Assignee: (unassigned) => dann frazier (dannf) -- 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/1951289 Title: ubuntu_ltp_controllers:cpuset_sched_domains: tests 3,9,11,17,19,25 report incorrect sched domain for cpu#32 Status in kunpeng920: New Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Hirsute: Incomplete Bug description: On scobee-kernel(arm64) with hirsute:linux(5.11.0-41.45) for sru-20211108 there are several reports about the sched domain not covering the full range. The same does not happen on kuzzle. But 32 is a bit of a suspicious number. Running tests... cpuset_sched_domains 1 TINFO: CPUs are numbered continuously starting at 0 (0-127) cpuset_sched_domains 1 TINFO: Nodes are numbered continuously starting at 0 (0-3) cpuset_sched_domains 1 TINFO: root group load balance test cpuset_sched_domains 1 TINFO: sched load balance: 0 cpuset_sched_domains 1 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 1 TPASS: partition sched domains succeeded. cpuset_sched_domains 3 TINFO: root group load balance test cpuset_sched_domains 3 TINFO: sched load balance: 1 cpuset_sched_domains 3 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 3 TFAIL: partition sched domains failed. cpuset_sched_domains 5 TINFO: root group load balance test cpuset_sched_domains 5 TINFO: sched load balance: 0 cpuset_sched_domains 5 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 5 TPASS: partition sched domains succeeded. cpuset_sched_domains 7 TINFO: root group load balance test cpuset_sched_domains 7 TINFO: sched load balance: 0 cpuset_sched_domains 7 TINFO: CPU hotplug: cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 7 TPASS: partition sched domains succeeded. cpuset_sched_domains 9 TINFO: root group load balance test cpuset_sched_domains 9 TINFO: sched load balance: 1 cpuset_sched_domains 9 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 9 TFAIL: partition sched domains failed. cpuset_sched_domains 11 TINFO: root group load balance test cpuset_sched_domains 11 TINFO: sched load balance: 1 cpuset_sched_domains 11 TINFO: CPU hotplug: cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 11 TFAIL: partition sched domains failed. cpuset_sched_domains 13 TINFO: general group load balance test cpuset_sched_domains 13 TINFO: root group info: cpuset_sched_domains 13 TINFO: sched load balance: 0 cpuset_sched_domains 13 TINFO: general group info: cpuset_sched_domains 13 TINFO: cpus: - cpuset_sched_domains 13 TINFO: sched load balance: 1 cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 13 TPASS: partition sched domains succeeded. cpuset_sched_domains 15 TINFO: general group load balance test cpuset_sched_domains 15 TINFO: root group info: cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_sched_domains 15 TINFO: general group info: cpuset_sched_domains 15 TINFO: cpus: 1 cpuset_sched_domains 15 TINFO: sched load balance: 0 cpuset_check_domains1 TPASS : check_sched_domains passed cpuset_sched_domains 15 TPASS: partition sched domains succeeded. cpuset_sched_domains 17 TINFO: general group load balance test cpuset_sched_domains 17 TINFO: root group info: cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_sched_domains 17 TINFO: general group info: cpuset_sched_domains 17 TINFO: cpus: - cpuset_sched_domains 17 TINFO: sched load balance: 1 cpuset_check_domains1 TFAIL : cpuset_sched_domains_check.c:110: cpu32's sched domain is wrong(Domain: 0-127, CPU's Sched Domain: 0-95). cpuset_sched_domains 17 TFAIL: partition sched domains failed. cpuset_sched_domains 19 TINFO: general group load balance test cpuset_sched_domains 19 TINFO: root group info: cpuset_sched_domains 19 TINFO: sched load balance: 1 cpuset_sched_domains 19 TINFO: general group
[Kernel-packages] [Bug 1958591] Re: [amdgpu] Random noise 'static' display after internal display turned off/on
I also have this issue on a thinkpad L14 with ubuntu Ubuntu 20.04.3 LTS, AMD Ryzen 7 pro. The issue appears with the kernel linux-image-5.13.0-1022-oem when is waked up from sleep. The issue is not present with older kernel version. Downgrading to an older version solves the problem. The laptop becomes useless without an external display. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1958591 Title: [amdgpu] Random noise 'static' display after internal display turned off/on Status in linux-hwe-5.13 package in Ubuntu: Confirmed Bug description: Laptop internal display shows random looking 'static' after it's turned off and then on again. e.g. on suspend/resume, or when plugging/unplugging an external monitor. This appeared to come after a `dist-upgrade` took the kernel from 5.11.0-44 to 5.13.0-25 (hwe). Others are seeing this with both NVidia and AMD graphics hardware: - https://www.reddit.com/r/Ubuntu/comments/s8c83w/laptop_shows_static_screen_after_going_into_lock/ - https://www.reddit.com/r/Ubuntu/comments/s8fit0/please_help_static_noise_display_on_ubuntu_2004/ I use i3 under gnome-flashback, but tried using default Ubuntu/Gnome both X and Wayland, and gnome-flashback/metacity. All showed the same problem. Also tried an `apt install --reinstall xserver-xorg-video-radeon libdrm-radeon1` for luck - no joy. Running a 20.04.3 live stick the problem does *not* occur. System: Thinkpad X13 Gen1 Processor: AMD Ryzen 7 PRO 4750U System Firmware: 1.35 $ lsb_release -rd Description:Ubuntu 20.04.3 LTS Release:20.04 Happy to assist with investigations. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.13.0-27.29~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: i3-GNOME-Flashback:GNOME-Flashback:GNOME Date: Thu Jan 20 19:37:09 2022 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Renoir [1002:1636] (rev d1) (prog-if 00 [VGA controller]) Subsystem: Lenovo Renoir [17aa:5082] InstallationDate: Installed on 2021-06-24 (210 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20UF0014US ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-27-generic root=UUID=5db0269f-fa23-487e-ace8-ba99bca814a8 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/20/2021 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET67W(1.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UF0014US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.36 dmi.modalias: dmi:bvnLENOVO:bvrR1CET67W(1.36):bd10/20/2021:br1.36:efr1.36:svnLENOVO:pn20UF0014US:pvrThinkPadX13Gen1:rvnLENOVO:rn20UF0014US:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20UF_BU_Think_FM_ThinkPadX13Gen1: dmi.product.family: ThinkPad X13 Gen 1 dmi.product.name: 20UF0014US dmi.product.sku: LENOVO_MT_20UF_BU_Think_FM_ThinkPad X13 Gen 1 dmi.product.version: ThinkPad X13 Gen 1 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.105-3~20.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.3-0ubuntu0.3~20.04.5 version.libgl1-mesa-glx: libgl1-mesa-glx 21.0.3-0ubuntu0.3~20.04.5 version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1~20.04.2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-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-hwe-5.13/+bug/1958591/+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 1961203] Re: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
*** This bug is a duplicate of bug 1950214 *** https://bugs.launchpad.net/bugs/1950214 ** This bug has been marked a duplicate of bug 1950214 raspi 64 bit Impish image fails update-initramfs with OOM on zstd -- 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/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ Status in linux-firmware package in Ubuntu: New Bug description: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1008-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+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 1961186] Re: [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade
*** This bug is a duplicate of bug 1950214 *** https://bugs.launchpad.net/bugs/1950214 ** This bug has been marked a duplicate of bug 1950214 raspi 64 bit Impish image fails update-initramfs with OOM on zstd -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU][Impish] Unable to boot rpi3a+ after apt dist-upgrade Status in linux-raspi package in Ubuntu: New Bug description: [Description] Unable to boot rpi3a+ after apt dist-upgrade [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt dist-upgrade -y 5. Reboot the system 6. Check kernel version using "uname -a" [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1961186/+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 1961300] Re: linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology
** Also affects: linux-hwe-5.11 (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.11 (Ubuntu Impish)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: linux-hwe-5.11 (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Impish)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Impish)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-hwe-5.11 (Ubuntu Impish)
Status: New => Invalid
** Changed in: linux-hwe-5.11 (Ubuntu Jammy)
Status: New => Invalid
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Changed in: linux-azure (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Impish)
Importance: Undecided => Medium
** Changed in: linux-azure (Ubuntu Jammy)
Importance: Undecided => Medium
** Changed in: linux-hwe-5.11 (Ubuntu Focal)
Importance: Undecided => Medium
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1961300
Title:
linux-azure: Fix NUMA node assignment when kernel boots with custom
NUMA topology
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-hwe-5.11 package in Ubuntu:
Invalid
Status in linux-azure source package in Focal:
In Progress
Status in linux-hwe-5.11 source package in Focal:
In Progress
Status in linux-azure source package in Impish:
In Progress
Status in linux-hwe-5.11 source package in Impish:
Invalid
Status in linux-azure source package in Jammy:
Fix Committed
Status in linux-hwe-5.11 source package in Jammy:
Invalid
Bug description:
SRU Justification
[Impact]
When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI
driver should only set an online NUMA node on the device. This can happen
during KDUMP where some NUMA nodes are not made online by the KDUMP kernel.
This patch also fixes the case where kernel is booting with "numa=off".
Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and
support PCI_BUS_RELATIONS2")
[Test Case]
Microsoft tested.
[Where things could go wrong]
NUMA node assignments could be wrong.
[Other Info]
SF: #00323281
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961300/+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 1952933] Re: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq
I've identified the problem(s) and reported it upstream: https://lore.kernel.org/linux- pci/Yf2wTLjmcRj+AbDv@xps13.dannf/T/#m4d8283082c3fded15050e03a9ad8aef53ad07394 -- 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/1952933 Title: impish kernel crashes on hp m400 in mlx4_en_poll_rx_cq Status in linux package in Ubuntu: Confirmed Status in linux source package in Impish: Confirmed Bug description: During MAAS deployment: [ 107.768146] Unable to handle kernel read from unreadable memory at virtual address domain : maas[ 107.943413] Mem abort info: rootserver: 10.229.32.21 rootpath: filename :[ 108.043666] ESR = 0x9604 lpxelinux.0 :: root=squash:http://10.229.32.21:5248/images/ubu[ 108.147045] EC = 0x25: DABT (current EL), IL = 32 bits ntu/arm64/xgene-uboot/impish/stable/squashfs :: mount_squash do[ 108.277541] SET = 0, FnV = 0 wnloading http://10.229.32.21:5248/images/ubuntu/arm64/xgene-ubo[ 108.380921] EA = 0, S1PTW = 0 ot/impish/stable/squashfs to /root.tmp.img Connecting to 10.229[ 108.485351] Data abort info: .32.21:5248 (10.229.32.21:5248) [ 108.586639] ISV = 0, ISS = 0x0004 [ 108.667060] CM = 0, WnR = 0 [ 108.702635] user pgtable: 4k pages, 48-bit VAs, pgdp=00401ce02000 root.tmp.img [ 108.779941] [] pgd=, p4d= 4% [ 108.884372] Internal error: Oops: 9604 [#1] SMP [ 108.948102] Modules linked in: raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor xor_neon raid6_pq libcrc32c raid1 raid0 multipath linear mlx4_ib ib_uverbs ib_core mlx4_en mlx4_core gpio_keys_polled gpio_dwapb crct10dif_ce ahci_xgene gpio_xgene_sb aes_neon_bs aes_neon_blk crypto_simd cryptd [ 109.286243] CPU: 0 PID: 11 Comm: ksoftirqd/0 Not tainted 5.13.0-20-generic #20-Ubuntu [ 109.380233] Hardware name: HP ProLiant m400 Server Cartridge (DT) [ 109.453258] pstate: 6045 (nZCv daif +PAN -UAO -TCO BTYPE=--) [ 109.525342] pc : mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 109.589087] lr : mlx4_en_poll_rx_cq+0x7c/0x17c [mlx4_en] [ 109.652828] sp : 8000129cbc60 [ 109.692470] x29: 8000129cbc60 x28: 012c x27: 000ff7e95fc0 [ 109.778115] x26: x25: 20908508 x24: 21b40940 [ 109.863763] x23: 20908508 x22: 20908400 x21: 21b4 [ 109.949409] x20: 0040 x19: 0040 x18: 0014 [ 110.035056] x17: 1122e350 x16: cb46f8bb x15: e2b6a183 [ 110.120703] x14: 26fff11e x13: 9312ff0b x12: [ 110.206349] x11: 0006 x10: 0040 x9 : 89119320 [ 110.291997] x8 : 08acdc00 x7 : 02c0 x6 : dff8 [ 110.377642] x5 : 0394 x4 : 03960040 x3 : 21c2 [ 110.463289] x2 : x1 : x0 : [ 110.548937] Call trace: [ 110.578147] mlx4_en_poll_rx_cq+0xb4/0x17c [mlx4_en] [ 110.637719] __napi_poll+0x40/0x1e0 [ 110.679551] net_rx_action+0x2d8/0x34c [ 110.724513] __do_softirq+0x128/0x388 [ 110.768432] run_ksoftirqd+0x6c/0x94 [ 110.811308] smpboot_thread_fn+0x15c/0x1a0 [ 110.860443] kthread+0x114/0x120 [ 110.899145] ret_from_fork+0x10/0x18 [ 110.942024] Code: 1100fc41 1a82b021 13067c21 93407c21 (f8617800) [ 111.015158] ---[ end trace b37ae99414884442 ]--- [ 111.070550] Kernel panic - not syncing: Oops: Fatal exception in interrupt [ 111.152964] SMP: stopping secondary CPUs [ 111.200016] Kernel Offset: 0x8 from 0x80001000 [ 111.265837] PHYS_OFFSET: 0x40 [ 111.309651] CPU features: 0x0251,0046 [ 111.361915] Memory Limit: none [ 111.398431] ---[ end Kernel panic - not syncing: Oops: Fatal exception in interrupt ]--- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1952933/+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 1961300] [NEW] linux-azure: Fix NUMA node assignment when kernel boots with custom NUMA topology
Public bug reported:
SRU Justification
[Impact]
When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI
driver should only set an online NUMA node on the device. This can happen
during KDUMP where some NUMA nodes are not made online by the KDUMP kernel.
This patch also fixes the case where kernel is booting with "numa=off".
Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support
PCI_BUS_RELATIONS2")
[Test Case]
Microsoft tested.
[Where things could go wrong]
NUMA node assignments could be wrong.
[Other Info]
SF: #00323281
** Affects: linux-azure (Ubuntu)
Importance: Undecided
Assignee: Tim Gardner (timg-tpi)
Status: Fix Committed
** Affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Assignee: Tim Gardner (timg-tpi)
Status: Fix Committed
** Package changed: linux (Ubuntu) => linux-azure (Ubuntu)
** Changed in: linux-azure (Ubuntu)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
** Also affects: linux-azure (Ubuntu Jammy)
Importance: Undecided
Assignee: Tim Gardner (timg-tpi)
Status: New
** Changed in: linux-azure (Ubuntu Jammy)
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/1961300
Title:
linux-azure: Fix NUMA node assignment when kernel boots with custom
NUMA topology
Status in linux-azure package in Ubuntu:
Fix Committed
Status in linux-azure source package in Jammy:
Fix Committed
Bug description:
SRU Justification
[Impact]
When kernel boots with a NUMA topology with some NUMA nodes offline, the PCI
driver should only set an online NUMA node on the device. This can happen
during KDUMP where some NUMA nodes are not made online by the KDUMP kernel.
This patch also fixes the case where kernel is booting with "numa=off".
Fixes: 999dd956d838 ("PCI: hv: Add support for protocol 1.3 and
support PCI_BUS_RELATIONS2")
[Test Case]
Microsoft tested.
[Where things could go wrong]
NUMA node assignments could be wrong.
[Other Info]
SF: #00323281
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1961300/+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 1961235] Re: 5.13.0-28-generic usbc video output
** Description changed: When I start my laptop with Ubuntu 21.10 and with a dock station DELL WD19S, the laptop becomes very unresponsive. Furthermore, if i unplug it an plug it again, it don't work... no video output to external monitors or mouse. linux-image-5.13.0-28-generic. Dmesg output when unplug an plug the dock station again: + ... + [ 1036.064752] i915 :00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF D to get idle + [ 1036.192475] i915 :00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns + [ 1036.192486] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful + ... [ 2126.814265] atkbd serio0: Unknown key pressed (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.814276] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.817581] atkbd serio0: Unknown key released (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.817592] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.836552] msi_wmi: Unknown event received - ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: wineos 3847 F pulseaudio /dev/snd/controlC1: wineos 3847 F pulseaudio /dev/snd/controlC0: wineos 3847 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Feb 17 15:38:24 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2020-11-30 (443 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd. Modern 15 A11M ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_skan4e@/vmlinuz-5.13.0-28-generic root=ZFS=rpool/ROOT/ubuntu_skan4e ro i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=igfx_off drm.debug=0 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.4 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-28 (81 days ago) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1552IMS.118 dmi.board.asset.tag: Default string dmi.board.name: MS-1552 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1552IMS.118:bd07/30/2021:br1.24:svnMicro-StarInternationalCo.,Ltd.:pnModern15A11M:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1552:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku1552.1: dmi.product.family: Modern dmi.product.name: Modern 15 A11M dmi.product.sku: 1552.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. -- 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/1961235 Title: 5.13.0-28-generic usbc video output Status in linux package in Ubuntu: Confirmed Bug description: When I start my laptop with Ubuntu 21.10 and with a dock station DELL WD19S, the laptop becomes very unresponsive. Furthermore, if i unplug it an plug it again, it don't work... no video output to external monitors or mouse. linux-image-5.13.0-28-generic. Dmesg output when unplug an plug the dock station again: ... [ 1036.064752] i915 :00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF D to get idle [ 1036.192475] i915 :00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns [ 1036.192486] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful ... [ 2126.814265] atkbd serio0: Unknown key pressed (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.814276] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.817581] atkbd serio0: Unknown key released (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.817592] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.836552] msi_wmi: Unknown event received ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64
[Kernel-packages] [Bug 1961199] Re: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
** Description changed: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages This prevents installing OEM kernels with nvidia, offline, from Ubuntu Desktop Focal point release media. Note this package is in the ship-live .debs archive pool only. -- Resolution of this bug report requires meta & lrm respin. 1022 - meta & lrm bad 1023 - meta is good; lrm is bad 1024 - will have meta & lrm good, but not prepared yet Preparing LRM only respin of 1023, in case 1024 is not available on time. - Jira card KSRU-1133 + Tracker https://bugs.launchpad.net/kernel-sru-workflow/+bug/1961204 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961199 Title: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages Status in linux-restricted-modules-oem-5.14 package in Ubuntu: New Status in linux-restricted-modules-oem-5.14 source package in Focal: New Bug description: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages This prevents installing OEM kernels with nvidia, offline, from Ubuntu Desktop Focal point release media. Note this package is in the ship-live .debs archive pool only. -- Resolution of this bug report requires meta & lrm respin. 1022 - meta & lrm bad 1023 - meta is good; lrm is bad 1024 - will have meta & lrm good, but not prepared yet Preparing LRM only respin of 1023, in case 1024 is not available on time. Jira card KSRU-1133 Tracker https://bugs.launchpad.net/kernel-sru-workflow/+bug/1961204 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-5.14/+bug/1961199/+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 1961235] 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/1961235 Title: 5.13.0-28-generic usbc video output Status in linux package in Ubuntu: Confirmed Bug description: When I start my laptop with Ubuntu 21.10 and with a dock station DELL WD19S, the laptop becomes very unresponsive. Furthermore, if i unplug it an plug it again, it don't work... no video output to external monitors or mouse. linux-image-5.13.0-28-generic. Dmesg output when unplug an plug the dock station again: [ 2126.814265] atkbd serio0: Unknown key pressed (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.814276] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.817581] atkbd serio0: Unknown key released (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.817592] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.836552] msi_wmi: Unknown event received ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: wineos 3847 F pulseaudio /dev/snd/controlC1: wineos 3847 F pulseaudio /dev/snd/controlC0: wineos 3847 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Feb 17 15:38:24 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2020-11-30 (443 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd. Modern 15 A11M ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_skan4e@/vmlinuz-5.13.0-28-generic root=ZFS=rpool/ROOT/ubuntu_skan4e ro i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=igfx_off drm.debug=0 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.4 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-28 (81 days ago) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1552IMS.118 dmi.board.asset.tag: Default string dmi.board.name: MS-1552 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1552IMS.118:bd07/30/2021:br1.24:svnMicro-StarInternationalCo.,Ltd.:pnModern15A11M:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1552:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku1552.1: dmi.product.family: Modern dmi.product.name: Modern 15 A11M dmi.product.sku: 1552.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1961235/+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 1961235] Re: 5.13.0-28-generic usbc video output
** Description changed: - When I start my laptop with Ubuntu 21.10 and with my dock station DELL WD19S it is very unresposive. Furthermore, if i unplug it an plug it again, it don't work... no video output to external monitors or mouse. - I need to disable in settings screens or unplug dock from usbc. If disable screens, mouse continue to work so the problem seems to be only with video output. + When I start my laptop with Ubuntu 21.10 and with a dock station DELL + WD19S, the laptop becomes very unresponsive. Furthermore, if i unplug it + an plug it again, it don't work... no video output to external monitors + or mouse. linux-image-5.13.0-28-generic. - Dmesg has a lot of errors like this: - [ 1826.094456] i915 :00:02.0: [drm] *ERROR* Timeout waiting for DDI BUF D to get idle - [ 1826.222507] i915 :00:02.0: [drm] *ERROR* Timed out waiting for DP idle patterns - [ 1826.222518] i915 :00:02.0: [drm] *ERROR* Link Training Unsuccessful + Dmesg output when unplug an plug the dock station again: + [ 2126.814265] atkbd serio0: Unknown key pressed (translated set 2, code 0xf0 on isa0060/serio0). + [ 2126.814276] atkbd serio0: Use 'setkeycodes e070 ' to make it known. + [ 2126.817581] atkbd serio0: Unknown key released (translated set 2, code 0xf0 on isa0060/serio0). + [ 2126.817592] atkbd serio0: Use 'setkeycodes e070 ' to make it known. + [ 2126.836552] msi_wmi: Unknown event received + ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: wineos 3847 F pulseaudio - /dev/snd/controlC1: wineos 3847 F pulseaudio - /dev/snd/controlC0: wineos 3847 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: wineos 3847 F pulseaudio + /dev/snd/controlC1: wineos 3847 F pulseaudio + /dev/snd/controlC0: wineos 3847 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Feb 17 15:38:24 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2020-11-30 (443 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd. Modern 15 A11M ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=es_ES.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=es_ES.UTF-8 + SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_skan4e@/vmlinuz-5.13.0-28-generic root=ZFS=rpool/ROOT/ubuntu_skan4e ro i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=igfx_off drm.debug=0 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.13.0-28-generic N/A - linux-backports-modules-5.13.0-28-generic N/A - linux-firmware 1.201.4 + linux-restricted-modules-5.13.0-28-generic N/A + linux-backports-modules-5.13.0-28-generic N/A + linux-firmware 1.201.4 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-28 (81 days ago) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1552IMS.118 dmi.board.asset.tag: Default string dmi.board.name: MS-1552 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1552IMS.118:bd07/30/2021:br1.24:svnMicro-StarInternationalCo.,Ltd.:pnModern15A11M:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1552:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku1552.1: dmi.product.family: Modern dmi.product.name: Modern 15 A11M dmi.product.sku: 1552.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. -- 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/1961235 Title: 5.13.0-28-generic usbc video output Status in linux package in Ubuntu: Confirmed Bug description: When I start my laptop with Ubuntu 21.10 and with a dock station DELL WD19S, the laptop becomes very unresponsive. Furthermore, if i unplug it an plug it again, it don't work... no video output to external monitors or mouse. linux-image-5.13.0-28-generic. Dmesg output when unplug an plug the dock station again: [ 2126.814265] atkbd
[Kernel-packages] [Bug 1961203] Re: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 update-initramfs: failed for /boot/initrd.img-5.13.0-1008-raspi with 1. -- 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/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ Status in linux-firmware package in Ubuntu: New Bug description: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1008-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+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 1961203] Re: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
Running out of memory because of initrd zstd compression. Not a kernel problem. -- 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/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ Status in linux-firmware package in Ubuntu: New Bug description: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1008-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+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 1961235] [NEW] 5.13.0-28-generic usbc video output
Public bug reported: When I start my laptop with Ubuntu 21.10 and with a dock station DELL WD19S, the laptop becomes very unresponsive. Furthermore, if i unplug it an plug it again, it don't work... no video output to external monitors or mouse. linux-image-5.13.0-28-generic. Dmesg output when unplug an plug the dock station again: [ 2126.814265] atkbd serio0: Unknown key pressed (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.814276] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.817581] atkbd serio0: Unknown key released (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.817592] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.836552] msi_wmi: Unknown event received ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: wineos 3847 F pulseaudio /dev/snd/controlC1: wineos 3847 F pulseaudio /dev/snd/controlC0: wineos 3847 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Feb 17 15:38:24 2022 HibernationDevice: RESUME=none InstallationDate: Installed on 2020-11-30 (443 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: Micro-Star International Co., Ltd. Modern 15 A11M ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=es_ES.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_skan4e@/vmlinuz-5.13.0-28-generic root=ZFS=rpool/ROOT/ubuntu_skan4e ro i915.enable_gvt=1 kvm.ignore_msrs=1 intel_iommu=igfx_off drm.debug=0 quiet splash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.4 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-11-28 (81 days ago) dmi.bios.date: 07/30/2021 dmi.bios.release: 1.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: E1552IMS.118 dmi.board.asset.tag: Default string dmi.board.name: MS-1552 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrE1552IMS.118:bd07/30/2021:br1.24:svnMicro-StarInternationalCo.,Ltd.:pnModern15A11M:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-1552:rvrREV1.0:cvnMicro-StarInternationalCo.,Ltd.:ct10:cvrDefaultstring:sku1552.1: dmi.product.family: Modern dmi.product.name: Modern 15 A11M dmi.product.sku: 1552.1 dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug impish ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1961235/+attachment/5561638/+files/lspci-vnvn.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/1961235 Title: 5.13.0-28-generic usbc video output Status in linux package in Ubuntu: Confirmed Bug description: When I start my laptop with Ubuntu 21.10 and with a dock station DELL WD19S, the laptop becomes very unresponsive. Furthermore, if i unplug it an plug it again, it don't work... no video output to external monitors or mouse. linux-image-5.13.0-28-generic. Dmesg output when unplug an plug the dock station again: [ 2126.814265] atkbd serio0: Unknown key pressed (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.814276] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.817581] atkbd serio0: Unknown key released (translated set 2, code 0xf0 on isa0060/serio0). [ 2126.817592] atkbd serio0: Use 'setkeycodes e070 ' to make it known. [ 2126.836552] msi_wmi: Unknown event received ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: wineos 3847 F pulseaudio /dev/snd/controlC1: wineos 3847 F pulseaudio /dev/snd/controlC0: wineos 3847 F pulseaudio CasperMD5CheckResult: unknown Date: Thu Feb 17 15:38:24 2022 HibernationDevice:
[Kernel-packages] [Bug 1960427] Re: Add inner_ipproto into sec_path
** Changed in: linux-bluefield (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1960427 Title: Add inner_ipproto into sec_path Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Focal: Fix Committed Bug description: * Explain the bug(s) The inner_ipproto saves the inner IP protocol of the plain text packet. This allows vendor's IPsec feature making offload decision at skb's features_check and configuring hardware at ndo_start_xmit. For example, ConnectX6-DX IPsec device needs the plaintext's IP protocol to support partial checksum offload on VXLAN/GENEVE packet over IPsec transport mode tunnel * Brief explanation of fixes As this data unrelated to the specific driver (the inner ip protocol of the plain text) then it makes sense to provide it in the xfrm stack layer to avoid code duplication in various drivers and do it on the fly in the xfrm layer instead of reparse the packet at the driver layer. * How to test Need to make sure that the code compiles post this change, run TCP encapsulated traffic (for example using vxlan) when IPSec crypto offload with transport mode is configured * What it could break. NA, this function adds data to a new field introduced to struct xfrm_offload, so if not used it have no effect and it is assigned in stack and used in driver so if driver does not used it then no effect. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1960427/+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 1786013] Autopkgtest regression report (linux-meta-hwe-5.15/5.15.0.22.22~20.04.4)
All autopkgtests for the newly accepted linux-meta-hwe-5.15 (5.15.0.22.22~20.04.4) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.15/5.15.0-22.22~20.04.1 (armhf) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1961203] Re: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
ubuntu@ubuntu:~$ sudo apt install linux-firmware Reading package lists... Done Building dependency tree... Done Reading state information... Done The following packages will be upgraded: linux-firmware 1 upgraded, 0 newly installed, 0 to remove and 87 not upgraded. Need to get 199 MB of archives. After this operation, 1,594 kB of additional disk space will be used. Get:1 http://ports.ubuntu.com/ubuntu-ports impish-updates/main arm64 linux-firmware all 1.201.4 [199 MB] Fetched 199 MB in 4min 56s (671 kB/s) (Reading database ... 82311 files and directories currently installed.) Preparing to unpack .../linux-firmware_1.201.4_all.deb ... Unpacking linux-firmware (1.201.4) over (1.201) ... Setting up linux-firmware (1.201.4) ... update-initramfs: Generating /boot/initrd.img-5.13.0-1008-raspi Killed E: mkinitramfs failure zstd -q -19 -T0 137 update-initramfs: failed for /boot/initrd.img-5.13.0-1008-raspi with 1. dpkg: error processing package linux-firmware (--configure): installed linux-firmware package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-firmware needrestart is being skipped since dpkg has failed E: Sub-process /usr/bin/dpkg returned an error code (1) -- 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/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ Status in linux-firmware package in Ubuntu: New Bug description: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1008-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+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 1939210] Re: When using HWE, zfs-kmod and zfs user tools versions must match
I have the same problem. In my case, it is caused by upgrading the NVIDIA driver metapackage to 510 from 470. I am very grateful to @lockszmith for sharing his steps on https://askubuntu.com/questions/1388997/zsys-commit-service-fails-with- couldnt-promote-dataset-not-a-cloned-filesy It really makes me very wary of upgrading my systems. Those are LTS releases and things like this are very concerning. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1939210 Title: When using HWE, zfs-kmod and zfs user tools versions must match Status in zfs-linux package in Ubuntu: Confirmed Status in zsys package in Ubuntu: Confirmed Bug description: Ubuntu 20.04.2 LTS I ran into a problem recently (https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939177) due to mismatched versions when HWE upgraded the kernel from 5.8 to 5.11 where the userspace tools don't match the zfs-kmod version. After the update the system ended up with zfs-0.8.3-1ubuntu12.12 and zfs- kmod-2.0.2-1ubuntu5 My understanding from asking in the OpenZFS github is that the two versions must match. This bug is to figure out what to do for those of us who use HWE and zfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1939210/+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 1947568] Re: cannot promote clone: "not a cloned filesystem"
I have the same problem. In my case, it is caused by upgrading the NVIDIA driver metapackage to 510 from 470. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1947568 Title: cannot promote clone: "not a cloned filesystem" Status in zfs-linux package in Ubuntu: Confirmed Bug description: I have a zvol containing a Windows image for a virtual machine. After restarting the system a node under /dev/zvol/... was not created for the virtual disk and no amount of prompting by `udevadm trigger` helped. Instead I created a snapshot from the most recent hourly backup: # zfs clone rpool/vm/windows/windows10/hda@hourly07 rpool/vm/windows/windows10/hda-new # zfs promote rpool/vm/windows/windows10/hda-new cannot promote 'rpool/vm/windows/windows10/hda-new': not a cloned filesystem (didn't work here but carried on assuming something can be sorted later) # zfs rename rpool/vm/windows/windows10/hda rpool/vm/windows/windows10/hda-old # zfs rename rpool/vm/windows/windows10/hda-new rpool/vm/windows/windows10/hda Entries in /dev appeared and I could start the virtual machine. Trying to promote the clone gives 'not a cloned filesystem' message. I later renamed the old zvol and tried to cleanup: # zfs rename rpool/vm/windows/windows10/hda-old rpool/to-be-deleted # zfs destroy rpool/to-be-deleted@hourly07 cannot destroy 'rpool/to-be-deleted@hourly07': snapshot has dependent clones use '-R' to destroy the following datasets: rpool/vm/windows/windows10/hda@hourly09 rpool/vm/windows/windows10/hda@hourly10 rpool/vm/windows/windows10/hda # zfs promote rpool/vm/windows/windows10/hda cannot promote 'rpool/vm/windows/windows10/hda': not a cloned filesystem # zfs get origin rpool/vm/windows/windows10/hda NAMEPROPERTY VALUE SOURCE rpool/vm/windows/windows10/hda originrpool/to-be-deleted@hourly07 - # zfs get clones rpool/to-be-deleted@hourly07 NAME PROPERTY VALUE SOURCE rpool/to-be-deleted@hourly07 clonesrpool/vm/windows/windows10/hda - The dependency between seems to be as expected. This small test fails in the same way: # zfs create -V1G rpool/vm/test # zfs snapshot rpool/vm/test@test2 # zfs clone rpool/vm/test@test2 rpool/vm/test3 # zfs promote rpool/vm/test3 cannot promote 'rpool/vm/test3': not a cloned filesystem # zfs get origin rpool/vm/test3 NAMEPROPERTY VALUESOURCE rpool/vm/test3 originrpool/vm/test@test2 - # zfs get clones rpool/vm/test@test2 NAME PROPERTY VALUE SOURCE rpool/vm/test@test2 clonesrpool/vm/test3 - All the zpool members are ONLINE and no errors are reported. # lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal # uname -r 5.11.0-37-generic # modinfo zfs | grep -i version version:2.0.2-1ubuntu5.1 srcversion: F267DF7B3FFB43AFE76257D vermagic: 5.11.0-37-generic SMP mod_unload modversions # apt-cache policy zfsutils-linux zfsutils-linux: Installed: 0.8.3-1ubuntu12.12 Candidate: 0.8.3-1ubuntu12.13 Version table: 0.8.3-1ubuntu12.13 500 500 http://gb.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages *** 0.8.3-1ubuntu12.12 100 100 /var/lib/dpkg/status 0.8.3-1ubuntu12.9 500 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 0.8.3-1ubuntu12 500 500 http://gb.archive.ubuntu.com/ubuntu focal/main amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1947568/+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 1961203] Re: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
** Tags added: sru ** Description changed: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: - https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz + https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ - Kernel Version: 5.13.0-1016-raspi + Kernel Version: 5.13.0-1008-raspi -- 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/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ Status in linux-firmware package in Ubuntu: New Bug description: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1008-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+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 1933301] Re: [uacc-0623] hisi_sec2 fail to alloc uacce
Focal 5.13.0-30-generic #33~20.04.1-Ubuntu verification passed. ubuntu@segers:~$ uname -a; lsb_release -a; sudo dmesg | grep "fail to alloc uacce" Linux segers 5.13.0-30-generic #33~20.04.1-Ubuntu SMP Mon Feb 7 14:28:43 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 20.04.3 LTS Release:20.04 Codename: focal ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- 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/1933301 Title: [uacc-0623] hisi_sec2 fail to alloc uacce Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-20.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-21.10 series: Fix Committed Status in kunpeng920 ubuntu-22.04 series: Fix Committed Status in linux package in Ubuntu: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: Fix Committed Bug description: SRU Justification = [Impact] * Users with HiSilicon Security Engine (SEC) version 2 controller fail to allocate Uacce. [Fix] * upstream 183b60e005975d3c84c22199ca64a9221e620fb6 crypto: hisilicon/qm - modify the uacce mode check [Test Plan] * Deploy Ubuntu Focal with HWE 5.13 kernel to a Kunpeng920 chip with HiSilicon Security Engine (SEC) version 2 controller * Boot the system * 'dmesg | grep "fail to alloc uacce"' and you will see complains from hisi_sec2. For example: [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Where problems could occur] * The regression can be considered as low, since it is HiSilicon crypto system specific == Original Bug Description == [Bug Description] ubuntu 20.04.2 boot system and fail to alloc uacce (-22) [Steps to Reproduce] 1) boot ubuntu 20.04.2 system 2) dmesg | grep fail [Actual Results] [ 27.86] cma: cma_alloc: alloc failed, req-size: 4 pages, ret: -12 [ 27.006515] hisi_sec2 :b6:00.0: Failed to enable PASID [ 27.012043] hisi_sec2 :b6:00.0: Adding to iommu group 45 [ 27.015484] hisi_sec2 :b6:00.0: fail to alloc uacce (-22) [Expected Results] no fail [Reproducibility] 100% [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] this following patches will solve this bug. commit f8408d2b79b834f79b6c578817e84f74a85d2190 Author: Kai Ye Date: Tue Jan 5 14:16:42 2021 +0800 crypto: hisilicon - add ZIP device using mode parameter Add 'uacce_mode' parameter for ZIP, which can be set as 0(default) or 1. '0' means ZIP is only registered to kernel crypto, and '1' means it's registered to both kernel crypto and UACCE. Signed-off-by: Kai Ye Reviewed-by: Zhou Wang Reviewed-by: Zaibo Xu Signed-off-by: Herbert Xu commit bedd04e4aa1434d2f0f038e15bb6c48ac36876e1 Author: Kai Ye Date: Tue Jan 5 14:16:43 2021 +0800 crypto: hisilicon/hpre - register HPRE device to uacce commit 34932a6033be3c0088935c334e4dc5ad43dcb0cc Author: Kai Ye Date: Tue Jan 5 14:16:44 2021 +0800 crypto: hisilicon/sec - register SEC device to uacce To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1933301/+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 1961203] [NEW] [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+
Public bug reported: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-raspi (Ubuntu) => linux-firmware (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1961203 Title: [SRU][Impish] Failed to upgrade linux-firmware on rpi3a+ Status in linux-firmware package in Ubuntu: New Bug description: [Description] Failed to upgrade linux-firmware on rpi3a+ [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz 2. Boot into system 3. sudo apt update 4. sudo apt install linux-firmware [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Image: ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1961203/+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 1961202] [NEW] Disable on-demand mode if nvidia-390 is in use
Public bug reported: As improvement, we can disable on-demand option from nvidia-settings to prevent "fallback to performance mode" confusion after user selects "on-demand" mode. The fallback still need to keep there to handle user switches it through command line. ** Affects: oem-priority Importance: Low Assignee: jeremyszu (os369510) Status: Confirmed ** Affects: nvidia-settings (Ubuntu) Importance: Undecided Assignee: jeremyszu (os369510) Status: New ** Tags: oem-priority ** Changed in: nvidia-settings (Ubuntu) Assignee: (unassigned) => jeremyszu (os369510) ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Assignee: (unassigned) => jeremyszu (os369510) ** Changed in: oem-priority Importance: Undecided => Low ** Changed in: oem-priority Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1961202 Title: Disable on-demand mode if nvidia-390 is in use Status in OEM Priority Project: Confirmed Status in nvidia-settings package in Ubuntu: New Bug description: As improvement, we can disable on-demand option from nvidia-settings to prevent "fallback to performance mode" confusion after user selects "on-demand" mode. The fallback still need to keep there to handle user switches it through command line. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1961202/+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 1961202] Re: Disable on-demand mode if nvidia-390 is in use
** Tags added: oem-priority -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1961202 Title: Disable on-demand mode if nvidia-390 is in use Status in OEM Priority Project: Confirmed Status in nvidia-settings package in Ubuntu: New Bug description: As improvement, we can disable on-demand option from nvidia-settings to prevent "fallback to performance mode" confusion after user selects "on-demand" mode. The fallback still need to keep there to handle user switches it through command line. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1961202/+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 1961199] Re: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
** Description changed: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages This prevents installing OEM kernels with nvidia, offline, from Ubuntu Desktop Focal point release media. Note this package is in the ship-live .debs archive pool only. -- Resolution of this bug report requires meta & lrm respin. 1022 - meta & lrm bad 1023 - meta is good; lrm is bad 1024 - will have meta & lrm good, but not prepared yet Preparing LRM only respin of 1023, in case 1024 is not available on time. + + + Jira card KSRU-1133 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961199 Title: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages Status in linux-restricted-modules-oem-5.14 package in Ubuntu: New Status in linux-restricted-modules-oem-5.14 source package in Focal: New Bug description: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages This prevents installing OEM kernels with nvidia, offline, from Ubuntu Desktop Focal point release media. Note this package is in the ship-live .debs archive pool only. -- Resolution of this bug report requires meta & lrm respin. 1022 - meta & lrm bad 1023 - meta is good; lrm is bad 1024 - will have meta & lrm good, but not prepared yet Preparing LRM only respin of 1023, in case 1024 is not available on time. Jira card KSRU-1133 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-5.14/+bug/1961199/+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 1961199] [NEW] Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages
Public bug reported: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages This prevents installing OEM kernels with nvidia, offline, from Ubuntu Desktop Focal point release media. Note this package is in the ship-live .debs archive pool only. -- Resolution of this bug report requires meta & lrm respin. 1022 - meta & lrm bad 1023 - meta is good; lrm is bad 1024 - will have meta & lrm good, but not prepared yet Preparing LRM only respin of 1023, in case 1024 is not available on time. ** Affects: linux-restricted-modules-oem-5.14 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-restricted-modules-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-restricted-modules-oem-5.14 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-restricted-modules-oem-5.14 (Ubuntu Focal) Milestone: None => ubuntu-20.04.4 ** Changed in: linux-restricted-modules-oem-5.14 (Ubuntu) Milestone: None => ubuntu-20.04.4 ** Description changed: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages This prevents installing OEM kernels with nvidia, offline, from Ubuntu Desktop Focal point release media. + + Note this package is in the ship-live .debs archive pool only. + + -- + + Resolution of this bug report requires meta & lrm respin. + 1022 - meta & lrm bad + 1023 - meta is good; lrm is bad + 1024 - will have meta & lrm good, but not prepared yet + + Preparing LRM only respin of 1023, in case 1024 is not available on + time. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-restricted-modules-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1961199 Title: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages Status in linux-restricted-modules-oem-5.14 package in Ubuntu: New Status in linux-restricted-modules-oem-5.14 source package in Focal: New Bug description: Missing oem-20.04 flavour for nvidia-modules of oem-5.14 packages This prevents installing OEM kernels with nvidia, offline, from Ubuntu Desktop Focal point release media. Note this package is in the ship-live .debs archive pool only. -- Resolution of this bug report requires meta & lrm respin. 1022 - meta & lrm bad 1023 - meta is good; lrm is bad 1024 - will have meta & lrm good, but not prepared yet Preparing LRM only respin of 1023, in case 1024 is not available on time. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-restricted-modules-oem-5.14/+bug/1961199/+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 1937295] Re: [SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping is enabled by IOMMU
** Changed in: linux (Ubuntu Impish)
Status: In Progress => 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/1937295
Title:
[SRU]PCI: vmd: Do not disable MSI-X remapping if interrupt remapping
is enabled by IOMMU
Status in subiquity:
Invalid
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
Invalid
Status in linux source package in Focal:
In Progress
Status in linux source package in Impish:
Fix Committed
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
A hardware partner discovered they were unable to install Ubuntu on
some servers using VROC setups. They point to this issue involving
DMAR that is blocking discovery of the VROC RAID devices:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=2565e5b69c44b4e42469afea3cc5a97e74d1ed45
`git bisect` points to this offending commit ee81ee84f873 ("PCI:
vmd: Disable MSI-X remapping when possible"), which disables VMD MSI
remapping. The IOMMU hardware blocks the compatibility format
interrupt request because Interrupt Remapping Enable Status (IRES) and
Extended Interrupt Mode Enable (EIME) are enabled. Please refer to
section "5.1.4 Interrupt-Remapping Hardware Operation" in Intel VT-d
spec.
To fix the issue, VMD driver still enables the interrupt remapping
irrespective of VMD_FEAT_CAN_BYPASS_MSI_REMAP if the IOMMU subsystem
enables the interrupt remapping.
[Fix]
2565e5b69c44 PCI: vmd: Do not disable MSI-X remapping if interrupt
remapping is enabled by IOMMU
[Test Plan]
1. Boot into VRoC controller in uEFI Setup and create a raid10 disk.
2. Install affected Ubuntu release on the RAID10.
3. The system hangs at "Partitions formatting 33%".
[Where problems could occur]
The fix itself is a very small change to drivers/pci/controller/vmd.c
and problems should not occur. The root cause was discovered by the
hardware partner's engineers, who tested and submitted it upstream
where it was accepted and landed in 5.16.
That said, I doubt this will fix 18.04.6 as it would require a respin
to get the patched kernel onto the ISO. 20.04 should pick it up in
ISO in 20.04.5, so there could still be the initial issue since those
ISOs would be lacking the patched kernel.
[Other Info]
As noted, this would need to not only land in the kernel but land in
the kernel in the ISO to resolve the issue in the installation
process. I'll bring this back as far as Focal with the expectation
that while 20.04.4 is too late, it will be present using the GA kernel
in 20.04.5 later on.
*
Original Bug Summary:
A hardware partner has been testing 18.04 subiquity images on their
servers with VROC enabled and configured in a RAID 10 setup.
In their own words:
Steps to reproduce:
1. Boot into VRoC controller in uEFI Setup and create a raid10
disk.
2. Install Ubuntu 18.04.5 on the RAID10.
3. The system hangs at "Partitions formatting 33%".
After looking at the launchpad
(https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1896578/), the
fix was included in the updated kernel.
[Quotes from the launchpad]
The released kernels are:
Hirsute: 5.11.0-22-generic
Groovy: 5.8.0-59-generic
Focal: 5.4.0-77-generic
Bionic: 4.15.0-147-generic
I've asked them to also confirm this on 20.04.2, and check that
20.04.3 dailies fix the issue.
It is at least a very reasonable hypothesis that this will also break
on all current ISO installs as none of them are respun once released
to include updated SRUs in the installation media. This currently
affects 20.04.2 but that will be resolved shortly when 20.04.3
releases as the GA and HWE kernels in that image should have the SRU
that fixes this issue. However, 18.04 has no further releases, and
even the 18.04.5 daily-live and daily images on cdimages.ubuntu.com
are not built after 18.04.5 was released.
To manage notifications about this bug go to:
https://bugs.launchpad.net/subiquity/+bug/1937295/+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 1786013] Autopkgtest regression report (linux-meta-oem-5.14/5.14.0.1023.21)
All autopkgtests for the newly accepted linux-meta-oem-5.14 (5.14.0.1023.21) for focal have finished running. The following regressions have been reported in tests triggered by the package: virtualbox/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) virtualbox-hwe/6.1.26-dfsg-3~ubuntu1.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-oem-5.14 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+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 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Impish) Status: In Progress => 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/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Committed Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: Fix CPU-MF error on new IBM Z Hardware by adding support for CPU-MF counter second version 7 Error Symptom: Daemon cpacfstatsd fails on start up of the system with this error message cpacfstatsd: Event DEA_FUNCTIONS for pmu cpum_cf not found (2:No such file or directory) Problem: When the CPU Measurement facility device driver is initialized during kernel boot, it reads out the CPU Measurement facility counter hardware first and second version numbers. Depending on these numbers the device driver exports attributes in the sysfs directory /sys/devices/cpum_cf/events. When the CPM-MF second version number is not known, no attributes of the crypto counter set are exported. However the cpacfstatsd program scans the sysfs directory /sys/devices/cpum_cf/events for attribute files of the crypto counter set, for example attribute file DEA_FUNCTIONS and others. Solution: Add support for the new CPU-MF Measurement counter facility second version number 7. This number then exports the crypto counter set in directory directory /sys/devices/cpum_cf/events. Also add support for limited samples. These hardware samples contain all zeroes and are of no value when using the CPU Measurement Facility sampling hardware. Drop these samples when the limited sampled bit is set in the sample descriptor. Reproduction: Run command ls -l /sys/devices/cpum_cf/events | fgrep DEA DEA_BLOCKED_CYCLES DEA_BLOCKED_FUNCTIONS DEA_CYCLES DEA_FUNCTIONS When there is no output at all the attributes files for the crypto counter set have not been exported. If above output is visible, the described problem does not show up. Upstream-ID: a87b0fd4f9003f8521226e226cf92b18147b3519 745f5d20e7936931f924410f32d8b0e599b5990e Problem-ID:196017 Preventive:yes Reported: Christian Rund SupportTicket: - Reference: - Date: 2022-01-20 Author:Thomas Richter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+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 1960875] Re: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call
** Changed in: linux (Ubuntu Impish) Status: In Progress => 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/1960875 Title: [UBUNTU 21.10] s390/cio: verify the driver availability for path_event call Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: Description: s390/cio: verify the driver availability for path_event call Symptom: If no driver is attached to a device or the driver does not provide the path_event function, an FCES path-event on this device could end up in a kernel-panic. Problem: There can be path-event generated for devices which are not bound to any drivers. And this is not verified before callback. Solution: Make sure the driver is available before the callback. Reproduction: - Upstream-ID: dd9cb842fa9d90653a9b48aba52f89c069f3bc50 Problem-ID:196414 Distros: Ubuntu 21.10 and higher Preventive:yes Reported: - SupportTicket: - Reference: - Date: 2022-02-14 Author:Vineeth Vijayan Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960875/+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 1960448] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561594/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561595/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] syslog.txt
apport information ** Attachment added: "syslog.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561606/+files/syslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] rfkill.txt
apport information ** Attachment added: "rfkill.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561605/+files/rfkill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] getfacl.txt
apport information ** Attachment added: "getfacl.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561604/+files/getfacl.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561603/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561600/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561602/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561601/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561598/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561599/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561597/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561596/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561592/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561593/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561591/+files/Dependencies.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: dmi.product.family: GSeries dmi.product.name: G3 3579 dmi.product.sku: 086F dmi.sys.vendor: Dell Inc. hciconfig: hci0:Type: Primary Bus: USB BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING RX bytes:17341 acl:0 sco:0 events:2806 errors:0 TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1960448/+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 1960448] Re: Sony WF-XB700 Bluetooth headset not detected
apport information ** Tags added: apport-collected ** Description changed: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu76 + Architecture: amd64 + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-09-09 (160 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + InterestingModules: rfcomm bnep btusb bluetooth + MachineType: Dell Inc. G3 3579 + NonfreeKernelModules: nvidia_modeset nvidia + Package: linux + PackageArchitecture: amd64 + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 + Tags: jammy + Uname: Linux 5.15.0-22-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) + UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/20/2021 + dmi.bios.release: 1.15 + dmi.bios.vendor: Dell Inc. + dmi.bios.version: 1.15.0 + dmi.board.name: 0M5H57 + dmi.board.vendor: Dell Inc. + dmi.board.version: A05 + dmi.chassis.type: 10 + dmi.chassis.vendor: Dell Inc. + dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd04/20/2021:br1.15:svnDellInc.:pnG33579:pvr:rvnDellInc.:rn0M5H57:rvrA05:cvnDellInc.:ct10:cvr:sku086F: + dmi.product.family: GSeries + dmi.product.name: G3 3579 + dmi.product.sku: 086F + dmi.sys.vendor: Dell Inc. + hciconfig: + hci0:Type: Primary Bus: USB + BD Address: 98:2C:BC:33:92:E8 ACL MTU: 1021:4 SCO MTU: 96:6 + UP RUNNING + RX bytes:17341 acl:0 sco:0 events:2806 errors:0 + TX bytes:689073 acl:0 sco:0 commands:2804 errors:0 ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1960448/+attachment/5561590/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1960448 Title: Sony WF-XB700 Bluetooth headset not detected Status in bluez package in Ubuntu: New Status in gnome-bluetooth package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: Gnome-bluetooth does not detect Sony WF-XB700 bluetooth headset. Installed blueman to try to figure out if this is related to gnome- bluetooth - the results are the same. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-bluetooth 3.34.5-4 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown Date: Wed Feb 9 22:01:56 2022 InstallationDate: Installed on 2021-09-09 (153 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) SourcePackage: gnome-bluetooth UpgradeStatus: Upgraded to jammy on 2022-01-13 (27 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-09-09 (160 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Dell Inc. G3 3579 NonfreeKernelModules: nvidia_modeset nvidia Package: linux PackageArchitecture: amd64 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-22-generic root=UUID=fd3be223-e609-4a8d-97fb-31ee2f754766 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.15.0-22.22-generic 5.15.19 Tags: jammy Uname: Linux 5.15.0-22-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-01-13 (34 days ago) UserGroups: adm bluetooth cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/20/2021 dmi.bios.release: 1.15 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.15.0 dmi.board.name: 0M5H57 dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1960933] Re: rtw89_pci constantly drops connection with old firmware
** Changed in: linux-firmware (Ubuntu Impish)
Status: In Progress => Fix Committed
** Changed in: linux-firmware (Ubuntu Impish)
Assignee: (unassigned) => Juerg Haefliger (juergh)
--
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/1960933
Title:
rtw89_pci constantly drops connection with old firmware
Status in linux-firmware package in Ubuntu:
Invalid
Status in linux-firmware source package in Impish:
Fix Committed
Bug description:
[Impact]
This was on a new Lenovo P14s Gen2 AMD. I'm using Ubuntu 21.10
(impish)
The current linux-firmware package (1.201.4+1.201.3) ships with
realtek rtw89_pci firmware (/lib/firmware/rtw89/rtw8852a_fw.bin)
version v0.13.8.0.
My wifi chip wasn't able to keep a connection for more than a minute when
connected to a Rodgers "Advanced Wi-Fi Modem". I searched around tried
disabling the power_save and stuff. But that had little to no effect. I was
about to open an issue on the upstream project and did a last ditch attempt to
see if there were any firmware updates... I found linux-firmware.git and it had
two newer versions!
- v0.13.30.0 (was submitted in May 2021, but it took until october 2021 to
show up)
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=ec17b637b7ab928ca7ebc0389e0e3921f1cc7d17
- v0.13.33.0 (was submitted in November 2021 and got merged in December
2021):
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/rtw89/rtw8852a_fw.bin?id=4a7e1f5cabaebe5c044b94b91149f35471d1e983
I've downloaded and installed the latest "v0.13.33.0" on a whim and
rebooted. And what a pleasant surprise: Instantly, my wifi connection
lasted until the rest of the day.
Could you please consider updating this realtek firmware in the next
release? Thanks!
[Test Case]
See above.
[Fix]
Cherry pick two commit to match current Jammy:
4a7e1f5cabae ("rtw89: 8852a: update fw to v0.13.33.0")
ec17b637b7ab ("rtw89: 8852a: update fw to v0.13.30.0")
[Where Problems Could Occur]
Limited to wifi using RTL8852A HW.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1960933/+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 1961186] Re: [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade
** Package changed: linux-firmware-raspi2 (Ubuntu) => linux-raspi (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1961186 Title: [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade Status in linux-raspi package in Ubuntu: New Bug description: [Description] Unable to boot rpi3+ after apt dist-upgrade [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz?_ga=2.116775055.84446.1645092439-394390262.1600931043 2. Boot into system 3. sudo apt update 4. sudo apt dist-upgrade -y 5. Reboot the system 6. Check kernel version using "uname -a" [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1961186/+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 1959610] Re: ubuntu_kernel_selftests / ftrace:ftracetest do_softirq failure on Jammy realtime
Sent SRU
** Changed in: linux (Ubuntu Jammy)
Importance: Medium => Low
--
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/1959610
Title:
ubuntu_kernel_selftests / ftrace:ftracetest do_softirq failure on
Jammy realtime
Status in ubuntu-kernel-tests:
New
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Jammy:
In Progress
Bug description:
[Impact]
* ubuntu_kernel_selftests / ftrace:ftracetest fails on realtime
kernel.
* ftrace:ftracetest which reports: "echo: I/O error". This is caused
by using "do_softirq" in test which does not exist on preempt RT
kernel.
[Fix]
* Use other function.
* Upstream commit 6fec1ab67f8d ("selftests/ftrace: Do not trace do_softirq
because of PREEMPT_RT")
[Test Plan]
* Run the test on regular (base) and realtime kernel.
[Where problems could occur]
* Only ftracetest tests.
[Other info]
Failure is reported for step 32 in Jenkins job:
23:48:45 DEBUG| [stdout] # selftests: ftrace: ftracetest
23:48:45 DEBUG| [stdout] # === Ftrace unit tests ===
23:48:45 DEBUG| [stdout] # [1] Basic trace file check [PASS]
23:48:49 DEBUG| [stdout] # [2] Basic test for tracers [PASS]
23:48:49 DEBUG| [stdout] # [3] Basic trace clock test [PASS]
23:48:49 DEBUG| [stdout] # [4] Basic event tracing check [PASS]
23:48:50 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS]
23:48:50 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS]
23:48:50 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS]
23:49:38 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers
[PASS]
23:49:57 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes
[PASS]
23:49:57 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe
events [PASS]
23:49:57 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe
events [PASS]
23:49:57 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic
events [PASS]
23:49:57 DEBUG| [stdout] # [13] Generic dynamic event - selective clear
(compatibility) [PASS]
23:49:58 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event
[PASS]
23:49:58 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate
events are caught [PASS]
23:49:58 DEBUG| [stdout] # [16] event tracing - enable/disable with event
level files [PASS]
23:49:58 DEBUG| [stdout] # [17] event tracing - restricts events based on pid
notrace filtering [PASS]
23:49:59 DEBUG| [stdout] # [18] event tracing - restricts events based on pid
[PASS]
23:49:59 DEBUG| [stdout] # [19] event tracing - enable/disable with subsystem
level files [PASS]
23:50:00 DEBUG| [stdout] # [20] event tracing - enable/disable with top level
files [PASS]
23:50:01 DEBUG| [stdout] # [21] Test trace_printk from module [PASS]
23:50:04 DEBUG| [stdout] # [22] ftrace - function graph filters with stack
tracer [PASS]
23:50:05 DEBUG| [stdout] # [23] ftrace - function graph filters [PASS]
23:50:06 DEBUG| [stdout] # [24] ftrace - function pid notrace filters [PASS]
23:50:06 DEBUG| [stdout] # [25] ftrace - function pid filters [PASS]
23:50:08 DEBUG| [stdout] # [26] ftrace - stacktrace filter command[PASS]
23:50:08 DEBUG| [stdout] # [27] ftrace - function trace with cpumask [PASS]
23:50:12 DEBUG| [stdout] # [28] ftrace - test for function event triggers
[PASS]
23:50:13 DEBUG| [stdout] # [29] ftrace - function trace on module [PASS]
23:50:16 DEBUG| [stdout] # [30] ftrace - function profiling [PASS]
23:50:21 DEBUG| [stdout] # [31] ftrace - function profiler with function
tracing [PASS]
23:50:22 DEBUG| [stdout] # [32] ftrace - test reading of set_ftrace_filter
[FAIL]
23:50:24 DEBUG| [stdout] # [33] ftrace - test for function traceon/off
triggers [PASS]
23:50:24 DEBUG| [stdout] # [34] ftrace - test tracing error log support
[PASS]
23:50:28 DEBUG| [stdout] # [35] Test creation and deletion of trace instances
while setting an event [PASS]
23:50:29 DEBUG| [stdout] # [36] Test creation and deletion of trace instances
[PASS]
23:50:30 DEBUG| [stdout] # [37] Kprobe dynamic event - adding and removing
[PASS]
23:50:30 DEBUG| [stdout] # [38] Kprobe dynamic event - busy event check
[PASS]
23:50:30 DEBUG| [stdout] # [39] Kprobe dynamic event with arguments [PASS]
23:50:30 DEBUG| [stdout] # [40] Kprobe event with comm arguments [PASS]
23:50:30 DEBUG| [stdout] # [41] Kprobe event string type argument [PASS]
23:50:31 DEBUG| [stdout] # [42] Kprobe event symbol argument [PASS]
23:50:32 DEBUG| [stdout] # [43] Kprobe event argument syntax [PASS]
23:50:32 DEBUG| [stdout] # [44] Kprobes event arguments with types[PASS]
23:50:32 DEBUG| [stdout] # [45] Kprobe event user-memory access [PASS]
23:50:33
[Kernel-packages] [Bug 1961186] [NEW] [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade
You have been subscribed to a public bug: [Description] Unable to boot rpi3+ after apt dist-upgrade [Steps to reproduce] 1. Flash following image on rpi3a+: https://cdimage.ubuntu.com/releases/21.10/release/ubuntu-21.10-preinstalled-server-arm64+raspi.img.xz?_ga=2.116775055.84446.1645092439-394390262.1600931043 2. Boot into system 3. sudo apt update 4. sudo apt dist-upgrade -y 5. Reboot the system 6. Check kernel version using "uname -a" [Actual result] Error when upgrading kernel, and unable to boot rpi3+ after apt dist-upgrade [Expected result] System can boot up and kernel is upgraded to correct version [Additional information] Hardware: rpi3a+ Kernel Version: 5.13.0-1016-raspi ** Affects: linux-raspi (Ubuntu) Importance: Undecided Status: New -- [SRU][Impish] Unable to boot rpi3+ after apt dist-upgrade https://bugs.launchpad.net/bugs/1961186 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi 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 1960182] Re: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7
** Changed in: linux (Ubuntu Jammy) Importance: High => Medium ** Changed in: linux (Ubuntu Impish) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1960182 Title: [UBUNTU 20.04] kernel: Add support for CPU-MF counter second version 7 Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Impish: In Progress Status in linux source package in Jammy: In Progress Bug description: Fix CPU-MF error on new IBM Z Hardware by adding support for CPU-MF counter second version 7 Error Symptom: Daemon cpacfstatsd fails on start up of the system with this error message cpacfstatsd: Event DEA_FUNCTIONS for pmu cpum_cf not found (2:No such file or directory) Problem: When the CPU Measurement facility device driver is initialized during kernel boot, it reads out the CPU Measurement facility counter hardware first and second version numbers. Depending on these numbers the device driver exports attributes in the sysfs directory /sys/devices/cpum_cf/events. When the CPM-MF second version number is not known, no attributes of the crypto counter set are exported. However the cpacfstatsd program scans the sysfs directory /sys/devices/cpum_cf/events for attribute files of the crypto counter set, for example attribute file DEA_FUNCTIONS and others. Solution: Add support for the new CPU-MF Measurement counter facility second version number 7. This number then exports the crypto counter set in directory directory /sys/devices/cpum_cf/events. Also add support for limited samples. These hardware samples contain all zeroes and are of no value when using the CPU Measurement Facility sampling hardware. Drop these samples when the limited sampled bit is set in the sample descriptor. Reproduction: Run command ls -l /sys/devices/cpum_cf/events | fgrep DEA DEA_BLOCKED_CYCLES DEA_BLOCKED_FUNCTIONS DEA_CYCLES DEA_FUNCTIONS When there is no output at all the attributes files for the crypto counter set have not been exported. If above output is visible, the described problem does not show up. Upstream-ID: a87b0fd4f9003f8521226e226cf92b18147b3519 745f5d20e7936931f924410f32d8b0e599b5990e Problem-ID:196017 Preventive:yes Reported: Christian Rund SupportTicket: - Reference: - Date: 2022-01-20 Author:Thomas Richter Component: kernel To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1960182/+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 1959610] Re: ubuntu_kernel_selftests / ftrace:ftracetest do_softirq failure on Jammy realtime
** Description changed:
- do_softirq does not exist on preempt RT kernel.
+ [Impact]
- This is causing a failure in ftrace:ftracetest which reports: "echo: I/O
- error".
+ * ubuntu_kernel_selftests / ftrace:ftracetest fails on realtime kernel.
+
+ * ftrace:ftracetest which reports: "echo: I/O error". This is caused by
+ using "do_softirq" in test which does not exist on preempt RT kernel.
+
+ [Fix]
+
+ * Use other function.
+ * Upstream commit 6fec1ab67f8d ("selftests/ftrace: Do not trace do_softirq
because of PREEMPT_RT")
+
+ [Test Plan]
+
+ * Run the test on regular (base) and realtime kernel.
+
+ [Where problems could occur]
+
+ * Only ftracetest tests.
+
+ [Other info]
Failure is reported for step 32 in Jenkins job:
-
23:48:45 DEBUG| [stdout] # selftests: ftrace: ftracetest
23:48:45 DEBUG| [stdout] # === Ftrace unit tests ===
23:48:45 DEBUG| [stdout] # [1] Basic trace file check [PASS]
23:48:49 DEBUG| [stdout] # [2] Basic test for tracers [PASS]
23:48:49 DEBUG| [stdout] # [3] Basic trace clock test [PASS]
23:48:49 DEBUG| [stdout] # [4] Basic event tracing check [PASS]
23:48:50 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS]
23:48:50 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS]
23:48:50 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS]
23:49:38 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers
[PASS]
23:49:57 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes
[PASS]
23:49:57 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe
events [PASS]
23:49:57 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe
events [PASS]
23:49:57 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic
events [PASS]
23:49:57 DEBUG| [stdout] # [13] Generic dynamic event - selective clear
(compatibility) [PASS]
23:49:58 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event
[PASS]
23:49:58 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate
events are caught [PASS]
23:49:58 DEBUG| [stdout] # [16] event tracing - enable/disable with event
level files [PASS]
23:49:58 DEBUG| [stdout] # [17] event tracing - restricts events based on pid
notrace filtering [PASS]
23:49:59 DEBUG| [stdout] # [18] event tracing - restricts events based on pid
[PASS]
23:49:59 DEBUG| [stdout] # [19] event tracing - enable/disable with subsystem
level files [PASS]
23:50:00 DEBUG| [stdout] # [20] event tracing - enable/disable with top level
files [PASS]
23:50:01 DEBUG| [stdout] # [21] Test trace_printk from module [PASS]
23:50:04 DEBUG| [stdout] # [22] ftrace - function graph filters with stack
tracer [PASS]
23:50:05 DEBUG| [stdout] # [23] ftrace - function graph filters [PASS]
23:50:06 DEBUG| [stdout] # [24] ftrace - function pid notrace filters [PASS]
23:50:06 DEBUG| [stdout] # [25] ftrace - function pid filters [PASS]
23:50:08 DEBUG| [stdout] # [26] ftrace - stacktrace filter command[PASS]
23:50:08 DEBUG| [stdout] # [27] ftrace - function trace with cpumask [PASS]
23:50:12 DEBUG| [stdout] # [28] ftrace - test for function event triggers
[PASS]
23:50:13 DEBUG| [stdout] # [29] ftrace - function trace on module [PASS]
23:50:16 DEBUG| [stdout] # [30] ftrace - function profiling [PASS]
23:50:21 DEBUG| [stdout] # [31] ftrace - function profiler with function
tracing [PASS]
23:50:22 DEBUG| [stdout] # [32] ftrace - test reading of set_ftrace_filter
[FAIL]
23:50:24 DEBUG| [stdout] # [33] ftrace - test for function traceon/off
triggers [PASS]
23:50:24 DEBUG| [stdout] # [34] ftrace - test tracing error log support
[PASS]
23:50:28 DEBUG| [stdout] # [35] Test creation and deletion of trace instances
while setting an event [PASS]
23:50:29 DEBUG| [stdout] # [36] Test creation and deletion of trace instances
[PASS]
23:50:30 DEBUG| [stdout] # [37] Kprobe dynamic event - adding and removing
[PASS]
23:50:30 DEBUG| [stdout] # [38] Kprobe dynamic event - busy event check
[PASS]
23:50:30 DEBUG| [stdout] # [39] Kprobe dynamic event with arguments [PASS]
23:50:30 DEBUG| [stdout] # [40] Kprobe event with comm arguments [PASS]
23:50:30 DEBUG| [stdout] # [41] Kprobe event string type argument [PASS]
23:50:31 DEBUG| [stdout] # [42] Kprobe event symbol argument [PASS]
23:50:32 DEBUG| [stdout] # [43] Kprobe event argument syntax [PASS]
23:50:32 DEBUG| [stdout] # [44] Kprobes event arguments with types[PASS]
23:50:32 DEBUG| [stdout] # [45] Kprobe event user-memory access [PASS]
23:50:33 DEBUG| [stdout] # [46] Kprobe event auto/manual naming [PASS]
23:50:33 DEBUG| [stdout] # [47] Kprobe dynamic event with function tracer
[PASS]
23:50:34 DEBUG| [stdout] # [48] Create/delete multiprobe on kprobe event
[PASS]
23:50:34 DEBUG| [stdout] # [49] Kprobe event parser error log check
[Kernel-packages] [Bug 1959610] Re: ubuntu_kernel_selftests / ftrace:ftracetest do_softirq failure on Jammy realtime
** Also affects: linux (Ubuntu Jammy) Importance: Medium Assignee: Krzysztof Kozlowski (krzk) Status: In Progress -- 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/1959610 Title: ubuntu_kernel_selftests / ftrace:ftracetest do_softirq failure on Jammy realtime Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Bug description: do_softirq does not exist on preempt RT kernel. This is causing a failure in ftrace:ftracetest which reports: "echo: I/O error". Failure is reported for step 32 in Jenkins job: 23:48:45 DEBUG| [stdout] # selftests: ftrace: ftracetest 23:48:45 DEBUG| [stdout] # === Ftrace unit tests === 23:48:45 DEBUG| [stdout] # [1] Basic trace file check [PASS] 23:48:49 DEBUG| [stdout] # [2] Basic test for tracers [PASS] 23:48:49 DEBUG| [stdout] # [3] Basic trace clock test [PASS] 23:48:49 DEBUG| [stdout] # [4] Basic event tracing check [PASS] 23:48:50 DEBUG| [stdout] # [5] Change the ringbuffer size [PASS] 23:48:50 DEBUG| [stdout] # [6] Snapshot and tracing setting [PASS] 23:48:50 DEBUG| [stdout] # [7] trace_pipe and trace_marker[PASS] 23:49:38 DEBUG| [stdout] # [8] Test ftrace direct functions against tracers [PASS] 23:49:57 DEBUG| [stdout] # [9] Test ftrace direct functions against kprobes [PASS] 23:49:57 DEBUG| [stdout] # [10] Generic dynamic event - add/remove eprobe events [PASS] 23:49:57 DEBUG| [stdout] # [11] Generic dynamic event - add/remove kprobe events [PASS] 23:49:57 DEBUG| [stdout] # [12] Generic dynamic event - add/remove synthetic events [PASS] 23:49:57 DEBUG| [stdout] # [13] Generic dynamic event - selective clear (compatibility) [PASS] 23:49:58 DEBUG| [stdout] # [14] Generic dynamic event - generic clear event [PASS] 23:49:58 DEBUG| [stdout] # [15] Generic dynamic event - check if duplicate events are caught [PASS] 23:49:58 DEBUG| [stdout] # [16] event tracing - enable/disable with event level files [PASS] 23:49:58 DEBUG| [stdout] # [17] event tracing - restricts events based on pid notrace filtering [PASS] 23:49:59 DEBUG| [stdout] # [18] event tracing - restricts events based on pid [PASS] 23:49:59 DEBUG| [stdout] # [19] event tracing - enable/disable with subsystem level files [PASS] 23:50:00 DEBUG| [stdout] # [20] event tracing - enable/disable with top level files [PASS] 23:50:01 DEBUG| [stdout] # [21] Test trace_printk from module [PASS] 23:50:04 DEBUG| [stdout] # [22] ftrace - function graph filters with stack tracer [PASS] 23:50:05 DEBUG| [stdout] # [23] ftrace - function graph filters [PASS] 23:50:06 DEBUG| [stdout] # [24] ftrace - function pid notrace filters [PASS] 23:50:06 DEBUG| [stdout] # [25] ftrace - function pid filters [PASS] 23:50:08 DEBUG| [stdout] # [26] ftrace - stacktrace filter command[PASS] 23:50:08 DEBUG| [stdout] # [27] ftrace - function trace with cpumask [PASS] 23:50:12 DEBUG| [stdout] # [28] ftrace - test for function event triggers [PASS] 23:50:13 DEBUG| [stdout] # [29] ftrace - function trace on module [PASS] 23:50:16 DEBUG| [stdout] # [30] ftrace - function profiling [PASS] 23:50:21 DEBUG| [stdout] # [31] ftrace - function profiler with function tracing [PASS] 23:50:22 DEBUG| [stdout] # [32] ftrace - test reading of set_ftrace_filter [FAIL] 23:50:24 DEBUG| [stdout] # [33] ftrace - test for function traceon/off triggers [PASS] 23:50:24 DEBUG| [stdout] # [34] ftrace - test tracing error log support [PASS] 23:50:28 DEBUG| [stdout] # [35] Test creation and deletion of trace instances while setting an event [PASS] 23:50:29 DEBUG| [stdout] # [36] Test creation and deletion of trace instances [PASS] 23:50:30 DEBUG| [stdout] # [37] Kprobe dynamic event - adding and removing [PASS] 23:50:30 DEBUG| [stdout] # [38] Kprobe dynamic event - busy event check [PASS] 23:50:30 DEBUG| [stdout] # [39] Kprobe dynamic event with arguments [PASS] 23:50:30 DEBUG| [stdout] # [40] Kprobe event with comm arguments [PASS] 23:50:30 DEBUG| [stdout] # [41] Kprobe event string type argument [PASS] 23:50:31 DEBUG| [stdout] # [42] Kprobe event symbol argument [PASS] 23:50:32 DEBUG| [stdout] # [43] Kprobe event argument syntax [PASS] 23:50:32 DEBUG| [stdout] # [44] Kprobes event arguments with types[PASS] 23:50:32 DEBUG| [stdout] # [45] Kprobe event user-memory access [PASS] 23:50:33 DEBUG| [stdout] # [46] Kprobe event auto/manual naming [PASS] 23:50:33 DEBUG| [stdout] # [47] Kprobe dynamic event with function tracer [PASS] 23:50:34 DEBUG| [stdout] # [48] Create/delete multiprobe on kprobe event [PASS] 23:50:34 DEBUG| [stdout] # [49] Kprobe event parser error log check [PASS] 23:50:35
[Kernel-packages] [Bug 1941829] Update Released
The verification of the Stable Release Update for linux-hwe-5.13 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.13 in Ubuntu. https://bugs.launchpad.net/bugs/1941829 Title: ubuntu_kernel_selftests: memory-hotplug: avoid spamming logs with dump_page() Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.10 source package in Bionic: Invalid Status in linux-oem-5.13 source package in Bionic: Invalid Status in linux source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-oem-5.13 source package in Focal: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.13 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Committed Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.13 source package in Impish: Invalid Status in linux source package in Jammy: Fix Released Status in linux-oem-5.10 source package in Jammy: Invalid Status in linux-oem-5.13 source package in Jammy: Invalid Bug description: [Impact] The memory-hotplug test has been intermittently timing out (or trashing the test VM, see below) on Impish/Hirsute ppc64el and x86-64 for quite some time now. While the offline memory test obey ratio limit, the same test with error injection does not and tries to offline all the hotpluggable memory, spamming system logs with hundreds of thousands of dump_page() entries, slowing system down (to the point the test itself timesout and gets terminated) and excessive fs occupation: ... [ 9784.393354] page:c00c007d1b40 refcount:3 mapcount:0 mapping:c001fc03e950 index:0xe7b [ 9784.393355] def_blk_aops [ 9784.393356] flags: 0x382062(referenced|active|workingset|private) [ 9784.393358] raw: 00382062 c001b9343a68 c001b9343a68 c001fc03e950 [ 9784.393359] raw: 0e7b c6607b18 0003 c490d000 [ 9784.393359] page dumped because: migration failure [ 9784.393360] page->mem_cgroup:c490d000 [ 9784.393416] migrating pfn 1f46d failed ret:1 ... $ grep "page dumped because: migration failure" /var/log/kern.log | wc -l 2405558 $ ls -la /var/log/kern.log -rw-r- 1 syslog adm 2256109539 Jun 30 14:19 /var/log/kern.log [Fix] * 0c0f6299ba71fa selftests: memory-hotplug: avoid spamming logs with dump_page(), ratio limit hot-remove error test [Test Plan] Run the memory-hotplug test, this log spamming issue should not happen again. [Where problems could occur] If this fix is incorrect we might be unable to catch some other issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1941829/+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 1957753] Update Released
The verification of the Stable Release Update for linux-hwe-5.13 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1957753 Title: net/mlx5e: EPERM on vlan 0 programming Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: Fix Released Status in linux source package in Hirsute: Won't Fix Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 From patch description: When using libvirt to passthrough VF to VM it will always set the VF vlan to 0 even if user didn’t request it, this will cause libvirt to fail to boot in case the PF isn't eswitch owner. Example of such case is the DPU host PF which isn't eswitch manager, so any attempt to passthrough VF of it using libvirt will fail. [Fix] * 7846665d net/mlx5e: Unblock setting vid 0 for VF in case PF isn't eswitch manager This patch can be cherry-picked into Impish and newer kernels, but it requires some backport work on F/H due to they're missing commit b55b3538 that split the legacy code out. The ESW_ALLOWED marco was later converted into a helper routine in commit b16f2bb6. [Test] Test kernels can be found here: F: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/F/ H: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/H/ I: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/I/ J: https://people.canonical.com/~phlin/kernel/lp-1957753-mlx5e/J/ Kernels tested on a SUT with this device by Dmitrii Shcherbakov, test passed with positive feedback. [Where problems could occur] If this patch is erroneous, it might cause issue to this mlx5 driver with certain operations (setting vid 0). And other programs such as libvirt that depends on this return value might be affected as well. [Original Bug Description] There is an issue with hypervisor host side mlx5 driver operation on Bluefield devices in kernels <=5.16 that was recently fixed in master with a one-liner: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7846665d3504812acaebf920d1141851379a7f37 It would be good to have this fix in Focal+ kernels. This is not needed in https://bugs.launchpad.net/ubuntu/+source/linux- bluefield since it's used at the DPU side whereas the issue in question affects the hypervisor side. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1957753/+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 1956508] Update Released
The verification of the Stable Release Update for linux-hwe-5.13 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1956508 Title: Impish update: upstream stable patchset 2022-01-05 Status in linux package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed 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: upstream stable patchset 2022-01-05 Ported from the following upstream stable releases: v5.10.83, v5.15.6 from git://git.kernel.org/ ACPI: Get acpi_device's parent from the parent field USB: serial: option: add Telit LE910S1 0x9200 composition USB: serial: option: add Fibocom FM101-GL variants usb: dwc2: gadget: Fix ISOC flow for elapsed frames usb: dwc2: hcd_queue: Fix use of floating point literal usb: dwc3: gadget: Ignore NoStream after End Transfer usb: dwc3: gadget: Check for L1/L2/U3 for Start Transfer usb: dwc3: gadget: Fix null pointer exception net: nexthop: fix null pointer dereference when IPv6 is not enabled usb: chipidea: ci_hdrc_imx: fix potential error pointer dereference in probe usb: typec: fusb302: Fix masking of comparator and bc_lvl interrupts usb: hub: Fix usb enumeration issue due to address0 race usb: hub: Fix locking issues with address0_mutex binder: fix test regression due to sender_euid change ALSA: ctxfi: Fix out-of-range access ALSA: hda/realtek: Add quirk for ASRock NUC Box 1100 ALSA: hda/realtek: Fix LED on HP ProBook 435 G7 media: cec: copy sequence field for the reply Revert "parisc: Fix backtrace to always include init funtion names" HID: wacom: Use "Confidence" flag to prevent reporting invalid contacts staging/fbtft: Fix backlight staging: greybus: Add missing rwsem around snd_ctl_remove() calls staging: rtl8192e: Fix use after free in _rtl92e_pci_disconnect() fuse: release pipe buf after last use xen: don't continue xenstore initialization in case of errors xen: detect uninitialized xenbus in xenbus_init KVM: PPC: Book3S HV: Prevent POWER7/8 TLB flush flushing SLB tracing/uprobe: Fix uprobe_perf_open probes iteration tracing: Fix pid filtering when triggers are attached mmc: sdhci-esdhc-imx: disable CMDQ support mmc: sdhci: Fix ADMA for PAGE_SIZE >= 64KiB mdio: aspeed: Fix "Link is Down" issue powerpc/32: Fix hardlockup on vmap stack overflow PCI: aardvark: Deduplicate code in advk_pcie_rd_conf() PCI: aardvark: Implement re-issuing config requests on CRS response PCI: aardvark: Simplify initialization of rootcap on virtual bridge PCI: aardvark: Fix link training proc/vmcore: fix clearing user buffer by properly using clear_user() netfilter: ctnetlink: fix filtering with CTA_TUPLE_REPLY netfilter: ctnetlink: do not erase error code with EINVAL netfilter: ipvs: Fix reuse connection if RS weight is 0 netfilter: flowtable: fix IPv6 tunnel addr match ARM: dts: BCM5301X: Fix I2C controller interrupt ARM: dts: BCM5301X: Add interrupt properties to GPIO node ARM: dts: bcm2711: Fix PCIe interrupts ASoC: qdsp6: q6routing: Conditionally reset FrontEnd Mixer ASoC: qdsp6: q6asm: fix q6asm_dai_prepare error handling ASoC: topology: Add missing rwsem around snd_ctl_remove() calls ASoC: codecs: wcd934x: return error code correctly from hw_params net: ieee802154: handle iftypes as u32 firmware: arm_scmi: pm: Propagate return value to caller NFSv42: Don't fail clone() unless the OP_CLONE operation failed ARM: socfpga: Fix crash with CONFIG_FORTIRY_SOURCE drm/nouveau/acr: fix a couple NULL vs IS_ERR() checks scsi: mpt3sas: Fix kernel panic during drive powercycle test drm/vc4: fix error code in vc4_create_object() net: marvell: prestera: fix double free issue on err path iavf: Prevent changing static ITR values if adaptive moderation is on ALSA: intel-dsp-config: add quirk for JSL devices based on ES8336 codec mptcp: fix delack timer firmware: smccc: Fix check for ARCH_SOC_ID not implemented ipv6: fix typos in __ip6_finish_output() nfp:
[Kernel-packages] [Bug 1956380] Re: Focal update: v5.4.163 upstream stable release
This bug was fixed in the package linux - 5.4.0-100.113
---
linux (5.4.0-100.113) focal; urgency=medium
* focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
* CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
* CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
* Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
* Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix timing computation
- dt-bindings: net: Reintroduce PHY no lane swap binding
- tools build: Remove needless libpython-version feature check that breaks
test-all fast path
- net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
- net: altera: set a couple error code in probe()
- net: fec: only clear interrupt of handling queue in fec_enet_rx_queue()
- net, neigh: clear whole pneigh_entry at alloc time
- net/qla3xxx: fix an error code in ql_adapter_up()
- Revert "UBUNTU: SAUCE: selftests: fib_tests: assign address to dummy1 for
rp_filter tests"
- selftests/fib_tests: Rework fib_rp_filter_test()
- USB: gadget: detect too-big endpoint 0 requests
- USB: gadget: zero allocate endpoint 0 buffers
- usb: core: config: fix validation of wMaxPacketValue entries
- xhci:
[Kernel-packages] [Bug 1958155] Update Released
The verification of the Stable Release Update for linux-hwe-5.13 has
completed successfully and the package is now being released to
-updates. Subsequently, the Ubuntu Stable Release Updates Team is being
unsubscribed and will not receive messages about this bug report. In
the event that you encounter a regression using the package from
-updates please report a new bug using ubuntu-bug and tag the bug report
regression-update so we can easily find any regressions.
--
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/1958155
Title:
Pod traffic not taking advantage of interfaces with multiple tx queues
Status in linux package in Ubuntu:
Fix Released
Status in linux-hwe-5.11 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-hwe-5.11 source package in Focal:
Fix Committed
Status in linux source package in Hirsute:
Won't Fix
Status in linux-hwe-5.11 source package in Hirsute:
Invalid
Status in linux source package in Impish:
Fix Committed
Status in linux-hwe-5.11 source package in Impish:
Invalid
Bug description:
SRU Justification
[Impact]
https://patchwork.kernel.org/project/netdevbpf/patch/ef4cf3168907944502c81d8bf45e24eea1061e47.1641427152.git.dan...@iogearbox.net/
Performance is impacted when multiple TX queues are enabled.
[Fix]
commit 710ad98c363a66a0cd8526465426c5c5f8377ee0 ("veth: Do not record rx
queue hint in veth_xmit")
This patch is already scheduled for release in these stable kernel
versions:
linux-5.10.y.txt:5f76445a31b79be85b337cce5f35affb77cc18fc veth: Do not record
rx queue hint in veth_xmit
linux-5.15.y.txt:78a19e506bdcd1bfff73523ec99190794e0af39c veth: Do not record
rx queue hint in veth_xmit
linux-5.16.y.txt:bf8963ea39ecfd1bddc657a81f1d657b43c950e8 veth: Do not record
rx queue hint in veth_xmit
linux-5.4.y.txt:d08a0a88db88462bdf1b2df33ded23269b832afc veth: Do not record
rx queue hint in veth_xmit
[Test Plan]
Upstream tested
[Where things could go wrong]
Transmit performance could be impacted in other ways.
[Other Info]
SF: #00326544
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958155/+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 1956381] Re: Focal update: v5.4.164 upstream stable release
This bug was fixed in the package linux - 5.4.0-100.113
---
linux (5.4.0-100.113) focal; urgency=medium
* focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
* CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
* CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
* Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
* Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix timing computation
- dt-bindings: net: Reintroduce PHY no lane swap binding
- tools build: Remove needless libpython-version feature check that breaks
test-all fast path
- net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
- net: altera: set a couple error code in probe()
- net: fec: only clear interrupt of handling queue in fec_enet_rx_queue()
- net, neigh: clear whole pneigh_entry at alloc time
- net/qla3xxx: fix an error code in ql_adapter_up()
- Revert "UBUNTU: SAUCE: selftests: fib_tests: assign address to dummy1 for
rp_filter tests"
- selftests/fib_tests: Rework fib_rp_filter_test()
- USB: gadget: detect too-big endpoint 0 requests
- USB: gadget: zero allocate endpoint 0 buffers
- usb: core: config: fix validation of wMaxPacketValue entries
- xhci:
[Kernel-packages] [Bug 1958151] Update Released
The verification of the Stable Release Update for linux-hwe-5.13 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1958151 Title: [SRU][I/J/OEM-5.13/OEM-5.14] Add basic support of MT7922 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-5.13 package in Ubuntu: Invalid Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux-oem-5.13 source package in Focal: Won't Fix Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Impish: Fix Committed Status in linux source package in Jammy: In Progress Bug description: [Impact] No driver is loaded for MT7922, and fw is missing too. [Fix] Add basic support of MT7922, and add ID of AMD RZ616/RZ608. Enable 160Mhz channel. [Test] Verified on RZ616, it works fine, suspend OK. iperf test result looks fine. Bluetooth works fine. [Where problems could occur] It may break MT7921 wifi support which shares mt7921e driver. Almost the code is specific for MT7922, checking security fw is based on MT7922 fw. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958151/+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 1957753] Re: net/mlx5e: EPERM on vlan 0 programming
This bug was fixed in the package linux - 5.4.0-100.113
---
linux (5.4.0-100.113) focal; urgency=medium
* focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
* CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
* CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
* Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
* Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix timing computation
- dt-bindings: net: Reintroduce PHY no lane swap binding
- tools build: Remove needless libpython-version feature check that breaks
test-all fast path
- net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
- net: altera: set a couple error code in probe()
- net: fec: only clear interrupt of handling queue in fec_enet_rx_queue()
- net, neigh: clear whole pneigh_entry at alloc time
- net/qla3xxx: fix an error code in ql_adapter_up()
- Revert "UBUNTU: SAUCE: selftests: fib_tests: assign address to dummy1 for
rp_filter tests"
- selftests/fib_tests: Rework fib_rp_filter_test()
- USB: gadget: detect too-big endpoint 0 requests
- USB: gadget: zero allocate endpoint 0 buffers
- usb: core: config: fix validation of wMaxPacketValue entries
- xhci:
[Kernel-packages] [Bug 1957008] Re: Focal update: v5.4.166 upstream stable release
This bug was fixed in the package linux - 5.4.0-100.113
---
linux (5.4.0-100.113) focal; urgency=medium
* focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
* CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
* CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
* Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
* Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix timing computation
- dt-bindings: net: Reintroduce PHY no lane swap binding
- tools build: Remove needless libpython-version feature check that breaks
test-all fast path
- net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
- net: altera: set a couple error code in probe()
- net: fec: only clear interrupt of handling queue in fec_enet_rx_queue()
- net, neigh: clear whole pneigh_entry at alloc time
- net/qla3xxx: fix an error code in ql_adapter_up()
- Revert "UBUNTU: SAUCE: selftests: fib_tests: assign address to dummy1 for
rp_filter tests"
- selftests/fib_tests: Rework fib_rp_filter_test()
- USB: gadget: detect too-big endpoint 0 requests
- USB: gadget: zero allocate endpoint 0 buffers
- usb: core: config: fix validation of wMaxPacketValue entries
- xhci:
[Kernel-packages] [Bug 1957007] Re: Focal update: v5.4.165 upstream stable release
This bug was fixed in the package linux - 5.4.0-100.113
---
linux (5.4.0-100.113) focal; urgency=medium
* focal/linux: 5.4.0-100.113 -proposed tracker (LP: #1959900)
* CVE-2022-22942
- SAUCE: drm/vmwgfx: Fix stale file descriptors on failed usercopy
* CVE-2022-0330
- drm/i915: Flush TLBs before releasing backing store
* Focal update: v5.4.166 upstream stable release (LP: #1957008)
- netfilter: selftest: conntrack_vrf.sh: fix file permission
- Linux 5.4.166
- net/packet: rx_owner_map depends on pg_vec
- USB: gadget: bRequestType is a bitfield, not a enum
- HID: holtek: fix mouse probing
- udp: using datalen to cap ipv6 udp max gso segments
- selftests: Calculate udpgso segment count without header adjustment
* Focal update: v5.4.165 upstream stable release (LP: #1957007)
- serial: tegra: Change lower tolerance baud rate limit for tegra20 and
tegra30
- ntfs: fix ntfs_test_inode and ntfs_init_locked_inode function type
- HID: quirks: Add quirk for the Microsoft Surface 3 type-cover
- HID: google: add eel USB id
- HID: add hid_is_usb() function to make it simpler for USB detection
- HID: add USB_HID dependancy to hid-prodikeys
- HID: add USB_HID dependancy to hid-chicony
- HID: add USB_HID dependancy on some USB HID drivers
- HID: bigbenff: prevent null pointer dereference
- HID: wacom: fix problems when device is not a valid USB device
- HID: check for valid USB device for many HID drivers
- can: kvaser_usb: get CAN clock frequency from device
- can: kvaser_pciefd: kvaser_pciefd_rx_error_frame(): increase correct
stats->{rx,tx}_errors counter
- can: sja1000: fix use after free in ems_pcmcia_add_card()
- nfc: fix potential NULL pointer deref in nfc_genl_dump_ses_done
- selftests: netfilter: add a vrf+conntrack testcase
- vrf: don't run conntrack on vrf with !dflt qdisc
- bpf: Fix the off-by-two error in range markings
- ice: ignore dropped packets during init
- bonding: make tx_rebalance_counter an atomic
- nfp: Fix memory leak in nfp_cpp_area_cache_add()
- seg6: fix the iif in the IPv6 socket control block
- udp: using datalen to cap max gso segments
- iavf: restore MSI state on reset
- iavf: Fix reporting when setting descriptor count
- IB/hfi1: Correct guard on eager buffer deallocation
- mm: bdi: initialize bdi_min_ratio when bdi is unregistered
- ALSA: ctl: Fix copy of updated id with element read/write
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
- ALSA: pcm: oss: Fix negative period/buffer sizes
- ALSA: pcm: oss: Limit the period size to 16MB
- ALSA: pcm: oss: Handle missing errors in snd_pcm_oss_change_params*()
- btrfs: clear extent buffer uptodate when we fail to write it
- btrfs: replace the BUG_ON in btrfs_del_root_ref with proper error handling
- nfsd: Fix nsfd startup race (again)
- tracefs: Have new files inherit the ownership of their parent
- clk: qcom: regmap-mux: fix parent clock lookup
- drm/syncobj: Deal with signalled fences in drm_syncobj_find_fence.
- can: pch_can: pch_can_rx_normal: fix use after free
- can: m_can: Disable and ignore ELO interrupt
- x86/sme: Explicitly map new EFI memmap table as encrypted
- libata: add horkage for ASMedia 1092
- wait: add wake_up_pollfree()
- SAUCE: binder: export __wake_up_pollfree for binder module
- binder: use wake_up_pollfree()
- signalfd: use wake_up_pollfree()
- aio: keep poll requests on waitqueue until completed
- aio: fix use-after-free due to missing POLLFREE handling
- tracefs: Set all files to the same group ownership as the mount option
- block: fix ioprio_get(IOPRIO_WHO_PGRP) vs setuid(2)
- qede: validate non LSO skb length
- ASoC: qdsp6: q6routing: Fix return value from msm_routing_put_audio_mixer
- i40e: Fix failed opcode appearing if handling messages from VF
- i40e: Fix pre-set max number of queues for VF
- mtd: rawnand: fsmc: Take instruction delay into account
- mtd: rawnand: fsmc: Fix timing computation
- dt-bindings: net: Reintroduce PHY no lane swap binding
- tools build: Remove needless libpython-version feature check that breaks
test-all fast path
- net: cdc_ncm: Allow for dwNtbOutMaxSize to be unset or zero
- net: altera: set a couple error code in probe()
- net: fec: only clear interrupt of handling queue in fec_enet_rx_queue()
- net, neigh: clear whole pneigh_entry at alloc time
- net/qla3xxx: fix an error code in ql_adapter_up()
- Revert "UBUNTU: SAUCE: selftests: fib_tests: assign address to dummy1 for
rp_filter tests"
- selftests/fib_tests: Rework fib_rp_filter_test()
- USB: gadget: detect too-big endpoint 0 requests
- USB: gadget: zero allocate endpoint 0 buffers
- usb: core: config: fix validation of wMaxPacketValue entries
- xhci:
[Kernel-packages] [Bug 1960034] Update Released
The verification of the Stable Release Update for linux-hwe-5.13 has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- 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/1960034 Title: systemd/248.3-1ubuntu8.2 ADT test failure with linux/5.13.0-29.32 Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Invalid Status in linux source package in Impish: Fix Committed Status in systemd source package in Impish: Invalid Bug description: This is a scripted bug report about ADT failures while running systemd tests for linux/5.13.0-29.32 on impish. Whether this is caused by the dep8 tests of the tested source or the kernel has yet to be determined. Testing failed on: amd64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/amd64/s/systemd/20220204_114518_6b600@/log.gz arm64: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/arm64/s/systemd/20220201_135548_7f169@/log.gz ppc64el: https://autopkgtest.ubuntu.com/results/autopkgtest-impish/impish/ppc64el/s/systemd/20220201_110103_b02e4@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960034/+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 1780872] Re: wake on lan is not working
@Ignacio, from your post #27, check you have no .deb in your downloads directory before you fetch both latest linux-headers-X.YZ.x-xxrcN and linux-headers-X.YZ.x-xxrcN-generic then run sudo dpkg -i path- to-DLs/*.deb -- 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/1780872 Title: wake on lan is not working Status in linux package in Ubuntu: Expired Bug description: I'm dual-booting Ubuntu 18.04 and Windows 10. If I turn off my computer with Windows, I can turn it back on using wol. However, if I turn it off using Ubuntu the computer won't turn back on if I use wol. These are my network cards: ``` ignacio@ignacio-XPS-8930:~$ ifconfig docker0: flags=4163 mtu 1500 inet 172.17.0.1 netmask 255.255.0.0 broadcast 172.17.255.255 inet6 fe80::42:e4ff:fe0a:9fee prefixlen 64 scopeid 0x20 ether 02:42:e4:0a:9f:ee txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 165 bytes 24102 (24.1 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 enp4s0: flags=4163 mtu 1500 inet 192.168.86.31 netmask 255.255.255.0 broadcast 192.168.86.255 inet6 fe80::955b:12c8:20b9:7645 prefixlen 64 scopeid 0x20 ether d8:9e:f3:85:42:8a txqueuelen 1000 (Ethernet) RX packets 50484 bytes 52395285 (52.3 MB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 29166 bytes 4575560 (4.5 MB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 device interrupt 19 lo: flags=73 mtu 65536 inet 127.0.0.1 netmask 255.0.0.0 inet6 ::1 prefixlen 128 scopeid 0x10 loop txqueuelen 1000 (Local Loopback) RX packets 1124 bytes 95423 (95.4 KB) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 1124 bytes 95423 (95.4 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 veth66fe4e4: flags=4163 mtu 1500 inet6 fe80::2078:3ff:feb3:2aa1 prefixlen 64 scopeid 0x20 ether 22:78:03:b3:2a:a1 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 224 bytes 30503 (30.5 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 vethb50cc6f: flags=4163 mtu 1500 inet6 fe80::5c0b:47ff:fef1:cfc9 prefixlen 64 scopeid 0x20 ether 5e:0b:47:f1:cf:c9 txqueuelen 0 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 125 bytes 18006 (18.0 KB) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 wlp3s0: flags=4099 mtu 1500 ether 5c:ea:1d:4c:61:a7 txqueuelen 1000 (Ethernet) RX packets 0 bytes 0 (0.0 B) RX errors 0 dropped 0 overruns 0 frame 0 TX packets 0 bytes 0 (0.0 B) TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0 ``` This is what ethtool tells me about my ethernet card: ``` ignacio@ignacio-XPS-8930:~$ sudo ethtool enp4s0 Settings for enp4s0: Supported ports: [ TP ] Supported link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Supported pause frame use: Symmetric Receive-only Supports auto-negotiation: Yes Supported FEC modes: Not reported Advertised link modes: 10baseT/Half 10baseT/Full 100baseT/Half 100baseT/Full 1000baseT/Full Advertised pause frame use: Symmetric Advertised auto-negotiation: Yes Advertised FEC modes: Not reported Speed: 1000Mb/s Duplex: Full Port: Twisted Pair PHYAD: 0 Transceiver: internal Auto-negotiation: on MDI-X: Unknown Current message level: 0x60e4 (24804) link ifup rx_err tx_err hw wol Link detected: yes ``` And this is what happens when I try to activate wake on lan: ``` ignacio@ignacio-XPS-8930:~$ sudo ethtool -s enp4s0 wol g Cannot get current wake-on-lan settings: Operation not supported not setting wol ``` Finally, this is the infor about my distro: ``` ignacio@ignacio-XPS-8930:~$ lsb_release -rd Description: Ubuntu 18.04 LTS Release: 18.04 ``` Thanks for the help! ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ethtool 1:4.15-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-23.25-generic 4.15.18 Uname: Linux 4.15.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME
[Kernel-packages] [Bug 1961171] 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/1961171 Title: System freezes when starting Eclipse Status in linux package in Ubuntu: Confirmed Bug description: Starting Eclipse will 100% likely cause a complete system freeze within a few minutes. Same problem occurs using Wayland and X.org. See the attached kernel stack trace. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: linux-image-5.13.0-28-generic 5.13.0-28.31 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jens 2427 F pulseaudio /dev/snd/controlC0: jens 2427 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Feb 17 08:38:59 2022 InstallationDate: Installed on 2019-04-12 (1042 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.2) Lsusb: Bus 002 Device 002: ID 05ac:8406 Apple, Inc. Internal Memory Card Reader Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 05ac:0273 Apple, Inc. Internal Keyboard/Trackpad (ISO) Bus 001 Device 002: ID 05ac:8290 Apple, Inc. Bluetooth Host Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro12,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=sv_SE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.13.0-28-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.13.0-28-generic N/A linux-backports-modules-5.13.0-28-generic N/A linux-firmware 1.201.4 SourcePackage: linux UpgradeStatus: Upgraded to impish on 2021-10-26 (114 days ago) dmi.bios.date: 09/17/2018 dmi.bios.release: 0.1 dmi.bios.vendor: Apple Inc. dmi.bios.version: 180.0.0.0.0 dmi.board.name: Mac-E43C1C25D4880AD6 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro12,1 dmi.chassis.type: 9 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-E43C1C25D4880AD6 dmi.modalias: dmi:bvnAppleInc.:bvr180.0.0.0.0:bd09/17/2018:br0.1:svnAppleInc.:pnMacBookPro12,1:pvr1.0:rvnAppleInc.:rnMac-E43C1C25D4880AD6:rvrMacBookPro12,1:cvnAppleInc.:ct9:cvrMac-E43C1C25D4880AD6:sku: dmi.product.family: MacBook Pro dmi.product.name: MacBookPro12,1 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/+bug/1961171/+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
