[Kernel-packages] [Bug 1987595] Re: Support Intel IPU6 MIPI camera
Firmware included in experimental firmware linux-firmware/jammy version 20220329.git681281e4-0ubuntu3.6+exp.56. To be SRUed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.17 in Ubuntu. https://bugs.launchpad.net/bugs/1987595 Title: Support Intel IPU6 MIPI camera Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-5.17 package in Ubuntu: Invalid Status in linux-oem-6.0 package in Ubuntu: Invalid Status in linux source package in Jammy: Invalid Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: Incomplete Status in linux-oem-5.17 source package in Kinetic: Invalid Status in linux-oem-6.0 source package in Kinetic: Invalid Bug description: This is a follow-up for bug 1964983 but on different platforms that runs linux-oem-5.17 or newer. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1987595/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL
** Changed in: ubuntu-z-systems Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#1989625, which made changes in the s390s IPL/boot area of kernel/arch/random. * The reason seems to be that the bad patch moves the decision about if arch randomness is available to setup.c function setup_randomness(). This code uses a static_key s390_arch_random_available. But in the Canonical kernel the initialization function for the jump labels (where the static keys are based on) jump_label_init() is called in generic start_kernel() wheres in the upstream kernel the init function is called early in setup_arch(). * Reverting this commit from bionic master-next makes bionic systems again bootable. (https://launchpad.net/~fheimes/+archive/ubuntu/test/) [ Test Plan ] * An IBM z14 or LinuxONE II or newer system is needed. * Now install latest bionic on that system - doesn't if it's on LPAR, z/VM or KVM. * After the installation (an the trigger of the post install reboot), the system will not come up. * To test a patched kernel with e4f74400308c can be tested in the following way: * Install 18.04 GA and prevent it from doing any kernel updates. * Means, install in 'island' mode or select in d-i 'Advanced Installation' and explicitly choose '4.15.0-50 generic' to install. * That allows the system to come up and to update the kernel to a modified one. * Then reboot and verify if the system comes up properly. [ Where problems could occur ] * Problems could occur due to the fact that the commit was not cleanly reversible because of minor context changes. * Adjustments that were needed might break other things if not done carefully. * Further commits (applied after e4f74400308c) may still rely on the bad e4f74400308c commit - or even further patches (from upstream stable). * In worst case IPL / boot might get broken, even on hardware older than z14. * If the revert works fine can be easily tested and was tested based on https://launchpad.net/~fheimes/+archive/ubuntu/test/ and the above test plan. [ Other Info ] * Ubuntu 20.04 (focal, using legacy image with virt-install) was tested as well, but is not affected by this issue. __ ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1988711] Re: Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
Hi Arvind,
The Kinetic (5.19) ones went in pretty easily and are likely to be in the
next SRU kernel for 5.19. The Jammy pull (5.15) is another story. In the
time it took for me to apply all 100ish patches and submit my tree, the
kernel team had made a ton of stable updates and when they went to apply my
changes for this, there were numerous conflicts and duplicates. So I'm
going to have to now go through all 100 or so patches and figure out what
needs to be pulled and what isn't cleanly applying otherwise.
Cheers
Jeff
--
Jeff Lane
Engineering Manager
IHV/OEM Alliances and Server Certification
"Entropy isn't what it used to be."
On Tue, Oct 18, 2022 at 6:40 AM Aravind Valloor Mana <
1988...@bugs.launchpad.net> wrote:
> Hi Jeff,
>
> Do you have the kernel version which has these lpfc patches integrated?
> If not, any ETA?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1988711
>
> Title:
> Update Broadcom Emulex FC HBA lpfc driver to 14.2.0.5 for Ubuntu 22.04
>
> Status in linux package in Ubuntu:
> In Progress
> Status in linux source package in Jammy:
> In Progress
> Status in linux source package in Kinetic:
> In Progress
>
> Bug description:
> [IMPACT/Justification]
> There are numerous bug fixes included in the more recent version of lpfc
> That Broadcom has asked to pull into Jammy and Kinetic to better support
> customers in the field who are using the GA kernel and cant or wont move to
> the HWE kernels. These all are limited to the lpfc driver itself, no
> patches to core code are requested.
>
> [FIX]
> A few of these were already landed in Jammy, and all but 6 (ones landed
> in 6.0 upstream) were already in Kinetic.
>
> b3d11f195cbb scsi: lpfc: Copyright updates for 14.2.0.5 patches
> 71faf8d30fdb scsi: lpfc: Update lpfc version to 14.2.0.5
> b21c9deb1479 scsi: lpfc: Refactor lpfc_nvmet_prep_abort_wqe() into
> lpfc_sli_prep_abort_xri()
> ffc566411ade scsi: lpfc: Revert RSCN_MEMENTO workaround for misbehaved
> configuration
> ea92e173dc55 scsi: lpfc: Fix lost NVMe paths during LIF bounce stress
> test
> 2f67dc7970bc scsi: lpfc: Fix possible memory leak when failing to issue
> CMF WQE
> 0948a9c53860 scsi: lpfc: Remove extra atomic_inc on cmd_pending in
> queuecommand after VMID
> 35251b4d79db scsi: lpfc: Set PU field when providing D_ID in
> XMIT_ELS_RSP64_CX iocb
> f8191d40aa61 scsi: lpfc: Prevent buffer overflow crashes in debugfs with
> malformed user input
> 4ecc9b0271a7 scsi: lpfc: Fix uninitialized cqe field in
> lpfc_nvme_cancel_iocb()
> 1af48fffd7ff scsi: lpfc: Update lpfc version to 14.2.0.4
> 2e7e9c0c1ec0 scsi: lpfc: Allow reduced polling rate for
> nvme_admin_async_event cmd completion
> ea7bd1f39331 scsi: lpfc: Add more logging of cmd and cqe information for
> aborted NVMe cmds
> 336d63615466 scsi: lpfc: Fix port stuck in bypassed state after LIP in
> PT2PT topology
> b1b3440f437b scsi: lpfc: Resolve NULL ptr dereference after an ELS LOGO
> is aborted
> 6f808bd78e82 scsi: lpfc: Address NULL pointer dereference after
> starget_to_rport()
> e27f05147bff scsi: lpfc: Resolve some cleanup issues following SLI path
> refactoring
> 24e1f056677e scsi: lpfc: Resolve some cleanup issues following abort
> path refactoring
> 44ba9786b673 scsi: lpfc: Correct BDE type for XMIT_SEQ64_WQE in
> lpfc_ct_reject_event()
> a5b168efba21 scsi: lpfc: Add support for ATTO Fibre Channel devices
> 348efeca7487 scsi: lpfc: Rework lpfc_vmid_get_appid() to be protocol
> independent
> ed913cf4a533 scsi: lpfc: Commonize VMID code location
> fcb9e738667c scsi: lpfc: Update lpfc version to 14.2.0.3
> a14396b6d139 scsi: lpfc: Use sg_dma_address() and sg_dma_len() macros
> for NVMe I/O
> e6f510414502 scsi: lpfc: Alter FPIN stat accounting logic
> de3ec318fee3 scsi: lpfc: Rework FDMI initialization after link up
> 5099478e436f scsi: lpfc: Change VMID registration to be based on fabric
> parameters
> dc8a71bd414f scsi: lpfc: Decrement outstanding gidft_inp counter if
> lpfc_err_lost_link()
> 4a0f4aff3ce5 scsi: lpfc: Use list_for_each_entry_safe() in
> rscn_recovery_check()
> 596fc8adb171 scsi: lpfc: Fix dmabuf ptr assignment in
> lpfc_ct_reject_event()
> ead76d4c09b8 scsi: lpfc: Inhibit aborts if external loopback plug is
> inserted
> b7e952cbc63c scsi: lpfc: Fix ndlp put following a LOGO completion
> ba3d58a1df46 scsi: lpfc: Fill in missing ndlp kref puts in error paths
> 84c6f99e3907 scsi: lpfc: Fix element offset in
> __lpfc_sli_release_iocbq_s4()
> 775266207105 scsi: lpfc: Correct BDE DMA address assignment for
> GEN_REQ_WQE
> cc28fac16ab7 scsi: lpfc: Fix split code for FLOGI on FCoE
> c2024e3b33ee scsi: lpfc: Remove redundant lpfc_sli_prep_wqe() call
> 92bd903da12b scsi: lpfc: Fix additional reference counting in
> lpfc_bsg_rport_els()
> db05628435aa blk-cgroup: move blkcg_{get,set}_fc_appid out of line
> 646db1a560f4 scsi: lpfc: Fix res
[Kernel-packages] [Bug 1995046] [NEW] Realtek 8852c WiFi/BT firmware support
Public bug reported: Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add both FW & config file to get it work with oem-6.0. WiFi: rtw8852c [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003) [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5 BT: rtl8852cu [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90 ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Kinetic) Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Tags: amd oem-priority originate-from-1994523 ** Also affects: linux-firmware (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Kinetic) Importance: Undecided Status: New ** Tags added: amd oem-priority originate-from-1994523 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1995046 Title: Realtek 8852c WiFi/BT firmware support Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-firmware source package in Jammy: New Status in linux-firmware source package in Kinetic: New Status in linux-firmware source package in Lunar: New Bug description: Some OEM design RTK-8852c as WiFi/BT solution on new platform, need to add both FW & config file to get it work with oem-6.0. WiFi: rtw8852c [ 2.628042] rtw89_8852ce :02:00.0: enabling device ( -> 0003) [ 2.628647] rtw89_8852ce :02:00.0: Direct firmware load for rtw89/rtw8852c_fw.bin failed with error -2 [ 2.628663] rtw89_8852ce :02:00.0: failed to request firmware [ 2.644819] rtw89_8852ce :02:00.0: failed to wait firmware completion [ 2.644843] rtw89_8852ce :02:00.0: failed to setup chip information [ 2.649823] rtw89_8852ce: probe of :02:00.0 failed with error -22 https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=d2aac63b8381c0633de00476a7f3d8f436ea4bc5 BT: rtl8852cu [ 2.476240] Bluetooth: hci0: RTL: loading rtl_bt/rtl8852cu_fw.bin [ 2.476441] Bluetooth: hci0: RTL: firmware file rtl_bt/rtl8852cu_fw.bin not found https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=8a2d811764e7fcc9e2862549f91487770b70563b https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux- firmware.git/commit/?id=cfbd6681696ba4b5eed279f28983d6a87cd6fd90 To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1995046/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874186] Re: vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests failed with timeout
https://lore.kernel.org/kvm/y1lhjojxn4fom...@google.com/T/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1874186 Title: vmx_vmcs_shadow_test from ubuntu_kvm_unit_tests failed with timeout Status in ubuntu-kernel-tests: In Progress Status in linux-kvm package in Ubuntu: Invalid Bug description: Issue found on E-KVM 5.3.0-1016.17-kvm and can be reproduced on 5.3.0-1015-kvm as well, thus this is not a regression. PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMWRITE (in 21056 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMWRITE (1) are as expected (1) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: shadowed for VMREAD (in 20236 cycles) PASS: invalid link pointer: field 6000: VMREAD and VMWRITE permission: ALU flags after VMREAD (1) are as expected (1) qemu-system-x86_64: terminating on signal 15 from pid 2874 (timeout) FAIL vmx_vmcs_shadow_test (timeout; duration=180) Need to test it with a longer timeout setting. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-1015-kvm 5.3.0-1015.16 ProcVersionSignature: User Name 5.3.0-1015.16-kvm 5.3.18 Uname: Linux 5.3.0-1015-kvm x86_64 ApportVersion: 2.20.11-0ubuntu8.8 Architecture: amd64 Date: Wed Apr 22 04:37:11 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1874186/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837326] Re: platform eisa.0: EISA: Cannot allocate resource for mainboard
The CONFIG_EISA and related flags only affect compilation. They will not affect an already compiled kernel. @Bram: how did you apply the kernel parameters? I tried using the bootconfig tool, compiling it from the ubuntu-kernel source, but they do not seem to loaded when I try cat /proc/bootconfig. -- 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/1837326 Title: platform eisa.0: EISA: Cannot allocate resource for mainboard Status in linux package in Ubuntu: Confirmed Bug description: dmesg: [0.889531] platform eisa.0: EISA: Cannot allocate resource for mainboard [0.889533] platform eisa.0: Cannot allocate resource for EISA slot 1 [0.889535] platform eisa.0: Cannot allocate resource for EISA slot 2 [0.889536] platform eisa.0: Cannot allocate resource for EISA slot 3 [0.889537] platform eisa.0: Cannot allocate resource for EISA slot 4 [0.889539] platform eisa.0: Cannot allocate resource for EISA slot 5 [0.889540] platform eisa.0: Cannot allocate resource for EISA slot 6 [0.889541] platform eisa.0: Cannot allocate resource for EISA slot 7 [0.889542] platform eisa.0: Cannot allocate resource for EISA slot 8 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.2.0-8-generic 5.2.0-8.9 ProcVersionSignature: Ubuntu 5.2.0-8.9-generic 5.2.0 Uname: Linux 5.2.0-8-generic x86_64 ApportVersion: 2.20.11-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 3028 F pulseaudio /dev/snd/pcmC0D0p: caravena 3028 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sun Jul 21 12:16:07 2019 HibernationDevice: RESUME=UUID=efcf081f-0bb0-4907-b78c-1299aa4aee57 InstallationDate: Installed on 2018-12-02 (230 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: HP HP Pavilion x360 Convertible 14-cd0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.2.0-8-generic root=UUID=28bdadba-133c-4f5b-a5c9-b06993ea7ce2 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.2.0-8-generic N/A linux-backports-modules-5.2.0-8-generic N/A linux-firmware 1.181 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2018-12-02 (230 days ago) dmi.bios.date: 04/29/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.34 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 8486 dmi.board.vendor: HP dmi.board.version: 72.23 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.34:bd04/29/2019:svnHP:pnHPPavilionx360Convertible14-cd0xxx:pvrType1ProductConfigId:rvnHP:rn8486:rvr72.23:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion x360 Convertible 14-cd0xxx dmi.product.sku: 3PX63LA#ABM dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837326/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995040] Re: test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on B-azure-5.4 ARM64 instance Standard_D2pds_v5
This can be found with Focal Azure 5.4.0-1094.100 on ARM64 instance Standard_D2pds_v5 as well (this node was added to the pool since that kernel) ** Tags added: focal ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released -- 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/1995040 Title: test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on B-azure-5.4 ARM64 instance Standard_D2pds_v5 Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: New Bug description: Issue found with Bionic Azure 5.4.0-1095.101~18.04.1 on ARM64 instance Standard_D2pds_v5 This failure can be found with 5.4.0-1094.100~18.04.1 as well. With which we have this ARM64 instance added to the pool. Test failed with: Running 'python2 ./test-kernel-security.py -v KernelSecurityConfigTest.test_320_config_arm_pan' Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: '5.4.0-1095.101~18.04.1 (Ubuntu 5.4.0-1095.101~18.04.1-azure 5.4.212)' arch: 'arm64' uid: 0/0 SUDO_USER: 'azure') test_320_config_arm_pan (__main__.KernelSecurityConfigTest) Ensure PAN for arm processors is set ... (arm64 processor, looking for CONFIG_ARM64_SW_TTBR0_PAN) FAIL == FAIL: test_320_config_arm_pan (__main__.KernelSecurityConfigTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2782, in test_320_config_arm_pan self.assertKernelConfig(config_name, expected) File "./test-kernel-security.py", line 231, in assertKernelConfig self.assertKernelConfigSet(name) File "./test-kernel-security.py", line 218, in assertKernelConfigSet '%s option was expected to be set in the kernel config' % name) AssertionError: ARM64_SW_TTBR0_PAN option was expected to be set in the kernel config -- Ran 1 test in 0.003s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1995040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995040] [NEW] test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on B-azure-5.4 ARM64 instance Standard_D2pds_v5
Public bug reported: Issue found with Bionic Azure 5.4.0-1095.101~18.04.1 on ARM64 instance Standard_D2pds_v5 This failure can be found with 5.4.0-1094.100~18.04.1 as well. With which we have this ARM64 instance added to the pool. Test failed with: Running 'python2 ./test-kernel-security.py -v KernelSecurityConfigTest.test_320_config_arm_pan' Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: '5.4.0-1095.101~18.04.1 (Ubuntu 5.4.0-1095.101~18.04.1-azure 5.4.212)' arch: 'arm64' uid: 0/0 SUDO_USER: 'azure') test_320_config_arm_pan (__main__.KernelSecurityConfigTest) Ensure PAN for arm processors is set ... (arm64 processor, looking for CONFIG_ARM64_SW_TTBR0_PAN) FAIL == FAIL: test_320_config_arm_pan (__main__.KernelSecurityConfigTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2782, in test_320_config_arm_pan self.assertKernelConfig(config_name, expected) File "./test-kernel-security.py", line 231, in assertKernelConfig self.assertKernelConfigSet(name) File "./test-kernel-security.py", line 218, in assertKernelConfigSet '%s option was expected to be set in the kernel config' % name) AssertionError: ARM64_SW_TTBR0_PAN option was expected to be set in the kernel config -- Ran 1 test in 0.003s FAILED (failures=1) ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Tags: 5.4 azure bionic focal sru-20221010 ubuntu-qrt-kernel-security ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Summary changed: - test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on B-azure-5.4 + test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on B-azure-5.4 ARM64 instance Standard_D2pds_v5 -- 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/1995040 Title: test_320_config_arm_pan from ubuntu_qrt_kernel_security failed on B-azure-5.4 ARM64 instance Standard_D2pds_v5 Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: New Bug description: Issue found with Bionic Azure 5.4.0-1095.101~18.04.1 on ARM64 instance Standard_D2pds_v5 This failure can be found with 5.4.0-1094.100~18.04.1 as well. With which we have this ARM64 instance added to the pool. Test failed with: Running 'python2 ./test-kernel-security.py -v KernelSecurityConfigTest.test_320_config_arm_pan' Running test: './test-kernel-security.py' distro: 'Ubuntu 18.04' kernel: '5.4.0-1095.101~18.04.1 (Ubuntu 5.4.0-1095.101~18.04.1-azure 5.4.212)' arch: 'arm64' uid: 0/0 SUDO_USER: 'azure') test_320_config_arm_pan (__main__.KernelSecurityConfigTest) Ensure PAN for arm processors is set ... (arm64 processor, looking for CONFIG_ARM64_SW_TTBR0_PAN) FAIL == FAIL: test_320_config_arm_pan (__main__.KernelSecurityConfigTest) Ensure PAN for arm processors is set -- Traceback (most recent call last): File "./test-kernel-security.py", line 2782, in test_320_config_arm_pan self.assertKernelConfig(config_name, expected) File "./test-kernel-security.py", line 231, in assertKernelConfig self.assertKernelConfigSet(name) File "./test-kernel-security.py", line 218, in assertKernelConfigSet '%s option was expected to be set in the kernel config' % name) AssertionError: ARM64_SW_TTBR0_PAN option was expected to be set in the kernel config -- Ran 1 test in 0.003s FAILED (failures=1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1995040/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995041] [NEW] Fix ath11k deadlock on WCN6855
Public bug reported: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched_curr+0x52/0xc0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule+0x55/0xd0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: schedule_timeout+0x115/0x150 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? raw_spin_rq_unlock+0x10/0x30 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? try_to_wake_up+0x211/0x600 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_ce_send+0x17a/0x2e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: wait_for_completion+0x8b/0xf0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __flush_work.isra.0+0x171/0x270 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? flush_workqueue_prep_pwqs+0x140/0x140 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __cancel_work_timer+0x11b/0x1a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? ath11k_mac_config_mon_status_default+0xcc/0x170 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: cancel_work_sync+0x10/0x20 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ath11k_mac_op_stop+0x9f/0x1e0 [ath11k] Aug 19 01:29:28 Thor-P3-AMD-2 kernel: drv_stop+0x45/0x110 [mac80211] [Fix] Fix this by switching from using regulatory_set_wiphy_regd_sync() to regulatory_set_wiphy_regd(). Now cfg80211 will schedule another workqueue which handles the locking on it's own. So the ath11k workqueue can simply exit without taking any locks, avoiding the deadlock. [Test] Verified on hardware, stress reboot and suspend 30 times OK. [Where problems could occur] It may break ath11k wifi driver. ** Affects: hwe-next Importance: Undecided Assignee: AaronMa (mapengyu) Status: In Progress ** Affects: linux (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Jammy) Importance: Undecided Status: In Progress ** Affects: linux (Ubuntu Kinetic) Importance: Undecided Status: In Progress ** Affects: linux-oem-5.17 (Ubuntu Kinetic) Importance: Undecided Status: In Progress ** Affects: linux-oem-6.0 (Ubuntu Kinetic) Importance: Undecided Status: In Progress ** Tags: oem-priority originate-from-1981178 sutton ** Tags added: oem-priority originate-from-1981178 sutton ** Also affects: linux (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Kinetic) Importance: Undecided Status: New ** Also affects: linux-oem-5.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.0 (Ubuntu) Importance: Undecided Status: New ** Changed in: hwe-next Assignee: (unassigned) => AaronMa (mapengyu) ** Changed in: linux (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-5.17 (Ubuntu Kinetic) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-oem-6.0 (Ubuntu Kinetic) Status: New => In Progress ** Changed in: hwe-next Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1995041 Title: Fix ath11k deadlock on WCN6855 Status in HWE Next: In Progress Status in linux package in Ubuntu: In Progress Status in linux-oem-5.17 package in Ubuntu: In Progress Status in linux-oem-6.0 package in Ubuntu: In Progress Status in linux source package in Jammy: In Progress Status in linux-oem-5.17 source package in Jammy: In Progress Status in linux-oem-6.0 source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Status in linux-oem-5.17 source package in Kinetic: In Progress Status in linux-oem-6.0 source package in Kinetic: In Progress Bug description: [Impact] ath11k is in deadlock when stress reboot or suspend on WCN6855. sometimes kernel hang. Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Call Trace: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: Aug 19 01:29:28 Thor-P3-AMD-2 kernel: __schedule+0x240/0x5a0 Aug 19 01:29:28 Thor-P3-AMD-2 kernel: ? resched
[Kernel-packages] [Bug 1995037] Re: OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI
** Description changed: During boot, latest Jammy Jellyfish (22.04.1 LTS) kernel crashes while - running in a VM. + running in a VM. The issue is repeatable and stable (not intermittent). exact kernel: "linux-image-5.15.0.52-generic" "5.15.0-52.58" WARNING: Logs extracted by booting with ISO and chrooting, so the apport-bug tool likely reported some wrong info, like the exact kernel version. Similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215 + + + + BOOT LOG + + -- Boot da94cf3252ed4733beeb896109b6f844 -- + Oct 28 05:04:44 data3 kernel: Linux version 5.15.0-52-generic (buildd@lcy02-amd64-032) (gcc (Ubuntu 11.2.0-19ubuntu1) 11.2.0, GNU ld (GNU Binutils for Ubuntu) 2.38) #58-Ubuntu SMP Thu Oct 13 08:03:55 UTC 2022 (Ubuntu 5.15.0-52.58-generic 5.15.60) + Oct 28 05:04:44 data3 kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=ed4c6bf6-c0e4-4aae-997f-fc7c5e4dc95a ro console=tty0 console=ttyS0,115200n8 tsc=reliable earlyprintk + te: 2022-10-28 + + [...] + + Oct 28 05:04:46 data3 kernel: random: crng init done + Oct 28 05:04:46 data3 kernel: random: 119 urandom warning(s) missed due to ratelimiting + Oct 28 05:04:47 data3 kernel: Adding 1996796k swap on /dev/vda2. Priority:-2 extents:1 across:1996796k FS + Oct 28 05:04:47 data3 kernel: spl: loading out-of-tree module taints kernel. + Oct 28 05:04:47 data3 kernel: znvpair: module license 'CDDL' taints kernel. + Oct 28 05:04:47 data3 kernel: Disabling lock debugging due to kernel taint + Oct 28 05:04:47 data3 kernel: invalid opcode: [#1] SMP PTI + Oct 28 05:04:47 data3 kernel: CPU: 0 PID: 457 Comm: modprobe Tainted: P O 5.15.0-52-generic #58-Ubuntu + Oct 28 05:04:47 data3 kernel: Hardware name: Joyent SmartDC HVM, BIOS Bochs 01/01/2007 + Oct 28 05:04:47 data3 kernel: RIP: 0010:kfpu_begin+0x30/0x70 [zcommon] + Oct 28 05:04:47 data3 kernel: Code: ff ff ff 48 8b 15 c0 95 00 00 65 8b 05 c1 e3 7d 3f 48 98 48 8b 3c c2 48 c7 c0 00 5c 23 be 0f 1f 44 00 00 b8 ff ff ff ff 89 c2 <0f> c7 2f 5d c3 cc cc cc cc 0f 1f 44 00 00 b8 ff ff ff ff 89 c2 0f + Oct 28 05:04:47 data3 kernel: RSP: 0018:be88c024b9c8 EFLAGS: 00010002 + Oct 28 05:04:47 data3 kernel: RAX: RBX: 952ad32a RCX: + Oct 28 05:04:47 data3 kernel: RDX: RSI: 952ad32a RDI: 952ad254b000 + Oct 28 05:04:47 data3 kernel: RBP: be88c024b9c8 R08: c083d9a0 R09: 00552ea95dfff000 + Oct 28 05:04:47 data3 kernel: R10: 00fedcb3a0ad3000 R11: 0552bfffe000 R12: 952ad32c + Oct 28 05:04:47 data3 kernel: R13: be88c024ba00 R14: 0002 R15: 0001d3079fe4 + Oct 28 05:04:47 data3 kernel: FS: 7fadc002fc40() GS:952b3dc0() knlGS: + Oct 28 05:04:47 data3 kernel: CS: 0010 DS: ES: CR0: 80050033 + Oct 28 05:04:47 data3 kernel: CR2: 5583b957ddb8 CR3: 0fcbe000 CR4: 06f0 + Oct 28 05:04:47 data3 kernel: Call Trace: + Oct 28 05:04:47 data3 kernel: + Oct 28 05:04:47 data3 kernel: fletcher_4_sse2_byteswap+0x1d/0x90 [zcommon] + Oct 28 05:04:47 data3 kernel: fletcher_4_byteswap_impl+0x58/0x90 [zcommon] + Oct 28 05:04:47 data3 kernel: ? __alloc_pages+0x17e/0x330 + Oct 28 05:04:47 data3 kernel: ? __mod_lruvec_page_state+0x99/0xb0 + Oct 28 05:04:47 data3 kernel: ? kmalloc_large_node+0x98/0xe0 + Oct 28 05:04:47 data3 kernel: ? ktime_get_raw_ts64+0x47/0xe0 + Oct 28 05:04:47 data3 kernel: fletcher_4_byteswap+0x67/0xb0 [zcommon] + Oct 28 05:04:47 data3 kernel: ? fletcher_4_byteswap_impl+0x90/0x90 [zcommon] + Oct 28 05:04:47 data3 kernel: fletcher_4_benchmark_impl.constprop.0+0xc1/0x2c0 [zcommon] + Oct 28 05:04:47 data3 kernel: fletcher_4_benchmark+0xb1/0x100 [zcommon] + Oct 28 05:04:47 data3 kernel: fletcher_4_init+0xe/0x90 [zcommon] + Oct 28 05:04:47 data3 kernel: zcommon_init+0x1c/0x1000 [zcommon] + Oct 28 05:04:47 data3 kernel: ? 0xc085 + Oct 28 05:04:47 data3 kernel: do_one_initcall+0x49/0x1e0 + Oct 28 05:04:47 data3 kernel: ? kmem_cache_alloc_trace+0x19e/0x2e0 + Oct 28 05:04:47 data3 kernel: do_init_module+0x52/0x260 + Oct 28 05:04:47 data3 kernel: load_module+0xb2b/0xbc0 + Oct 28 05:04:47 data3 kernel: __do_sys_finit_module+0xbf/0x120 + Oct 28 05:04:47 data3 kernel: __x64_sys_finit_module+0x18/0x20 + Oct 28 05:04:47 data3 kernel: do_syscall_64+0x5c/0xc0 + Oct 28 05:04:47 data3 kernel: ? exit_to_user_mode_prepare+0x37/0xb0 + Oct 28 05:04:47 data3 kernel: ? syscall_exit_to_user_mode+0x27/0x50 + Oct 28 05:04:47 data3 kernel: ? __x64_sys_mmap+0x33/0x50 + Oct 28 05:04:47 data3 kernel: ? do_syscall_64+0x69/0xc0 + Oct 28 05:04:47 data3 kernel: ? do_syscall_64+0x69/0xc0 + Oct 28 05:04:47 data3 kernel: ? syscall_exit_to_user_mode+0x27/0x50 + Oct 28 05:04:47 data3 kernel: ? __
[Kernel-packages] [Bug 1987964] Re: Read-Only crash on Samsung Galaxy Book S (Intel)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- 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/1987964 Title: Read-Only crash on Samsung Galaxy Book S (Intel) Status in linux package in Ubuntu: Expired Bug description: Ubuntu 22.04 LTS (Kernel updated to version 5.18.19) has chronic read- only crashes when using Samsung KLUFG8RHDA-B2D1, the UFS of Samsung Galaxy Book S (Intel) - SAMSUNG ELECTRONICS CO., LTD. 767XCL And from Kernel version 5.19 onwards, it doesn't even boot, it stops on "initramfs". --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-08-18 (10 days ago) InstallationMedia: Ubuntu 22.04.1 2022.08.17 LTS "Custom Jammy Jellyfish" (20220817) Package: linux (not installed) Tags: jammy Uname: Linux 5.18.19-051819-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1987964/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995037] 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/1995037 Title: OOPs on boot: invalid opcode: [#1] SMP NOPTI Status in linux package in Ubuntu: Confirmed Bug description: During boot, latest Jammy Jellyfish (22.04.1 LTS) kernel crashes while running in a VM. exact kernel: "linux-image-5.15.0.52-generic" "5.15.0-52.58" WARNING: Logs extracted by booting with ISO and chrooting, so the apport-bug tool likely reported some wrong info, like the exact kernel version. Similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: cfg80211 intel_rapl_msr intel_rapl_common mac_hid bochs i2c_piix4 pata_acpi AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 28 05:07 seq crw-rw+ 1 root audio 116, 33 Oct 28 05:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Fri Oct 28 05:43:18 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Joyent SmartDC HVM PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-24 (3 days ago) WifiSyslog: dmi.bios.date: 01/01/2007 dmi.bios.release: 1.0 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:br1.0:svnJoyent:pnSmartDCHVM:pvr7.20220519T001745Z:cvnBochs:ct1:cvr:sku001: dmi.product.family: Virtual Machine dmi.product.name: SmartDC HVM dmi.product.sku: 001 dmi.product.version: 7.20220519T001745Z dmi.sys.vendor: Joyent To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1995037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995037] [NEW] OOPs on boot: invalid opcode: 0000 [#1] SMP NOPTI
Public bug reported: During boot, latest Jammy Jellyfish (22.04.1 LTS) kernel crashes while running in a VM. exact kernel: "linux-image-5.15.0.52-generic" "5.15.0-52.58" WARNING: Logs extracted by booting with ISO and chrooting, so the apport-bug tool likely reported some wrong info, like the exact kernel version. Similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: cfg80211 intel_rapl_msr intel_rapl_common mac_hid bochs i2c_piix4 pata_acpi AlsaDevices: total 0 crw-rw+ 1 root audio 116, 1 Oct 28 05:07 seq crw-rw+ 1 root audio 116, 33 Oct 28 05:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Fri Oct 28 05:43:18 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Joyent SmartDC HVM PciMultimedia: ProcEnviron: TERM=linux PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz --- RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-24 (3 days ago) WifiSyslog: dmi.bios.date: 01/01/2007 dmi.bios.release: 1.0 dmi.bios.vendor: Bochs dmi.bios.version: Bochs dmi.chassis.type: 1 dmi.chassis.vendor: Bochs dmi.modalias: dmi:bvnBochs:bvrBochs:bd01/01/2007:br1.0:svnJoyent:pnSmartDCHVM:pvr7.20220519T001745Z:cvnBochs:ct1:cvr:sku001: dmi.product.family: Virtual Machine dmi.product.name: SmartDC HVM dmi.product.sku: 001 dmi.product.version: 7.20220519T001745Z dmi.sys.vendor: Joyent ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug jammy uec-images ** Description changed: During boot, latest Jammy Jellyfish (22.04.1 LTS) kernel crashes while running in a VM. exact kernel: "linux-image-5.15.0.52-generic" "5.15.0-52.58" - Logs extracted by booting with ISO and chrooting. + WARNING: Logs extracted by booting with ISO and chrooting, so the + apport-bug tool likely reported some wrong info, like the exact kernel + version. Similar to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1942215 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: cfg80211 intel_rapl_msr intel_rapl_common mac_hid bochs i2c_piix4 pata_acpi AlsaDevices: - total 0 - crw-rw+ 1 root audio 116, 1 Oct 28 05:07 seq - crw-rw+ 1 root audio 116, 33 Oct 28 05:07 timer + total 0 + crw-rw+ 1 root audio 116, 1 Oct 28 05:07 seq + crw-rw+ 1 root audio 116, 33 Oct 28 05:07 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: unknown Date: Fri Oct 28 05:43:18 2022 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: - Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet - Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub + Bus 001 Device 002: ID 0627:0001 Adomax Technology Co., Ltd QEMU USB Tablet + Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Lsusb-t: - /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M - |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M + /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=uhci_hcd/2p, 12M + |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Joyent SmartDC HVM PciMultimedia: - + ProcEnviron: - TERM=linux - PATH=(custom, no user) - LANG=C.UTF-8 - SHELL=/bin/bash + TERM=linux + PATH=(custom, no user) + LANG=C.UTF-8 + SHELL=/bin/bash ProcFB: 0 bochs-drmdrmfb ProcKernelCmdLine
[Kernel-packages] [Bug 1970074] Re: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41
Any updates? -- 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/1970074 Title: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 Status in linux package in Ubuntu: Confirmed Bug description: Something wrong with ata driver in dmesg found: [1.980693] kernel: [1.980699] kernel: fbcon: Taking over console [1.980703] kernel: UBSAN: array-index-out-of-bounds in /build/linux-9H675w/linux-5.15.0/drivers/ata/libahci.c:968:41 [1.980709] kernel: index 15 is out of range for type 'ahci_em_priv [8]' [1.980713] kernel: CPU: 0 PID: 209 Comm: scsi_eh_8 Not tainted 5.15.0-25-generic #25-Ubuntu [1.980716] kernel: Hardware name: System manufacturer System Product Name/P5Q3, BIOS 110206/11/2010 [1.980718] kernel: Call Trace: [1.980721] kernel: [1.980723] kernel: show_stack+0x52/0x58 [1.980729] kernel: dump_stack_lvl+0x4a/0x5f [1.980734] kernel: dump_stack+0x10/0x12 [1.980736] kernel: ubsan_epilogue+0x9/0x45 [1.980739] kernel: __ubsan_handle_out_of_bounds.cold+0x44/0x49 [1.980742] kernel: ahci_qc_issue+0x166/0x170 [libahci] [1.980748] kernel: ata_qc_issue+0x135/0x240 [1.980752] kernel: ata_exec_internal_sg+0x2c4/0x580 [1.980754] kernel: ? vprintk_default+0x1d/0x20 [1.980759] kernel: ata_exec_internal+0x67/0xa0 [1.980762] kernel: sata_pmp_read+0x8d/0xc0 [1.980765] kernel: sata_pmp_read_gscr+0x3c/0x90 [1.980768] kernel: sata_pmp_attach+0x8b/0x310 [1.980771] kernel: ata_eh_revalidate_and_attach+0x28c/0x4b0 [1.980775] kernel: ata_eh_recover+0x6b6/0xb30 [1.980778] kernel: ? ahci_do_hardreset+0x180/0x180 [libahci] [1.980783] kernel: ? ahci_stop_engine+0xb0/0xb0 [libahci] [1.980787] kernel: ? ahci_do_softreset+0x290/0x290 [libahci] [1.980792] kernel: ? trace_event_raw_event_ata_eh_link_autopsy_qc+0xe0/0xe0 [1.980795] kernel: sata_pmp_eh_recover.isra.0+0x214/0x560 [1.980799] kernel: sata_pmp_error_handler+0x23/0x40 [1.980802] kernel: ahci_error_handler+0x43/0x80 [libahci] [1.980806] kernel: ata_scsi_port_error_handler+0x2b1/0x600 [1.980810] kernel: ata_scsi_error+0x9c/0xd0 [1.980813] kernel: scsi_error_handler+0xa1/0x180 [1.980817] kernel: ? scsi_unjam_host+0x1c0/0x1c0 [1.980820] kernel: kthread+0x12a/0x150 [1.980823] kernel: ? set_kthread_struct+0x50/0x50 [1.980826] kernel: ret_from_fork+0x22/0x30 [1.980831] kernel: ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-25-generic 5.15.0-25.25 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: eugene16798 F pulseaudio /dev/snd/pcmC0D0p: eugene16798 F...m pulseaudio /dev/snd/controlC1: eugene16798 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Sun Apr 24 05:13:34 2022 HibernationDevice: RESUME=UUID=7e115b53-56a4-444f-bd93-6ad4f15c4a61 InstallationDate: Installed on 2019-04-13 (1106 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) IwConfig: lono wireless extensions. enp2s0no wireless extensions. virbr0no wireless extensions. MachineType: System manufacturer System Product Name ProcEnviron: LANGUAGE= PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.15.0-25-generic root=UUID=d87288b4-dbdd-4448-8088-4ebb6ed6cf33 ro rootflags=subvol=@ quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-25-generic N/A linux-backports-modules-5.15.0-25-generic N/A linux-firmware 20220329.git681281e4-0ubuntu1 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-22 (1 days ago) dmi.bios.date: 06/11/2010 dmi.bios.release: 11.2 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1102 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: P5Q3 dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1102:bd06/11/2010:br11.2:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q3:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:skuToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M.
[Kernel-packages] [Bug 1990434] Re: Bionic update: upstream stable patchset 2022-09-21
"s390/archrandom: prevent CPACF trng invocations in interrupt context" is being dropped from the current cycle as the patch that it was fixing is getting reverted. -- 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/1990434 Title: Bionic update: upstream stable patchset 2022-09-21 Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2022-09-21 Ported from the following upstream stable releases: v4.14.290, v4.19.254 v4.19.255 from git://git.kernel.org/ xen/gntdev: Ignore failure to unmap INVALID_GRANT_HANDLE 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 perf/core: Fix data race between perf_event_set_output() and perf_mmap_close() ip: Fix a data-race around sysctl_fwmark_reflect. tcp/dccp: Fix a data-race around sysctl_tcp_fwmark_accept. tcp: Fix a data-race around sysctl_tcp_probe_threshold. tcp: Fix a data-race around sysctl_tcp_probe_interval. i2c: cadence: Change large transfer count reset logic to be unconditional net: stmmac: fix dma queue left shift overflow issue igmp: Fix data-races around sysctl_igmp_llm_reports. igmp: Fix a data-race around sysctl_igmp_max_memberships. tcp: Fix a data-race around sysctl_tcp_notsent_lowat. be2net: Fix buffer overflow in be_get_module_eeprom Revert "Revert "char/random: silence a lockdep splat with printk()"" mm/mempolicy: fix uninit-value in mpol_rebind_policy() bpf: Make sure mac_header was set before using it drm/tilcdc: Remove obsolete crtc_mode_valid() hack tilcdc: tilcdc_external: fix an incorrect NULL check on list iterator ALSA: memalloc: Align buffer allocations in page size Bluetooth: Add bt_skb_sendmsg helper Bluetooth: Add bt_skb_sendmmsg helper Bluetooth: SCO: Replace use of memcpy_from_msg with bt_skb_sendmsg Bluetooth: RFCOMM: Replace use of memcpy_from_msg with bt_skb_sendmmsg Bluetooth: Fix passing NULL to PTR_ERR Bluetooth: SCO: Fix sco_send_frame returning skb->len Bluetooth: Fix bt_skb_sendmmsg not allocating partial chunks tty: drivers/tty/, stop using tty_schedule_flip() tty: the rest, stop using tty_schedule_flip() tty: drop tty_schedule_flip() tty: extract tty_flip_buffer_commit() from tty_flip_buffer_push() tty: use new tty_insert_flip_string_and_push_buffer() in pty_write() 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 ip: Fix data-races around sysctl_ip_fwd_use_pmtu. ip: Fix data-races around sysctl_ip_nonlocal_bind. tcp: Fix data-races around sysctl_tcp_mtu_probing. tcp: Fix data-races around sysctl_tcp_reordering. tcp: Fix data-races around some timeout sysctl knobs. tcp: Fix a data-race around sysctl_tcp_tw_reuse. tcp: Fix data-races around sysctl_tcp_fastopen. tcp: Fix a data-race around sysctl_tcp_early_retrans. tcp: Fix data-races around sysctl_tcp_recovery. tcp: Fix a data-race around sysctl_tcp_thin_linear_timeouts. tcp: Fix data-races around sysctl_tcp_slow_start_after_idle. tcp: Fix a data-race around sysctl_tcp_retrans_collapse. tcp: Fix a data-race around sysctl_tcp_stdurg. tcp: Fix a data-race around sysctl_tcp_rfc1337. tcp: Fix data-races around sysctl_tcp_max_reordering. ima: remove the IMA_TEMPLATE Kconfig option UBUNTU: [Config] updateconfigs for IMA_TEMPLATE UBUNTU: Upstream stable to v4.14.290, v4.19.254 s390/archrandom: prevent CPACF trng invocations in interrupt context 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. scsi: ufs: host: Hold reference returned by of_parse_phandle() tcp: Fix a data-race around sysctl_tcp_challenge_ack_limit. net: ping6: Fix memleak in ipv6_renew_options(). igmp: Fix data-races around sysctl_igmp_qrv. 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 dat
[Kernel-packages] [Bug 1992194] Re: random CSR_RESET errors in iwlwifi appear under kinetic
Unfortunately, this bug has gotten worse under 5.19.0-23.24 despite the options hack. On a cold boot, about half the time the iwlwifi driver shows the bug. -- 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/1992194 Title: random CSR_RESET errors in iwlwifi appear under kinetic Status in linux package in Ubuntu: Confirmed Status in linux source package in Kinetic: Confirmed Bug description: A Gigabyte GC-WBAX210 WIFI 6E Aorus PCI card worked fine under Ubuntu 22.04 LTS but under Ubuntu 22.10 fails to initialize properly half of the time. When this occurs, the kern.log shows... Oct 2 10:59:26 howarth-X570-UD kernel: [5.581395] iwlwifi :05:00.0: CSR_RESET = 0x10 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581410] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x0 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581427] iwlwifi :05:00.0: value [iter 0]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581443] iwlwifi :05:00.0: value [iter 1]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581459] iwlwifi :05:00.0: value [iter 2]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581474] iwlwifi :05:00.0: value [iter 3]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581490] iwlwifi :05:00.0: value [iter 4]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581505] iwlwifi :05:00.0: value [iter 5]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581521] iwlwifi :05:00.0: value [iter 6]: 0x3f7d8430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581537] iwlwifi :05:00.0: value [iter 7]: 0x3f7d0830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581552] iwlwifi :05:00.0: value [iter 8]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581568] iwlwifi :05:00.0: value [iter 9]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581583] iwlwifi :05:00.0: value [iter 10]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581599] iwlwifi :05:00.0: value [iter 11]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581614] iwlwifi :05:00.0: value [iter 12]: 0x3f7d0430 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581630] iwlwifi :05:00.0: value [iter 13]: 0x3f7d8830 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581646] iwlwifi :05:00.0: value [iter 14]: 0x3f7d0c30 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581659] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x1 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581675] iwlwifi :05:00.0: value [iter 0]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581691] iwlwifi :05:00.0: value [iter 1]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581706] iwlwifi :05:00.0: value [iter 2]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581722] iwlwifi :05:00.0: value [iter 3]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581737] iwlwifi :05:00.0: value [iter 4]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581753] iwlwifi :05:00.0: value [iter 5]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581768] iwlwifi :05:00.0: value [iter 6]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581784] iwlwifi :05:00.0: value [iter 7]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581799] iwlwifi :05:00.0: value [iter 8]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581815] iwlwifi :05:00.0: value [iter 9]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581830] iwlwifi :05:00.0: value [iter 10]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581845] iwlwifi :05:00.0: value [iter 11]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581861] iwlwifi :05:00.0: value [iter 12]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581877] iwlwifi :05:00.0: value [iter 13]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581893] iwlwifi :05:00.0: value [iter 14]: 0x040066c2 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581906] iwlwifi :05:00.0: Host monitor block 0x0 vector 0x6 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581922] iwlwifi :05:00.0: value [iter 0]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581938] iwlwifi :05:00.0: value [iter 1]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581953] iwlwifi :05:00.0: value [iter 2]: 0xb00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581969] iwlwifi :05:00.0: value [iter 3]: 0xe00c7c75 Oct 2 10:59:26 howarth-X570-UD kernel: [5.581984] iwlwifi :0
[Kernel-packages] [Bug 1995023] [NEW] Integrate Nvidia Orin Audio, cpu frequency and other enablement patches
Private bug reported: [Impact] Adding these patches enables the Ubuntu kernel on Orin reference HW [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality on Nvidia HW. ** Affects: linux-nvidia (Ubuntu) Importance: Undecided Status: New ** Information type changed from Public to Private -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-nvidia in Ubuntu. https://bugs.launchpad.net/bugs/1995023 Title: Integrate Nvidia Orin Audio, cpu frequency and other enablement patches Status in linux-nvidia package in Ubuntu: New Bug description: [Impact] Adding these patches enables the Ubuntu kernel on Orin reference HW [Fix] These patches do not constitute a single fix or a set of fixes for bugs but instead enable kernel functionality on Nvidia HW. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-nvidia/+bug/1995023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Luke Nowakowski-Krijger (lukenow) ** Changed in: linux (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#1989625, which made changes in the s390s IPL/boot area of kernel/arch/random. * The reason seems to be that the bad patch moves the decision about if arch randomness is available to setup.c function setup_randomness(). This code uses a static_key s390_arch_random_available. But in the Canonical kernel the initialization function for the jump labels (where the static keys are based on) jump_label_init() is called in generic start_kernel() wheres in the upstream kernel the init function is called early in setup_arch(). * Reverting this commit from bionic master-next makes bionic systems again bootable. (https://launchpad.net/~fheimes/+archive/ubuntu/test/) [ Test Plan ] * An IBM z14 or LinuxONE II or newer system is needed. * Now install latest bionic on that system - doesn't if it's on LPAR, z/VM or KVM. * After the installation (an the trigger of the post install reboot), the system will not come up. * To test a patched kernel with e4f74400308c can be tested in the following way: * Install 18.04 GA and prevent it from doing any kernel updates. * Means, install in 'island' mode or select in d-i 'Advanced Installation' and explicitly choose '4.15.0-50 generic' to install. * That allows the system to come up and to update the kernel to a modified one. * Then reboot and verify if the system comes up properly. [ Where problems could occur ] * Problems could occur due to the fact that the commit was not cleanly reversible because of minor context changes. * Adjustments that were needed might break other things if not done carefully. * Further commits (applied after e4f74400308c) may still rely on the bad e4f74400308c commit - or even further patches (from upstream stable). * In worst case IPL / boot might get broken, even on hardware older than z14. * If the revert works fine can be easily tested and was tested based on https://launchpad.net/~fheimes/+archive/ubuntu/test/ and the above test plan. [ Other Info ] * Ubuntu 20.04 (focal, using legacy image with virt-install) was tested as well, but is not affected by this issue. __ ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995004] Re: Increase stability with connection tracking offload
** Summary changed: - Fix return value of qdisc ingress handling on success + Increase stability with connection tracking offload ** Description changed: - SRU Justification: + * Explain the bug(s) - net: Fix return value of qdisc ingress handling on success - - * Explain the bug(s) - Currently qdisc ingress handling (sch_handle_ingress()) doesn't set a return value and it is left to the old return value of the caller (__netif_receive_skb_core()) which is RX drop, so if the packet is consumed, caller will stop and return this value as if the packet was dropped. - - * brief explanation of fixes - - Fix that by setting the return value to RX success if - the packet was handled successfully. - + + Also, include set of patches to increase stability with connection + tracking offload, including reduced cpu load and possible deadlock on + cleanup. + + * What it could break. + + Packet on egress tc rule forwarding to a ingress tc rule will drop. + High cpu load. Possible deadlock on cleanup. + * How to test - - Commit msg has the steps. - - * What it could break. - - Packet on egress tc rule forwarding to a ingress tc rule will drop. - - - SRU Justification: - - netfilter: conntrack: annotate data-races around ct->timeout - netfilter: conntrack: remove unneeded nf_ct_put - netfilter: conntrack: convert to refcount_t api - netfilter: flowtable: Make sure GC works periodically in idle system - netfilter: flowtable: avoid possible false sharing - netfilter: flowtable: fix excessive hw offload attempts after failure - netfilter: nf_flowtable: expose nf_flow_table_gc_cleanup() - netfilter: flowtable: add function to invoke garbage collection immediately - netfilter: flowtable: fix stuck flows on cleanup due to pending work - - - * Explain the bug(s) - - Set of patches to increase stability with connection tracking offload, - including reduced cpu load and possible deadlock on cleanup. - - * brief explanation of fixes - - Fix that by setting the return value to RX success if - the packet was handled successfully. - - * How to test - - Run connection tracking hw offload scenario with millions of flows, check cpu load, test cleanup and readd scenarios. - - * What it could break. - - High cpu load. Possible deadlock on cleanup. + Run connection tracking hw offload scenario with millions of flows, + check cpu load, test cleanup and readd scenarios. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1995004 Title: Increase stability with connection tracking offload Status in linux-bluefield package in Ubuntu: New Bug description: * Explain the bug(s) Currently qdisc ingress handling (sch_handle_ingress()) doesn't set a return value and it is left to the old return value of the caller (__netif_receive_skb_core()) which is RX drop, so if the packet is consumed, caller will stop and return this value as if the packet was dropped. Also, include set of patches to increase stability with connection tracking offload, including reduced cpu load and possible deadlock on cleanup. * What it could break. Packet on egress tc rule forwarding to a ingress tc rule will drop. High cpu load. Possible deadlock on cleanup. * How to test Run connection tracking hw offload scenario with millions of flows, check cpu load, test cleanup and readd scenarios. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990417] Re: Bluetooth stoped working on Lenovo Yoga Slim 7
bt-adapter has stopped crashing under 5.15.0-52. -- 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/1990417 Title: Bluetooth stoped working on Lenovo Yoga Slim 7 Status in linux package in Ubuntu: Confirmed Bug description: Bluetooth adapted got completely disabled/coudn't be found on the latest kernel version of 5.15.0-48. I needed to revert, did the lspci on older kernel (5.15.0-43 - works ok) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pavel 2194 F pulseaudio /dev/snd/controlC1: pavel 2194 F pulseaudio /dev/snd/controlC0: pavel 2194 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 20.3 EcryptfsInUse: Yes InstallationDate: Installed on 2021-09-18 (367 days ago) InstallationMedia: Linux Mint 20.2 "Uma" - Release amd64 20210703 MachineType: LENOVO 82A2 Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.15.0-43-generic root=/dev/mapper/vgmint-root ro quiet splash ProcVersionSignature: Ubuntu 5.15.0-43.46~20.04.1-generic 5.15.39 RelatedPackageVersions: linux-restricted-modules-5.15.0-43-generic N/A linux-backports-modules-5.15.0-43-generic N/A linux-firmware 1.187.33 Tags: una Uname: Linux 5.15.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/18/2020 dmi.bios.release: 1.36 dmi.bios.vendor: LENOVO dmi.bios.version: DMCN36WW dmi.board.asset.tag: ��� dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: ��� dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga Slim 7 14ARE05 dmi.ec.firmware.release: 1.28 dmi.modalias: dmi:bvnLENOVO:bvrDMCN36WW:bd11/18/2020:br1.36:efr1.28:svnLENOVO:pn82A2:pvrYogaSlim714ARE05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrYogaSlim714ARE05:skuLENOVO_MT_82A2_BU_idea_FM_YogaSlim714ARE05: dmi.product.family: Yoga Slim 7 14ARE05 dmi.product.name: 82A2 dmi.product.sku: LENOVO_MT_82A2_BU_idea_FM_Yoga Slim 7 14ARE05 dmi.product.version: Yoga Slim 7 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990417/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993566] Re: dbus-daemon: Unknown group "power" in message bus configuration file
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: thermald (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1993566 Title: dbus-daemon: Unknown group "power" in message bus configuration file Status in thermald package in Ubuntu: Confirmed Bug description: Hi, I see the following error message in the logs: # journalctl | grep 'Unknown group "power"' Oct 19 18:41:35 jophur dbus-daemon[630]: dbus[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:35 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file Oct 19 18:46:36 jophur dbus-daemon[630]: Unknown group "power" in message bus configuration file The problem comes from this file: # grep -r power /etc/dbus-1/ /etc/dbus-1/system.d/org.freedesktop.thermald.conf:
[Kernel-packages] [Bug 1992679] Re: Can not login after new kernel installed (nvidia driver crashed)
I did fresh installation of Ubuntu 22.10. Issue still occur on fresh OS as well. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1992679 Title: Can not login after new kernel installed (nvidia driver crashed) Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-510 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-515 package in Ubuntu: Confirmed Status in linux source package in Jammy: Confirmed Status in nvidia-graphics-drivers-510 source package in Jammy: Confirmed Status in nvidia-graphics-drivers-515 source package in Jammy: Confirmed Bug description: Hello. Today i have installed new kernel from. I installed 5.15.0-50 and after that i can not login to system... I see boot text, but after booting i see black log screen and can not login. I able boot and login with old kernel (5.15.0-48). I updated these packages: Install: linux-headers-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-modules-extra-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-cloud-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-headers-5.15.0-50:amd64 (5.15.0-50.56, automatic), linux-image-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic), linux-tools-5.15.0-50-generic:amd64 (5.15.0-50.56, automatic) Upgrade: linux-headers-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), google-chrome-stable:amd64 (106.0.5249.103-1, 106.0.5249.119-1), linux-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-image-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50), linux-cloud-tools-generic:amd64 (5.15.0.48.48, 5.15.0.50.50) Updated logs see in attachement. Logs from journalctl see in attachements. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-image-5.15.0-50-generic 5.15.0-50.56 ProcVersionSignature: Ubuntu 5.15.0-48.54-generic 5.15.53 Uname: Linux 5.15.0-48-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: vodka 1819 F pulseaudio /dev/snd/controlC1: vodka 1819 F pulseaudio CasperMD5CheckResult: unknown Date: Wed Oct 12 19:56:43 2022 InstallationDate: Installed on 2018-05-02 (1623 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 003: ID 09da:fa18 A4Tech Co., Ltd. USB Device Bus 001 Device 002: ID 046d:c084 Logitech, Inc. G203 Gaming Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Gigabyte Technology Co., Ltd. H610M S2H DDR4 ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-48-generic root=UUID=b27e8e45-cedd-4ab6-b2e6-ab6bef5e9336 ro PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.15.0-48-generic N/A linux-backports-modules-5.15.0-48-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-04-27 (167 days ago) dmi.bios.date: 03/28/2022 dmi.bios.release: 5.24 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: F7a dmi.board.asset.tag: Default string dmi.board.name: H610M S2H DDR4 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF7a:bd03/28/2022:br5.24:svnGigabyteTechnologyCo.,Ltd.:pnH610MS2HDDR4:pvr-CF:rvnGigabyteTechnologyCo.,Ltd.:rnH610MS2HDDR4:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring: dmi.product.family: H610 MB dmi.product.name: H610M S2H DDR4 dmi.product.sku: Default string dmi.product.version: -CF dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1992679/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993890] Re: Jammy does not work on wifi for Intel 3165
Did you reinstall backport-iwlwifi-dkms package after trying the module options? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1993890 Title: Jammy does not work on wifi for Intel 3165 Status in linux package in Ubuntu: Confirmed Bug description: Intel 3165 wifi does not work on Jammy new install. Ubuntu's Network Manager sees the router but never manages to connect to it. I've tried the purge of the backport iwlwifi module but that didn't help. I followed the instructions on another post to give diagnostics. They are at https://pastebin.ubuntu.com/p/6tgVfYkmFj/ Some more info: admin@Server:~$ lspci -nnk | grep 3165 02:00.0 Network controller [0280]: Intel Corporation Wireless 3165 [8086:3165] (rev 81) Subsystem: Intel Corporation Dual Band Wireless AC 3165 [8086:4010] admin@Server:~$ rfkill list all 0: hci0: Bluetooth Soft blocked: yes Hard blocked: no 1: hci1: Bluetooth Soft blocked: yes Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no – I've just tried 'sudo apt install linux-modules-iwlwifi-generic" and that worked Ok. I rebooted, disconnected Ethernet & turned wifi on. But still get 'SSID connecting' which never finishes and no wifi. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: linux-modules-iwlwifi-generic 5.15.0.52.52 ProcVersionSignature: Ubuntu 5.15.0-52.58-generic 5.15.60 Uname: Linux 5.15.0-52-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: admin 1506 F pulseaudio /dev/snd/controlC0: admin 1506 F pulseaudio /dev/snd/controlC1: admin 1506 F pulseaudio CRDA: N/A CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Oct 22 14:36:50 2022 InstallationDate: Installed on 2022-08-15 (68 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) IwConfig: lono wireless extensions. enp3s0no wireless extensions. wlp2s0no wireless extensions. ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-52-generic root=UUID=20e3b886-2699-47b3-ad21-a02afc4ac9d2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.15.0-52-generic N/A linux-backports-modules-5.15.0-52-generic N/A linux-firmware 20220329.git681281e4-0ubuntu3.5 SourcePackage: linux UpgradeStatus: Upgraded to jammy on 2022-10-05 (16 days ago) dmi.bios.date: 03/14/2018 dmi.bios.release: 5.6 dmi.bios.vendor: Intel Corp. dmi.bios.version: PYBSWCEL.86A.0069.2018.0314.1745 dmi.board.name: NUC5CPYB dmi.board.vendor: Intel Corporation dmi.board.version: H61145-404 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPYBSWCEL.86A.0069.2018.0314.1745:bd03/14/2018:br5.6:svn:pn:pvr:rvnIntelCorporation:rnNUC5CPYB:rvrH61145-404:cvn:ct3:cvr:sku: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1970127] Re: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U)
Hello all, with the new Bios update to version F.08 the installation works again. I think this is another case where the manufacturers are unable to program working firmware. The right address for the bug report was hp not Canonical. It is definitely my last hp laptop. thanks to all developers & best regards -- 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/1970127 Title: Ubuntu-22.04 Live CD not booting on HP ENVY X360 notebook (Ryzen 7 3700U) Status in linux package in Ubuntu: Confirmed Bug description: The ubuntu-22.04-desktop-amd64.iso live cd does not boot on a HP ENVY X360 notebook (Ryzen 7 3700U). Model: HP ENVY X360 13-ar0777ng 9YN58EA#ABD After a few minutes the screen simply switches to black. No possibility to get a console by pressing CTRL-ALT-F1, F2, ... I removed the boot options "quiet splash" and recorded the boot via video. (just ask if you need the full video) I attach a significantly looking screenshot from that video, showing a kernel bug message. Currently the notebook runs with Ubuntu-20.04 using the Linux-5.11 HWE kernel. But suspend to memory isn't working. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1903292 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970127/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1973098] Re: Intermittent freezing and LSPCON init failed kernel messages
I too am having this problem: 5.15.0-52-generic #58~20.04.1-Ubuntu System-manufacturer : LENOVO System-product-name : 20SUS5W300 System-version : ThinkPad P15 Gen 1 Bios-release-date : 07/04/2022 Bios-version : N30ET47W (1.30 ) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed-oem-5.14 in Ubuntu. https://bugs.launchpad.net/bugs/1973098 Title: Intermittent freezing and LSPCON init failed kernel messages Status in linux package in Ubuntu: Confirmed Status in linux-signed-oem-5.14 package in Ubuntu: Confirmed Bug description: Hardware: Lenovo ThinkPad model 20ST0055AU Boot messages show: [6.397804] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [6.397901] [drm] Initialized i915 1.6.0 20201103 for :00:02.0 on minor 0 During normal operation there will intermittently be a freeze for a second or two and then more of these messages display in the kernel logs: [ 505.487006] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 505.487072] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D [ 506.747930] [drm:lspcon_init [i915]] *ERROR* Failed to probe lspcon [ 506.748018] [drm:lspcon_resume [i915]] *ERROR* LSPCON init failed on port D The system will then become operational again. The system is still usable, but it is annoying. I've switched onto this OEM kernel from the generic kernel (5.13), as I had other problems with 5.13 regarding external displays not coming back after idle timeouts. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.14.0-1036-oem 5.14.0-1036.40 ProcVersionSignature: Ubuntu 5.14.0-1036.40-oem 5.14.21 Uname: Linux 5.14.0-1036-oem x86_64 ApportVersion: 2.20.11-0ubuntu27.23 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 12 10:29:31 2022 InstallationDate: Installed on 2021-05-05 (371 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: linux-signed-oem-5.14 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1973098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1995004] [NEW] Fix return value of qdisc ingress handling on success
Public bug reported: SRU Justification: net: Fix return value of qdisc ingress handling on success * Explain the bug(s) Currently qdisc ingress handling (sch_handle_ingress()) doesn't set a return value and it is left to the old return value of the caller (__netif_receive_skb_core()) which is RX drop, so if the packet is consumed, caller will stop and return this value as if the packet was dropped. * brief explanation of fixes Fix that by setting the return value to RX success if the packet was handled successfully. * How to test Commit msg has the steps. * What it could break. Packet on egress tc rule forwarding to a ingress tc rule will drop. SRU Justification: netfilter: conntrack: annotate data-races around ct->timeout netfilter: conntrack: remove unneeded nf_ct_put netfilter: conntrack: convert to refcount_t api netfilter: flowtable: Make sure GC works periodically in idle system netfilter: flowtable: avoid possible false sharing netfilter: flowtable: fix excessive hw offload attempts after failure netfilter: nf_flowtable: expose nf_flow_table_gc_cleanup() netfilter: flowtable: add function to invoke garbage collection immediately netfilter: flowtable: fix stuck flows on cleanup due to pending work * Explain the bug(s) Set of patches to increase stability with connection tracking offload, including reduced cpu load and possible deadlock on cleanup. * brief explanation of fixes Fix that by setting the return value to RX success if the packet was handled successfully. * How to test Run connection tracking hw offload scenario with millions of flows, check cpu load, test cleanup and readd scenarios. * What it could break. High cpu load. Possible deadlock on cleanup. ** Affects: linux-bluefield (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-bluefield in Ubuntu. https://bugs.launchpad.net/bugs/1995004 Title: Fix return value of qdisc ingress handling on success Status in linux-bluefield package in Ubuntu: New Bug description: SRU Justification: net: Fix return value of qdisc ingress handling on success * Explain the bug(s) Currently qdisc ingress handling (sch_handle_ingress()) doesn't set a return value and it is left to the old return value of the caller (__netif_receive_skb_core()) which is RX drop, so if the packet is consumed, caller will stop and return this value as if the packet was dropped. * brief explanation of fixes Fix that by setting the return value to RX success if the packet was handled successfully. * How to test Commit msg has the steps. * What it could break. Packet on egress tc rule forwarding to a ingress tc rule will drop. SRU Justification: netfilter: conntrack: annotate data-races around ct->timeout netfilter: conntrack: remove unneeded nf_ct_put netfilter: conntrack: convert to refcount_t api netfilter: flowtable: Make sure GC works periodically in idle system netfilter: flowtable: avoid possible false sharing netfilter: flowtable: fix excessive hw offload attempts after failure netfilter: nf_flowtable: expose nf_flow_table_gc_cleanup() netfilter: flowtable: add function to invoke garbage collection immediately netfilter: flowtable: fix stuck flows on cleanup due to pending work * Explain the bug(s) Set of patches to increase stability with connection tracking offload, including reduced cpu load and possible deadlock on cleanup. * brief explanation of fixes Fix that by setting the return value to RX success if the packet was handled successfully. * How to test Run connection tracking hw offload scenario with millions of flows, check cpu load, test cleanup and readd scenarios. * What it could break. High cpu load. Possible deadlock on cleanup. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-bluefield/+bug/1995004/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
** Tags added: verification-done-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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress 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: In Progress Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994987] Re: Azure: RMB Patch to backport on the Azure Linux Images
https://lists.ubuntu.com/archives/kernel-team/2022-October/134336.html -- 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/1994987 Title: Azure: RMB Patch to backport on the Azure Linux Images Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] MANA driver is not conforming to the HW specification in one small instance. This request from Azure LSG team to backport the rmb patch to be backported in all the azure images. (https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/ethernet/microsoft/mana?id=6fd2c68da55c552f86e401ebe40c4a619025ef69) Jammy and Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] At worst there might be a small performance impact. [Other Info] SF: #00346991 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994987] [NEW] Azure: RMB Patch to backport on the Azure Linux Images
Public bug reported: SRU Justification [Impact] MANA driver is not conforming to the HW specification in one small instance. This request from Azure LSG team to backport the rmb patch to be backported in all the azure images. (https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/ethernet/microsoft/mana?id=6fd2c68da55c552f86e401ebe40c4a619025ef69) Jammy and Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] At worst there might be a small performance impact. [Other Info] SF: #00346991 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: linux-azure (Ubuntu Focal) Importance: Medium Assignee: Tim Gardner (timg-tpi) Status: In Progress ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Description changed: SRU Justification [Impact] MANA driver is not conforming to the HW specification in one small instance. - This request from Azure LSG team to backport the rmb patch to be backported in all the azure images. ( - https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net-next.git/commit/drivers/net/ethernet/microsoft/mana?id=6fd2c68da55c552f86e401ebe40c4a619025ef69) + This request from Azure LSG team to backport the rmb patch to be + backported in all the azure images. + (https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- + next.git/commit/drivers/net/ethernet/microsoft/mana?id=6fd2c68da55c552f86e401ebe40c4a619025ef69) Jammy and Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] At worst there might be a small performance impact. [Other Info] SF: #00346991 -- 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/1994987 Title: Azure: RMB Patch to backport on the Azure Linux Images Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Bug description: SRU Justification [Impact] MANA driver is not conforming to the HW specification in one small instance. This request from Azure LSG team to backport the rmb patch to be backported in all the azure images. (https://git.kernel.org/pub/scm/linux/kernel/git/netdev/net- next.git/commit/drivers/net/ethernet/microsoft/mana?id=6fd2c68da55c552f86e401ebe40c4a619025ef69) Jammy and Kinetic will get this patch via stable updates. [Test Case] Microsoft tested [Where things could go wrong] At worst there might be a small performance impact. [Other Info] SF: #00346991 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994987/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1990985] Re: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems
** Tags added: verification-done-bionic verification-done-focal ** Tags removed: servcert-550 verification-done-bionic verification- done-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/1990985 Title: ACPI: processor idle: Practically limit "Dummy wait" workaround to old Intel systems Status in linux package in Ubuntu: In Progress 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: In Progress Bug description: IMPACT: Old, circa 2002 chipsets have a bug: they don't go idle when they are supposed to. So, a workaround was added to slow the CPU down and ensure that the CPU waits a bit for the chipset to actually go idle. This workaround is ancient and has been in place in some form since the original kernel ACPI implementation. But, this workaround is very painful on modern systems. The "inl()" can take thousands of cycles (see Link: for some more detailed numbers and some fun kernel archaeology). First and foremost, modern systems should not be using this code. Typical Intel systems have not used it in over a decade because it is horribly inferior to MWAIT-based idle. Despite this, people do seem to be tripping over this workaround on AMD system today. Limit the "dummy wait" workaround to Intel systems. Keep Modern AMD systems from tripping over the workaround. Remotely modern Intel systems use intel_idle instead of this code and will, in practice, remain unaffected by the dummy wait. Reported-by: K Prateek Nayak Suggested-by: Rafael J. Wysocki Signed-off-by: Dave Hansen Reviewed-by: Mario Limonciello Tested-by: K Prateek Nayak Link: https://lore.kernel.org/all/20220921063638.2489-1-kprateek.na...@amd.com/ Link: https://lkml.kernel.org/r/20220922184745.3252932-1-dave.han...@intel.com FIX: This issue pertains to all Zen based processors starting with Naples(Zen1). All LTS releases will need this fix: https://github.com/torvalds/linux/commit/e400ad8b7e6a1b9102123c6240289a811501f7d9 TESTCASE: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1990985/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993315] Re: md: Replace snprintf with scnprintf
** Tags added: verification-done-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/1993315 Title: md: Replace snprintf with scnprintf Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Jammy: In Progress Status in linux source package in Kinetic: In Progress Bug description: SRU Justification [Impact] Current code produces a warning as shown below when total characters in the constituent block device names plus the slashes exceeds 200. snprintf() returns the number of characters generated from the given input, which could cause the expression “200 – len” to wrap around to a large positive number. Fix this by using scnprintf() instead, which returns the actual number of characters written into the buffer. [ 1513.267938] [ cut here ] [ 1513.267943] WARNING: CPU: 15 PID: 37247 at /lib/vsprintf.c:2509 vsnprintf+0x2c8/0x510 [ 1513.267944] Modules linked in: [ 1513.267969] CPU: 15 PID: 37247 Comm: mdadm Not tainted 5.4.0-1085-azure #90~18.04.1-Ubuntu [ 1513.267969] Hardware name: Microsoft Corporation Virtual Machine/Virtual Machine, BIOS Hyper-V UEFI Release v4.1 05/09/2022 [ 1513.267971] RIP: 0010:vsnprintf+0x2c8/0x510 <-snip-> [ 1513.267982] Call Trace: [ 1513.267986] snprintf+0x45/0x70 [ 1513.267990] ? disk_name+0x71/0xa0 [ 1513.267993] dump_zones+0x114/0x240 [raid0] [ 1513.267996] ? _cond_resched+0x19/0x40 [ 1513.267998] raid0_run+0x19e/0x270 [raid0] [ 1513.268000] md_run+0x5e0/0xc50 [ 1513.268003] ? security_capable+0x3f/0x60 [ 1513.268005] do_md_run+0x19/0x110 [ 1513.268006] md_ioctl+0x195e/0x1f90 [ 1513.268007] blkdev_ioctl+0x91f/0x9f0 [ 1513.268010] block_ioctl+0x3d/0x50 [ 1513.268012] do_vfs_ioctl+0xa9/0x640 [ 1513.268014] ? __fput+0x162/0x260 [ 1513.268016] ksys_ioctl+0x75/0x80 [ 1513.268017] __x64_sys_ioctl+0x1a/0x20 [ 1513.268019] do_syscall_64+0x5e/0x200 [ 1513.268021] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [Fix] https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=1727fd5015d8f93474148f94e34cda5aa6ad4a43 [Where things could go wrong] This seems unlikely to cause a regression [Other Info] SF: #00346036 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1987699] Re: azure: CIFS Backport Updates to 5.15 Kernel
** Tags added: verification-done-jammy -- 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/1987699 Title: azure: CIFS Backport Updates to 5.15 Kernel Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Jammy: Fix Committed Bug description: SRU Justification [Impact] Microsoft has requested updating CIFS to the 5.15 backport as published in 'git://git.samba.org/sfrench/cifs-2.6.git 5.15-backport'. [Test Plan] Microsoft tested [Where things could go wrong] CIFS network connections could misbehave [Other Info] SF: #00343105 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1987699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834771] Re: No HDMI-audio after kernel 4.15.-0.50
The fix is imminent. https://gitlab.freedesktop.org/agd5f/linux/-/commit/34d84636e5e09521d031863a01f9b9fb22ffa875 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993217/comments/37 After proven by the community, I look forward to updating the workaround post as "No longer needed!" -- 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/1834771 Title: No HDMI-audio after kernel 4.15.-0.50 Status in linux package in Ubuntu: Confirmed Bug description: I've got no HDMI-audio. Latest kernel with working HDMI-audio is 4.15.-0.50. In pavucontrol HDMI-audio shows unplugged. And also internal audio shows unplugged, but it still works. I'm on linux mint 18.3. --- ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jouni 1859 F pulseaudio /dev/snd/controlC1: jouni 1859 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux 18.3 HibernationDevice: RESUME=UUID=9e8d7bf3-dc5f-4c72-b875-6dbe81a36c36 InstallationDate: Installed on 2017-01-28 (883 days ago) InstallationMedia: Linux Mint 18.1 "Serena" - Release amd64 20161213 IwConfig: lono wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. To be filled by O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-54-generic root=UUID=f167a2b0-3b30-4a5a-907f-6b97c95b7a91 ro quiet iommu=soft splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.15.0-54.58~16.04.1-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-54-generic N/A linux-backports-modules-4.15.0-54-generic N/A linux-firmware 1.157.21 RfKill: Tags: sylvia Uname: Linux 4.15.0-54-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/26/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: FC dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: 970A-UD3P dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrFC:bd02/26/2016:svnGigabyteTechnologyCo.,Ltd.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rn970A-UD3P:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1834771/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL
Kernel SRU request submitted for bionic: https://lists.ubuntu.com/archives/kernel-team/2022-October/134331.html changing status to 'In Progress'. ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: ubuntu-z-systems Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: Skipper Bug Screeners (skipper-screen-team) => Canonical Kernel Team (canonical-kernel-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#1989625, which made changes in the s390s IPL/boot area of kernel/arch/random. * The reason seems to be that the bad patch moves the decision about if arch randomness is available to setup.c function setup_randomness(). This code uses a static_key s390_arch_random_available. But in the Canonical kernel the initialization function for the jump labels (where the static keys are based on) jump_label_init() is called in generic start_kernel() wheres in the upstream kernel the init function is called early in setup_arch(). * Reverting this commit from bionic master-next makes bionic systems again bootable. (https://launchpad.net/~fheimes/+archive/ubuntu/test/) [ Test Plan ] * An IBM z14 or LinuxONE II or newer system is needed. * Now install latest bionic on that system - doesn't if it's on LPAR, z/VM or KVM. * After the installation (an the trigger of the post install reboot), the system will not come up. * To test a patched kernel with e4f74400308c can be tested in the following way: * Install 18.04 GA and prevent it from doing any kernel updates. * Means, install in 'island' mode or select in d-i 'Advanced Installation' and explicitly choose '4.15.0-50 generic' to install. * That allows the system to come up and to update the kernel to a modified one. * Then reboot and verify if the system comes up properly. [ Where problems could occur ] * Problems could occur due to the fact that the commit was not cleanly reversible because of minor context changes. * Adjustments that were needed might break other things if not done carefully. * Further commits (applied after e4f74400308c) may still rely on the bad e4f74400308c commit - or even further patches (from upstream stable). * In worst case IPL / boot might get broken, even on hardware older than z14. * If the revert works fine can be easily tested and was tested based on https://launchpad.net/~fheimes/+archive/ubuntu/test/ and the above test plan. [ Other Info ] * Ubuntu 20.04 (focal, using legacy image with virt-install) was tested as well, but is not affected by this issue. __ ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.
[Kernel-packages] [Bug 1993217] Re: fixed "HDMI ATI/AMD: no speaker allocation for ELD" on Radeon module
@Paul_Dufresne, many thanks for driving the fix to this longstanding
bug. It's been present for over three years and likely affects millions
of users.
Following your work here:
https://gitlab.freedesktop.org/drm/amd/-/issues/1569#note_1601169, it
appears there's finally going to be a real, permanent correction
upstream. Dancing in the streets is unlikely, but a vast number of users
will get happy their HDMI audio works again, largely thanks to your
efforts.
This should stand as an example of how even a single contributor who is
dedicated to the task can make a huge difference.
--
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/1993217
Title:
fixed "HDMI ATI/AMD: no speaker allocation for ELD" on Radeon module
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is on my friend laptop with his TV.
HDMI audio not available in pavucontrol (profile say unplugged, unavailable)
in kernel versions with bugs.
It is just shown as an audio output (HDMI audio) on kernels where it is
working.
When not working, I can play with aplay -D HDMI ...
When working... I select HDMI audio in output, and test sound ok, Youtube
videos ok, etc.
4.9.177 working.
4.9.178 not working.
I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
is between those versions, and is related to audio (realtek in part).
More info at:
https://forums.linuxmint.com/viewtopic.php?f=49&t=383607&p=2246352#p2246352
although the laptop now runs ... 17.10 I think (a version with a not broken
kernel).
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: client 1023 F pulseaudio
/dev/snd/pcmC0D0p: client 1023 F...m pulseaudio
/dev/snd/controlC1: client 1023 F pulseaudio
CasperMD5json: {
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: SAMSUNG ELECTRONICS CO., LTD. R425D/R525D
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
LANGUAGE=fr_CA:fr
TERM=xterm-256color
PATH=(custom, no user)
LANG=fr_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic
root=UUID=2db14083-ebb6-4a5a-b0b1-4a65e79069d7 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
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-50-generic N/A
linux-backports-modules-5.15.0-50-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.5
Tags: vanessa apport-hook-error
Uname: Linux 5.15.0-50-generic x86_64
UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 10/16/2010
dmi.bios.release: 2.0
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02UF
dmi.board.name: R425D/R525D
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr02UF:bd10/16/2010:br2.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnR425D/R525D:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR425D/R525D:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:sku:
dmi.product.name: R425D/R525D
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993217/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994974] Re: Azure: hv_netvsc: Fix race between VF offering and VF association message from host
Patches submitted: https://lists.ubuntu.com/archives/kernel-team/2022-October/134324.html Focal test kernel: https://kernel.ubuntu.com/~rtg/focal-azure-vf-race-lp1994974/5.4.0-1096.102~lp1994974.1/ ** Also affects: linux-azure (Ubuntu Kinetic) Importance: Undecided Status: Fix Released ** Changed in: linux-azure (Ubuntu Kinetic) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Kinetic) Status: Fix Released => In Progress ** Changed in: linux-azure (Ubuntu Kinetic) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1994974 Title: Azure: hv_netvsc: Fix race between VF offering and VF association message from host Status in linux-azure package in Ubuntu: In Progress Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Jammy: In Progress Status in linux-azure source package in Kinetic: In Progress Bug description: SRU Justification [Impact] During vm boot, there might be possibility that vf registration call comes before the vf association from host to vm. And this might break netvsc vf path, this is in order to prevent the same block vf registration until vf bind message comes from host. [Test Plan] Microsoft tested [Where things could go wrong] The 5.4 backport patch could hang waiting for a VF addition to complete. [Other Info] SF: #00347129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994974] Re: Azure: hv_netvsc: Fix race between VF offering and VF association message from host
** Also affects: linux-azure (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Focal) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Focal) Assignee: (unassigned) => Tim Gardner (timg-tpi) ** Changed in: linux-azure (Ubuntu) Status: New => Fix Released ** Changed in: linux-azure (Ubuntu Jammy) Importance: Undecided => Medium ** Changed in: linux-azure (Ubuntu Jammy) Status: New => In Progress ** Changed in: linux-azure (Ubuntu Jammy) Assignee: (unassigned) => Tim Gardner (timg-tpi) -- 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/1994974 Title: Azure: hv_netvsc: Fix race between VF offering and VF association message from host Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Focal: In Progress Status in linux-azure source package in Jammy: In Progress Bug description: SRU Justification [Impact] During vm boot, there might be possibility that vf registration call comes before the vf association from host to vm. And this might break netvsc vf path, this is in order to prevent the same block vf registration until vf bind message comes from host. [Test Plan] Microsoft tested [Where things could go wrong] The 5.4 backport patch could hang waiting for a VF addition to complete. [Other Info] SF: #00347129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
When will the ISOs be correct? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Committed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994974] [NEW] Azure: hv_netvsc: Fix race between VF offering and VF association message from host
Public bug reported: SRU Justification [Impact] During vm boot, there might be possibility that vf registration call comes before the vf association from host to vm. And this might break netvsc vf path, this is in order to prevent the same block vf registration until vf bind message comes from host. [Test Plan] Microsoft tested [Where things could go wrong] The 5.4 backport patch could hang waiting for a VF addition to complete. [Other Info] SF: #00347129 ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Package changed: linux (Ubuntu) => linux-azure (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994974 Title: Azure: hv_netvsc: Fix race between VF offering and VF association message from host Status in linux-azure package in Ubuntu: New Bug description: SRU Justification [Impact] During vm boot, there might be possibility that vf registration call comes before the vf association from host to vm. And this might break netvsc vf path, this is in order to prevent the same block vf registration until vf bind message comes from host. [Test Plan] Microsoft tested [Where things could go wrong] The 5.4 backport patch could hang waiting for a VF addition to complete. [Other Info] SF: #00347129 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1994974/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994601] Comment bridged from LTC Bugzilla
--- Comment From mihaj...@de.ibm.com 2022-10-27 08:49 EDT--- With Frank's revert [build https://launchpad.net/~fheimes/+archive/ubuntu/test/] kernel boots up OK. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#1989625, which made changes in the s390s IPL/boot area of kernel/arch/random. * The reason seems to be that the bad patch moves the decision about if arch randomness is available to setup.c function setup_randomness(). This code uses a static_key s390_arch_random_available. But in the Canonical kernel the initialization function for the jump labels (where the static keys are based on) jump_label_init() is called in generic start_kernel() wheres in the upstream kernel the init function is called early in setup_arch(). * Reverting this commit from bionic master-next makes bionic systems again bootable. (https://launchpad.net/~fheimes/+archive/ubuntu/test/) [ Test Plan ] * An IBM z14 or LinuxONE II or newer system is needed. * Now install latest bionic on that system - doesn't if it's on LPAR, z/VM or KVM. * After the installation (an the trigger of the post install reboot), the system will not come up. * To test a patched kernel with e4f74400308c can be tested in the following way: * Install 18.04 GA and prevent it from doing any kernel updates. * Means, install in 'island' mode or select in d-i 'Advanced Installation' and explicitly choose '4.15.0-50 generic' to install. * That allows the system to come up and to update the kernel to a modified one. * Then reboot and verify if the system comes up properly. [ Where problems could occur ] * Problems could occur due to the fact that the commit was not cleanly reversible because of minor context changes. * Adjustments that were needed might break other things if not done carefully. * Further commits (applied after e4f74400308c) may still rely on the bad e4f74400308c commit - or even further patches (from upstream stable). * In worst case IPL / boot might get broken, even on hardware older than z14. * If the revert works fine can be easily tested and was tested based on https://launchpad.net/~fheimes/+archive/ubuntu/test/ and the above test plan. [ Other Info ] * Ubuntu 20.04 (focal, using legacy image with virt-install) was tested as well, but is not affected by this issue. __ ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL
Separately recent rework in random causes hangs and inability to boot on x86 virtio-rnd machines too. I feel like I need to escalate this issue to upstream kernel, together/separately from the virtio-rnd one. It seems like rnd rewrites are not quite as robust as the old status quo. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#1989625, which made changes in the s390s IPL/boot area of kernel/arch/random. * The reason seems to be that the bad patch moves the decision about if arch randomness is available to setup.c function setup_randomness(). This code uses a static_key s390_arch_random_available. But in the Canonical kernel the initialization function for the jump labels (where the static keys are based on) jump_label_init() is called in generic start_kernel() wheres in the upstream kernel the init function is called early in setup_arch(). * Reverting this commit from bionic master-next makes bionic systems again bootable. (https://launchpad.net/~fheimes/+archive/ubuntu/test/) [ Test Plan ] * An IBM z14 or LinuxONE II or newer system is needed. * Now install latest bionic on that system - doesn't if it's on LPAR, z/VM or KVM. * After the installation (an the trigger of the post install reboot), the system will not come up. * To test a patched kernel with e4f74400308c can be tested in the following way: * Install 18.04 GA and prevent it from doing any kernel updates. * Means, install in 'island' mode or select in d-i 'Advanced Installation' and explicitly choose '4.15.0-50 generic' to install. * That allows the system to come up and to update the kernel to a modified one. * Then reboot and verify if the system comes up properly. [ Where problems could occur ] * Problems could occur due to the fact that the commit was not cleanly reversible because of minor context changes. * Adjustments that were needed might break other things if not done carefully. * Further commits (applied after e4f74400308c) may still rely on the bad e4f74400308c commit - or even further patches (from upstream stable). * In worst case IPL / boot might get broken, even on hardware older than z14. * If the revert works fine can be easily tested and was tested based on https://launchpad.net/~fheimes/+archive/ubuntu/test/ and the above test plan. [ Other Info ] * Ubuntu 20.04 (focal, using legacy image with virt-install) was tested as well, but is not affected by this issue. __ ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL
** Summary changed: - [UBUNTU 18.04] Ubuntu 18.04 crashes during IPL + [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#1989625, which made changes in the s390s IPL/boot area of kernel/arch/random. * The reason seems to be that the bad patch moves the decision about if arch randomness is available to setup.c function setup_randomness(). This code uses a static_key s390_arch_random_available. But in the Canonical kernel the initialization function for the jump labels (where the static keys are based on) jump_label_init() is called in generic start_kernel() wheres in the upstream kernel the init function is called early in setup_arch(). * Reverting this commit from bionic master-next makes bionic systems again bootable. (https://launchpad.net/~fheimes/+archive/ubuntu/test/) [ Test Plan ] * An IBM z14 or LinuxONE II or newer system is needed. * Now install latest bionic on that system - doesn't if it's on LPAR, z/VM or KVM. * After the installation (an the trigger of the post install reboot), the system will not come up. * To test a patched kernel with e4f74400308c can be tested in the following way: * Install 18.04 GA and prevent it from doing any kernel updates. * Means, install in 'island' mode or select in d-i 'Advanced Installation' and explicitly choose '4.15.0-50 generic' to install. * That allows the system to come up and to update the kernel to a modified one. * Then reboot and verify if the system comes up properly. [ Where problems could occur ] * Problems could occur due to the fact that the commit was not cleanly reversible because of minor context changes. * Adjustments that were needed might break other things if not done carefully. * Further commits (applied after e4f74400308c) may still rely on the bad e4f74400308c commit - or even further patches (from upstream stable). * In worst case IPL / boot might get broken, even on hardware older than z14. * If the revert works fine can be easily tested and was tested based on https://launchpad.net/~fheimes/+archive/ubuntu/test/ and the above test plan. [ Other Info ] * Ubuntu 20.04 (focal, using legacy image with virt-install) was tested as well, but is not affected by this issue. __ ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 crashes during IPL
** Description changed: + SRU Justification: + == + + [ Impact ] + + * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 +are no longer able to IPL (boot) on IBM z14 or newer hardware. + + * This issue got introduced by upstream commit e4f74400308c +"s390/archrandom: simplify back to earlier design and initialize earlier" +that was SRUed to 18.04/bionic based on LP#1989625, +which made changes in the s390s IPL/boot area of kernel/arch/random. + + * The reason seems to be that the bad patch moves the decision about +if arch randomness is available to setup.c function setup_randomness(). +This code uses a static_key s390_arch_random_available. +But in the Canonical kernel the initialization function +for the jump labels (where the static keys are based on) +jump_label_init() is called in generic start_kernel() +wheres in the upstream kernel the init function is +called early in setup_arch(). + + * Reverting this commit from bionic master-next makes bionic systems +again bootable. +(https://launchpad.net/~fheimes/+archive/ubuntu/test/) + + [ Test Plan ] + + * An IBM z14 or LinuxONE II or newer system is needed. + + * Now install latest bionic on that system - doesn't if it's on LPAR, +z/VM or KVM. + + * After the installation (an the trigger of the post install reboot), +the system will not come up. + + * To test a patched kernel with e4f74400308c can be tested in the +following way: + + * Install 18.04 GA and prevent it from doing any kernel updates. + + * Means, install in 'island' mode +or select in d-i 'Advanced Installation' +and explicitly choose '4.15.0-50 generic' to install. + + * That allows the system to come up and to update the kernel to +a modified one. + + * Then reboot and verify if the system comes up properly. + + [ Where problems could occur ] + + * Problems could occur due to the fact that the commit +was not cleanly reversible because of minor context changes. + + * Adjustments that were needed might break other things if not +done carefully. + + * Further commits (applied after e4f74400308c) may still rely +on the bad e4f74400308c commit - or even further patches +(from upstream stable). + + * In worst case IPL / boot might get broken, +even on hardware older than z14. + + * If the revert works fine can be easily tested and was tested based on +https://launchpad.net/~fheimes/+archive/ubuntu/test/ +and the above test plan. + + [ Other Info ] + + * Ubuntu 20.04 (focal, using legacy image with virt-install) +was tested as well, but is not affected by this issue. + __ + ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. - - Contact Information = Viktor Mihajlovski - + Contact Information = Viktor Mihajlovski + ---uname output--- n/a - - Machine Type = 3096 - + + Machine Type = 3096 + ---Debugger--- A debugger is not configured - + ---Steps to Reproduce--- - Install Ubuntu 18.04 as a KVM guest using the following command: + Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. - + Stack trace output: - no - + no + Oops output: - no + no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 kernel 4.15.0-194 crashes on IPL Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: SRU Justification: == [ Impact ] * Ubuntu 18.04 / bionic installations with latest kernel 4.15.0-194 are no longer able to IPL (boot) on IBM z14 or newer hardware. * This issue got introduced by upstream commit e4f74400308c "s390/archrandom: simplify back to earlier design and initialize earlier" that was SRUed to 18.04/bionic based on LP#
[Kernel-packages] [Bug 1994601] Comment bridged from LTC Bugzilla
--- Comment From cborn...@de.ibm.com 2022-10-27 07:25 EDT--- > Now, should we proceed with the revert (which btw. did not revert cleanly, I > had to massage it a little bit), or do you want to fix upstream > "s390/archrandom: simplify back to earlier design and initialize earlier"? If Viktor can confirm that the revert works, I would go with a revert. Obviously the upstream fix is not enough and we might need more patches which are not known by now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 crashes during IPL Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994693] Re: linux-kvm: use annotations from debian.master
** Changed in: linux-kvm (Ubuntu Kinetic) Importance: Undecided => Low ** Changed in: linux-kvm (Ubuntu Kinetic) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1994693 Title: linux-kvm: use annotations from debian.master Status in linux-kvm package in Ubuntu: In Progress Status in linux-kvm source package in Kinetic: In Progress Bug description: [Issue] linux-kvm wasn't using annotations from debian.master, and that induced a skew in fundamental config options between main and kvm kernels. [Fix] The attached series (broken down in pieces to ease review) make linux-kvm use annotations from debian.master and override options that are meant to be different. Must be applied on top of "[SRU][KINETIC linux-kvm][PATCH] UBUNTU: [Config] Update SQUASHFS configs" already posted on the mailing list. [How to test] Crank updateconfigs shouldn't report any check-config error afterward. [Regression potential] These five patches: UBUNTU: [Config] align IMA config with debian.master UBUNTU: [Config] align UBSAN config with debian.master UBUNTU: [Config] disable X86_KERNEL_IBT UBUNTU: [Config] align LSM_MMAP_MIN_ADDR with master UBUNTU: [Config] align LSM with master are the only changes in kvm config, everything else is annotations fix up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1994693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627256/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627249/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627245/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627257/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627244/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627248/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627246/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627247/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627252/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627253/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627255/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627254/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627251/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627250/+files/ProcCpuinfoMinimal.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627242/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627241/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627240/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627243/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 Tags: kinetic Uname: Linux 5.19.0-23-generic x86_64 UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/15/2022 dmi.bios.release: 5.25 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: UX3402ZA.305 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX3402ZA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.ec.firmware.release: 3.5 dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: dmi.product.family: Zenbook dmi.product.name: Zenbook UX3402ZA_UX3402ZA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] Re: Asus ZenBook UX3402 has no sound
apport information ** Tags added: apport-collected kinetic ** Description changed: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. + --- + ProblemType: Bug + ApportVersion: 2.23.1-0ubuntu3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: isti 2081 F pipewire + isti 2084 F wireplumber + /dev/snd/seq:isti 2081 F pipewire + CasperMD5CheckResult: unknown + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.10 + HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b + InstallationDate: Installed on 2014-10-28 (2920 days ago) + InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) + MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA + NonfreeKernelModules: wl + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.19.0-23.24-generic 5.19.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 + Tags: kinetic + Uname: Linux 5.19.0-23-generic x86_64 + UpgradeStatus: Upgraded to kinetic on 2022-10-24 (2 days ago) + UserGroups: adm cdrom dip fuse lpadmin plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 06/15/2022 + dmi.bios.release: 5.25 + dmi.bios.vendor: American Megatrends International, LLC. + dmi.bios.version: UX3402ZA.305 + dmi.board.asset.tag: ATN12345678901234567 + dmi.board.name: UX3402ZA + dmi.board.vendor: ASUSTeK COMPUTER INC. + dmi.board.version: 1.0 + dmi.chassis.asset.tag: No Asset Tag + dmi.chassis.type: 31 + dmi.chassis.vendor: ASUSTeK COMPUTER INC. + dmi.chassis.version: 1.0 + dmi.ec.firmware.release: 3.5 + dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrUX3402ZA.305:bd06/15/2022:br5.25:efr3.5:svnASUSTeKCOMPUTERINC.:pnZenbookUX3402ZA_UX3402ZA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX3402ZA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct31:cvr1.0:sku: + dmi.product.family: Zenbook + dmi.product.name: Zenbook UX3402ZA_UX3402ZA + dmi.product.version: 1.0 + dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1994948/+attachment/5627239/+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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Confirmed Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. --- ProblemType: Bug ApportVersion: 2.23.1-0ubuntu3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: isti 2081 F pipewire isti 2084 F wireplumber /dev/snd/seq:isti 2081 F pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.10 HibernationDevice: RESUME=UUID=3c5f5acb-f7db-4f1e-84cb-ad91d85d495b InstallationDate: Installed on 2014-10-28 (2920 days ago) InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1) MachineType: ASUSTeK COMPUTER INC. Zenbook UX3402ZA_UX3402ZA NonfreeKernelModules: wl Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-5.19.0-23-generic root=UUID=15681307-21c7-46eb-9726-303aaf0a4107 ro rootflags=subvol=@ quiet splash vt.han
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
Ubuntu-SRU please release this one if possible, it is tested and working, and preventing people from building kernel modules. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Committed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: originate-from-1994098 stella
--
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
“obj/monolithic/grub-efi-amd64/grubx64.efi”, in my case:
`/var/cache/pbuilder/build/276481/build/grub2-2.06/obj/monolithic/grub-
[Kernel-packages] [Bug 1377279] Re: dmesg fills with "speaker allocation warnings"
Should be a duplicate of just now fixed upstream bug #1993217 -- 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/1377279 Title: dmesg fills with "speaker allocation warnings" Status in linux package in Ubuntu: Confirmed Bug description: This is an issue with the driver message log filling with warnings, and NOT an actual issue with the hardware or software functionality. Sound on this system works as expected, but dmesg becomes cluttered with log information that does not appear of significant value, considering the frequency and repetition of the warnings. The following message appears, repeated on multiple consecutive lines: "sound hdaudioC0D0: HDMI ATI/AMD: no speaker allocation for ELD" and on some occasions is accompanied by an entry stating: "[drm:dce4_afmt_write_speaker_allocation] *ERROR* Couldn't read Speaker Allocation Data Block: 0" The system in question is a laptop with an external monitor connected over HDMI. It has been freshly built with Lubuntu 14.10 Beta 2, and the same issue also occurs when using testing the mainline kernel 3.17.0-031700rc7.201409281835. The occasions on which this issue (the repeated warnings) occurs under strict testing conditions include: * Using the Monitor Preferences (LXRandR) to turn OFF and ON the external monitor (approx 10 warnings for each action) * Putting the system into the suspend power mode and subsequently resuming (approx 30 warnings) No warnings occur when: * unplugging or plugging the HDMI cable * locking and unlocking the lightdm desktop I have observed occasions where the warnings are written many, many hundreds of times, on an almost continuous basis, but I have not been able to reproduce this behavior in controlled circumstances. ProblemType: Bug DistroRelease: Ubuntu 14.10 Package: linux-image-3.16.0-20-generic 3.16.0-20.27 ProcVersionSignature: Ubuntu 3.16.0-20.27-generic 3.16.3 Uname: Linux 3.16.0-20-generic x86_64 ApportVersion: 2.14.7-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: art2113 F pulseaudio /dev/snd/controlC0: art2113 F pulseaudio CRDA: Error: [Errno 2] No such file or directory: 'iw' CurrentDesktop: LXDE CurrentDmesg: Error: command ['sh', '-c', 'dmesg | comm -13 --nocheck-order /var/log/dmesg -'] failed with exit code 1: comm: /var/log/dmesg: Permission denied Date: Fri Oct 3 19:20:02 2014 EcryptfsInUse: Yes InstallationDate: Installed on 2014-09-26 (7 days ago) InstallationMedia: Lubuntu 14.10 "Utopic Unicorn" - Alpha amd64 (20140923) MachineType: Acer AO722 ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-20-generic root=UUID=bf9f8de0-2b70-4f49-85ee-54f7d94a6508 ro SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 09/25/2012 dmi.bios.vendor: Acer dmi.bios.version: V1.11 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: JE10-BZ dmi.board.vendor: Acer dmi.board.version: Base Board Version dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.11 dmi.modalias: dmi:bvnAcer:bvrV1.11:bd09/25/2012:svnAcer:pnAO722:pvrV1.11:rvnAcer:rnJE10-BZ:rvrBaseBoardVersion:cvnAcer:ct10:cvrV1.11: dmi.product.name: AO722 dmi.product.version: V1.11 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1377279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] 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 1994948 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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1993217] Re: old commit make HDMI audio not available if not eld_valid
The previously accepted patch have received itself a new patch that use
a more fine grained mutex.
** Patch added: "patch previous patch with mutex on audio component"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993217/+attachment/5627221/+files/0001-drm-radeon-Use-a-local-mutex-for-bind-unbind-protect.patch
** Summary changed:
- old commit make HDMI audio not available if not eld_valid
+ fixed "HDMI ATI/AMD: no speaker allocation for ELD" on Radeon module
--
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/1993217
Title:
fixed "HDMI ATI/AMD: no speaker allocation for ELD" on Radeon module
Status in linux package in Ubuntu:
Confirmed
Bug description:
This is on my friend laptop with his TV.
HDMI audio not available in pavucontrol (profile say unplugged, unavailable)
in kernel versions with bugs.
It is just shown as an audio output (HDMI audio) on kernels where it is
working.
When not working, I can play with aplay -D HDMI ...
When working... I select HDMI audio in output, and test sound ok, Youtube
videos ok, etc.
4.9.177 working.
4.9.178 not working.
I suspect commit 72cf0b07418a9c8349aa9137194b1ccba6e54a9d because it
is between those versions, and is related to audio (realtek in part).
More info at:
https://forums.linuxmint.com/viewtopic.php?f=49&t=383607&p=2246352#p2246352
although the laptop now runs ... 17.10 I think (a version with a not broken
kernel).
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.1
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: client 1023 F pulseaudio
/dev/snd/pcmC0D0p: client 1023 F...m pulseaudio
/dev/snd/controlC1: client 1023 F pulseaudio
CasperMD5json: {
DistroRelease: Linux Mint 21
InstallationDate: Installed on 2022-10-18 (0 days ago)
InstallationMedia: Linux Mint 21 "Vanessa" - Release amd64 20220726
MachineType: SAMSUNG ELECTRONICS CO., LTD. R425D/R525D
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
Package: linux (not installed)
ProcEnviron:
LANGUAGE=fr_CA:fr
TERM=xterm-256color
PATH=(custom, no user)
LANG=fr_CA.UTF-8
SHELL=/bin/bash
ProcFB: 0 radeondrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-50-generic
root=UUID=2db14083-ebb6-4a5a-b0b1-4a65e79069d7 ro quiet splash
ProcVersionSignature: Ubuntu 5.15.0-50.56-generic 5.15.60
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-50-generic N/A
linux-backports-modules-5.15.0-50-generic N/A
linux-firmware 20220329.git681281e4-0ubuntu3.5
Tags: vanessa apport-hook-error
Uname: Linux 5.15.0-50-generic x86_64
UnreportableReason: Ce rapport concerne un paquet qui n'est pas installé.
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: N/A
_MarkForUpload: False
dmi.bios.date: 10/16/2010
dmi.bios.release: 2.0
dmi.bios.vendor: Phoenix Technologies Ltd.
dmi.bios.version: 02UF
dmi.board.name: R425D/R525D
dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD.
dmi.chassis.version: N/A
dmi.modalias:
dmi:bvnPhoenixTechnologiesLtd.:bvr02UF:bd10/16/2010:br2.0:svnSAMSUNGELECTRONICSCO.,LTD.:pnR425D/R525D:pvrNotApplicable:rvnSAMSUNGELECTRONICSCO.,LTD.:rnR425D/R525D:rvrNotApplicable:cvnSAMSUNGELECTRONICSCO.,LTD.:ct10:cvrN/A:sku:
dmi.product.name: R425D/R525D
dmi.product.version: Not Applicable
dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1993217/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] Re: Asus ZenBook UX3402 has no sound
** Description changed: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. + Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. -- 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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: New Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. Occurs on 22.04 and 22.10 with standard kernel. Occurs under 22.10 with 6.0.3 mainline kernel. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994948] [NEW] Asus ZenBook UX3402 has no sound
Public bug reported: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: asus cirrus-logic um3402 ux3402 zenbook ** Tags added: asus -- 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/1994948 Title: Asus ZenBook UX3402 has no sound Status in linux package in Ubuntu: New Bug description: [Impact] Asus ZenBook UX3402 has no sound over laptop speakers (speakers work under Windows). BT audio and jack output works. It seems to affect UM3402 as well: https://www.reddit.com/r/ASUS/comments/wc4ojy/zenbook_14_um3402_no_audio_on_linux/ [Where problems could occur] cirrus-logic side-codec is not enabled. [Related bugs] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1965496 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1966010 [Test] Boot patched kernel, sound should be audible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1994948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 crashes during IPL
** 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/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 crashes during IPL Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994693] Re: Align annotations with master kernel
** Description changed: [Issue] - The linux-kvm wasn't using annotations from debian.master, and that - induced a skew in important options between master and kvm. + linux-kvm wasn't using annotations from debian.master, and that induced a + skew in fundamental config options between main and kvm kernels. [Fix] - Apply the attached series. + The attached series (broken down in pieces to ease review) make linux-kvm use + annotations from debian.master and override options that are meant to be + different. + + Must be applied on top of "[SRU][KINETIC linux-kvm][PATCH] UBUNTU: [Config] + Update SQUASHFS configs" already posted on the mailing list. [How to test] - Crank updateconfigs shouldn't report any check-config error. + Crank updateconfigs shouldn't report any check-config error afterward. + + [Regression potential] + + These five patches: + + UBUNTU: [Config] align IMA config with debian.master + UBUNTU: [Config] align UBSAN config with debian.master + UBUNTU: [Config] disable X86_KERNEL_IBT + UBUNTU: [Config] align LSM_MMAP_MIN_ADDR with master + UBUNTU: [Config] align LSM with master + + are the only changes in kvm config, everything else is annotations fix + up. ** Summary changed: - Align annotations with master kernel + linux-kvm: use annotations from debian.master -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1994693 Title: linux-kvm: use annotations from debian.master Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Kinetic: New Bug description: [Issue] linux-kvm wasn't using annotations from debian.master, and that induced a skew in fundamental config options between main and kvm kernels. [Fix] The attached series (broken down in pieces to ease review) make linux-kvm use annotations from debian.master and override options that are meant to be different. Must be applied on top of "[SRU][KINETIC linux-kvm][PATCH] UBUNTU: [Config] Update SQUASHFS configs" already posted on the mailing list. [How to test] Crank updateconfigs shouldn't report any check-config error afterward. [Regression potential] These five patches: UBUNTU: [Config] align IMA config with debian.master UBUNTU: [Config] align UBSAN config with debian.master UBUNTU: [Config] disable X86_KERNEL_IBT UBUNTU: [Config] align LSM_MMAP_MIN_ADDR with master UBUNTU: [Config] align LSM with master are the only changes in kvm config, everything else is annotations fix up. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1994693/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1991725] Re: fails to sign kernel modules
At the time of this writing, this fix is still stuck in -proposed. This makes the Lubuntu release notes wrong, as it makes it so that updating the system prior to installing WiFi drivers is not enough, even though it is documented as being enough. Considering that this fix very nearly was hotfixed into the Kinetic ISOs just before release, it might be helpful if this could be pushed through to -updates as soon as possible. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1991725 Title: fails to sign kernel modules Status in Release Notes for Ubuntu: Fix Released Status in dkms package in Ubuntu: Fix Committed Bug description: Expected on kinetic: dkms will sign built modules with MOK key if requested. What happens: dkms outputs "Binary kmod-sign not found, modules won't be signed" Fix: update dkms to 3.0.7: https://github.com/dell/dkms/pull/242 --- dkms 3.0.6-2ubuntu2 is being tested in kinetic-proposed to resolve this issue To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1991725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1971151] Re: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support
Hi Michael, Friendly reminder ! Thanks, Sumit -- 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/1971151 Title: [Ubuntu 22.04.1] mpi3mr: Add management application interface(BSG) support Status in linux package in Ubuntu: In Progress Bug description: Request to include below mpi3mr driver bug fix patches in Ubuntu 22.04.1(5.15 kernel). These patches got accepted by the upstream and please find the corresponding commit IDs as below: ed567615f7ec scsi: mpi3mr: Fix build errors in uapi header scsi_bsg_mpi3mr.h dde822e21700 scsi: mpi3mr: Update driver version to 8.0.0.69.0 04dfa01e77ea scsi: mpi3mr: Add support for NVMe passthrough 937a6f2c4f2e scsi: mpi3mr: Expose adapter state to sysfs 83959ce5204a scsi: mpi3mr: Add support for PEL commands eb8a3217cd7d scsi: mpi3mr: Add support for MPT commands 455aac4f7a13 scsi: mpi3mr: Move data structures/definitions from MPI headers to uapi header a212ebe7d4b1 scsi: mpi3mr: Add support for driver commands 7fbaf8b0d8b8 scsi: mpi3mr: Add bsg device support Thanks, Sumit To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1971151/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1994601] Re: [UBUNTU 18.04] Ubuntu 18.04 crashes during IPL
I just tried 20.04 (focal legacy image), just to be sure, but it's not affected and worked fine. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1994601 Title: [UBUNTU 18.04] Ubuntu 18.04 crashes during IPL Status in Ubuntu on IBM z Systems: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: ---Problem Description--- Ubuntu 18.04 crashes during IPL with no output on the console. Contact Information = Viktor Mihajlovski ---uname output--- n/a Machine Type = 3096 ---Debugger--- A debugger is not configured ---Steps to Reproduce--- Install Ubuntu 18.04 as a KVM guest using the following command: virt-install -n bionic --cdrom /var/lib/libvirt/images/ubuntu-18.04.5-server-s390x.iso --memory 2048 --disk size=8 then reboot. Stack trace output: no Oops output: no == Comment: #1 - Viktor Mihajlovski - 2022-10-25 10:48:30 == Installing under z/VM leads to the same failure. == Comment: #2 - Viktor Mihajlovski - 2022-10-25 10:55:10 == I have captured a dump using virsh dump --memory-only. The output of crash log is uploaded == Comment: #7 - Harald Freudenberger - 2022-10-26 07:33:52 == Looks like all ubuntu 18.04 installations on s390 are not working any more. It is not an issue with z14 but z17 also fails to run a fresh installed ubuntu 18.04. == Comment: #8 - Harald Freudenberger - 2022-10-26 08:25:52 == when I use the 'advanced installation' where I am able to choose the kernel package and then choose the 4.15.0-50 generic the installed Ubuntu 18.04 comes up fine. So this issue is somewhere between kernel 4.15.0-50 and 4.15.0-194. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1994601/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
