[Kernel-packages] [Bug 1995154] 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/1995154 Title: Touchpad and WiFi stopped working and are not detected Status in linux package in Ubuntu: Confirmed Bug description: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 1643 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 22:37:31 2022 InstallationDate: Installed on 2022-06-27 (123 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. enx92af39b68b72 no wireless extensions. MachineType: ASUSTeK COMPUTER INC. Q503UA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=9ebc8858-a399-48f5-a6a2-af95e1c466cd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q503UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q503UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ503UA.206:bd01/28/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnQ503UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ503UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: Q dmi.product.name: Q503UA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995154/+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 1995154] [NEW] Touchpad and WiFi stopped working and are not detected
Public bug reported: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #0 (rev 21) 00:15.1 Signal processing controller: Intel Corporation Sunrise Point-LP Serial IO I2C Controller #1 (rev 21) 00:16.0 Communication controller: Intel Corporation Sunrise Point-LP CSME HECI #1 (rev 21) 00:17.0 SATA controller: Intel Corporation Sunrise Point-LP SATA Controller [AHCI mode] (rev 21) 00:1c.0 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #3 (rev f1) 00:1c.4 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #5 (rev f1) 00:1c.5 PCI bridge: Intel Corporation Sunrise Point-LP PCI Express Root Port #6 (rev f1) 00:1f.0 ISA bridge: Intel Corporation Sunrise Point-LP LPC Controller (rev 21) 00:1f.2 Memory controller: Intel Corporation Sunrise Point-LP PMC (rev 21) 00:1f.3 Audio device: Intel Corporation Sunrise Point-LP HD Audio (rev 21) 00:1f.4 SMBus: Intel Corporation Sunrise Point-LP SMBus (rev 21) 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 10) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-43-generic 5.15.0-43.46 ProcVersionSignature: Ubuntu 5.15.0-43.46-generic 5.15.39 Uname: Linux 5.15.0-43-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 1643 F pulseaudio CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 22:37:31 2022 InstallationDate: Installed on 2022-06-27 (123 days ago) InstallationMedia: Ubuntu 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. enx92af39b68b72 no wireless extensions. MachineType: ASUSTeK COMPUTER INC. Q503UA ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-43-generic root=UUID=9ebc8858-a399-48f5-a6a2-af95e1c466cd ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.3 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/28/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: Q503UA.206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: Q503UA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrQ503UA.206:bd01/28/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnQ503UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnQ503UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:skuASUS-NotebookSKU: dmi.product.family: Q dmi.product.name: Q503UA dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy wayland-session -- 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/1995154 Title: Touchpad and WiFi stopped working and are not detected Status in linux package in Ubuntu: New Bug description: 00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers (rev 08) 00:02.0 VGA compatible controller: Intel Corporation Skylake GT2 [HD Graphics 520] (rev 07) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 08) 00:13.0 Non-VGA unclassified device: Intel Corporation Sunrise Point-LP Integrated Sensor Hub (rev 21) 00:14.0 USB controller: Intel Corporation Sunrise Point-LP USB 3.0 xHCI Controller (rev 21) 00:14.2 Signal processing controller: Intel Corporation Sunrise Point-LP Thermal subsystem (rev 21) 00:15.0
[Kernel-packages] [Bug 1995147] 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/1995147 Title: r8169 : eth0 link down after 5 minutes 'kernel: [ ] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Confirmed Bug description: Hello, I use reverse tethering trough an ethernet link: my Ubuntu 22.04 LTS laptop is providing internet access to a LG CL600 thin client. This ethernet link works fine from power up until 5 minutes after this power up, then the ethernet link freezes. I don't have this problem when my laptop is providing the same internet access with Debian 11 live (kernel 5.10.0): in this case reverse tethering trough ethernet works fluently trough the time, no ethernet freeze at all. So my hardware isn't faulty, but there seems to be a regression in the kernel r8169 module, between the 5.10 and 5.15 kernels. Can you solve this regression? The r8169 module is a part the linux-modules-extra-5.15.0-52-generic package. Here is the involved sample from /var/log/syslog: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053253] [ cut here ] Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053278] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053308] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x277/0x280 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053326] Modules linked in: nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_ct nft_masq nft_counter nft_chain_nat xt_MASQUERADE nft_compat bridge stp llc rfcomm ccm nf_tables nfnetlink nf_nat_h323 binfmt_misc nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_conexant snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_common snd_intel_dspcfg iwlmvm rtsx_usb_ms snd_intel_sdw_acpi mac80211 uvcvideo snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core x86_pkg_temp_thermal intel_powerclamp videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_hwdep libarc4 snd_seq_midi coretemp mc memstick snd_pcm snd_seq_m idi_event i915 kvm_intel snd_rawmidi snd_seq kvm Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053625] iwlwifi ttm drm_kms_helper snd_seq_device snd_timer btusb crct10dif_pclmul btrtl btbcm ghash_clmulni_intel cec aesni_intel snd rc_core btintel crypto_simd i2c_algo_bit bluetooth mei_me cfg80211 cryptd mei soundcore at24 fb_sys_fops ecdh_generic ecc rapl intel_cstate syscopyarea sysfillrect sysimgblt joydev input_leds ideapad_laptop sparse_keymap serio_raw platform_profile mac_hid wmi acpi_pad sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp mtd ramoops pstore_blk pstore_zone parport drm reed_solomon efi_pstore ip_tables x_tables autofs4 hid_generic usbhid rtsx_usb_sdmmc hid rtsx_usb i2c_i801 r8169 ahci xhci_pci psmouse i2c_smbus crc32_pclmul lpc_ich libahci realtek xhci_pci_renesas video Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053905] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.15.0-48-generic #54-Ubuntu Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053914] Hardware name: LENOVO 80FF/Lenovo G70-80, BIOS ABCN80WW 05/18/2015 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053918] RIP: 0010:dev_watchdog+0x277/0x280 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053931] Code: eb 97 48 8b 5d d0 c6 05 03 39 69 01 01 48 89 df e8 ee 67 f9 ff 44 89 e1 48 89 de 48 c7 c7 50 49 cd 8d 48 89 c2 e8 a7 bb 19 00 <0f> 0b eb 80 e9 51 25 23 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053938] RSP: 0018:c03440154e70 EFLAGS: 00010282 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053946] RAX: RBX: a05f80b34000 RCX: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053952] RDX: a062cf32c240 RSI: a062cf320580 RDI: 0300 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053957] RBP: c03440154ea8 R08: 0003 R09: fffd7858 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053963] R10: 000a R11: 0001 R12: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053968] R13: a05f80ca0280 R14: 0001 R15: a05f80b344c0 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053974] FS: () GS:a062cf30() knlGS: Oct 22 17:59:57
[Kernel-packages] [Bug 1995147] Re: r8169 : eth0 link down after 5 minutes 'kernel: [ ] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995147 Title: r8169 : eth0 link down after 5 minutes 'kernel: [ ] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: New Bug description: Hello, I use reverse tethering trough an ethernet link: my Ubuntu 22.04 LTS laptop is providing internet access to a LG CL600 thin client. This ethernet link works fine from power up until 5 minutes after this power up, then the ethernet link freezes. I don't have this problem when my laptop is providing the same internet access with Debian 11 live (kernel 5.10.0): in this case reverse tethering trough ethernet works fluently trough the time, no ethernet freeze at all. So my hardware isn't faulty, but there seems to be a regression in the kernel r8169 module, between the 5.10 and 5.15 kernels. Can you solve this regression? The r8169 module is a part the linux-modules-extra-5.15.0-52-generic package. Here is the involved sample from /var/log/syslog: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053253] [ cut here ] Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053278] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053308] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x277/0x280 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053326] Modules linked in: nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_ct nft_masq nft_counter nft_chain_nat xt_MASQUERADE nft_compat bridge stp llc rfcomm ccm nf_tables nfnetlink nf_nat_h323 binfmt_misc nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_conexant snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_common snd_intel_dspcfg iwlmvm rtsx_usb_ms snd_intel_sdw_acpi mac80211 uvcvideo snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core x86_pkg_temp_thermal intel_powerclamp videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_hwdep libarc4 snd_seq_midi coretemp mc memstick snd_pcm snd_seq_m idi_event i915 kvm_intel snd_rawmidi snd_seq kvm Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053625] iwlwifi ttm drm_kms_helper snd_seq_device snd_timer btusb crct10dif_pclmul btrtl btbcm ghash_clmulni_intel cec aesni_intel snd rc_core btintel crypto_simd i2c_algo_bit bluetooth mei_me cfg80211 cryptd mei soundcore at24 fb_sys_fops ecdh_generic ecc rapl intel_cstate syscopyarea sysfillrect sysimgblt joydev input_leds ideapad_laptop sparse_keymap serio_raw platform_profile mac_hid wmi acpi_pad sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp mtd ramoops pstore_blk pstore_zone parport drm reed_solomon efi_pstore ip_tables x_tables autofs4 hid_generic usbhid rtsx_usb_sdmmc hid rtsx_usb i2c_i801 r8169 ahci xhci_pci psmouse i2c_smbus crc32_pclmul lpc_ich libahci realtek xhci_pci_renesas video Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053905] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.15.0-48-generic #54-Ubuntu Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053914] Hardware name: LENOVO 80FF/Lenovo G70-80, BIOS ABCN80WW 05/18/2015 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053918] RIP: 0010:dev_watchdog+0x277/0x280 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053931] Code: eb 97 48 8b 5d d0 c6 05 03 39 69 01 01 48 89 df e8 ee 67 f9 ff 44 89 e1 48 89 de 48 c7 c7 50 49 cd 8d 48 89 c2 e8 a7 bb 19 00 <0f> 0b eb 80 e9 51 25 23 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053938] RSP: 0018:c03440154e70 EFLAGS: 00010282 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053946] RAX: RBX: a05f80b34000 RCX: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053952] RDX: a062cf32c240 RSI: a062cf320580 RDI: 0300 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053957] RBP: c03440154ea8 R08: 0003 R09: fffd7858 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053963] R10: 000a R11: 0001 R12: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053968] R13: a05f80ca0280 R14: 0001 R15: a05f80b344c0 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053974] FS: () GS:a062cf30() knlGS: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053980] CS: 0010 DS: ES:
[Kernel-packages] [Bug 1995147] [NEW] r8169 : eth0 link down after 5 minutes 'kernel: [ ] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out
You have been subscribed to a public bug: Hello, I use reverse tethering trough an ethernet link: my Ubuntu 22.04 LTS laptop is providing internet access to a LG CL600 thin client. This ethernet link works fine from power up until 5 minutes after this power up, then the ethernet link freezes. I don't have this problem when my laptop is providing the same internet access with Debian 11 live (kernel 5.10.0): in this case reverse tethering trough ethernet works fluently trough the time, no ethernet freeze at all. So my hardware isn't faulty, but there seems to be a regression in the kernel r8169 module, between the 5.10 and 5.15 kernels. Can you solve this regression? The r8169 module is a part the linux-modules-extra-5.15.0-52-generic package. Here is the involved sample from /var/log/syslog: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053253] [ cut here ] Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053278] NETDEV WATCHDOG: enp2s0 (r8169): transmit queue 0 timed out Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053308] WARNING: CPU: 2 PID: 0 at net/sched/sch_generic.c:477 dev_watchdog+0x277/0x280 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053326] Modules linked in: nft_reject_ipv4 nf_reject_ipv4 nft_reject nft_ct nft_masq nft_counter nft_chain_nat xt_MASQUERADE nft_compat bridge stp llc rfcomm ccm nf_tables nfnetlink nf_nat_h323 binfmt_misc nf_conntrack_h323 nf_nat_pptp nf_conntrack_pptp nf_nat_tftp nf_conntrack_tftp nf_nat_sip nf_conntrack_sip nf_nat_irc nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 mei_hdcp intel_rapl_msr snd_hda_codec_conexant snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel intel_rapl_common snd_intel_dspcfg iwlmvm rtsx_usb_ms snd_intel_sdw_acpi mac80211 uvcvideo snd_usb_audio snd_hda_codec snd_usbmidi_lib snd_hda_core x86_pkg_temp_thermal intel_powerclamp videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev snd_hwdep libarc4 snd_seq_midi coretemp mc memstick snd_pcm snd_seq_mid i_event i915 kvm_intel snd_rawmidi snd_seq kvm Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053625] iwlwifi ttm drm_kms_helper snd_seq_device snd_timer btusb crct10dif_pclmul btrtl btbcm ghash_clmulni_intel cec aesni_intel snd rc_core btintel crypto_simd i2c_algo_bit bluetooth mei_me cfg80211 cryptd mei soundcore at24 fb_sys_fops ecdh_generic ecc rapl intel_cstate syscopyarea sysfillrect sysimgblt joydev input_leds ideapad_laptop sparse_keymap serio_raw platform_profile mac_hid wmi acpi_pad sch_fq_codel ipmi_devintf ipmi_msghandler msr parport_pc ppdev lp mtd ramoops pstore_blk pstore_zone parport drm reed_solomon efi_pstore ip_tables x_tables autofs4 hid_generic usbhid rtsx_usb_sdmmc hid rtsx_usb i2c_i801 r8169 ahci xhci_pci psmouse i2c_smbus crc32_pclmul lpc_ich libahci realtek xhci_pci_renesas video Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053905] CPU: 2 PID: 0 Comm: swapper/2 Not tainted 5.15.0-48-generic #54-Ubuntu Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053914] Hardware name: LENOVO 80FF/Lenovo G70-80, BIOS ABCN80WW 05/18/2015 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053918] RIP: 0010:dev_watchdog+0x277/0x280 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053931] Code: eb 97 48 8b 5d d0 c6 05 03 39 69 01 01 48 89 df e8 ee 67 f9 ff 44 89 e1 48 89 de 48 c7 c7 50 49 cd 8d 48 89 c2 e8 a7 bb 19 00 <0f> 0b eb 80 e9 51 25 23 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053938] RSP: 0018:c03440154e70 EFLAGS: 00010282 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053946] RAX: RBX: a05f80b34000 RCX: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053952] RDX: a062cf32c240 RSI: a062cf320580 RDI: 0300 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053957] RBP: c03440154ea8 R08: 0003 R09: fffd7858 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053963] R10: 000a R11: 0001 R12: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053968] R13: a05f80ca0280 R14: 0001 R15: a05f80b344c0 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053974] FS: () GS:a062cf30() knlGS: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053980] CS: 0010 DS: ES: CR0: 80050033 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053986] CR2: 1b2801ab4000 CR3: 65010006 CR4: 001706e0 Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053991] Call Trace: Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.053996] Oct 22 17:59:57 damien-Lenovo-G70-80 kernel: [ 537.054002] ? pfifo_fast_enqueue+0x160/0x160 Oct 22 17:59:57
[Kernel-packages] [Bug 1989578] Re: Add HDMI codec ID for Intel Raptor Lake
This bug is awaiting verification that the linux/5.15.0-53.59 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1989578 Title: Add HDMI codec ID for Intel Raptor Lake Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] The HDAudio is not functional on some RaptorLake machines. The audio codec is failed to be probed so no PCM stream available for audio functions. [Fix] Backport the patch from upstream which adds the support for the HDMI codec ID on RaptorLake. [Test] Power on the machine and check if the audio function's working with alsa utilities. [Where problems could occur] The change only applies to the new RaptorLake Intel HDA controller and HDMI codec. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1989578/+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 1990240] Re: To support Intel Maple Ridge Thunderbolt [8086:1134]
This bug is awaiting verification that the linux/5.15.0-53.59 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990240 Title: To support Intel Maple Ridge Thunderbolt [8086:1134] Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] The TBT ID[8086:1134] the new project uses is not listed in the driver. [Fix] Intel submits this as we requested which is still in linux-next https://lore.kernel.org/linux-usb/20220908104320.3409720-1-gil.f...@intel.com/ [Where problems could occur] Adding only one ID, should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990240/+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 1990800] Re: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4
This bug is awaiting verification that the linux/5.4.0-132.148 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-focal' to 'verification-done-focal'. If the problem still exists, change the tag 'verification-needed-focal' to 'verification-failed-focal'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1990800 Title: fib_nexthop_nongw.sh from ubuntu_kernel_selftests failed on B-5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Bug description: Issue found on B-5.4.0-128-generic #144~18.04.1-Ubuntu This is a new test case from bug 1988809 Test failed with: Running 'make run_tests -C net TEST_PROGS=fib_nexthop_nongw.sh TEST_GEN_PROGS='' TEST_CUSTOM_PROGS=''' make: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net' make --no-builtin-rules ARCH=x86 -C ../../../.. headers_install make[1]: Entering directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' INSTALL ./usr/include make[1]: Leaving directory '/home/ubuntu/autotest/client/tmp/ubuntu_kernel_selftests/src/linux' TAP version 13 1..1 # selftests: net: fib_nexthop_nongw.sh # Object "nexthop" is unknown, try "ip help". # Error: either "to" is duplicate, or "nhid" is a garbage. # TEST: nexthop: get route with nexthop without gw[FAIL] # TEST: nexthop: ping through nexthop without gw [FAIL] not ok 1 selftests: net: fib_nexthop_nongw.sh # exit=1 -- [Impact] When running kselftests on Bionic with a 5.4 kernel, it would fail because of no nexthop capability. [Fix] We query the ip command help to know whether it is implemented or not, and we skip or execute the test accordingly [Test Plan] Running the test script directly in Bionic will throw a Skip, while running it in Focal will throw the test result. [Where problems could ocurr] The regression potential for this is low. [Other Info] None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1990800/+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 1990242] Re: Intel graphic driver is not probing[8086:468b]
This bug is awaiting verification that the linux/5.15.0-53.59 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1990242 Title: Intel graphic driver is not probing[8086:468b] Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Committed Status in linux-oem-5.17 source package in Jammy: Fix Released Status in linux-oem-6.0 source package in Jammy: Fix Released Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [Impact] Got blank screen after entered desktop [Fix] Below commit in linux-next fixes the issue. 6215a7c8f552 drm/i915: Add new ADL-S pci id [Test] Verified on the target machine. [Where problems could occur] It only adds an ID to the list, should be pretty safe. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1990242/+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 1992484] Re: Kernel regresses openjdk on riscv64
This bug is awaiting verification that the linux/5.15.0-53.59 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-jammy' to 'verification-done-jammy'. If the problem still exists, change the tag 'verification-needed-jammy' to 'verification-failed-jammy'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! -- 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/1992484 Title: Kernel regresses openjdk on riscv64 Status in linux package in Ubuntu: Fix Released Status in linux source package in Jammy: Fix Committed Bug description: Over at https://lore.kernel.org/linux- riscv/Yz80ewHKTPI5Rvuz@spud/T/#ebde47064434d4ca4807b4abb8eb39898c48a8de2 it is reported that 2139619bcad7ac44cc8f6f749089120594056613 regresses userspace (openjdk) on riscv64. This commit has already been released in v6.0 kernel upstream, but has also been included in the stable patch series all the way back to v4.19.y There is a proposed fix for this at https://lore.kernel.org/linux- riscv/20220915193702.2201018-1-abres...@rivosinc.com/ which has not yet been merged upstream or in stable series. Please review and merge above proposed fix, or please revert 2139619bcad7ac44cc8f6f749089120594056613 to stop the regression spreading to all the distributions. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992484/+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 1955383] Re: Support Intel IPU6 MIPI camera on Alder Lake platforms
hi, I too am having problems getting the webcam working on my "Dell Inc. XPS 9320/0P9FNW, BIOS 1.4.0 05/13/2022" running jammy. I only have http://fr.archive.ubuntu.com/ubuntu/ and http://security.ubuntu.com/ubuntu as sources in /etc/apt. I have oem- somerville-tentacool-meta 22.04~ubuntu1 and libcanberra- gtk3-module:amd64 0.30-10ubuntu1 installed. I have the 5.15.0-52-generic kernel. I have looked at https://wiki.ubuntu.com/Dell but the instructions seem to be out of date. Thanks for any help, Stuart zbarcam causes dmesg to output "intel-ipu6-isys intel-ipu6-isys0: dma_alloc_coherent of size 536903680 failed" stuart@xps9320:/etc/apt$ zbarcam Using mplane plugin for capture libv4l2: error turning on stream: Link has been severed ERROR: zbar processor in v4l2_start(): system error: starting video stream (VIDIOC_STREAMON): Link has been severed (67) stuart@xps9320:/etc/apt$ cheese ../src/intel/isl/isl.c:2220: FINISHME: ../src/intel/isl/isl.c:isl_surf_supports_ccs: CCS for 3D textures is disabled, but a workaround is available. (cheese:7404): cheese-WARNING **: 00:53:26.993: Device '/dev/video0' does not support 2:0:0:0 colourimetry: ../sys/v4l2/gstv4l2object.c(4105): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Device wants 2:0:0:0 colorimetry stuart@xps9320:/etc/apt$ chromium https://webcamtests.com/ Gtk-Message: 00:57:53.924: Failed to load module "canberra-gtk-module" Gtk-Message: 00:57:53.925: Failed to load module "canberra-gtk-module" WARNING: Kernel has no file descriptor comparison support: Operation not permitted [7612:7701:1029/005757.683021:ERROR:udev_watcher.cc(98)] Failed to begin udev enumeration. stuart@xps9320:/etc/apt$ firefox https://webcamtests.com/ Gtk-Message: 01:06:54.292: Failed to load module "canberra-gtk-module" Gtk-Message: 01:06:54.293: Failed to load module "canberra-gtk-module" stuart@xps9320:/etc/apt$ sudo dmesg | grep ipu6 [ 11.006142] intel-ipu6 intel-ipu: enabling device ( -> 0002) [ 11.006332] intel-ipu6 intel-ipu: Device 0x465d (rev: 0x2) [ 11.006351] intel-ipu6 intel-ipu: physical base address 0x603c00 [ 11.006352] intel-ipu6 intel-ipu: mapped as: 0x4d40cc25 [ 11.006446] intel-ipu6 intel-ipu: Unable to set secure mode [ 11.006446] intel-ipu6 intel-ipu: IPU in non-secure mode [ 11.006450] intel-ipu6 intel-ipu: Skip ipc reset for non-secure mode [ 11.006451] intel-ipu6 intel-ipu: IPC reset done [ 11.006451] intel-ipu6 intel-ipu: cpd file name: intel/ipu6ep_fw.bin [ 11.008293] intel-ipu6 intel-ipu: FW version: 20211011 [ 11.131890] intel-ipu6 intel-ipu: IPU driver version 1.0 [ 20.435874] intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 [ 20.435988] intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 [ 20.575899] intel-ipu6-isys intel-ipu6-isys0: bind ov01a10 17-0036 nlanes is 1 port is 2 [ 20.576105] intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. [ 936.060203] intel-ipu6-isys intel-ipu6-isys0: dma_alloc_coherent of size 536903680 failed [ 1347.230485] intel-ipu6-isys intel-ipu6-isys0: dma_alloc_coherent of size 536903680 failed [ 1821.440819] intel-ipu6-isys intel-ipu6-isys0: dma_alloc_coherent of size 536903680 failed [ 1953.807143] intel-ipu6-isys intel-ipu6-isys0: dma_alloc_coherent of size 536903680 failed -- 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/1955383 Title: Support Intel IPU6 MIPI camera on Alder Lake platforms Status in HWE Next: Fix Released Status in OEM Priority Project: Fix Released Status in linux package in Ubuntu: Invalid Status in linux-firmware package in Ubuntu: Fix Released Status in linux-oem-5.14 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.14 source package in Focal: Fix Released Status in linux source package in Jammy: Fix Released Status in linux-firmware source package in Jammy: Fix Released Status in linux-oem-5.14 source package in Jammy: Invalid Bug description: == kernel driver SRU == [SRU Justification] [Impact] To support Intel IPU6 MIPI camera on Alder Lake platforms. [Fix] Initial support for Intel IPU6 MIPI camera on Tiger Lake platforms has been addressed by bug 1921345 and 1939539. They are backported from https://github.com/intel/ipu6-drivers. Further works to enable IPU6 camera on Alder Lake platforms depend on a few more fixes from same ipu6-drivers repository, as well as an extra https://github.com/intel/ivsc-driver for Intel Vision Sensing Controller(IVSC). [Test Case] This depends on an integral of enablement components inclusive of the kernel drivers that are being proposed, firmware, updates for the userspace camera
[Kernel-packages] [Bug 1993818] Re: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10
Sorry for the late comment, I've tried the patches from the linked kernel packages, no crashes for me so far either. -- 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/1993818 Title: Linux kernel crash on Ubuntu 22.10 on Thinkpad X1 Carbon Gen 10 Status in linux package in Ubuntu: Fix Committed Bug description: Been experiencing random hangs since upgraded to 22.10. Looking at /var/log/kern.log after crash I'm seeing general protection fault from /var/log/kern.log. Oct 21 20:41:38 tyrant kernel: [ 281.051619] general protection fault, probably for non-canonical address 0x258d1b207028: [#1] PREEMPT SMP NOPTI Oct 21 20:41:38 tyrant kernel: [ 281.051629] CPU: 13 PID: 2445 Comm: gnome-shell Tainted: GW 5.19.0-21-generic #21-Ubuntu Oct 21 20:41:38 tyrant kernel: [ 281.051633] Hardware name: LENOVO 21CBCTO1WW/21CBCTO1WW, BIOS N3AET67W (1.32 ) 09/27/2022 Oct 21 20:41:38 tyrant kernel: [ 281.051636] RIP: 0010:rm_hole+0x1a7/0x340 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.051676] Code: 8b 78 08 eb 1c 48 89 50 28 48 8b 10 48 89 d0 48 83 e0 fc 48 83 fa 03 76 32 48 8b 48 10 48 8b 78 08 48 8b 50 20 48 85 c9 74 0b <48> 8b 49 28 48 39 ca 48 0f 42 d1 48 85 ff 74 0b 48 8b 4f 28 48 39 Oct 21 20:41:38 tyrant kernel: [ 281.051679] RSP: 0018:ac26834ab9c0 EFLAGS: 00010206 Oct 21 20:41:38 tyrant kernel: [ 281.051683] RAX: 90258161d1b0 RBX: 902580fd7800 RCX: 258d1b207000 Oct 21 20:41:38 tyrant kernel: [ 281.051686] RDX: 0003ccf0 RSI: 9025a4351528 RDI: 0090 Oct 21 20:41:38 tyrant kernel: [ 281.051688] RBP: ac26834ab9e0 R08: R09: Oct 21 20:41:38 tyrant kernel: [ 281.051690] R10: 902580fd7870 R11: 902581747740 R12: 902580fd7858 Oct 21 20:41:38 tyrant kernel: [ 281.051692] R13: 9025a4351528 R14: 9025a43515f8 R15: 0011 Oct 21 20:41:38 tyrant kernel: [ 281.051694] FS: 7f553c5d45c0() GS:902cbf74() knlGS: Oct 21 20:41:38 tyrant kernel: [ 281.051697] CS: 0010 DS: ES: CR0: 80050033 Oct 21 20:41:38 tyrant kernel: [ 281.051700] CR2: 7f35e73685c0 CR3: 00013119a001 CR4: 00770ee0 Oct 21 20:41:38 tyrant kernel: [ 281.051702] PKRU: 5554 Oct 21 20:41:38 tyrant kernel: [ 281.051704] Call Trace: Oct 21 20:41:38 tyrant kernel: [ 281.051707] Oct 21 20:41:38 tyrant kernel: [ 281.051711] drm_mm_insert_node_in_range+0x26a/0x500 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.051745] _i915_gem_object_stolen_init+0x28c/0x2e0 [i915] Oct 21 20:41:38 tyrant kernel: [ 281.051871] __i915_gem_object_create_region+0xb2/0x170 [i915] Oct 21 20:41:38 tyrant kernel: [ 281.051977] i915_gem_object_create_region+0x1e/0x30 [i915] Oct 21 20:41:38 tyrant kernel: [ 281.052080] i915_gem_object_create_stolen+0x19/0x30 [i915] Oct 21 20:41:38 tyrant kernel: [ 281.052184] intel_dpt_create+0x20b/0x2c0 [i915] Oct 21 20:41:38 tyrant kernel: [ 281.052299] intel_framebuffer_init+0x749/0x960 [i915] Oct 21 20:41:38 tyrant kernel: [ 281.052408] ? kmem_cache_alloc_trace+0x189/0x310 Oct 21 20:41:38 tyrant kernel: [ 281.052414] intel_framebuffer_create+0x40/0x90 [i915] Oct 21 20:41:38 tyrant kernel: [ 281.052521] intel_user_framebuffer_create+0xf8/0x1d0 [i915] Oct 21 20:41:38 tyrant kernel: [ 281.052626] drm_internal_framebuffer_create+0xb3/0x150 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.052667] drm_mode_addfb2+0x44/0xd0 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.052705] ? drm_mode_addfb_ioctl+0x20/0x20 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.052743] drm_mode_addfb2_ioctl+0xe/0x20 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.052780] drm_ioctl_kernel+0xd3/0x180 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.052811] drm_ioctl+0x29d/0x4d0 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.052840] ? drm_mode_addfb_ioctl+0x20/0x20 [drm] Oct 21 20:41:38 tyrant kernel: [ 281.052879] __x64_sys_ioctl+0x9d/0xe0 Oct 21 20:41:38 tyrant kernel: [ 281.052884] do_syscall_64+0x58/0x90 Oct 21 20:41:38 tyrant kernel: [ 281.052888] ? __do_sys_kcmp+0x208/0x550 Oct 21 20:41:38 tyrant kernel: [ 281.052894] ? exit_to_user_mode_prepare+0x30/0xb0 Oct 21 20:41:38 tyrant kernel: [ 281.052899] ? syscall_exit_to_user_mode+0x26/0x50 Oct 21 20:41:38 tyrant kernel: [ 281.052902] ? __x64_sys_kcmp+0x1f/0x30 Oct 21 20:41:38 tyrant kernel: [ 281.052905] ? do_syscall_64+0x67/0x90 Oct 21 20:41:38 tyrant kernel: [ 281.052908] ? sysvec_apic_timer_interrupt+0x4b/0xd0 Oct 21 20:41:38 tyrant kernel: [ 281.052911] entry_SYSCALL_64_after_hwframe+0x63/0xcd Oct 21 20:41:38 tyrant kernel: [ 281.052915] RIP: 0033:0x7f5540712d8f Oct 21 20:41:38 tyrant kernel: [ 281.052919] Code: 00 48 89 44 24 18 31 c0 48 8d 44 24 60 c7 04 24 10
[Kernel-packages] [Bug 1995150] 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/1995150 Title: Crash after monitor wake Status in linux package in Ubuntu: Confirmed Bug description: I ran into a bug shortly after upgrading from 22.04 to 22.10. I have 2 monitors connected to a Radeon R9 FURY / NANO Series via DP cables. When returning to the PC after a screen lock (when both monitors had entered a power saving mode), the second monitor did not wake up. I see the following warning and `kernel NULL pointer dereference` in the systemd journal: Oct 28 12:24:11 desktop kernel: [ cut here ] Oct 28 12:24:11 desktop kernel: WARNING: CPU: 12 PID: 91 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dce110/dce110_clk_mgr.c:140 dce110_fill_display_configs+0x83/0x2e0 [amdgpu] Oct 28 12:24:11 desktop kernel: Modules linked in: xt_multiport tls nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter nvme_fabrics rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat n> Oct 28 12:24:11 desktop kernel: gigabyte_wmi rapl drm_kms_helper fb_sys_fops snd_timer syscopyarea iwlwifi(O) ccp sysfillrect snd sysimgblt k10temp soundcore cfg80211(O) iwlwifi_compat(O) mac_hid msr parport_pc ppdev lp parport drm ramoops pstore_blk reed_solomon pstore_zone efi_> Oct 28 12:24:11 desktop kernel: CPU: 12 PID: 91 Comm: kworker/12:0H Tainted: G O 5.19.0-23.24-justin-stock-generic #stock Oct 28 12:24:11 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI/X570 AORUS PRO WIFI, BIOS F21 07/31/2020 Oct 28 12:24:11 desktop kernel: Workqueue: events_highpri dm_irq_work_func [amdgpu] Oct 28 12:24:11 desktop kernel: RIP: 0010:dce110_fill_display_configs+0x83/0x2e0 [amdgpu] Oct 28 12:24:11 desktop kernel: Code: 89 dd 31 db 4c 63 f3 49 83 fe 05 0f 87 80 01 00 00 4d 39 65 00 0f 84 29 01 00 00 83 c3 01 49 81 c5 10 08 00 00 83 fb 06 75 da <0f> 0b 31 db 45 0f b6 ac 24 c8 03 00 00 41 80 fd 01 0f 87 fd 55 19 Oct 28 12:24:11 desktop kernel: RSP: 0018:b291404dfa90 EFLAGS: 00010246 Oct 28 12:24:11 desktop kernel: RAX: 0110 RBX: 0006 RCX: Oct 28 12:24:11 desktop kernel: RDX: RSI: 908acdcd2980 RDI: 908acdcc Oct 28 12:24:11 desktop kernel: RBP: b291404dfae0 R08: 908acdcc R09: Oct 28 12:24:11 desktop kernel: R10: 908acdcd2980 R11: 908acdcc01f0 R12: 908aa3478000 Oct 28 12:24:11 desktop kernel: R13: 908acdcc3250 R14: 0005 R15: Oct 28 12:24:11 desktop kernel: FS: () GS:90911ed0() knlGS: Oct 28 12:24:11 desktop kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 12:24:11 desktop kernel: CR2: 7f36aced3098 CR3: 0001a3e6c000 CR4: 00350ee0 Oct 28 12:24:11 desktop kernel: Call Trace: Oct 28 12:24:11 desktop kernel: Oct 28 12:24:11 desktop kernel: ? dce_get_required_clocks_state+0x25/0x140 [amdgpu] Oct 28 12:24:11 desktop kernel: dce_update_clocks+0xdb/0x170 [amdgpu] Oct 28 12:24:11 desktop kernel: dce100_prepare_bandwidth+0x3e/0x50 [amdgpu] Oct 28 12:24:11 desktop kernel: commit_planes_for_stream+0xd54/0x1060 [amdgpu] Oct 28 12:24:11 desktop kernel: ? dc_resource_state_copy_construct+0x167/0x2b0 [amdgpu] Oct 28 12:24:11 desktop kernel: dc_commit_updates_for_stream+0x1e8/0x5b0 [amdgpu] Oct 28 12:24:11 desktop kernel: set_all_streams_dpms_off_for_link+0x159/0x190 [amdgpu] Oct 28 12:24:11 desktop kernel: ? detect_link_and_local_sink+0x5f2/0xc40 [amdgpu] Oct 28 12:24:11 desktop kernel: verify_link_capability.isra.0+0x260/0x300 [amdgpu] Oct 28 12:24:11 desktop kernel: dc_link_detect+0x35/0x1d0 [amdgpu] Oct 28 12:24:11 desktop kernel: handle_hpd_irq_helper+0x106/0x1d0 [amdgpu] Oct 28 12:24:11 desktop kernel: handle_hpd_irq+0xe/0x20 [amdgpu] Oct 28 12:24:11 desktop kernel: dm_irq_work_func+0x19/0x30 [amdgpu] Oct 28 12:24:11 desktop kernel: process_one_work+0x225/0x400 Oct 28 12:24:11 desktop kernel: worker_thread+0x50/0x3e0 Oct 28 12:24:11 desktop kernel: ? rescuer_thread+0x3c0/0x3c0 Oct 28 12:24:11 desktop kernel: kthread+0xe9/0x110 Oct 28 12:24:11 desktop kernel: ? kthread_complete_and_exit+0x20/0x20 Oct 28 12:24:11 desktop kernel: ret_from_fork+0x22/0x30 Oct 28 12:24:11 desktop kernel: Oct 28 12:24:11 desktop kernel: ---[ end trace ]--- Oct 28 12:24:11 desktop kernel: BUG: kernel NULL pointer dereference, address: 0008 Oct 28 12:24:11 desktop kernel: #PF: supervisor read access in kernel mode Oct 28 12:24:11 desktop kernel: #PF:
[Kernel-packages] [Bug 1995150] [NEW] Crash after monitor wake
Public bug reported: I ran into a bug shortly after upgrading from 22.04 to 22.10. I have 2 monitors connected to a Radeon R9 FURY / NANO Series via DP cables. When returning to the PC after a screen lock (when both monitors had entered a power saving mode), the second monitor did not wake up. I see the following warning and `kernel NULL pointer dereference` in the systemd journal: Oct 28 12:24:11 desktop kernel: [ cut here ] Oct 28 12:24:11 desktop kernel: WARNING: CPU: 12 PID: 91 at drivers/gpu/drm/amd/amdgpu/../display/dc/clk_mgr/dce110/dce110_clk_mgr.c:140 dce110_fill_display_configs+0x83/0x2e0 [amdgpu] Oct 28 12:24:11 desktop kernel: Modules linked in: xt_multiport tls nf_conntrack_netlink xfrm_user xfrm_algo xt_addrtype br_netfilter nvme_fabrics rfcomm snd_seq_dummy snd_hrtimer xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat n> Oct 28 12:24:11 desktop kernel: gigabyte_wmi rapl drm_kms_helper fb_sys_fops snd_timer syscopyarea iwlwifi(O) ccp sysfillrect snd sysimgblt k10temp soundcore cfg80211(O) iwlwifi_compat(O) mac_hid msr parport_pc ppdev lp parport drm ramoops pstore_blk reed_solomon pstore_zone efi_> Oct 28 12:24:11 desktop kernel: CPU: 12 PID: 91 Comm: kworker/12:0H Tainted: G O 5.19.0-23.24-justin-stock-generic #stock Oct 28 12:24:11 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI/X570 AORUS PRO WIFI, BIOS F21 07/31/2020 Oct 28 12:24:11 desktop kernel: Workqueue: events_highpri dm_irq_work_func [amdgpu] Oct 28 12:24:11 desktop kernel: RIP: 0010:dce110_fill_display_configs+0x83/0x2e0 [amdgpu] Oct 28 12:24:11 desktop kernel: Code: 89 dd 31 db 4c 63 f3 49 83 fe 05 0f 87 80 01 00 00 4d 39 65 00 0f 84 29 01 00 00 83 c3 01 49 81 c5 10 08 00 00 83 fb 06 75 da <0f> 0b 31 db 45 0f b6 ac 24 c8 03 00 00 41 80 fd 01 0f 87 fd 55 19 Oct 28 12:24:11 desktop kernel: RSP: 0018:b291404dfa90 EFLAGS: 00010246 Oct 28 12:24:11 desktop kernel: RAX: 0110 RBX: 0006 RCX: Oct 28 12:24:11 desktop kernel: RDX: RSI: 908acdcd2980 RDI: 908acdcc Oct 28 12:24:11 desktop kernel: RBP: b291404dfae0 R08: 908acdcc R09: Oct 28 12:24:11 desktop kernel: R10: 908acdcd2980 R11: 908acdcc01f0 R12: 908aa3478000 Oct 28 12:24:11 desktop kernel: R13: 908acdcc3250 R14: 0005 R15: Oct 28 12:24:11 desktop kernel: FS: () GS:90911ed0() knlGS: Oct 28 12:24:11 desktop kernel: CS: 0010 DS: ES: CR0: 80050033 Oct 28 12:24:11 desktop kernel: CR2: 7f36aced3098 CR3: 0001a3e6c000 CR4: 00350ee0 Oct 28 12:24:11 desktop kernel: Call Trace: Oct 28 12:24:11 desktop kernel: Oct 28 12:24:11 desktop kernel: ? dce_get_required_clocks_state+0x25/0x140 [amdgpu] Oct 28 12:24:11 desktop kernel: dce_update_clocks+0xdb/0x170 [amdgpu] Oct 28 12:24:11 desktop kernel: dce100_prepare_bandwidth+0x3e/0x50 [amdgpu] Oct 28 12:24:11 desktop kernel: commit_planes_for_stream+0xd54/0x1060 [amdgpu] Oct 28 12:24:11 desktop kernel: ? dc_resource_state_copy_construct+0x167/0x2b0 [amdgpu] Oct 28 12:24:11 desktop kernel: dc_commit_updates_for_stream+0x1e8/0x5b0 [amdgpu] Oct 28 12:24:11 desktop kernel: set_all_streams_dpms_off_for_link+0x159/0x190 [amdgpu] Oct 28 12:24:11 desktop kernel: ? detect_link_and_local_sink+0x5f2/0xc40 [amdgpu] Oct 28 12:24:11 desktop kernel: verify_link_capability.isra.0+0x260/0x300 [amdgpu] Oct 28 12:24:11 desktop kernel: dc_link_detect+0x35/0x1d0 [amdgpu] Oct 28 12:24:11 desktop kernel: handle_hpd_irq_helper+0x106/0x1d0 [amdgpu] Oct 28 12:24:11 desktop kernel: handle_hpd_irq+0xe/0x20 [amdgpu] Oct 28 12:24:11 desktop kernel: dm_irq_work_func+0x19/0x30 [amdgpu] Oct 28 12:24:11 desktop kernel: process_one_work+0x225/0x400 Oct 28 12:24:11 desktop kernel: worker_thread+0x50/0x3e0 Oct 28 12:24:11 desktop kernel: ? rescuer_thread+0x3c0/0x3c0 Oct 28 12:24:11 desktop kernel: kthread+0xe9/0x110 Oct 28 12:24:11 desktop kernel: ? kthread_complete_and_exit+0x20/0x20 Oct 28 12:24:11 desktop kernel: ret_from_fork+0x22/0x30 Oct 28 12:24:11 desktop kernel: Oct 28 12:24:11 desktop kernel: ---[ end trace ]--- Oct 28 12:24:11 desktop kernel: BUG: kernel NULL pointer dereference, address: 0008 Oct 28 12:24:11 desktop kernel: #PF: supervisor read access in kernel mode Oct 28 12:24:11 desktop kernel: #PF: error_code(0x) - not-present page Oct 28 12:24:11 desktop kernel: PGD 1a73f3067 P4D 1a73f3067 PUD 1a73f2067 PMD 0 Oct 28 12:24:11 desktop kernel: Oops: [#1] PREEMPT SMP NOPTI Oct 28 12:24:11 desktop kernel: CPU: 12 PID: 91 Comm: kworker/12:0H Tainted: G W O 5.19.0-23.24-justin-stock-generic #stock Oct 28 12:24:11 desktop kernel: Hardware name: Gigabyte Technology Co., Ltd. X570 AORUS PRO WIFI/X570 AORUS PRO WIFI, BIOS F21
[Kernel-packages] [Bug 1995148] [NEW] mlxbf_gige: need to add BlueField-3 support
Public bug reported:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo does not yet
support the BlueField-3 SoC. The "mlxbf_gige" driver which
supports BlueField-2 SoC currently will be extended to include
the BlueField-3 support.
[Fix]
The BlueField-3 support will be provided in the form of a set
of 4 patches, to be sent in as a pull request.
[Test Case]
BlueField-2: Boot platform and bring up "oob_net0" interface properly
Test that network traffic works properly
BlueField-3: Tested in simulator platforms and early silicon
[Regression Potential]
Since this is initial support there is chance of regression
on BlueField-2 platforms, but it's been tested there.
[Other]
n/a
** Affects: linux-bluefield (Ubuntu)
Importance: Undecided
Status: New
--
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/1995148
Title:
mlxbf_gige: need to add BlueField-3 support
Status in linux-bluefield package in Ubuntu:
New
Bug description:
SRU Justification:
[Impact]
The GIGE driver ("mlxbf_gige") in the Jammy repo does not yet
support the BlueField-3 SoC. The "mlxbf_gige" driver which
supports BlueField-2 SoC currently will be extended to include
the BlueField-3 support.
[Fix]
The BlueField-3 support will be provided in the form of a set
of 4 patches, to be sent in as a pull request.
[Test Case]
BlueField-2: Boot platform and bring up "oob_net0" interface properly
Test that network traffic works properly
BlueField-3: Tested in simulator platforms and early silicon
[Regression Potential]
Since this is initial support there is chance of regression
on BlueField-2 platforms, but it's been tested there.
[Other]
n/a
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995148/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
https://forums.developer.nvidia.com/t/significant-delay-in-loading- xserver-with-proprietary-driver-on-kernel-version-above-5-15-0-48/ posted here as recommended on nvidia-forum. -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1995126] Re: upgrade from 20.04 to 22.04.1 fails
May have been solved by: sudo pip uninstall distro-info sudo apt install --reinstall python3-distro-info ref: https://askubuntu.com/questions/1137645/python-error-when- upgrading-from-18-10-to-19-04 -- 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/1995126 Title: upgrade from 20.04 to 22.04.1 fails Status in linux package in Ubuntu: Confirmed Bug description: $ sudo do-release-upgrade -d Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,265 kB] Fetched 1,266 kB in 0s (0 B/s) authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg' extracting 'jammy.tar.gz' [screen blanks here] Reading cache Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Hit http://archive.canonical.com/ubuntu focal InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit http://security.ubuntu.com/ubuntu focal-security InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Hit http://dl.google.com/linux/chrome/deb stable InRelease Hit http://ppa.launchpad.net/mutlaqja/ppa/ubuntu focal InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done === Command detached from window (Fri Oct 28 11:16:34 2022) === === Command terminated with exit status 1 (Fri Oct 28 11:16:44 2022) === [screen is terminating] $ uname -a Linux tempo 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/*elease* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.5 LTS" NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-131-generic 5.4.0-131.147 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: edik 1914 F pulseaudio /dev/snd/controlC0: edik 1914 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 28 11:21:00 2022 InstallationDate: Installed on 2019-05-30 (1246 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. eno0 no wireless extensions. ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-131-generic root=UUID=a501cd51-bc07-496b-a8dd-bee5e1db7c02 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-131-generic N/A linux-backports-modules-5.4.0-131-generic N/A linux-firmware 1.187.33 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-10-28 (0 days ago) dmi.bios.date: 05/21/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.5531.2010.0521.1135 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55SB dmi.board.vendor: Intel Corporation dmi.board.version: AAE47220-304 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.5531.2010.0521.1135:bd05/21/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55SB:rvrAAE47220-304:cvn:ct2:cvr: To manage notifications about this bug go to:
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
I created topic on Nvidia forum as well: https://www.nvidia.com/en-us/geforce/forums/game-ready-drivers/13/503446/nvidia-drivers-not-work-on-ubuntu-22042210-mass-pr/ -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1995108] Re: RTL8111/8168/8411 throughput/power/CPU bug
** Description changed: Hi, I'm running into an issue where the RTL8111/8168/8411 (rev 15) gigabit ethernet adapter is stuck at 700mbps transfer speeds, but will be able to hit 940-950mbps speeds as soon as the CPU is stressed to 100%. It is the same as this bug posted several years ago: https://superuser.com/questions/1428360/poor-network-throughput-but- double-under-high-cpu-load/1749982 Exact instructions to reproduce this bug: on mini PC run: iperf3 -s -B on client run: iperf3 -R -c miniPC.lan λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34124 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 1.00-2.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 2.00-3.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 3.00-4.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 4.00-5.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 5.00-6.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 6.00-7.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 7.00-8.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 8.00-9.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 9.00-10.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 10.00-11.00 sec 82.7 MBytes 693 Mbits/sec [ 5] 11.00-12.00 sec 83.4 MBytes 699 Mbits/sec [ 5] 12.00-13.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 13.00-14.00 sec 82.8 MBytes 695 Mbits/sec [ 5] 14.00-15.00 sec 82.7 MBytes 694 Mbits/sec [ 5] 15.00-16.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 16.00-17.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 17.00-18.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 18.00-19.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 19.00-19.09 sec 7.42 MBytes 694 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-19.09 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-19.09 sec 1.55 GBytes 696 Mbits/sec receiver iperf3: interrupt - the client has terminated under stress test I ran s-tui on the mini PC, enabled the stress test option, and saw all cores boosted to 2.90 GHz (max turbo on an Intel N5095). The ethernet speeds immediately jumped to gigabit wire speeds: λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34144 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 113 MBytes 946 Mbits/sec [ 5] 1.00-2.00 sec 113 MBytes 949 Mbits/sec [ 5] 2.00-3.00 sec 113 MBytes 949 Mbits/sec [ 5] 3.00-4.00 sec 113 MBytes 949 Mbits/sec [ 5] 4.00-5.00 sec 113 MBytes 949 Mbits/sec [ 5] 5.00-6.00 sec 113 MBytes 949 Mbits/sec [ 5] 6.00-6.27 sec 31.0 MBytes 949 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-6.27 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-6.27 sec 709 MBytes 949 Mbits/sec receiver iperf3: interrupt - the client has terminated I have tried both the r8169 and r8168 drivers on both 22.04 (kernel 5.15 and 5.19) and also on 22.10 (only kernel 5.19 tested). This issue - remains on all combinations tested. + remains on all combinations tested. When I tested using r8168 same issue + showed up but speeds were constantly ~800mbps instead of 700mbps, but + same thing - stress testing the cpu to 100% made it go to 940-950mbps + instead. I verified the driver being used by running the following: root@snuminipc:~# ethtool -i enp2s0 driver: r8169 version: 5.19.0-23-generic firmware-version: rtl8168h-2_0.0.2 02/26/15 expansion-rom-version: bus-info: :02:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c',
[Kernel-packages] [Bug 1995126] 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/1995126 Title: upgrade from 20.04 to 22.04.1 fails Status in linux package in Ubuntu: Confirmed Bug description: $ sudo do-release-upgrade -d Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,265 kB] Fetched 1,266 kB in 0s (0 B/s) authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg' extracting 'jammy.tar.gz' [screen blanks here] Reading cache Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Hit http://archive.canonical.com/ubuntu focal InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit http://security.ubuntu.com/ubuntu focal-security InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Hit http://dl.google.com/linux/chrome/deb stable InRelease Hit http://ppa.launchpad.net/mutlaqja/ppa/ubuntu focal InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done === Command detached from window (Fri Oct 28 11:16:34 2022) === === Command terminated with exit status 1 (Fri Oct 28 11:16:44 2022) === [screen is terminating] $ uname -a Linux tempo 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/*elease* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.5 LTS" NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-131-generic 5.4.0-131.147 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: edik 1914 F pulseaudio /dev/snd/controlC0: edik 1914 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 28 11:21:00 2022 InstallationDate: Installed on 2019-05-30 (1246 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. eno0 no wireless extensions. ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-131-generic root=UUID=a501cd51-bc07-496b-a8dd-bee5e1db7c02 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-131-generic N/A linux-backports-modules-5.4.0-131-generic N/A linux-firmware 1.187.33 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-10-28 (0 days ago) dmi.bios.date: 05/21/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.5531.2010.0521.1135 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55SB dmi.board.vendor: Intel Corporation dmi.board.version: AAE47220-304 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.5531.2010.0521.1135:bd05/21/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55SB:rvrAAE47220-304:cvn:ct2:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995126/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1995108] Re: RTL8111/8168/8411 throughput/power/CPU bug
I wanted to try v6.1-rc2 kernel but no builds for amd64 were available, so I tried 2022-10-28 Mainline instead. root@snuminipc:~# uname -r 6.1.0-060100rc2daily20221028-generic root@snuminipc:~# ethtool -i enp2s0 driver: r8169 version: 6.1.0-060100rc2daily20221028-ge firmware-version: rtl8168h-2_0.0.2 02/26/15 expansion-rom-version: bus-info: :02:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no Same issue: λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 63859 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 82.7 MBytes 693 Mbits/sec [ 5] 1.00-2.00 sec 77.7 MBytes 652 Mbits/sec [ 5] 2.00-3.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 3.00-4.00 sec 82.9 MBytes 696 Mbits/sec [ 5] 4.00-5.00 sec 82.9 MBytes 696 Mbits/sec [ 5] 5.00-6.00 sec 83.7 MBytes 702 Mbits/sec [ 5] 6.00-7.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 7.00-8.00 sec 83.0 MBytes 697 Mbits/sec [ 5] 8.00-8.99 sec 81.5 MBytes 694 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-8.99 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-8.99 sec 741 MBytes 692 Mbits/sec receiver iperf3: interrupt - the client has terminated s-tui stress test: λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 63872 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 113 MBytes 945 Mbits/sec [ 5] 1.00-2.00 sec 113 MBytes 949 Mbits/sec [ 5] 2.00-3.00 sec 113 MBytes 949 Mbits/sec [ 5] 3.00-4.00 sec 113 MBytes 949 Mbits/sec [ 5] 4.00-5.00 sec 113 MBytes 949 Mbits/sec [ 5] 5.00-6.00 sec 113 MBytes 949 Mbits/sec [ 5] 6.00-7.00 sec 113 MBytes 949 Mbits/sec [ 5] 7.00-8.00 sec 113 MBytes 949 Mbits/sec [ 5] 8.00-8.82 sec 92.9 MBytes 949 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-8.82 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-8.82 sec 998 MBytes 949 Mbits/sec receiver iperf3: interrupt - the client has terminated -- 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/1995108 Title: RTL8111/8168/8411 throughput/power/CPU bug Status in linux package in Ubuntu: Confirmed Bug description: Hi, I'm running into an issue where the RTL8111/8168/8411 (rev 15) gigabit ethernet adapter is stuck at 700mbps transfer speeds, but will be able to hit 940-950mbps speeds as soon as the CPU is stressed to 100%. It is the same as this bug posted several years ago: https://superuser.com/questions/1428360/poor-network-throughput-but- double-under-high-cpu-load/1749982 Exact instructions to reproduce this bug: on mini PC run: iperf3 -s -B on client run: iperf3 -R -c miniPC.lan λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34124 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 1.00-2.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 2.00-3.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 3.00-4.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 4.00-5.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 5.00-6.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 6.00-7.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 7.00-8.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 8.00-9.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 9.00-10.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 10.00-11.00 sec 82.7 MBytes 693 Mbits/sec [ 5] 11.00-12.00 sec 83.4 MBytes 699 Mbits/sec [ 5] 12.00-13.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 13.00-14.00 sec 82.8 MBytes 695 Mbits/sec [ 5] 14.00-15.00 sec 82.7 MBytes 694 Mbits/sec [ 5] 15.00-16.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 16.00-17.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 17.00-18.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 18.00-19.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 19.00-19.09 sec 7.42 MBytes 694 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-19.09 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-19.09 sec 1.55 GBytes 696 Mbits/sec
[Kernel-packages] [Bug 1995126] Re: upgrade from 20.04 to 22.04.1 fails
I made the terminal window several screens' tall, to see the following
(before the screen gets blanked by the install process - why would it do
that?):
Reading cache
Checking package manager
Reading package lists... Done
Building dependency tree
Reading state information... Done
Hit http://security.ubuntu.com/ubuntu focal-security InRelease
Hit http://ca.archive.ubuntu.com/ubuntu focal InRelease
Hit http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease
Hit http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease
Hit http://archive.canonical.com/ubuntu focal InRelease
Hit http://dl.google.com/linux/chrome/deb stable InRelease
Hit http://ppa.launchpad.net/mutlaqja/ppa/ubuntu focal InRelease
Fetched 0 B in 0s (0 B/s)
Reading package lists... Done
Building dependency tree
Reading state information... Done
Traceback (most recent call last):
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
205, in _get_from_and_to_version
di.version('%s' % self.controller.fromDist).split()[0]
AttributeError: 'UbuntuDistroInfo' object has no attribute 'version'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-hq1pt_14/jammy", line 8, in
sys.exit(main())
File "/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeMain.py",
line 241, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 2042, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 1873, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 906, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
118, in jammyPostInitialUpdate
self._get_from_and_to_version()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
211, in _get_from_and_to_version
(r.version for r in di.get_all("object")
AttributeError: 'UbuntuDistroInfo' object has no attribute 'get_all'
Error in sys.excepthook:
Traceback (most recent call last):
File "/usr/lib/python3/dist-packages/problem_report.py", line 477, in
add_to_existing
self.write(f)
File "/usr/lib/python3/dist-packages/problem_report.py", line 430, in write
block = f.read(1048576)
File "/usr/lib/python3.8/codecs.py", line 322, in decode
(result, consumed) = self._buffer_decode(data, self.errors, final)
UnicodeDecodeError: 'utf-8' codec can't decode byte 0x8b in position 1: invalid
start byte
Original exception was:
Traceback (most recent call last):
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
205, in _get_from_and_to_version
di.version('%s' % self.controller.fromDist).split()[0]
AttributeError: 'UbuntuDistroInfo' object has no attribute 'version'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/tmp/ubuntu-release-upgrader-hq1pt_14/jammy", line 8, in
sys.exit(main())
File "/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeMain.py",
line 241, in main
if app.run():
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 2042, in run
return self.fullUpgrade()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 1873, in fullUpgrade
if not self.doPostInitialUpdate():
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeController.py",
line 906, in doPostInitialUpdate
self.quirks.run("PostInitialUpdate")
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
99, in run
func()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
118, in jammyPostInitialUpdate
self._get_from_and_to_version()
File
"/tmp/ubuntu-release-upgrader-hq1pt_14/DistUpgrade/DistUpgradeQuirks.py", line
211, in _get_from_and_to_version
(r.version for r in di.get_all("object")
AttributeError: 'UbuntuDistroInfo' object has no attribute 'get_all'
=== Command detached from window (Fri Oct 28 11:44:51 2022) ===
=== Command terminated with exit status 1 (Fri Oct 28 11:45:01 2022) ===
--
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/1995126
Title:
upgrade from 20.04 to 22.04.1 fails
Status in linux package in Ubuntu:
New
Bug description:
$ sudo do-release-upgrade -d
Checking for a new Ubuntu release
Get:1 Upgrade tool signature [819 B]
[Kernel-packages] [Bug 1995126] [NEW] upgrade from 20.04 to 22.04.1 fails
Public bug reported: $ sudo do-release-upgrade -d Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,265 kB] Fetched 1,266 kB in 0s (0 B/s) authenticate 'jammy.tar.gz' against 'jammy.tar.gz.gpg' extracting 'jammy.tar.gz' [screen blanks here] Reading cache Checking package manager Reading package lists... Done Building dependency tree Reading state information... Done Hit http://archive.canonical.com/ubuntu focal InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal InRelease Hit http://security.ubuntu.com/ubuntu focal-security InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-updates InRelease Hit http://ca.archive.ubuntu.com/ubuntu focal-backports InRelease Hit http://dl.google.com/linux/chrome/deb stable InRelease Hit http://ppa.launchpad.net/mutlaqja/ppa/ubuntu focal InRelease Fetched 0 B in 0s (0 B/s) Reading package lists... Done Building dependency tree Reading state information... Done === Command detached from window (Fri Oct 28 11:16:34 2022) === === Command terminated with exit status 1 (Fri Oct 28 11:16:44 2022) === [screen is terminating] $ uname -a Linux tempo 5.4.0-131-generic #147-Ubuntu SMP Fri Oct 14 17:07:22 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/*elease* DISTRIB_ID=Ubuntu DISTRIB_RELEASE=20.04 DISTRIB_CODENAME=focal DISTRIB_DESCRIPTION="Ubuntu 20.04.5 LTS" NAME="Ubuntu" VERSION="20.04.5 LTS (Focal Fossa)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04.5 LTS" VERSION_ID="20.04" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; VERSION_CODENAME=focal UBUNTU_CODENAME=focal ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-131-generic 5.4.0-131.147 ProcVersionSignature: Ubuntu 5.4.0-131.147-generic 5.4.210 Uname: Linux 5.4.0-131-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: edik 1914 F pulseaudio /dev/snd/controlC0: edik 1914 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Fri Oct 28 11:21:00 2022 InstallationDate: Installed on 2019-05-30 (1246 days ago) InstallationMedia: Xubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. eno0 no wireless extensions. ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-131-generic root=UUID=a501cd51-bc07-496b-a8dd-bee5e1db7c02 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-131-generic N/A linux-backports-modules-5.4.0-131-generic N/A linux-firmware 1.187.33 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2022-10-28 (0 days ago) dmi.bios.date: 05/21/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: KGIBX10J.86A.5531.2010.0521.1135 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: DP55SB dmi.board.vendor: Intel Corporation dmi.board.version: AAE47220-304 dmi.chassis.type: 2 dmi.modalias: dmi:bvnIntelCorp.:bvrKGIBX10J.86A.5531.2010.0521.1135:bd05/21/2010:svn:pn:pvr:rvnIntelCorporation:rnDP55SB:rvrAAE47220-304:cvn:ct2:cvr: ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995126 Title: upgrade from 20.04 to 22.04.1 fails Status in linux package in Ubuntu: New Bug description: $ sudo do-release-upgrade -d Checking for a new Ubuntu release Get:1 Upgrade tool signature [819 B] Get:2 Upgrade tool [1,265 kB]
[Kernel-packages] [Bug 1995108] Re: RTL8111/8168/8411 throughput/power/CPU bug
** Description changed: Hi, - I'm running into an issue where the RTL8111/8168/8411 gigabit ethernet - adapter is stuck at 700mbps transfer speeds, but will be able to hit - 940-950mbps speeds as soon as the CPU is stressed to 100%. It is the - same as this bug posted several years ago: + I'm running into an issue where the RTL8111/8168/8411 (rev 15) gigabit + ethernet adapter is stuck at 700mbps transfer speeds, but will be able + to hit 940-950mbps speeds as soon as the CPU is stressed to 100%. It is + the same as this bug posted several years ago: https://superuser.com/questions/1428360/poor-network-throughput-but- double-under-high-cpu-load/1749982 - Exact instructions to reproduce this bug: on mini PC run: iperf3 -s -B on client run: iperf3 -R -c miniPC.lan - λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34124 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 1.00-2.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 2.00-3.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 3.00-4.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 4.00-5.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 5.00-6.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 6.00-7.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 7.00-8.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 8.00-9.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 9.00-10.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 10.00-11.00 sec 82.7 MBytes 693 Mbits/sec [ 5] 11.00-12.00 sec 83.4 MBytes 699 Mbits/sec [ 5] 12.00-13.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 13.00-14.00 sec 82.8 MBytes 695 Mbits/sec [ 5] 14.00-15.00 sec 82.7 MBytes 694 Mbits/sec [ 5] 15.00-16.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 16.00-17.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 17.00-18.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 18.00-19.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 19.00-19.09 sec 7.42 MBytes 694 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-19.09 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-19.09 sec 1.55 GBytes 696 Mbits/sec receiver iperf3: interrupt - the client has terminated - under stress test I ran s-tui on the mini PC, enabled the stress test option, and saw all cores boosted to 2.90 GHz (max turbo on an Intel N5095). The ethernet speeds immediately jumped to gigabit wire speeds: λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34144 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 113 MBytes 946 Mbits/sec [ 5] 1.00-2.00 sec 113 MBytes 949 Mbits/sec [ 5] 2.00-3.00 sec 113 MBytes 949 Mbits/sec [ 5] 3.00-4.00 sec 113 MBytes 949 Mbits/sec [ 5] 4.00-5.00 sec 113 MBytes 949 Mbits/sec [ 5] 5.00-6.00 sec 113 MBytes 949 Mbits/sec [ 5] 6.00-6.27 sec 31.0 MBytes 949 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-6.27 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-6.27 sec 709 MBytes 949 Mbits/sec receiver iperf3: interrupt - the client has terminated - I have tried both the r8169 and r8168 drivers on both 22.04 (kernel 5.15 and 5.19) and also on 22.10 (only kernel 5.19 tested). This issue remains on all combinations tested. I verified the driver being used by running the following: root@snuminipc:~# ethtool -i enp2s0 driver: r8169 version: 5.19.0-23-generic firmware-version: rtl8168h-2_0.0.2 02/26/15 - expansion-rom-version: + expansion-rom-version: bus-info: :02:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p',
[Kernel-packages] [Bug 1806488] Re: Support non-strict iommu mode on arm64
** Also affects: linux-aws (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-aws (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-aws (Ubuntu Bionic) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Cosmic) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Disco) Status: New => Invalid ** Changed in: linux-aws (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-aws (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu Jammy) Status: New => Invalid ** Changed in: linux (Ubuntu Kinetic) Status: New => Invalid ** Changed in: linux-aws (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1806488 Title: Support non-strict iommu mode on arm64 Status in linux package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-aws source package in Bionic: Invalid Status in linux source package in Cosmic: Fix Released Status in linux-aws source package in Cosmic: Invalid Status in linux source package in Disco: Fix Released Status in linux-aws source package in Disco: Invalid Status in linux source package in Jammy: Invalid Status in linux-aws source package in Jammy: In Progress Status in linux source package in Kinetic: Invalid Status in linux-aws source package in Kinetic: In Progress Bug description: [Impact] The Intel IOMMU driver provides an option for strict mode. When disabled, batching of IOTLB flush operations is permitted, allowing the user to trade-off isolation for improved performance. Ubuntu's kernel currently lacks a parity for this feature for ARM. There's a significant performance gain to be had by removing the need to flush the IOMMU TLB on every unmap on arm64. I'm seeing a 25% performance gain w/ fio reads on a single NVMe device. This mode of operation is available for x86 via the "intel_iommu=strict" parameter. Upstream now exposes an equivalent feature for ARM platforms via the "iommu.strict=[0|1]" parameter, while retaining the default strict-enabled mode. [Test Case] Run fio with the following config before and after applying the patches and collection IOPS count. Run again after applying the patches. Finally, run a 3rd time after adding iommu.strict=0 to the kernel commandline. Performance should not regress after the update. Performance should further improve after adding iommu.strict=0 - but if it doesn't for some reason, that is not a regression. $ cat fio.rc [global] rw=read direct=1 ioengine=libaio iodepth=2048 numjobs=10 bs=4k group_reporting=1 group_reporting=1 cpumask=0xff runtime=100 loops = 1 [job1] filename=/dev/nvme0n1 [Fix] 44f6876a00e83 iommu/arm-smmu: Support non-strict mode b2dfeba654cb0 iommu/io-pgtable-arm-v7s: Add support for non-strict mode 9662b99a19abc iommu/arm-smmu-v3: Add support for non-strict mode b6b65ca20bc93 iommu/io-pgtable-arm: Add support for non-strict mode 68a6efe86f6a1 iommu: Add "iommu.strict" command line option 2da274cdf998a iommu/dma: Add support for non-strict mode 07fdef34d2be6 iommu/arm-smmu-v3: Implement flush_iotlb_all hook 85c7a0f1ef624 iommu/io-pgtable-arm: Fix race handling in split_blk_unmap() [Regression Risk] Most of these patches are specific to ARM, and have been regression tested on both arm64 (HiSilicon D06) and armhf (QEMU virt) using "stress-ng --vm $(nproc)" 2 patches do touch arch-indep code however: > 68a6efe86f6a1 iommu: Add "iommu.strict" command line option Adds a new command line option and sets an attribute that iommu drivers can optionally react to. Doesn't change default behavior. > 2da274cdf998a iommu/dma: Add support for non-strict mode This driver is only built for arm64 and ppc64el (determined by looking at the build logs). Most of this patch only changes behavior in the non-default (and new) iommu.strict=0 case. The exception, which is called out in the commit message, is this hunk: - WARN_ON(iommu_unmap(domain, dma_addr, size) != size); + WARN_ON(iommu_unmap_fast(domain, dma_addr, size) != size); + if (!cookie->fq_domain) + iommu_tlb_sync(domain); In the default case, where fq_domain will be NULl, we are now factoring iommu_unmap() into: iommu_unmap_fast() iommu_tlb_sync() Looking at the source to iommu_unmap() confirms that this is functionally equivalent. To manage notifications
[Kernel-packages] [Bug 1995108] 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/1995108 Title: RTL8111/8168/8411 throughput/power/CPU bug Status in linux package in Ubuntu: Confirmed Bug description: Hi, I'm running into an issue where the RTL8111/8168/8411 gigabit ethernet adapter is stuck at 700mbps transfer speeds, but will be able to hit 940-950mbps speeds as soon as the CPU is stressed to 100%. It is the same as this bug posted several years ago: https://superuser.com/questions/1428360/poor-network-throughput-but- double-under-high-cpu-load/1749982 Exact instructions to reproduce this bug: on mini PC run: iperf3 -s -B on client run: iperf3 -R -c miniPC.lan λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34124 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 1.00-2.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 2.00-3.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 3.00-4.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 4.00-5.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 5.00-6.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 6.00-7.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 7.00-8.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 8.00-9.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 9.00-10.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 10.00-11.00 sec 82.7 MBytes 693 Mbits/sec [ 5] 11.00-12.00 sec 83.4 MBytes 699 Mbits/sec [ 5] 12.00-13.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 13.00-14.00 sec 82.8 MBytes 695 Mbits/sec [ 5] 14.00-15.00 sec 82.7 MBytes 694 Mbits/sec [ 5] 15.00-16.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 16.00-17.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 17.00-18.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 18.00-19.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 19.00-19.09 sec 7.42 MBytes 694 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-19.09 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-19.09 sec 1.55 GBytes 696 Mbits/sec receiver iperf3: interrupt - the client has terminated under stress test I ran s-tui on the mini PC, enabled the stress test option, and saw all cores boosted to 2.90 GHz (max turbo on an Intel N5095). The ethernet speeds immediately jumped to gigabit wire speeds: λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34144 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 113 MBytes 946 Mbits/sec [ 5] 1.00-2.00 sec 113 MBytes 949 Mbits/sec [ 5] 2.00-3.00 sec 113 MBytes 949 Mbits/sec [ 5] 3.00-4.00 sec 113 MBytes 949 Mbits/sec [ 5] 4.00-5.00 sec 113 MBytes 949 Mbits/sec [ 5] 5.00-6.00 sec 113 MBytes 949 Mbits/sec [ 5] 6.00-6.27 sec 31.0 MBytes 949 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-6.27 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-6.27 sec 709 MBytes 949 Mbits/sec receiver iperf3: interrupt - the client has terminated I have tried both the r8169 and r8168 drivers on both 22.04 (kernel 5.15 and 5.19) and also on 22.10 (only kernel 5.19 tested). This issue remains on all combinations tested. I verified the driver being used by running the following: root@snuminipc:~# ethtool -i enp2s0 driver: r8169 version: 5.19.0-23-generic firmware-version: rtl8168h-2_0.0.2 02/26/15 expansion-rom-version: bus-info: :02:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p',
[Kernel-packages] [Bug 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Any signs of improvement after the 20220329.git681281e4-0ubuntu3.6 update? After updating I had no more problems. -- 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/1971656 Title: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04 Status in linux-firmware package in Ubuntu: Confirmed Bug description: On a Lenovo P14s (RTL8111/8168/8411), the WiFi connection gets stuck at times. When this happens, there is no way to use `sudo`, the WiFi GNOME UI says NetworkManager is not running (which it is), and `dmesg -w` continuously outputs: ``` [90296.470925] rtw89_pci :03:00.0: failed to get available addr cam [90296.470935] rtw89_pci :03:00.0: failed to init addr cam [90296.586817] rtw89_pci :03:00.0: failed to get available addr cam [90296.586828] rtw89_pci :03:00.0: failed to init addr cam [90296.698790] rtw89_pci :03:00.0: failed to get available addr cam [90296.698797] rtw89_pci :03:00.0: failed to init addr cam [90296.810783] rtw89_pci :03:00.0: failed to get available addr cam [90296.810790] rtw89_pci :03:00.0: failed to init addr cam ``` The only solution I've found is to reboot the machine. However, turning off needs to be forced (magic keys still work for rebooting). ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-firmware 20220329.git681281e4-0ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 5 07:49:18 2022 Dependencies: firmware-sof-signed 2.0-1ubuntu2 InstallationDate: Installed on 2022-02-25 (68 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) MachineType: LENOVO 21A3MZ PackageArchitecture: all ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-27-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 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.15.0-27-generic N/A linux-backports-modules-5.15.0-27-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 SourcePackage: linux-firmware UpgradeStatus: Upgraded to jammy on 2022-04-21 (13 days ago) dmi.bios.date: 11/05/2021 dmi.bios.release: 1.13 dmi.bios.vendor: LENOVO dmi.bios.version: R1MET43W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 21A3MZ 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.13 dmi.modalias: dmi:bvnLENOVO:bvrR1MET43W(1.13):bd11/05/2021:br1.13:efr1.13:svnLENOVO:pn21A3MZ:pvrThinkPadP14sGen2a:rvnLENOVO:rn21A3MZ:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21A0_BU_Think_FM_ThinkPadP14sGen2a: dmi.product.family: ThinkPad P14s Gen 2a dmi.product.name: 21A3MZ dmi.product.sku: LENOVO_MT_21A0_BU_Think_FM_ThinkPad P14s Gen 2a dmi.product.version: ThinkPad P14s Gen 2a dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1971656/+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 1995109] [NEW] bluefield-edac: Potentially overflowing expression
Public bug reported: SRU Justification: [Impact] Potential integer overflow in men_ctrl_idx detected by static tool analyser. [Fix] Declare as type u64 instead of type int [Test Case] NA since the variable is read from the ACPI table [Regression Potential] Can be considered minimal ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- 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/1995109 Title: bluefield-edac: Potentially overflowing expression Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: [Impact] Potential integer overflow in men_ctrl_idx detected by static tool analyser. [Fix] Declare as type u64 instead of type int [Test Case] NA since the variable is read from the ACPI table [Regression Potential] Can be considered minimal To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995109/+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 1995108] [NEW] RTL8111/8168/8411 throughput/power/CPU bug
Public bug reported: Hi, I'm running into an issue where the RTL8111/8168/8411 gigabit ethernet adapter is stuck at 700mbps transfer speeds, but will be able to hit 940-950mbps speeds as soon as the CPU is stressed to 100%. It is the same as this bug posted several years ago: https://superuser.com/questions/1428360/poor-network-throughput-but- double-under-high-cpu-load/1749982 Exact instructions to reproduce this bug: on mini PC run: iperf3 -s -B on client run: iperf3 -R -c miniPC.lan λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34124 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 1.00-2.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 2.00-3.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 3.00-4.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 4.00-5.00 sec 82.8 MBytes 694 Mbits/sec [ 5] 5.00-6.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 6.00-7.00 sec 83.3 MBytes 699 Mbits/sec [ 5] 7.00-8.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 8.00-9.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 9.00-10.00 sec 82.6 MBytes 693 Mbits/sec [ 5] 10.00-11.00 sec 82.7 MBytes 693 Mbits/sec [ 5] 11.00-12.00 sec 83.4 MBytes 699 Mbits/sec [ 5] 12.00-13.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 13.00-14.00 sec 82.8 MBytes 695 Mbits/sec [ 5] 14.00-15.00 sec 82.7 MBytes 694 Mbits/sec [ 5] 15.00-16.00 sec 83.1 MBytes 697 Mbits/sec [ 5] 16.00-17.00 sec 83.8 MBytes 703 Mbits/sec [ 5] 17.00-18.00 sec 83.2 MBytes 698 Mbits/sec [ 5] 18.00-19.00 sec 82.5 MBytes 692 Mbits/sec [ 5] 19.00-19.09 sec 7.42 MBytes 694 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-19.09 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-19.09 sec 1.55 GBytes 696 Mbits/sec receiver iperf3: interrupt - the client has terminated under stress test I ran s-tui on the mini PC, enabled the stress test option, and saw all cores boosted to 2.90 GHz (max turbo on an Intel N5095). The ethernet speeds immediately jumped to gigabit wire speeds: λ iperf3 -R -c 192.168.1.103 -t 600 # download Connecting to host 192.168.1.103, port 5201 Reverse mode, remote host 192.168.1.103 is sending [ 5] local 192.168.1.127 port 34144 connected to 192.168.1.103 port 5201 [ ID] Interval Transfer Bitrate [ 5] 0.00-1.00 sec 113 MBytes 946 Mbits/sec [ 5] 1.00-2.00 sec 113 MBytes 949 Mbits/sec [ 5] 2.00-3.00 sec 113 MBytes 949 Mbits/sec [ 5] 3.00-4.00 sec 113 MBytes 949 Mbits/sec [ 5] 4.00-5.00 sec 113 MBytes 949 Mbits/sec [ 5] 5.00-6.00 sec 113 MBytes 949 Mbits/sec [ 5] 6.00-6.27 sec 31.0 MBytes 949 Mbits/sec - - - - - - - - - - - - - - - - - - - - - - - - - [ ID] Interval Transfer Bitrate [ 5] 0.00-6.27 sec 0.00 Bytes 0.00 bits/sec sender [ 5] 0.00-6.27 sec 709 MBytes 949 Mbits/sec receiver iperf3: interrupt - the client has terminated I have tried both the r8169 and r8168 drivers on both 22.04 (kernel 5.15 and 5.19) and also on 22.10 (only kernel 5.19 tested). This issue remains on all combinations tested. I verified the driver being used by running the following: root@snuminipc:~# ethtool -i enp2s0 driver: r8169 version: 5.19.0-23-generic firmware-version: rtl8168h-2_0.0.2 02/26/15 expansion-rom-version: bus-info: :02:00.0 supports-statistics: yes supports-test: no supports-eeprom-access: no supports-register-dump: yes supports-priv-flags: no ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.19.0-23-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D12p', '/dev/snd/pcmC0D11p', '/dev/snd/pcmC0D10p', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer' CasperMD5CheckResult: pass Date: Fri Oct 28 14:38:41 2022 InstallationDate: Installed on 2022-10-16 (11 days ago) InstallationMedia: Ubuntu-Server 22.04.1 LTS "Jammy Jellyfish" - Release amd64 (20220809)
[Kernel-packages] [Bug 1995104] 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/1995104 Title: Bluetooth error Status in linux package in Ubuntu: Confirmed Bug description: bluetoothd - Failed to set mode: Failed (0x03) Bluetooth: hci0: Failed to read MSFT supported features (-19) Bluetooth: hci0: sending frame failed (-19) Bluetooth: hci0: FW download error recovery failed (-19) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: zayar 2007 F wireplumber /dev/snd/controlC0: zayar 2007 F wireplumber /dev/snd/controlC1: zayar 2007 F wireplumber /dev/snd/seq:zayar 2005 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 20:06:03 2022 MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IH_GA401IH ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=6383ae46-de76-411c-b77b-bc93ae454315 ro quiet splash vt.handoff=7 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.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IH.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.212:bd03/14/2022:br5.16:efr3.15:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995104/+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 1995104] [NEW] Bluetooth error
Public bug reported: bluetoothd - Failed to set mode: Failed (0x03) Bluetooth: hci0: Failed to read MSFT supported features (-19) Bluetooth: hci0: sending frame failed (-19) Bluetooth: hci0: FW download error recovery failed (-19) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: zayar 2007 F wireplumber /dev/snd/controlC0: zayar 2007 F wireplumber /dev/snd/controlC1: zayar 2007 F wireplumber /dev/snd/seq:zayar 2005 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 20:06:03 2022 MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IH_GA401IH ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=6383ae46-de76-411c-b77b-bc93ae454315 ro quiet splash vt.handoff=7 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.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IH.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.212:bd03/14/2022:br5.16:efr3.15:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14 GA401IH_GA401IH dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 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/1995104 Title: Bluetooth error Status in linux package in Ubuntu: New Bug description: bluetoothd - Failed to set mode: Failed (0x03) Bluetooth: hci0: Failed to read MSFT supported features (-19) Bluetooth: hci0: sending frame failed (-19) Bluetooth: hci0: FW download error recovery failed (-19) ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: zayar 2007 F wireplumber /dev/snd/controlC0: zayar 2007 F wireplumber /dev/snd/controlC1: zayar 2007 F wireplumber /dev/snd/seq:zayar 2005 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 20:06:03 2022 MachineType: ASUSTeK COMPUTER INC. ROG Zephyrus G14 GA401IH_GA401IH ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=6383ae46-de76-411c-b77b-bc93ae454315 ro quiet splash vt.handoff=7 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.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/14/2022 dmi.bios.release: 5.16 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GA401IH.212 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GA401IH dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.15 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGA401IH.212:bd03/14/2022:br5.16:efr3.15:svnASUSTeKCOMPUTERINC.:pnROGZephyrusG14GA401IH_GA401IH:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGA401IH:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0:sku: dmi.product.family: ROG Zephyrus G14 dmi.product.name: ROG Zephyrus G14
[Kernel-packages] [Bug 1930783] Re: integrity: Problem loading X.509 certificate
I have this error message as well on an Acer laptop. There doesn't seem to be any issues outside of the error message. I ran sudo badblocks -sv /dev/ with no change. -- 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/1930783 Title: integrity: Problem loading X.509 certificate Status in linux package in Ubuntu: Expired Bug description: Following error shows on Acer machines while booting when UEFI boot is enabled. integrity: Problem loading X.509 certificate -65 The issue is discussed at https://bugzilla.opensuse.org/show_bug.cgi?id=1129471 and a patch is available at https://lkml.org/lkml/2019/7/16/23. Seems like this patch is not included in Ubuntu as I'm still getting this error. I'm using Linux Mint 20, which is based on Ubuntu 20.04. This error comes while live booting Ubuntu 20.04 and Ubuntu 18.04 also. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930783/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
looks like not u-d-c's issue because logind also got stuck when operates with nvidia. I think either trying drm-tip / bisect kernel / reports it to nvidia may help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1995046] Re: Realtek 8852c WiFi/BT firmware support
SRU: * https://lists.ubuntu.com/archives/kernel-team/2022-October/134376.html (jammy) * https://lists.ubuntu.com/archives/kernel-team/2022-October/134377.html (kinetic) ** Description changed: + [SRU Justification] + + [Impact] + + Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add + both FW & config file to get it work with oem-6.0. + + WiFi: rtw8852c + + rtw89_8852ce :02:00.0: enabling device ( -> 0003) + rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 + rtw89_8852ce :02:00.0: failed to request firmware + rtw89_8852ce :02:00.0: failed to wait firmware completion + rtw89_8852ce :02:00.0: failed to setup chip information + rtw89_8852ce: probe of :02:00.0 failed with error -22 + + BT: rtl8852cu + + Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin + Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found + + [Fix] + + rtw89/rtw8852c_fw.bin and rtl_bt/rtl8852cu_fw.bin are required. Kinetic + has already 5 commits out of 8. + + [Test Case] + + The driver will prompt for missed firmware blobs for a given platform. + + [Where problems could occur] + + New device to be supported for Jammy oem-6.0. May cause system stability + issues or power consumption performance. + + [Other Info] + + This device is supported since v5.19, so only Jammy (for oem-6.0) and + Kinetic are nominated for fix. + + == original bug report == + Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add both FW & config file to get it work with oem-6.0. WiFi: rtw8852c [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003) [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5 BT: rtl8852cu [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90 -- 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/1995046 Title: Realtek 8852c WiFi/BT firmware support Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Kinetic: In Progress Status in linux-firmware source package in Lunar: Fix Released Bug description: [SRU Justification] [Impact] Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add both FW & config file to get it work with oem-6.0. WiFi: rtw8852c rtw89_8852ce :02:00.0: enabling device ( -> 0003) rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 rtw89_8852ce :02:00.0: failed to request firmware rtw89_8852ce :02:00.0: failed to wait firmware completion rtw89_8852ce :02:00.0: failed to setup chip information rtw89_8852ce: probe of :02:00.0 failed with error -22 BT: rtl8852cu Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found [Fix] rtw89/rtw8852c_fw.bin and rtl_bt/rtl8852cu_fw.bin are required. Kinetic has already 5 commits out of 8. [Test Case] The driver will prompt for missed firmware blobs for a given platform. [Where problems could occur] New device to be supported for Jammy oem-6.0. May cause system stability issues or power consumption performance. [Other Info] This device is supported since v5.19, so only Jammy (for oem-6.0) and Kinetic are nominated for fix. == original bug report == Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add both FW & config file to get it work with oem-6.0. WiFi: rtw8852c [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003) [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion [ 2.644843] rtw89_8852ce
[Kernel-packages] [Bug 1958191] Re: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later)
Having this issue on razer blade 17 pro (2021) on Ubuntu 22.10. Don't see anything relevant in logs. It works fine most of the time but every so often has heavy flickering for a few seconds or minutes. -- 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/1958191 Title: [i915] Screen flickering in Ubuntu 22.04 (until i915.enable_dc=0 intel_idle.max_cstate=2 are added) (fixed in 5.17.7 and later) Status in linux package in Ubuntu: Fix Released Bug description: Ubuntu 22.04 development branch on kernel 5.15.0-17-generic @ 18/1/2022 Booting into desktop gets heavy screen flickering and disforming (unusable) both booting on xorg and wayland on kernel 5.13 it did not occur so heavy (only little glitches once in a while see bug 1948778) adding the kernel paramater intel_idle.max_cstate=4 fixed this i had these same bugs on this machine before: https://bugs.launchpad.net/ubuntu/+source/linux-hwe/+bug/1838644 https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1948778 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-17-generic 5.15.0-17.17 ProcVersionSignature: Ubuntu 5.15.0-17.17-generic 5.15.12 Uname: Linux 5.15.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu75 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lotuspsychje 1201 F pipewire-media- lotuspsychje 1207 F pulseaudio /dev/snd/seq:lotuspsychje 1193 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Jan 18 04:22:00 2022 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter Bus 001 Device 003: ID 04f2:b59e Chicony Electronics Co., Ltd Chicony USB2.0 Camera Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Notebook N7x0WU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-17-generic root=UUID=a41247d1-3bc3-453e-849a-e07fdcca6201 ro quiet splash intel_idle.max_cstate=4 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-17-generic N/A linux-backports-modules-5.15.0-17-generic N/A linux-firmware 1.204 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/07/2019 dmi.bios.release: 7.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 7.13 dmi.board.asset.tag: Tag 12345 dmi.board.name: N7x0WU dmi.board.vendor: Notebook dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: No Enclosure dmi.chassis.version: N/A dmi.ec.firmware.release: 7.14 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr7.13:bd01/07/2019:br7.13:efr7.14:svnNotebook:pnN7x0WU:pvrNotApplicable:rvnNotebook:rnN7x0WU:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:skuNotApplicable: dmi.product.family: Not Applicable dmi.product.name: N7x0WU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: Notebook To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1958191/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
** Attachment added: "nv.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+attachment/5627492/+files/nv.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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
Also i found the solution! Listen: 1) I boot with latest kernel 2) After booting i do not see any output in monitor, just 'no signal' 3) Do not reboot! Go away for 2-3 minutes! Do not touch to PC 4) And after that all works! I see login screen and able to login! Just wait 2-3 min! I attached journalctl -b Someone, please, try this solution and confirm. Is this behavior reproduced on your system? Not cool to wait 2-3 min, but works! There is some bug that should be fixed... Probably logs bellow can help to analyze problem? -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
/var/log/gpu-manager.log ** Attachment added: "gpu-manager.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+attachment/5627490/+files/gpu-manager.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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+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 1995046] Re: Realtek 8852c WiFi/BT firmware support
** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Kinetic) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Lunar) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1995046 Title: Realtek 8852c WiFi/BT firmware support Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Kinetic: In Progress Status in linux-firmware source package in Lunar: Fix Released Bug description: Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add both FW & config file to get it work with oem-6.0. WiFi: rtw8852c [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003) [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5 BT: rtl8852cu [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995046/+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 1993223] Re: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04
SRU: https://lists.ubuntu.com/archives/kernel- team/2022-October/134375.html (jammy) ** Changed in: linux-firmware (Ubuntu Jammy) Status: Confirmed => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Description changed: + [SRU Justification] + + [Impact] + + Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs + firmware to be loaded by amdgpu. + + [Fix] + + 5 commits from mainline firmware repository. + + [Test Case] + + Kernel dmesg should no longer dump: + + amdgpu_vcn: Can't load firmware amdgpu/vcn_3_1_2.bin + + [Where problems could occur] + + New hardware support. May affect system stability. + + [Other Info] + + These firmware blobs are only referenced in linux/kinetic and linux- + oem-6.0/jammy, and are already available in linux-firmware/kinetic, so + only Jammy is nominated for fix here. + + == original bug report == + Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs firmware to be loaded by amdgpu. This firmware has been upstreamed by these commits, which are already part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1) db6db36a amdgpu: add firmware for VCN 3.1.2 IP block 3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block 639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block 76589464 amdgpu: add firmware for GC 10.3.6 IP block 427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block Matching kernel code for this processor is already upstreamed in 6.0 kernel, and so this should work with OEM-6.0. -- 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/1993223 Title: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: In Progress Status in linux-firmware source package in Kinetic: Fix Released Bug description: [SRU Justification] [Impact] Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs firmware to be loaded by amdgpu. [Fix] 5 commits from mainline firmware repository. [Test Case] Kernel dmesg should no longer dump: amdgpu_vcn: Can't load firmware amdgpu/vcn_3_1_2.bin [Where problems could occur] New hardware support. May affect system stability. [Other Info] These firmware blobs are only referenced in linux/kinetic and linux- oem-6.0/jammy, and are already available in linux-firmware/kinetic, so only Jammy is nominated for fix here. == original bug report == Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs firmware to be loaded by amdgpu. This firmware has been upstreamed by these commits, which are already part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1) db6db36a amdgpu: add firmware for VCN 3.1.2 IP block 3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block 639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block 76589464 amdgpu: add firmware for GC 10.3.6 IP block 427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block Matching kernel code for this processor is already upstreamed in 6.0 kernel, and so this should work with OEM-6.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993223/+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 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
not sure if anyone reports here are same as #10 log. if anyone got the nvidia stuck because of gpu-manager(#10). Is it possible to share the /var/log/gpu-manager.log ? not sure if the system is ssh-able when issue happens but if yes, it's easy to get the log. or boot to multi-user.target (if it's reachable), then record the content of /var/log/gpu-manager.log when entering graphic.target. or disable gpu-manager and start it after gnome-shell? If we can know which command issued by gpu-manager then we may have some ideas. -- 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/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro 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.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage
[Kernel-packages] [Bug 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
If possible, I still expect we can make grub supports to boot from
bigger initramfs.
There will still have users to meet this issue in the future if their
initramfs somehow bigger as long as we don't choose use higher
compression as workaround (for ubuntu desktop / server).
--
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/1842320
Title:
Can't boot: "error: out of memory." immediately after the grub menu
Status in grub:
Unknown
Status in OEM Priority Project:
Triaged
Status in grub2-signed package in Ubuntu:
Triaged
Status in grub2-unsigned package in Ubuntu:
Triaged
Status in initramfs-tools package in Ubuntu:
Won't Fix
Status in linux package in Ubuntu:
Confirmed
Bug description:
[Impact]
* In some cases, if the users’ initramfs grow bigger, then it’ll
likely not be able to be loaded by grub2.
* Some real cases from OEM projects:
In many built-in 4k monitor laptops with nvidia drivers, the u-d-c
puts the nvidia*.ko to initramfs which grows the initramfs to ~120M.
Also the gfxpayload=auto will remain to use 4K resolution since it’s
what EFI POST passed.
In this case, the grub isn't able to load initramfs because the
grub_memalign() won't be able to get suitable memory for the larger
file:
```
#0 grub_memalign (align=1, size=592214020) at ../../../grub-core/kern/mm.c:376
#1 0x7dd7b074 in grub_malloc (size=592214020) at
../../../grub-core/kern/mm.c:408
#2 0x7dd7a2c8 in grub_verifiers_open (io=0x7bc02d80, type=131076)
at ../../../grub-core/kern/verifiers.c:150
#3 0x7dd801d4 in grub_file_open (name=0x7bc02f00
"/boot/initrd.img-5.17.0-1011-oem",
type=131076) at ../../../grub-core/kern/file.c:121
#4 0x7bcd5a30 in ?? ()
#5 0x7fe21247 in ?? ()
#6 0x7bc030c8 in ?? ()
#7 0x00017fe21238 in ?? ()
#8 0x7bcd5320 in ?? ()
#9 0x7fe21250 in ?? ()
#10 0x in ?? ()
```
Based on grub_mm_dump, we can see the memory fragment (some parts seem
likely be used because of 4K resolution?) and doesn’t have available
contiguous memory for larger file as:
```
grub_real_malloc(...)
...
if (cur->size >= n + extra)
```
Based on UEFI Specification Section 7.2[1] and UEFI driver writers’
guide 4.2.3[2], we can ask 32bits+ on AllocatePages().
As most X86_64 platforms should support 64 bits addressing, we should
extend GRUB_EFI_MAX_USABLE_ADDRESS to 64 bits to get more available
memory.
* When users grown the initramfs, then probably will get initramfs
not found which really annoyed and impact the user experience (system
not able to boot).
[Test Plan]
* detailed instructions how to reproduce the bug:
1. Any method to grow the initramfs, such as install nvidia-driver.
2. If developers would like to reproduce, then could dd if=/dev/random
of=... bs=1M count=500, something like:
```
$ cat /usr/share/initramfs-tools/hooks/zzz-touch-a-file
#!/bin/sh
PREREQ=""
prereqs()
{
echo "$PREREQ"
}
case $1 in
# get pre-requisites
prereqs)
prereqs
exit 0
;;
esac
. /usr/share/initramfs-tools/hook-functions
dd if=/dev/random of=${DESTDIR}/test-500M bs=1M count=500
```
And then update-initramfs
* After applying my patches, the issue is gone.
* I did also test my test grubx64.efi in:
1. X86_64 qemu with
1.1. 60M initramfs + 5.15.0-37-generic kernel
1.2. 565M initramfs + 5.17.0-1011-oem kernel
2. Amd64 HP mobile workstation with
2.1. 65M initramfs + 5.15.0-39-generic kernel
2.2. 771M initramfs + 5.17.0-1011-oem kernel
All working well.
[Where problems could occur]
* The changes almost in i386/efi, thus the impact will be in the i386 /
x86_64 EFI system.
The other change is to modify the “grub-core/kern/efi/mm.c” but I use the
original addressing for “arm/arm64/ia64/riscv32/riscv64”.
Thus it should not impact them.
* There is a “#if defined(__x86_64__)” which intent to limit the >
32bits code in i386 system and also
```
#if defined (__code_model_large__)
-#define GRUB_EFI_MAX_USABLE_ADDRESS 0x
+#define GRUB_EFI_MAX_USABLE_ADDRESS __UINTPTR_MAX__
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x7fff
#else
#define GRUB_EFI_MAX_USABLE_ADDRESS 0x7fff
+#define GRUB_EFI_MAX_ALLOCATION_ADDRESS 0x3fff
#endif
```
If everything works as expected, then i386 should working good.
If not lucky, based on “UEFI writers’ guide”[2], the i386 will get >
4GB memory region and never be able to access.
[Other Info]
* Upstream grub2 bug #61058
https://savannah.gnu.org/bugs/index.php?61058
* Test PPA: https://launchpad.net/~os369510/+archive/ubuntu/lp1842320
* Test grubx64.efi:
https://people.canonical.com/~jeremysu/lp1842320/grubx64.efi.lp1842320
* Test source code:
[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera
SRU: * https://lists.ubuntu.com/archives/kernel-team/2022-October/134373.html (jammy) * https://lists.ubuntu.com/archives/kernel-team/2022-October/134374.html (kinetic) ** Description changed: + [SRU Justfication:linux-firmware] + + [Impact] + + Need new firmware updates for additional camera senesors. + + [Fix] + + Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for + hi556/ovti02c1. + + [Test Case] + + The driver will prompt for missed firmware blobs for a given platform. + + [Where problems could occur] + + There is still no suspend support for the camera driver, and user sessions + across system suspend have to be restarted. + + [Other Info] + + New sensors are introduced in Jammy oem kernels only, and kinetic is nominated + for future hwe migration. + + = original bug report == + This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. ** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Jammy) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Jammy) Assignee: (unassigned) => You-Sheng Yang (vicamo) ** Changed in: linux-firmware (Ubuntu Kinetic) Importance: Undecided => High ** Changed in: linux-firmware (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-firmware (Ubuntu Kinetic) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987595 Title: Support Intel IPU6 MIPI camera Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-firmware package in Ubuntu: New Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-firmware source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Status in linux-firmware source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: [SRU Justfication:linux-firmware] [Impact] Need new firmware updates for additional camera senesors. [Fix] Firmware updates for Intel IPU6/VSC drivers, as well as new firmware blobs for hi556/ovti02c1. [Test Case] The driver will prompt for missed firmware blobs for a given platform. [Where problems could occur] There is still no suspend support for the camera driver, and user sessions across system suspend have to be restarted. [Other Info] New sensors are introduced in Jammy oem kernels only, and kinetic is nominated for future hwe migration. = original bug report == This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987595/+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 1993890] Re: Jammy does not work on wifi for Intel 3165
I'm not even sure that backport-iwlwifi-dkms package was actually installed when I did 'sudo apt remove backport-iwlwifi-dkms'. I've just done 'sudo apt install backport-iwlwifi-dkms': resulted in about 30 packages being installed (including ones for compiling kernel), and a new 5.15.0-52 kernel being compiled. wifi still not work after rebooting. -- 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/1993890 Title: Jammy does not work on wifi for Intel 3165 Status in linux package in Ubuntu: Confirmed Bug description: Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network Manager sees the router but never manages to connect to it. I've tried the purge of the backport iwlwifi module but that didn't help. I followed the instructions on another post to give diagnostics. They are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/ Some more info: admin@Server:~$ lspci -nnk | grep 3165 02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010] admin@Server:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no – I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and that worked Ok. I rebooted, disconnected Ethernet & turned wifi on. But still get 'SSID connecting' which never finishes and no wifi. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-iwlwifi-generic 5.15.0.52.52 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: admin 1506 F pulseaudio /dev/snd/controlC0: admin 1506 F pulseaudio /dev/snd/controlC1: admin 1506 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 14:36:50 2022 InstallationDate: Installed on 2022-08-15 (68 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IwConfig: lono wireless extensions. enp3s0no wireless extensions. wlp2s0no wireless extensions. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago) dmi.bios.date: 03/14/2018 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993890/+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 1993890] Re: Jammy does not work on wifi for Intel 3165
I'm not even sure that backport-iwlwifi-dkms package was actually installed when I did 'sudo apt remove backport-iwlwifi-dkms'. I've just done 'sudo apt install backport-iwlwifi-dkms': resulted in about 30 packages being installed (including ones for compiling kernel), and a new 5.15.0-52 kernel being compiled. wifi still not work after rebooting. -- 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/1993890 Title: Jammy does not work on wifi for Intel 3165 Status in linux package in Ubuntu: Confirmed Bug description: Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network Manager sees the router but never manages to connect to it. I've tried the purge of the backport iwlwifi module but that didn't help. I followed the instructions on another post to give diagnostics. They are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/ Some more info: admin@Server:~$ lspci -nnk | grep 3165 02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010] admin@Server:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no – I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and that worked Ok. I rebooted, disconnected Ethernet & turned wifi on. But still get 'SSID connecting' which never finishes and no wifi. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-iwlwifi-generic 5.15.0.52.52 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: admin 1506 F pulseaudio /dev/snd/controlC0: admin 1506 F pulseaudio /dev/snd/controlC1: admin 1506 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 14:36:50 2022 InstallationDate: Installed on 2022-08-15 (68 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IwConfig: lono wireless extensions. enp3s0no wireless extensions. wlp2s0no wireless extensions. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago) dmi.bios.date: 03/14/2018 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993890/+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 1994126] Re: NULL pointer dereference in power_supply_get_property
** Description changed: - Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 (containing nvidia gpu) + Ubuntu 22.10 final release boot via usb thumb drive on thinkpad T480 (containing nvidia gpu) reproducible kernel panic during boot backtrace via OCR from picture of kernel panic: Started Periodic ext4 Online Hetadata Check for All Filesystems. Started Discard unused blocks once a week. Started Refresh fuupd metadate regularly. Started Daily rotation of log files. Started Daily man-db regeneration. Started Message of the Day. Started Daily Cleanup of Temporary Directories. Started Ubuntu Advantage Timer for running repeated jobs. Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation Socket. 1 Listening on CUPS Scheduler. 1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation for snappy deeson... Listening on UUID deemon activation socket. 1 Listening on Socket activation for snappy daemon. Reached target Socket Units. 1 Reached target Basic System. 20.300662) BUG: Kernel NULL pointer dereference, address: 20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 WPF: error code (0x0010) - not-present page 20.302458) PGD O P40 0 20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579) CPU: 4 PID: 1 Comm: systemd Tainted: P 0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 20L5000BGE/20L5000BGE, BIOS N24ET7ON (1.45) 07/22/2022 20.304190) 20.304774) RIP: 0010:0N0 20.305376) Code: Unable to access opcode bytes at RIP Oxffd6. 20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202 20.3066231 RAX: RBX: 95538288 RCX: 8c43c1d89800 20.307282) RDX: b17180087cdo RSI: 0004 RDI: 8c43c1d89800 20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09: 0 20.308627) R10: R11: R12: 00 20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15: 9553a288 20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000 20.310762) CS: 0010 DS: ES: CRO: 80050033 20.311491) CR2: fffds CRS: 00011eida002 CR4: 003706e0 20.312241) Call Trace: 20.312992) https://bugs.launchpad.net/bugs/1994126 Title: NULL pointer dereference in power_supply_get_property Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 final release boot via usb thumb drive on thinkpad T480 (containing nvidia gpu) reproducible kernel panic during boot backtrace via OCR from picture of kernel panic: Started Periodic ext4 Online Hetadata Check for All Filesystems. Started Discard unused blocks once a week. Started Refresh fuupd metadate regularly. Started Daily rotation of log files. Started Daily man-db regeneration. Started Message of the Day. Started Daily Cleanup of Temporary Directories. Started Ubuntu Advantage Timer for running repeated jobs. Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation Socket. 1 Listening on CUPS Scheduler. 1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation for snappy deeson... Listening on UUID deemon activation socket. 1 Listening on Socket activation for snappy daemon. Reached target Socket Units. 1 Reached target Basic System. 20.300662) BUG: Kernel NULL pointer dereference, address: 20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 WPF: error code (0x0010) - not-present page 20.302458) PGD O P40 0 20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579) CPU: 4 PID: 1 Comm: systemd Tainted: P 0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 20L5000BGE/20L5000BGE, BIOS N24ET7ON (1.45) 07/22/2022 20.304190) 20.304774) RIP: 0010:0N0 20.305376) Code: Unable to access opcode bytes at RIP Oxffd6. 20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202 20.3066231 RAX: RBX: 95538288 RCX: 8c43c1d89800 20.307282) RDX: b17180087cdo RSI: 0004 RDI: 8c43c1d89800 20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09: 0 20.308627) R10: R11: R12: 00 20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15: 9553a288 20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000 20.310762) CS: 0010 DS: ES: CRO: 80050033 20.311491) CR2: fffds CRS:
[Kernel-packages] [Bug 1994126] Re: NULL pointer dereference in power_supply_get_property
https://bugzilla.suse.com/show_bug.cgi?id=1202386#c29 looks very similar ** Bug watch added: bugzilla.suse.com/ #1202386 https://bugzilla.suse.com/show_bug.cgi?id=1202386 -- 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/1994126 Title: NULL pointer dereference in power_supply_get_property Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu 22.10 final release boot via us thumb drive on thinkpad T480 (containing nvidia gpu) reproducible kernel panic during boot backtrace via OCR from picture of kernel panic: Started Periodic ext4 Online Hetadata Check for All Filesystems. Started Discard unused blocks once a week. Started Refresh fuupd metadate regularly. Started Daily rotation of log files. Started Daily man-db regeneration. Started Message of the Day. Started Daily Cleanup of Temporary Directories. Started Ubuntu Advantage Timer for running repeated jobs. Reached target Path Units. Listening on Avehi MONS/DNS-SD Stack Activation Socket. 1 Listening on CUPS Scheduler. 1 Listening on 0-Bus System Message Bus Socket. Starting Socket activation for snappy deeson... Listening on UUID deemon activation socket. 1 Listening on Socket activation for snappy daemon. Reached target Socket Units. 1 Reached target Basic System. 20.300662) BUG: Kernel NULL pointer dereference, address: 20.3012911 #PF: supervisor instruction fetch in kernel mode 20.3018531 WPF: error code (0x0010) - not-present page 20.302458) PGD O P40 0 20.909018) Oops: 0010 [#1] PREEMPT SHP PTI 20.303579) CPU: 4 PID: 1 Comm: systemd Tainted: P 0 5.19.0-21-generic #21-Ubuntu Hardware name: LENOVO 20L5000BGE/20L5000BGE, BIOS N24ET7ON (1.45) 07/22/2022 20.304190) 20.304774) RIP: 0010:0N0 20.305376) Code: Unable to access opcode bytes at RIP Oxffd6. 20.305982) RSP: 0018:b17180087c98 EFLAGS: 00010202 20.3066231 RAX: RBX: 95538288 RCX: 8c43c1d89800 20.307282) RDX: b17180087cdo RSI: 0004 RDI: 8c43c1d89800 20.307949) RBP: b17180087ca8 R08: 8c43c1d89838 R09: 0 20.308627) R10: R11: R12: 00 20.309318) R13: 8c43de65c000 R14: 8c43c1d89838 R15: 9553a288 20.310023) FS: 7f37adf23940 () GS:8c532270() kn1GS:000 20.310762) CS: 0010 DS: ES: CRO: 80050033 20.311491) CR2: fffds CRS: 00011eida002 CR4: 003706e0 20.312241) Call Trace: 20.312992) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994126/+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 1993223] Re: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04
Linux OEM 6.0 is starting to be available in Jammy now and Ryzen 7000 is out in the field, perhaps this could be SRU-ed to Jammy now already? -- 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/1993223 Title: MIssing GPU firmware for AMD Ryzen 7000 desktop on Jammy 22.04 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Jammy: Confirmed Status in linux-firmware source package in Kinetic: Fix Released Bug description: Ryzen 7000 (AM5) desktop processors contain RDNA2 GFX that needs firmware to be loaded by amdgpu. This firmware has been upstreamed by these commits, which are already part of Kinetic (version 20220923.gitf09bebf3-0ubuntu1) db6db36a amdgpu: add firmware for VCN 3.1.2 IP block 3647da5c amdgpu: add firmware for SDMA 5.2.6 IP block 639b5c13 amdgpu: add firmware for PSP 13.0.5 IP block 76589464 amdgpu: add firmware for GC 10.3.6 IP block 427ca6ca amdgpu: add firmware for DCN 3.1.5 IP block Matching kernel code for this processor is already upstreamed in 6.0 kernel, and so this should work with OEM-6.0. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1993223/+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 1982833] Re: Bump (kernel) '-mtune' to z16 / arch14 with 23.04
** Tags removed: l-release ** Tags added: bot-stop-nagging lunar -- 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/1982833 Title: Bump (kernel) '-mtune' to z16 / arch14 with 23.04 Status in Ubuntu on IBM z Systems: New Status in gcc-12 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Consider to bump the kernel '-mtune' to z16 (equals arch14), starting with 23.04. Discuss with IBM Z team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982833/+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 1982833] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1982833 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1982833 Title: Bump (kernel) '-mtune' to z16 / arch14 with 23.04 Status in Ubuntu on IBM z Systems: New Status in gcc-12 package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Bug description: Consider to bump the kernel '-mtune' to z16 (equals arch14), starting with 23.04. Discuss with IBM Z team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982833/+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 1982833] Re: Consider bumping (kernel) '-mtune' to z16 / arch14 with 23.04
** Information type changed from Private to Public ** Summary changed: - Consider bumping (kernel) '-mtune' to z16 / arch14 with 23.04 + Bump (kernel) '-mtune' to z16 / arch14 with 23.04 -- 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/1982833 Title: Bump (kernel) '-mtune' to z16 / arch14 with 23.04 Status in Ubuntu on IBM z Systems: New Status in gcc-12 package in Ubuntu: New Status in linux package in Ubuntu: New Bug description: Consider to bump the kernel '-mtune' to z16 (equals arch14), starting with 23.04. Discuss with IBM Z team. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1982833/+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 1994125] Re: [Solved] Gnome desktop freezes after reboot or resume after sleep
** Changed in: linux (Ubuntu) Status: Opinion => 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/1994125 Title: [Solved] Gnome desktop freezes after reboot or resume after sleep Status in linux package in Ubuntu: Confirmed Bug description: After a reboot or resuming from sleep, the desktop appears and is fully functional for about 20 seconds. Then the desktop freezes, the fan spins up but the mouse still moves. Now click around, open programs, execute to switch programs does nothing. The system stays this way for 60 seconds. Then the desktop becomes responsive again and all click and keystrokes executed during this time are executed. After that the system stays responsive and normal. The system log fills up with the following lines (many of them) during this period, pointing at a gnome javascript / message queue issue : ``` Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). ``` ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2224 F wireplumber /dev/snd/controlC1: robert 2224 F wireplumber /dev/snd/seq:robert 2221 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 09:49:23 2022 InstallationDate: Installed on 2022-10-23 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote Control Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1
[Kernel-packages] [Bug 1995052] 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/1995052 Title: 22.10 randomly freezes on Thinkpad T14s Gen3 (Intel) Status in linux package in Ubuntu: Confirmed Bug description: Freshly installed Ubuntu 22.10 have frozen twice in 2 days. I'm not entirely sure but I think in both cases it happened right after executing `sudo -s`. I have the fingerprint reader enabled in `pam-auth-update` which usually works fine though. The system seems to freeze completely, I wasn't even able to reboot it with SysRq sequence. This didn't happen with Fedora 37 which I've been using for few days on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 10:01:17 2022 InstallationDate: Installed on 2022-10-27 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21BR00DURA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2022 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: N3CET47W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BR00DURA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN3CET47W(1.28):bd07/01/2022:br1.28:efr1.10:svnLENOVO:pn21BR00DURA:pvrThinkPadT14sGen3:rvnLENOVO:rn21BR00DURA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BR_BU_Think_FM_ThinkPadT14sGen3: dmi.product.family: ThinkPad T14s Gen 3 dmi.product.name: 21BR00DURA dmi.product.sku: LENOVO_MT_21BR_BU_Think_FM_ThinkPad T14s Gen 3 dmi.product.version: ThinkPad T14s Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995052/+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 1994125] Re: [Solved] Gnome desktop freezes after reboot or resume after sleep
** Summary changed: - Gnome desktop freezes after reboot or resume after sleep + [Solved] Gnome desktop freezes after reboot or resume after sleep ** Changed in: linux (Ubuntu) Status: Confirmed => Opinion -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994125 Title: [Solved] Gnome desktop freezes after reboot or resume after sleep Status in linux package in Ubuntu: Confirmed Bug description: After a reboot or resuming from sleep, the desktop appears and is fully functional for about 20 seconds. Then the desktop freezes, the fan spins up but the mouse still moves. Now click around, open programs, execute to switch programs does nothing. The system stays this way for 60 seconds. Then the desktop becomes responsive again and all click and keystrokes executed during this time are executed. After that the system stays responsive and normal. The system log fills up with the following lines (many of them) during this period, pointing at a gnome javascript / message queue issue : ``` Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). ``` ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2224 F wireplumber /dev/snd/controlC1: robert 2224 F wireplumber /dev/snd/seq:robert 2221 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 09:49:23 2022 InstallationDate: Installed on 2022-10-23 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote Control Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Micro-Star International Co., Ltd. GS65 Stealth Thin 8RF ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=0c55150a-14de-418b-b87f-c46b8f0ef3e7 ro acpi_osi=! "acpi_osi=Windows 2009" quiet splash vt.handoff=7 RelatedPackageVersions:
[Kernel-packages] [Bug 1994125] Re: Gnome desktop freezes after reboot or resume after sleep
The moment the desktop freezes, gnome-shell spins to 100%, the syslog messages from that moment start with a stack trace for `resource:///org/gnome/shell/ui/calendar.js` This points to the configured google account. Removing this cloud account fixed the issue (desktop freeze), in a way this bug is now solved and there should be a new bug created somewhere else. Can anyone point me in the right direction ? ** Attachment added: "gnome-shell log messages" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994125/+attachment/5627446/+files/syslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994125 Title: [Solved] Gnome desktop freezes after reboot or resume after sleep Status in linux package in Ubuntu: Opinion Bug description: After a reboot or resuming from sleep, the desktop appears and is fully functional for about 20 seconds. Then the desktop freezes, the fan spins up but the mouse still moves. Now click around, open programs, execute to switch programs does nothing. The system stays this way for 60 seconds. Then the desktop becomes responsive again and all click and keystrokes executed during this time are executed. After that the system stays responsive and normal. The system log fills up with the following lines (many of them) during this period, pointing at a gnome javascript / message queue issue : ``` Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to call back into JSAPI during the sweeping phase of GC. This is mos t likely caused by not destroying a Clutter actor or Gtk+ widget with ::destroy signals connected, but can also be cau sed by using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked and the JS callback not invoked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending signal was g-signal on GDBusProxy 0x559e48c700d0. Oct 24 21:35:53 msi gnome-shell[2707]: Attempting to run a JS callback during garbage collection. This is most likely caused by destroying a Clutter actor or GTK widget with ::destroy signal connected, or using the destroy(), dispose(), or remove() vfuncs. Because it would crash the application, it has been blocked. Oct 24 21:35:53 msi gnome-shell[2707]: The offending callback was DBusSignalCallback(). ``` ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: robert 2224 F wireplumber /dev/snd/controlC1: robert 2224 F wireplumber /dev/snd/seq:robert 2221 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Oct 25 09:49:23 2022 InstallationDate: Installed on 2022-10-23 (1 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 1038:1122 SteelSeries ApS SteelSeries KLC Bus 001 Device 002: ID 1d57:ad03 Xenta [T3] 2.4GHz and IR Air Mouse Remote Control Bus 001 Device 008: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP) Bus 001 Device 001: ID 1d6b:0002 Linux
[Kernel-packages] [Bug 1995052] Re: 22.10 randomly freezes on Thinkpad T14s Gen3 (Intel)
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995052 Title: 22.10 randomly freezes on Thinkpad T14s Gen3 (Intel) Status in linux package in Ubuntu: New Bug description: Freshly installed Ubuntu 22.10 have frozen twice in 2 days. I'm not entirely sure but I think in both cases it happened right after executing `sudo -s`. I have the fingerprint reader enabled in `pam-auth-update` which usually works fine though. The system seems to freeze completely, I wasn't even able to reboot it with SysRq sequence. This didn't happen with Fedora 37 which I've been using for few days on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 10:01:17 2022 InstallationDate: Installed on 2022-10-27 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21BR00DURA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2022 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: N3CET47W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BR00DURA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN3CET47W(1.28):bd07/01/2022:br1.28:efr1.10:svnLENOVO:pn21BR00DURA:pvrThinkPadT14sGen3:rvnLENOVO:rn21BR00DURA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BR_BU_Think_FM_ThinkPadT14sGen3: dmi.product.family: ThinkPad T14s Gen 3 dmi.product.name: 21BR00DURA dmi.product.sku: LENOVO_MT_21BR_BU_Think_FM_ThinkPad T14s Gen 3 dmi.product.version: ThinkPad T14s Gen 3 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995052/+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 1995052] [NEW] 22.10 randomly freezes on Thinkpad T14s Gen3 (Intel)
You have been subscribed to a public bug: Freshly installed Ubuntu 22.10 have frozen twice in 2 days. I'm not entirely sure but I think in both cases it happened right after executing `sudo -s`. I have the fingerprint reader enabled in `pam-auth- update` which usually works fine though. The system seems to freeze completely, I wasn't even able to reboot it with SysRq sequence. This didn't happen with Fedora 37 which I've been using for few days on the same laptop. ProblemType: Bug DistroRelease: Ubuntu 22.10 Package: linux-image-5.19.0-23-generic 5.19.0-23.24 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.7 Uname: Linux 5.19.0-23-generic x86_64 ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Oct 28 10:01:17 2022 InstallationDate: Installed on 2022-10-27 (0 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: LENOVO 21BR00DURA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.19.0-23-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.19.0-23-generic N/A linux-backports-modules-5.19.0-23-generic N/A linux-firmware 20220923.gitf09bebf3-0ubuntu1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/01/2022 dmi.bios.release: 1.28 dmi.bios.vendor: LENOVO dmi.bios.version: N3CET47W (1.28 ) dmi.board.asset.tag: Not Available dmi.board.name: 21BR00DURA dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.10 dmi.modalias: dmi:bvnLENOVO:bvrN3CET47W(1.28):bd07/01/2022:br1.28:efr1.10:svnLENOVO:pn21BR00DURA:pvrThinkPadT14sGen3:rvnLENOVO:rn21BR00DURA:rvrNotDefined:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_21BR_BU_Think_FM_ThinkPadT14sGen3: dmi.product.family: ThinkPad T14s Gen 3 dmi.product.name: 21BR00DURA dmi.product.sku: LENOVO_MT_21BR_BU_Think_FM_ThinkPad T14s Gen 3 dmi.product.version: ThinkPad T14s Gen 3 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic wayland-session -- 22.10 randomly freezes on Thinkpad T14s Gen3 (Intel) https://bugs.launchpad.net/bugs/1995052 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
Not sure why you were seeing this, if those patches fix the issue, but they have existed in 5.15 for a while from what I can see. -- 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/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+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 1960324] Re: [VROC] Kernel does not contain fixes for iostat for md devices
the 5.15 kernel has contained these patches since Ubuntu-5.15.0-1.1 bladernr@arcadia:~/development/kernels-ubuntu/jammy$ git tag --contains 10764815ff4728d2c57da677cd5d3dd6f446cf5f |head -1 Ubuntu-5.15.0-1.1 bladernr@arcadia:~/development/kernels-ubuntu/jammy$ git tag --contains de3ea66e9d23a34eef5e17f960d6473f78a1c54b |head -1 Ubuntu-5.15.0-1.1 -- 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/1960324 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Status in linux-hwe-5.13 package in Ubuntu: In Progress Status in linux source package in Focal: Invalid Status in linux-hwe-5.13 source package in Focal: In Progress Status in linux source package in Impish: Won't Fix Status in linux-hwe-5.13 source package in Impish: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 (hwe-5.13) does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1960324/+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 1986668] Re: [VROC] Kernel does not contain fixes for iostat for md devices
》Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top 》 on the revert patch: 〉- first commit from series: 10764815ff415728d2c57da677cd5d3dd6f446cf5f 》(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/？id=10) 》- last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b 》(https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id66=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) both of those patches exist in 5.15 since the beginning from Ubuntu-5.15.0-1.1 ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1986668 Title: [VROC] Kernel does not contain fixes for iostat for md devices Status in linux package in Ubuntu: Invalid Bug description: Hello, I noticed that kernel which was used in ubuntu 22.04 does not contain fixes for IO statistics for md devices. IO statistics for md devices were added to kernel 5.10 (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41d2d848e5c09209bdb57ff9c0ca34075e22783d) but then bug for double fault was reported and this patch was reverted by Guoqing Jiang (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=ad3fc798800fb7ca04c1dfc439dba946818048d8). Guoqing Jiang added series of patches which fixes problem and adds IO stats for md devices on top on the revert patch: - first commit from series: 10764815ff4728d2c57da677cd5d3dd6f446cf5f (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=10764815ff4728d2c57da677cd5d3dd6f446cf5f) - last one: de3ea66e9d23a34eef5e17f960d6473f78a1c54b (https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=de3ea66e9d23a34eef5e17f960d6473f78a1c54b) I checked that kernel used in ubuntu 22.04 contains only patch with revert - iostat does not report for md devices (https://kernel.ubuntu.com/git/ubuntu/ubuntu-focal.git/log/?h=hwe-5.13=author=Guoqing+Jiang) Please consider adding series of patches described above. Regards, Kinga Tanska To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986668/+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 1994897] Re: Support BlueField-3 GPIO driver
** Also affects: linux-bluefield (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: linux-bluefield (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-bluefield (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-bluefield (Ubuntu Jammy) Assignee: (unassigned) => Asmaa Mnebhi (asmaam) ** Changed in: linux-bluefield (Ubuntu) Status: New => Invalid -- 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/1994897 Title: Support BlueField-3 GPIO driver Status in linux-bluefield package in Ubuntu: Invalid Status in linux-bluefield source package in Jammy: In Progress Bug description: SRU Justification: [Impact] * Support GPIO driver for BlueField-3 SoCs. [Fix] * Support GPIO driver for BlueField-3 SoCs. * Allows user to alter GPIO value when direction is set to output * Support configuring GPIOs as interrupts for dependent drivers such as pwr-mlxbf and mlxbf-gige [Test Case] * At the moment, this driver can only be tested internally on palladium and via the ARM simulator. * This driver only loaded on BF3 platforms so has no impact on older platforms such as BF2 and BF1. [Regression Potential] * Code will need to be tested once real HW is ready (bringup) [Other] * This driver is in the process of being upstreamed. This code is likely to change depending on feedback we receive from maintainers. But the upstreaming process is long and we need to have this code to be available before BlueField-3 bringup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1994897/+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 1987595] Re: Support Intel IPU6 MIPI camera
Firmware included in experimental firmware linux-firmware/jammy version 20220329.git681281e4-0ubuntu3.6+exp.56. To be SRUed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987595 Title: Support Intel IPU6 MIPI camera Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987595/+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 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL
** Changed in: ubuntu-z-systems 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/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#1989625, which made changes in the s390s IPL/boot area of kernel/arch/random. * The reason seems to be that the bad patch moves the decision about if arch randomness is available to setup.c function setup_randomness(). This code uses a static_key s390_arch_random_available. But in the Canonical kernel the initialization function for the jump labels (where the static keys are based on) jump_label_init() is called in generic start_kernel() wheres in the upstream kernel the init function is called early in setup_arch(). * Reverting this commit from bionic master-next makes bionic systems again bootable. (https://launchpad.net/~fheimes/+archive/ubuntu/test/) [ Test Plan ] * An IBM z14 or LinuxONE II or newer system is needed. * Now install latest bionic on that system - doesn't if it's on LPAR, z/VM or KVM. * After the installation (an the trigger of the post install reboot), the system will not come up. * To test a patched kernel with e4f74400308c can be tested in the following way: * Install 18.04 GA and prevent it from doing any kernel updates. * Means, install in 'island' mode or select in d-i 'Advanced Installation' and explicitly choose '4.15.0-50 generic' to install. * That allows the system to come up and to update the kernel to a modified one. * Then reboot and verify if the system comes up properly. [ Where problems could occur ] * Problems could occur due to the fact that the commit was not cleanly reversible because of minor context changes. * Adjustments that were needed might break other things if not done carefully. * Further commits (applied after e4f74400308c) may still rely on the bad e4f74400308c commit - or even further patches (from upstream stable). * In worst case IPL / boot might get broken, even on hardware older than z14. * If the revert works fine can be easily tested and was tested based on https://launchpad.net/~fheimes/+archive/ubuntu/test/ and the above test plan. [ Other Info ] * Ubuntu 20.04 (focal, using legacy image with virt-install) was tested as well, but is not affected by this issue. __ ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+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
Re: [Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
Hi Arvind,
The Kinetic (5.19) ones went in pretty easily and are likely to be in the
next SRU kernel for 5.19. The Jammy pull (5.15) is another story. In the
time it took for me to apply all 100ish patches and submit my tree, the
kernel team had made a ton of stable updates and when they went to apply my
changes for this, there were numerous conflicts and duplicates. So I'm
going to have to now go through all 100 or so patches and figure out what
needs to be pulled and what isn't cleanly applying otherwise.
Cheers
Jeff
--
Jeff Lane
Engineering Manager
IHV/OEM Alliances and Server Certification
"Entropy isn't what it used to be."
On Tue, Oct 18, 2022 at 6:40 AM Aravind Valloor Mana <
1988...@bugs.launchpad.net> wrote:
> Hi Jeff,
>
> Do you have the kernel version which has these lpfc patches integrated?
> If not, any ETA?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988711
>
> Title:
> Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
>
> Status in linux package in Ubuntu:
> In Progress
> Status in linux source package in Jammy:
> In Progress
> Status in linux source package in Kinetic:
> In Progress
>
> Bug description:
> [IMPACT/Justification]
> There are numerous bug fixes included in the more recent version of lpfc
> That Broadcom has asked to pull into Jammy and Kinetic to better support
> customers in the field who are using the GA kernel and cant or wont move to
> the HWE kernels. These all are limited to the lpfc driver itself, no
> patches to core code are requested.
>
> [FIX]
> A few of these were already landed in Jammy, and all but 6 (ones landed
> in 6.0 upstream) were already in Kinetic.
>
> b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
> 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
> b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
> lpfc_sli_prep_abort_xri()
> ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
> configuration
> ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress
> test
> 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue
> CMF WQE
> 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
> queuecommand after VMID
> 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
> XMIT_ELS_RSP64_CX iocb
> f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
> malformed user input
> 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
> lpfc_nvme_cancel_iocb()
> 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
> 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
> nvme_admin_async_event cmd completion
> ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
> aborted NVMe cmds
> 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in
> PT2PT topology
> b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO
> is aborted
> 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
> starget_to_rport()
> e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
> refactoring
> 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort
> path refactoring
> 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
> lpfc_ct_reject_event()
> a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
> 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
> independent
> ed913cf4a533 scsi: lpfc: Commonize VMID code location
> fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
> a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros
> for NVMe I/O
> e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
> de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
> 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
> parameters
> dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
> lpfc_err_lost_link()
> 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
> rscn_recovery_check()
> 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in
> lpfc_ct_reject_event()
> ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is
> inserted
> b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
> ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
> 84c6f99e3907 scsi: lpfc: Fix element offset in
> __lpfc_sli_release_iocbq_s4()
> 775266207105 scsi: lpfc: Correct BDE DMA address assignment for
> GEN_REQ_WQE
> cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
> c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
> 92bd903da12b scsi: lpfc: Fix additional reference counting in
> lpfc_bsg_rport_els()
> db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
> 646db1a560f4 scsi: lpfc: Fix
[Kernel-packages] [Bug 1995046] [NEW] Realtek 8852c WiFi/BT firmware support
Public bug reported: Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add both FW & config file to get it work with oem-6.0. WiFi: rtw8852c [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003) [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5 BT: rtl8852cu [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1994523 ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Kinetic) Importance: Undecided Status: New ** Tags added: amd oem-priority originate-from-1994523 -- 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/1995046 Title: Realtek 8852c WiFi/BT firmware support Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Kinetic: New Status in linux-firmware source package in Lunar: New Bug description: Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add both FW & config file to get it work with oem-6.0. WiFi: rtw8852c [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003) [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5 BT: rtl8852cu [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995046/+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
