[Kernel-packages] [Bug 1997160] Re: Kernels 128, 131 and 132 won't boot on Pentium 3, attempted to kill the idle task
After adding mitigations=off to the kernel command line, 5.4.0-132-generic boots successfully every time. This workaround satisfies me. I don't need those mitigations on that old PC, and turning them off probably speeds it up a bit. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1997160 Title: Kernels 128, 131 and 132 won't boot on Pentium 3, attempted to kill the idle task Status in linux-hwe-5.4 package in Ubuntu: New Bug description: I am running Ubuntu 18.04.6 LTS on an old PC with a Pentium 3 and Soltek SL-65KVB motherboard. The 5.4.0 generic kernels work fine up to and including release 126. Attempts to boot 128, 131 and 132 quickly lead to a panic every time. The error seems to be "Attempted to kill the idle task". I tried idle=halt and idle=poll kernel command line options without any change. The installation procedure for the kernels seems fine, because I installed kernel 125 after installing the problem kernels, and it worked. I am attaching a photo of what the screen shows when the crash happens. I could try to capture more of that via a serial port if that would be helpful. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-126-generic 5.4.0-126.142~18.04.1 ProcVersionSignature: Ubuntu 5.4.0-126.142~18.04.1-generic 5.4.203 Uname: Linux 5.4.0-126-generic i686 ApportVersion: 2.20.9-0ubuntu7.28 Architecture: i386 CurrentDesktop: XFCE Date: Sat Nov 19 18:01:57 2022 InstallationDate: Installed on 2012-10-07 (3695 days ago) InstallationMedia: Mythbuntu 12.04.1 "Precise Pangolin" - Release i386 (20120818.1) SourcePackage: linux-hwe-5.4 UpgradeStatus: Upgraded to bionic on 2018-04-08 (1686 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-hwe-5.4/+bug/1997160/+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 1997279] Re: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS
** Also affects: linux-hwe-5.15 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-hwe-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Confirmed Status in linux-hwe-5.15 package in Ubuntu: New Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. I tried again using kernel 5.15.0.-53-generic in the recovery mode, and I was able to run a terminal and use apport-collect 1997279. Only, I do not know where this report has been sent to. Unfortunately, I was not able to copy the file content, therefore I could not post it here. If you need information on a specific item from that report, please let me know, and I'll go again and try to get the information for you. Thanks a lot for your help. :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64
[Kernel-packages] [Bug 1997505] [NEW] Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver
Public bug reported:
If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
would like meet this issue.
1020-oem is in security channel. In jammy the unattende-upgrade will
install security fixes by default.
For the I+N platforms, the nvidia driver couldn't be installed for
1020-oem kernel, then user will meet a black screen cause of nvidia
modules couldn't be loaded.
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESMApps:${distro_codename}-apps-security";
"${distro_id}ESM:${distro_codename}-infra-security";
** Affects: oem-priority
Importance: Critical
Assignee: Bin Li (binli)
Status: In Progress
** Affects: nvidia-graphics-drivers-515 (Ubuntu)
Importance: Undecided
Status: New
** Tags: oem-priority originate-from-1995563 sutton
** Description changed:
- If the GMed image used earlier kernel than 1020-oem, then you would like
- meet this issue.
+ If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
+ would like meet this issue.
1020-oem is in security channel. In jammy the unattende-upgrade will
install security fixes by default.
For the I+N platforms, the nvidia driver couldn't be installed for
1020-oem kernel, then user will meet a black screen cause of nvidia
modules couldn't be loaded.
Unattended-Upgrade::Allowed-Origins {
- "${distro_id}:${distro_codename}";
- "${distro_id}:${distro_codename}-security";
- // Extended Security Maintenance; doesn't necessarily exist for
- // every release and this system may not have it installed, but if
- // available, the policy for updates is such that unattended-upgrades
- // should also install from here by default.
- "${distro_id}ESMApps:${distro_codename}-apps-security";
- "${distro_id}ESM:${distro_codename}-infra-security";
+ "${distro_id}:${distro_codename}";
+ "${distro_id}:${distro_codename}-security";
+ // Extended Security Maintenance; doesn't necessarily exist for
+ // every release and this system may not have it installed, but if
+ // available, the policy for updates is such that unattended-upgrades
+ // should also install from here by default.
+ "${distro_id}ESMApps:${distro_codename}-apps-security";
+ "${distro_id}ESM:${distro_codename}-infra-security";
** Tags added: oem-priority originate-from-1995563 sutton
** Changed in: oem-priority
Importance: Undecided => Critical
** Changed in: oem-priority
Assignee: (unassigned) => Bin Li (binli)
** Changed in: oem-priority
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-graphics-drivers-515 in Ubuntu.
https://bugs.launchpad.net/bugs/1997505
Title:
Unattended-Upgrade will upgrade 1020-oem kernel without nvidia-driver
Status in OEM Priority Project:
In Progress
Status in nvidia-graphics-drivers-515 package in Ubuntu:
New
Bug description:
If the GMed image used earlier kernel than 5.17.0-1020-oem, then you
would like meet this issue.
1020-oem is in security channel. In jammy the unattende-upgrade will
install security fixes by default.
For the I+N platforms, the nvidia driver couldn't be installed for
1020-oem kernel, then user will meet a black screen cause of nvidia
modules couldn't be loaded.
Unattended-Upgrade::Allowed-Origins {
"${distro_id}:${distro_codename}";
"${distro_id}:${distro_codename}-security";
// Extended Security Maintenance; doesn't necessarily exist for
// every release and this system may not have it installed, but if
// available, the policy for updates is such that unattended-upgrades
// should also install from here by default.
"${distro_id}ESMApps:${distro_codename}-apps-security";
"${distro_id}ESM:${distro_codename}-infra-security";
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/1997505/+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 1979173] Re: Enable WiFi hotspot feature for MediaTek MT7921
this still doesn't work for me on jammy with kernel 5.15.0-52-generic on this hardware: https://linux-hardware.org/?probe=029cddbcd6 the module loads, hostapd starts but clients don't see the ssid, not even with minimal hostapd config on kernel wiki (https://wireless.wiki.kernel.org/en/users/documentation/hostapd) $ sudo lspci -d 14c3:7961 - 03:00.0 Network controller: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter DeviceName: Onboard - RTK Ethernet Subsystem: MEDIATEK Corp. MT7921 802.11ax PCI Express Wireless Network Adapter Physical Slot: 4 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+ Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- SERR- Capabilities: [108 v1] Latency Tolerance Reporting Max snoop latency: 3145728ns Max no snoop latency: 3145728ns Capabilities: [110 v1] L1 PM Substates L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+ PortCommonModeRestoreTime=3us PortTPowerOnTime=28us L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ T_CommonMode=0us LTR1.2_Threshold=65536ns L1SubCtl2: T_PwrOn=28us Capabilities: [200 v2] Advanced Error Reporting UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol- UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP+ ECRC- UnsupReq- ACSViol- CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr- CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+ AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn- MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap- HeaderLog: Kernel driver in use: mt7921e Kernel modules: mt7921e $ cat /var/tmp/hostapd-minimal.conf interface=wlan3 driver=nl80211 ssid=test channel=1 logger_stdout_level=0 $ sudo hostapd -tKdd /var/tmp/hostapd-minimal.conf 1669162887.018252: random: getrandom() support available 1669162887.018311: Configuration file: /var/tmp/hostapd-minimal.conf 1669162887.019151: nl80211: TDLS supported 1669162887.019164: nl80211: TDLS external setup 1669162887.019170: nl80211: Supported cipher 00-0f-ac:1 1669162887.019176: nl80211: Supported cipher 00-0f-ac:5 1669162887.019180: nl80211: Supported cipher 00-0f-ac:2 1669162887.019186: nl80211: Supported cipher 00-0f-ac:4 1669162887.019199: nl80211: Supported cipher 00-0f-ac:10 1669162887.019207: nl80211: Supported cipher 00-0f-ac:8 1669162887.019212: nl80211: Supported cipher 00-0f-ac:9 1669162887.019220: nl80211: Supported cipher 00-0f-ac:6 1669162887.019231: nl80211: Supported cipher 00-0f-ac:13 1669162887.019237: nl80211: Supported cipher 00-0f-ac:11 1669162887.019247: nl80211: Supported cipher 00-0f-ac:12 1669162887.019280: nl80211: Using driver-based off-channel TX 1669162887.019302: nl80211: Driver-advertised extended capabilities (default) - hexdump(len=8): 00 00 00 00 00 00 00 40 1669162887.019316: nl80211: Driver-advertised extended capabilities mask (default) - hexdump(len=8): 00 00 00 00 00 00 00 40 1669162887.019339: nl80211: key_mgmt=0x1ff0f enc=0xfef auth=0x7 flags=0x4003d10d35bd0e0 rrm_flags=0x30 probe_resp_offloads=0x0 max_stations=0 max_remain_on_chan=5000 max_scan_ssids=4 1669162887.019356: nl80211: interface wlan3 in phy phy3 1669162887.019393: nl80211: Set mode ifindex 17 iftype 3 (AP) 1669162887.019438: nl80211: Failed to set interface 17 to mode 3: -16 (Device or resource busy) 1669162887.019476: nl80211: Try mode change after setting interface down 1669162887.041456: nl80211: Set mode ifindex 17 iftype 3 (AP) 1669162887.041656: nl80211: Mode change succeeded while interface is down 1669162887.089266: nl80211: Setup AP(wlan3) - device_ap_sme=0 use_monitor=0 1669162887.089343: nl80211: Subscribe to mgmt frames with AP handle 0x55d6960f7b80 1669162887.089357: nl80211: Register frame type=0xb0 (WLAN_FC_STYPE_AUTH) nl_handle=0x55d6960f7b80 match= multicast=0 1669162887.089413: nl80211: Register frame type=0x0 (WLAN_FC_STYPE_ASSOC_REQ) nl_handle=0x55d6960f7b80 match= multicast=0 1669162887.089445: nl80211: Register frame type=0x20 (WLAN_FC_STYPE_REASSOC_REQ) nl_handle=0x55d6960f7b80 match= multicast=0 1669162887.089524: nl80211: Register frame type=0xa0 (WLAN_FC_STYPE_DISASSOC) nl_handle=0x55d6960f7b80 match= multicast=0 1669162887.089595: nl80211: Register frame type=0xc0 (WLAN_FC_STYPE_DEAUTH) nl_handle=0x55d6960f7b80 match= multicast=0 1669162887.089688: nl80211: Register frame type=0x40 (WLAN_FC_STYPE_PROBE_REQ)
[Kernel-packages] [Bug 1997279] Re: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS
** Description changed: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. + + I tried again using kernel 5.15.0.-53-generic in the recovery mode, and I was able to run a terminal and use apport-collect 1997279. Only, I do not know where this report has been sent to. Unfortunately, I was not able to copy the file content, therefore I could not post it here. + If you need information on a specific item from that report, please let me know, and I'll go again and try to get the information for you. Thanks a lot for your help. :-) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: cord 2837 F pulseaudio - /dev/snd/controlC2: cord 2837 F pulseaudio - /dev/snd/controlC0: cord 2837 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: cord 2837 F pulseaudio + /dev/snd/controlC2: cord 2837 F pulseaudio + /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: - lono wireless extensions. - - enp5s0no wireless extensions. + lono wireless extensions. + + enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: - linux-restricted-modules-5.15.0-53-generic N/A - linux-backports-modules-5.15.0-53-generic N/A - linux-firmware 20220329.git681281e4-0ubuntu3.6 + linux-restricted-modules-5.15.0-53-generic N/A +
[Kernel-packages] [Bug 1997279] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632197/+files/acpidump.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/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632196/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632191/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1997279] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632190/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632193/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632194/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632192/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632187/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632195/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632188/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632186/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632189/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632185/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632184/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632183/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string
[Kernel-packages] [Bug 1997279] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632182/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 2837 F pulseaudio /dev/snd/controlC2: cord 2837 F pulseaudio /dev/snd/controlC0: cord 2837 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 RelatedPackageVersions: linux-restricted-modules-5.15.0-53-generic N/A linux-backports-modules-5.15.0-53-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Tags: jammy Uname: Linux 5.15.0-53-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type:
[Kernel-packages] [Bug 1997279] Re: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS
apport information ** Description changed: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: cord 2837 F pulseaudio + /dev/snd/controlC2: cord 2837 F pulseaudio + /dev/snd/controlC0: cord 2837 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2019-06-02 (1269 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + IwConfig: + lono wireless extensions. + + enp5s0no wireless extensions. + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 EFI VGA + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-53-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro recovery nomodeset dis_ucode_ldr + ProcVersionSignature: Ubuntu 5.15.0-53.59-generic 5.15.64 + RelatedPackageVersions: + linux-restricted-modules-5.15.0-53-generic N/A + linux-backports-modules-5.15.0-53-generic N/A + linux-firmware 20220329.git681281e4-0ubuntu3.6 + RfKill: + + Tags: jammy + Uname: Linux 5.15.0-53-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/25/2019 + dmi.bios.release: 5.13 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4801 + dmi.board.asset.tag: Default string + dmi.board.name: PRIME A320M-K + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product
[Kernel-packages] [Bug 1997279] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632175/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632176/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632177/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632178/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632173/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632179/+files/acpidump.txt ** Description changed: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) - --- + + The following output has been produced using kernel 5.15.0-52-generic, as + I don't get access to terminal when using kernel 5.15.0.-53-generic. + + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC1: cord 1601 F pulseaudio - /dev/snd/controlC2: cord 1601 F pulseaudio - /dev/snd/controlC0: cord 1601 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC1: cord 1601 F pulseaudio + /dev/snd/controlC2: cord 1601 F pulseaudio + /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: - lono wireless extensions. - - enp5s0no wireless extensions. + lono wireless extensions. + + enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=de_DE.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 + 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.6 RfKill: - + Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer -- 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/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1997279] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632174/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632168/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632172/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632171/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632169/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632170/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632167/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632166/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632165/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632164/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/25/2019 dmi.bios.release: 5.13 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 4801 dmi.board.asset.tag: Default string dmi.board.name: PRIME A320M-K dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997279/+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 1997279] Re: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS
apport information ** Tags added: apport-collected jammy wayland-session ** Description changed: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: cord 1601 F pulseaudio + /dev/snd/controlC2: cord 1601 F pulseaudio + /dev/snd/controlC0: cord 1601 F pulseaudio + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2019-06-02 (1269 days ago) + InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) + IwConfig: + lono wireless extensions. + + enp5s0no wireless extensions. + MachineType: System manufacturer System Product Name + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=de_DE.UTF-8 + SHELL=/bin/bash + ProcFB: 0 amdgpudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash + ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 + 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.6 + RfKill: + + Tags: jammy wayland-session + Uname: Linux 5.15.0-52-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) + UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 04/25/2019 + dmi.bios.release: 5.13 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: 4801 + dmi.board.asset.tag: Default string + dmi.board.name: PRIME A320M-K + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: Rev X.0x + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 3 + dmi.chassis.vendor: Default string + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr4801:bd04/25/2019:br5.13:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnPRIMEA320M-K:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring:skuSKU: + dmi.product.family: To be filled by O.E.M. + dmi.product.name: System Product Name + dmi.product.sku: SKU + dmi.product.version: System Version + dmi.sys.vendor: System manufacturer ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1997279/+attachment/5632163/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997279 Title: Desktop won't open after using 5.15.0-53-generic ubuntu 22.04.1 LTS Status in linux package in Ubuntu: Incomplete Bug description: I use ubuntu 22.04.1 LTS with AMD Ryzen 3 2200G with Radeon Vega on my desktop PC. When using the new kernel 5.15.0-53-generic, I receive a black monitor right after booting the system (=ubuntu just won't start). (Kernel 5.15.0-52-generic used to work and still works fine.) The following output has been produced using kernel 5.15.0-52-generic, as I don't get access to terminal when using kernel 5.15.0.-53-generic. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cord 1601 F pulseaudio /dev/snd/controlC2: cord 1601 F pulseaudio /dev/snd/controlC0: cord 1601 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2019-06-02 (1269 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: lono wireless extensions. enp5s0no wireless extensions. MachineType: System manufacturer System Product Name Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=7852e422-5024-4002-a6fc-45d17fbd9226 ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 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.6 RfKill: Tags: jammy wayland-session Uname: Linux 5.15.0-52-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-08-18 (96 days ago) UserGroups: adm cdrom dip
[Kernel-packages] [Bug 1997488] Re: NFS 4.1 mounts on AKS are reusing the same source port when a reconnect needs to happen
Fix patch: commit e6237b6feb37582fbd6bd7a8336d1256a6b4b4f9 ("NFSv4.1:
Don't rebind to the same source port when reconnecting to the server")
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu)
Status: New => Fix Released
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Status: New => In Progress
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Tim Gardner (timg-tpi)
--
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/1997488
Title:
NFS 4.1 mounts on AKS are reusing the same source port when a
reconnect needs to happen
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Focal:
In Progress
Bug description:
SRU Justification
[Impact]
NFSv2, v3 and NFSv4 servers often have duplicate replay caches that look
at the source port when deciding whether or not an RPC call is a replay
of a previous call. This requires clients to perform strange TCP gymnastics
in order to ensure that when they reconnect to the server, they bind
to the same source port.
NFSv4.1 and NFSv4.2 have sessions that provide proper replay semantics,
that do not look at the source port of the connection. This patch therefore
ensures they can ignore the rebind requirement.
[Where things could go wrong]
NFS reconnects may erroneously fail.
[Other Info]
SF: #00345839
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997488/+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 1997488] [NEW] NFS 4.1 mounts on AKS are reusing the same source port when a reconnect needs to happen
Public bug reported: SRU Justification [Impact] NFSv2, v3 and NFSv4 servers often have duplicate replay caches that look at the source port when deciding whether or not an RPC call is a replay of a previous call. This requires clients to perform strange TCP gymnastics in order to ensure that when they reconnect to the server, they bind to the same source port. NFSv4.1 and NFSv4.2 have sessions that provide proper replay semantics, that do not look at the source port of the connection. This patch therefore ensures they can ignore the rebind requirement. [Where things could go wrong] NFS reconnects may erroneously fail. [Other Info] SF: #00345839 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1997488 Title: NFS 4.1 mounts on AKS are reusing the same source port when a reconnect needs to happen Status in linux package in Ubuntu: New Bug description: SRU Justification [Impact] NFSv2, v3 and NFSv4 servers often have duplicate replay caches that look at the source port when deciding whether or not an RPC call is a replay of a previous call. This requires clients to perform strange TCP gymnastics in order to ensure that when they reconnect to the server, they bind to the same source port. NFSv4.1 and NFSv4.2 have sessions that provide proper replay semantics, that do not look at the source port of the connection. This patch therefore ensures they can ignore the rebind requirement. [Where things could go wrong] NFS reconnects may erroneously fail. [Other Info] SF: #00345839 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997488/+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 1995491] Re: [UBUNTU 20.04] "kauditd: hold queue overflow " and node failure
Hi Boris et al. We are unable to retrieve the Kernel Dump from ECuRep. Please, whenever possible, send it over to us through sftp on files.support.canonical.com. Let us know what the filename is, also, please. Thanks! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995491 Title: [UBUNTU 20.04] "kauditd: hold queue overflow " and node failure Status in linux package in Ubuntu: New Bug description: ---Problem Description--- This is an issue being reported on a node that went down. Had a chance to look at the currently available logs, which doesn't provide me sufficient indication of a potential issue beyond an issue w.r.t "kauditd: hold queue overflow " (~790 number of messages ) Would be great to have your review on the dump file to see , whether there is anything significant that caused the node down. Contact Information = Kishore Kumar G/kishore.pil...@in.ibm.com ---uname output--- I will come back with the uname output , as I couldn't get that info from the logs Machine Type = z15 -GT2 lpar ---Debugger--- A debugger is not configured Stack trace output: no Oops output: no System Dump Location: [18:in07100f@ecurep]:/ecurep/toibm/linux $ ls 2022_09_26_18_18_51_tor2-qz1-sr1-rk085-s03_192.168.85.7_5.4.0-121-generic_dumpfile 2022_09_26_18_18_51_tor2-qz1-sr1-rk085-s03_192.168.85.7_5.4.0-121-generic_locDmsg *Additional Instructions for Kishore Kumar G/kishore.pil...@in.ibm.com: -Attach sysctl -a output output to the bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995491/+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 1996117] Re: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning
** Changed in: linux-azure (Ubuntu Jammy) Status: In Progress => Fix Committed ** Changed in: linux-azure (Ubuntu Kinetic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1996117 Title: [Azure][Arm64] Unable to detect all VF nics / Failing provisioning Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Status in linux-azure source package in Kinetic: Fix Committed Bug description: SRU Justification [Impact] SRIOV tests fail where sometimes 0 and other times only 6 VF devices are detected instead of 8. This is using the 5.19 Edge kernel. Example failure from LISA test run - Sriov.verify_sriov_provision_with_max_nics_reboot: FAILED failed. AssertionError: [VF count inside VM is 6,actual sriov nic count is 8] Expected <6> to be equal to <8>, but was not. Microsoft has requested the inclusion of [1], now in linux-next. 1 - https://git.kernel.org/pub/scm/linux/kernel/git/hyperv/linux.git/commit/?h=hyperv- fixes=f134588e4cebaecdeafbbb19317517ea9b729aa9 [Test Plan] Microsoft tested [Where things could go wrong] VNICs could go undetected. [Other Info] SF: #00346751 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996117/+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 1971656] Re: rtw89_pci failure on Lenovo P14s with Ubuntu 22.04
Same issue here. I have a Lenovo legion s7 slim. Have been having this problem for the past two weeks I think. Ubuntu 22. -- 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 1997472] 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/1997472 Title: Touchpad problem detecting working area on Dell XPS Status in linux package in Ubuntu: Confirmed Bug description: I am using a new Dell XPS 17 with the latest Ubuntu (22.10). One bug I could see is the touchpad sensitivity. Sometimes, randomly, the upper part of the touchpad is the only one working, most of its surface does not work. If the movement starts in the working area, then you can use the whole touchpad until you lift the finger. After a while it seems to recover by itself. My feeling is that this is somehow related to the sensitivity of the touchpad (some instability) or related to the system that disables the touchpad while writing (again, some buggy detection). While writing this text I experienced the bug twice, for instance, intermittently. 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: florin 1581 F pipewire florin 1584 F wireplumber /dev/snd/controlC0: florin 1584 F wireplumber /dev/snd/seq:florin 1581 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 22 17:25:52 2022 InstallationDate: Installed on 2022-10-24 (29 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Dell Inc. XPS 17 9720 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=99833626-9acf-4145-9fee-2cbbe47e4d33 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: 09/08/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0KNF8J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/08/2022:br1.11:svnDellInc.:pnXPS179720:pvr:rvnDellInc.:rn0KNF8J:rvrA00:cvnDellInc.:ct10:cvr:sku0AFF: dmi.product.family: XPS dmi.product.name: XPS 17 9720 dmi.product.sku: 0AFF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997472/+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 1993665] Re: Update the 470-server NVIDIA driver
Re-running through the testing on our DGX2 now passes for both DKMS and LRM. I will need to retry the testing on A100 again and see if I missed something like the fabricmanager not being ready yet. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1993665 Title: Update the 470-server NVIDIA driver Status in fabric-manager-470 package in Ubuntu: In Progress Status in libnvidia-nscq-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in fabric-manager-470 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in fabric-manager-470 source package in Kinetic: In Progress Status in libnvidia-nscq-470 source package in Kinetic: In Progress Status in nvidia-graphics-drivers-470-server source package in Kinetic: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/1993665/+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 1997472] Re: Touchpad problem detecting working area on Dell XPS
In the past I have had multiple problems with the touchpad on the old laptops (Toshiba) and hoped these will disappear with a new one, but some seem to still be here. I am willing to do some deep debugging if someone shows me step by step (I am a simple user) how to do it. Or even allow someone to connect remotely if needed, but I really wish Linux & Ubuntu have a 100% reliable touchpad function. -- 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/1997472 Title: Touchpad problem detecting working area on Dell XPS Status in linux package in Ubuntu: New Bug description: I am using a new Dell XPS 17 with the latest Ubuntu (22.10). One bug I could see is the touchpad sensitivity. Sometimes, randomly, the upper part of the touchpad is the only one working, most of its surface does not work. If the movement starts in the working area, then you can use the whole touchpad until you lift the finger. After a while it seems to recover by itself. My feeling is that this is somehow related to the sensitivity of the touchpad (some instability) or related to the system that disables the touchpad while writing (again, some buggy detection). While writing this text I experienced the bug twice, for instance, intermittently. 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: florin 1581 F pipewire florin 1584 F wireplumber /dev/snd/controlC0: florin 1584 F wireplumber /dev/snd/seq:florin 1581 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 22 17:25:52 2022 InstallationDate: Installed on 2022-10-24 (29 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Dell Inc. XPS 17 9720 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=99833626-9acf-4145-9fee-2cbbe47e4d33 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: 09/08/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0KNF8J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/08/2022:br1.11:svnDellInc.:pnXPS179720:pvr:rvnDellInc.:rn0KNF8J:rvrA00:cvnDellInc.:ct10:cvr:sku0AFF: dmi.product.family: XPS dmi.product.name: XPS 17 9720 dmi.product.sku: 0AFF dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997472/+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 1997472] [NEW] Touchpad problem detecting working area on Dell XPS
Public bug reported: I am using a new Dell XPS 17 with the latest Ubuntu (22.10). One bug I could see is the touchpad sensitivity. Sometimes, randomly, the upper part of the touchpad is the only one working, most of its surface does not work. If the movement starts in the working area, then you can use the whole touchpad until you lift the finger. After a while it seems to recover by itself. My feeling is that this is somehow related to the sensitivity of the touchpad (some instability) or related to the system that disables the touchpad while writing (again, some buggy detection). While writing this text I experienced the bug twice, for instance, intermittently. 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: florin 1581 F pipewire florin 1584 F wireplumber /dev/snd/controlC0: florin 1584 F wireplumber /dev/snd/seq:florin 1581 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 22 17:25:52 2022 InstallationDate: Installed on 2022-10-24 (29 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Dell Inc. XPS 17 9720 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=99833626-9acf-4145-9fee-2cbbe47e4d33 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: 09/08/2022 dmi.bios.release: 1.11 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.0 dmi.board.name: 0KNF8J dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.0:bd09/08/2022:br1.11:svnDellInc.:pnXPS179720:pvr:rvnDellInc.:rn0KNF8J:rvrA00:cvnDellInc.:ct10:cvr:sku0AFF: dmi.product.family: XPS dmi.product.name: XPS 17 9720 dmi.product.sku: 0AFF dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug kinetic ** Attachment added: "filming the touchpad problems on dell xps 17 Ubuntu 22.10" https://bugs.launchpad.net/bugs/1997472/+attachment/5632133/+files/touchpad-problem-dell-xps-20221122_172423.mp4 -- 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/1997472 Title: Touchpad problem detecting working area on Dell XPS Status in linux package in Ubuntu: New Bug description: I am using a new Dell XPS 17 with the latest Ubuntu (22.10). One bug I could see is the touchpad sensitivity. Sometimes, randomly, the upper part of the touchpad is the only one working, most of its surface does not work. If the movement starts in the working area, then you can use the whole touchpad until you lift the finger. After a while it seems to recover by itself. My feeling is that this is somehow related to the sensitivity of the touchpad (some instability) or related to the system that disables the touchpad while writing (again, some buggy detection). While writing this text I experienced the bug twice, for instance, intermittently. 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: florin 1581 F pipewire florin 1584 F wireplumber /dev/snd/controlC0: florin 1584 F wireplumber /dev/snd/seq:florin 1581 F pipewire CRDA: N/A CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Nov 22 17:25:52 2022 InstallationDate: Installed on 2022-10-24 (29 days ago) InstallationMedia: Ubuntu 22.10 "Kinetic Kudu" - Release amd64 (20221020) MachineType: Dell Inc. XPS 17 9720 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.19.0-23-generic root=UUID=99833626-9acf-4145-9fee-2cbbe47e4d33 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
[Kernel-packages] [Bug 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
** Tags added: patch -- 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/1931715 Title: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices" Status in linux package in Ubuntu: Confirmed Bug description: Laptop model: Lenovo Ideapad S145 82DJ0001BR Manufacturer of the Touchpad: Elan, Synaptics When the symptom first appeared: At the time I installed Ubuntu on my notebook (dual-boot) - it works fine on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-55-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jun 11 11:58:39 2021 InstallationDate: Installed on 2021-06-09 (1 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-hwe-5.8 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+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 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
** Tags added: patch
--
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/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
[Fix]
It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
[Test]
Verified by the bug reporter.
[Where problems could occur]
The 6 commits are all clean cherry-picked, and the sixth commit reverts the
third commit which are the 2 commits that do real functional changes.
a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for
E820 regions\"")
4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
The fourth and and fifth commits introduce a new quirk to ignore E820
reserved regions and the quirk only affects the listed machines.
Drivers that operates E820 table may fail if we ignore the E820 regions, but
it should have no impact on the listed consumer PCs.
===
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
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=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
dmi.product.version: V1.00
dmi.sys.vendor: Acer
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+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 1932069] Re: Touchpad not working at all
** Tags added: patch -- 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/1932069 Title: Touchpad not working at all Status in linux package in Ubuntu: Confirmed Bug description: Notebook Lenovo BS-145 15 HL ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: cesar 1314 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Jun 15 16:36:11 2021 InstallationDate: Installed on 2021-06-15 (0 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera Bus 001 Device 005: ID 10c4:8105 Silicon Labs USB OPTICAL MOUSE Bus 001 Device 004: 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: LENOVO 82HB ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic root=UUID=2ff10f98-8e1f-42ac-98b7-284459b8d285 ro quiet splash vt.handoff=7 RebootRequiredPkgs: gnome-shell RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/23/2020 dmi.bios.release: 1.51 dmi.bios.vendor: LENOVO dmi.bios.version: DKCN51WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo BS145-15IIL dmi.ec.firmware.release: 1.51 dmi.modalias: dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82HB:pvrLenovoBS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoBS145-15IIL: dmi.product.family: BS145-15IIL dmi.product.name: 82HB dmi.product.sku: LENOVO_MT_82HB_BU_idea_FM_BS145-15IIL dmi.product.version: Lenovo BS145-15IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932069/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
@Craig The limit in Debian is actually much lower than in Ubuntu even,
but fixing it there is even harder as that misses a lot more patches.
--
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: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
[Kernel-packages] [Bug 1884232] Re: touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product Name, and Board Name. This isn't
an ideal solution because there are likely other systems we don't know
about that need a similar fix.
The patch I'm attaching here is an experimental idea to work around this
issue without the maintenance burden of the quirks.
If anybody would be willing to test this patch, I would be very
grateful. To test it, apply this patch to your kernel, boot with
"pci=use_e820 efi=debug", and collect the dmesg log.
** Attachment added: "experimental patch to remove EfiMemoryMappedIO"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+attachment/5632129/+files/remove-mmio
--
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/1884232
Title:
touchpad and touchscreen doesn't work at all on ACER Spin 5
(SP513-54N)
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Focal:
Won't Fix
Status in linux source package in Jammy:
Fix Released
Bug description:
[Impact]
E820 reserved retire memory window, and make other hot-added devices unable
to get the required memory window.
[Fix]
It only can be fixed by a list of quirk to mark those machines out, and
requires below commits from v5.19-rc1 and v5.19-rc3
a2b36ffbf5b6 x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820
regions"
d341838d776a x86/PCI: Disable E820 reserved region clipping via quirks
fa6dae5d8208 x86/PCI: Add kernel cmdline options to use/ignore E820 reserved
regions
4c5e242d3e93 x86/PCI: Clip only host bridge windows for E820 regions
31bf0f433325 x86: Log resource clipping for E820 regions
93d256cd3c1e x86/PCI: Eliminate remove_e820_regions() common subexpressions
[Test]
Verified by the bug reporter.
[Where problems could occur]
The 6 commits are all clean cherry-picked, and the sixth commit reverts the
third commit which are the 2 commits that do real functional changes.
a2b36ffbf5b6 ("x86/PCI: Revert \"x86/PCI: Clip only host bridge windows for
E820 regions\"")
4c5e242d3e93 ("x86/PCI: Clip only host bridge windows for E820 regions")
The fourth and and fifth commits introduce a new quirk to ignore E820
reserved regions and the quirk only affects the listed machines.
Drivers that operates E820 table may fail if we ignore the E820 regions, but
it should have no impact on the listed consumer PCs.
===
Touchpad is not working at all on ACER Spin 5 SP513-54N.
According to
https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29
I am creating this kernel bug issue.
There are more issues, too, like touchscreen not working and Ubuntu
not installable - see here if interrested
https://askubuntu.com/questions/1251719/
I would like to run Ubuntu on this machine and I am willing to help
with any debug or kernel tweaking... Please let me know.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-26-generic 5.4.0-26.30
ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30
Uname: Linux 5.4.0-26-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: ubuntu 4195 F pulseaudio
CasperMD5CheckResult: skip
CasperVersion: 1.445
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 19 10:44:58 2020
LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: Acer Spin SP513-54N
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=/casper/vmlinuz
file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash ---
RelatedPackageVersions:
linux-restricted-modules-5.4.0-26-generic N/A
linux-backports-modules-5.4.0-26-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 02/21/2020
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: V1.00
dmi.board.name: Caboom_IL
dmi.board.vendor: IL
dmi.board.version: V1.00
dmi.chassis.type: 31
dmi.chassis.vendor: Acer
dmi.chassis.version: V1.00
dmi.modalias:
dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00:
dmi.product.family: Spin 5
dmi.product.name: Spin SP513-54N
dmi.product.sku:
[Kernel-packages] [Bug 1921649] Re: 'Ideapad S145 Touchpad' not working at all. Not even detected after a fresh Ubuntu 20.10 install.
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product Name, and Board Name. This isn't an
ideal solution because there are likely other systems we don't know
about that need a similar fix.
The patch I'm attaching here is an experimental idea to work around this
issue without the maintenance burden of the quirks.
If anybody would be willing to test this patch, I would be very
grateful. To test it, apply this patch to your kernel, boot with
"pci=use_e820 efi=debug", and collect the dmesg log.
** Attachment added: "experimental patch to remove EfiMemoryMappedIO"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921649/+attachment/5632130/+files/remove-mmio
--
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/1921649
Title:
'Ideapad S145 Touchpad' not working at all. Not even detected after a
fresh Ubuntu 20.10 install.
Status in linux package in Ubuntu:
Expired
Bug description:
Just installed Ubuntu 20.10 in a new Lenovo Ideapad S145 82DJBR
and touchpad does not work. It's not detected as seen here:
$ xinput list
⎡ Virtual core pointerid=2[master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4[slave pointer
(2)]
⎣ Virtual core keyboard id=3[master keyboard (2)]
↳ Virtual core XTEST keyboard id=5[slave
keyboard (3)]
↳ Power Buttonid=6[slave
keyboard (3)]
↳ Video Bus id=7[slave
keyboard (3)]
↳ Power Buttonid=8[slave
keyboard (3)]
↳ Integrated Camera: Integrated C id=10 [slave
keyboard (3)]
↳ Ideapad extra buttons id=11 [slave
keyboard (3)]
↳ AT Translated Set 2 keyboardid=12 [slave
keyboard (3)]
ProblemType: Bug
DistroRelease: Ubuntu 20.10
Package: linux-image-5.8.0-48-generic 5.8.0-48.54
ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18
Uname: Linux 5.8.0-48-generic x86_64
ApportVersion: 2.20.11-0ubuntu50.5
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: netto 1359 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Sun Mar 28 17:30:14 2021
InstallationDate: Installed on 2021-03-20 (7 days ago)
InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
Bus 001 Device 002: ID 0461:4d51 Primax Electronics, Ltd 0Y357C PMX-MMOCZUL
(B) [Dell Laser Mouse]
Bus 001 Device 004: 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: LENOVO 82DJ
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic
root=UUID=8f45bc43-cd22-4cfa-83ee-4cb09fd58f0c ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.8.0-48-generic N/A
linux-backports-modules-5.8.0-48-generic N/A
linux-firmware1.190.3
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/22/2020
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: DKCN48WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40688 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo IdeaPad S145-15IIL
dmi.ec.firmware.release: 1.48
dmi.modalias:
dmi:bvnLENOVO:bvrDKCN48WW:bd07/22/2020:br1.48:efr1.48:svnLENOVO:pn82DJ:pvrLenovoIdeaPadS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct10:cvrLenovoIdeaPadS145-15IIL:
dmi.product.family: IdeaPad S145-15IIL
dmi.product.name: 82DJ
dmi.product.sku: LENOVO_MT_82DJ_BU_idea_FM_IdeaPad S145-15IIL
dmi.product.version: Lenovo IdeaPad S145-15IIL
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921649/+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 1931715] Re: [Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not appear on "cat /proc/bus/input/devices"
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product Name, and Board Name. This isn't an
ideal solution because there are likely other systems we don't know
about that need a similar fix.
The patch I'm attaching here is an experimental idea to work around this
issue without the maintenance burden of the quirks.
If anybody would be willing to test this patch, I would be very
grateful. To test it, apply this patch to your kernel, boot with
"pci=use_e820 efi=debug", and collect the dmesg log.
** Attachment added: "experimental patch to remove EfiMemoryMappedIO"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+attachment/5632131/+files/remove-mmio
--
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/1931715
Title:
[Lenovo Ideapad S145 82DJ0001BR] touchpad not working - does not
appear on "cat /proc/bus/input/devices"
Status in linux package in Ubuntu:
Confirmed
Bug description:
Laptop model: Lenovo Ideapad S145 82DJ0001BR
Manufacturer of the Touchpad: Elan, Synaptics
When the symptom first appeared: At the time I installed Ubuntu on my
notebook (dual-boot) - it works fine on Windows.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.8.0-55-generic 5.8.0-55.62~20.04.1
ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-generic 5.8.18
Uname: Linux 5.8.0-55-generic x86_64
ApportVersion: 2.20.11-0ubuntu27.18
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Fri Jun 11 11:58:39 2021
InstallationDate: Installed on 2021-06-09 (1 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64
(20210209.1)
SourcePackage: linux-signed-hwe-5.8
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1931715/+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 1932069] Re: Touchpad not working at all
This is likely a duplicate of https://bugs.launchpad.net/bugs/1878279
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product Name, and Board Name. This isn't an
ideal solution because there are likely other systems we don't know
about that need a similar fix.
The patch I'm attaching here is an experimental idea to work around this
issue without the maintenance burden of the quirks.
If anybody would be willing to test this patch, I would be very
grateful. To test it, apply this patch to your kernel, boot with
"pci=use_e820 efi=debug", and collect the dmesg log.
** Attachment added: "experimental patch to remove EfiMemoryMappedIO"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932069/+attachment/5632132/+files/remove-mmio
--
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/1932069
Title:
Touchpad not working at all
Status in linux package in Ubuntu:
Confirmed
Bug description:
Notebook Lenovo BS-145 15 HL
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: linux-image-5.11.0-18-generic 5.11.0-18.19
ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17
Uname: Linux 5.11.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu65.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: cesar 1314 F pulseaudio
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Tue Jun 15 16:36:11 2021
InstallationDate: Installed on 2021-06-15 (0 days ago)
InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 174f:1176 Syntek Integrated Camera
Bus 001 Device 005: ID 10c4:8105 Silicon Labs USB OPTICAL MOUSE
Bus 001 Device 004: 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: LENOVO 82HB
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.11.0-18-generic
root=UUID=2ff10f98-8e1f-42ac-98b7-284459b8d285 ro quiet splash vt.handoff=7
RebootRequiredPkgs: gnome-shell
RelatedPackageVersions:
linux-restricted-modules-5.11.0-18-generic N/A
linux-backports-modules-5.11.0-18-generic N/A
linux-firmware 1.197.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/23/2020
dmi.bios.release: 1.51
dmi.bios.vendor: LENOVO
dmi.bios.version: DKCN51WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo BS145-15IIL
dmi.ec.firmware.release: 1.51
dmi.modalias:
dmi:bvnLENOVO:bvrDKCN51WW:bd12/23/2020:br1.51:efr1.51:svnLENOVO:pn82HB:pvrLenovoBS145-15IIL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoBS145-15IIL:
dmi.product.family: BS145-15IIL
dmi.product.name: 82HB
dmi.product.sku: LENOVO_MT_82HB_BU_idea_FM_BS145-15IIL
dmi.product.version: Lenovo BS145-15IIL
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1932069/+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 1878279] Re: MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized from any given boot
The current upstream resolution to this problem is
https://git.kernel.org/linus/d341838d776a ("x86/PCI: Disable E820
reserved region clipping via quirks"), which relies on quirks that match
DMI Vendor, Product Version, Product Name, and Board Name. This isn't
an ideal solution because there are likely other systems we don't know
about that need a similar fix.
The patch I'm attaching here is an experimental idea to work around this
issue without the maintenance burden of the quirks.
If anybody would be willing to test this patch, I would be very
grateful. To test it, apply this patch to your kernel, boot with
"pci=use_e820 efi=debug", and collect the dmesg log.
** Attachment added: "experimental patch to remove EfiMemoryMappedIO"
https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1878279/+attachment/5632128/+files/remove-mmio
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-hwe in Ubuntu.
https://bugs.launchpad.net/bugs/1878279
Title:
MSFT0004:00 06CB:CD98 Touchpad/trackpad mouse randomly not recognized
from any given boot
Status in Linux:
Confirmed
Status in Ubuntu:
Confirmed
Status in linux-signed-hwe package in Ubuntu:
In Progress
Status in linux-signed-hwe package in Fedora:
New
Bug description:
Touchpad 'Buttonless Mylar surface multi-touch touchpad' doesn't work
at all (No response from the Touchpad) for notebook 'Lenovo Ideapad 5
14IIL05 81YH' from first system start on.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-29-generic 5.4.0-29.33
ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30
Uname: Linux 5.4.0-29-generic x86_64
ApportVersion: 2.20.11-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: tilman 1607 F pulseaudio
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Tue May 12 21:22:22 2020
InstallationDate: Installed on 2020-05-12 (0 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
MachineType: LENOVO 81YH
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=de_DE.UTF-8
SHELL=/bin/bash
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic
root=UUID=bb961a96-8855-4e50-814d-7994235377c3 ro quiet splash vt.handoff=7
RelatedPackageVersions:
linux-restricted-modules-5.4.0-29-generic N/A
linux-backports-modules-5.4.0-29-generic N/A
linux-firmware1.187
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 03/25/2020
dmi.bios.vendor: LENOVO
dmi.bios.version: DSCN23WW(V1.09)
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: LNVNB161216
dmi.board.vendor: LENOVO
dmi.board.version: No DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: IdeaPad 5 14IIL05
dmi.modalias:
dmi:bvnLENOVO:bvrDSCN23WW(V1.09):bd03/25/2020:svnLENOVO:pn81YH:pvrIdeaPad514IIL05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514IIL05:
dmi.product.family: IdeaPad 5 14IIL05
dmi.product.name: 81YH
dmi.product.sku: LENOVO_MT_81YH_BU_idea_FM_IdeaPad 5 14IIL05
dmi.product.version: IdeaPad 5 14IIL05
dmi.sys.vendor: LENOVO
To manage notifications about this bug go to:
https://bugs.launchpad.net/linux/+bug/1878279/+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 1993665] Re: Update the 470-server NVIDIA driver
Kinetic seems the only one that is missing fabric-manager and libnvidia- nscq. I think explains the failures that Francis reported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-470-server in Ubuntu. https://bugs.launchpad.net/bugs/1993665 Title: Update the 470-server NVIDIA driver Status in fabric-manager-470 package in Ubuntu: In Progress Status in libnvidia-nscq-470 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-470-server package in Ubuntu: In Progress Status in fabric-manager-470 source package in Bionic: Fix Released Status in libnvidia-nscq-470 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-470-server source package in Bionic: Fix Released Status in fabric-manager-470 source package in Focal: Fix Released Status in libnvidia-nscq-470 source package in Focal: Fix Released Status in nvidia-graphics-drivers-470-server source package in Focal: Fix Released Status in fabric-manager-470 source package in Jammy: Fix Released Status in libnvidia-nscq-470 source package in Jammy: Fix Released Status in nvidia-graphics-drivers-470-server source package in Jammy: Fix Released Status in fabric-manager-470 source package in Kinetic: In Progress Status in libnvidia-nscq-470 source package in Kinetic: In Progress Status in nvidia-graphics-drivers-470-server source package in Kinetic: In Progress Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fabric-manager-470/+bug/1993665/+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 1981649] Re: Jammy update: v5.15.44 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1981649 Title: Jammy update: v5.15.44 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.44 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1981649/+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 1982968] Re: Jammy update: v5.15.47 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1982968 Title: Jammy update: v5.15.47 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.47 upstream stable release from git://git.kernel.org/ pcmcia: db1xxx_ss: restrict to MIPS_DB1XXX boards staging: greybus: codecs: fix type confusion of list iterator variable iio: adc: ad7124: Remove shift from scan_type lkdtm/bugs: Check for the NULL pointer after calling kmalloc lkdtm/bugs: Don't expect thread termination without CONFIG_UBSAN_TRAP tty: goldfish: Use tty_port_destroy() to destroy port tty: serial: owl: Fix missing clk_disable_unprepare() in owl_uart_probe tty: n_tty: Restore EOF push handling behavior serial: 8250_aspeed_vuart: Fix potential NULL dereference in aspeed_vuart_probe tty: serial: fsl_lpuart: fix potential bug when using both of_alias_get_id and ida_simple_get remoteproc: imx_rproc: Ignore create mem entry for resource table usb: usbip: fix a refcount leak in stub_probe() usb: usbip: add missing device lock on tweak configuration cmd USB: storage: karma: fix rio_karma_init return usb: musb: Fix missing of_node_put() in omap2430_probe staging: fieldbus: Fix the error handling path in anybuss_host_common_probe() pwm: lp3943: Fix duty calculation in case period was clamped pwm: raspberrypi-poe: Fix endianness in firmware struct rpmsg: qcom_smd: Fix irq_of_parse_and_map() return value usb: dwc3: gadget: Replace list_for_each_entry_safe() if using giveback usb: dwc3: pci: Fix pm_runtime_get_sync() error checking misc: fastrpc: fix an incorrect NULL check on list iterator firmware: stratix10-svc: fix a missing check on list iterator usb: typec: mux: Check dev_set_name() return value rpmsg: virtio: Fix possible double free in rpmsg_probe() rpmsg: virtio: Fix possible double free in rpmsg_virtio_add_ctrl_dev() rpmsg: virtio: Fix the unregistration of the device rpmsg_ctrl iio: adc: stmpe-adc: Fix wait_for_completion_timeout return value check iio: proximity: vl53l0x: Fix return value check of wait_for_completion_timeout iio: adc: sc27xx: fix read big scale voltage not right iio: adc: sc27xx: Fine tune the scale calibration values rpmsg: qcom_smd: Fix returning 0 if irq_of_parse_and_map() fails pvpanic: Fix typos in the comments misc/pvpanic: Convert regular spinlock into trylock on panic path phy: qcom-qmp: fix pipe-clock imbalance on power-on failure power: supply: axp288_fuel_gauge: Drop BIOS version check from "T3 MRD" DMI quirk serial: sifive: Report actual baud base rather than fixed 115200 export: fix string handling of namespace in EXPORT_SYMBOL_NS soundwire: intel: prevent pm_runtime resume prior to system suspend coresight: cpu-debug: Replace mutex with mutex_trylock on panic notifier ksmbd: fix reference count leak in smb_check_perm_dacl() extcon: ptn5150: Add queue work sync before driver release soc: rockchip: Fix refcount leak in rockchip_grf_init clocksource/drivers/riscv: Events are stopped during CPU suspend ARM: dts: aspeed: ast2600-evb: Enable RX delay for MAC0/MAC1 rtc: mt6397: check return value after calling platform_get_resource() rtc: ftrtc010: Use platform_get_irq() to get the interrupt rtc: ftrtc010: Fix error handling in ftrtc010_rtc_probe staging: r8188eu: add check for kzalloc tty: n_gsm: Don't ignore write return value in gsmld_output() tty: n_gsm: Fix packet data hex dump output serial: meson: acquire port->lock in startup() serial: 8250_fintek: Check SER_RS485_RTS_* only with RS485 serial: cpm_uart: Fix build error without CONFIG_SERIAL_CPM_CONSOLE serial:
[Kernel-packages] [Bug 1983146] Re: Jammy update: v5.15.48 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1983146 Title: Jammy update: v5.15.48 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.48 upstream stable release from git://git.kernel.org/ Note: Every commit from v5.15.48 had already been applied. Linux 5.15.48 UBUNTU: Upstream stable to v5.15.48 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1983146/+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 1983149] Re: Jammy update: v5.15.49 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1983149 Title: Jammy update: v5.15.49 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.49 upstream stable release from git://git.kernel.org/ Revert "drm/amd/display: Fix DCN3 B0 DP Alt Mapping" nfsd: Replace use of rwsem with errseq_t arm64: dts: imx8mm-beacon: Enable RTS-CTS on UART3 arm64: dts: imx8mn-beacon: Enable RTS-CTS on UART3 powerpc/kasan: Silence KASAN warnings in __get_wchan() ASoC: nau8822: Add operation for internal PLL off and on drm/amd/display: Read Golden Settings Table from VBIOS drm/amdkfd: Use mmget_not_zero in MMU notifier dma-debug: make things less spammy under memory pressure ASoC: cs42l52: Fix TLV scales for mixer controls ASoC: cs35l36: Update digital volume TLV ASoC: cs53l30: Correct number of volume levels on SX controls ASoC: cs42l52: Correct TLV for Bypass Volume ASoC: cs42l56: Correct typo in minimum level for SX volume controls ASoC: cs42l51: Correct minimum value for SX volume control drm/amdkfd: add pinned BOs to kfd_bo_list ata: libata-core: fix NULL pointer deref in ata_host_alloc_pinfo() quota: Prevent memory allocation recursion while holding dq_lock ASoC: wm8962: Fix suspend while playing music ASoC: es8328: Fix event generation for deemphasis control ASoC: wm_adsp: Fix event generation for wm_adsp_fw_put() Input: soc_button_array - also add Lenovo Yoga Tablet2 1051F to dmi_use_low_level_irq scsi: vmw_pvscsi: Expand vcpuHint to 16 bits scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO is aborted scsi: lpfc: Fix port stuck in bypassed state after LIP in PT2PT topology scsi: lpfc: Allow reduced polling rate for nvme_admin_async_event cmd completion scsi: mpt3sas: Fix out-of-bounds compiler warning scsi: ipr: Fix missing/incorrect resource cleanup in error case scsi: pmcraid: Fix missing resource cleanup in error case ALSA: hda/realtek - Add HW8326 support virtio-mmio: fix missing put_device() when vm_cmdline_parent registration failed nfc: nfcmrvl: Fix memory leak in nfcmrvl_play_deferred ipv6: Fix signed integer overflow in l2tp_ip6_sendmsg net: ethernet: mtk_eth_soc: fix misuse of mem alloc interface netdev[napi]_alloc_frag gcc-12: disable '-Wdangling-pointer' warning for now mellanox: mlx5: avoid uninitialized variable warning with gcc-12 MIPS: Loongson-3: fix compile mips cpu_hwmon as module build error. random: credit cpu and bootloader seeds by default gpio: dwapb: Don't print error on -EPROBE_DEFER platform/x86: gigabyte-wmi: Add Z690M AORUS ELITE AX DDR4 support platform/x86: gigabyte-wmi: Add support for B450M DS3H-CF platform/x86/intel: hid: Add Surface Go to VGBS allow list staging: r8188eu: fix rtw_alloc_hwxmits error detection for now staging: r8188eu: Use zeroing allocator in wpa_set_encryption() staging: r8188eu: Fix warning of array overflow in ioctl_linux.c pNFS: Don't keep retrying if the server replied NFS4ERR_LAYOUTUNAVAILABLE pNFS: Avoid a live lock condition in pnfs_update_layout() sunrpc: set cl_max_connect when cloning an rpc_clnt clocksource: hyper-v: unexport __init-annotated hv_init_clocksource() i40e: Fix adding ADQ filter to TC0 i40e: Fix calculating the number of queue pairs i40e: Fix call trace in setup_tx_descriptors Drivers: hv: vmbus: Release cpu lock in error case tty: goldfish: Fix free_irq() on remove misc: atmel-ssc: Fix IRQ check in ssc_probe io_uring: fix races with file table unregister io_uring: fix races with buffer table unregister drm/i915/reset: Fix error_state_read ptr + offset use net: hns3: split
[Kernel-packages] [Bug 1986718] Re: Jammy update: v5.15.51 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1986718 Title: Jammy update: v5.15.51 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.51 upstream stable release from git://git.kernel.org/ random: schedule mix_interrupt_randomness() less often random: quiet urandom warning ratelimit suppression message ALSA: hda/via: Fix missing beep setup ALSA: hda/conexant: Fix missing beep setup ALSA: hda/realtek: Add mute LED quirk for HP Omen laptop ALSA: hda/realtek: Apply fixup for Lenovo Yoga Duet 7 properly ALSA: hda/realtek: Add quirk for Clevo PD70PNT ALSA: hda/realtek: Add quirk for Clevo NS50PU net: openvswitch: fix parsing of nw_proto for IPv6 fragments 9p: Fix refcounting during full path walks for fid lookups 9p: fix fid refcount leak in v9fs_vfs_atomic_open_dotl 9p: fix fid refcount leak in v9fs_vfs_get_link btrfs: fix hang during unmount when block group reclaim task is running btrfs: prevent remounting to v1 space cache for subpage mount btrfs: add error messages to all unrecognized mount options scsi: ibmvfc: Store vhost pointer during subcrq allocation scsi: ibmvfc: Allocate/free queue resource only during probe/remove mmc: sdhci-pci-o2micro: Fix card detect by dealing with debouncing mmc: mediatek: wait dma stop bit reset to 0 xen/gntdev: Avoid blocking in unmap_grant_pages() MAINTAINERS: Add new IOMMU development mailing list ata: libata: add qc->flags in ata_qc_complete_template tracepoint dm era: commit metadata in postsuspend after worker stops dm mirror log: clear log bits up to BITS_PER_LONG boundary tracing/kprobes: Check whether get_kretprobe() returns NULL in kretprobe_dispatcher() drm/i915: Implement w/a 22010492432 for adl-s USB: serial: pl2303: add support for more HXN (G) types USB: serial: option: add Telit LE910Cx 0x1250 composition USB: serial: option: add Quectel EM05-G modem USB: serial: option: add Quectel RM500K module support drm/msm: Ensure mmap offset is initialized drm/msm: Fix double pm_runtime_disable() call netfilter: use get_random_u32 instead of prandom scsi: scsi_debug: Fix zone transition to full condition drm/msm: Switch ordering of runpm put vs devfreq_idle scsi: iscsi: Exclude zero from the endpoint ID range xsk: Fix generic transmit when completion queue reservation fails drm/msm: use for_each_sgtable_sg to iterate over scatterlist bpf: Fix request_sock leak in sk lookup helpers drm/sun4i: Fix crash during suspend after component bind failure bpf, x86: Fix tail call count offset calculation on bpf2bpf call scsi: storvsc: Correct reporting of Hyper-V I/O size limits phy: aquantia: Fix AN when higher speeds than 1G are not advertised KVM: arm64: Prevent kmemleak from accessing pKVM memory net: Write lock dev_base_lock without disabling bottom halves. net: fix data-race in dev_isalive() tipc: fix use-after-free Read in tipc_named_reinit igb: fix a use-after-free issue in igb_clean_tx_ring bonding: ARP monitor spams NETDEV_NOTIFY_PEERS notifiers ethtool: Fix get module eeprom fallback net/sched: sch_netem: Fix arithmetic in netem_dump() for 32-bit platforms drm/msm/mdp4: Fix refcount leak in mdp4_modeset_init_intf drm/msm/dp: check core_initialized before disable interrupts at dp_display_unbind() drm/msm/dp: Drop now unused hpd_high member drm/msm/dp: dp_link_parse_sink_count() return immediately if aux read failed drm/msm/dp: do not initialize phy until plugin interrupt received drm/msm/dp: force link training for display resolution change perf arm-spe: Don't set data source if it's not a memory operation
[Kernel-packages] [Bug 1986715] Re: Jammy update: v5.15.50 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1986715 Title: Jammy update: v5.15.50 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.50 upstream stable release from git://git.kernel.org/ net: mana: Add handling of CQE_RX_TRUNCATED zonefs: fix zonefs_iomap_begin() for reads usb: gadget: u_ether: fix regression in setting fixed MAC address bpf: Fix calling global functions from BPF_PROG_TYPE_EXT programs selftests/bpf: Add selftest for calling global functions from freplace serial: core: Initialize rs485 RTS polarity already on probe arm64: mm: Don't invalidate FROM_DEVICE buffers at start of DMA transfer Linux 5.15.50 UBUNTU: Upstream stable to v5.15.50 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986715/+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 1986724] Re: Jammy update: v5.15.52 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1986724 Title: Jammy update: v5.15.52 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.52 upstream stable release from git://git.kernel.org/ tick/nohz: unexport __init-annotated tick_nohz_full_setup() xfs: use kmem_cache_free() for kmem_cache objects xfs: punch out data fork delalloc blocks on COW writeback failure xfs: Fix the free logic of state in xfs_attr_node_hasname xfs: remove all COW fork extents when remounting readonly xfs: check sb_meta_uuid for dabuf buffer recovery xfs: prevent UAF in xfs_log_item_in_current_chkpt xfs: only bother with sync_filesystem during readonly remount powerpc/ftrace: Remove ftrace init tramp once kernel init is complete fs: add is_idmapped_mnt() helper fs: move mapping helpers fs: tweak fsuidgid_has_mapping() fs: account for filesystem mappings docs: update mapping documentation fs: use low-level mapping helpers fs: remove unused low-level mapping helpers fs: port higher-level mapping helpers fs: add i_user_ns() helper fs: support mapped mounts of mapped filesystems fs: fix acl translation fs: account for group membership rtw88: 8821c: support RFE type4 wifi NIC rtw88: rtw8821c: enable rfe 6 devices net: mscc: ocelot: allow unregistered IP multicast flooding to CPU io_uring: fix not locked access to fixed buf table Linux 5.15.52 UBUNTU: Upstream stable to v5.15.52 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1986724/+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 1986728] Re: Jammy update: v5.15.53 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1986728 Title: Jammy update: v5.15.53 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.53 upstream stable release from git://git.kernel.org/ Revert "drm/amdgpu/display: set vblank_disable_immediate for DC" drm/amdgpu: To flush tlb for MMHUB of RAVEN series ksmbd: set the range of bytes to zero without extending file size in FSCTL_ZERO_DATA ksmbd: check invalid FileOffset and BeyondFinalZero in FSCTL_ZERO_DATA ksmbd: use vfs_llseek instead of dereferencing NULL ipv6: take care of disable_policy when restoring routes net: phy: Don't trigger state machine while in suspend nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA XPG SX6000LNP (AKA SPECTRIX S40G) nvme-pci: add NVME_QUIRK_BOGUS_NID for ADATA IM2P33F8ABR1 nvdimm: Fix badblocks clear off-by-one error powerpc/prom_init: Fix kernel config grep powerpc/book3e: Fix PUD allocation size in map_kernel_page() powerpc/bpf: Fix use of user_pt_regs in uapi dm raid: fix accesses beyond end of raid member array dm raid: fix KASAN warning in raid5_add_disks s390/archrandom: simplify back to earlier design and initialize earlier SUNRPC: Fix READ_PLUS crasher net: rose: fix UAF bugs caused by timer handler net: usb: ax88179_178a: Fix packet receiving virtio-net: fix race between ndo_open() and virtio_device_ready() selftests/net: pass ipv6_args to udpgso_bench's IPv6 TCP test net: dsa: bcm_sf2: force pause link settings net: tun: unlink NAPI from device on destruction net: tun: stop NAPI when detaching queues net: dp83822: disable false carrier interrupt net: dp83822: disable rx error interrupt RDMA/qedr: Fix reporting QP timeout attribute RDMA/cm: Fix memory leak in ib_cm_insert_listen linux/dim: Fix divide by 0 in RDMA DIM net: usb: asix: do not force pause frames support usbnet: fix memory allocation in helpers selftests: mptcp: more stable diag tests net: ipv6: unexport __init-annotated seg6_hmac_net_init() NFSD: restore EINVAL error translation in nfsd_commit() vfs: fix copy_file_range() regression in cross-fs copies caif_virtio: fix race between virtio_device_ready() and ndo_open() PM / devfreq: exynos-ppmu: Fix refcount leak in of_get_devfreq_events vdpa/mlx5: Update Control VQ callback information s390: remove unneeded 'select BUILD_BIN2C' netfilter: nft_dynset: restore set element counter when failing to update net/dsa/hirschmann: Add missing of_node_get() in hellcreek_led_setup() net/sched: act_api: Notify user space if any actions were flushed before error net: asix: fix "can't send until first packet is send" issue net: bonding: fix possible NULL deref in rlb code net: phy: ax88772a: fix lost pause advertisement configuration net: bonding: fix use-after-free after 802.3ad slave unbind powerpc/memhotplug: Add add_pages override for PPC nfc: nfcmrvl: Fix irq_of_parse_and_map() return value NFC: nxp-nci: Don't issue a zero length i2c_master_read() tipc: move bc link creation back to tipc_node_create epic100: fix use after free on rmmod io_uring: ensure that send/sendmsg and recv/recvmsg check sqe->ioprio ACPI: video: Change how we determine if brightness key-presses are handled tunnels: do not assume mac header is set in skb_tunnel_check_pmtu() ipv6/sit: fix ipip6_tunnel_get_prl return value ipv6: fix lockdep splat in in6_dump_addrs() mlxsw: spectrum_router: Fix rollback in tunnel next hop init net: tun: avoid disabling NAPI twice MAINTAINERS: add Leah as xfs maintainer for 5.15.y tcp: add a missing nf_reset_ct() in 3WHS handling selftests/bpf: Add
[Kernel-packages] [Bug 1987451] Re: Jammy update: v5.15.54 upstream stable release
This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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!
** Tags added: verification-needed-jammy
--
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/1987451
Title:
Jammy update: v5.15.54 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.54 upstream stable release
from git://git.kernel.org/
mm/slub: add missing TID updates on slab deactivation
mm/filemap: fix UAF in find_lock_entries
Revert "selftests/bpf: Add test for bpf_timer overwriting crash"
ALSA: usb-audio: Workarounds for Behringer UMC 204/404 HD
ALSA: hda/realtek: Add quirk for Clevo L140PU
ALSA: cs46xx: Fix missing snd_card_free() call at probe error
can: bcm: use call_rcu() instead of costly synchronize_rcu()
can: grcan: grcan_probe(): remove extra of_node_get()
can: gs_usb: gs_usb_open/close(): fix memory leak
can: m_can: m_can_chip_config(): actually enable internal timestamping
can: m_can: m_can_{read_fifo,echo_tx_event}(): shift timestamp to full 32 bits
can: mcp251xfd: mcp251xfd_regmap_crc_read(): improve workaround handling for
mcp2517fd
can: mcp251xfd: mcp251xfd_regmap_crc_read(): update workaround broken CRC on
TBC register
bpf: Fix incorrect verifier simulation around jmp32's jeq/jne
bpf: Fix insufficient bounds propagation from adjust_scalar_min_max_vals
usbnet: fix memory leak in error case
net: rose: fix UAF bug caused by rose_t0timer_expiry
netfilter: nft_set_pipapo: release elements in clone from abort path
btrfs: rename btrfs_alloc_chunk to btrfs_create_chunk
btrfs: add additional parameters to btrfs_init_tree_ref/btrfs_init_data_ref
btrfs: fix invalid delayed ref after subvolume creation failure
btrfs: fix warning when freeing leaf after subvolume creation failure
Input: cpcap-pwrbutton - handle errors from platform_get_irq()
Input: goodix - change goodix_i2c_write() len parameter type to int
Input: goodix - add a goodix.h header file
Input: goodix - refactor reset handling
Input: goodix - try not to touch the reset-pin on x86/ACPI devices
dma-buf/poll: Get a file reference for outstanding fence callbacks
btrfs: fix deadlock between chunk allocation and chunk btree modifications
drm/i915: Disable bonding on gen12+ platforms
drm/i915/gt: Register the migrate contexts with their engines
drm/i915: Replace the unconditional clflush with drm_clflush_virt_range()
media: ir_toy: prevent device from hanging during transmit
memory: renesas-rpc-if: Avoid unaligned bus access for HyperFlash
ath11k: add hw_param for wakeup_mhi
qed: Improve the stack space of filter_config()
platform/x86: wmi: introduce helper to convert driver to WMI driver
platform/x86: wmi: Replace read_takes_no_args with a flags field
platform/x86: wmi: Fix driver->notify() vs ->probe() race
mt76: mt7921: get rid of mt7921_mac_set_beacon_filter
mt76: mt7921: introduce mt7921_mcu_set_beacon_filter utility routine
mt76: mt7921: fix a possible race enabling/disabling runtime-pm
bpf: Stop caching subprog index in the bpf_pseudo_func insn
bpf, arm64: Use emit_addr_mov_i64() for BPF_PSEUDO_FUNC
riscv: defconfig: enable DRM_NOUVEAU
RISC-V: defconfigs: Set CONFIG_FB=y, for FB console
net/mlx5e: Check action fwd/drop flag exists also for nic flows
net/mlx5e: Split actions_match_supported() into a sub function
net/mlx5e: TC, Reject rules with drop and modify hdr action
net/mlx5e: TC, Reject rules with forward and drop actions
ASoC: rt5682: Avoid the unexpected IRQ event during going to suspend
ASoC: rt5682: Re-detect the combo jack after resuming
ASoC: rt5682: Fix deadlock on resume
netfilter: nf_tables: convert pktinfo->tprot_set to flags field
netfilter: nft_payload: support for inner header matching / mangling
netfilter:
[Kernel-packages] [Bug 1988338] Re: Jammy update: v5.15.55 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1988338 Title: Jammy update: v5.15.55 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.55 upstream stable release from git://git.kernel.org/ NOTE This patch set (v5.15.55) is empty; it contained only one revert: Revert "mtd: rawnand: gpmi: Fix setting busy timeout setting" which was never applied to Jammy. Linux 5.15.55 UBUNTU: Upstream stable to v5.15.55 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988338/+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 1988351] Re: Jammy update: v5.15.56 upstream stable release
This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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!
** Tags added: verification-needed-jammy
--
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/1988351
Title:
Jammy update: v5.15.56 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.56 upstream stable release
from git://git.kernel.org/
ALSA: hda - Add fixup for Dell Latitidue E5430
ALSA: hda/conexant: Apply quirk for another HP ProDesk 600 G3 model
ALSA: hda/realtek: Fix headset mic for Acer SF313-51
ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc671
ALSA: hda/realtek - Fix headset mic problem for a HP machine with alc221
ALSA: hda/realtek - Enable the headset-mic on a Xiaomi's laptop
xen/netback: avoid entering xenvif_rx_next_skb() with an empty rx queue
fix race between exit_itimers() and /proc/pid/timers
mm: userfaultfd: fix UFFDIO_CONTINUE on fallocated shmem pages
mm: split huge PUD on wp_huge_pud fallback
tracing/histograms: Fix memory leak problem
net: sock: tracing: Fix sock_exceed_buf_limit not to dereference stale pointer
ip: fix dflt addr selection for connected nexthop
ARM: 9213/1: Print message about disabled Spectre workarounds only once
ARM: 9214/1: alignment: advance IT state after emulating Thumb instruction
wifi: mac80211: fix queue selection for mesh/OCB interfaces
cgroup: Use separate src/dst nodes when preloading css_sets for migration
btrfs: return -EAGAIN for NOWAIT dio reads/writes on compressed and inline
extents
drm/panfrost: Put mapping instead of shmem obj on
panfrost_mmu_map_fault_addr() error
drm/panfrost: Fix shrinker list corruption by madvise IOCTL
fs/remap: constrain dedupe of EOF blocks
nilfs2: fix incorrect masking of permission flags for symlinks
sh: convert nommu io{re,un}map() to static inline functions
Revert "evm: Fix memleak in init_desc"
xfs: only run COW extent recovery when there are no live extents
xfs: don't include bnobt blocks when reserving free block pool
xfs: run callbacks before waking waiters in xlog_state_shutdown_callbacks
xfs: drop async cache flushes from CIL commits.
reset: Fix devm bulk optional exclusive control getter
ARM: dts: imx6qdl-ts7970: Fix ngpio typo and count
spi: amd: Limit max transfer and message size
ARM: 9209/1: Spectre-BHB: avoid pr_info() every time a CPU comes out of idle
ARM: 9210/1: Mark the FDT_FIXED sections as shareable
net/mlx5e: kTLS, Fix build time constant test in TX
net/mlx5e: kTLS, Fix build time constant test in RX
net/mlx5e: Fix enabling sriov while tc nic rules are offloaded
net/mlx5e: Fix capability check for updating vnic env counters
net/mlx5e: Ring the TX doorbell on DMA errors
drm/i915: fix a possible refcount leak in intel_dp_add_mst_connector()
ima: Fix a potential integer overflow in ima_appraise_measurement
ASoC: sgtl5000: Fix noise on shutdown/remove
ASoC: tas2764: Add post reset delays
ASoC: tas2764: Fix and extend FSYNC polarity handling
ASoC: tas2764: Correct playback volume range
ASoC: tas2764: Fix amp gain register offset & default
ASoC: Intel: Skylake: Correct the ssp rate discovery in skl_get_ssp_clks()
ASoC: Intel: Skylake: Correct the handling of fmt_config flexible array
net: stmmac: dwc-qos: Disable split header for Tegra194
net: ethernet: ti: am65-cpsw: Fix devlink port register sequence
sysctl: Fix data races in proc_dointvec().
sysctl: Fix data races in proc_douintvec().
sysctl: Fix data races in proc_dointvec_minmax().
sysctl: Fix data races in proc_douintvec_minmax().
sysctl: Fix data races in proc_doulongvec_minmax().
sysctl: Fix data races in proc_dointvec_jiffies().
tcp: Fix a data-race around sysctl_tcp_max_orphans.
inetpeer: Fix data-races around
[Kernel-packages] [Bug 1988353] Re: Jammy update: v5.15.57 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1988353 Title: Jammy update: v5.15.57 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.57 upstream stable release from git://git.kernel.org/ x86/xen: Fix initialisation in hypercall_page after rethunk tools arch x86: Sync the msr-index.h copy with the kernel sources tools headers cpufeatures: Sync with the kernel sources um: Add missing apply_returns() x86: Use -mindirect-branch-cs-prefix for RETPOLINE builds Linux 5.15.57 UBUNTU: Upstream stable to v5.15.57 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1988353/+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 1988479] Re: Jammy update: v5.15.58 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1988479 Title: Jammy update: v5.15.58 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.58 upstream stable release from git://git.kernel.org/ pinctrl: stm32: fix optional IRQ support to gpios riscv: add as-options for modules with assembly compontents mlxsw: spectrum_router: Fix IPv4 nexthop gateway indication lockdown: Fix kexec lockdown bypass with ima policy drm/ttm: fix locking in vmap/vunmap TTM GEM helpers bus: mhi: host: pci_generic: add Telit FN980 v1 hardware revision bus: mhi: host: pci_generic: add Telit FN990 Revert "selftest/vm: verify remap destination address in mremap_test" Revert "selftest/vm: verify mmap addr in mremap_test" PCI: hv: Fix multi-MSI to allow more than one MSI vector PCI: hv: Fix hv_arch_irq_unmask() for multi-MSI PCI: hv: Reuse existing IRTE allocation in compose_msi_msg() PCI: hv: Fix interrupt mapping for multi-MSI serial: mvebu-uart: correctly report configured baudrate value batman-adv: Use netif_rx_any_context() any. xfs: fix maxlevels comparisons in the btree staging code xfs: fold perag loop iteration logic into helper function xfs: rename the next_agno perag iteration variable xfs: terminate perag iteration reliably on agcount xfs: fix perag reference leak on iteration race with growfs xfs: prevent a WARN_ONCE() in xfs_ioc_attr_list() r8152: fix a WOL issue ip: Fix data-races around sysctl_ip_default_ttl. xfrm: xfrm_policy: fix a possible double xfrm_pols_put() in xfrm_bundle_lookup() power/reset: arm-versatile: Fix refcount leak in versatile_reboot_probe RDMA/irdma: Do not advertise 1GB page size for x722 RDMA/irdma: Fix sleep from invalid context BUG pinctrl: ralink: rename MT7628(an) functions to MT76X8 pinctrl: ralink: rename pinctrl-rt2880 to pinctrl-ralink pinctrl: ralink: Check for null return of devm_kcalloc perf/core: Fix data race between perf_event_set_output() and perf_mmap_close() ipv4/tcp: do not use per netns ctl sockets net: tun: split run_ebpf_filter() and pskb_trim() into different "if statement" mm/pagealloc: sysctl: change watermark_scale_factor max limit to 30% sysctl: move some boundary constants from sysctl.c to sysctl_vals tcp: Fix data-races around sysctl_tcp_ecn. drm/amd/display: Add option to defer works of hpd_rx_irq drm/amd/display: Fork thread to offload work of hpd_rx_irq drm/amdgpu/display: add quirk handling for stutter mode drm/amd/display: Ignore First MST Sideband Message Return Error scsi: megaraid: Clear READ queue map's nr_queues scsi: ufs: core: Drop loglevel of WriteBoost message nvme: check for duplicate identifiers earlier nvme: fix block device naming collision igc: Reinstate IGC_REMOVED logic and implement it properly ip: Fix data-races around sysctl_ip_no_pmtu_disc. ip: Fix data-races around sysctl_ip_fwd_use_pmtu. ip: Fix data-races around sysctl_ip_fwd_update_priority. ip: Fix data-races around sysctl_ip_nonlocal_bind. ip: Fix a data-race around sysctl_ip_autobind_reuse. ip: Fix a data-race around sysctl_fwmark_reflect. tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept. tcp: sk->sk_bound_dev_if once in inet_request_bound_dev_if() tcp: Fix data-races around sysctl_tcp_l3mdev_accept. tcp: Fix data-races around sysctl_tcp_mtu_probing. tcp: Fix data-races around sysctl_tcp_base_mss. tcp: Fix data-races around sysctl_tcp_min_snd_mss. tcp: Fix a data-race around sysctl_tcp_mtu_probe_floor. tcp: Fix a data-race around sysctl_tcp_probe_threshold. tcp: Fix a data-race around sysctl_tcp_probe_interval. net:
[Kernel-packages] [Bug 1990162] Re: Jammy update: v5.15.61 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1990162 Title: Jammy update: v5.15.61 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.61 upstream stable release from git://git.kernel.org/ Makefile: link with -z noexecstack --no-warn-rwx-segments x86: link vdso and boot with -z noexecstack --no-warn-rwx-segments Revert "pNFS: nfs3_set_ds_client should set NFS_CS_NOPING" scsi: Revert "scsi: qla2xxx: Fix disk failure to rediscover" pNFS/flexfiles: Report RDMA connection errors to the server NFSD: Clean up the show_nf_flags() macro nfsd: eliminate the NFSD_FILE_BREAK_* flags ALSA: usb-audio: Add quirk for Behringer UMC202HD ALSA: bcd2000: Fix a UAF bug on the error path of probing ALSA: hda/realtek: Add quirk for Clevo NV45PZ ALSA: hda/realtek: Add quirk for HP Spectre x360 15-eb0xxx wifi: mac80211_hwsim: fix race condition in pending packet wifi: mac80211_hwsim: add back erroneously removed cast wifi: mac80211_hwsim: use 32-bit skb cookie add barriers to buffer_uptodate and set_buffer_uptodate lockd: detect and reject lock arguments that overflow HID: hid-input: add Surface Go battery quirk HID: wacom: Only report rotation for art pen HID: wacom: Don't register pad_input for touch switch KVM: nVMX: Snapshot pre-VM-Enter BNDCFGS for !nested_run_pending case KVM: nVMX: Snapshot pre-VM-Enter DEBUGCTL for !nested_run_pending case KVM: SVM: Don't BUG if userspace injects an interrupt with GIF=0 KVM: s390: pv: don't present the ecall interrupt twice KVM: x86: Split kvm_is_valid_cr4() and export only the non-vendor bits KVM: nVMX: Let userspace set nVMX MSR to any _host_ supported value KVM: nVMX: Account for KVM reserved CR4 bits in consistency checks KVM: nVMX: Inject #UD if VMXON is attempted with incompatible CR0/CR4 KVM: x86: Mark TSS busy during LTR emulation _after_ all fault checks KVM: x86: Set error code to segment selector on LLDT/LTR non-canonical #GP KVM: nVMX: Always enable TSC scaling for L2 when it was enabled for L1 KVM: x86: Tag kvm_mmu_x86_module_init() with __init KVM: x86: do not report preemption if the steal time cache is stale KVM: x86: revalidate steal time cache if MSR value changes riscv: set default pm_power_off to NULL ALSA: hda/conexant: Add quirk for LENOVO 20149 Notebook model ALSA: hda/cirrus - support for iMac 12,1 model ALSA: hda/realtek: Add quirk for another Asus K42JZ model ALSA: hda/realtek: Add a quirk for HP OMEN 15 (8786) mute LED tty: vt: initialize unicode screen buffer vfs: Check the truncate maximum size in inode_newsize_ok() fs: Add missing umask strip in vfs_tmpfile thermal: sysfs: Fix cooling_device_stats_setup() error code path fbcon: Fix boundary checks for fbcon=vc:n1-n2 parameters fbcon: Fix accelerated fbdev scrolling while logo is still shown usbnet: Fix linkwatch use-after-free on disconnect fix short copy handling in copy_mc_pipe_to_iter() crypto: ccp - Use kzalloc for sev ioctl interfaces to prevent kernel memory leak ovl: drop WARN_ON() dentry is NULL in ovl_encode_fh() parisc: Fix device names in /proc/iomem parisc: Drop pa_swapper_pg_lock spinlock parisc: Check the return value of ioremap() in lba_driver_probe() parisc: io_pgetevents_time64() needs compat syscall in 32-bit compat mode riscv:uprobe fix SR_SPIE set/clear handling dt-bindings: riscv: fix SiFive l2-cache's cache-sets RISC-V: kexec: Fixup use of smp_processor_id() in preemptible context RISC-V: Fixup get incorrect user mode PC for kernel mode regs RISC-V: Fixup schedule out issue in machine_crash_shutdown() RISC-V: Add modules to
[Kernel-packages] [Bug 1989221] Re: Jammy update: v5.15.60 upstream stable release
This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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!
** Tags added: verification-needed-jammy
--
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/1989221
Title:
Jammy update: v5.15.60 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.60 upstream stable release
from git://git.kernel.org/
x86/speculation: Make all RETbleed mitigations 64-bit only
selftests/bpf: Extend verifier and bpf_sock tests for dst_port loads
selftests/bpf: Check dst_port only on the client socket
block: fix default IO priority handling again
tools/vm/slabinfo: Handle files in debugfs
ACPI: video: Force backlight native for some TongFang devices
ACPI: video: Shortening quirk list by identifying Clevo by board_name only
ACPI: APEI: Better fix to avoid spamming the console with old error logs
crypto: arm64/poly1305 - fix a read out-of-bound
KVM: x86: do not report a vCPU as preempted outside instruction boundaries
KVM: x86: do not set st->preempted when going back to user space
KVM: selftests: Make hyperv_clock selftest more stable
tools/kvm_stat: fix display of error when multiple processes are found
selftests: KVM: Handle compiler optimizations in ucall
KVM: x86/svm: add __GFP_ACCOUNT to __sev_dbg_{en,de}crypt_user()
arm64: set UXN on swapper page tables
btrfs: zoned: prevent allocation from previous data relocation BG
btrfs: zoned: fix critical section of relocation inode writeback
Bluetooth: hci_bcm: Add BCM4349B1 variant
Bluetooth: hci_bcm: Add DT compatible for CYW55572
dt-bindings: bluetooth: broadcom: Add BCM4349B1 DT binding
Bluetooth: btusb: Add support of IMC Networks PID 0x3568
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04CA:0x4007
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x04C5:0x1675
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x0CB8:0xC558
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3587
Bluetooth: btusb: Add Realtek RTL8852C support ID 0x13D3:0x3586
macintosh/adb: fix oob read in do_adb_query() function
x86/speculation: Add RSB VM Exit protections
x86/speculation: Add LFENCE to RSB fill sequence
Linux 5.15.60
UBUNTU: Upstream stable to v5.15.60
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1989221/+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 1989218] Re: Jammy update: v5.15.59 upstream stable release
This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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!
** Tags added: verification-needed-jammy
--
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/1989218
Title:
Jammy update: v5.15.59 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.59 upstream stable release
from git://git.kernel.org/
Bluetooth: L2CAP: Fix use-after-free caused by l2cap_chan_put
Revert "ocfs2: mount shared volume without ha stack"
ntfs: fix use-after-free in ntfs_ucsncmp()
fs: sendfile handles O_NONBLOCK of out_fd
secretmem: fix unhandled fault in truncate
mm: fix page leak with multiple threads mapping the same page
hugetlb: fix memoryleak in hugetlb_mcopy_atomic_pte
asm-generic: remove a broken and needless ifdef conditional
s390/archrandom: prevent CPACF trng invocations in interrupt context
nouveau/svm: Fix to migrate all requested pages
drm/simpledrm: Fix return type of simpledrm_simple_display_pipe_mode_valid()
watch_queue: Fix missing rcu annotation
watch_queue: Fix missing locking in add_watch_to_object()
tcp: Fix data-races around sysctl_tcp_dsack.
tcp: Fix a data-race around sysctl_tcp_app_win.
tcp: Fix a data-race around sysctl_tcp_adv_win_scale.
tcp: Fix a data-race around sysctl_tcp_frto.
tcp: Fix a data-race around sysctl_tcp_nometrics_save.
tcp: Fix data-races around sysctl_tcp_no_ssthresh_metrics_save.
ice: check (DD | EOF) bits on Rx descriptor rather than (EOP | RS)
ice: do not setup vlan for loopback VSI
scsi: ufs: host: Hold reference returned by of_parse_phandle()
Revert "tcp: change pingpong threshold to 3"
octeontx2-pf: Fix UDP/TCP src and dst port tc filters
tcp: Fix data-races around sysctl_tcp_moderate_rcvbuf.
tcp: Fix a data-race around sysctl_tcp_limit_output_bytes.
tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit.
scsi: core: Fix warning in scsi_alloc_sgtables()
scsi: mpt3sas: Stop fw fault watchdog work item during system shutdown
net: ping6: Fix memleak in ipv6_renew_options().
ipv6/addrconf: fix a null-ptr-deref bug for ip6_ptr
net/tls: Remove the context from the list in tls_device_down
igmp: Fix data-races around sysctl_igmp_qrv.
net: pcs: xpcs: propagate xpcs_read error to xpcs_get_state_c37_sgmii
net: sungem_phy: Add of_node_put() for reference returned by of_get_parent()
tcp: Fix a data-race around sysctl_tcp_min_tso_segs.
tcp: Fix a data-race around sysctl_tcp_min_rtt_wlen.
tcp: Fix a data-race around sysctl_tcp_autocorking.
tcp: Fix a data-race around sysctl_tcp_invalid_ratelimit.
Documentation: fix sctp_wmem in ip-sysctl.rst
macsec: fix NULL deref in macsec_add_rxsa
macsec: fix error message in macsec_add_rxsa and _txsa
macsec: limit replay window size with XPN
macsec: always read MACSEC_SA_ATTR_PN as a u64
net: macsec: fix potential resource leak in macsec_add_rxsa() and
macsec_add_txsa()
net: mld: fix reference count leak in mld_{query | report}_work()
tcp: Fix data-races around sk_pacing_rate.
net: Fix data-races around sysctl_[rw]mem(_offset)?.
tcp: Fix a data-race around sysctl_tcp_comp_sack_delay_ns.
tcp: Fix a data-race around sysctl_tcp_comp_sack_slack_ns.
tcp: Fix a data-race around sysctl_tcp_comp_sack_nr.
tcp: Fix data-races around sysctl_tcp_reflect_tos.
ipv4: Fix data-races around sysctl_fib_notify_on_flag_change.
i40e: Fix interface init with MSI interrupts (no MSI-X)
sctp: fix sleep in atomic context bug in timer handlers
octeontx2-pf: cn10k: Fix egress ratelimit configuration
virtio-net: fix the race between refill work and close
perf symbol: Correct address for bss symbols
sfc: disable softirqs for ptp TX
sctp: leave the err path free in sctp_stream_init to sctp_stream_free
ARM: crypto: comment out gcc
[Kernel-packages] [Bug 1990554] Re: Jammy update: v5.15.62 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1990554 Title: Jammy update: v5.15.62 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.62 upstream stable release from git://git.kernel.org/ io_uring: use original request task for inflight tracking tee: add overflow check in register_shm_helper() net_sched: cls_route: disallow handle of 0 ksmbd: prevent out of bound read for SMB2_WRITE ksmbd: fix heap-based overflow in set_ntacl_dacl() btrfs: only write the sectors in the vertical stripe which has data stripes btrfs: raid56: don't trust any cached sector in __raid56_parity_recover() Linux 5.15.62 UBUNTU: Upstream stable to v5.15.62 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990554/+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 1990564] Re: Jammy update: v5.15.63 upstream stable release
This bug is awaiting verification that the linux-
bluefield/5.15.0-1010.12 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!
** Tags added: verification-needed-jammy
--
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/1990564
Title:
Jammy update: v5.15.63 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Jammy:
Fix Released
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.15.63 upstream stable release
from git://git.kernel.org/
ALSA: info: Fix llseek return value when using callback
ALSA: hda/realtek: Add quirk for Clevo NS50PU, NS70PU
KVM: Unconditionally get a ref to /dev/kvm module when creating a VM
x86/mm: Use proper mask when setting PUD mapping
rds: add missing barrier to release_refill
locking/atomic: Make test_and_*_bit() ordered on failure
drm/nouveau: recognise GA103
drm/ttm: Fix dummy res NULL ptr deref bug
drm/amd/display: Check correct bounds for stream encoder instances for DCN303
ata: libata-eh: Add missing command name
mmc: pxamci: Fix another error handling path in pxamci_probe()
mmc: pxamci: Fix an error handling path in pxamci_probe()
mmc: meson-gx: Fix an error handling path in meson_mmc_probe()
btrfs: unset reloc control if transaction commit fails in
prepare_to_relocate()
btrfs: reset RO counter on block group if we fail to relocate
btrfs: fix lost error handling when looking up extended ref on log replay
cifs: Fix memory leak on the deferred close
x86/kprobes: Fix JNG/JNLE emulation
tracing/eprobes: Do not allow eprobes to use $stack, or % for regs
tracing/eprobes: Do not hardcode $comm as a string
tracing/eprobes: Have event probes be consistent with kprobes and uprobes
tracing/probes: Have kprobes and uprobes use $COMM too
tracing: Have filter accept "common_cpu" to be consistent
ALSA: usb-audio: More comprehensive mixer map for ASUS ROG Zenith II
dt-bindings: usb: mtk-xhci: Allow wakeup interrupt-names to be optional
can: ems_usb: fix clang's -Wunaligned-access warning
apparmor: fix quiet_denied for file rules
Revert "UBUNTU: SAUCE: apparmor: drop prefixing abs root labels with '='"
apparmor: fix absroot causing audited secids to begin with =
apparmor: Fix failed mount permission check error message
apparmor: fix aa_label_asxprint return check
apparmor: fix setting unconfined mode on a loaded profile
apparmor: fix overlapping attachment computation
apparmor: fix reference count leak in aa_pivotroot()
apparmor: Fix memleak in aa_simple_write_to_buffer()
Documentation: ACPI: EINJ: Fix obsolete example
NFSv4.1: Don't decrease the value of seq_nr_highest_sent
NFSv4.1: Handle NFS4ERR_DELAY replies to OP_SEQUENCE correctly
NFSv4: Fix races in the legacy idmapper upcall
NFSv4.1: RECLAIM_COMPLETE must handle EACCES
NFSv4/pnfs: Fix a use-after-free bug in open
BPF: Fix potential bad pointer dereference in bpf_sys_bpf()
bpf: Don't reinit map value in prealloc_lru_pop
bpf: Acquire map uref in .init_seq_private for array map iterator
bpf: Acquire map uref in .init_seq_private for hash map iterator
bpf: Acquire map uref in .init_seq_private for sock local storage map iterator
bpf: Acquire map uref in .init_seq_private for sock{map,hash} iterator
bpf: Check the validity of max_rdwr_access for sock local storage map iterator
can: mcp251x: Fix race condition on receive interrupt
can: j1939: j1939_session_destroy(): fix memory leak of skbs
net: atlantic: fix aq_vec index out of range error
m68k: coldfire/device.c: protect FLEXCAN blocks
sunrpc: fix expiry of auth creds
SUNRPC: Fix xdr_encode_bool()
SUNRPC: Reinitialise the backchannel request buffers before reuse
virtio_net: fix memory leak inside XPD_TX with mergeable
devlink: Fix use-after-free after a failed reload
net: phy: Warn about incorrect mdio_bus_phy_resume() state
net: bcmgenet: Indicate MAC is in charge of PHY PM
[Kernel-packages] [Bug 1991717] Re: Jammy update: v5.15.64 upstream stable release
This bug is awaiting verification that the linux- bluefield/5.15.0-1010.12 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! ** Tags added: verification-needed-jammy -- 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/1991717 Title: Jammy update: v5.15.64 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Jammy: Fix Released Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.15.64 upstream stable release from git://git.kernel.org/ wifi: rtlwifi: remove always-true condition pointed out by GCC 12 eth: sun: cassini: remove dead code audit: fix potential double free on error path from fsnotify_add_inode_mark cgroup: Fix race condition at rebind_subsystems() parisc: Make CONFIG_64BIT available for ARCH=parisc64 only parisc: Fix exception handler for fldw and fstw instructions kernel/sys_ni: add compat entry for fadvise64_64 x86/entry: Move CLD to the start of the idtentry macro block: add a bdev_max_zone_append_sectors helper block: add bdev_max_segments() helper btrfs: zoned: revive max_zone_append_bytes btrfs: replace BTRFS_MAX_EXTENT_SIZE with fs_info->max_extent_size btrfs: convert count_max_extents() to use fs_info->max_extent_size Input: i8042 - move __initconst to fix code styling warning Input: i8042 - merge quirk tables Input: i8042 - add TUXEDO devices to i8042 quirk tables Input: i8042 - add additional TUXEDO devices to i8042 quirk tables drivers/base: fix userspace break from using bin_attributes for cpumap and cpulist scsi: qla2xxx: Fix response queue handler reading stale packets scsi: qla2xxx: edif: Fix dropped IKE message btrfs: put initial index value of a directory in a constant btrfs: pass the dentry to btrfs_log_new_name() instead of the inode btrfs: remove unnecessary parameter delalloc_start for writepage_delalloc() riscv: lib: uaccess: fold fixups into body riscv: lib: uaccess: fix CSR_STATUS SR_SUM bit xfrm: fix refcount leak in __xfrm_policy_check() xfrm: clone missing x->lastused in xfrm_do_migrate af_key: Do not call xfrm_probe_algs in parallel xfrm: policy: fix metadata dst->dev xmit null pointer dereference fs: require CAP_SYS_ADMIN in target namespace for idmapped mounts net: use eth_hw_addr_set() instead of ether_addr_copy() Revert "net: macsec: update SCI upon MAC address change." NFS: Don't allocate nfs_fattr on the stack in __nfs42_ssc_open() NFSv4.2 fix problems with __nfs42_ssc_open SUNRPC: RPC level errors should set task->tk_rpc_status mm/smaps: don't access young/dirty bit if pte unpresent ntfs: fix acl handling rose: check NULL rose_loopback_neigh->loopback r8152: fix the units of some registers for RTL8156A r8152: fix the RX FIFO settings when suspending nfc: pn533: Fix use-after-free bugs caused by pn532_cmd_timeout ice: xsk: Force rings to be sized to power of 2 ice: xsk: prohibit usage of non-balanced queue id net/mlx5e: Properly disable vlan strip on non-UL reps net/mlx5: Avoid false positive lockdep warning by adding lock_class_key net/mlx5e: Fix wrong application of the LRO state net/mlx5e: Fix wrong tc flag used when set hw-tc-offload off net: ipa: don't assume SMEM is page-aligned net: phy: Don't WARN for PHY_READY state in mdio_bus_phy_resume() net: moxa: get rid of asymmetry in DMA mapping/unmapping bonding: 802.3ad: fix no transmission of LACPDUs net: ipvtap - add __init/__exit annotations to module init/exit funcs netfilter: ebtables: reject blobs that don't provide all entry points bnxt_en: fix NQ resource accounting during vf creation on 57500 chips netfilter: nf_tables: disallow updates of implicit chain netfilter: nf_tables: make table handle allocation per-netns friendly netfilter: nft_payload: report ERANGE for too long offset and length netfilter: nft_payload: do not truncate csum_offset and csum_type netfilter: nf_tables: do not
[Kernel-packages] [Bug 1996806] Re: Azure: Jammy fio test causes panic
** Tags added: verification-done-jammy
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1996806
Title:
Azure: Jammy fio test causes panic
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure source package in Jammy:
Fix Released
Bug description:
SRU Justification
[Impact]
During Storage performance tests, 16 disks are attached and fio is
ran. The fio command does not consistently result in a kernel panic,
but the test runs fio enough times to result in consistent kernel
panic. The panic is most often observed on instances with many cores
and disks.
[Test Case]
Using an instance with 96 cores and 16 disks:
sudo fio --ioengine=libaio --bs=1024K
--filename=/dev/sda:/dev/sdb:/dev/sdc:/dev/sdd:/dev/sde:/dev/sdf:/dev/sdg:/dev/sdh:/dev/sdi:/dev/sdj:/dev/sdk:/dev/sdl:/dev/sdm:/dev/sdn:/dev/sdo:/dev/sdp
--readwrite=read --runtime=120 --iodepth=32 --numjob=96
--name=iteration23 --direct=1 --size=8192M --group_reporting
--overwrite=1
Test results from Microsoft and myself are positive. No panics were
observed.
[Regression Potential]
The fix is an upstream patch from 5.17, commit
0bd2fbee9d0b7f801a9c0264d90b1e0d8053f395 ('scsi: storvsc: Fix unsigned
comparison to zero'). Regression potential is low.
[Other Info]
SF: #00346757
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1996806/+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 1984117] Re: [VROC] Kernel panic during reshape - probably missing patch
Hello, do you have any update on this issue? Thanks, Kinga Tanska -- 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/1984117 Title: [VROC] Kernel panic during reshape - probably missing patch Status in linux package in Ubuntu: Confirmed Bug description: Bug found for Jammy (22.04) Steps to reproduce: 1. Create 3 partitions with parted tool on initial non-RAID drive # parted -s /dev/nvme6n1 mklabel gpt # parted -s /dev/nvme6n1 mkpart primary ext4 0% 30% # parted -s /dev/nvme6n1 mkpart primary btrfs 30% 60% # parted -s /dev/nvme6n1 mkpart primary xfs 60% 90% 2. Create filesystem on each partition # mkfs.ext4 /dev/nvme6n1p1 # mkfs.ext4 /dev/nvme6n1p2 # mkfs.ext4 /dev/nvme6n1p3 4. Create RAID container # mdadm --create /dev/md/imsm0 --metadata=imsm --raid-devices=4 /dev/nvme6n1 /dev/nvme4n1 /dev/nvme2n1 /dev/nvme1n1 --run –force 5. Create RAID on drive with data # mdadm --create /dev/md/volume --level=0 --chunk 64 --raid-devices=1 /dev/nvme6n1 --run –force 6. Make sure GPT data structures are in proper place # sgdisk -e /dev/md/volume 7. Grow temporary RAID 0 volume with two devices. Wait for reshape end. # mdadm --grow /dev/md/imsm0 --raid-devices=2 8. Grow temporary RAID 0 to RAID 10 # mdadm --grow /dev/md/volume --level=10 Results: Recovery starts but frozen. Kernel BUG occurs: [ 724.885252] md: recovery of RAID array md126 [ 724.885956] [ cut here ] [ 724.885960] kernel BUG at drivers/md/raid10.c:928! [ 724.891527] invalid opcode: [#1] SMP NOPTI [ 724.896736] CPU: 5 PID: 4872 Comm: md126_resync Not tainted 5.15.0-25-generic #25-Ubuntu [ 724.905943] Hardware name: Intel Corporation ArcherCity/ArcherCity, BIOS EGSDCRB1.SYS.0079.D34.2205030421 05/03/2022 [ 724.917839] RIP: 0010:raise_barrier+0x184/0x190 [raid10] [ 724.923896] Code: 89 f7 e8 4f c6 cf d4 e9 e5 fe ff ff 8b 8f ec 00 00 00 85 c9 74 14 4c 8d a7 dc 00 00 00 4c 89 e7 e8 91 7f 93 d5 e9 c7 fe ff ff <0f> 0b e8 35 9b 92 d5 0f 1f 44 00 00 0f 1f 44 00 00 55 48 89 e5 41 [ 724.945031] RSP: 0018:ff3c62714464fbd8 EFLAGS: 00010246 [ 724.950978] RAX: RBX: ff3282bd578e4c00 RCX: [ 724.959064] RDX: RSI: 0001 RDI: ff3282bd578e4c00 [ 724.967154] RBP: ff3c62714464fc28 R08: ff3282b9cf23ca00 R09: 0001 [ 724.975239] R10: 0293 R11: ff3282bcae577590 R12: ff3282b9cf23ca00 [ 724.983306] R13: 0003 R14: 0080 R15: ff3282bd578e4c00 [ 724.991405] FS: () GS:ff3282bcae54() knlGS: [ 725.000572] CS: 0010 DS: ES: CR0: 80050033 [ 725.007105] CR2: 7f086b758a50 CR3: 44010001 CR4: 00771ee0 [ 725.015209] DR0: DR1: DR2: [ 725.023295] DR3: DR6: fffe07f0 DR7: 0400 [ 725.031391] PKRU: 5554 [ 725.034514] Call Trace: [ 725.037360] [ 725.039787] ? bio_reset+0x12/0x50 [ 725.043721] ? raid10_alloc_init_r10buf+0x6d/0xc0 [raid10] [ 725.049966] raid10_sync_request+0x77c/0x1600 [raid10] [ 725.055832] md_do_sync.cold+0x42c/0xa17 [ 725.060331] md_thread+0xaa/0x160 [ 725.064144] ? md_write_inc+0x50/0x50 [ 725.068350] kthread+0x127/0x150 [ 725.072055] ? set_kthread_struct+0x50/0x50 [ 725.076850] ret_from_fork+0x1f/0x30 [ 725.080963] [ 725.083515] Modules linked in: xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp nft_compat nft_chain_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nft_counter bridge stp llc nf_tables nfnetlink nvme_fabrics intel_rapl_msr intel_rapl_common i10nm_edac nfit x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_realtek snd_hda_codec_generic kvm_intel ledtrig_audio kvm snd_hda_intel snd_intel_dspcfg snd_intel_sdw_acpi snd_hda_codec rapl snd_hda_core snd_hwdep snd_pcm snd_timer snd efi_pstore joydev input_leds isst_if_mbox_pci pmt_telemetry idxd pmt_crashlog isst_if_mmio mei_me soundcore pmt_class isst_if_common mei idxd_bus ipmi_ssif acpi_ipmi ipmi_si acpi_power_meter acpi_pad mac_hid sch_fq_codel dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ipmi_devintf ipmi_msghandler msr nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables autofs4 btrfs blake2b_generic zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor [ 725.083585] async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear dm_mirror dm_region_hash dm_log nvme nvme_core hid_generic usbhid ast i2c_algo_bit hid drm_vram_helper drm_ttm_helper ttm ax88179_178a drm_kms_helper usbnet syscopyarea uas mii sysfillrect usb_storage sysimgblt crct10dif_pclmul
[Kernel-packages] [Bug 1997151] Re: The volume from the microphone is very weak
** Description changed: - With the program Audacity, the missing gain can be estimated to about - 1000 (30dB). It does not matter whether an internal microphone, a - microphone on the Jack plug or on the Usb is used. + With the app "Audacity", the missing gain can be estimated to about 1000 + (30dB). It does not matter whether an internal microphone, a microphone + on the Jack plug or on the Usb is used. (Bluetooth is not tested.) - In the audio system settings a inactiv card "Renoir Radeon High - Definition Audio Controller" is shown. + In the audio system settings is an inactiv card "Renoir Radeon High + Definition Audio Controller" shown. The card cannot be activated. Ubuntu 5.15.0-53.59-generic 5.15.64 https://linux-hardware.org/?probe=124d4a2353 grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC236 ** Description changed: With the app "Audacity", the missing gain can be estimated to about 1000 (30dB). It does not matter whether an internal microphone, a microphone - on the Jack plug or on the Usb is used. (Bluetooth is not tested.) + on the Jack plug or on the Usb is used. (Bluetooth was not tested.) In the audio system settings is an inactiv card "Renoir Radeon High Definition Audio Controller" shown. The card cannot be activated. Ubuntu 5.15.0-53.59-generic 5.15.64 https://linux-hardware.org/?probe=124d4a2353 grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC236 ** Description changed: - With the app "Audacity", the missing gain can be estimated to about 1000 - (30dB). It does not matter whether an internal microphone, a microphone - on the Jack plug or on the Usb is used. (Bluetooth was not tested.) + With the app "Audacity", the missing gain can be estimated to about + factor 1000 (30dB). It does not matter whether an internal microphone, a + microphone on the Jack plug or on the Usb is used. (Bluetooth was not + tested.) In the audio system settings is an inactiv card "Renoir Radeon High Definition Audio Controller" shown. The card cannot be activated. Ubuntu 5.15.0-53.59-generic 5.15.64 https://linux-hardware.org/?probe=124d4a2353 grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC236 -- 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/1997151 Title: The volume from the microphone is very weak Status in linux package in Ubuntu: Confirmed Bug description: With the app "Audacity", the missing gain can be estimated to about factor 1000 (30dB). It does not matter whether an internal microphone, a microphone on the Jack plug or on the Usb is used. (Bluetooth was not tested.) In the audio system settings is an inactiv card "Renoir Radeon High Definition Audio Controller" shown. The card cannot be activated. Ubuntu 5.15.0-53.59-generic 5.15.64 https://linux-hardware.org/?probe=124d4a2353 grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC236 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997151/+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 1997151] Re: The channels for the microphones does not have enough volume.
** Description changed: With the program Audacity, the missing gain can be estimated to about - 1000 (30dB). It does not matter whether the internal microphone, a - microphone on the headset via the jack plug or a USB microphone is used. + 1000 (30dB). It does not matter whether an internal microphone, a + microphone on the plogin or on the Usb is used. - In the audio system settings a inactiv "Card Renoir Radeon High + In the audio system settings a inactiv card "Renoir Radeon High Definition Audio Controller" is shown. Ubuntu 5.15.0-53.59-generic 5.15.64 https://linux-hardware.org/?probe=124d4a2353 grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC236 ** Summary changed: - The channels for the microphones does not have enough volume. + The volume from the microphone is very weak ** Description changed: With the program Audacity, the missing gain can be estimated to about 1000 (30dB). It does not matter whether an internal microphone, a - microphone on the plogin or on the Usb is used. + microphone on the Jack plug or on the Usb is used. In the audio system settings a inactiv card "Renoir Radeon High Definition Audio Controller" is shown. Ubuntu 5.15.0-53.59-generic 5.15.64 https://linux-hardware.org/?probe=124d4a2353 grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC236 -- 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/1997151 Title: The volume from the microphone is very weak Status in linux package in Ubuntu: Confirmed Bug description: With the program Audacity, the missing gain can be estimated to about 1000 (30dB). It does not matter whether an internal microphone, a microphone on the Jack plug or on the Usb is used. In the audio system settings a inactiv card "Renoir Radeon High Definition Audio Controller" is shown. Ubuntu 5.15.0-53.59-generic 5.15.64 https://linux-hardware.org/?probe=124d4a2353 grep "Codec:" /proc/asound/card*/codec* /proc/asound/card0/codec#0:Codec: ATI R6xx HDMI /proc/asound/card1/codec#0:Codec: Realtek ALC236 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997151/+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 1842320] Re: Can't boot: "error: out of memory." immediately after the grub menu
can this be a solution ?
https://stackoverflow.com/questions/2895816/how-do-i-strip-local-
symbols-from-linux-kernel-module-without-breaking-it
--
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: https://github.com/os369510/grub2/tree/lp1842320
* If you built the package, then test grubx64.efi is under
[Kernel-packages] [Bug 1992118] Re: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel
** Changed in: hwe-next Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-intel-iotg-5.15 in Ubuntu. https://bugs.launchpad.net/bugs/1992118 Title: AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 intel IoTG kernel Status in HWE Next: Fix Released Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-intel-iotg-5.15 package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Bug description: [Summary] AX210 (8086:e024) WLAN init failed ucode -5 after upgrading to 5.15 Intel IoTG kernel. [Steps to reproduce] $ sudo apt update $ sudo apt upgrade $ reboot [Expected result] WLAN works with no problem. [Actual result] Can't detect WLAN. [Failure rate] 100% [Other Info] [4.485407] iwlwifi :02:00.0: enabling device ( -> 0002) [4.512442] iwlwifi :02:00.0: api flags index 2 larger than supported by driver [4.512500] iwlwifi :02:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.63.2.2 [4.514725] iwlwifi :02:00.0: loaded firmware version 66.f1c864e0.0 ty-a0-gf-a0-66.ucode op_mode iwlmvm [4.636133] iwlwifi :02:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420 [4.811565] iwlwifi :02:00.0: Detected RF GF, rfid=0x10d000 [4.812366] iwlwifi :02:00.0: Microcode SW error detected. Restarting 0x0. [4.812478] iwlwifi :02:00.0: Start IWL Error Log Dump: [4.812484] iwlwifi :02:00.0: Transport status: 0x004A, valid: 6 [4.812489] iwlwifi :02:00.0: Loaded firmware version: 66.f1c864e0.0 ty-a0-gf-a0-66.ucode [4.812494] iwlwifi :02:00.0: 0x0071 | NMI_INTERRUPT_UMAC_FATAL [4.812499] iwlwifi :02:00.0: 0x002002F0 | trm_hw_status0 [4.812503] iwlwifi :02:00.0: 0x | trm_hw_status1 [4.812507] iwlwifi :02:00.0: 0x004DA722 | branchlink2 [4.812510] iwlwifi :02:00.0: 0x004D0CCE | interruptlink1 [4.812514] iwlwifi :02:00.0: 0x004D0CCE | interruptlink2 [4.812517] iwlwifi :02:00.0: 0x004D94DA | data1 [4.812520] iwlwifi :02:00.0: 0x0010 | data2 [4.812523] iwlwifi :02:00.0: 0x | data3 [4.812527] iwlwifi :02:00.0: 0x | beacon time [4.812530] iwlwifi :02:00.0: 0x0001324E | tsf low [4.812533] iwlwifi :02:00.0: 0x | tsf hi [4.812536] iwlwifi :02:00.0: 0x | time gp1 [4.812540] iwlwifi :02:00.0: 0x000244E1 | time gp2 [4.812543] iwlwifi :02:00.0: 0x0001 | uCode revision type [4.812546] iwlwifi :02:00.0: 0x0042 | uCode version major [4.812550] iwlwifi :02:00.0: 0xF1C864E0 | uCode version minor [4.812553] iwlwifi :02:00.0: 0x0420 | hw version [4.812557] iwlwifi :02:00.0: 0x18C89002 | board version [4.812560] iwlwifi :02:00.0: 0x8008FF05 | hcmd [4.812563] iwlwifi :02:00.0: 0x0002 | isr0 [4.812566] iwlwifi :02:00.0: 0x6000 | isr1 [4.812569] iwlwifi :02:00.0: 0x48F2 | isr2 [4.812572] iwlwifi :02:00.0: 0x00C0001C | isr3 [4.812575] iwlwifi :02:00.0: 0x | isr4 [4.812578] iwlwifi :02:00.0: 0x | last cmd Id [4.812581] iwlwifi :02:00.0: 0x004D94DA | wait_event [4.812584] iwlwifi :02:00.0: 0x | l2p_control [4.812588] iwlwifi :02:00.0: 0x | l2p_duration [4.812591] iwlwifi :02:00.0: 0x | l2p_mhvalid [4.812594] iwlwifi :02:00.0: 0x | l2p_addr_match [4.812597] iwlwifi :02:00.0: 0x0009 | lmpm_pmg_sel [4.812600] iwlwifi :02:00.0: 0x | timestamp [4.812603] iwlwifi :02:00.0: 0x0024 | flow_handler [4.812640] iwlwifi :02:00.0: Start IWL Error Log Dump: [4.812643] iwlwifi :02:00.0: Transport status: 0x004A, valid: 7 [4.812647] iwlwifi :02:00.0: 0x2010070D | ADVANCED_SYSASSERT [4.812651] iwlwifi :02:00.0: 0x | umac branchlink1 [4.812654] iwlwifi :02:00.0: 0x8045DFC6 | umac branchlink2 [4.812658] iwlwifi :02:00.0: 0x010910FE | umac interruptlink1 [4.812661] iwlwifi :02:00.0: 0x | umac interruptlink2 [4.812664] iwlwifi :02:00.0: 0x0005 | umac data1 [4.812667] iwlwifi :02:00.0: 0xDEADBEEF | umac data2 [4.812670] iwlwifi :02:00.0: 0xDEADBEEF | umac data3 [4.812673] iwlwifi :02:00.0: 0x0042 | umac major [4.812677] iwlwifi :02:00.0: 0xF1C864E0 | umac minor [4.812680] iwlwifi :02:00.0: 0x000244D8 | frame pointer [4.812683] iwlwifi :02:00.0: 0xC0885E88 | stack pointer [4.812686] iwlwifi :02:00.0: 0x00010C00 | last host cmd [4.812689] iwlwifi :02:00.0: 0x | isr status reg [4.812702] iwlwifi
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-hwe-5.15/5.15.0.54.60~20.04.22)
All autopkgtests for the newly accepted linux-meta-hwe-5.15 (5.15.0.54.60~20.04.22) for focal have finished running. The following regressions have been reported in tests triggered by the package: glibc/2.31-0ubuntu9.9 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-hwe-5.15 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Fix Released Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Won't Fix Status in linux-azure-edge source package in Precise: Won't Fix Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Won't Fix Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Won't Fix Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera
Hi, This bug remains in linux-firmware (20220923.gitf09bebf3-0ubuntu1.1). Not fixed as the web camera still not starts on my XPS9320. linux-firmware (20220923.gitf09bebf3-0ubuntu1.1) kinetic; urgency=medium * Add support for Intel DG2 (LP: #1971712) - i915: Add GuC v70.5.1 for DG1, DG2, TGL and ADL-P * Miscellaneous Ubuntu changes - Initial dummy SRU release * Support Intel IPU6 MIPI camera (LP: #1987595) - SAUCE: intel-ipu6: update ipu6ep firmware - SAUCE: intel-ivsc: support more sensors - SAUCE: intel-ivsc: add more firmware * Realtek 8852c WiFi/BT firmware support (LP: #1995046) - rtw89: 8852c: update fw to v0.27.56.0 - rtw89: 8852c: update fw to v0.27.56.1 - rtl_bt: Update RTL8852C BT USB firmware to 0xD5B8_A40A * Add cs35l41 firmware loading support (LP: #1995957) - linux-firmware: Add firmware for Cirrus CS35L41 on HP Laptops - linux-firmware: Add firmware for Cirrus CS35L41 on Lenovo Laptops - linux-firmware: Add firmware for Cirrus CS35L41 on ASUS Laptops -- Juerg Haefliger Wed, 16 Nov 2022 16:12:23 +0100 -- 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/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: Fix Released 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: Fix Committed 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: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Status in linux source package in Lunar: Incomplete Status in linux-firmware source package in Lunar: Fix Released Status in linux-oem-5.17 source package in Lunar: Invalid Status in linux-oem-6.0 source package in Lunar: 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 1992714] Re: [SRU] SoF for RPL platform support
** Changed in: linux (Ubuntu Kinetic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Kinetic) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux (Ubuntu Lunar) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Lunar) Assignee: (unassigned) => AceLan Kao (acelankao) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-6.0 in Ubuntu. https://bugs.launchpad.net/bugs/1992714 Title: [SRU] SoF for RPL platform support Status in HWE Next: Fix Released Status in firmware-sof package in Ubuntu: Fix Released Status in linux package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: Invalid Status in firmware-sof source package in Jammy: Fix Released Status in linux source package in Jammy: Won't Fix Status in linux-oem-6.0 source package in Jammy: Fix Released Status in firmware-sof source package in Kinetic: Fix Released Status in linux source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: Invalid Status in firmware-sof source package in Lunar: Fix Released Status in linux source package in Lunar: In Progress Status in linux-oem-6.0 source package in Lunar: Invalid Bug description: [Impact] RPL platforms require new sof struct and firmware to enable its audio [Fix] Below 2 commits are from v6.1-rc1 63d375b9f2a9 ASoC: SOF: Intel: pci-tgl: use RPL specific firmware definitions 5f3db54cfbc2 ASoC: Intel: common: add ACPI matching tables for Raptor Lake Firmware are from here https://github.com/thesofproject/sof-bin/releases/tag/v2.2.2 [Test] Verified Dell machine which comes with rpl sdw audio. [Where problems could occur] Adding new struct, new ID, and new firmware, it won't affect old systems. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1992714/+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 1997201] Re: BlueZ 5.66 release
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1997201 Title: BlueZ 5.66 release Status in bluez package in Ubuntu: Triaged Bug description: Release to Lunar: http://www.bluez.org/release-of-bluez-5-66/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1997201/+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 1997346] 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 1997346 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/1997346 Title: AMD Rembrandt USB4 DPIA docking handling fixes Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: To improve the DP tunneling over docking scenario. Especially for S0i3 stress, Displays might be blank or system hang. Kernel panic can be observed when the issue occurs. [ 91.782291] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: drm_dp_dpcd_probe+0xea/0xf0 [drm_display_helper] ]--- *CC to stable(v6.0.y), need to pick into hwe-5.15 as well https://patchwork.freedesktop.org/patch/510829/ https://patchwork.freedesktop.org/patch/510825/ *CCed to stable(v6.0.3) and landed in oem-6.0-1007, need to pick into hwe-5.15 as well https://github.com/torvalds/linux/commit/876fcc4222e1d0e5b73343f4010a8b66be058f48 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997346/+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 1997346] [NEW] AMD Rembrandt USB4 DPIA docking handling fixes
Public bug reported: To improve the DP tunneling over docking scenario. Especially for S0i3 stress, Displays might be blank or system hang. Kernel panic can be observed when the issue occurs. [ 91.782291] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: drm_dp_dpcd_probe+0xea/0xf0 [drm_display_helper] ]--- *CC to stable(v6.0.y), need to pick into hwe-5.15 as well https://patchwork.freedesktop.org/patch/510829/ https://patchwork.freedesktop.org/patch/510825/ *CCed to stable(v6.0.3) and landed in oem-6.0-1007, need to pick into hwe-5.15 as well https://github.com/torvalds/linux/commit/876fcc4222e1d0e5b73343f4010a8b66be058f48 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1996194 ** Tags added: amd oem-priority originate-from-1996194 -- 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/1997346 Title: AMD Rembrandt USB4 DPIA docking handling fixes Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: To improve the DP tunneling over docking scenario. Especially for S0i3 stress, Displays might be blank or system hang. Kernel panic can be observed when the issue occurs. [ 91.782291] ---[ end Kernel panic - not syncing: stack-protector: Kernel stack is corrupted in: drm_dp_dpcd_probe+0xea/0xf0 [drm_display_helper] ]--- *CC to stable(v6.0.y), need to pick into hwe-5.15 as well https://patchwork.freedesktop.org/patch/510829/ https://patchwork.freedesktop.org/patch/510825/ *CCed to stable(v6.0.3) and landed in oem-6.0-1007, need to pick into hwe-5.15 as well https://github.com/torvalds/linux/commit/876fcc4222e1d0e5b73343f4010a8b66be058f48 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1997346/+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 1996892] Re: Expose built-in trusted and revoked certificates
** Changed in: linux (Ubuntu Kinetic) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Jammy) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Committed ** Changed in: linux (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1996892 Title: Expose built-in trusted and revoked certificates Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux source package in Lunar: Confirmed Bug description: [ Impact ] * Kernels have a set of builtin trusted and revoked certificates as a bundle * It is not very easy to access them, one needs to either download linux kernel package source code; or boot the kernel look up builtin hashes; and then find certificates externally * It would be more convenient for inspection to expose these in the buildinfo package, which already exposes auxiliary kernel information [ Test Plan ] * sudo apt install linux-buildinfo-$(uname -r) * check that /usr/lib/linux/$(uname -r)/canonical-certs.pem exists and contains livepatch cert * check that /usr/lib/linux/$(uname -r)/canonical-uefi-2012-all.pem exists and contains 2012 cert Example output: $ grep Subject: -r usr/lib/linux usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: CN = Canonical Ltd. Live Patch Signing usr/lib/linux/5.19.0-24-generic/canonical-certs.pem:Subject: C = GB, ST = Isle of Man, L = Douglas, O = Canonical Ltd., CN = Canonical Ltd. Kernel Module Signing usr/lib/linux/5.19.0-24-generic/canonical-revoked-certs.pem:Subject: C = GB, ST = Isle of Man, O = Canonical Ltd., OU = Secure Boot, CN = Canonical Ltd. Secure Boot Signing [ Where problems could occur ] * buildinfo is an auxiliary package not installed by default, but used by developer tooling and packaging. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1996892/+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 1997213] Re: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add
The command apport-collect couldn't run successfully on our system, we upload the file generate by sosreport command for your reference. ** Attachment added: "sosreport file" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+attachment/5632060/+files/sosreport-config23-2022-11-22-ecpwfxl.tar.xz ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1997213 Title: [Lenovo Ubuntu 22.04 Bug]SATA disk couldn't be recognized by "lsblk" after hot add Status in linux package in Ubuntu: Confirmed Bug description: Description: After installing Ubuntu 22.04 and boot to OS, we try to hot add a SATA disk to the Onboard AHCI controller in our system by plugging a SATA disk into the SATA slot, However, the OS can not recognize the added disks, both running command "lsblk" and "lsscsi", even "ll /sys/class/block/" couldn't find these disks we added before, and there isn't any log show up in /var/log/syslog after adding this SATA disks. Produce Steps: 1. Install Ubunut 22.04 (kernel 5.15.0-25.25-generic) 2. Boot into OS 3. Hot plug a SATA disk into SATA slot in the front bay 4. wait and observe whether the disks are show up by command "lsblk" Configuration: Systems：Lenovo SR655, AMD GENOA platform OS:ubuntu-22.04-live-server-amd64.iso CPU:AMD EPYC 9654 96-Core Processor *1 Memory:Hynix 32GB 2RX8 DDR5-4800 16Gbit RDIMM M-Die *12 storage： 7MM Drive 0-1：7.68TB 7MM NVMe SSD（PN：MTFDKCB7T6TFR，FW：E2MU110） Drive 0：240GB SATA SSD （PN：SSS7B07725 ，FW：MQ31） Drive 1-2：1.92TB NVMe SSD（PN：SSDPF2KX019T1O，FW：9CV10320） Drive 3-4：400GB NVMe SSD（PN：SSDPF21Q400GB，FW：L0310600） Drive 5-8：12.0TB SATA HDD（PN：01GV193，FW：LEGNK9R5） Drive 9：240GB SATA SSD（PN：SSS7B07725，FW：MQ31） Drive 10-11：960GB SATA SSD（PN：SSS7A43198，FW：MP33） Expected results: OS can recognize the SATA disks we hot added in. Actual results: OS cannot recognize SATA disks we hot added in. Additional info: 1. Hot add more SATA disks to different slot, "lsblk" couldn't show up the added disks as well. 2. Other OS like RHEL9.0 can recognize this hot added disks. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1997213/+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 1995573] Re: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536]
** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: In Progress => Fix Committed -- 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/1995573 Title: Screen cannot turn on after screen off with Matrox G200eW3 [102b:0536] Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux source package in Jammy: Won't Fix Status in linux-oem-5.17 source package in Jammy: Fix Committed Status in linux source package in Kinetic: Fix Committed Status in linux-oem-5.17 source package in Kinetic: Invalid Bug description: [Impact] Screen cannot turn on after screen is off [Fix] Below commit from v6.0-rc1 fixes the issue c577b2f43e80 drm/mgag200: Enable atomic gamma lut update And applied some other commits to fix the conflicts c48a36301634 drm/mgag200: Optimize damage clips 3064debaf55e drm/mgag200: Add FB_DAMAGE_CLIPS support 5913ab941d6e drm/mgag200: Acquire I/O lock while reading EDID 931e3f3a0e99 drm/mgag200: Protect concurrent access to I/O registers with lock e13f13e039dc drm: Add DRM-managed mutex_init() [Tests] Verified on the machine with Matrox G200eW3 [102b:0536] graphics card. [Where problems could occur] The commits to solve the conflicts are trivial, and not likely to introduce regressions. The fix patch change a lot of code and hard to evaluate the risk, but check the latest linus/master tree and linux-next/master tree, there is no fixed commit for all these cherry-picked commits, so should be safe to include them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995573/+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
