[Kernel-packages] [Bug 1901401] Re: SD card does not work on linux, but window (O2Micro)
Fixed in Ubuntu 21.04 ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1901401 Title: SD card does not work on linux, but window (O2Micro) Status in linux package in Ubuntu: Fix Released Bug description: I try to use a micro SD card (256GB, connected via microSD-to-SD adapter) on my laptop. I could not ... - ...mount my (micro) SD card - ...format with gparted - ...format with "disks" disks error: --- Error wiping device: failed to probe the device "/dev/mmcblk0" (udisks error-quark,0) gparted error: --- "Input/output error during read on /dev/mmcblk0" `lspci -nn` shows: --- SD Host controller [0805]: O2 Micro, Inc. SD/MMC Card Reader Controller [1217:8520] (rev 01) Output of `journalctl -f` when inserting - 10月 25 20:21:08 myuser kernel: mmc0: new ultra high speed SDR104 SDXC card at address 59b4 10月 25 20:21:08 myuser kernel: mmcblk0: mmc0:59b4 EE4S5 239 GiB 10月 25 20:21:08 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:08 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:09 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:09 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:09 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:09 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:09 myuser kernel: ldm_validate_partition_table(): Disk read failed. 10月 25 20:21:09 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:09 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:10 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:10 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:10 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:10 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:10 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:10 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:10 myuser kernel: Dev mmcblk0: unable to read RDB block 0 10月 25 20:21:11 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:11 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:11 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 0 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:11 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 0, async page read 10月 25 20:21:11 myuser kernel: blk_update_request: I/O error, dev mmcblk0, sector 24 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 10月 25 20:21:11 myuser kernel: Buffer I/O error on dev mmcblk0, logical block 3, async page read 10月 25 20:21:12 myuser kernel: mmcblk0: unable to read partition table 10月 25 20:21:13 myuser fwupd[19538]: 11:21:13:0166 FuEngine failed to add udev device /sys/devices/pci:00/:00:1d.0/:03:00.0/mmc_host/mmc0/mmc0:59b4/block/mmcblk0: failed get ffu_capable for (null) I tried: - - Another micoSD-SD adapter: No change - Rebooting: No change I can do: --- - Use the card under Win 10: Same reader, same adapter, same card - Use other SD/microSD cards with the same reader under Linux lsb_release -rd -- Description: Ubuntu 20.04 Release: 20.04 and Description: Ubuntu 20.10 Release: 20.10 digging in `journalctl -b 0` --- xhci_hcd :00:14.0: xHCI Host Controller xhci_hcd :00:14.0: new USB bus registered, assigned bus number 2 xhci_hcd :00:14.0: Host supports USB 3.0 SuperSpeed usb usb2: New USB device found, idVendor=1d6b, idProduct=0003, bcdDevice= 5.08 usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1 usb usb2: Product: xHCI Host Controller usb usb2: Manufacturer: Linux 5.8.0-25-generic xhci-hcd usb usb2: SerialNumber: :00:14.0 hub 2-0:1.0: USB hub found hub 2-0:1.0: 6 ports
[Kernel-packages] [Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
Opened another ticket to upgrade alsa-lib to 1.2.5 for impish. https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930941 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921632 Title: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Confirmed Bug description: [Impact] Ubuntu users ran the kernel on the Dell soundwire audio machines, the dmesg shows the audio mchine driver is not found, then the audio fails to initialize [Fix] Enable the intel soundwire audio machine driver and some related codec driver. [Test] run fakeroot debian/rules clean updateconfigs, and check the config.common.ubuntu, the content is not changed. Build the kernel with this patch applied, the soundwire audio machine driver is built. [Where problems could occur] This could possibly introduce the building failure, I tested it, so far no failure. See also https://bugzilla.kernel.org/show_bug.cgi?id=212465 Default kernel from https://cdimage.ubuntu.com/kubuntu/daily-live/20210327/ and also upstream kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc4/ tested and both do not work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-28 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210326) MachineType: HP HP Spectre x360 Convertible 13-aw2xxx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=/dev/mapper/sys-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 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.11.0-11-generic N/A linux-backports-modules-5.11.0-11-generic N/A linux-firmware 1.195 Tags: hirsute Uname: Linux 5.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 15.10 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8709 dmi.board.vendor: HP dmi.board.version: 31.30 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.30 dmi.modalias: dmi:bvnAMI:bvrF.10:bd12/08/2020:br15.10:efr31.30:svnHP:pnHPSpectrex360Convertible13-aw2xxx:pvr:rvnHP:rn8709:rvr31.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw2xxx dmi.product.sku: 2G2D8EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930941] [NEW] upgrade ALSA libraries to version 1.2.5
Public bug reported: Please build the latest alsa libraries (version 1.2.5) for impish/ upgrade from version 1.2.4 libasound2 1.2.4-1.1ubuntu2 libasound2-data 1.2.4-1.1ubuntu2 alsa-utils 1.2.4-1ubuntu3 alsa-topology-conf 1.2.4-1 alsa-ucm-conf 1.2.4-2ubuntu1.1 alsa-tools 1.2.2-1 alsa-base 1.0.25+dfsg-0ubuntu7 https://alsa-project.org/wiki/Main_Page See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/comments/48 Modern hardware (HP spectre X360) seems to need the latest alsa libraries and configurations. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930941 Title: upgrade ALSA libraries to version 1.2.5 Status in linux package in Ubuntu: New Bug description: Please build the latest alsa libraries (version 1.2.5) for impish/ upgrade from version 1.2.4 libasound2 1.2.4-1.1ubuntu2 libasound2-data 1.2.4-1.1ubuntu2 alsa-utils 1.2.4-1ubuntu3 alsa-topology-conf 1.2.4-1 alsa-ucm-conf 1.2.4-2ubuntu1.1 alsa-tools 1.2.2-1 alsa-base 1.0.25+dfsg-0ubuntu7 https://alsa-project.org/wiki/Main_Page See also https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/comments/48 Modern hardware (HP spectre X360) seems to need the latest alsa libraries and configurations. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
In case of non-kernel packages can ubuntu deviate from debian? According to https://distrowatch.com/table.php?distribution=debian debian uses alsa-lib version 1.2.4 in testing branch. Is it the reason ubuntu cannot upgrade to 1.2.5 of this package for impish? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921632 Title: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Confirmed Bug description: [Impact] Ubuntu users ran the kernel on the Dell soundwire audio machines, the dmesg shows the audio mchine driver is not found, then the audio fails to initialize [Fix] Enable the intel soundwire audio machine driver and some related codec driver. [Test] run fakeroot debian/rules clean updateconfigs, and check the config.common.ubuntu, the content is not changed. Build the kernel with this patch applied, the soundwire audio machine driver is built. [Where problems could occur] This could possibly introduce the building failure, I tested it, so far no failure. See also https://bugzilla.kernel.org/show_bug.cgi?id=212465 Default kernel from https://cdimage.ubuntu.com/kubuntu/daily-live/20210327/ and also upstream kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc4/ tested and both do not work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-28 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210326) MachineType: HP HP Spectre x360 Convertible 13-aw2xxx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=/dev/mapper/sys-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 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.11.0-11-generic N/A linux-backports-modules-5.11.0-11-generic N/A linux-firmware 1.195 Tags: hirsute Uname: Linux 5.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 15.10 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8709 dmi.board.vendor: HP dmi.board.version: 31.30 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.30 dmi.modalias: dmi:bvnAMI:bvrF.10:bd12/08/2020:br15.10:efr31.30:svnHP:pnHPSpectrex360Convertible13-aw2xxx:pvr:rvnHP:rn8709:rvr31.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw2xxx dmi.product.sku: 2G2D8EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921632] Re: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later
Two questions. 1) Will impish 5.13 kernel be backported and made available to ubuntu 21.03/hirsute ? 2) Will the packages libasound2 1.2.4-1.1ubuntu2 libasound2-data1.2.4-1.1ubuntu2 alsa-utils 1.2.4-1ubuntu3 alsa-topology-conf 1.2.4-1 alsa-ucm-conf 1.2.4-2ubuntu1.1 alsa-tools 1.2.2-1 alsa-base 1.0.25+dfsg-0ubuntu7 be upgraded to version 1.2.5 in impish? There is a syntax change in the latest alsa-ucm-conf (git clone https://github.com/alsa-project /alsa-ucm-conf.git) that can be read only with 1.2.5 alsa-utils library. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1921632 Title: build module CONFIG_SND_SOC_INTEL_SOUNDWIRE_SOF_MACH=m for 5.11, 5.13-rc2 and later Status in linux package in Ubuntu: Confirmed Status in linux source package in Hirsute: Fix Committed Status in linux source package in Impish: Confirmed Bug description: [Impact] Ubuntu users ran the kernel on the Dell soundwire audio machines, the dmesg shows the audio mchine driver is not found, then the audio fails to initialize [Fix] Enable the intel soundwire audio machine driver and some related codec driver. [Test] run fakeroot debian/rules clean updateconfigs, and check the config.common.ubuntu, the content is not changed. Build the kernel with this patch applied, the soundwire audio machine driver is built. [Where problems could occur] This could possibly introduce the building failure, I tested it, so far no failure. See also https://bugzilla.kernel.org/show_bug.cgi?id=212465 Default kernel from https://cdimage.ubuntu.com/kubuntu/daily-live/20210327/ and also upstream kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.12-rc4/ tested and both do not work. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu61 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2p', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D7c', '/dev/snd/pcmC0D6c', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 InstallationDate: Installed on 2021-03-28 (0 days ago) InstallationMedia: Kubuntu 21.04 "Hirsute Hippo" - Alpha amd64 (20210326) MachineType: HP HP Spectre x360 Convertible 13-aw2xxx Package: linux (not installed) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm-256color PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-11-generic root=/dev/mapper/sys-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.11.0-11.12-generic 5.11.0 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.11.0-11-generic N/A linux-backports-modules-5.11.0-11-generic N/A linux-firmware 1.195 Tags: hirsute Uname: Linux 5.11.0-11-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 12/08/2020 dmi.bios.release: 15.10 dmi.bios.vendor: AMI dmi.bios.version: F.10 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8709 dmi.board.vendor: HP dmi.board.version: 31.30 dmi.chassis.type: 31 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 31.30 dmi.modalias: dmi:bvnAMI:bvrF.10:bd12/08/2020:br15.10:efr31.30:svnHP:pnHPSpectrex360Convertible13-aw2xxx:pvr:rvnHP:rn8709:rvr31.30:cvnHP:ct31:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Spectre dmi.product.name: HP Spectre x360 Convertible 13-aw2xxx dmi.product.sku: 2G2D8EA#ABU dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921632/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
Ok, I thank you very much for your effort! If anything else comes to your mind I'm willing to do the testing. Can you please suggest how do I get the debug code and what the pm_genpd_add_device() function is? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Incomplete Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.: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.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930921] Re: Apache 2.4.41 corrupts files from samba share
I've added a few more packages to the bug; nothing in the various links suggested to me that anyone has yet identified where the fault lies. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: New Status in linux package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930921] Re: Apache 2.4.41 corrupts files from samba share
** Information type changed from Private Security to Public Security ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: samba (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930921 Title: Apache 2.4.41 corrupts files from samba share Status in apache2 package in Ubuntu: New Status in linux package in Ubuntu: New Status in samba package in Ubuntu: New Bug description: Wenn I serve a samba share with apache 2.4.41 on Ubuntu 20.04 then some files have a corrupt header during transmission. It seems that the first few bytes of the headers are truncated and sometimes other bytes of the download are not belonging to the file. A workaround I found that works is to set "EnableMMAP Off" in the apache config. See other bug reports like this: https://serverfault.com/questions/1044724/apache2-sends-corrupt-responses-when-using-a-cifs-share https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=900821 This is most probably not a bug in Ubuntu itself but I am reporting it here since I assume that a data corruption bug is seen as critical. I am also marking it as a security vulnerability since it seems that wrong parts of memory get exposed during file download. I don't know how random the exposed memory is and if it potentially could expose e.g. secrets. Please feel free to remove the security vulnerability flag if your assessment leads to a different conclusion. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1930921/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Autopkgtest regression report (linux-base/4.5ubuntu3.5)
All autopkgtests for the newly accepted linux-base (4.5ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-55.62~20.04.1 (amd64) linux-gcp-5.8/5.8.0-1032.34~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications
[Kernel-packages] [Bug 1928700] Autopkgtest regression report (linux-base/4.5ubuntu3.5)
All autopkgtests for the newly accepted linux-base (4.5ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-55.62~20.04.1 (amd64) linux-gcp-5.8/5.8.0-1032.34~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1928700 Title: new postinst hook requires initramfs-tools Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [SRU Justification] == Impact == The new postinst hook from bug 1877088 currently requires initramfs-tools installed, or installing a kernel would fail. This happens for me on a builder chroot trying to build linux-meta of a derivative kernel. == Fix == The fix would be to skip running the script if update-initramfs is not available. The check was taken from the /etc/kernel/postinst.d/initramfs-tools script which has exactly that check at the beginning. == Testcase == Building linux-meta in a sbuild chroot which should again work without the messages about verifying links. Reinstalling a kernel on a system with update-initramfs existing should still print the messages. == Regression Potential == Systems with update-initramfs installed and initrd files might for some reason again fail to fix missing links. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1928700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929255] Autopkgtest regression report (linux-base/4.5ubuntu3.5)
All autopkgtests for the newly accepted linux-base (4.5ubuntu3.5) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-hwe-5.8/5.8.0-55.62~20.04.1 (amd64) linux-gcp-5.8/5.8.0-1032.34~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-base [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-kvm/5.4.0.1041.39)
All autopkgtests for the newly accepted linux-meta-kvm (5.4.0.1041.39) for focal have finished running. The following regressions have been reported in tests triggered by the package: evdi/1.7.0+dfsg-1ubuntu1~20.04.3 (amd64) sl-modem/2.9.11~20110321-16ubuntu1 (amd64) virtualbox/6.1.16-dfsg-6~ubuntu1.20.04.2 (amd64) nvidia-graphics-drivers-450-server/450.119.04-0ubuntu0.20.04.2 (amd64) dahdi-linux/1:2.11.1~dfsg-1ubuntu6.2 (amd64) nvidia-graphics-drivers-460/460.80-0ubuntu0.20.04.2 (amd64) lttng-modules/2.12.2-1ubuntu1~20.04.2 (amd64) glibc/2.31-0ubuntu9.2 (amd64) nvidia-graphics-drivers-460-server/460.73.01-0ubuntu0.20.04.1 (amd64) backport-iwlwifi-dkms/8324-0ubuntu3~20.04.3 (amd64) v4l2loopback/0.12.3-1ubuntu0.4 (amd64) oss4/4.2-build2010-5ubuntu6~20.04.2 (amd64) rtl8821ce/5.5.2.1-0ubuntu4~20.04.3 (amd64) rtl8812au/4.3.8.12175.20140902+dfsg-0ubuntu13~20.04.2 (amd64) virtualbox-hwe/6.1.16-dfsg-6ubuntu1.20.04.2 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-kvm [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
Thanks, the kernel from https://people.canonical.com/~khfeng/lp1927808/ seems to work fine. Attaching dmesg output. ** Attachment added: "dmesg-5.13.0-5.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+attachment/5502531/+files/dmesg-5.13.0-5.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/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829620] Re: i7-8565U, sig=0x806eb/20190514, intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security
Same here, DELL LATITUDE 7400, lscpu: Model name: Intel(R) Core(TM) i5-8365U CPU @ 1.60GHz After all my problem is solved by adding the "dis_ucode_ldr" after "quiet splash". Thank you guys. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829620 Title: i7-8565U, sig=0x806eb/20190514, intel-microcode on ASUS makes kernel stuck during loading initramfs on bionic-updates, bionic-security Status in intel-microcode package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-hwe package in Ubuntu: Confirmed Status in linux-hwe-edge package in Ubuntu: Confirmed Bug description: Description: - my system gets stuck at "Booting, Loading initramfs" (the first 2 lines of booting, after grub) - does not even show the enter cryptsetup passphrase - affected kernels: # apt list --installed |grep linux-signed WARNING: apt does not have a stable CLI interface. Use with caution in scripts. linux-signed-generic/bionic-security,bionic-updates,now 4.15.0.50.52 amd64 [installed] linux-signed-generic-hwe-18.04/bionic-security,bionic-updates,now 4.18.0.20.70 amd64 [installed] linux-signed-generic-hwe-18.04-edge/bionic-security,bionic-updates,now 5.0.0.15.71 amd64 [installed] - the setup is not new, has been working perfectly before (about 7 days since my last restart?) System: - HW: ASUS Zenbook 14 UX433FN - Ubuntu 18.04, runing latest HWE, fully updated - grub(-pc), cryptsetup (crypttab entries for custom encrypted LUKS setup), Suspected/possible cause?: - recent intel-microcode package update - recent kernel package updates Steps taken: - tried to remove "splash quiet" from grub/kernel cmd line (also tried adding nosplash, noplymouth) - completely removed nvidia drivers (apt purge *nvidia*) - completely purged and reinstalled grub (grup-pc) - completely purged and reinstalled all kernels (headers, modules, image, ..) - toggle BIOS "fastboot" (now using OFF) - toggle UEFI SecureBoot (now using ON) - remove plymouth (apt remove *plymouth* , but the workaround is working with plymouth installed) Workaround: - so far, I'm only able to boot with non-Ubuntu kernel! (linux-image-liquorix-amd64) - which needs "splash" option ON - reinstall cryptsetup & update-grub (as suggested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829620/comments/10 ) I am not sure how to get you more debug info, as this setup has been working before, and it's a very eary boot-process bug, so I can't even access dmesg etc. EDIT: Hypothesis: Only affects ASUS with i7-8565U Whiskey Lake Intel CPU Upstream Bug Report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/1 WORKAROUND 1: disable intel microcode updates during boot From this bug: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920 1/ add the boot parameter: dis_ucode_ldr to /etc/default/grub 2/ update-grub WORKAROUND 2: downgrade (and hold) intel-microcode to older version from bionic/main apt install --reinstall intel-microcode=3.20180312.0~ubuntu18.04.1 WORKAROUND 3: upgrade BIOS Asus has released updated BIOSes, which probably include the newest microcode. After upgrading workarounds 1,2 are not needed. Please NOTE, unlike workarounds 1,2, BIOS upgrade is permanent and cannot be (easily) reverted. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2337 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge (not installed) Tags: bionic wayland-session Uname: Linux 5.0.0-17.1-liquorix-amd64 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo vboxusers video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 CurrentDesktop: KDE DistroRelease: KDE neon 18.04 InstallationDate: Installed on 2012-12-23 (2339 days ago) InstallationMedia: Kubuntu 12.10 "Quantal Quetzal" - Release amd64 (20121017.1) Package: linux-hwe-edge PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.0.0-15.16~18.04.1-generic 5.0.6 Tags: third-party-packages bionic wayland-session Uname: Linux 5.0.0-15-generic x86_64 UnreportableReason: Toto není oficiální KDE balík. Prosíme odstraňte všechny balíky třetích stran a zkuste to znovu. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm libvirtd lpadmin netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to:
[Kernel-packages] [Bug 1930923] Re: Miscelaneou kernel freeze after connecting USB-C dock
PS: On 5.08 kernel, the bug appears too, but in different form. Instead of "whole-kernel-freeze", some processes trying to write on btrfs filesystem hung, same as some system utilities. The hanged processes sometimes remainded in the system as zombie (as orphans under systemd init), without posibility to remove them (even using waitpid gdb). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930923 Title: Miscelaneou kernel freeze after connecting USB-C dock Status in linux package in Ubuntu: New Bug description: If the notebook (DELL 5590) is connected to USB-C dock I-Tec Metal Nano https://i-tec.pro/en/produkt/c31nanodocklanpd-2/ occasionally (in few hours) the kernel locks itself and hard reset have to be done. There are then usually errors in "journalctl" (after some occurences, nothing is logged, but it is probably due to incompleteness of the writed logs). During each freeze more errors are logged and the error differ, so I append complete logged errors from two cases (I can post more "cases", if it will help). Both memcheck and smart says no error, and without the dock the notebook works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logik 2404 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Fri Jun 4 21:01:08 2021 HibernationDevice: RESUME=UUID=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f InstallationDate: Installed on 2017-01-06 (1610 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude 5590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=be75c71c-97f3-406f-9310-e1bf1252c62a ro quiet splash resume=uuid=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-01 (2 days ago) WifiSyslog: dmi.bios.date: 03/05/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.3 dmi.board.name: 02N9PD dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.3:bd03/05/2021:br1.16:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn02N9PD:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5590 dmi.product.sku: 0817 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930923] [NEW] Miscelaneou kernel freeze after connecting USB-C dock
Public bug reported: If the notebook (DELL 5590) is connected to USB-C dock I-Tec Metal Nano https://i-tec.pro/en/produkt/c31nanodocklanpd-2/ occasionally (in few hours) the kernel locks itself and hard reset have to be done. There are then usually errors in "journalctl" (after some occurences, nothing is logged, but it is probably due to incompleteness of the writed logs). During each freeze more errors are logged and the error differ, so I append complete logged errors from two cases (I can post more "cases", if it will help). Both memcheck and smart says no error, and without the dock the notebook works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logik 2404 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Fri Jun 4 21:01:08 2021 HibernationDevice: RESUME=UUID=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f InstallationDate: Installed on 2017-01-06 (1610 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude 5590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=be75c71c-97f3-406f-9310-e1bf1252c62a ro quiet splash resume=uuid=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-01 (2 days ago) WifiSyslog: dmi.bios.date: 03/05/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.3 dmi.board.name: 02N9PD dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.3:bd03/05/2021:br1.16:svnDellInc.:pnLatitude5590:pvr:rvnDellInc.:rn02N9PD:rvrA05:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 5590 dmi.product.sku: 0817 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute ** Attachment added: "Kernel errors" https://bugs.launchpad.net/bugs/1930923/+attachment/5502494/+files/error.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930923 Title: Miscelaneou kernel freeze after connecting USB-C dock Status in linux package in Ubuntu: New Bug description: If the notebook (DELL 5590) is connected to USB-C dock I-Tec Metal Nano https://i-tec.pro/en/produkt/c31nanodocklanpd-2/ occasionally (in few hours) the kernel locks itself and hard reset have to be done. There are then usually errors in "journalctl" (after some occurences, nothing is logged, but it is probably due to incompleteness of the writed logs). During each freeze more errors are logged and the error differ, so I append complete logged errors from two cases (I can post more "cases", if it will help). Both memcheck and smart says no error, and without the dock the notebook works fine. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: logik 2404 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: X-Cinnamon Date: Fri Jun 4 21:01:08 2021 HibernationDevice: RESUME=UUID=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f InstallationDate: Installed on 2017-01-06 (1610 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) MachineType: Dell Inc. Latitude 5590 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=be75c71c-97f3-406f-9310-e1bf1252c62a ro quiet splash resume=uuid=5f7825a4-cd50-4645-9ff6-32de3bdf9b1f usbcore.autosuspend=-1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-01 (2 days ago) WifiSyslog: dmi.bios.date: 03/05/2021 dmi.bios.release: 1.16 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.3 dmi.board.name: 02N9PD dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias:
[Kernel-packages] [Bug 1925421] Re: arm64 support
** Also affects: linux-oracle (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oracle-5.4 (Ubuntu Groovy) Importance: Undecided Status: New ** Also affects: linux-oracle-5.8 (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux-oracle-5.8 (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: linux-oracle (Ubuntu Groovy) Status: New => Fix Committed ** Changed in: linux-oracle-5.4 (Ubuntu Groovy) Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1925421 Title: arm64 support Status in linux-oracle package in Ubuntu: Fix Released Status in linux-oracle-5.4 package in Ubuntu: New Status in linux-oracle-5.8 package in Ubuntu: New Status in linux-oracle source package in Bionic: Invalid Status in linux-oracle-5.4 source package in Bionic: Fix Released Status in linux-oracle-5.8 source package in Bionic: New Status in linux-oracle source package in Focal: Fix Released Status in linux-oracle-5.4 source package in Focal: Invalid Status in linux-oracle-5.8 source package in Focal: Fix Released Status in linux-oracle source package in Groovy: Fix Committed Status in linux-oracle-5.4 source package in Groovy: Invalid Status in linux-oracle-5.8 source package in Groovy: Fix Committed Bug description: See https://canonical.lightning.force.com/lightning/r/Case/5003z2BzFG4AAN/view for more info [Impact] No support for arm64 currently [Fix] Add arm64 support, including hardware support patches [Test] Confirm that it boots on desired arm64 hardware, as well as VMs [Regression Potential] This was never working on arm64 so there should be no risk of regression. The requested changes included some refactorings of early memory initialization code (all arches) so this presents a small risk. The changes were tested on arm64 as well amd64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oracle/+bug/1925421/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Apologies for not getting back to this earlier, it looks like the verification was already done. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919275] Re: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL
Apologies for not getting back to this earlier, it looks like the verification was already done. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to crash in Ubuntu. https://bugs.launchpad.net/bugs/1919275 Title: crash utility fails on arm64 with cannot determine VA_BITS_ACTUAL Status in crash package in Ubuntu: New Status in linux package in Ubuntu: Incomplete Status in crash source package in Bionic: Fix Committed Status in linux source package in Bionic: Invalid Status in crash source package in Focal: Fix Committed Status in linux source package in Focal: Fix Released Status in crash source package in Groovy: Fix Committed Status in linux source package in Groovy: Fix Released Bug description: [Impact] On Ubuntu Bionic with the 5.4.0-1038-aws kernel the crash utility 7.2.8-1ubuntu0.18.04 fails with: crash: cannot determine VA_BITS_ACTUAL This bug has been addressed upstream and needed patches both in crash and kernel. Kernel patch : commit bbdbc11804ff0b4130e7550113b452e96a74d16e Author: Bhupesh Sharma Date: Thu May 14 00:22:37 2020 +0530 arm64/crash_core: Export TCR_EL1.T1SZ in vmcoreinfo Crash patch : commit 1c45cea02df7f947b4296c1dcaefa1024235ef10 Author: Bhupesh Sharma Date: Tue Jul 14 01:14:49 2020 +0530 arm64: Change tcr_el1_t1sz variable name to TCR_EL1_T1SZ Series affected : Kenrel : This affects Focal (5.4 kernel) and Groovy (5.8 kernel). Hirsute already contains the commit and kernels prior to 5.3 are not affected. Crash : The commit is already in Hirsute. Groovy, Focal and Bionic are affected. In case of Bionic the bug appears only if 5.4 hwe kernel is used. [Test Case] On an arm64 host which runs the affected releases and kernels after creating a crashdump try to open it with crash. It will fail with : crash: cannot determine VA_BITS_ACTUAL [Where problems could occur] Kernel patch : The kernel patch reads the appropriate cpu register and exports TCR_EL1.T1SZ variable in vmcoreinfo. Given that this is a simple operation and that this patch landed upstream in 5.9 and no regressions have been reported, it is safe to assume that the regression potential is minimal. Any potential problem would occur in vmcoreinfo since this is where TCR_EL1.T1SZ variable is exported. Crash patch : This patch renames tcr_el1_t1sz variable to TCR_EL1_T1SZ to be compatible with the kernel change above for crash to be able to read it. The regression potential is small and any problem would regard reading this variable. [Other] Workaround : This bug/change in crash provides a workaround for 5.4+ https://github.com/crash-utility/crash/issues/52 kernels. While it appears as though it this was fixed it https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1858958 it still doesn't seem to work with a 5.4 kernel including. I also tested https://launchpad.net/ubuntu/+source/crash/7.2.8-1ubuntu0.18.04.1/+build/18807621/+files/crash_7.2.8-1ubuntu0.18.04.1_arm64.deb and it exhibits the same problem. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/crash/+bug/1919275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926062] Re: [hirsute/impish] Can't turn bluetooth on again after turning it off
I have the same bug here. You can activate or turn it off but the bluetooth is always "off", for me happens sometimes when I reboot. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1926062 Title: [hirsute/impish] Can't turn bluetooth on again after turning it off Status in bluez package in Ubuntu: Confirmed Status in gnome-control-center package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: When ever i Turn on my system or restart bluetooth is open any it connects to any device. But when i turn off bluetooth and try to turn it on again. it neither turns on nor scans/connects to any device. This is happening since I updated my system to ubuntu 21.04 LTS ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Apr 25 15:09:23 2021 InstallationDate: Installed on 2020-12-15 (130 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 80TR ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=7c507bd4-c66c-4233-a64e-804f6df5412b ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to hirsute on 2021-04-22 (2 days ago) dmi.bios.date: 07/31/2017 dmi.bios.release: 1.29 dmi.bios.vendor: LENOVO dmi.bios.version: 3UCN29WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Nano 5B1 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad 110-15AST dmi.ec.firmware.release: 1.29 dmi.modalias: dmi:bvnLENOVO:bvr3UCN29WW:bd07/31/2017:br1.29:efr1.29:svnLENOVO:pn80TR:pvrLenovoideapad110-15AST:rvnLENOVO:rnNano5B1:rvrNoDPK:cvnLENOVO:ct10:cvrLenovoideapad110-15AST: dmi.product.family: IDEAPAD dmi.product.name: 80TR dmi.product.sku: LENOVO_MT_80TR_BU_idea_FM_Lenovo ideapad 110-15AST dmi.product.version: Lenovo ideapad 110-15AST dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: C8:3D:D4:84:E0:06 ACL MTU: 820:8 SCO MTU: 255:16 DOWN RX bytes:744804 acl:76 sco:0 events:105989 errors:0 TX bytes:51871528 acl:113157 sco:0 commands:192 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1926062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925843] Re: Linux 5.8.0-49+ fails to resume from suspend
I think that's a git bug. Use sha1 directly to workaround the issue: $ git bisect new ce6471a4dff253eab89bd4eb3a84eef6bdba1f44 $ git bisect old 939326287f7e63045200ed4ee1653029a7aa8065 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1925843 Title: Linux 5.8.0-49+ fails to resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: Expected Result: System resumes from suspend and displays the log in screen to unlock the computer. Actual Result: System displays a black screen with a flashing cursor in the upper left and cannot be interacted with. Hard reboot is required to get back to a working system. Additional information: When I boot my computer with 5.8.0-48, the system resumes from suspend as expected. Both 5.8.0-49 and 5.8.0-50 fail to resume from suspend. This problem began after I updated from 20.04 to 20.10 using the Software Updater on 4-19-21. I was using the latest kernel available for 20.04 at that time (5.8.0-48, I think) before updating. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-50-generic 5.8.0-50.56 ProcVersionSignature: Ubuntu 5.8.0-50.56-generic 5.8.18 Uname: Linux 5.8.0-50-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steven 1268 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 23 12:54:52 2021 InstallationDate: Installed on 2020-09-01 (234 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 002: ID 0bda:58eb Realtek Semiconductor Corp. HP Wide Vision HD Camera Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-ce0xx ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-50-generic root=UUID=208c1c0d-3e9e-43da-ba24-0d1cd92b5ad0 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-50-generic N/A linux-backports-modules-5.8.0-50-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/30/2020 dmi.bios.release: 15.23 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F.23 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 838F dmi.board.vendor: HP dmi.board.version: 40.28 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.ec.firmware.release: 40.28 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF.23:bd10/30/2020:br15.23:efr40.28:svnHP:pnOMENbyHPLaptop15-ce0xx:pvr:rvnHP:rn838F:rvr40.28:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-ce0xx dmi.product.sku: 1KV78UA#ABA dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1925843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921345] Re: Support MIPI camera through Intel IPU6
** No longer affects: linux-oem-5.10 (Ubuntu) ** No longer affects: linux-oem-5.10 (Ubuntu Hirsute) -- 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/1921345 Title: Support MIPI camera through Intel IPU6 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Invalid Status in linux-firmware source package in Focal: Fix Released Status in linux-oem-5.10 source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] There are new platforms with MIPI camera based on Intel IPU6(Imaging Processing Unit version 6) currently unsupported in Ubuntu. [Fix] Intel IPU6 can be enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc This patchset took kernel patches from intel/ipu6-drivers. [Test Case] With kernel/firmware properly installed, the hardware should be ready for further development: $ dmesg | grep ipu intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 There should be nearly 24 video4linux devices created under /dev. [Where problems could occur] MIPI camera through Intel IPU6 takes also firmware blobs loaded in runtime from user space, addtional softwares are also required to fully enable it for oridinary use. The exposed video devices are hidden from general users and a relay daemon+v4l2loopback is used to enable use from existing applications. >From kernel's point of view, there is still a known issue that it takes root priviledge to access these devices. [Other Info] So far Intel has no plan to commit this driver to upstream yet, so it's only nominated for oem-5.10. It will only be nominated to generic kernels when the plan/requirements have changed. The original driver Kconfig would disable VIDEO_IPU3_CIO2, but that's reverted to avoid unnecessary changes to existing users. == original bug description == The Intel imaging processing unit version 6, found in Intel SoCs and used for capturing images and video from a camera sensor is enabled by integration of following kernel driver, firmware, userspace HAL libraries as well as a GStreamer source element: * https://github.com/intel/ipu6-drivers * https://github.com/intel/ipu6-camera-bins * https://github.com/intel/ipu6-camera-hal * https://github.com/intel/icamerasrc With all components properly installed, the hardware should be ready for further development: intel-ipu6 intel-ipu: enabling device ( -> 0002) intel-ipu6 intel-ipu: Device 0x9a19 (rev: 0x1) intel-ipu6 intel-ipu: physical base address 0x605400 intel-ipu6 intel-ipu: mapped as: 0x97793328 intel-ipu6 intel-ipu: IPU in secure mode intel-ipu6 intel-ipu: IPC reset done intel-ipu6 intel-ipu: cpd file name: intel/ipu6_fw.bin intel-ipu6 intel-ipu: FW version: 20201222 intel-ipu6 intel-ipu: Sending BOOT_LOAD to CSE intel-ipu6 intel-ipu: Sending AUTHENTICATE_RUN to CSE intel-ipu6 intel-ipu: CSE authenticate_run done intel-ipu6 intel-ipu: IPU driver version 1.0 intel-ipu6-psys intel-ipu6-psys0: pkg_dir entry count:8 intel-ipu6-psys intel-ipu6-psys0: psys probe minor: 0 intel-ipu6-isys intel-ipu6-isys0: bind ov01a1s 20-0036 nlanes is 1 port is 1 intel-ipu6-isys intel-ipu6-isys0: All sensor registration completed. intel-ipu6-isys intel-ipu6-isys0: stream on ov01a1s 20-0036 This one equips an OV01A1S sensor, and HM11B1 is also supported. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1721 F pulseaudio
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Does kernel parameter "intel_idle.max_cstate=1" help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 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.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 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.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias:
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
Ok, I have no idea then. It will be useful if you can print some debug code and find where the error propagates to pm_genpd_add_device(). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Incomplete Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.: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.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
In the meantime please file a bug at https://gitlab.freedesktop.org/drm/amd/-/issues -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Incomplete Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.: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.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871917] Re: Unable to boot 20.04 installer on Dell XPS 15 9560
Same issue on Chuwi Aerobook Pro, except choosing safe graphics makes no difference. Also, no legacy options in bios, and the only way I managed bott it into linux was removing the ssd and installing ubuntu on it on a desktop pc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871917 Title: Unable to boot 20.04 installer on Dell XPS 15 9560 Status in linux package in Ubuntu: Confirmed Bug description: I tried to boot the 20.04 nightly image (focal-desktop-amd64.iso 2020-04-05 11:06 ) as well as an older one (a week ago) on my Dell XPS 15 9560, and I got the same error message each time. The live system performs a filesystem check while showing a progress bar on a screen with dell and ubuntu logo, then the linux console shows with following error: sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x80700 phys_seg 1 prio class 0 sd 2:0:0:0: [sda] tag#0 access beyond end of device blk_update_request: I/O error, dev sda, sector 30529408 op 0x0:(READ) flags 0x0 phys_seg 1 prio class 0 Buffer I/O error on dev sda, logical block 3816176 async page read This happens with two different 16GB usb sticks on the Dell XPS 15. They both worked fine on an old samsung netbook. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871917/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930794] Re: Ubuntu 20.04 LTS does not start after kernel update
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930794 Title: Ubuntu 20.04 LTS does not start after kernel update Status in linux package in Ubuntu: New Bug description: Hi I got a notification to update my kernel to 5.8.0-55 and when I update and reboot my PC. The desktop does not start and when I downgrade my kernel 5.8.0-53. Again, it does not work either. Finally, I have to reimage my PC from the scratch and I lose all of my local data in this situation. I Hope you can solve this critical problem soon. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930794/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930794] [NEW] Ubuntu 20.04 LTS does not start after kernel update
You have been subscribed to a public bug: Hi I got a notification to update my kernel to 5.8.0-55 and when I update and reboot my PC. The desktop does not start and when I downgrade my kernel 5.8.0-53. Again, it does not work either. Finally, I have to reimage my PC from the scratch and I lose all of my local data in this situation. I Hope you can solve this critical problem soon. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- Ubuntu 20.04 LTS does not start after kernel update https://bugs.launchpad.net/bugs/1930794 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930868] Re: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firm
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1930868 Title: Package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Status in firmware-sof package in Ubuntu: New Status in linux-firmware package in Ubuntu: New Bug description: (Reading database ... 220533 files and directories currently installed.) Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 Errors were encountered while processing: /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb Is there a work around? ProblemType: Package DistroRelease: Ubuntu 21.04 Package: firmware-sof-signed (not installed) ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu65.1 AptOrdering: firmware-sof-signed:amd64: Install NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: pass Date: Fri Jun 4 17:22:54 2021 DpkgTerminalLog: Preparing to unpack .../firmware-sof-signed_1.6.1-2_all.deb ... Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 DuplicateSignature: package:firmware-sof-signed:(not installed) Unpacking firmware-sof-signed (1.6.1-2) ... dpkg: error processing archive /var/cache/apt/archives/firmware-sof-signed_1.6.1-2_all.deb (--unpack): trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 ErrorMessage: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 InstallationDate: Installed on 2021-06-02 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.3 SourcePackage: firmware-sof Title: package firmware-sof-signed (not installed) failed to install/upgrade: trying to overwrite '/lib/firmware/intel/sof/sof-apl.ri', which is also in package linux-firmware 1.197 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firmware-sof/+bug/1930868/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
@replydev: Many thanks for the feedback! The patch work comes from Hui Wang, I only posted the easier-to-use .diff. And I assume, this won't be the final version, as we do too indifferently override the kernel default behaviour. But IMO it's a great first step in such a short period of time, based on a coincidential finding. Mainly the sound related Fn keys are problematic. Somehow, they don't send a key release event. It's in discussion and as I'm no programmer I will be patient. (Most of the malfunctioning Fn+ functions are controllable via the DE, at least on here in KDE plasma desktop.) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1758512] Re: No virtual terminals (CTRL+ALT+F?) when no user logged in
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: plasma-desktop (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/1758512 Title: No virtual terminals (CTRL+ALT+F?) when no user logged in Status in gdm3 package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Status in plasma-desktop package in Ubuntu: Confirmed Bug description: As of today's 18.04 version, on a dell xps-13 (the old i7-4500U one), to reproduce: - boot Ubuntu - Press Ctrl+Alt+F2 (or F3 or...) Expected behaviour: virtual console should appear with login prompt. Actual behaviour: nothing happens. When a user is logged in, Ctrl+Alt+F3 switches to terminal tty3... However, hitting first Ctrl+Alt+F1 and, subsequently, hitting Ctrl+Alt+F3 does not show tty3, and remains at the graphical login screen but keyboard and mouse are unresponsive until either Ctrl+Alt+F1 or Ctrl+Alt+F? are pressed, being ? the virtual terminal the ubuntu session is running at. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gdm3 3.27.92-0ubuntu1 ProcVersionSignature: Ubuntu 4.15.0-12.13-generic 4.15.7 Uname: Linux 4.15.0-12-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Mar 24 10:11:26 2018 InstallationDate: Installed on 2014-05-05 (1418 days ago) InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=es_ES.UTF-8 SHELL=/bin/bash SourcePackage: gdm3 UpgradeStatus: Upgraded to bionic on 2018-03-22 (1 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1758512/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
5.13.0-5again with "blacklist=amdgpu modprobe.blacklist=amdgpu" then ssh and modprobe amdgpu: a) black screen & system freeze, no errors in log (attached) b) "Segmentation fault" message in the ssh console right after modprobe amdgpu ** Attachment added: "journal_5.13.0-5again_ModprobeAmdgpu_noX.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+attachment/5502457/+files/journal_5.13.0-5again_ModprobeAmdgpu_noX.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/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Incomplete Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.: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.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1909814] Re: Keyboard not working
@Manuel Krause - #30 Hi and thanks a lot for your work. I compiled my own custom kernel version 5.12.9 with the patch you released using Arch Build System, because of course I use Arch Linux, now the keyboard works well except for Fn functions, some works and others don't. It's not a problem because I don't use fn functions at all. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1909814 Title: Keyboard not working Status in linux package in Ubuntu: Incomplete Bug description: Hello, Brand new laptop (Medion), keyboard is only working with the grub menu. Mouse is now working since 20.10 have been installed. Only the luminosity key are working on the keyboard. External usb keyboard works fine. I tried to install with usb keyboard disconnected but doesn't change anything. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-25-generic 5.8.0-25.26 ProcVersionSignature: Ubuntu 5.8.0-25.26-generic 5.8.14 Uname: Linux 5.8.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: did4364 F pulseaudio /dev/snd/pcmC0D0p: did4364 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jan 1 16:24:12 2021 InstallationDate: Installed on 2021-01-01 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: MEDION S15450 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-25-generic root=UUID=da76ef9f-aca8-4bb0-94a9-03b7cc82a59a ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-25-generic N/A linux-backports-modules-5.8.0-25-generic N/A linux-firmware1.190.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/24/2020 dmi.bios.release: 5.19 dmi.bios.vendor: American Megatrends International, LLC. dmi.bios.version: 209 dmi.board.asset.tag: Default string dmi.board.name: M15T dmi.board.vendor: MEDION dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvr209:bd11/24/2020:br5.19:svnMEDION:pnS15450:pvrDefaultstring:rvnMEDION:rnM15T:rvrDefaultstring:cvnMEDION:ct10:cvrDefaultstring: dmi.product.family: Akoya dmi.product.name: S15450 dmi.product.sku: ML-230008 30030452 dmi.product.version: Default string dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1909814/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929831] Re: cifs: On cifs_reconnect, resolve the hostname again
** Changed in: linux-azure (Ubuntu Focal) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1929831 Title: cifs: On cifs_reconnect, resolve the hostname again Status in linux package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Focal: New Status in linux-azure source package in Focal: Fix Committed Bug description: SRU Justification [Impact] The Microsoft CIFS team is requesting below patch to be backported for 5.4 Azure tuned kernel https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=4e456b30f78c429b183db420e23b26cde7e03a78 A customer is encountering the bug fixed by this patch. [Fix] 7d397a034d5c45528c7bdf7fc3752c4793029cce cifs: rename reconn_inval_dfs_target() 7d6535b720421d58886d5590ffc3617d359aa871 cifs: Simplify reconnect code when dfs upcall is enabled 4e456b30f78c429b183db420e23b26cde7e03a78 cifs: On cifs_reconnect, resolve the hostname again. The first 2 patches are scaffolding to make the backport simpler. the 3rd patch is the bug fix. [Test Plan] The test kernel at https://launchpad.net/~timg-tpi/+archive/ubuntu /cifs-reconnect-sf00309672 has been found to fix the issue. [Where problems could occur] This could perturb CIFS connections in new and different ways. [Other Info] https://canonical.my.salesforce.com/5004K05pQNG To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929831/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925008] Re: no memory hot-plugging in cloud-images
This bug was fixed in the package linux-kvm - 5.11.0-1008.8+21.10.1 --- linux-kvm (5.11.0-1008.8+21.10.1) impish; urgency=medium * impish/linux-kvm: 5.11.0-1008.8+21.10.1 -proposed tracker (LP: #1927567) * Packaging resync (LP: #1786013) - [Packaging] update update.conf - update dkms package versions -- Paolo Pisati Tue, 18 May 2021 17:14:57 +0200 ** Changed in: linux-kvm (Ubuntu) Status: In Progress => Fix Released -- 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/1925008 Title: no memory hot-plugging in cloud-images Status in cloud-images: Invalid Status in linux package in Ubuntu: Fix Released Status in linux-kvm package in Ubuntu: Fix Released Status in linux source package in Focal: Fix Released Status in linux-kvm source package in Focal: Fix Released Status in linux source package in Groovy: Fix Released Status in linux-kvm source package in Groovy: Fix Released Status in linux source package in Hirsute: Fix Released Status in linux-kvm source package in Hirsute: Fix Released Bug description: SRU Justification [Impact] Memory hot-plugging is not working with public cloud-images. Error with dmesg shows: [ 184.544535] acpi PNP0C80:00: Enumeration failure checking kernel configuration: root@ubuntu:/boot# uname -r 5.4.0-1038-kvm root@ubuntu:/boot# grep CONFIG_ACPI_HOTPLUG_MEMORY config-5.4.0-1038-kvm # CONFIG_ACPI_HOTPLUG_MEMORY is not set Obviously the necessary kernel configuration for ACPI memory hotplug is missing. root@ubuntu:~# cat /etc/cloud/build.info build_name: server serial: 20210415 --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' CRDA: N/A CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: Lsusb-t: Error: command ['lsusb', '-t'] failed with exit code 1: /sys/bus/usb/devices: No such file or directory Lsusb-v: Error: command ['lsusb', '-v'] failed with exit code 1: MachineType: QEMU Standard PC (i440FX + PIIX, 1996) Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-1038-kvm root=PARTUUID=a204284f-e3de-498d-a306-c4e7f6b62831 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: Ubuntu 5.4.0-1038.39-kvm 5.4.101 RelatedPackageVersions: linux-restricted-modules-5.4.0-1038-kvm N/A linux-backports-modules-5.4.0-1038-kvm N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill' Tags: focal uec-images Uname: Linux 5.4.0-1038-kvm x86_64 UnreportableReason: This report is about a package that is not installed. UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: False dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.12.0-1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-2.7 dmi.modalias: dmi:bvnSeaBIOS:bvr1.12.0-1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-2.7:cvnQEMU:ct1:cvrpc-i440fx-2.7: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-2.7 dmi.sys.vendor: QEMU [Test Plan] Boot a kernel with CONFIG_ACPI_HOTPLUG_MEMORY enabled. Check that requested memory has been added. [Where problems could occur] Adding memory could fail, or cause other configurations issues. Regressions seem unlikely since this config option is enabled in all cloud kernels except linux-azure. To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1925008/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Attached the corresponding dmesg output for the last tested kernel. ** Attachment added: "dmesg-oem-2030.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927925/+attachment/5502454/+files/dmesg-oem-2030.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 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.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 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.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Tried the kernel from #59, receive speeds are still very poor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 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.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 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.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias:
[Kernel-packages] [Bug 1930879] [NEW] Current hwe-netboot kernel does not support Intel X710 NICs
Public bug reported: Hi. (sorry if this is in the wrong place, but a nice person at #ubuntu@LiberaChat told me to try here) The current hwe-netboot kernel for bionic is still suffering from the bug described in #1893956, which basically lacks the support for Intel X710 NICs. Causing netboot to be impossible with these cards. Would it be possible to update this to a newer version? The kernel that the hwe-netboot installs (5.4.0-74-generic) has the fix included, and the NIC works perfectly fine on a installed OS with that kernel. ** Affects: linux-meta (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1930879 Title: Current hwe-netboot kernel does not support Intel X710 NICs Status in linux-meta package in Ubuntu: New Bug description: Hi. (sorry if this is in the wrong place, but a nice person at #ubuntu@LiberaChat told me to try here) The current hwe-netboot kernel for bionic is still suffering from the bug described in #1893956, which basically lacks the support for Intel X710 NICs. Causing netboot to be impossible with these cards. Would it be possible to update this to a newer version? The kernel that the hwe-netboot installs (5.4.0-74-generic) has the fix included, and the NIC works perfectly fine on a installed OS with that kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1930879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930877] [NEW] oops.kernel.org unusable
Public bug reported: Nothing. Just like debian distribution, this package need to be remove. ** Affects: kerneloops (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to kerneloops in Ubuntu. https://bugs.launchpad.net/bugs/1930877 Title: oops.kernel.org unusable Status in kerneloops package in Ubuntu: New Bug description: Nothing. Just like debian distribution, this package need to be remove. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kerneloops/+bug/1930877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
Can you please give this kernel a try, thanks! https://people.canonical.com/~khfeng/lp1920674-again/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Incomplete Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.: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.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887661] Re: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message
Passed on 5.4.0-75.84-generic On Focal 5.10, the net test build was blocked by bpf build like previous cycle. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1887661 Title: pmtu.sh from net in ubuntu_kernel_selftests failed with no error message Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Fix Released Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux-oem-5.6 package in Ubuntu: Invalid Status in linux source package in Focal: Fix Committed Status in linux-oem-5.10 source package in Focal: Fix Committed Status in linux-oem-5.6 source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-oem-5.10 source package in Groovy: Invalid Status in linux-oem-5.6 source package in Groovy: Invalid Status in linux source package in Hirsute: Fix Released Status in linux-oem-5.10 source package in Hirsute: Invalid Status in linux-oem-5.6 source package in Hirsute: Invalid Status in linux source package in Impish: Fix Released Status in linux-oem-5.10 source package in Impish: Invalid Status in linux-oem-5.6 source package in Impish: Invalid Bug description: [Impact] The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions [SKIP] geneve4 not supported TEST: IPv6 over geneve4: PMTU exceptions [SKIP] TEST: IPv4 over geneve6: PMTU exceptions [ OK ] TEST: IPv6 over geneve6: PMTU exceptions [ OK ] TEST: IPv4 over fou4: PMTU exceptions [ OK ] TEST: IPv6 over fou4: PMTU exceptions [ OK ] TEST: IPv4 over fou6: PMTU exceptions [ OK ] TEST: IPv6 over fou6: PMTU exceptions [ OK ] TEST: IPv4 over gue4: PMTU exceptions [ OK ] TEST: IPv6 over gue4: PMTU exceptions [ OK ] TEST: IPv4 over gue6: PMTU exceptions [ OK ] TEST: IPv6 over gue6: PMTU exceptions [ OK ] TEST: vti6: PMTU exceptions [ OK ] TEST: vti4: PMTU exceptions [ OK ] TEST: vti4: default MTU assignment [ OK ] TEST: vti6: default MTU assignment [ OK ] TEST: vti4: MTU setting on link creation [ OK ] TEST: vti6: MTU setting on link creation [ OK ] TEST: vti6: MTU changes on link changes [ OK ] vxlan4 not supported TEST: ipv4: cleanup of cached exceptions [SKIP] TEST: ipv6: cleanup of cached exceptions [ OK ] TEST: ipv4: list and flush cached exceptions [ OK ] TEST: ipv6: list and flush cached exceptions [ OK ] $ echo $? 1 This is because the test script treats all non-zero return code as a failure, thus it will be marked as FAILED when some sub-test got skipped. [Fix] * ef1220a7d4bbdb selftests: pmtu.sh: use $ksft_skip for skipped return code * 2a9d3716b810a4 selftests: pmtu.sh: improve the test result processing This patchset will: 1. Use the kselftest framework skip code $ksft_skip to replace the hardcoded SKIP return code. 2. Improve the result processing, the test will be marked as PASSED if nothing goes wrong and not all the tests were skipped. These have already landed in newer releases and this test does not exist in B, thus we just need this for F/F-OEM-5.6/F-OEM-5.10/G. The first patch needs to be backported (except on F-OEM-5.10) as some test cases were not added yet. The second one can be cherry-picked. [Test] Run this test directly on a patched kernel. The skipped test will cause failure to this test. [Where problems could occur] Changes limited to testing tools, it's unlikely to cause any problem to kernel functions. [Original Bug Report] Issue found on B-5.4 oracle 5.4.0-1021.21~18.04.1 The pmtu.sh test in net from ubuntu_kernel_selftests will be marked as failed even there is no obvious failure message from the test: $ sudo ./pmtu.sh TEST: ipv4: PMTU exceptions [ OK ] TEST: ipv6: PMTU exceptions [ OK ] vxlan4 not supported TEST: IPv4 over vxlan4: PMTU exceptions [SKIP] vxlan4 not supported TEST: IPv6 over vxlan4: PMTU exceptions [SKIP] TEST: IPv4 over vxlan6: PMTU exceptions [ OK ] TEST: IPv6 over vxlan6: PMTU exceptions [ OK ] geneve4 not supported TEST: IPv4 over geneve4: PMTU exceptions
[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Hi Chris, Here is output of the cat /sys/kernel/debug/hid/0003\:17EF\:60A9.0003/events report (size 3) (numbered) = 01 00 00 # for Fn+F4 report (size 3) (numbered) = 01 00 00 # for Fn+F10 I've added rdesc as attachment as it quite long. ** Attachment added: "cat /sys/kernel/debug/hid/0003\:17EF\:60A9.0003/rdesc" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+attachment/5502431/+files/rdesc -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Please give this one a try: https://people.canonical.com/~khfeng/lp1920674-2/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 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.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 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.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias:
[Kernel-packages] [Bug 1825488] Re: wl driver throws stack trace repeatdly
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: bcmwl (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1825488 Title: wl driver throws stack trace repeatdly Status in bcmwl package in Ubuntu: Confirmed Bug description: wl driver is thriwing stack trace repeatdly in log avril 19 09:13:56 titan kernel: Hardware name: Dell Inc. Inspiron 3521/06RYX8, BIOS A12 10/25/2013 avril 19 09:13:56 titan kernel: RIP: 0010:cfg80211_roamed+0x217/0x230 [cfg80211] avril 19 09:13:56 titan kernel: Code: 00 00 00 49 8d 4d 70 4c 89 f7 45 0f b6 85 90 00 00 00 6a 02 48 8b 36 e8 37 8c fd ff 48 89 43 08 5a 48 85 c0 0f 8 avril 19 09:13:56 titan kernel: RSP: 0018:ae46c150bdb0 EFLAGS: 00010246 avril 19 09:13:56 titan kernel: RAX: RBX: ae46c150be00 RCX: 0002 avril 19 09:13:56 titan kernel: RDX: 0002 RSI: fe01 RDI: c07b92b4 avril 19 09:13:56 titan kernel: RBP: ae46c150bde0 R08: R09: avril 19 09:13:56 titan kernel: R10: ae46c150be00 R11: 9c7f769b4fba R12: 006000c0 avril 19 09:13:56 titan kernel: R13: 9c7f77550c00 R14: 9c7f769b4300 R15: dead0100 avril 19 09:13:56 titan kernel: FS: () GS:9c7f870c() knlGS: avril 19 09:13:56 titan kernel: CS: 0010 DS: ES: CR0: 80050033 avril 19 09:13:56 titan kernel: CR2: 7ffc4c52bbe8 CR3: 000238ada001 CR4: 001626e0 avril 19 09:13:56 titan kernel: Call Trace: avril 19 09:13:56 titan kernel: wl_bss_roaming_done.isra.25+0xd6/0x110 [wl] avril 19 09:13:56 titan kernel: ? wl_bss_roaming_done.isra.25+0xd6/0x110 [wl] avril 19 09:13:56 titan kernel: wl_notify_roaming_status+0x44/0x60 [wl] avril 19 09:13:56 titan kernel: ? down_interruptible+0x33/0x60 avril 19 09:13:56 titan kernel: wl_event_handler+0x6c/0x150 [wl] avril 19 09:13:56 titan kernel: kthread+0x120/0x140 avril 19 09:13:56 titan kernel: ? wl_notify_scan_status+0x230/0x230 [wl] avril 19 09:13:56 titan kernel: ? __kthread_parkme+0x70/0x70 avril 19 09:13:56 titan kernel: ret_from_fork+0x35/0x40 avril 19 09:13:56 titan kernel: ---[ end trace c5aea32843ce9cab ]--- broadcom-sta-dkms does not behave like that. But both driver are unable to let me to connect to my AP with AUTH failed (WPA2 handshake failing) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: bcmwl-kernel-source (not installed) ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Apr 19 10:47:04 2019 InstallationDate: Installed on 2018-05-07 (346 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: bcmwl UpgradeStatus: Upgraded to disco on 2019-04-18 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1825488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825488] Re: wl driver throws stack trace repeatdly
I'm seeing a very similar stacktrace in focal with kernel 5.4.0-73-generic, although it's not constantly popping up AFAICT: [133613.129375] [ cut here ] [133613.129433] WARNING: CPU: 2 PID: 542 at net/wireless/sme.c:973 cfg80211_roamed+0x210/0x230 [cfg80211] [133613.129435] Modules linked in: xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo iptable_nat xt_addrtype iptable_filter bpfilter xt_conntrack nf_nat n f_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c br_netfilter bridge stp llc aufs snd_hda_codec_hdmi intel_powerclamp kvm_intel kvm intel_cstate snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_hda_core snd_hwdep snd_pcm snd_seq_midi samsung_laptop snd_seq_midi_event snd_rawmi di uvcvideo videobuf2_vmalloc videobuf2_memops snd_seq videobuf2_v4l2 btusb videobuf2_common btrtl btbcm btintel videodev bluetooth snd_seq_device serio_raw input_leds s nd_timer joydev mc binfmt_misc ecdh_generic wl(POE) snd ecc cfg80211 soundcore mac_hid sch_fq_codel cuse coretemp parport_pc ppdev lp parport ip_tables x_tables autofs4 hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nouveau mxm_wmi wmi i2c_algo_bit ttm drm_kms_helper syscopyarea sysfillrect psmouse sysimgblt fb_sys_fops [133613.129500] ahci drm sky2 libahci i2c_i801 lpc_ich video [133613.129512] CPU: 2 PID: 542 Comm: wl_event_handle Kdump: loaded Tainted: P W OE 5.4.0-73-generic #82-Ubuntu [133613.129514] Hardware name: SAMSUNG ELECTRONICS CO., LTD. Q430/Q530 /Q430/Q530 , BIOS 02KF.M008.20100529.KSJ 05/29/2010 [133613.129550] RIP: 0010:cfg80211_roamed+0x210/0x230 [cfg80211] [133613.129554] Code: 00 00 00 49 8d 4d 70 4c 89 f7 45 0f b6 85 90 00 00 00 6a 02 48 8b 36 e8 7e 54 fd ff 48 89 43 08 5a 48 85 c0 0f 85 36 fe ff ff <0f> 0b eb 85 0f 0b 4 8 8b 73 08 49 8b 7d 00 e8 1d 4d fd ff e9 71 ff [133613.129556] RSP: 0018:ac4ac0e47db0 EFLAGS: 00010246 [133613.129559] RAX: RBX: ac4ac0e47e00 RCX: 0003 [133613.129561] RDX: 0002 RSI: fe01 RDI: c061587a [133613.129563] RBP: ac4ac0e47de0 R08: R09: 898c94e5e0f8 [133613.129565] R10: 898c94e5efba R11: fffefe0390b6 R12: 0cc0 [133613.129566] R13: 898c911fcc00 R14: 898c94e5e300 R15: dead0100 [133613.129569] FS: () GS:898c9bb0() knlGS: [133613.129571] CS: 0010 DS: ES: CR0: 80050033 [133613.129574] CR2: 7fc10d169000 CR3: 00010500a000 CR4: 06e0 [133613.129576] Call Trace: [133613.129669] wl_bss_roaming_done.isra.0+0xd6/0x110 [wl] [133613.129748] ? wl_bss_roaming_done.isra.0+0xd6/0x110 [wl] [133613.129828] wl_notify_roaming_status+0x46/0x60 [wl] [133613.129834] ? down_interruptible+0x38/0x60 [133613.129913] wl_event_handler+0x6c/0x150 [wl] [133613.129918] kthread+0x104/0x140 [133613.129996] ? wl_notify_scan_status+0x250/0x250 [wl] [133613.12] ? kthread_park+0x90/0x90 [133613.130003] ret_from_fork+0x35/0x40 [133613.130008] ---[ end trace 8542296f4654f377 ]--- [133614.516019] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1825488 Title: wl driver throws stack trace repeatdly Status in bcmwl package in Ubuntu: Confirmed Bug description: wl driver is thriwing stack trace repeatdly in log avril 19 09:13:56 titan kernel: Hardware
[Kernel-packages] [Bug 1929444] Re: SD card initialization on insertion fails
I can confirm that the "author" kernel fixes the problem on my laptop. (And for good measure I've also tested it on my old laptop, which didn't show the problem, and it still works there too). Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1929444 Title: SD card initialization on insertion fails Status in linux package in Ubuntu: New Bug description: If I boot my laptop with an SD card (actually SDXC) in the MMC slot the system sees it and I can mount and use it. If I then unmount it, remove it then re-insert it I get this in the system ,og: [ 194.673108] mmc0: card e624 removed [ 205.462065] mmc0: cannot verify signal voltage switch [ 205.567479] mmc0: error -84 whilst initialising SD card and the card cannot then be used. It was OK in groovy. It's failing in hirsute. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.17.18 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gml44104153 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Mon May 24 17:36:49 2021 HibernationDevice: RESUME=UUID=03dec042-8ba2-48a8-8d19-373ca2e0829c InstallationDate: Installed on 2020-08-13 (284 days ago) InstallationMedia: Kubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: PC Specialist LTD N150CU ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-17-generic root=UUID=b21720c3-60bf-4298-9d73-743672f89216 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-17-generic N/A linux-backports-modules-5.11.0-17-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-05-13 (11 days ago) dmi.bios.date: 11/15/2019 dmi.bios.release: 7.7 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 1.07.07TPCS2 dmi.board.asset.tag: Tag 12345 dmi.board.name: N151CU dmi.board.vendor: CLEVO dmi.board.version: Not Applicable dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Notebook dmi.chassis.version: N/A dmi.ec.firmware.release: 7.7 dmi.modalias: dmi:bvnINSYDECorp.:bvr1.07.07TPCS2:bd11/15/2019:br7.7:efr7.7:svnPCSpecialistLTD:pnN150CU:pvrNotApplicable:rvnCLEVO:rnN151CU:rvrNotApplicable:cvnNotebook:ct10:cvrN/A: dmi.product.family: Not Applicable dmi.product.name: N150CU dmi.product.sku: Not Applicable dmi.product.version: Not Applicable dmi.sys.vendor: PC Specialist LTD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1929444/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922651] Re: r8152 tx status -71
This patch has been applied to Groovy (20.10) via upstream stable update (bug 1929132). ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) 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/1922651 Title: r8152 tx status -71 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Status in linux source package in Groovy: Fix Committed Status in linux source package in Hirsute: Fix Committed Bug description: I've bought ThinkPad T14s with a USB-based docking station. Everything is working marvelously, but from time to time the ethernet port on the docking station won't connect. I've discovered the following messages in my dmesg: [ 400.597506] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 401.164370] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 463.168412] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 465.314415] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 529.409871] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 533.718163] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 591.168537] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 [ 594.335383] r8152 5-1.1:1.0 enx482ae3a2a6f0: Tx status -71 Rebooting the machine doesn't seem to work, turning the ethernet connection off and on doesn't seem to work. I have a dualboot Linux+Windows (one wants to play games from time to time :-p ) and it could be that rebooting from Win to Lin causes this issue, but this needs to be confirmed yet. I will try to power off the computer and/or the docking station, to see whether that would help. I've found numerous bug reports, but they are rather old or may not apply to this situation, therefore I figured it's best to open a new bug report. Thank you so much for your hard work! ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: linux-image-5.8.0-48-generic 5.8.0-48.54 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Apr 6 10:00:29 2021 InstallationDate: Installed on 2021-03-24 (12 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: LENOVO 20UH001QMX ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-48-generic root=UUID=14a0-0947-4e58-ade1-ad9963053d85 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.8.0-48-generic N/A linux-backports-modules-5.8.0-48-generic N/A linux-firmware1.190.3 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/21/2020 dmi.bios.release: 1.30 dmi.bios.vendor: LENOVO dmi.bios.version: R1CET61W(1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20UH001QMX dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.30 dmi.modalias: dmi:bvnLENOVO:bvrR1CET61W(1.30):bd12/21/2020:br1.30:efr1.30:svnLENOVO:pn20UH001QMX:pvrThinkPadT14sGen1:rvnLENOVO:rn20UH001QMX:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14s Gen 1 dmi.product.name: 20UH001QMX dmi.product.sku: LENOVO_MT_20UH_BU_Think_FM_ThinkPad T14s Gen 1 dmi.product.version: ThinkPad T14s Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922651/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gkeop/5.4.0.1017.20)
All autopkgtests for the newly accepted linux-meta-gkeop (5.4.0.1017.20) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-gkeop/5.4.0-1017.18 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gkeop [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Re: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf
@Niklas, would you please give it another try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691 May 6 11:52 System.map-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 4031691 May 6 11:49 System.map-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root37 May 6 11:52 vmlinuz -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw--- 1 root root 8086072 Apr 29 15:54 vmlinuz-5.4.0-29-generic -rw-r--r-- 1 root root 9080832 May 6 11:52 vmlinuz-5.7.0-rc4-06500-gb67ea026badd -rw-r--r-- 1 root root 9080832 May 6 11:49 vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old lrwxrwxrwx 1 root root41 May 6 11:52 vmlinuz.old -> vmlinuz-5.7.0-rc4-06500-gb67ea026badd.old To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1877088/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930637] Re: ath11k WIFI not working in proposed kernel 5.11.0-19-generic
** Changed in: linux (Ubuntu Hirsute)
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/1930637
Title:
ath11k WIFI not working in proposed kernel 5.11.0-19-generic
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Hirsute:
Fix Committed
Bug description:
[SRU Justification]
[Impact]
Bug 1928857 pulls stable patches from v5.11.20, which contains commit
dc764382762e {"bus: mhi: core: Process execution environment changes
serially") that cause a regression on ath11k cards and fails device
init:
mhi mhi0: MHI did not enter SBL
[Fix]
Upsteram commit 4884362f6977 ("bus: mhi: core: Download AMSS image
from appropriate function"), also landed to v5.12.6 but not v5.11
stable tree, has fixed this.
[Test Case]
Tested on Dell XPS 13 9310. No longer has this regression and both
WiFi/Bluetooth works fine as before.
[Where problems could occur]
The actual firmware downloading process is moved into a state machine
callback that has identical semantics with before. Additions or removals
to this in the future may change the timing of fw being dowloaded.
[Other Info]
While the commit causing this regress is backported to 5.11 onward and
fixed in v5.12 and 5.13, leaving Hirsute is the only victim.
== original bug report ==
See these references for more information:
- https://bugzilla.kernel.org/show_bug.cgi?id=213055
- https://bugs.archlinux.org/task/70849
Can you please prevent this already fixed bug from being introduced any
further into Ubuntu.
Thanks.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930637/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930629] Re: Raspberry pi 4 USB controller randomly crashes
Can you provide some additional data? $ apport-collect 1930629 ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1930629 Title: Raspberry pi 4 USB controller randomly crashes Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Focal: New Bug description: My raspberry pi 4 running Ubuntu 20.04 server is constantly having trouble the the usb controller. I have 2 externally powered USB hubs connected that have a few HDDs plugged in. After a seemingly random amount of time (between 1 minute and 2 days) the usb controller will crash completely. No USB devices are detected anymore after that, i have to reboot the system. I have tried: * Providing a lot of cooling (metal case + desktop size fan) * Switching the USB Hubs to a different brand * Switching the power supply of the USB hubs * Switching the power supply of the raspberry Nothing helped, so i concluded that this probably is a kernel bug. I think the USB controller should not crash at the very least. I've attached my dmesg. lsb_release -rd Description:Ubuntu 20.04.2 LTS Release:20.04 linux-raspi version: 5.4.0.1035.70 uname -a Linux pi 5.4.0-1035-raspi #38-Ubuntu SMP PREEMPT Tue Apr 20 21:37:03 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux lsusb (after crash) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1930629/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930694] Re: Hirsute Hippo terminal not working
Can you provide some additional data? $ apport-collect 1930694 ** Summary changed: - Hirtute Hippo terminal not working + Hirsute Hippo terminal not working ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1930694 Title: Hirsute Hippo terminal not working Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Hirsute: New Bug description: Good Morning, Hirtute Hippois working great on the RPI 4. Except one strange behavior. I'am using a wireless keyboard type Logitech K400. Works well with most of the applications. This keyboard does't show characters in the Terminal mode. But if I connect another keyboard to the usb port, but without using it. Then the Logitech wireless keyboard works. Without touching the other connected keyboard. Not found the cause of this problem. Regards, Bram Verkerk To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1930694/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926938] Re: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS
5.10 the official kernel LTS release. If Ubuntu decides to long-term other releases, it's their choice, I'm sticking to 5.10. Making 5.10 even more difficult to install than it already is (going to the mainline "PPA", which isn't really a PPA, is already unfriendly), even if they document the fact on a wiki, is still a 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/1926938 Title: Recent mainline packages are built with Hirsuite 21.04, not Focal 20.04 LTS Status in linux package in Ubuntu: Confirmed Bug description: Hi all, The Mainline wiki states that the mainline kernels are built with the previous LTS toolchain, but the recent 5.12.x and 5.11.x releases are being built with Hirsuite 21.04, and before that Groovy? If this is intentional, then the wiki should be updated to reflect the change in policy. From https://wiki.ubuntu.com/Kernel/MainlineBuilds Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The 5.12 kernel was built with GCC 10.3.0, and 5.11.16 with 10.2.0. On my Focal LTS system I have GCC 9.3.0. The Mainline kernel build toolchain These kernels are built with the toolchain (gcc, g++, etc.) from the previous Ubuntu LTS release. (e.g. Ubuntu 14.04 "Trusty Tahr" / 16.04 "Xenial Xerus" / 18.04 "Bionic Beaver", etc.) Therefore, out-of-tree kernel modules you already have built and installed for use with your release kernels are not likely to work with the mainline builds. The *linux-headers-generic* packages have unmet dependencies on 20.04 LTS. I could install Groovy built kernels fine, but the Hirsuite ones built with GCC 10.3.0 appear to require libc6 >= 2.33. So the new kernels can't be installed on Focal (libc 2.31). Thanks, Mark To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926938/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928146] Re: Please SRU nvidia-modprobe 465.24
Hello Erich, or anyone else affected,
Accepted nvidia-modprobe into hirsute-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/nvidia-
modprobe/465.24.02-1~ubuntu21.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
hirsute to verification-done-hirsute. If it does not fix the bug for
you, please add a comment stating that, and change the tag to
verification-failed-hirsute. In either case, without details of your
testing we will not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags added: verification-needed verification-needed-hirsute
** Tags added: verification-needed-groovy
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
Fix Released
Status in nvidia-modprobe source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
Fix Released
Status in nvidia-modprobe source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Released
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
Debdiffs:
Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
Focal:
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
To manage notifications about this bug
[Kernel-packages] [Bug 1928146] Please test proposed package
Hello Erich, or anyone else affected,
Accepted nvidia-modprobe into groovy-proposed. The package will build
now and be available at https://launchpad.net/ubuntu/+source/nvidia-
modprobe/465.24.02-1~ubuntu20.10.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
groovy to verification-done-groovy. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-groovy. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
** Tags added: verification-needed-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
Fix Released
Status in nvidia-modprobe source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
Fix Released
Status in nvidia-modprobe source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Released
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
Debdiffs:
Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
Focal:
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
To manage notifications about this bug go to:
[Kernel-packages] [Bug 1928146] Please test proposed package
Hello Erich, or anyone else affected,
Accepted nvidia-modprobe into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/nvidia-
modprobe/465.24.02-1~ubuntu20.04.1 in a few hours, and then in the
-proposed repository.
Please help us by testing this new package. See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed. Your feedback will aid us getting this
update out to other Ubuntu users.
If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.
Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in
advance for helping!
N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to nvidia-settings in Ubuntu.
https://bugs.launchpad.net/bugs/1928146
Title:
Please SRU nvidia-modprobe 465.24
Status in nvidia-modprobe package in Ubuntu:
Fix Released
Status in nvidia-settings package in Ubuntu:
Fix Released
Status in nvidia-modprobe source package in Focal:
Fix Committed
Status in nvidia-settings source package in Focal:
Fix Released
Status in nvidia-modprobe source package in Groovy:
Fix Committed
Status in nvidia-settings source package in Groovy:
Fix Released
Status in nvidia-modprobe source package in Hirsute:
Fix Committed
Status in nvidia-settings source package in Hirsute:
Fix Released
Status in nvidia-modprobe source package in Impish:
Fix Released
Status in nvidia-settings source package in Impish:
Fix Released
Bug description:
[Impact]
Users of the Nvidia CUDA libraries using Hirsute, Groovy, or Focal are
unable to install and/or upgrade to version 460.73 of the CUDA
libraries. This is because the new libraries have a versioned hard
dependency on nvidia-modprobe >= 460.73 and nvidia-settings >= 460.73.
This is impacting data scientists and deep learning customers.
[Test Case]
* Add the Nvidia CUDA repositories below:
echo 'deb
http://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/x86_64 /
deb
http://developer.download.nvidia.com/compute/machine-learning/repos/ubuntu1804/x86_64
/
' | sudo tee /etc/apt/sources.list.d/nvidia-cuda.list
sudo apt-get update
* Ensure nvidia and libnvidia files come from the Ubuntu repository:
echo 'Package: nvidia-* libnvidia-* xserver-xorg-*
Pin: release l=NVIDIA CUDA
Pin-Priority: -1' |sudo tee /etc/apt/preferences.d/nvidia-libs.conf
sudo apt-get update
* Install nvidia-driver-460 from the Ubuntu repository:
sudo apt-get install nvidia-driver-460
* Confirm that almost all Nvidia driver packages are set to the same
version (460.73.01) except for nvidia-settings and nvidia-modprobe:
dpkg --list |grep nvidia |grep ^ii |awk '{print $3"\t" $2}' |sort -n
* Attempt to install the CUDA package from Nvidia
sudo apt-get install cuda-drivers-460
* The drivers will not install due to a version mismatch as show
below:
sudo apt-get install cuda-drivers-460
...
The following packages have unmet dependencies:
cuda-drivers-460
Depends: nvidia-modprobe (>= 460.73.01) but 460.32.03-0ubuntu20.04.1 is to be
installed
Depends: nvidia-settings (>= 460.73.01) but 460.39-0ubuntu0.20.04.1 is to be
installed
E: Unable to correct problems, you have held broken packages.
[Where problems could occur]
* This may potentially cause issues with older versions of the Nvidia
driver, but this is low since this is for users of the 460 drivers.
[Other Information]
Can nvidia-modprobe and nvidia-settings be synchronized to match the
other versions provided in this and all future nvidia-drivers-*
metapackages? This should resolve the issue forever going forward.
Debdiffs:
Hirsute: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_460.56-0ubuntu2_460.73.01-0ubuntu1~ubuntu21.04.1~ppa1.diff.gz
Groovy: https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files
/nvidia-
settings_440.82-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.10.1~ppa1.diff.gz
Focal:
https://launchpad.net/~eeickmeyer/+archive/ubuntu/ppa/+files/nvidia-settings_440.64-0ubuntu1_460.73.01-0ubuntu1~ubuntu20.04.1~ppa1.diff.gz
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvidia-modprobe/+bug/1928146/+subscriptions
--
Mailing list:
[Kernel-packages] [Bug 1748105] Re: port80 test in ubuntu_kvm_unit_tests failed with timeout
This test will be removed in the future. (Removed in upstream.) ** Changed in: ubuntu-kernel-tests Status: Triaged => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Po-Hsu Lin (cypressyew) -- 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/1748105 Title: port80 test in ubuntu_kvm_unit_tests failed with timeout Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux-kvm package in Ubuntu: Confirmed Status in linux-oracle-5.0 package in Ubuntu: Confirmed Bug description: With Joshua's comment in bug 1719524: "Nested KVM can only be tried on instance sizes with nested Hypervisor support: Ev3 and Dv3.", although the instance name is E4v3 here but I can start a KVM on it. Test port80 test will timeout on it. Steps: 1. git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 2. cd kvm-unit-tests; ./configure; make 3. Run the port80 test as root: # TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/port80.flat -smp 1 # -initrd /tmp/tmp.3p9PWc2SRi enabling apic begining port 0x80 write test qemu-system-x86_64: terminating on signal 15 from pid 7790 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.14.0-1004-azure-edge 4.14.0-1004.4 ProcVersionSignature: User Name 4.14.0-1004.4-username-edge 4.14.14 Uname: Linux 4.14.0-1004-azure-edge x86_64 ApportVersion: 2.20.1-0ubuntu2.15 Architecture: amd64 Date: Thu Feb 8 06:13:18 2018 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-azure-edge UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1748105/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930707] Re: Mic-mute/mute LEDs not work on some HP platforms
** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: linux (Ubuntu Hirsute) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Hirsute) Status: New => In Progress ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux-oem-5.10 (Ubuntu Hirsute) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-5.10 (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux-oem-5.10 (Ubuntu Focal) 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/1930707 Title: Mic-mute/mute LEDs not work on some HP platforms Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: In Progress Status in linux-oem-5.10 package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Status in linux-oem-5.10 source package in Focal: In Progress Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [Impact] The mic mute/audio mute LEDS are not work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC The right channel of internal speaker doesn't work on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC [Fix] These four platforms need specific quirk for different hardware layout. Thus, add the quirks for them. [Test] After applying the quirk, the LEDs/function are work good on 1) HP ZBook Fury 17.3 Inch G8 Mobile Workstation PC 2) HP ZBook Fury 15.6 Inch G8 Mobile Workstation PC 3) HP ZBook Studio 15.6 Inch G8 Mobile Workstation PC 4) HP EliteBook 855 G8 Notebook PC [Where problems could occur] If HP ships the different system boards design with the same subsystem ID of audio codec which is using different GPIO pins (different layout), then the quirk will not work (LEDs/function will not work when muting audio-output or microphone). To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1930707/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925209] Re: No iwilwifi driver in Linux 5.4.0-1034-raspi
This bug was fixed in the package linux-raspi - 5.4.0-1036.39
---
linux-raspi (5.4.0-1036.39) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1036.39 -proposed tracker (LP: #1927614)
* Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
* hctosys not reading hardware clock on CM4 (LP: #1926911)
- rtc: class: support hctosys from modular RTC drivers
* Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
* No iwilwifi driver in Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
[ Ubuntu: 5.4.0-74.83 ]
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
* linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
* Enable CIFS GCM256 (LP: #1921916)
- smb3: add defines for new crypto algorithms
- smb3.1.1: add new module load parm require_gcm_256
- smb3.1.1: add new module load parm enable_gcm_256
- smb3.1.1: print warning if server does not support requested encryption
type
- smb3.1.1: rename nonces used for GCM and CCM encryption
- smb3.1.1: set gcm256 when requested
- cifs: Adjust key sizes and key generation routines for AES256 encryption
* locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184)
- locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
* [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink
(LP: #1925452)
- net/mlx5: Fix HW spec violation configuring uplink
* Focal update: v5.4.114 upstream stable release (LP: #1926493)
- Revert "scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure"
- Revert "scsi: qla2xxx: Fix stuck login session using prli_pend_timer"
- scsi: qla2xxx: Dual FCP-NVMe target port support
- scsi: qla2xxx: Fix device connect issues in P2P configuration
- scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure
- scsi: qla2xxx: Add a shadow variable to hold disc_state history of fcport
- scsi: qla2xxx: Fix stuck login session using prli_pend_timer
- scsi: qla2xxx: Fix fabric scan hang
- net/sctp: fix race condition in sctp_destroy_sock
- Input: nspire-keypad - enable interrupts only when opened
- gpio: sysfs: Obey valid_mask
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- arc: kernel: Return -EFAULT if copy_to_user() fails
- ASoC: max98373: Added 30ms turn on/off time delay
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ARM: omap1: fix building with clang IAS
- drm/msm: Fix a5xx/a6xx timestamps
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: forbid monitor for add llsec key
- net: ieee802154: forbid monitor for del llsec key
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: forbid monitor for del llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: forbid monitor for del llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- virt_wifi: Return micros for BSS TSF values
- Input: s6sy761 - fix coordinate read bit shift
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- dm verity fec: fix misaligned RS roots IO
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- vfio/pci: Add missing range check in vfio_pci_mmap
- riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
- netfilter: bridge: add pre_exit hooks for ebtable unregistration
- netfilter: arp_tables: add pre_exit hook for
[Kernel-packages] [Bug 1926911] Re: hctosys not reading hardware clock on CM4
This bug was fixed in the package linux-raspi - 5.4.0-1036.39
---
linux-raspi (5.4.0-1036.39) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1036.39 -proposed tracker (LP: #1927614)
* Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
* hctosys not reading hardware clock on CM4 (LP: #1926911)
- rtc: class: support hctosys from modular RTC drivers
* Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
* No iwilwifi driver in Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
[ Ubuntu: 5.4.0-74.83 ]
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
* linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
* Enable CIFS GCM256 (LP: #1921916)
- smb3: add defines for new crypto algorithms
- smb3.1.1: add new module load parm require_gcm_256
- smb3.1.1: add new module load parm enable_gcm_256
- smb3.1.1: print warning if server does not support requested encryption
type
- smb3.1.1: rename nonces used for GCM and CCM encryption
- smb3.1.1: set gcm256 when requested
- cifs: Adjust key sizes and key generation routines for AES256 encryption
* locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184)
- locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
* [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink
(LP: #1925452)
- net/mlx5: Fix HW spec violation configuring uplink
* Focal update: v5.4.114 upstream stable release (LP: #1926493)
- Revert "scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure"
- Revert "scsi: qla2xxx: Fix stuck login session using prli_pend_timer"
- scsi: qla2xxx: Dual FCP-NVMe target port support
- scsi: qla2xxx: Fix device connect issues in P2P configuration
- scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure
- scsi: qla2xxx: Add a shadow variable to hold disc_state history of fcport
- scsi: qla2xxx: Fix stuck login session using prli_pend_timer
- scsi: qla2xxx: Fix fabric scan hang
- net/sctp: fix race condition in sctp_destroy_sock
- Input: nspire-keypad - enable interrupts only when opened
- gpio: sysfs: Obey valid_mask
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- arc: kernel: Return -EFAULT if copy_to_user() fails
- ASoC: max98373: Added 30ms turn on/off time delay
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ARM: omap1: fix building with clang IAS
- drm/msm: Fix a5xx/a6xx timestamps
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: forbid monitor for add llsec key
- net: ieee802154: forbid monitor for del llsec key
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: forbid monitor for del llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: forbid monitor for del llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- virt_wifi: Return micros for BSS TSF values
- Input: s6sy761 - fix coordinate read bit shift
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- dm verity fec: fix misaligned RS roots IO
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- vfio/pci: Add missing range check in vfio_pci_mmap
- riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
- netfilter: bridge: add pre_exit hooks for ebtable unregistration
- netfilter: arp_tables: add pre_exit hook for
[Kernel-packages] [Bug 1926755] Re: Support Auvidea B101 (TC358743)
This bug was fixed in the package linux-raspi - 5.4.0-1036.39
---
linux-raspi (5.4.0-1036.39) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1036.39 -proposed tracker (LP: #1927614)
* Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
* hctosys not reading hardware clock on CM4 (LP: #1926911)
- rtc: class: support hctosys from modular RTC drivers
* Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
* No iwilwifi driver in Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
[ Ubuntu: 5.4.0-74.83 ]
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
* linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
* Enable CIFS GCM256 (LP: #1921916)
- smb3: add defines for new crypto algorithms
- smb3.1.1: add new module load parm require_gcm_256
- smb3.1.1: add new module load parm enable_gcm_256
- smb3.1.1: print warning if server does not support requested encryption
type
- smb3.1.1: rename nonces used for GCM and CCM encryption
- smb3.1.1: set gcm256 when requested
- cifs: Adjust key sizes and key generation routines for AES256 encryption
* locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184)
- locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
* [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink
(LP: #1925452)
- net/mlx5: Fix HW spec violation configuring uplink
* Focal update: v5.4.114 upstream stable release (LP: #1926493)
- Revert "scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure"
- Revert "scsi: qla2xxx: Fix stuck login session using prli_pend_timer"
- scsi: qla2xxx: Dual FCP-NVMe target port support
- scsi: qla2xxx: Fix device connect issues in P2P configuration
- scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure
- scsi: qla2xxx: Add a shadow variable to hold disc_state history of fcport
- scsi: qla2xxx: Fix stuck login session using prli_pend_timer
- scsi: qla2xxx: Fix fabric scan hang
- net/sctp: fix race condition in sctp_destroy_sock
- Input: nspire-keypad - enable interrupts only when opened
- gpio: sysfs: Obey valid_mask
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- arc: kernel: Return -EFAULT if copy_to_user() fails
- ASoC: max98373: Added 30ms turn on/off time delay
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ARM: omap1: fix building with clang IAS
- drm/msm: Fix a5xx/a6xx timestamps
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: forbid monitor for add llsec key
- net: ieee802154: forbid monitor for del llsec key
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: forbid monitor for del llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: forbid monitor for del llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- virt_wifi: Return micros for BSS TSF values
- Input: s6sy761 - fix coordinate read bit shift
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- dm verity fec: fix misaligned RS roots IO
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- vfio/pci: Add missing range check in vfio_pci_mmap
- riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
- netfilter: bridge: add pre_exit hooks for ebtable unregistration
- netfilter: arp_tables: add pre_exit hook for
[Kernel-packages] [Bug 1927108] Re: Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
This bug was fixed in the package linux-raspi - 5.4.0-1036.39
---
linux-raspi (5.4.0-1036.39) focal; urgency=medium
* focal/linux-raspi: 5.4.0-1036.39 -proposed tracker (LP: #1927614)
* Raspberry Pi kernel config doesn't match generic for NFT, breaks LXD
(LP: #1927108)
- [Config] raspi: SET NFT_FIB_INET=m
* hctosys not reading hardware clock on CM4 (LP: #1926911)
- rtc: class: support hctosys from modular RTC drivers
* Support Auvidea B101 (TC358743) (LP: #1926755)
- [Config] raspi: Set VIDEO_TC358743=m
* No iwilwifi driver in Linux 5.4.0-1034-raspi (LP: #1925209)
- [Config] raspi: Set IWLWIFI=m
[ Ubuntu: 5.4.0-74.83 ]
* focal/linux: 5.4.0-74.83 -proposed tracker (LP: #1927619)
* Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
(LP: #1925522)
- debian/dkms-versions -- add NVIDIA 465 and migrate 450 to 460
* linux-image-5.0.0-35-generic breaks checkpointing of container
(LP: #1857257)
- SAUCE: overlayfs: fix incorrect mnt_id of files opened from map_files
* Enable CIFS GCM256 (LP: #1921916)
- smb3: add defines for new crypto algorithms
- smb3.1.1: add new module load parm require_gcm_256
- smb3.1.1: add new module load parm enable_gcm_256
- smb3.1.1: print warning if server does not support requested encryption
type
- smb3.1.1: rename nonces used for GCM and CCM encryption
- smb3.1.1: set gcm256 when requested
- cifs: Adjust key sizes and key generation routines for AES256 encryption
* locking/qrwlock: Fix ordering in queued_write_lock_slowpath() (LP: #1926184)
- locking/qrwlock: Fix ordering in queued_write_lock_slowpath()
* [Ubuntu 21.04] net/mlx5: Fix HW spec violation configuring uplink
(LP: #1925452)
- net/mlx5: Fix HW spec violation configuring uplink
* Focal update: v5.4.114 upstream stable release (LP: #1926493)
- Revert "scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure"
- Revert "scsi: qla2xxx: Fix stuck login session using prli_pend_timer"
- scsi: qla2xxx: Dual FCP-NVMe target port support
- scsi: qla2xxx: Fix device connect issues in P2P configuration
- scsi: qla2xxx: Retry PLOGI on FC-NVMe PRLI failure
- scsi: qla2xxx: Add a shadow variable to hold disc_state history of fcport
- scsi: qla2xxx: Fix stuck login session using prli_pend_timer
- scsi: qla2xxx: Fix fabric scan hang
- net/sctp: fix race condition in sctp_destroy_sock
- Input: nspire-keypad - enable interrupts only when opened
- gpio: sysfs: Obey valid_mask
- dmaengine: dw: Make it dependent to HAS_IOMEM
- ARM: dts: Drop duplicate sha2md5_fck to fix clk_disable race
- ARM: dts: Fix moving mmc devices with aliases for omap4 & 5
- lockdep: Add a missing initialization hint to the "INFO: Trying to
register
non-static key" message
- arc: kernel: Return -EFAULT if copy_to_user() fails
- ASoC: max98373: Added 30ms turn on/off time delay
- neighbour: Disregard DEAD dst in neigh_update
- ARM: keystone: fix integer overflow warning
- ARM: omap1: fix building with clang IAS
- drm/msm: Fix a5xx/a6xx timestamps
- ASoC: fsl_esai: Fix TDM slot setup for I2S mode
- scsi: scsi_transport_srp: Don't block target in SRP_PORT_LOST state
- net: ieee802154: stop dump llsec keys for monitors
- net: ieee802154: forbid monitor for add llsec key
- net: ieee802154: forbid monitor for del llsec key
- net: ieee802154: stop dump llsec devs for monitors
- net: ieee802154: forbid monitor for add llsec dev
- net: ieee802154: forbid monitor for del llsec dev
- net: ieee802154: stop dump llsec devkeys for monitors
- net: ieee802154: forbid monitor for add llsec devkey
- net: ieee802154: forbid monitor for del llsec devkey
- net: ieee802154: stop dump llsec seclevels for monitors
- net: ieee802154: forbid monitor for add llsec seclevel
- pcnet32: Use pci_resource_len to validate PCI resource
- mac80211: clear sta->fast_rx when STA removed from 4-addr VLAN
- virt_wifi: Return micros for BSS TSF values
- Input: s6sy761 - fix coordinate read bit shift
- Input: i8042 - fix Pegatron C15B ID entry
- HID: wacom: set EV_KEY and EV_ABS only for non-HID_GENERIC type of devices
- dm verity fec: fix misaligned RS roots IO
- readdir: make sure to verify directory entry for legacy interfaces too
- arm64: fix inline asm in load_unaligned_zeropad()
- arm64: alternatives: Move length validation in alternative_{insn, endif}
- vfio/pci: Add missing range check in vfio_pci_mmap
- riscv: Fix spelling mistake "SPARSEMEM" to "SPARSMEM"
- scsi: libsas: Reset num_scatter if libata marks qc as NODATA
- netfilter: conntrack: do not print icmpv6 as unknown via /proc
- libnvdimm/region: Fix nvdimm_has_flush() to handle ND_REGION_ASYNC
- netfilter: bridge: add pre_exit hooks for ebtable unregistration
- netfilter: arp_tables: add pre_exit hook for
[Kernel-packages] [Bug 1912673] Re: sounds not working on Dell XPS 17 (9700)
I have done this and can confirm the -19 has working audio! thanks for you work on this! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1912673 Title: sounds not working on Dell XPS 17 (9700) Status in linux package in Ubuntu: Confirmed Status in linux package in Debian: Fix Released Bug description: My investigation process: Dell XPS 17 (9700) comes with Windows 10 preinstalled, where sounds worked. I installed Ubuntu 20.04 LTS fresh, sounds did not work on speakers or 3.5mm headphones, using linux-image-5.4.0-42-generic, I did not try blutooth. I sudo apt upgrade, dist-upgrade to get kernels linux-image-5.8.0-38-generic linux-image-5.8.0-40-generic Sounds did not work. I download linux-image-unsigned-5.10.9-051009-generic. Sounds did not work. I upgrade Dell XPS 9700 firmware from 1.3 to 1.63. Sounds did not work. After googling I found this solution in the comments: https://askubuntu.com/questions/1270442/no-sound-on-xps-17-9700 """ Download and install dkms module: https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/pc-oem- dkms/+packages Alternatively, you can install linux-oem-20.04, it will install the 5.6 kernel with the above driver. Your system may be more stable with 5.4 kernel since it is in wide use. Manually install sof-firmware from Arch Linux: https://archlinux.pkgs.org/rolling/archlinux-extra-x86_64/sof- firmware-1.5.1-1-any.pkg.tar.zst.html You will need to delete the existing "sof" and "sof-tplg" files from the Ubuntu linux-firmware package first. Note if this package gets updated from Canoncial and they don't update these, you will have to delete and then reextract. Files go into the /usr/lib/firmware/intel/sof and /usr/lib/firmware/intel/sof-tplg folders. Manually install the ucm2 files: http://xps17.ddns.net/sof-soundwire.zip These go into /usr/share/alsa/ucm2/sof-soundwire. Delete the contents of the existing sof-soundwire folder (if you have it) and replace them with the ones from the archive. Reboot. You should now have all your audio devices available. If speakers do not play, you may need to run alsamixer (non-root) from a terminal and unmute and set the mixer levels all the way up. """ This solution worked for me on linux-image-5.6.0-1042-oem AFTER manually opening alsa-mixer and changing soundcard to sof. The sound would otherwise just show 'dummy'. My sounds still do not work on 5.8 or 5.10, full name listed above. I did not get to test this temporary fix with 5.4. my full alsa-info: http://alsa-project.org/db/?f=6a638be0cfbe8ed08a010eb26a7702e324dce5ff based on some google research, this seems to be a common problem: https://www.reddit.com/r/Dell/comments/hj8oxw/xps_17_9700_no_audio_on_linux_also_hardware_is/ https://www.reddit.com/r/Dell/comments/hge2yo/no_audio_on_linux_ubuntu_2004_xps_17_9700_realtek/ https://www.reddit.com/r/Dell/comments/j2kdjw/xps_17_9700_on_linux_audio_issue/ etc... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3.10 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 Uname: Linux 5.6.0-1042-oem x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: neoh 1786 F pulseaudio /dev/snd/pcmC1D0p: neoh 1786 F...m pulseaudio /dev/snd/controlC0: neoh 1786 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jan 21 12:08:45 2021 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.3 dmi.board.name: 0CXCCY dmi.board.vendor: Dell Inc. dmi.board.version: A03 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.3:bd12/30/2020:svnDellInc.:pnXPS179700:pvr:rvnDellInc.:rn0CXCCY:rvrA03:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 17 9700 dmi.product.sku: 098F dmi.sys.vendor: Dell Inc. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-20 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) NonfreeKernelModules: nvidia_modeset nvidia Package: linux
[Kernel-packages] [Bug 1929255] Re: update-initrd-links creates incorrect symlinks
Hello Fabien, or anyone else affected, Accepted linux-base into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-base (Ubuntu Hirsute) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1928700] Please test proposed package
Hello Timo, or anyone else affected, Accepted linux-base into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1928700 Title: new postinst hook requires initramfs-tools Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [SRU Justification] == Impact == The new postinst hook from bug 1877088 currently requires initramfs-tools installed, or installing a kernel would fail. This happens for me on a builder chroot trying to build linux-meta of a derivative kernel. == Fix == The fix would be to skip running the script if update-initramfs is not available. The check was taken from the /etc/kernel/postinst.d/initramfs-tools script which has exactly that check at the beginning. == Testcase == Building linux-meta in a sbuild chroot which should again work without the messages about verifying links. Reinstalling a kernel on a system with update-initramfs existing should still print the messages. == Regression Potential == Systems with update-initramfs installed and initrd files might for some reason again fail to fix missing links. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1928700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted linux-base into hirsute-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu5.2 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- hirsute to verification-done-hirsute. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-hirsute. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root
[Kernel-packages] [Bug 1877088] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted linux-base into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root 4031691
[Kernel-packages] [Bug 1929255] Re: update-initrd-links creates incorrect symlinks
Hello Fabien, or anyone else affected, Accepted linux-base into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-base (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: New Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930384] Re: Suspension not possible due to hanging vfs access
Syslog of a case, where virtual machine was not paused - not even touched. I tried to suspend right after opening a youtube tab in firefox. ** Attachment added: "syslog_different_case.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930384/+attachment/5502405/+files/syslog_different_case.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/1930384 Title: Suspension not possible due to hanging vfs access Status in linux package in Ubuntu: Confirmed Bug description: Note: The setup I describe here is perhaps a little special, but the problem itself is - I think - a rather general one. Reproduce = - Setup a vm (locally) - Setup an smb-server within the vm and create a read/writable folder - On physical system: Open Visual Studio Code in that folder (`code ./` while in folder or Menu -> File -> OpenFolder) - < Now VSCode on the host accesses the files on the guest > - Pause the VM - Start suspension - EXPECTED: suspension works - ACTUAL: suspension fails with syslog below: Remarks === It seems, that hanging fs-access actions of an application prevent suspension. I had similar problems with Thunar hanging while trying to opening an inaccessible samba share (non-VM that time) Syslog === myuser kernel: [347533.623866] Freezing of tasks failed after 20.003 seconds (5 tasks refusing to freeze, wq_busy=0): myuser kernel: [347533.624460] codeD0 266587 266536 0x4004 myuser kernel: [347533.624472] Call Trace: myuser kernel: [347533.624495] __schedule+0x212/0x5d0 myuser kernel: [347533.624504] schedule+0x55/0xc0 myuser kernel: [347533.624514] d_alloc_parallel+0x42e/0x4a0 myuser kernel: [347533.624530] ? wake_up_q+0xa0/0xa0 myuser kernel: [347533.624538] __lookup_slow+0x5b/0x150 myuser kernel: [347533.624547] walk_component+0x141/0x1b0 myuser kernel: [347533.624556] link_path_walk.part.0+0x221/0x360 myuser kernel: [347533.624562] ? path_init+0x269/0x410 myuser kernel: [347533.624570] path_lookupat+0x3f/0x1c0 myuser kernel: [347533.624579] filename_lookup+0xaa/0x1b0 myuser kernel: [347533.624595] ? __check_object_size.part.0+0x128/0x150 myuser kernel: [347533.624606] ? __check_object_size+0x1c/0x20 myuser kernel: [347533.624618] ? strncpy_from_user+0x4c/0x150 myuser kernel: [347533.624626] ? getname_flags.part.0+0x4c/0x1b0 myuser kernel: [347533.624635] user_path_at_empty+0x59/0x90 myuser kernel: [347533.624645] vfs_statx+0x81/0x120 myuser kernel: [347533.624655] __do_sys_newstat+0x3e/0x70 myuser kernel: [347533.624666] ? vfs_write+0x169/0x200 myuser kernel: [347533.624677] ? fput+0x13/0x20 myuser kernel: [347533.624691] ? __prepare_exit_to_usermode+0x62/0xe0 myuser kernel: [347533.624702] ? __syscall_return_slowpath+0x31/0x160 myuser kernel: [347533.624710] __x64_sys_newstat+0x16/0x20 myuser kernel: [347533.624718] do_syscall_64+0x49/0xc0 myuser kernel: [347533.624728] entry_SYSCALL_64_after_hwframe+0x44/0xa9 myuser kernel: [347533.624737] RIP: 0033:0x7fc0b518504a myuser kernel: [347533.624742] RSP: 002b:7fc0b0b56858 EFLAGS: 0246 ORIG_RAX: 0004 myuser kernel: [347533.624751] RAX: ffda RBX: 2a263d3326e0 RCX: 7fc0b518504a myuser kernel: [347533.624755] RDX: 7fc0b0b569e0 RSI: 7fc0b0b569e0 RDI: 2a263d3326e0 myuser kernel: [347533.624760] RBP: 7fc0b0b58a10 R08: 0001 R09: myuser kernel: [347533.624764] R10: 0fff R11: 0246 R12: 0007 myuser kernel: [347533.624769] R13: 2a263d66e340 R14: 7fc0b0b59500 R15: 2a263d66e2d0 myuser kernel: [347533.624780] codeD0 266588 266536 0x4004 myuser kernel: [347533.624787] Call Trace: myuser kernel: [347533.624796] __schedule+0x212/0x5d0 myuser kernel: [347533.624804] schedule+0x55/0xc0 myuser kernel: [347533.624811] d_alloc_parallel+0x42e/0x4a0 myuser kernel: [347533.624823] ? wake_up_q+0xa0/0xa0 myuser kernel: [347533.624831] __lookup_slow+0x5b/0x150 myuser kernel: [347533.624839] walk_component+0x141/0x1b0 myuser kernel: [347533.624847] link_path_walk.part.0+0x221/0x360 myuser kernel: [347533.624853] ? path_init+0x269/0x410 myuser kernel: [347533.624861] path_lookupat+0x3f/0x1c0 myuser kernel: [347533.624869] filename_lookup+0xaa/0x1b0 myuser kernel: [347533.624883] ? __check_object_size.part.0+0x128/0x150 myuser kernel: [347533.624894] ? __check_object_size+0x1c/0x20 myuser kernel: [347533.624904] ? strncpy_from_user+0x4c/0x150 myuser kernel: [347533.624912] ? getname_flags.part.0+0x4c/0x1b0 myuser kernel: [347533.624920] user_path_at_empty+0x59/0x90 myuser kernel: [347533.624930] vfs_statx+0x81/0x120 myuser kernel: [347533.624940] __do_sys_newstat+0x3e/0x70 myuser kernel:
[Kernel-packages] [Bug 1928700] Please test proposed package
Hello Timo, or anyone else affected, Accepted linux-base into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu3.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-focal. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1928700 Title: new postinst hook requires initramfs-tools Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [SRU Justification] == Impact == The new postinst hook from bug 1877088 currently requires initramfs-tools installed, or installing a kernel would fail. This happens for me on a builder chroot trying to build linux-meta of a derivative kernel. == Fix == The fix would be to skip running the script if update-initramfs is not available. The check was taken from the /etc/kernel/postinst.d/initramfs-tools script which has exactly that check at the beginning. == Testcase == Building linux-meta in a sbuild chroot which should again work without the messages about verifying links. Reinstalling a kernel on a system with update-initramfs existing should still print the messages. == Regression Potential == Systems with update-initramfs installed and initrd files might for some reason again fail to fix missing links. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1928700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877088] Please test proposed package
Hello bugproxy, or anyone else affected, Accepted linux-base into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1877088 Title: [UBUNTU 20.04] installkernel script does not symlink /boot/initrd.img which is required with the default zipl.conf Status in Ubuntu on IBM z Systems: Fix Committed Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Bug description: [Impact] * initrd link is not updated when using installkernel or "make install" from kernel sources. This leads to boot failure after installing a new kernel with mentioned methods because the kernel does not match initrd. * It's a regression because for Focal it was working before. * Issue was reproduced also on Bionic. * The proposed fixed by Stefan Bader adds a hook in /etc/kernel/postinst.d/ so installkernel will relink the initrd. The kernel DEB packages should not be affected. * The solution from Stefan (first patch) was tested by the bug reporter (niklas.schne...@ibm.com). [Test Plan] * Build a kernel * sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot * Check if /boot/initrd or /initrd symlink to the new initrd [Where problems could occur] * Installing kernel via: installkernel or "make install", so mostly kernel developer environments [Other info from developer] When testing development kernels I usually rely on the installkernel script either through the "make install" target of the Kernel source or manually. This used to work great on Ubuntu on Z. On Ubuntu 20.04 (freshly installed up to date) this fails however because /boot/initrd.img is not updated (/boot/vmlinuz is) and thus zipl installs the wrong kernel/initrd combination rendering the system unbootable. (with the correct modules already copied to /usr/lib/modules/5.7.0-rc4-06500-gb67ea026badd/) # sudo installkernel 5.7.0-rc4-06500-gb67ea026badd bzImage System.map /boot run-parts: executing /etc/kernel/postinst.d/apt-auto-removal 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd run-parts: executing /etc/kernel/postinst.d/initramfs-tools 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd update-initramfs: Generating /boot/initrd.img-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. run-parts: executing /etc/kernel/postinst.d/zz-zipl 5.7.0-rc4-06500-gb67ea026badd /boot/vmlinuz-5.7.0-rc4-06500-gb67ea026badd Using config file '/etc/zipl.conf' Building bootmap in '/boot' Building menu 'menu' Adding #1: IPL section 'ubuntu' (default) Adding #2: IPL section 'old' Preparing boot device: dasda (3844). Done. # ls -l /boot total 178364 -rw--- 1 root root135168 May 6 11:52 bootmap -rw-r--r-- 1 root root 90471 Apr 29 15:34 config-5.4.0-29-generic lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img -> initrd.img-5.4.0-29-generic <== should point to new version -rw-r--r-- 1 root root 19663996 May 6 11:42 initrd.img-5.4.0-29-generic -rw-r--r-- 1 root root 125339494 May 6 11:52 initrd.img-5.7.0-rc4-06500-gb67ea026badd lrwxrwxrwx 1 root root27 May 6 11:40 initrd.img.old -> initrd.img-5.4.0-29-generic -rw--- 1 root root 3087920 Apr 29 15:34 System.map-5.4.0-29-generic -rw-r--r-- 1 root root
[Kernel-packages] [Bug 1928700] Please test proposed package
Hello Timo, or anyone else affected, Accepted linux-base into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1928700 Title: new postinst hook requires initramfs-tools Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Hirsute: Fix Committed Status in linux-base source package in Impish: Fix Released Bug description: [SRU Justification] == Impact == The new postinst hook from bug 1877088 currently requires initramfs-tools installed, or installing a kernel would fail. This happens for me on a builder chroot trying to build linux-meta of a derivative kernel. == Fix == The fix would be to skip running the script if update-initramfs is not available. The check was taken from the /etc/kernel/postinst.d/initramfs-tools script which has exactly that check at the beginning. == Testcase == Building linux-meta in a sbuild chroot which should again work without the messages about verifying links. Reinstalling a kernel on a system with update-initramfs existing should still print the messages. == Regression Potential == Systems with update-initramfs installed and initrd files might for some reason again fail to fix missing links. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1928700/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1929255] Re: update-initrd-links creates incorrect symlinks
Hello Fabien, or anyone else affected, Accepted linux-base into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux- base/4.5ubuntu1.6 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. ** Changed in: linux-base (Ubuntu Bionic) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1929255 Title: update-initrd-links creates incorrect symlinks Status in linux-base package in Ubuntu: Fix Released Status in linux-base source package in Bionic: Fix Committed Status in linux-base source package in Focal: Fix Committed Status in linux-base source package in Groovy: New Status in linux-base source package in Hirsute: New Status in linux-base source package in Impish: Fix Released Bug description: [Impact] ## Problem description Executing the `/etc/kernel/postinst.d/xx-update-initrd-links` script incorrectly detects symbolic links targets and then creates malformed (hence broken) ones instead: /initrd.img -> initrd.imgboot/vmlinuz-5.3.0-53-generic /initrd.img.old -> initrd.imgboot/vmlinuz-5.3.0-53-generic while it should actually be: /initrd.img -> boot/initrd.img-5.3.0-53-generic /initrd.img.old -> boot/initrd.img-5.3.0-53-generic The problem appeared with the release of the version 4.5ubuntu1.5 of the linux-base package, which made this script executable. [Test Plan] * Install new linux-base and initramfs-tools * create /etc/kernel-img.conf with do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = yes * Install one kernel flavour, check that symlinks in /boot have sane targets * Install another kernel, check that symlinks in /boot/ have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it). and check that symlinks in /boot have sane targets. * Purge all kernel, and remove symlinks in /boot * Update /etc/kernel-img.conf to do_symlinks = yes do_bootloader = no do_initrd = yes link_in_boot = no * Install one kernel flavour, check that symlinks in / have sane targets * Install another kernel, check that symlinks in / have sane targets * create a selfbuilt kernel and install it by calling installkernel (you can download kernel debs from kernel-ppa, and unpack them to pretend one has self built it) * remove all kernels, purge initramfs-tools, clean up symlinks in / and /boot * repeat all of the above, without having initramfs-tools installed. I.e. install kernels _without_ recommneds. [Where problems could occur] * The rewritten postinst.d script now simply mostly calls linux- update-links like the normal linux-image postinst script does. One has to make sure that .deb installations of kernels happens correctly and that installkernel way of installing kernels happens correctly. Under different kernel-img.conf settings. The previous incarnations of fixing this and related issues did not account for the above cases and codepaths. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1929255/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927545] Re: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work
Hi Anton, Can you provide the content of /sys/kernel/debug/hid/:17ef:60a9./rdesc and the output of /sys/kernel/debug/hid/:17ef:60a9./events when you press Fn+F4 and Fn+F10? It will help us understand the PTP message format to parse the raw data from the hiddev. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927545 Title: Some of Lenovo Lenovo Essential Wireless Keyboard Fn keys doesn't work Status in linux package in Ubuntu: Confirmed Bug description: I found that some of the Lenovo Lenovo Essential Wireless Keyboard Fn keys don't work. First one is Mute mic (Fn+F4), second one is Scissors (Fn+F10, probably hotkey for Windows Snipping Tool for selective screenshot).gnome-control-panel, xev and evtest doesn't react on pressing these buttons. Here what I was able to get via sudo cat /dev/usb/hiddev0 | hexdump -v -e '/1 "%02X\n"' : For Mute key 00 00 00 FF DC 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 For Scissors 00 00 00 FF DB 00 00 00 00 00 00 FF 00 00 00 00 00 00 00 FF 00 00 00 00 ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-generic 5.11.0.16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 2085 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Thu May 6 22:36:50 2021 InstallationDate: Installed on 2021-04-13 (23 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 174f:1800 Syntek Integrated RGB Camera Bus 001 Device 003: ID 8087:0029 Intel Corp. AX200 Bluetooth Bus 001 Device 002: ID 17ef:60a9 Lenovo Lenovo Essential Wireless Keyboard and Mouse Combo Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO F0FA0066UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=9ef69356-31e9-488f-9a6b-99e10c0ed863 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-04-18 (17 days ago) dmi.bios.date: 03/31/2021 dmi.bios.release: 1.32 dmi.bios.vendor: LENOVO dmi.bios.version: O4VKT32A dmi.board.asset.tag: INVALID dmi.board.name: 371F dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN 3424143288435 dmi.chassis.type: 13 dmi.chassis.vendor: LENOVO dmi.chassis.version: 0.1 dmi.ec.firmware.release: 1.13 dmi.modalias: dmi:bvnLENOVO:bvrO4VKT32A:bd03/31/2021:br1.32:efr1.13:svnLENOVO:pnF0FA0066UA:pvrIdeaCentreAIO527IMB05:rvnLENOVO:rn371F:rvrSDK0J40688WIN3424143288435:cvnLENOVO:ct13:cvr0.1: dmi.product.family: IdeaCentre AIO 5 27IMB05 dmi.product.name: F0FA0066UA dmi.product.sku: LENOVO_MT_F0FA_BU_Lenovo_FM_IdeaCentre AIO 5 27IMB05 dmi.product.version: IdeaCentre AIO 5 27IMB05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927545/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1926597] Re: Linux 5.10.0-1024.25 breaks HDMI with Intel i915
FYI I still do experience this bug with latest 1030 kernel oem. No issue running 5.8 hwe or 5.11 hwe. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1926597 Title: Linux 5.10.0-1024.25 breaks HDMI with Intel i915 Status in linux package in Ubuntu: Incomplete Bug description: Hi, [Thinkpad T480s, Intel iGPU 8550u, Ubuntu Focal up-to-date, GNOME Wayland session] Previous 5.10.0-1023.24 was ok. Kernel 5.8 HWE is ok. I did not test a X session. Plugging HDMI after GNOME is loaded fails to display anything on the HDMI display. Plugging HDMI at boot or at GDM screen makes the HDMI display works as usual. Unplugging HDMI (display only on this one) during GNOME session does not update displays state. Nothing happens. I have to press the switch-display-key on my laptop to actualize the setup and make my laptop's display active. When I unplug HDMI during GNOME session, nothing appears in logs. My laptop fails to enter sleep after having unplugged the HDMI. Related: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1924238 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1926597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930813] [NEW] touchpad not recognised after upgrade 21.04
Public bug reported: Touchpad doesn't work anymore after upgrading to 21.04 on a notebook asus zenbook UX306. Worked perfectly before upgrade ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thilu 11394 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Jun 4 09:15:12 2021 InstallationDate: Installed on 2020-04-23 (406 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=884c588c-71bb-489c-a602-bb6c0463c7c0 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-04 (0 days ago) dmi.bios.date: 08/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrUX305UAB.301:bd08/09/2016:br5.11:svnASUSTeKCOMPUTERINC.:pnUX305UAB:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnUX305UAB:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: UX dmi.product.name: UX305UAB dmi.product.sku: ASUS-NotebookSKU dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930813 Title: touchpad not recognised after upgrade 21.04 Status in linux package in Ubuntu: New Bug description: Touchpad doesn't work anymore after upgrading to 21.04 on a notebook asus zenbook UX306. Worked perfectly before upgrade ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-18-generic 5.11.0-18.19 ProcVersionSignature: Ubuntu 5.11.0-18.19-generic 5.11.17 Uname: Linux 5.11.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: thilu 11394 F pulseaudio CasperMD5CheckResult: unknown CurrentDesktop: GNOME Date: Fri Jun 4 09:15:12 2021 InstallationDate: Installed on 2020-04-23 (406 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 8087:0a2a Intel Corp. Bluetooth wireless interface Bus 001 Device 003: ID 04f2:b56b Chicony Electronics Co., Ltd USB2.0 HD UVC WebCam Bus 001 Device 005: ID 046d:c52b Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. UX305UAB ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-18-generic root=UUID=884c588c-71bb-489c-a602-bb6c0463c7c0 ro quiet splash acpi_backlight=vendor vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-18-generic N/A linux-backports-modules-5.11.0-18-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: Upgraded to hirsute on 2021-06-04 (0 days ago) dmi.bios.date: 08/09/2016 dmi.bios.release: 5.11 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: UX305UAB.301 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: UX305UAB dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
For #28. Thank you, Kai-Heng. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
Please do below step-by-step: 1. install compiler $ sudo apt install build-essential 2. untar attached driver into any place you want $ tar zxvf rtw88_.tar.gz 3. enter the folder 4. compiler driver $ make -f Makefile-rtw88 -j8 5. remove module $ sudo rmmod rtw88_8821ce rtw88_8821c $ sudo rmmod rtw88_pci rtw88_core 6. insert module $ sudo insmod rtw88_core.ko $ sudo insmod rtw88_pci.ko $ sudo insmod rtw88_8821c.ko $ sudo insmod rtw88_8821ce.ko 7. check module paramters $ grep . /sys/module/rtw88_pci/parameters/* 8. try if it works well If any error you meet, please let me know. ** Attachment added: "rtw88_20210604_00_quirk.tar.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+attachment/5502378/+files/rtw88_20210604_00_quirk.tar.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
A custom built Ubuntu kernel with the patch can be found here: https://people.canonical.com/~khfeng/lp1927808/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1786013] Autopkgtest regression report (linux-meta-gcp-5.8/5.8.0.1032.34~20.04.7)
All autopkgtests for the newly accepted linux-meta-gcp-5.8 (5.8.0.1032.34~20.04.7) for focal have finished running. The following regressions have been reported in tests triggered by the package: linux-gcp-5.8/5.8.0-1032.34~20.04.1 (amd64) Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1]. https://people.canonical.com/~ubuntu-archive/proposed- migration/focal/update_excuses.html#linux-meta-gcp-5.8 [1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1786013 Title: Packaging resync Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-edge package in Ubuntu: Confirmed Status in linux source package in Precise: Fix Released Status in linux-azure source package in Precise: Invalid Status in linux-azure-edge source package in Precise: Invalid Status in linux source package in Trusty: Fix Released Status in linux-azure source package in Trusty: Fix Released Status in linux-azure-edge source package in Trusty: Invalid Status in linux source package in Xenial: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-edge source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure-edge source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure-edge source package in Cosmic: Confirmed Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Fix Released Status in linux-azure-edge source package in Disco: Won't Fix Bug description: Ongoing packing resyncs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1786013/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920674] Re: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation
This kernel did not help I'm affraid. 1) 5.13.0-5 with standard kernel params but without "amdgpu.ip_block_mask=0xfdff" => black screen & system freeze during boot (cannot ssh) 2) 5.13.0-5 with "blacklist=amdgpu modprobe.blacklist=amdgpu" then ssh and modprobe amdgpu => black screen & system freeze ... but some errors got caught in journal, attached ** Attachment added: "journal_5.13.0-5_ModprobeAmdgpu_noX.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+attachment/5502376/+files/journal_5.13.0-5_ModprobeAmdgpu_noX.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/1920674 Title: AMD A8-7680 (amdgpu): broken Xorg acceleration and hibernation Status in linux package in Ubuntu: Incomplete Bug description: Dear developers, please let me thank you for all your hard work first of all, I'm a big fan of yours! On my desktop PC with AMD A8-7680 APU, I'm facing 2 problems which seem to be connected to the amdgpu kernel module: 1. Amdgpu kernel module loads correctly during boot, but VESA Xorg module is loaded instead of AMDGPU Xorg module during X startup. This results in non-accelerated X and high CPU load. - This situation is always reproducible. - I'm experiencing it with all kernel versions in between 5.4.0-47-generic and 5.4.0-67-generic inclusive. - The situation escalates more with newer kernel version. For 5.8.0-45-generic and 5.11.8-051108-generic, X even does not start and I just get black screen. - I have found a workaround after many days of googling and testing. AMDGPU Xorg module is loaded correctly if and only if I disable AMD ACP by means of the following kernel boot parameter: amdgpu.ip_block_mask=0xfdff - Acceleration is ok with kernels where AMD ACP is disabled by default (linux-image-linuxlite-5.6.0 for example) 2. The 2nd problem I'm facing is with non functioning hibernation after I "fixed" the X acceleration. Hibernation image does not seem to get created, screen goes black, PC freezes but never turns off whenever AMDGPU Xorg module is loaded. Hibernation and subsequent resume is all ok if I disable AMDGPU by means of "nomodeset" and go just with VESA module. - always reproducible but tested only with 5.4.0-67-generic Thank you and best regards, Radek ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-67-generic 5.4.0-67.75 ProcVersionSignature: Ubuntu 5.4.0-67.75-generic 5.4.94 Uname: Linux 5.4.0-67-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: radek 1513 F pulseaudio /dev/snd/controlC0: radek 1513 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Sun Mar 21 15:22:29 2021 HibernationDevice: RESUME=/dev/disk/by-label/SSD_LinuxSwap IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-67-generic root=UUID=1cc747ae-f2db-4733-aa04-be8d4bde050a ro ipv6.disable=1 net.ifnames=0 nmi_watchdog=0 resume=LABEL=SSD_LinuxSwap amdgpu.ip_block_mask=0xfdff no_console_suspend RelatedPackageVersions: linux-restricted-modules-5.4.0-67-generic N/A linux-backports-modules-5.4.0-67-generic N/A linux-firmware1.187.10 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.20 dmi.board.name: FM2A68M-HD+ dmi.board.vendor: ASRock dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To be filled by O.E.M. dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.20:bd02/13/2019:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnFM2A68M-HD+:rvr:cvnTobefilledbyO.E.M.: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.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1920674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1927808] Re: rtw88_8821ce causes freeze
Running "uname -a" shows: Linux ollee 5.13.0-051300rc4-generic #202105302331 SMP Sun May 30 23:33:24 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux as installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.13-rc4/amd64/ Maybe you could send me the compiled files that I would need to put in place? I do have the kernel headers, but probably not the build tools, nor the knowledge to build. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927808 Title: rtw88_8821ce causes freeze Status in linux package in Ubuntu: Confirmed Bug description: My laptop (Ollee L116HTN6SPW) has a Realtek 8821CE WiFi card. Now at hirsute, this is "supported" in the linux-image-5.11.0-16-generic kernel,and it works "well" for both WiFi and Bluetooth. However, this module (driver) causes frequent freezes, randomly but usually within a few minutes of running (thus very soon after boot): screen display remains frozen, no response to either keyboard or mouse input. All I can do is to hold the power button to power off, then reboot. After reboot, I do not see any crash reports, nor logs about the freeze. Please let me know if I should try to collect some info, and how. For now I use the DKMS module/driver from https://github.com/tomaspinho/rtl8821ce (having blacklisted rtw88_8821ce), and it seems to work perfectly. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: linux-image-5.11.0-16-generic 5.11.0-16.17 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 Uname: Linux 5.11.0-16-generic x86_64 ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: psz1189 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat May 8 16:58:19 2021 InstallationDate: Installed on 2021-04-23 (14 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 058f:5608 Alcor Micro Corp. USB 2.0 Camera Bus 001 Device 003: ID 0bda:c821 Realtek Semiconductor Corp. Bluetooth Radio Bus 001 Device 002: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Protempo Ltd L116HTN6SPW ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.11.0-16-generic root=UUID=f3700d1b-be99-4cb7-baef-c0f157487c64 ro quiet splash pci=noaer vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/26/2020 dmi.bios.release: 5.12 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: YHSM-BI-11.6-X116AR300-AA55C-195-A dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.6 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrYHSM-BI-11.6-X116AR300-AA55C-195-A:bd05/26/2020:br5.12:efr1.6:svnProtempoLtd:pnL116HTN6SPW:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: L116HTN6SPW dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Protempo Ltd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927808/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1925522] Re: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq
For some reason 460.80 won't show the login/display manager screen when plugged into DisplayPort. https://www.reddit.com/r/Ubuntu/comments/nr476z/has_anyone_here_having_issues_with_nvidia_465/h0gcvut/?context=1000 https://forums.developer.nvidia.com/t/465-24-02-page-fault/175782/64 Can you roll back from version 460.80 to 460.7x? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-460 in Ubuntu. https://bugs.launchpad.net/bugs/1925522 Title: Introduce the 465 driver series, fabric-manager, and libnvidia-nscq Status in fabric-manager-450 package in Ubuntu: Fix Released Status in fabric-manager-460 package in Ubuntu: Fix Released Status in libnvidia-nscq-450 package in Ubuntu: Fix Released Status in libnvidia-nscq-460 package in Ubuntu: Fix Released Status in linux-restricted-modules package in Ubuntu: In Progress Status in nvidia-graphics-drivers-450-server package in Ubuntu: In Progress Status in nvidia-graphics-drivers-460 package in Ubuntu: In Progress Status in nvidia-graphics-drivers-465 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: In Progress Status in fabric-manager-450 source package in Bionic: Fix Released Status in fabric-manager-460 source package in Bionic: Fix Released Status in libnvidia-nscq-450 source package in Bionic: Fix Released Status in libnvidia-nscq-460 source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Bionic: Fix Released Status in nvidia-graphics-drivers-460 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-465 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Committed Status in fabric-manager-450 source package in Focal: Fix Released Status in fabric-manager-460 source package in Focal: Fix Released Status in libnvidia-nscq-450 source package in Focal: Fix Released Status in libnvidia-nscq-460 source package in Focal: Fix Released Status in linux-restricted-modules source package in Focal: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Focal: Fix Released Status in nvidia-graphics-drivers-460 source package in Focal: Fix Released Status in nvidia-graphics-drivers-465 source package in Focal: Fix Released Status in nvidia-settings source package in Focal: Fix Committed Status in fabric-manager-450 source package in Groovy: Fix Committed Status in fabric-manager-460 source package in Groovy: Fix Committed Status in libnvidia-nscq-450 source package in Groovy: Fix Committed Status in libnvidia-nscq-460 source package in Groovy: Fix Committed Status in linux-restricted-modules source package in Groovy: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Groovy: Fix Released Status in nvidia-graphics-drivers-460 source package in Groovy: Fix Released Status in nvidia-graphics-drivers-465 source package in Groovy: Fix Released Status in nvidia-settings source package in Groovy: Fix Committed Status in fabric-manager-450 source package in Hirsute: Fix Released Status in fabric-manager-460 source package in Hirsute: Fix Released Status in libnvidia-nscq-450 source package in Hirsute: Fix Released Status in libnvidia-nscq-460 source package in Hirsute: Fix Released Status in linux-restricted-modules source package in Hirsute: Fix Committed Status in nvidia-graphics-drivers-450-server source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-460 source package in Hirsute: Fix Released Status in nvidia-graphics-drivers-465 source package in Hirsute: Fix Released Status in nvidia-settings source package in Hirsute: Fix Committed Bug description: Introduce the new NVIDIA 465 driver series, fabric-manager and libnvidia-nscq. Also migrate the UDA 450 series to the 460 series. [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] [Changelog] == 450-server == * New upstream release (LP: #1925522). -
[Kernel-packages] [Bug 1930760] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502362/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502374/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502373/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502372/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502361/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502367/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502363/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502371/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502364/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502359/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502365/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502360/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-99-generic N/A linux-backports-modules-4.15.0-99-generic N/A linux-firmware 1.173.20 RfKill: Tags: bionic Uname: Linux 4.15.0-99-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: 05/21/2007 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: L1.71 dmi.board.name: ConRoe865PE dmi.board.version: 3.00 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: dmi.product.name: ConRoe865PE dmi.product.version: 3.00 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1930760/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1930760] Re: AGP Radeon Graphics stuck at black screen GUI looping boot
apport information ** Tags added: apport-collected bionic ** Description changed: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon - The temporary workaround is nomodeset in grub options, but I need to use - radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. + The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.23 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: mp 2519 F pulseaudio + /dev/snd/controlC0: mp 2519 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 + InstallationDate: Installed on 2018-12-22 (894 days ago) + InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) + IwConfig: + docker0 no wireless extensions. + + enp2s3no wireless extensions. + + lono wireless extensions. + Package: linux (not installed) + ProcFB: 0 radeondrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic root=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 ro elevator=noop quiet splash resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 vt.handoff=1 + ProcVersionSignature: Ubuntu 4.15.0-99.100-generic 4.15.18 + RelatedPackageVersions: + linux-restricted-modules-4.15.0-99-generic N/A + linux-backports-modules-4.15.0-99-generic N/A + linux-firmware 1.173.20 + RfKill: + + Tags: bionic + Uname: Linux 4.15.0-99-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: 05/21/2007 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: L1.71 + dmi.board.name: ConRoe865PE + dmi.board.version: 3.00 + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrL1.71:bd05/21/2007:svn:pnConRoe865PE:pvr3.00:rvn:rnConRoe865PE:rvr3.00: + dmi.product.name: ConRoe865PE + dmi.product.version: 3.00 ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1930760/+attachment/5502358/+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/1930760 Title: AGP Radeon Graphics stuck at black screen GUI looping boot Status in linux package in Ubuntu: New Bug description: After recommended Ubuntu desktop system update from kernel vmlinuz-4.15.0-99-generic to vmlinuz-4.15.0-142-generic I am stuck at black screen on boot. After update to the latest update kernel vmlinuz-4.15.0-143-generic I also has this problem. With no splash I pictured warning info about radeon from latest kernel(see attachment). Distributor ID: Ubuntu Description: Ubuntu 18.04.5 LTS Release: 18.04 Codename: bionic My Video is: 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] RV730 [Radeon HD 4600 AGP Series] Subsystem: Advanced Micro Devices, Inc. [AMD/ATI] Radeon HD 4650/4670 AGP Kernel driver in use: radeon Kernel modules: radeon The temporary workaround is nomodeset in grub options, but I need to use radeon drivers which worked ok like on vmlinuz-4.15.0-99-generic. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.23 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mp 2519 F pulseaudio /dev/snd/controlC0: mp 2519 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: resume=UUID=8afd3edb-2178-4c74-bd44-d4345b2160a1 resume_offset=5324800 InstallationDate: Installed on 2018-12-22 (894 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IwConfig: docker0 no wireless extensions. enp2s3no wireless extensions. lono wireless extensions. Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-99-generic
[Kernel-packages] [Bug 1927925] Re: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e)
Attached dmesg of a fresh boot with the Kernel from #52. ** Attachment added: "dmesg.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1927925/+attachment/5502354/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1927925 Title: Massive network problems with I219-V on Thinkpad T14 Gen2 (e1000e) Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: I recently got a Thinkpad T14 Gen2 with a I219-V network adapter (8086:15fc). I get very slow connection speeds and even total loss of connectivity without seeing much in the logs (like dmesg etc.). ethtool reports CRC errors and paket loss. Besides Ubuntu 21.04/kernel 5.11 I tried to install Ubuntu 20.04 (kernel seems to old) and i tried the e1000e driver directly from upstream (3.8.7) with no success. A strange behaviour I observed: if connectivity is lost (notebook is not reachable via ping from another host), if I do something like "ping 8.8.8.8" on the notebook itself, it becomes reachable from the other host again. Downloads in general are very slow if they work at all. WLAN (AX210) seems to work fine, wired network using a USB-network adapter works fine, too. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu65 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros3285 F pulseaudio CasperMD5CheckResult: pass DistroRelease: Ubuntu 21.04 HibernationDevice: RESUME=none InstallationDate: Installed on 2021-05-07 (2 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) MachineType: LENOVO 20W0004MGE NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_n51dtp@/vmlinuz-5.11.0-16-generic root=ZFS=rpool/ROOT/ubuntu_n51dtp ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.11.0-16.17-generic 5.11.12 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.11.0-16-generic N/A linux-backports-modules-5.11.0-16-generic N/A linux-firmware 1.197 Tags: hirsute Uname: Linux 5.11.0-16-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8 dmi.modalias: dmi:bvnLENOVO:bvrN34ET21W(1.10):bd03/10/2021:br1.10:efr1.8:svnLENOVO:pn20W0004MGE:pvrThinkPadT14Gen2i:rvnLENOVO:rn20W0004MGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 2i dmi.product.name: 20W0004MGE dmi.product.sku: LENOVO_MT_20W0_BU_Think_FM_ThinkPad T14 Gen 2i dmi.product.version: ThinkPad T14 Gen 2i dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.18 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ros1673 F pulseaudio /dev/snd/controlC1: ros1673 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-05-31 (0 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) MachineType: LENOVO 20W0004MGE Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.10.0-1026-oem root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-1026.27-oem 5.10.31 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.10.0-1026-oem N/A linux-backports-modules-5.10.0-1026-oem N/A linux-firmware 1.187.12 Tags: focal Uname: Linux 5.10.0-1026-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: N/A _MarkForUpload: True dmi.bios.date: 03/10/2021 dmi.bios.release: 1.10 dmi.bios.vendor: LENOVO dmi.bios.version: N34ET21W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20W0004MGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.ec.firmware.release: 1.8
