[Kernel-packages] [Bug 1909680] Re: Ubuntu 20.10 Desktop on Pi4B - random Xorg freezes
Thanks for reporting back. I'll close the ticker as 'Fix Released'. Please open a new one if you encounter the issue again. ** Changed in: linux-raspi (Ubuntu Groovy) Status: New => Fix Released -- 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/1909680 Title: Ubuntu 20.10 Desktop on Pi4B - random Xorg freezes Status in linux-raspi package in Ubuntu: New Status in linux-raspi source package in Groovy: Fix Released Bug description: My system: Linux myRaspi 5.8.0-1010-raspi #13-Ubuntu SMP PREEMPT Wed Dec 9 17:14:07 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux I'm using - Raspberry Pi4B 8GB - Logitech MK120 Keyboard and Mouse (wired) I'm using Ubuntu 20.10 Desktop and get random crashes in both of my desktops, ubuntu and lxqt. After 1 or 2 hours (often during CPU/GPU-heavy work like using Firefox), the system freezes, which means: - Screen freezes (just shows the same picture. mouse-cursor not moving, keyboard not working) - Keyboard not responding (e.g. Num-LED not changing when pressing Num) - Changing to another tty via e.g. Ctrl+Alt+F3 is not working anymore - BUT: System in the background still works. I can still hear audio (of a movie for example). Other tasks like ffmpeg-downloads are still working. During a freeze, Alt+SysRq+k isn't changing much. I can hear the audio stopping. But the system is "too frozen" to be able to kill Xorg. I also tried killing it via ssh - no chance. Alt+SysRq+reisub works to do a Pi-restart. These freezes occur during typing, during clicking, but also when doing nothing with mouse and keyboard (like watching a video). A journalctl-log of the freeze (occurred at 00:08:something when typing with my keyboard) during ubuntu-desktop session is given here (I tried Alt+SysRq+k at 00:10:something without success): [...] Dez 26 00:07:31 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 Dez 26 00:07:36 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 Dez 26 00:07:41 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 Dez 26 00:07:46 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 Dez 26 00:07:48 myRaspi dbus-daemon[4131]: [session uid=1000 pid=4131] Activating via systemd: service name='org.freedesktop.Tracker1' unit='tracker-store.service' requested by ':1.2' (uid=1000 pid=4128 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Dez 26 00:07:48 myRaspi systemd[4119]: Starting Tracker metadata database store and lookup manager... Dez 26 00:07:48 myRaspi dbus-daemon[4131]: [session uid=1000 pid=4131] Successfully activated service 'org.freedesktop.Tracker1' Dez 26 00:07:48 myRaspi systemd[4119]: Started Tracker metadata database store and lookup manager. Dez 26 00:07:49 myRaspi dbus-daemon[4131]: [session uid=1000 pid=4131] Activating via systemd: service name='org.freedesktop.Tracker1.Miner.Extract' unit='tracker-extract.service' requested by ':1.2' (uid=1000 pid=4128 comm="/usr/libexec/tracker-miner-fs " label="unconfined") Dez 26 00:07:49 myRaspi systemd[4119]: Starting Tracker metadata extractor... Dez 26 00:07:49 myRaspi tracker-extract[179165]: Set scheduler policy to SCHED_IDLE Dez 26 00:07:49 myRaspi tracker-extract[179165]: Setting priority nice level to 19 Dez 26 00:07:49 myRaspi dbus-daemon[4131]: [session uid=1000 pid=4131] Successfully activated service 'org.freedesktop.Tracker1.Miner.Extract' Dez 26 00:07:49 myRaspi systemd[4119]: Started Tracker metadata extractor. Dez 26 00:07:51 myRaspi gnome-shell[166054]: JS ERROR: TypeError: windowActor is null _addWindowEffect@resource:///org/gnome/shell/ui/closeDialog.js:90:28 vfunc_show@resource:///org/gnome/shell/ui/closeDialog.js:162:14 Dez 26 00:08:00
[Kernel-packages] [Bug 1914960] Re: no soundcard present with linux-image-5.8.0-43-generic
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1914960 Title: no soundcard present with linux-image-5.8.0-43-generic Status in linux package in Ubuntu: Expired Bug description: Beginning of February 2021 Ubuntu shipped a 3. time in a row (few months difference) a Kernel update that does not discover the onboard sound card. Same problem as described here: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1910920 Booting back into linux-image-5.8.0-41-generic works. my on-board sound card & USB headset are well recognized! To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1914960/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1908264] Re: Disable Atari partition support for cloud kernels
** No longer affects: linux-gke (Ubuntu Hirsute) ** No longer affects: linux-gke (Ubuntu Groovy) ** No longer affects: linux-gke (Ubuntu Bionic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1908264 Title: Disable Atari partition support for cloud kernels Status in linux-aws package in Ubuntu: In Progress Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure-4.15 package in Ubuntu: Invalid Status in linux-gcp package in Ubuntu: New Status in linux-gke package in Ubuntu: New Status in linux-gkeop package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-aws source package in Xenial: Fix Committed Status in linux-azure source package in Xenial: Fix Released Status in linux-azure-4.15 source package in Xenial: Invalid Status in linux-aws source package in Bionic: Fix Released Status in linux-azure source package in Bionic: Invalid Status in linux-azure-4.15 source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: New Status in linux-oracle source package in Bionic: New Status in linux-aws source package in Focal: Fix Released Status in linux-azure source package in Focal: Fix Released Status in linux-azure-4.15 source package in Focal: Invalid Status in linux-gcp source package in Focal: New Status in linux-gke source package in Focal: New Status in linux-gkeop source package in Focal: New Status in linux-oracle source package in Focal: New Status in linux-aws source package in Groovy: Fix Committed Status in linux-azure source package in Groovy: Fix Released Status in linux-azure-4.15 source package in Groovy: Invalid Status in linux-gcp source package in Groovy: New Status in linux-oracle source package in Groovy: New Status in linux-aws source package in Hirsute: In Progress Status in linux-azure source package in Hirsute: Fix Released Status in linux-azure-4.15 source package in Hirsute: Invalid Status in linux-gcp source package in Hirsute: New Status in linux-oracle source package in Hirsute: New Bug description: [Impact] Atari partition tables have very broad specifications, and can spontaneously show up on uncleared disks with "garbage" data. There have been reports of misinterpreted AHDI partition tables before (see [0] and [1]), usually as an unintended side-effect of using non-zeroed disks. Users of this specific partition scheme are unlikely to be on AWS instances, so we should disable them. [0] https://lore.kernel.org/linux-block/1467736712-11825-1-git-send-email-kris...@linux.vnet.ibm.com/ [1] https://mail-index.netbsd.org/port-atari/1995/11/19/0001.html [Test Case] Ensure that CONFIG_ATARI_PARTITION is not set in /boot/config-$(uname -r) [Fix] Unset CONFIG_ATARI_PARTITION in debian.aws/config/config.common.ubuntu [Regression Potential] There could be unexpected dependencies on Atari partitions that are impacted by this change. Considering Atari hardware hasn't been produced in a long time, and is unlikely to be used in AWS instances, the regression potential should be very low. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-aws/+bug/1908264/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1919408] Re: [amdgpu] System freeze
I don't see anything related in the logs, but a full system freeze could be another hardware problem. Not sure what to do next... ** Summary changed: - [amdgpu] GUI freeze + [amdgpu] System freeze -- 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/1919408 Title: [amdgpu] System freeze Status in linux package in Ubuntu: Incomplete Bug description: After copied (dd copy) old disk /home to bigger one then reboot xorg start to freeze it seems kernel crash rather than only Xorg, because all input devices (keyboard, mouse) turned off completely. only option is hard reboot. I upgrade distro from 20.04 to 20.10, the situation remain the same after every login to desktop the system freeze completely and need it to do hard reboot. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: xorg 1:7.7+19ubuntu15 ProcVersionSignature: Ubuntu 5.8.0-45.51-lowlatency 5.8.18 Uname: Linux 5.8.0-45-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] CompositorRunning: None CurrentDesktop: MATE Date: Wed Mar 17 01:11:19 2021 DistUpgraded: 2021-03-15 02:52:49,427 INFO cache.commit() DistroCodename: groovy DistroVariant: ubuntu ExtraDebuggingInterest: Yes GconfCompiz: /apps/compiz-1/general: /apps/compiz-1/general/screen0: /apps/compiz-1/general/screen0/options: active_plugins = [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] GpuHangFrequency: Continuously GpuHangReproducibility: Occurs more often under certain circumstances GpuHangStarted: Within the last week or two GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Radeon RX 570 [1682:c570] InstallationDate: Installed on 2018-05-05 (1046 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: To be filled by O.E.M. To be filled by O.E.M. ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-lowlatency root=UUID=17faa721-1006-4426-b460-57b94bfebefa ro threadirqs crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=512M-:192M SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to groovy on 2021-03-15 (1 days ago) dmi.bios.date: 04/10/2013 dmi.bios.release: 4.6 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1708 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: M5A99FX PRO R2.0 dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx 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.:bvr1708:bd04/10/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx: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: SKU dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: To be filled by O.E.M. version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 version.libdrm2: libdrm2 2.4.102-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921403] Re: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels
** Changed in: makedumpfile (Debian) Status: New => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1921403 Title: makedumpfile does not create dmesg file in /var/crash on 5.10+ kernels Status in makedumpfile package in Ubuntu: New Status in makedumpfile source package in Hirsute: New Status in makedumpfile package in Debian: Fix Released Bug description: makedumpfile does not create the dmesg. in /var/crash. This happens only on 5.10+ kernel because 5.10 kernel introduces a new lockless ringbuffer. This issue has been addressed upstream with commits : [1] c617ec633392([PATCH 1/2] printk: add support for lockless ringbuffer) [2] 44b073b7ec46([PATCH 2/2] printk: use committed/finalized state values) [1] https://github.com/makedumpfile/makedumpfile/commit/c617ec63339222f3a44d73e36677a9acc8954ccd [2] https://github.com/makedumpfile/makedumpfile/commit/44b073b7ec467aee0d7de381d455b8ace1199184 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1921403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920874] Re: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+
Hi Chris, may you please verify that the Focal kernel in -proposed resolves the problem encountered? If it does, you can leave a comment letting me know and/or update the tag from 'verification-needed-focal' to 'verification-done-focal'. Thank you! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1920874 Title: [Regression] Partition not removed after removing the memory cards from card reader since kernel 5.9.0-rc3+ Status in HWE Next: New 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: Fix Committed Status in linux source package in Hirsute: In Progress Status in linux-oem-5.10 source package in Hirsute: Invalid Bug description: [SRU Justification] [Impact] Memory card removal event can not be reflected via uevent on some card readers Ex. Realtek card readers 0bda:0328 and 0bda:0158. Thus the file browser still see the ghost disk even it's already removed. [Fix] Found the commit 6540fbf6b643 in 5.9.0-rc3 introduce this regression. Fix it by making sure the partition scan will never be skipped for each vfs_open until the partition scan is really done [Test] Verified on the Realtek card reader 0bda:0328 on Dell Precision 7820 and the external Realtek usb interface card reader 0bda:0158. Insert the SD card in the card reader $ udevadm monitor Remove the SD card and check the udevadm monitor output KERNEL[188.377042] change /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.383261] remove /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) KERNEL[188.390887] change /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) UDEV [188.396012] remove /devices/pci:00/:00:14.0/usb2/2-9/2-9:1.0/host5/target5:0:0/5:0:0:0/block/sdc (block) The remove event should be observed from the output messages. On the affected card reader, only change event would be observed. [Where problem could occur] These kind of card readers doesn't send remove event of scsi_disk and scsi_device like others so they only depend on the block subsystem to detect the media change and relect the removal event by partition scan. The behavior related to media removal is changed after 5.9.0-rc3. The remove event is not able to be correcly reflected since then, the device node of the media will remain there until next card insertion. == Original Bug Description == Ubuntu version: 20.10 Kernel: 5.10.0-1013-oem Card reader: Realtek Card Reader (0bda:0328 and 0bda:0158) Summary === After upgrading to kernel 5.9.0-rc3 or later, the device node for the partitions on the memory cards will not disappear after removing the memory cards. This is confusing to the user level applications like File Browser since the partition label will remain there for a long time. Steps to reproduce == 1. Upgrade to kernel later than 5.9.0-rc3 2. Plug the external card reader and insert the formatted memory card 3. Verify if the memory card mounted and visible on File Browser 4. Remove the memory card from the card reader 5. Verify if the mounted memory card removed from the File Browser Expected results The mounted memory card identifier should be disappear after remove the memory card Actual results == The partition label of the memory card exists for a long time. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: dev1443 F pulseaudio /dev/snd/controlC0: dev1443 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2021-03-22 (0 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Release amd64 (20201022) MachineType: ASUSTeK COMPUTER INC. ZenBook UX434IQ_UX434IQ Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-14-generic root=UUID=ac0e9628-3402-4892-84ab-a1dfb21be15a ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.10.0-14.15-generic 5.10.11 RelatedPackageVersions: linux-restricted-modules-5.10.0-14-generic N/A linux-backports-modules-5.10.0-14-generic N/A linux-firmware 1.190 Tags: groovy Uname: Linux 5.10.0-14-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/26/2020
[Kernel-packages] [Bug 1923114] [NEW] ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy
Public bug reported: Test cpu-hotplug from ubuntu_kernel_selftests failed with bionic:linux- azure-4.15 running on a Basic A2 with 2 cores (besides other instance types): selftests: cpu-on-off-test.sh pid 28041's current affinity mask: 3 pid 28041's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy offline_cpu_expect_success 1: unexpected fail http://10.246.72.46/4.15.0-1112.124~16.04.1-azure/xenial-linux-azure- azure- amd64-4.15.0-Basic_A2-ubuntu_kernel_selftests/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests .cpu-hotplug/debug/ubuntu_kernel_selftests.cpu-hotplug.DEBUG.html The problem happens at "autotest-client-tests/ubuntu_kernel_selftests /cpu-on-off-test.sh" when executing: echo 0 > $SYSFS/devices/system/cpu/cpu$1/online ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu Trusty) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu Xenial) Importance: Undecided Status: New ** Affects: linux-azure (Ubuntu Bionic) Importance: Undecided Status: New ** Affects: linux-azure-4.15 (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: 4.15 amd64 azure bionic kqa-blocker sru-20210315 trusty ubuntu-kernel-selftests xenial ** Also affects: linux-azure-4.15 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-azure-4.15 (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-azure-4.15 (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux-azure-4.15 (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: linux-azure (Ubuntu) Importance: Undecided Status: New ** Tags added: 4.15 amd64 azure bionic kqa-blocker sru-20210315 trusty ubuntu-kernel-selftests xenial -- 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/1923114 Title: ubuntu_kernel_selftests: ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-azure-4.15 package in Ubuntu: New Status in linux-azure source package in Trusty: New Status in linux-azure-4.15 source package in Trusty: New Status in linux-azure source package in Xenial: New Status in linux-azure-4.15 source package in Xenial: New Status in linux-azure source package in Bionic: New Status in linux-azure-4.15 source package in Bionic: New Bug description: Test cpu-hotplug from ubuntu_kernel_selftests failed with bionic :linux-azure-4.15 running on a Basic A2 with 2 cores (besides other instance types): selftests: cpu-on-off-test.sh pid 28041's current affinity mask: 3 pid 28041's new affinity mask: 1 CPU online/offline summary: present_cpus = 0-1 present_max = 1 Cpus in online state: 0-1 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 1 not ok 1..1 selftests: cpu-on-off-test.sh [FAIL] ./cpu-on-off-test.sh: line 94: echo: write error: Device or resource busy offline_cpu_expect_success 1: unexpected fail http://10.246.72.46/4.15.0-1112.124~16.04.1-azure/xenial-linux-azure- azure- amd64-4.15.0-Basic_A2-ubuntu_kernel_selftests/ubuntu_kernel_selftests/results/ubuntu_kernel_selftests .cpu-hotplug/debug/ubuntu_kernel_selftests.cpu-hotplug.DEBUG.html The problem happens at "autotest-client-tests/ubuntu_kernel_selftests /cpu-on-off-test.sh" when executing: echo 0 > $SYSFS/devices/system/cpu/cpu$1/online To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923114/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1919408] Re: [amdgpu] GUI freeze
Crashed again 2 times within 15 minutes. On Tue, Apr 6, 2021 at 1:25 AM Daniel van Vugt <1919...@bugs.launchpad.net> wrote: > It might help with debugging if you could stop 'sinfod' from flooding > the log. Either by reconfiguring it or by uninstalling it. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1919408 > > Title: > [amdgpu] GUI freeze > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > After copied (dd copy) old disk /home to bigger one then reboot xorg > start to freeze it seems kernel crash rather than only Xorg, because all > input devices (keyboard, mouse) turned off completely. only option is hard > reboot. > I upgrade distro from 20.04 to 20.10, the situation remain the same > after every login to desktop the system freeze completely and need it to do > hard reboot. > > ProblemType: Bug > DistroRelease: Ubuntu 20.10 > Package: xorg 1:7.7+19ubuntu15 > ProcVersionSignature: Ubuntu 5.8.0-45.51-lowlatency 5.8.18 > Uname: Linux 5.8.0-45-lowlatency x86_64 > NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair > .tmp.unity_support_test.0: > > ApportVersion: 2.20.11-0ubuntu50.5 > Architecture: amd64 > BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' > CasperMD5CheckResult: skip > CompizPlugins: > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > CompositorRunning: None > CurrentDesktop: MATE > Date: Wed Mar 17 01:11:19 2021 > DistUpgraded: 2021-03-15 02:52:49,427 INFO cache.commit() > DistroCodename: groovy > DistroVariant: ubuntu > ExtraDebuggingInterest: Yes > GconfCompiz: >/apps/compiz-1/general: > /apps/compiz-1/general/screen0: > /apps/compiz-1/general/screen0/options: >active_plugins = > [core,composite,opengl,compiztoolbox,decor,vpswitch,snap,mousepoll,resize,place,move,wall,grid,regex,imgpng,session,gnomecompat,animation,fade,staticswitcher,workarounds,scale,expo,ezoom,dbus] > GpuHangFrequency: Continuously > GpuHangReproducibility: Occurs more often under certain circumstances > GpuHangStarted: Within the last week or two > GraphicsCard: >Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX > 470/480/570/570X/580/580X/590] [1002:67df] (rev ef) (prog-if 00 [VGA > controller]) > Subsystem: XFX Pine Group Inc. Radeon RX 570 [1682:c570] > InstallationDate: Installed on 2018-05-05 (1046 days ago) > InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 > (20180426) > MachineType: To be filled by O.E.M. To be filled by O.E.M. > ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.8.0-45-lowlatency > root=UUID=17faa721-1006-4426-b460-57b94bfebefa ro threadirqs > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M > crashkernel=512M-:192M > SourcePackage: xorg > Symptom: display > Title: Xorg freeze > UpgradeStatus: Upgraded to groovy on 2021-03-15 (1 days ago) > dmi.bios.date: 04/10/2013 > dmi.bios.release: 4.6 > dmi.bios.vendor: American Megatrends Inc. > dmi.bios.version: 1708 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: M5A99FX PRO R2.0 > dmi.board.vendor: ASUSTeK COMPUTER INC. > dmi.board.version: Rev 1.xx > 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.:bvr1708:bd04/10/2013:br4.6:svnTobefilledbyO.E.M.:pnTobefilledbyO.E.M.:pvrTobefilledbyO.E.M.:rvnASUSTeKCOMPUTERINC.:rnM5A99FXPROR2.0:rvrRev1.xx: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: SKU > dmi.product.version: To be filled by O.E.M. > dmi.sys.vendor: To be filled by O.E.M. > version.compiz: compiz 1:0.9.14.1+20.10.20200813-0ubuntu1 > version.libdrm2: libdrm2 2.4.102-1ubuntu1 > version.libgl1-mesa-dri: libgl1-mesa-dri 20.2.6-0ubuntu0.20.10.1 > version.libgl1-mesa-glx: libgl1-mesa-glx 20.2.6-0ubuntu0.20.10.1 > version.xserver-xorg-core: xserver-xorg-core 2:1.20.9-2ubuntu1.2~20.04.1 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1ubuntu1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20200714-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1919408/+subscriptions > ** Attachment added: "Freeze-GUI-1_2-04-08-2021.tar.gz"
Re: [Kernel-packages] [Bug 1918427] Re: curtin: install flash-kernel in arm64 UEFI unexpected
On Fri, Mar 19, 2021 at 1:31 PM Ryan Harper <1918...@bugs.launchpad.net> wrote:
>
> * dann frazier <1918...@bugs.launchpad.net> [2021-03-19 12:16]:
> > On Fri, Mar 19, 2021 at 10:01 AM Ryan Harper <1918...@bugs.launchpad.net>
> > wrote:
> > >
> > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 16:30]:
> > > > On Thu, Mar 18, 2021 at 12:25 PM Ryan Harper
> > > > <1918...@bugs.launchpad.net> wrote:
> > > > >
> > > > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-18 12:11]:
> > > > > > On Thu, Mar 18, 2021 at 10:25 AM Ryan Harper
> > > > > > <1918...@bugs.launchpad.net> wrote:
> > > > > > >
> > > > > > > * dann frazier <1918...@bugs.launchpad.net> [2021-03-17 20:30]:
> > > > > > > > On Tue, Mar 16, 2021 at 10:05 AM Ryan Harper
> > > > > > > > <1918...@bugs.launchpad.net> wrote:
> > > > > > > > >
> > > > > > > > > Hi Dan,
> > > > > > > > >
> > > > > > > >
> > > > > > > > 1) flash-kernel could get installed post-divert. In that case,
> > > > > > > > flash-kernel's own postinst will cause it to run and then fail.
> > > > > > > > This
> > > > > > > > happens today if you start with a cloud image w/o flash-kernel
> > > > > > > > pre-baked because Ubuntu's kernel recommends flash-kernel,
> > > > > > > > causing it
> > > > > > > > to be installed along with the kernel. Official cloud images
> > > > > > > > happen to
> > > > > > >
> > > > > > > Hrm, so if we take a squashfs rootfs (with no flash-kernel
> > > > > > > present)
> > > > > > > chroot into it and install the linux-image-generic package
> > > > > > > pulling in
> > > > > > > flash-kernel this fails due to postinst of flash-kernel expecting
> > > > > > > initramfs to already be generated? This doesn't seem like a
> > > > > > > curtin bug.
> > > > > >
> > > > > > If done so in a chroot that exposes the kernel interfaces (/proc &
> > > > > > /sys) that claim to be hardware that requires the initramfs to be
> > > > > > post-processed, yes.
> > > > >
> > > > > Maybe I'm missing something but if I install linux-image-generic
> > > > > it populates /boot with vmlinuz-$version (and a few more things)
> > > > > and /lib/modules/$version and the kernels postinst will invoke
> > > > > update-initramfs. The /boot/initrd.img-$version is *generated* at
> > > > > that time during the kernel's postinstall
> > > > >
> > > > > Now, in the arm case IIUC, the kernel package has a dep on
> > > > > flash-kernel
> > > > > being present as it's "needed" to generate the initramfs ... so how
> > > > > can
> > > > > flash-kernel's postinst *fail* if it is the tool that's generating
> > > > > said
> > > > > initramfs file?
> > > >
> > > > What flash-kernel does is generate wrapped versions of *exisiting*
> > > > vmlinuz and initrd.img files. It doesn't generate those files, rather
> > > > post-processes them.
> > > > The kernel doesn't depend on flash-kernel, it just recommends it like
> > > > it does GRUB on x86.
> > >
> > > Yes, I get that but it still looks like a packaging bug if dpkg installs
> > > flash-kernel first and /boot is not populated with existing initrds; one
> > > could easily see this happen in a debootstrap.
> >
> > Given that a failure to produce a wrapped initrd could cause a system
> > to become unbootable, it does seem to me like a hard failure here is
> > warranted. But, perhaps we could provide a "s... it's ok, just
> > chill" mechanism. Maybe a FLASH_KERNEL_SKIP=1 environment variable?
>
> Agreed but with the condition that the *input* is present. If the
> initrd file has not yet been generated then another error from
> flash-kernel seems redundant, specifically in the case where if the
> kernel package is not yet installed (and maybe this is the reasonble
> check the post-inst can do) then it's *always* going to fail.
Sorry for the late reply.
Certainly it seems like flash-kernel should exit 0 if no kernel is
installed, you could be in a chroot/container/whatever. But I don't
know if it's safe to exit 0 if a kernel is installed but no initrd is
found. It could be that we're in the middle of an install w/ initrd
generation temporarily disabled. But it could also mean that a user
has installed a local unpackaged kernel and is trying to boot it
without an initrd (either intentionally, or they just forgot to
mkinitramfs). For some platforms, like xgene-uboot, flash-kernel knows
that the firmware boot script will error out if no initrd is present.
Should it not throw an error in that case?
It feels safer to do something explicit to prevent f-k from running
(diversion, envvar, etc) rather than relying on f-k to make
assumptions about its environment.
> Does flash-kernel hook into initramfs updates via the
> /etc/kernel/{pre,post}inst.d/flash-kernel ? like initramfs-tools does?
Yes it does.
> I suspect most of what flash-kernel does would be triggered via kernel
> postinst hooks.
True, kernel postinst hooks will also do the flashing, but I don't see
how it would help the case here.
> >
> > > Is the "liveness" of the
[Kernel-packages] [Bug 1923104] Re: Include Infiniband Peer Memory interface
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => dann frazier (dannf) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923104 Title: Include Infiniband Peer Memory interface Status in linux package in Ubuntu: In Progress Bug description: The peer_memory_client scheme allows a driver to register with the ib_umem system that it has the ability to understand user virtual address ranges that are not compatible with get_user_pages(). For instance VMAs created with io_remap_pfn_range(), or other driver special VMA. For ranges the interface understands it can provide a DMA mapped sg_table for use by the ib_umem, allowing user virtual ranges that cannot be supported by get_user_pages() to be used as umems for RDMA. This is designed to preserve the kABI, no functions or structures are changed, only new symbols are added: ib_register_peer_memory_client ib_unregister_peer_memory_client ib_umem_activate_invalidation_notifier ib_umem_get_peer And a bitfield in struct ib_umem uses more bits. This interface is compatible with the two out of tree GPU drivers: https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/blob/master/drivers/gpu/drm/amd/amdkfd/kfd_peerdirect.c https://github.com/Mellanox/nv_peer_memory/blob/master/nv_peer_mem.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923104] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1923104 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923104 Title: Include Infiniband Peer Memory interface Status in linux package in Ubuntu: Incomplete Bug description: The peer_memory_client scheme allows a driver to register with the ib_umem system that it has the ability to understand user virtual address ranges that are not compatible with get_user_pages(). For instance VMAs created with io_remap_pfn_range(), or other driver special VMA. For ranges the interface understands it can provide a DMA mapped sg_table for use by the ib_umem, allowing user virtual ranges that cannot be supported by get_user_pages() to be used as umems for RDMA. This is designed to preserve the kABI, no functions or structures are changed, only new symbols are added: ib_register_peer_memory_client ib_unregister_peer_memory_client ib_umem_activate_invalidation_notifier ib_umem_get_peer And a bitfield in struct ib_umem uses more bits. This interface is compatible with the two out of tree GPU drivers: https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/blob/master/drivers/gpu/drm/amd/amdkfd/kfd_peerdirect.c https://github.com/Mellanox/nv_peer_memory/blob/master/nv_peer_mem.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels
** Tags added: focal -- 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/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.
** Tags added: focal kvm -- 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/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: 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[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 ] ubuntu@selfprovisioned-phlin-b-5-4-net:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ echo $? 1 Probably a test case issue. This is not a regression as I can reproduce this on Bionic 5.4.0-1019-oracle as well ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-1019-oracle 5.4.0-1019.19~18.04.1 ProcVersionSignature: User Name 5.4.0-1019.19~18.04.1-oracle 5.4.44 Uname: Linux 5.4.0-1019-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jul 15 11:28:29 2020 SourcePackage: linux-signed-oracle-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923104] [NEW] Include Infiniband Peer Memory interface
Public bug reported: The peer_memory_client scheme allows a driver to register with the ib_umem system that it has the ability to understand user virtual address ranges that are not compatible with get_user_pages(). For instance VMAs created with io_remap_pfn_range(), or other driver special VMA. For ranges the interface understands it can provide a DMA mapped sg_table for use by the ib_umem, allowing user virtual ranges that cannot be supported by get_user_pages() to be used as umems for RDMA. This is designed to preserve the kABI, no functions or structures are changed, only new symbols are added: ib_register_peer_memory_client ib_unregister_peer_memory_client ib_umem_activate_invalidation_notifier ib_umem_get_peer And a bitfield in struct ib_umem uses more bits. This interface is compatible with the two out of tree GPU drivers: https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/blob/master/drivers/gpu/drm/amd/amdkfd/kfd_peerdirect.c https://github.com/Mellanox/nv_peer_memory/blob/master/nv_peer_mem.c ** 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/1923104 Title: Include Infiniband Peer Memory interface Status in linux package in Ubuntu: New Bug description: The peer_memory_client scheme allows a driver to register with the ib_umem system that it has the ability to understand user virtual address ranges that are not compatible with get_user_pages(). For instance VMAs created with io_remap_pfn_range(), or other driver special VMA. For ranges the interface understands it can provide a DMA mapped sg_table for use by the ib_umem, allowing user virtual ranges that cannot be supported by get_user_pages() to be used as umems for RDMA. This is designed to preserve the kABI, no functions or structures are changed, only new symbols are added: ib_register_peer_memory_client ib_unregister_peer_memory_client ib_umem_activate_invalidation_notifier ib_umem_get_peer And a bitfield in struct ib_umem uses more bits. This interface is compatible with the two out of tree GPU drivers: https://github.com/RadeonOpenCompute/ROCK-Kernel-Driver/blob/master/drivers/gpu/drm/amd/amdkfd/kfd_peerdirect.c https://github.com/Mellanox/nv_peer_memory/blob/master/nv_peer_mem.c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923104/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837348] Re: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels
Found on Focal/linux-kvm, cycle sru-20210315 ** Tags added: kvm sru-20210315 -- 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/1837348 Title: test_vxlan_under_vrf.sh in net from ubuntu_kernel_selftests failed with KVM kernels Status in ubuntu-kernel-tests: New Status in linux-kvm package in Ubuntu: New Status in linux-kvm source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: Issue found on a AMD64 KVM node with Disco KVM kernel. selftests: net: test_vxlan_under_vrf.sh Error: Unknown device type. Cannot remove namespace file "/var/run/netns/hv-2": No such file or directory Cannot remove namespace file "/var/run/netns/vm-1": No such file or directory Cannot remove namespace file "/var/run/netns/vm-2": No such file or directory not ok 1..24 selftests: net: test_vxlan_under_vrf.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1010-kvm 5.0.0-1010.11 ProcVersionSignature: User Name 5.0.0-1010.11-kvm 5.0.8 Uname: Linux 5.0.0-1010-kvm x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 Date: Mon Jul 22 05:04:42 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1837348/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type.
Found on Focal/linux-kvm, cycle sru-20210315 ** Tags added: sru-20210315 -- 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/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed with Operation not supported / Error: Unknown device type. Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Eoan: Won't Fix Status in linux-aws source package in Eoan: Won't Fix Status in linux-kvm source package in Eoan: Won't Fix Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Found on Focal/linux-kvm, cycle sru-20210315 ** Tags added: kvm sru-20210315 -- 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/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: In Progress Status in linux source package in Focal: In Progress Status in linux source package in Groovy: In Progress Status in linux source package in Hirsute: In Progress Bug description: 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[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 ] ubuntu@selfprovisioned-phlin-b-5-4-net:~/autotest/client/tmp/ubuntu_kernel_selftests/src/linux/tools/testing/selftests/net$ echo $? 1 Probably a test case issue. This is not a regression as I can reproduce this on Bionic 5.4.0-1019-oracle as well ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.4.0-1019-oracle 5.4.0-1019.19~18.04.1 ProcVersionSignature: User Name 5.4.0-1019.19~18.04.1-oracle 5.4.44 Uname: Linux 5.4.0-1019-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Jul 15 11:28:29 2020 SourcePackage: linux-signed-oracle-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887661/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1893504] Re: System froze
Sorry for the late response, I RMA the motherboard because I thought it could be the problem, it wasn't. I added the kernel parameters to the grub boot file, but it did not solve the problem. Do you have any other idea? -- 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/1893504 Title: System froze Status in linux package in Ubuntu: Expired Bug description: After of about 8 to 12 hours of use the system simply freezes. No mouse or keyboard response. Even video playing on the page stops responding. There is nothing special to be done to cause the problem, sometimes the system freezes at idle sometimes, sometimes it freezes while I'm using it. Hardware: CPU: Ryzen Threadripper 3970x Memory: 128GB Corsair Vengeance LPX Motherboard: Asus Zenith Extreme 2 NVMe: SSD Samsung 970 EVO Plus 1TB, M.2 NVMe System: Ubuntu 5.4.0-42.46-generic 5.4.44 lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: pcarrara 2332 F pulseaudio /dev/snd/controlC1: pcarrara 2332 F pulseaudio /dev/snd/controlC0: pcarrara 2332 F pulseaudio /dev/snd/pcmC0D7p: pcarrara 2332 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Aug 29 02:07:36 2020 InstallationDate: Installed on 2020-08-27 (1 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) MachineType: System manufacturer System Product Name ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=9e72229e-3b67-433e-94f7-4cb8f323faeb ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/05/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1101 dmi.board.asset.tag: Default string dmi.board.name: ROG ZENITH II EXTREME dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1101:bd06/05/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnROGZENITHIIEXTREME:rvrRev1.xx:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1893504/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923084] [NEW] duplicate consoles on riscv64
Public bug reported: When booting on SiFive boards, there are two gettys launched on the same console. There is sifive serial console which is the active/only physical console. But also, there is serial console exposed over legacy opensbi extension; which in linux kernel is implemented as hvc0 console, which systemd starts getty for. The issue is that the both consoles are actually the same one. Thus some other distros chose to hard-code disable hvc0 console on riscv64. But given that the legacy sbi serial console extension will eventually go away, it makes sense to disable that in the kernel out right. By setting: +# CONFIG_RISCV_SBI_V01 is not set +# CONFIG_SERIAL_EARLYCON_RISCV_SBI is not set +# CONFIG_HVC_RISCV_SBI is not set This way sifive0 console will be discovered and used automatically; ditto earlyprintk without needing to specify sbi or explicitely set sifive0 console. This will also improve UX experience with just a single getty on the serial connection. ** Affects: linux-riscv (Ubuntu) Importance: Critical Status: Confirmed ** Changed in: linux-riscv (Ubuntu) Milestone: None => ubuntu-21.04 ** Changed in: linux-riscv (Ubuntu) Importance: Undecided => Critical ** Changed in: linux-riscv (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1923084 Title: duplicate consoles on riscv64 Status in linux-riscv package in Ubuntu: Confirmed Bug description: When booting on SiFive boards, there are two gettys launched on the same console. There is sifive serial console which is the active/only physical console. But also, there is serial console exposed over legacy opensbi extension; which in linux kernel is implemented as hvc0 console, which systemd starts getty for. The issue is that the both consoles are actually the same one. Thus some other distros chose to hard-code disable hvc0 console on riscv64. But given that the legacy sbi serial console extension will eventually go away, it makes sense to disable that in the kernel out right. By setting: +# CONFIG_RISCV_SBI_V01 is not set +# CONFIG_SERIAL_EARLYCON_RISCV_SBI is not set +# CONFIG_HVC_RISCV_SBI is not set This way sifive0 console will be discovered and used automatically; ditto earlyprintk without needing to specify sbi or explicitely set sifive0 console. This will also improve UX experience with just a single getty on the serial connection. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1923084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878389] Re: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13'
Found on Focal/linux-kvm, cycle sru-20210315 ** Tags added: kvm -- 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/1878389 Title: tpci from kernel_misc in ubuntu_ltp failed with Test-case '13' Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: With bug 1868707 fixed, the tpci test can finish now, and it's reporting another issue here: test_pci 489 TFAIL : tpci.c:73: PCI bus 01 slot 01 : Test-case '13' Please find attachment for dmesg log and the full test log. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: User Name 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 13 10:08 seq crw-rw 1 root audio 116, 33 May 13 10:08 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Wed May 13 10:19:01 2020 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: HP ProLiant DL360 Gen9 PciMultimedia: ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=6422cfdd-2a69-4c0b-9784-6809a77ab980 ro RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/25/2017 dmi.bios.vendor: HP dmi.bios.version: P89 dmi.board.name: ProLiant DL360 Gen9 dmi.board.vendor: HP dmi.chassis.type: 23 dmi.chassis.vendor: HP dmi.modalias: dmi:bvnHP:bvrP89:bd04/25/2017:svnHP:pnProLiantDL360Gen9:pvr:rvnHP:rnProLiantDL360Gen9:rvr:cvnHP:ct23:cvr: dmi.product.family: ProLiant dmi.product.name: ProLiant DL360 Gen9 dmi.product.sku: 780020-S01 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1878389/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
Found on Focal/linux-kvm, cycle sru-20210315
** Tags added: kvm
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1829995
Title:
getaddrinfo_01 from ipv6_lib test suite in LTP failed
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux-aws package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-aws source package in Bionic:
New
Status in linux source package in Eoan:
New
Status in linux-aws source package in Eoan:
New
Bug description:
startup='Wed May 22 08:02:52 2019'
getaddrinfo_011 TPASS : getaddrinfo IPv4 basic lookup
getaddrinfo_012 TFAIL : getaddrinfo_01.c:140: getaddrinfo IPv4
canonical name ("curly.maas") doesn't match hostname ("curly")
getaddrinfo_013 TFAIL : getaddrinfo_01.c:578: getaddrinfo IPv6 basic
lookup ("curly") returns -5 ("No address associated with hostname")
tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 02:57 seq
crw-rw 1 root audio 116, 33 May 22 02:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Wed May 22 08:04:30 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
linux-restricted-modules-4.15.0-50-generic N/A
linux-backports-modules-4.15.0-50-generic N/A
linux-firmware 1.173.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853610] Re: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails
Found on Focal/linux-kvm, cycle sru-20210315 ** Tags added: kvm -- 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/1853610 Title: mkfs01_ext3_sh / mkfs01_ext4_sh / nm01_sh from commands test in ubuntu_ltp fails Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Bug description: Series: E Problem: commands test in ubuntu_ltp fails on E, test cases listed below: * mkfs01_ext3_sh * mkfs01_ext4_sh * nm01_sh startup='Fri Dec 6 02:30:45 2019' mkfs01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2' mkfs01 1 TPASS: 'mkfs -t ext3 /dev/loop2 ' passed. mkfs01 2 TFAIL: 'mkfs -t ext3 /dev/loop2 16000' failed, not expected. mkfs01 3 TPASS: 'mkfs -t ext3 -c /dev/loop2 ' passed. mkfs01 4 TPASS: 'mkfs -V ' passed. mkfs01 5 TPASS: 'mkfs -h ' passed. mkfs01 6 TINFO: AppArmor enabled, this may affect test results mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) mkfs01 6 TINFO: loaded AppArmor profiles: none Summary: passed 4 failed 1 skipped 0 warnings 0 tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 cs=12 tag=mkfs01_ext3_sh stime=1575599445 dur=2 exit=exited stat=1 core=no cu=8 cs=12 startup='Fri Dec 6 02:30:52 2019' mkfs01 1 TINFO: timeout per run is 0h 5m 0s tst_device.c:238: INFO: Using test device LTP_DEV='/dev/loop2' mkfs01 1 TPASS: 'mkfs -t ext4 /dev/loop2 ' passed. mkfs01 2 TFAIL: 'mkfs -t ext4 /dev/loop2 16000' failed, not expected. mkfs01 3 TPASS: 'mkfs -t ext4 -c /dev/loop2 ' passed. mkfs01 4 TPASS: 'mkfs -V ' passed. mkfs01 5 TPASS: 'mkfs -h ' passed. mkfs01 6 TINFO: AppArmor enabled, this may affect test results mkfs01 6 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) mkfs01 6 TINFO: loaded AppArmor profiles: none Summary: passed 4 failed 1 skipped 0 warnings 0 tag=mkfs01_ext4_sh stime=1575599452 dur=2 exit=exited stat=1 core=no cu=4 cs=1 startup='Fri Dec 6 02:28:44 2019' nm01 1 TINFO: timeout per run is 0h 5m 0s nm01 1 TPASS: nm -f posix -A lib.a > nm.out passed as expected nm01 1 TPASS: Got correct listing nm01 1 TPASS: nm -f posix -A dir/lib.a > nm.out passed as expected nm01 1 TPASS: Got correct listing nm01 2 TPASS: nm -f posix -g /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 2 TPASS: Got only external symbols with -g nm01 3 TPASS: nm -f posix -t o /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 3 TPASS: Got an octal symbol values with -f nm01 4 TPASS: nm -f sysv /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 4 TPASS: Got SysV format with -f sysv nm01 5 TPASS: nm -f bsd /opt/ltp/testcases/data/nm01/f1 > nm_bsd.out passed as expected nm01 5 TPASS: nm -f posix /opt/ltp/testcases/data/nm01/f1 > nm_posix.out passed as expected nm01 5 TFAIL: Got wrong format with -f bsd 3dc8 d _DYNAMIC 3fb8 d _GLOBAL_OFFSET_TABLE_ 2000 R _IO_stdin_used w _ITM_deregisterTMCloneTable w _ITM_registerTMCloneTable 2154 r __FRAME_END__ 2010 r __GNU_EH_FRAME_HDR 4010 D __TMC_END__ 4010 B __bss_start w __cxa_finalize@@GLIBC_2.2.5 4000 D __data_start 1120 t __do_global_dtors_aux 3dc0 d __do_global_dtors_aux_fini_array_entry 4008 D __dso_handle 3db8 d __frame_dummy_init_array_entry w __gmon_start__ 3dc0 d __init_array_end 3db8 d __init_array_start 11e0 T __libc_csu_fini 1170 T __libc_csu_init U __libc_start_main@@GLIBC_2.2.5 4010 D _edata 4018 B _end 11e8 T _fini 1000 t _init 1080 T _start 4010 b completed.8055 4000 W data_start 10b0 t deregister_tm_clones 1160 t frame_dummy 1060 T main U puts@@GLIBC_2.2.5 10e0 t register_tm_clones nm01 6 TPASS: nm -f sysv -u /opt/ltp/testcases/data/nm01/f1 > nm.out passed as expected nm01 6 TPASS: Got undefined symbols with -u nm01 7 TPASS: nm -s /opt/ltp/testcases/data/nm01/lib.a > nm.out passed as expected nm01 7 TPASS: Got index with -s nm01 8 TINFO: AppArmor enabled, this may affect test results nm01 8 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) nm01 8 TINFO: loaded AppArmor profiles: none Summary: passed 16 failed 1 skipped 0 warnings 0 tag=nm01_sh stime=1575599324 dur=0 exit=exited stat=1 core=no cu=3 cs=0 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1829984] Re: memcg_usage_in_bytes from controllers test suite in LTP failed
Found on Focal/linux-kvm, cycle sru-20210315 ** Tags added: kvm -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1829984 Title: memcg_usage_in_bytes from controllers test suite in LTP failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux source package in Xenial: New Status in linux-aws source package in Xenial: New Status in linux source package in Bionic: Confirmed Status in linux-aws source package in Bionic: New Status in linux source package in Cosmic: Confirmed Status in linux-aws source package in Cosmic: New Bug description: startup='Wed May 22 05:59:09 2019' memcg_usage_in_bytes_test 1 TINFO: Starting test 1 sh: echo: I/O error memcg_usage_in_bytes_test 1 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 1 TINFO: Running memcg_process --mmap-anon -s 4194304 memcg_usage_in_bytes_test 1 TINFO: Warming up pid: 31689 memcg_usage_in_bytes_test 1 TINFO: Process is still here after warm up: 31689 memcg_usage_in_bytes_test 1 TFAIL: memory.usage_in_bytes is 4202496, 4194304 expected memcg_usage_in_bytes_test 2 TINFO: Starting test 2 sh: echo: I/O error memcg_usage_in_bytes_test 2 TINFO: set /dev/memcg/memory.use_hierarchy to 0 failed memcg_usage_in_bytes_test 2 TCONF: mem+swap is not enabled tag=memcg_usage_in_bytes stime=1558504749 dur=1 exit=exited stat=33 core=no cu=5 cs=3 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-50-generic 4.15.0-50.54 ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18 Uname: Linux 4.15.0-50-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 May 22 02:57 seq crw-rw 1 root audio 116, 33 May 22 02:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [14538.862950] cfg80211: Loading compiled-in X.509 certificates for regulatory database [14538.874559] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7' Date: Wed May 22 07:17:43 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro RelatedPackageVersions: linux-restricted-modules-4.15.0-50-generic N/A linux-backports-modules-4.15.0-50-generic N/A linux-firmware 1.173.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829984/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905157] Re: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
zfs mount on / is failing because / is not empty: ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sun 2020-11-22 06:41:54 CET; 3ms ago Docs: man:zfs(8) Process: 4123780 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 4123780 (code=exited, status=1/FAILURE) nov 22 06:41:54 Home systemd[1]: Starting Mount ZFS filesystems... nov 22 06:41:54 Home zfs[4123780]: cannot mount '/': directory is not empty nov 22 06:41:54 Home systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE nov 22 06:41:54 Home systemd[1]: zfs-mount.service: Failed with result 'exit-code'. nov 22 06:41:54 Home systemd[1]: Failed to start Mount ZFS filesystems. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 This suggests a ZFS on / was installed. Do you mind informing me how the install was performed? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1905157 Title: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 Status in zfs-linux package in Ubuntu: Incomplete Bug description: When I try to update zfsutils-linux, the upgrade process tries to mount all zfs file systems but since my root / is on zfs it fails with: nov 22 08:21:28 Home systemd[1]: Starting Mount ZFS filesystems... nov 22 08:21:28 Home zfs[286979]: cannot mount '/': directory is not empty nov 22 08:21:28 Home systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE nov 22 08:21:28 Home systemd[1]: zfs-mount.service: Failed with result 'exit-code'. nov 22 08:21:28 Home systemd[1]: Failed to start Mount ZFS filesystems. As a consequence, the upgrade process fails. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: zfsutils-linux 0.8.3-1ubuntu12.4 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.12 AptOrdering: linux-headers-5.4.0-52-generic:amd64: Remove linux-headers-5.4.0-52:amd64: Remove NULL: ConfigurePending Architecture: amd64 CasperMD5CheckResult: skip Date: Sun Nov 22 06:41:54 2020 ErrorMessage: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 InstallationDate: Installed on 2020-07-08 (136 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4 RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2ubuntu0.1 SourcePackage: zfs-linux Title: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status 1 UpgradeStatus: No upgrade log present (probably fresh install) mtime.conffile..etc.default.zfs: 2020-08-05T10:29:12.101838 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905157/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1905157] Re: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade: installed zfsutils-linux package post-installation script subprocess returned error exit status
I wonder if this has to do with the fact that the defaults in
/etc/default/zfs have been modified:
# Wait for this many seconds in the initrd pre_mountroot?
# This delays startup and should be '0' on most systems.
# Only applicable for Debian GNU/Linux {dkms,initramfs}.
ZFS_INITRD_PRE_MOUNTROOT_SLEEP='0'
# Wait for this many seconds in the initrd mountroot?
# This delays startup and should be '0' on most systems. This might help on
# systems which have their ZFS root on a USB disk that takes just a little
# longer to be available
# Only applicable for Debian GNU/Linux {dkms,initramfs}.
ZFS_INITRD_POST_MODPROBE_SLEEP='0'
# List of additional datasets to mount after the root dataset is mounted?
#
# The init script will use the mountpoint specified in the 'mountpoint'
# property value in the dataset to determine where it should be mounted.
#
# This is a space separated list, and will be mounted in the order specified,
# so if one filesystem depends on a previous mountpoint, make sure to put
# them in the right order.
#
# It is not necessary to add filesystems below the root fs here. It is
# taken care of by the initrd script automatically. These are only for
# additional filesystems needed. Such as /opt, /usr/local which is not
# located under the root fs.
# Example: If root FS is 'rpool/ROOT/rootfs', this would make sense.
#ZFS_INITRD_ADDITIONAL_DATASETS="rpool/ROOT/usr rpool/ROOT/var"
ZFS_INITRD_ADDITIONAL_DATASETS="x data x/tmp data/tmp x/livebackup"
** Changed in: zfs-linux (Ubuntu)
Status: New => Incomplete
** Changed in: zfs-linux (Ubuntu)
Importance: Undecided => Low
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to zfs-linux in Ubuntu.
https://bugs.launchpad.net/bugs/1905157
Title:
package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade:
installed zfsutils-linux package post-installation script subprocess
returned error exit status 1
Status in zfs-linux package in Ubuntu:
Incomplete
Bug description:
When I try to update zfsutils-linux, the upgrade process tries to mount all
zfs file systems but since my root / is on zfs it fails with:
nov 22 08:21:28 Home systemd[1]: Starting Mount ZFS filesystems...
nov 22 08:21:28 Home zfs[286979]: cannot mount '/': directory is not empty
nov 22 08:21:28 Home systemd[1]: zfs-mount.service: Main process exited,
code=exited, status=1/FAILURE
nov 22 08:21:28 Home systemd[1]: zfs-mount.service: Failed with result
'exit-code'.
nov 22 08:21:28 Home systemd[1]: Failed to start Mount ZFS filesystems.
As a consequence, the upgrade process fails.
ProblemType: Package
DistroRelease: Ubuntu 20.04
Package: zfsutils-linux 0.8.3-1ubuntu12.4
ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44
Uname: Linux 5.4.0-40-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset
nvidia
ApportVersion: 2.20.11-0ubuntu27.12
AptOrdering:
linux-headers-5.4.0-52-generic:amd64: Remove
linux-headers-5.4.0-52:amd64: Remove
NULL: ConfigurePending
Architecture: amd64
CasperMD5CheckResult: skip
Date: Sun Nov 22 06:41:54 2020
ErrorMessage: installed zfsutils-linux package post-installation script
subprocess returned error exit status 1
InstallationDate: Installed on 2020-07-08 (136 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Python3Details: /usr/bin/python3.8, Python 3.8.5, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: /usr/bin/python2.7, Python 2.7.18, python-is-python2, 2.7.17-4
RelatedPackageVersions:
dpkg 1.19.7ubuntu3
apt 2.0.2ubuntu0.1
SourcePackage: zfs-linux
Title: package zfsutils-linux 0.8.3-1ubuntu12.4 failed to install/upgrade:
installed zfsutils-linux package post-installation script subprocess returned
error exit status 1
UpgradeStatus: No upgrade log present (probably fresh install)
mtime.conffile..etc.default.zfs: 2020-08-05T10:29:12.101838
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1905157/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923069] [NEW] Hirsute update: v5.11.12 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.11.12 upstream stable release from git://git.kernel.org/ Linux 5.11.12 Revert "net: bonding: fix error return code of bond_neigh_init()" Revert "kernel: freezer should treat PF_IO_WORKER like PF_KTHREAD for freezing" io_uring: do ctx sqd ejection in a clear context riscv: evaluate put_user() arg before enabling user access drivers: video: fbcon: fix NULL dereference in fbcon_cursor() driver core: clear deferred probe reason on probe retry staging: rtl8192e: Change state information from u16 to u8 staging: rtl8192e: Fix incorrect source in memcpy() soc: qcom-geni-se: Cleanup the code to remove proxy votes usb: dwc3: gadget: Clear DEP flags after stop transfers in ep disable usb: dwc3: qcom: skip interconnect init for ACPI probe usb: dwc2: Prevent core suspend when port connection flag is 0 usb: dwc2: Fix HPRT0.PrtSusp bit setting for HiKey 960 board. usb: gadget: udc: amd5536udc_pci fix null-ptr-dereference USB: cdc-acm: fix use-after-free after probe failure USB: cdc-acm: fix double free on probe failure USB: cdc-acm: downgrade message to debug USB: cdc-acm: untangle a circular dependency between callback and softint cdc-acm: fix BREAK rx code path adding necessary calls usb: xhci-mtk: fix broken streams issue on 0.96 xHCI usb: musb: Fix suspend with devices connected for a64 USB: quirks: ignore remote wake-up on Fibocom L850-GL LTE modem usbip: vhci_hcd fix shift out-of-bounds in vhci_hub_control() firewire: nosy: Fix a use-after-free bug in nosy_ioctl() powerpc/mm/book3s64: Use the correct storage key value when calling H_PROTECT video: hyperv_fb: Fix a double free in hvfb_probe usb: dwc3: pci: Enable dis_uX_susphy_quirk for Intel Merrifield powerpc/pseries/mobility: handle premature return from H_JOIN powerpc/pseries/mobility: use struct for shared state firmware: stratix10-svc: reset COMMAND_RECONFIG_FLAG_PARTIAL to 0 extcon: Fix error handling in extcon_dev_register extcon: Add stubs for extcon_register_notifier_all() functions pinctrl: qcom: fix unintentional string concatenation pinctrl: qcom: lpass lpi: use default pullup/strength values pinctrl: qcom: sc7280: Fix SDC1_RCLK configurations pinctrl: qcom: sc7280: Fix SDC_QDSD_PINGROUP and UFS_RESET offsets pinctrl: rockchip: fix restore error in resume pinctrl: microchip-sgpio: Fix wrong register offset for IRQ trigger vfio/nvlink: Add missing SPAPR_TCE_IOMMU depends drm/tegra: sor: Grab runtime PM reference across reset drm/tegra: dc: Restore coupling of display controllers drm/imx: fix memory leak when fails to init reiserfs: update reiserfs_xattrs_initialized() condition drm/amdgpu: check alignment on CPU page for bo map drm/amdgpu: Set a suitable dev_info.gart_page_size drm/amdgpu: fix offset calculation in amdgpu_vm_bo_clear_mappings() drm/amdgpu/vangogh: don't check for dpm in is_dpm_running when in suspend drm/amd/pm: no need to force MCLK to highest when no display connected drm/amdkfd: dqm fence memory corruption mm: fix race by making init_zero_pfn() early_initcall drm/ttm: make ttm_bo_unpin more defensive s390/vdso: fix tod_steering_delta type s390/vdso: copy tod_steering_delta value to vdso_data page tracing: Fix stack trace event size PM: runtime: Fix ordering in pm_runtime_get_suppliers() PM: runtime: Fix race getting/putting suppliers at probe KVM: SVM: ensure that EFER.SVME is set when running nested guest or on nested vmexit KVM: SVM: load control fields from VMCB12 before checking them xtensa: move coprocessor_flush to the .text section xtensa: fix uaccess-related livelock in do_page_fault ALSA: hda/realtek: fix mute/micmute LEDs for HP 640 G8 ALSA: hda/realtek: call alc_update_headset_mode() in hp_automute_hook ALSA: hda/realtek: fix a determine_headset_type issue for a Dell AIO ALSA: hda: Add missing sanity checks in PM prepare/complete callbacks ALSA: hda: Re-add dropped snd_poewr_change_state() calls ALSA: usb-audio: Apply sample rate quirk to Logitech Connect ACPI: scan: Fix _STA getting called on devices with unmet dependencies ACPI: processor: Fix CPU0 wakeup in acpi_idle_play_dead() ACPI: tables: x86: Reserve memory occupied by ACPI tables bpf: Remove MTU check in __bpf_skb_max_len net: 9p: advance iov on empty read net: wan/lmc: unregister device when no matching device is found net: ipa: fix register write command validation net: ipa: use a separate pointer for adjusted GSI memory net: ipa: remove two unused register definitions appletalk: Fix skb allocation size in loopback case net: ethernet: aquantia: Handle error cleanup
[Kernel-packages] [Bug 1915175] Re: wifi network stops working and shows a green wifi icon
** Description changed: I recently started using ubuntu 20.04, I connected it to my 2.4ghz Wi-Fi, at first the wifi worked fine, but suddenly the wifi stopped connecting, and after a few seconds it said "unable to activate network". I checked the "additional drivers tab" and it showed my wifi adapter, but it said "this device is using an alternate driver". right now I'm using my 5ghz Wi-Fi network, but sometimes it happens that it stops working, usually after suspend. UPDATE #1: Apparently it's working now, I suppose it's from an update. Anyways I guess it's fixed. UPDATE #2: it's broken again UPDATE #3: after checking the error a long time I've realized that this error happens when I leave it suspended it for a long time, it is fixed by doing about 3-4 restarts. I'm going to try to use a code that restarts the network-service after suspend, I'll see if it works. UPDATE #4 (probably final update): the error can be fixed temporarily by turning off and then on the router,i'm going to contact my network provider to see if the error can be fixed by configuring the router. + + UPDATE #5: after moving to Groovy the issue still persists, I really + hope this can be fixed, I don't want to have to move to another distro ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: network-manager 1.22.10-1ubuntu2.2 ProcVersionSignature: Ubuntu 5.8.0-41.46~20.04.1-generic 5.8.18 Uname: Linux 5.8.0-41-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Feb 9 12:09:28 2021 InstallationDate: Installed on 2021-02-08 (0 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) IpRoute: default via 192.168.1.254 dev wlp1s0 proto dhcp metric 600 169.254.0.0/16 dev wlp1s0 scope link metric 1000 192.168.1.0/24 dev wlp1s0 proto kernel scope link src 192.168.1.8 metric 600 SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: [connection] wifi.powersave = 2 mtime.conffile..etc.NetworkManager.conf.d.default-wifi-powersave-on.conf: 2021-02-08T22:50:26.196692 nmcli-dev: DEVICE TYPE STATE IP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTION CON-UUID CON-PATH wlp1s0 wifi connected full limited /org/freedesktop/NetworkManager/Devices/2 Betancur 5G cda009c8-c845-4366-8436-8e9c44da2cbf /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged unknown unknown /org/freedesktop/NetworkManager/Devices/1 -- -- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.22.10 connected started full enabled enabled enabled enabled enabled --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gustavo1035 F pulseaudio /dev/snd/controlC0: gustavo1035 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-08 (6 days ago) InstallationMedia: Ubuntu 20.04.2 LTS "Focal Fossa" - Release amd64 (20210204) MachineType: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X509DA_M509DA Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-43-generic root=UUID=ded079f2-3f25-4b66-9496-ffb73191187f ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-43.49~20.04.1-generic 5.8.18 RelatedPackageVersions: linux-restricted-modules-5.8.0-43-generic N/A linux-backports-modules-5.8.0-43-generic N/A linux-firmware1.187.9 Tags: focal Uname: Linux 5.8.0-43-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/11/2019 dmi.bios.release: 5.14 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X509DA.306 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X509DA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX509DA.306:bd10/11/2019:br5.14:svnASUSTeKCOMPUTERINC.:pnVivoBook_ASUSLaptopX509DA_M509DA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX509DA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: VivoBook dmi.product.name: VivoBook_ASUSLaptop
[Kernel-packages] [Bug 1810183] Re: numpad on touchpad doesn't work in ASUS Zenbook 14
Works properly on my new VivoBook_ASUSLaptop X435EA_S435EA (with % and = symbols). Maybe instead of "QWERTY" you could write "QWERTY / QWERTZ", because it makes no difference for the % and works on my German keyboard as well without any issues. I was a bit surprised for a short time because it was not clear to me at first what effects the query for the keyboard layout would have. -- 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/1810183 Title: numpad on touchpad doesn't work in ASUS Zenbook 14 Status in Linux: New Status in linux package in Ubuntu: Confirmed Bug description: I have Asus Zenbook 14 UX433FA which I have installed Ubuntu 18.10 alongside windows 10. The numeric keypads are within the touchpad and are supposed to be turned on by a button on the touchpad. This works well in Windows but doesn't work in Ubuntu. I have tried to search for any related problems/solutions online but I haven't been able to. I will appreciate any suggestion or help. Thanks, --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.19.11-041911-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.10 InstallationDate: Installed on 2018-12-30 (4 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) Package: linux (not installed) Tags: cosmic Uname: Linux 4.18.10-041810-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1810183/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915063] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1915063 Title: Windows 10 wil not install using qemu-system-x86_64 Status in QEMU: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.10 package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Steps to reproduce install virt-manager and ovmf if nopt already there copy windows and virtio iso files to /var/lib/libvirt/images Use virt-manager from local machine to create your VMs with the disk, CPUs and memory required Select customize configuration then select OVMF(UEFI) instead of seabios set first CDROM to the windows installation iso (enable in boot options) add a second CDROM and load with the virtio iso change spice display to VNC Always get a security error from windows and it fails to launch the installer (works on RHEL and Fedora) I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of no help --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-20 (19 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201030-14:39 MachineType: LENOVO 30E102Z NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1042-oem N/A linux-backports-modules-5.6.0-1042-oem N/A linux-firmware 1.187.8 RfKill: Tags: focal Uname: Linux 5.6.0-1042-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2020 dmi.bios.vendor: LENOVO dmi.bios.version: S07KT08A dmi.board.name: 1046 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: INVALID dmi.product.name: 30E102Z dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620 dmi.product.version: ThinkStation P620 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1915063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861554] Re: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54
Hi, I have the same problem on ATI mobility Radeon HD 3650 (RV635) installed on laptop Compal FL90. Card worked corretly on old Linux releases, but recently all different distributions I try have corrupted screen image. Problem exist only on internal laptop LCD. External LCD connected to VGA port works without problems. Last kernel which works for me is 4.15.0-54-generic. Starting from 4.15.0-55-generic I have corrupted screen. Please see some more details here: https://forums.linuxmint.com/viewtopic.php?f=59=346544=1999384 Is it possible to have this solved on newer kernel releases ? BR ** Attachment added: "configuration settings log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+attachment/5485635/+files/logs.zip -- 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/1861554 Title: Radeon mobility HD3450 (RV620) heavy screen flickering after trying to upgrade kernel 4.15.0-54 Status in linux package in Ubuntu: Confirmed Bug description: laptop Asus x50sl with graphic card AMD rv620 / Mobility Radeon HD3450. Distro: Linux Mint 19.2 Tina base: Ubuntu 18.04 bionic. This happen trying any distro. I tried Ubuntu, Manjaro, Debian, Deepin, MX and so on. I'm stuck with Kernel 4.15.0-54 and 5.0.0-20 (and the contemporary 5.3 kernel). I cannot upgrade to newer kernels. Seems that the fixes for bug #1791312 broke my kind of card. here is a video: https://youtu.be/9Rez7s0V6iA here is another user with same problem: https://forums.linuxmint.com/viewtopic.php?p=1702005#p1702005 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861554/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
** Changed in: linux Status: Unknown => Confirmed ** Changed in: linux Importance: Unknown => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Confirmed Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1920916] Re: cold boot panics on unmatched board, soft reboot is fine
There should be a kernel available with this fix on Monday. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1920916 Title: cold boot panics on unmatched board, soft reboot is fine Status in linux-riscv package in Ubuntu: In Progress Bug description: [ 16.622852] Kernel panic - not syncing: L2CACHE: DirFail @ 0x.0001CB00 [ 16.629408] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.11.0-1004-generic #4-Ubuntu [ 16.637136] Call Trace: [ 16.639655] [] walk_stackframe+0x0/0xcc [ 16.645131] SMP: stopping secondary CPUs [ 16.649144] ---[ end Kernel panic - not syncing: L2CACHE: DirFail @ 0x.0001CB00 ]--- On cold boot, I am observing L2CACHE DirFail panic, then after soft reset it boots fine. See full attached screenlog.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-riscv/+bug/1920916/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1915063] Re: Windows 10 wil not install using qemu-system-x86_64
David used "5.6.0-1042.46-oem", the closest I had was "5.6.0-1052-oem" so I tried that one. With that my win10 install immediately crashed into the reported issue. So to summarize: 1. I can reproduce it 2. Chances are high that it is fixed by kernel commit 841c2be0 "kvm: x86: replace kvm_spec_ctrl_test_value with runtime test on the host" 3. there are some qemu changes which might be related, but we need Babu to reply about if/how those are related I need to get myself updated on Ubuntu oem kernels. If there is a 5.6 series that is supposed to work on that, then this patch needs to be backported. But if OTOH it is a valid upgrade path that you'll get the 5.10.0-1020-oem that I had or later as part of your 20.04 OEM then that "is the fix" for you @David. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-5.10 (Ubuntu) Importance: Undecided Status: New ** Changed in: linux-oem-5.10 (Ubuntu) Status: New => Fix Released ** Changed in: linux-oem-5.6 (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/1915063 Title: Windows 10 wil not install using qemu-system-x86_64 Status in QEMU: New Status in linux package in Ubuntu: New Status in linux-oem-5.10 package in Ubuntu: Fix Released Status in linux-oem-5.6 package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Confirmed Bug description: Steps to reproduce install virt-manager and ovmf if nopt already there copy windows and virtio iso files to /var/lib/libvirt/images Use virt-manager from local machine to create your VMs with the disk, CPUs and memory required Select customize configuration then select OVMF(UEFI) instead of seabios set first CDROM to the windows installation iso (enable in boot options) add a second CDROM and load with the virtio iso change spice display to VNC Always get a security error from windows and it fails to launch the installer (works on RHEL and Fedora) I tried updating the qemu version from Focals 4.2 to Groovy 5.0 which was of no help --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-sutton-focal-amd64-20201030-422+pc-sutton-bachman-focal-amd64+X00 DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-01-20 (19 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20201030-14:39 MachineType: LENOVO 30E102Z NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.6.0-1042-oem root=UUID=389cd165-fc52-4814-b837-a1090b9c2387 ro locale=en_US quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.6.0-1042.46-oem 5.6.19 RelatedPackageVersions: linux-restricted-modules-5.6.0-1042-oem N/A linux-backports-modules-5.6.0-1042-oem N/A linux-firmware 1.187.8 RfKill: Tags: focal Uname: Linux 5.6.0-1042-oem x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip docker kvm libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/29/2020 dmi.bios.vendor: LENOVO dmi.bios.version: S07KT08A dmi.board.name: 1046 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.type: 3 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrS07KT08A:bd07/29/2020:svnLENOVO:pn30E102Z:pvrThinkStationP620:rvnLENOVO:rn1046:rvrNotDefined:cvnLENOVO:ct3:cvrNone: dmi.product.family: INVALID dmi.product.name: 30E102Z dmi.product.sku: LENOVO_MT_30E1_BU_Think_FM_ThinkStation P620 dmi.product.version: ThinkStation P620 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/qemu/+bug/1915063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922792] Re: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi
Thank you for the work, could give a bit more context why a reboot is needed in those cases? Isn't restarting the service enough? Having hardcoded addresses in the script seems a bit fragile. And is that the sort of change we could try to upstream to Debian to not increase our delta? Also the description states 'In the case of upgrading bluez', is that specific to some version? if the issue is with upgrade the postinst code should check that we are in the upgrade case and not a new install no? ** Changed in: bluez (Ubuntu) Status: Triaged => Incomplete -- 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/1922792 Title: Bluez should notify users when they need to reboot to apply changes on Raspberry Pi Status in bluez package in Ubuntu: Incomplete Bug description: In the case of upgrading bluez on certain raspberry pi devices, a reboot may be required to apply the changes. We should add a check for this scenario in the postinst script. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1922792/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1917116] Re: ubuntu 20.04.2 LTS linux kernel 5.11 updates
Hello, it's unclear what is the problem here. can you tell us more about the issue that you have encountered? Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1917116 Title: ubuntu 20.04.2 LTS linux kernel 5.11 updates Status in linux package in Ubuntu: Incomplete Bug description: ubuntu 20.04.2 LTS linux kernel 5.11 updates desktops and laptops MSI MS-7817 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1430 F pulseaudio /dev/snd/controlC0: snowden1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: snowden1430 F pulseaudio /dev/snd/controlC0: snowden1430 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-15 (11 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) IwConfig: enp2s0no wireless extensions. lono wireless extensions. MachineType: MSI MS-7817 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fi_FI.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-66-generic root=UUID=0ed74528-b26e-4707-b8a8-4f0c985be8c2 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-66.74-generic 5.4.86 RelatedPackageVersions: linux-restricted-modules-5.4.0-66-generic N/A linux-backports-modules-5.4.0-66-generic N/A linux-firmware1.187.9 RfKill: Tags: focal Uname: Linux 5.4.0-66-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/21/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V10.9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-E45 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 2.0 dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV10.9:bd04/21/2015:svnMSI:pnMS-7817:pvr2.0:rvnMSI:rnB85M-E45(MS-7817):rvr2.0:cvnMSI:ct3:cvr2.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 2.0 dmi.sys.vendor: MSI --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tessetessu 1400 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2021-02-20 (7 days ago) InstallationMedia:
[Kernel-packages] [Bug 1922494] Re: Ubuntu 20.04 - 'Support flow counters offset for bulk counters'
Amit Tzin - commit 208d70f562e5 ("IB/mlx5: Support flow counters offset
for bulk counters") extends an existing interface, correct ? Can you
tell me what user space applications might be affected ? It doesn't look
like it should impact ethtool.
--
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/1922494
Title:
Ubuntu 20.04 - 'Support flow counters offset for bulk counters'
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Focal:
In Progress
Bug description:
[impact]
Add Support for flow counters offset for bulk counters on kernel side.
Currently Ubuntu 20.04 supports 'flow counters offset for bulk counters' on
user space side only with these 3 rdma-core patches from v27.0
3956cf74 mlx5: Add support for bulk flow counters steering actions
65ed59c6 Update kernel headers
b32eee70 mlx5: Fix typos
[test case]
/* download and install dpdk from github (issue do not reproduce with inbox
dpdk) */
$ git clone https://github.com/mellanox/dpdk.org
$ cd dpdk.org/
/* install dependencies if needed */
$ apt-get install -y python3-pyelftools python-pyelftools
$ apt install meson
$ meson build-meson
$ ninja -C build-meson/
/* run dpdk-testpmd with mellanox HCA (I used CX5) :05:00.0,
:05:00.1 are pci id for the cx5 devices */
//dpdk.org/build-meson/app/dpdk-testpmd -v -n 4
-w :05:00.0,txq_inline=147,rx_vec_en=1 -w
:05:00.1,txq_inline=147,rx_vec_en=1 -- --mbcache=512 -i --nb-
cores=7 --txd=8192 --rxd=8192 --burst=64
EAL: Detected 12 lcore(s)
EAL: Detected 2 NUMA nodes
EAL: RTE Version: 'DPDK 21.05.0-rc0'
Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
Option -w, --pci-whitelist is deprecated, use -a, --allow option instead
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'VA'
EAL: Probing VFIO support...
EAL: VFIO support initialized
EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.0 (socket 0)
mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
mlx5_pci: Default miss action is not supported.
mlx5_pci: Unexpected error in counter offset support detection /*
LINE INDICATING ERROR*/
EAL: Probe PCI driver: mlx5_pci (15b3:101d) device: :05:00.1 (socket 0)
mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
mlx5_pci: txq_inline: deprecated parameter, converted to txq_inline_max
mlx5_pci: Default miss action is not supported.
mlx5_pci: Unexpected error in counter offset support detection /*
LINE INDICATING ERROR*/
Interactive-mode selected
testpmd: create a new mbuf pool : n=327680, size=2176, socket=0
testpmd: preferred mempool ops selected: ring_mp_mc
testpmd: create a new mbuf pool : n=327680, size=2176, socket=1
testpmd: preferred mempool ops selected: ring_mp_mc
Configuring Port 0 (socket 0)
Port 0: 0C:42:A1:D1:D0:64
Configuring Port 1 (socket 0)
Port 1: 0C:42:A1:D1:D0:65
Checking link statuses...
Done
testpmd>
two lines indicates errors in counter offset supports detection.
[Fix]
the issue is fixed with the following upstream commit from v5.5-rc1 which
cleanly applied above focal.
208d70f562e5 IB/mlx5: Support flow counters offset for bulk counters
Our QA-dpdk team tested the focal kernel with this patch and found no issues.
Thanks,
Amir
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922494/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] acpidump.txt
apport information ** Attachment added: "acpidump.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485630/+files/acpidump.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Description changed: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. - ProblemType: Bug - DistroRelease: Ubuntu 20.10 - Package: gnome-power-manager 3.32.0-2 - ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 - Uname: Linux 5.8.0-48-generic x86_64 - NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia - ApportVersion: 2.20.11-0ubuntu50.5 - Architecture: amd64 - CasperMD5CheckResult: skip - CurrentDesktop: ubuntu:GNOME - Date: Thu Apr 8 14:54:05 2021 - SourcePackage: gnome-power-manager - UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: gerd-jln 4642 F pulseaudio - /dev/snd/controlC1: gerd-jln 4642 F pulseaudio - /dev/snd/controlC0: gerd-jln 4642 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: gerd-jln 4642 F pulseaudio + /dev/snd/controlC1: gerd-jln 4642 F pulseaudio + /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 + linux-restricted-modules-5.8.0-48-generic N/A + linux-backports-modules-5.8.0-48-generic N/A + linux-firmware1.190.3 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO -- 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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic
[Kernel-packages] [Bug 1923050] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485629/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485628/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485627/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485626/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485625/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485624/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485623/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485622/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485621/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] PaInfo.txt
apport information ** Attachment added: "PaInfo.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485620/+files/PaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485619/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485618/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485617/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485616/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485615/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485614/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485612/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485613/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/23/2021 dmi.bios.release: 1.19 dmi.bios.vendor: LENOVO dmi.bios.version: N2XET29W (1.19 ) dmi.board.asset.tag: Not Available dmi.board.name: 20S0CTO1WW 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.8 dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T14 Gen 1 dmi.product.name: 20S0CTO1WW dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 dmi.product.version: ThinkPad T14 Gen 1 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] Re: Cannot resume from suspend
apport information ** Tags added: apport-collected ** Description changed: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 14:54:05 2021 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu50.5 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC2: gerd-jln 4642 F pulseaudio + /dev/snd/controlC1: gerd-jln 4642 F pulseaudio + /dev/snd/controlC0: gerd-jln 4642 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.10 + MachineType: LENOVO 20S0CTO1WW + NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 + 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 + Tags: groovy + Uname: Linux 5.8.0-48-generic x86_64 + UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) + UserGroups: adm cdrom dip docker lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True + dmi.bios.date: 03/23/2021 + dmi.bios.release: 1.19 + dmi.bios.vendor: LENOVO + dmi.bios.version: N2XET29W (1.19 ) + dmi.board.asset.tag: Not Available + dmi.board.name: 20S0CTO1WW + 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.8 + dmi.modalias: dmi:bvnLENOVO:bvrN2XET29W(1.19):bd03/23/2021:br1.19:efr1.8:svnLENOVO:pn20S0CTO1WW:pvrThinkPadT14Gen1:rvnLENOVO:rn20S0CTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: + dmi.product.family: ThinkPad T14 Gen 1 + dmi.product.name: 20S0CTO1WW + dmi.product.sku: LENOVO_MT_20S0_BU_Think_FM_ThinkPad T14 Gen 1 + dmi.product.version: ThinkPad T14 Gen 1 + dmi.sys.vendor: LENOVO ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1923050/+attachment/5485611/+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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Confirmed Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: gerd-jln 4642 F pulseaudio /dev/snd/controlC1: gerd-jln 4642 F pulseaudio /dev/snd/controlC0: gerd-jln 4642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 MachineType: LENOVO 20S0CTO1WW NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.8.0-48-generic root=UUID=cbb6a58a-3e2d-44a3-ab59-54919a1464d4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 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 Tags: groovy Uname: Linux 5.8.0-48-generic x86_64 UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago)
[Kernel-packages] [Bug 1923050] [NEW] Cannot resume from suspend
Public bug reported: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 14:54:05 2021 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug groovy lenovo power ** Package changed: gnome-power-manager (Ubuntu) => ubuntu ** Package changed: ubuntu => linux (Ubuntu) ** Description changed: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither - pushing the power button or opening the lid solves the issue. I've tried - switching between versions 450 and 460 of the Nvidia graphics driver as - well as Noveau and the issues persists regardless of which driver I use. + pushing the power button or opening the lid solves the issue. The led + indicator continues to pulsate and there's no indication of any response + from the computer. + + I've tried switching between versions 450 and 460 of the Nvidia graphics + driver as well as Noveau and the issues persists regardless of which + driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 14:54:05 2021 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) -- 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/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 14:54:05 2021 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923049] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1923049 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923049 Title: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Bug description: Focal, linux-gcp, 5.4.0-1041.44: 1.03/31 01:43:32 INFO |ubuntu_ltp:0103| Setting LTP_TIMEOUT_MUL exceptions... 2.03/31 01:43:32 INFO |ubuntu_ltp:0106| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 for memcg_test_3 (lp:1836694) 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1923050 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923050 Title: Cannot resume from suspend Status in linux package in Ubuntu: Incomplete Bug description: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. The led indicator continues to pulsate and there's no indication of any response from the computer. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 14:54:05 2021 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1923050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923049] [NEW] autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4
Public bug reported: Focal, linux-gcp, 5.4.0-1041.44: 1. 03/31 01:43:32 INFO |ubuntu_ltp:0103| Setting LTP_TIMEOUT_MUL exceptions... 2. 03/31 01:43:32 INFO |ubuntu_ltp:0106| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 for memcg_test_3 (lp:1836694) 3. ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: 5.4 amd64 focal gcp sru-20210315 ** Also affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Tags added: amd64 focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1923049 Title: autotest.ubuntu_ltp_stable dio fails on focal:linux-gcp 5.4 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: New Bug description: Focal, linux-gcp, 5.4.0-1041.44: 1.03/31 01:43:32 INFO |ubuntu_ltp:0103| Setting LTP_TIMEOUT_MUL exceptions... 2.03/31 01:43:32 INFO |ubuntu_ltp:0106| Running in VM, set timeout multiplier LTP_TIMEOUT_MUL=3 for memcg_test_3 (lp:1836694) 3. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1923049/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1923050] [NEW] Cannot resume from suspend
You have been subscribed to a public bug: I cannot resume from suspend. I am on Ubuntu 20.10, Gnome 3.38. Neither pushing the power button or opening the lid solves the issue. I've tried switching between versions 450 and 460 of the Nvidia graphics driver as well as Noveau and the issues persists regardless of which driver I use. This started happening no too long ago, maybe around a month from now. It previously worked just fine. ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.8.0-48.54-generic 5.8.18 Uname: Linux 5.8.0-48-generic x86_64 NonfreeKernelModules: vtsspp sep5 socperf3 pax nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu50.5 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 8 14:54:05 2021 SourcePackage: gnome-power-manager UpgradeStatus: Upgraded to groovy on 2020-12-21 (107 days ago) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug groovy lenovo power -- Cannot resume from suspend https://bugs.launchpad.net/bugs/1923050 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 1891768] Re: hfs+ filesystems fail reading / writing large files
Richard - you could try installing linux-oem-5.10. There are a few bug fixes between v5.4 and v5.10 releases. sudo apt-get install linux-oem-5.10 -- 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/1891768 Title: hfs+ filesystems fail reading / writing large files Status in linux package in Ubuntu: Confirmed Bug description: I noticed a problem reading hfs+ partitions on a USB flash drive after I installed Ubuntu 20.04 on two laptop machines. I have a Mini Mac that I share files via an USB flash drive formatted with hfs+ from the laptops with Ubuntu installed. I had no issues with Ubuntu Mate 18.10. I noticed that very large files, typicality larger than 100 MB, would have read errors or sometimes have a zero file size. One particular file about 500MB fails nearly every time. Other files, down to about 100MB fail sometimes. I bought a new USB flash drive, but have the same failures on that. I have an identical flash drive formatted with ext4 which has no issues. I'm currently booting to Ubuntu Mate 18.10 to write the hfs+ USB flash drive. 1007 ceres ~ cat /proc/version_signature Ubuntu 5.4.0-42.46-generic 5.4.44 1000 ceres ~ lsb_release -rd Description: Ubuntu 20.04.1 LTS Release: 20.04 1005 admin@ceres ~ sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error pcilib: sysfs_read_vpd: read failed: Input/output error --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.6 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: uschcld1581 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-17 (91 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 0408:a030 Quanta Computer, Inc. HD WebCam Bus 001 Device 003: ID 04ca:3015 Lite-On Technology Corp. Bus 001 Device 002: ID 046d:c06c Logitech, Inc. Optical Mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Aspire E5-576 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=75021464-0e3f-4ad2-a466-cf655a6c4dd7 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 Tags: focal Uname: Linux 5.4.0-42-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip fax floppy plugdev tape video www-data _MarkForUpload: True dmi.bios.date: 09/06/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.47 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Ironman_SK dmi.board.vendor: KBL dmi.board.version: V1.47 dmi.chassis.type: 10 dmi.chassis.vendor: Chassis Manufacturer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.47:bd09/06/2018:svnAcer:pnAspireE5-576:pvrV1.47:rvnKBL:rnIronman_SK:rvrV1.47:cvnChassisManufacturer:ct10:cvrChassisVersion: dmi.product.family: Aspire E 15 dmi.product.name: Aspire E5-576 dmi.product.sku: dmi.product.version: V1.47 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891768/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829995] Re: getaddrinfo_01 from ipv6_lib test suite in LTP failed
** Tags added: gcp
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-aws in Ubuntu.
https://bugs.launchpad.net/bugs/1829995
Title:
getaddrinfo_01 from ipv6_lib test suite in LTP failed
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux-aws package in Ubuntu:
New
Status in linux source package in Bionic:
Incomplete
Status in linux-aws source package in Bionic:
New
Status in linux source package in Eoan:
New
Status in linux-aws source package in Eoan:
New
Bug description:
startup='Wed May 22 08:02:52 2019'
getaddrinfo_011 TPASS : getaddrinfo IPv4 basic lookup
getaddrinfo_012 TFAIL : getaddrinfo_01.c:140: getaddrinfo IPv4
canonical name ("curly.maas") doesn't match hostname ("curly")
getaddrinfo_013 TFAIL : getaddrinfo_01.c:578: getaddrinfo IPv6 basic
lookup ("curly") returns -5 ("No address associated with hostname")
tag=getaddrinfo_01 stime=1558512172 dur=1 exit=exited stat=1 core=no cu=0 cs=0
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-50-generic 4.15.0-50.54
ProcVersionSignature: User Name 4.15.0-50.54-generic 4.15.18
Uname: Linux 4.15.0-50-generic x86_64
AlsaDevices:
total 0
crw-rw 1 root audio 116, 1 May 22 02:57 seq
crw-rw 1 root audio 116, 33 May 22 02:57 timer
AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay'
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord':
'arecord'
AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
'/dev/snd/timer'] failed with exit code 1:
CurrentDmesg:
Date: Wed May 22 08:04:30 2019
IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig'
Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: QEMU Standard PC (i440FX + PIIX, 1996)
PciMultimedia:
ProcFB: 0 cirrusdrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-50-generic
root=UUID=57e8-9e7f-40ee-934e-f1dce18323e5 ro
RelatedPackageVersions:
linux-restricted-modules-4.15.0-50-generic N/A
linux-backports-modules-4.15.0-50-generic N/A
linux-firmware 1.173.6
RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill'
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 04/01/2014
dmi.bios.vendor: SeaBIOS
dmi.bios.version: Ubuntu-1.8.2-1ubuntu1
dmi.chassis.type: 1
dmi.chassis.vendor: QEMU
dmi.chassis.version: pc-i440fx-xenial
dmi.modalias:
dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial:
dmi.product.name: Standard PC (i440FX + PIIX, 1996)
dmi.product.version: pc-i440fx-xenial
dmi.sys.vendor: QEMU
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1829995/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922402] Re: zfs list has no boot partition as specified
** Changed in: zfs-linux (Ubuntu Hirsute) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1922402 Title: zfs list has no boot partition as specified Status in zfs-linux package in Ubuntu: Fix Released Status in zfs-linux source package in Hirsute: Fix Released Bug description: no zfs boot filesystem as specified in test case, but solaris boot partition shows in fdisk list. System operates normally, snapshot taken successfully of rpool/ROOT/ubuntu_qyi2f5. # zfs mount rpool/ROOT/ubuntu_qyi2f5/ rpool/ROOT/ubuntu_qyi2f5/var/games /var/games rpool/ROOT/ubuntu_qyi2f5/var/spool /var/spool rpool/ROOT/ubuntu_qyi2f5/var/snap /var/snap rpool/ROOT/ubuntu_qyi2f5/var/www /var/www rpool/ROOT/ubuntu_qyi2f5/srv/srv rpool/ROOT/ubuntu_qyi2f5/var/lib /var/lib rpool/ROOT/ubuntu_qyi2f5/var/mail /var/mail rpool/ROOT/ubuntu_qyi2f5/usr/local /usr/local rpool/ROOT/ubuntu_qyi2f5/var/lib/apt /var/lib/apt rpool/ROOT/ubuntu_qyi2f5/var/log /var/log rpool/ROOT/ubuntu_qyi2f5/var/lib/AccountsService /var/lib/AccountsService rpool/ROOT/ubuntu_qyi2f5/var/lib/NetworkManager /var/lib/NetworkManager rpool/ROOT/ubuntu_qyi2f5/var/lib/dpkg /var/lib/dpkg # zsysctl show Name: rpool/ROOT/ubuntu_qyi2f5 ZSys: true Last Used: current Users: $ fdisk -l Disk /dev/sda: 596.17 GiB, 640135028736 bytes, 1250263728 sectors Disk model: TOSHIBA MK6459GS Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 512 bytes I/O size (minimum/optimal): 512 bytes / 512 bytes Disklabel type: gpt Disk identifier: A5C2BBD7-0A3F-4822-B0E4-B5DC00B91CB7 Device StartEndSectors Size Type /dev/sda1 2048 4095 2048 1M BIOS boot /dev/sda2 409610547191050624 513M EFI System /dev/sda3 105472052490234194304 2G Linux swap /dev/sda4 524902494433274194304 2G Solaris boot /dev/sda5 9443328 1250263694 1240820367 591.7G Solaris root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1922402/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1521173] Re: AER: Corrected error received: id=00e0
Hello to all. I have the same problem, and this has affected me for a long time now. I described it in detail here, with output, videos, photos etc: https://ubuntuforums.org/showthread.php?t=2460318 I hope this adds useful information to draw attention to the bug in question. -- 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/1521173 Title: AER: Corrected error received: id=00e0 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Status in linux source package in Xenial: Triaged Bug description: WORKAROUND: add pci=noaer to your kernel command line: 1) edit /etc/default/grub and and add pci=noaer to the line starting with GRUB_CMDLINE_LINUX_DEFAULT. It will look like this: GRUB_CMDLINE_LINUX_DEFAULT="quiet splash pci=noaer" 2) run "sudo update-grub" 3) reboot My dmesg gets completely spammed with the following messages appearing over and over again. It stops after one s3 cycle; it only happens after reboot. [ 5315.986588] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.987249] pcieport :00:1c.0: can't find device of ID00e0 [ 5315.995632] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5315.995664] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5315.995674] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5315.995683] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.002772] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.002811] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.002826] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.002838] pcieport :00:1c.0:[ 0] Receiver Error [ 5316.009926] pcieport :00:1c.0: AER: Corrected error received: id=00e0 [ 5316.009964] pcieport :00:1c.0: PCIe Bus Error: severity=Corrected, type=Physical Layer, id=00e0(Receiver ID) [ 5316.009979] pcieport :00:1c.0: device [8086:9d14] error status/mask=0001/2000 [ 5316.009991] pcieport :00:1c.0:[ 0] Receiver Error ProblemType: BugDistroRelease: Ubuntu 16.04 Package: linux-image-4.2.0-19-generic 4.2.0-19.23 [modified: boot/vmlinuz-4.2.0-19-generic] ProcVersionSignature: Ubuntu 4.2.0-19.23-generic 4.2.6 Uname: Linux 4.2.0-19-generic x86_64 ApportVersion: 2.19.2-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0c: david 1502 F...m pulseaudio /dev/snd/controlC0: david 1502 F pulseaudio CurrentDesktop: Unity Date: Mon Nov 30 13:19:00 2015 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=fe528b90-b4eb-4a20-82bd-6a03b79cfb14 InstallationDate: Installed on 2015-11-28 (2 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20151127) MachineType: Dell Inc. Inspiron 13-7359 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-19-generic.efi.signed root=UUID=94d54f88-5d18-4e2b-960a-8717d6e618bb ro noprompt persistent quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-19-generic N/A linux-backports-modules-4.2.0-19-generic N/A linux-firmware1.153SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/07/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: 01.00.00 dmi.board.name: 0NT3WX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr01.00.00:bd08/07/2015:svnDellInc.:pnInspiron13-7359:pvr:rvnDellInc.:rn0NT3WX:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.name: Inspiron 13-7359 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1521173/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921137] Re: mount.ocfs2 causes kernel BUG at lib/string.c:1149!
** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Tags added: rls-ff-incoming -- 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/1921137 Title: mount.ocfs2 causes kernel BUG at lib/string.c:1149! Status in corosync package in Ubuntu: New Status in libaio package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in ocfs2-tools package in Ubuntu: New Bug description: the ocfs2-tools autopkgtests for hirsute recently started failing, and a local test run shows this kernel bug occurring during the test: [ 100.791586] o2dlm: Leaving domain 1D5A19C6EC8F430AB4E29230BC54D70E [ 108.864491] detected buffer overflow in strlen [ 108.869193] [ cut here ] [ 108.869196] kernel BUG at lib/string.c:1149! [ 108.869962] invalid opcode: [#1] SMP PTI [ 108.870715] CPU: 15 PID: 1725 Comm: mount.ocfs2 Not tainted 5.11.0-11-generic #12-Ubuntu [ 108.872156] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS 1.13.0-1ubuntu1.1 04/01/2014 [ 108.873701] RIP: 0010:fortify_panic+0x13/0x15 [ 108.874452] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.879043] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.880396] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.882165] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.883474] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.884758] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.885961] R13: 926a49917800 R14: 926a54bdc800 R15: 926a4cd06291 [ 108.887163] FS: 7f8440b60600() GS:926b77bc() knlGS: [ 108.888626] CS: 0010 DS: ES: CR0: 80050033 [ 108.889607] CR2: 55eec2b97dc8 CR3: 000106c64000 CR4: 06e0 [ 108.890823] Call Trace: [ 108.891279] ocfs2_initialize_super.isra.0.cold+0xc/0x18 [ocfs2] [ 108.892603] ? ocfs2_sb_probe+0x133/0x3a0 [ocfs2] [ 108.893484] ? pointer+0x185/0x4d0 [ 108.894079] ocfs2_fill_super+0x15d/0x7a0 [ocfs2] [ 108.894965] mount_bdev+0x18d/0x1c0 [ 108.895570] ? ocfs2_remount+0x450/0x450 [ocfs2] [ 108.896518] ocfs2_mount+0x15/0x20 [ocfs2] [ 108.897293] legacy_get_tree+0x2b/0x50 [ 108.897939] vfs_get_tree+0x2a/0xc0 [ 108.898542] do_new_mount+0x14b/0x1a0 [ 108.899175] path_mount+0x1d4/0x4e0 [ 108.899789] __x64_sys_mount+0x108/0x140 [ 108.900465] do_syscall_64+0x38/0x90 [ 108.901129] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 108.902376] RIP: 0033:0x7f8441109bce [ 108.903169] Code: 48 8b 0d 9d 72 0c 00 f7 d8 64 89 01 48 83 c8 ff c3 66 2e 0f 1f 84 00 00 00 00 00 90 f3 0f 1e fa 49 89 ca b8 a5 00 00 00 0f 05 <48> 3d 01 f0 ff ff 73 01 c3 48 8b 0d 6a 72 0c 00 f7 d8 64 89 01 48 [ 108.906322] RSP: 002b:7fff92a4e2f8 EFLAGS: 0246 ORIG_RAX: 00a5 [ 108.907610] RAX: ffda RBX: RCX: 7f8441109bce [ 108.909000] RDX: 55eec0e140ae RSI: 55eec2b899e0 RDI: 55eec2b8f060 [ 108.910727] RBP: 7fff92a4e4a0 R08: 55eec2b8f000 R09: 7fff92a4bd00 [ 108.912443] R10: R11: 0246 R12: 7fff92a4e390 [ 108.914190] R13: 7fff92a4e310 R14: 55eec2b8ac00 R15: [ 108.916009] Modules linked in: ocfs2 quota_tree ocfs2_dlmfs ocfs2_stack_o2cb ocfs2_dlm ocfs2_nodemanager ocfs2_stackglue 9p fscache nls_iso8859_1 dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua ppdev bochs_drm drm_vram_helper drm_ttm_helper ttm kvm_intel drm_kms_helper parport_pc 9pnet_virtio cec input_leds joydev 9pnet parport rc_core fb_sys_fops serio_raw kvm syscopyarea sysfillrect sysimgblt mac_hid qemu_fw_cfg sch_fq_codel msr drm virtio_rng ip_tables x_tables autofs4 btrfs blake2b_generic xor raid6_pq libcrc32c virtio_net net_failover psmouse failover virtio_blk i2c_piix4 pata_acpi floppy [ 108.925313] ---[ end trace 72e4f69b08b1a89a ]--- [ 108.927136] RIP: 0010:fortify_panic+0x13/0x15 [ 108.928706] Code: 35 28 e5 36 01 48 c7 c7 2b f2 80 92 e8 00 c4 fe ff 41 5c 41 5d 5d c3 55 48 89 fe 48 c7 c7 78 f2 80 92 48 89 e5 e8 e7 c3 fe ff <0f> 0b 48 c7 c7 d0 f7 48 92 e8 df ff ff ff 48 c7 c7 d8 f7 48 92 e8 [ 108.932308] RSP: 0018:a9cf811afc90 EFLAGS: 00010246 [ 108.933231] RAX: 0022 RBX: 926a4cd06000 RCX: [ 108.934468] RDX: RSI: 926b77bd8ac0 RDI: 926b77bd8ac0 [ 108.935659] RBP: a9cf811afc90 R08: R09: a9cf811afa88 [ 108.936933] R10: a9cf811afa80 R11: 92f53508 R12: 0004 [ 108.938141] R13:
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot
I am using the desktop ISO (both images). I've added to the bug description that the original ISO that I used was the beta ISO downloaded from this URL: http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso I validated the ISO checksum against the given checksum and verified the checksum file against the signing key. I downloaded the daily image on 04-05-2021 when the file had a last modified date of 04-05-2021 from this URL: https://cdimage.ubuntu.com /daily-live/current/hirsute-desktop-amd64.iso and it had the same issue. ** Summary changed: - hirsute live cd kernel panic on boot + hirsute beta desktop ISO kernel panic on boot ** Summary changed: - hirsute beta desktop ISO kernel panic on boot + hirsute beta desktop AMD64 ISO kernel panic on boot -- 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/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot Status in linux package in Ubuntu: Confirmed Bug description: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot
** Description changed: - I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a - Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI - Certificate Authority) enabled. + I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; + http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) + inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft + UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). -- 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/1922403 Title: hirsute beta desktop AMD64 ISO kernel panic on boot Status in linux package in Ubuntu: Confirmed Bug description: I've tried to boot the Ubuntu 21.04 desktop beta Live CD (AMD64; http://releases.ubuntu.com/21.04/ubuntu-21.04-beta-desktop-amd64.iso) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922779] Re: vc4 and v3d module not loaded
Ah yes, you're right, thanks. I removed Groovy and added instead Hirsute. Daily hirsute images: http://cdimage.ubuntu.com/daily-preinstalled/ ** Also affects: linux-raspi (Ubuntu Hirsute) Importance: Undecided Status: New ** Changed in: linux-raspi (Ubuntu Hirsute) Status: New => Fix Released ** No longer affects: linux-raspi (Ubuntu Groovy) -- 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/1922779 Title: vc4 and v3d module not loaded Status in linux-raspi package in Ubuntu: Fix Released Status in linux-raspi source package in Hirsute: Fix Released Bug description: I am testing ubuntu 21.04 beta on raspberry pi 4 and after installation and also after restart vc4 v3d kernel module isn't loaded So 3d acceleration don't work uname -a Linux misko-desktop 5.11.0-1004-raspi #4-Ubuntu SMP PREEMPT Mon Mar 22 15:51:28 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1922779/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922403] Re: hirsute live cd kernel panic on boot
Thank you for taking the time to report this bug and helping to make Ubuntu better. I realize you cannot run the `apport-collect`, but this bug currently is missing details as to - what ISO you're talking about? server? desktop? etc - which daily image? (usually in format mmdd but may also have a .y appended if image is re-spun that day) - if you validated the ISO checksum? (did you verify your ISO? as per https://tutorials.ubuntu.com/tutorial/tutorial-how-to-verify-ubuntu#0 for example) You do mention the 2021-04-04 ISO had that same issue, thanks for that detail, but is that the ISO you filed against? and what ISO was it? Thank you for your report. -- 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/1922403 Title: hirsute live cd kernel panic on boot Status in linux package in Ubuntu: Confirmed Bug description: I've tried to boot the Ubuntu 21.04 beta Live CD (AMD64) inside a Hyper-V Gen 2 Virtual Machine with UEFI Secure Boot (Microsoft UEFI Certificate Authority) enabled. The GRUB boot menu loads, and I continue with the default option. I immediately get a kernel panic (screenshot attached). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes
** Tags added: sru-20210315 -- 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/1783881 Title: ltp-syscalls: msgstress03 / msgstress04 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797341] Re: msgstress03 in ubuntu_ltp_syscalls failed with KVM nodes
*** This bug is a duplicate of bug 1783881 *** https://bugs.launchpad.net/bugs/1783881 ** Tags added: sru-20210315 ** Tags added: 5.4 -- 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/1797341 Title: msgstress03 in ubuntu_ltp_syscalls failed with KVM nodes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Bug description: The test failed with: Fork failed (may be OK if under stress) <<>> tag=msgstress03 stime=1539248897 cmdline="msgstress03" contacts="" analysis=exit <<>> incrementing stop Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157:Fork failed (may be OK if under stress) <<>> initiation_status="ok" duration=48 termination_type=exited termination_id=1 corefile=no cutime=3 cstime=24 <<>> Complete test log: https://pastebin.ubuntu.com/p/rW2DkFpsKm/ ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-1036-kvm 4.4.0-1036.42 ProcVersionSignature: User Name 4.4.0-1036.42-kvm 4.4.155 Uname: Linux 4.4.0-1036-kvm x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 Date: Thu Oct 11 09:08:52 2018 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1797341/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1888647] Re: Realtek wifi dont work after update
** Changed in: linux-firmware (Ubuntu) Status: Triaged => In Progress -- 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/1888647 Title: Realtek wifi dont work after update Status in linux-firmware package in Ubuntu: In Progress Bug description: lsb_release -rd Description:Ubuntu 18.04.4 LTS Release:18.04 apt-cache policy linux-firmware linux-firmware: Installed: 1.173.19 Candidate: 1.173.19 Version table: *** 1.173.19 500 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic-updates/main i386 Packages 100 /var/lib/dpkg/status 1.173.18 500 500 http://security.ubuntu.com/ubuntu bionic-security/main amd64 Packages 500 http://security.ubuntu.com/ubuntu bionic-security/main i386 Packages 1.173 500 500 http://ru.archive.ubuntu.com/ubuntu bionic/main amd64 Packages 500 http://ru.archive.ubuntu.com/ubuntu bionic/main i386 Packages PCI Wifi adapter dont work after update Part of kern.log Jul 23 14:04:25 pao-note kernel: [0.570519] pci :02:00.0: [10ec:c822] type 00 class 0x028000 Jul 23 14:04:25 pao-note kernel: [0.570564] pci :02:00.0: reg 0x10: [io 0x2000-0x20ff] Jul 23 14:04:25 pao-note kernel: [0.570598] pci :02:00.0: reg 0x18: [mem 0xb130-0xb130 64bit] Jul 23 14:04:25 pao-note kernel: [0.570758] pci :02:00.0: supports D1 D2 Jul 23 14:04:25 pao-note kernel: [0.570759] pci :02:00.0: PME# supported from D0 D1 D2 D3hot D3cold Jul 23 14:04:25 pao-note kernel: [ 21.479711] rtw_pci :02:00.0: enabling device ( -> 0003) Jul 23 14:04:25 pao-note kernel: [ 21.479783] rtw_pci :02:00.0: Direct firmware load for rtw88/rtw8822c_wow_fw.bin failed with error -2 Jul 23 14:04:25 pao-note kernel: [ 21.479784] rtw_pci :02:00.0: failed to request firmware Jul 23 14:04:25 pao-note kernel: [ 21.480312] rtw_pci :02:00.0: Firmware version 5.0.0, H2C version 14 Jul 23 14:04:25 pao-note kernel: [ 21.593905] rtw_pci :02:00.0 wlp2s0: renamed from wlan0 Jul 23 14:04:25 pao-note kernel: [ 22.164022] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.176798] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:25 pao-note kernel: [ 22.177910] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.014995] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:35 pao-note kernel: [ 32.017051] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.012048] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:45 pao-note kernel: [ 42.013137] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.011861] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:04:55 pao-note kernel: [ 52.013348] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.203876] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:05 pao-note kernel: [ 62.205477] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.262757] rtw_pci :02:00.0: failed to wait firmware completion Jul 23 14:05:15 pao-note kernel: [ 72.263944] rtw_pci :02:00.0: failed to wait firmware completion lspci 00:00.0 Host bridge: Intel Corporation Device 9b61 (rev 0c) 00:02.0 VGA compatible controller: Intel Corporation Device 9b41 (rev 02) 00:04.0 Signal processing controller: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Thermal Subsystem (rev 0c) 00:08.0 System peripheral: Intel Corporation Xeon E3-1200 v5/v6 / E3-1500 v5 / 6th/7th Gen Core Processor Gaussian Mixture Model 00:12.0 Signal processing controller: Intel Corporation Device 02f9 00:14.0 USB controller: Intel Corporation Device 02ed 00:14.2 RAM memory: Intel Corporation Device 02ef 00:15.0 Serial bus controller [0c80]: Intel Corporation Device 02e8 00:16.0 Communication controller: Intel Corporation Device 02e0 00:17.0 SATA controller: Intel Corporation Device 02d3 00:1d.0 PCI bridge: Intel Corporation Device 02b0 (rev f0) 00:1d.1 PCI bridge: Intel Corporation Device 02b1 (rev f0) 00:1d.2 PCI bridge: Intel Corporation Device 02b2 (rev f0) 00:1d.4 PCI bridge: Intel Corporation Device 02b4 (rev f0) 00:1e.0 Communication controller: Intel Corporation Device 02a8 00:1f.0 ISA bridge: Intel Corporation Device 0284 00:1f.3 Audio device: Intel Corporation Device 02c8 00:1f.4 SMBus: Intel Corporation Device 02a3 00:1f.5 Serial bus controller [0c80]: Intel
[Kernel-packages] [Bug 1922909] Re: Ubuntu 18.04 not detection SSD on SSD Samsung PM981a on Dell 5820 X-series
Getting below error while formating ext4 filesysstem on SSD drive
manually
Apr 8 13:12:25 localhost kernel: [ 773.855092] show_signal: 35 callbacks
suppressed
Apr 8 13:12:25 localhost kernel: [ 773.855094] traps: dpkg-query[8579]
general protection fault ip:7f008f209f11 sp:7ffc1d8d16a8 error:0 in
libc-2.27.so[7f008f07f000+1e7000]
Apr 8 13:12:25 localhost kernel: [ 773.913058] traps: apport[8581] general
protection fault ip:544414 sp:7ffe1f3ff9f0 error:0 in python3.6[40+3b4000]
Apr 8 13:12:25 localhost kernel: [ 773.913070] Process 8581(apport) has
RLIMIT_CORE set to 1
Apr 8 13:12:25 localhost kernel: [ 773.913070] Aborting core
Apr 8 13:12:27 localhost kernel: [ 776.151560] traps: dpkg-query[8582]
general protection fault ip:7f279c3f8f11 sp:7ffc81d44d18 error:0 in
libc-2.27.so[7f279c26e000+1e7000]
Apr 8 13:12:31 localhost kernel: [ 780.513187] XFS (nvme0n1): Unmounting
Filesystem
Apr 8 13:13:02 localhost kernel: [ 810.919029] traps: mkfs.ext4[8587]
general protection fault ip:7f003ac171bb sp:7ffcd7625470 error:0 in
libext2fs.so.2.4[7f003ac0+4d000]
Apr 8 13:13:16 localhost kernel: [ 825.229643] traps: apport[8598] general
protection fault ip:59cb64 sp:7ffcea1e5cf8 error:0 in python3.6[40+3b4000]
Apr 8 13:13:16 localhost kernel: [ 825.229657] Process 8598(apport) has
RLIMIT_CORE set to 1
Apr 8 13:13:16 localhost kernel: [ 825.229657] Aborting core
Apr 8 13:13:36 localhost kernel: [ 844.807235] traps: apport-checkrep[8604]
general protection fault ip:59cb60 sp:7fff43e688b8 error:0 in
python3.6[40+3b4000]
Apr 8 13:13:36 localhost kernel: [ 844.991014] apport-checkrep[8609]:
segfault at 8 ip 0054dc65 sp 7ffe23d42520 error 6 in
python3.6[40+3b4000]
Apr 8 13:13:36 localhost kernel: [ 844.991018] Code: 46 28 00 00 00 00 49 89
4e 20 48 85 c9 74 04 4c 89 71 28 4c 89 35 b3 0f 52 00 e9 c6 fc ff ff 4c 8b 52
e8 4c 8b 4a f0 4d 89 11 <4d> 89 4a 08 48 c7 42 e8 00 00 00 00 e9 7d fd ff ff 48
89 fe 48 8b
Apr 8 13:14:09 localhost kernel: [ 878.006289] traps: apport[8637] general
protection fault ip:59cb60 sp:7ffe82f661f8 error:0 in python3.6[40+3b4000]
Apr 8 13:14:09 localhost kernel: [ 878.006303] Process 8637(apport) has
RLIMIT_CORE set to 1
Apr 8 13:14:09 localhost kernel: [ 878.006303] Aborting core
Apr 8 13:14:33 localhost systemd[1]: Starting Cleanup of Temporary
Directories...
Apr 8 13:14:33 localhost systemd[1]: Started Cleanup of Temporary Directories.
Apr 8 13:15:01 localhost kernel: [ 929.918109] traps: apt-config[8682]
general protection fault ip:7f56f13e3ed0 sp:7ffeef400768 error:0 in
libapt-pkg.so.5.0.2[7f56f13a2000+1b6000]
Apr 8 13:15:01 localhost kernel: [ 929.928414] traps: apport[8683] general
protection fault ip:50cdaa sp:7ffd9052a960 error:0 in python3.6[40+3b4000]
Apr 8 13:15:01 localhost kernel: [ 929.928436] Process 8683(apport) has
RLIMIT_CORE set to 1
Apr 8 13:15:01 localhost kernel: [ 929.928436] Aborting core
Apr 8 13:15:01 localhost kernel: [ 930.422542] traps: apt-config[8868]
general protection fault ip:7f867f5347f8 sp:7ffcb8a4a8e8 error:0 in
ld-2.27.so[7f867f516000+29000]
Apr 8 13:15:01 localhost kernel: [ 930.431142] traps: apport[8869] general
protection fault ip:55d749 sp:7ffddcc41e60 error:0 in python3.6[40+3b4000]
Apr 8 13:15:01 localhost kernel: [ 930.431166] Process 8869(apport) has
RLIMIT_CORE set to 1
Apr 8 13:15:01 localhost kernel: [ 930.431167] Aborting core
--
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/1922909
Title:
Ubuntu 18.04 not detection SSD on SSD Samsung PM981a on Dell 5820
X-series
Status in linux package in Ubuntu:
Incomplete
Bug description:
Hi Team,
Please be note Ubuntu ISO 18.04.5 not detecting the samsung PM981a SSD
drive upon installation
#nvme list
Node SN Model
Namespace Usage Format FW Rev
- --
/dev/nvme0n1 S4UFNF0NC01090 PM981a NVMe SAMSUNG 2048GB
1 165.28 GB / 2.05 TB512 B + 0 B 15302229
Please provide a fix in the next 18.05.6 ISO.
Please note there is no uissue detecting in Ubuntu 20.04.2 ISO
Thanks
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1922909/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1922152] Re: F atal error: classmap.h: No such file or directory
** Changed in: linux-raspi (Ubuntu) Status: New => Invalid -- 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/1922152 Title: F atal error: classmap.h: No such file or directory Status in linux-raspi package in Ubuntu: Invalid Bug description: When building kernel module on ubuntu 20.04 server for raspberry (aarch64), I get the following error: make -C /lib/modules/5.4.0-1032-raspi/build SUBDIRS=/home/ubuntu/andor/src/driver modules make[1]: Entering directory '/usr/src/linux-headers-5.4.0-1032-raspi' HOSTCC scripts/selinux/genheaders/genheaders scripts/selinux/genheaders/genheaders.c:18:10: fatal error: classmap.h: No such file or directory 18 | #include "classmap.h" | ^~~~ compilation terminated. make[4]: *** [scripts/Makefile.host:107: scripts/selinux/genheaders/genheaders] Error 1 make[3]: *** [scripts/Makefile.build:522: scripts/selinux/genheaders] Error 2 make[2]: *** [scripts/Makefile.build:522: scripts/selinux] Error 2 make[1]: *** [Makefile:1127: scripts] Error 2 make[1]: Leaving directory '/usr/src/linux-headers-5.4.0-1032-raspi' make: *** [Makefile:12: default] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1922152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1912940] Re: Intel Wireless-AC 3165 [8086:3166] Subsystem [8086:4210] Bluetooth (ideapad_bluetooth) disabled every time on startup
Intel WiFi/Bluetooth Dual chips always have WiFi in `lspci` and Bluetooth in `lsusb`. For PCI part its PCI ID _and_ subsystem ID is critical for identifying them, USB VID/PID is not so useful as they can be even identical across different models. Anyway, this one has 3165 as updated in bug title. ** Summary changed: - Bluetooth (ideapad_bluetooth) disabled every time on startup + Intel Wireless-AC 3165 [8086:3166] Subsystem [8086:4210] Bluetooth (ideapad_bluetooth) disabled every time on startup ** Tags added: hwe-bluetooth -- 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/1912940 Title: Intel Wireless-AC 3165 [8086:3166] Subsystem [8086:4210] Bluetooth (ideapad_bluetooth) disabled every time on startup Status in linux package in Ubuntu: Confirmed Bug description: [Policy] AutoEnable=true not working ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 Uname: Linux 5.10.0-051000-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.14 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME CurrentDmesg: Error: command ['dmesg'] failed with exit code 1: dmesg: read kernel buffer failed: Operation not permitted Date: Sun Jan 24 19:49:49 2021 InstallationDate: Installed on 2021-01-24 (0 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 4: Dev 2, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 4: Dev 2, If 1, Class=Wireless, Driver=btusb, 12M MachineType: LENOVO 81CG ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.10.0-051000-generic root=UUID=0281b4fb-589a-46ed-b8ee-896d3505e7bd ro SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.release: 1.39 dmi.bios.vendor: LENOVO dmi.bios.version: 6NCN39WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40688 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 32 dmi.chassis.vendor: LENOVO dmi.chassis.version: MIIX 520-12IKB dmi.ec.firmware.release: 1.39 dmi.modalias: dmi:bvnLENOVO:bvr6NCN39WW:bd10/10/2019:br1.39:efr1.39:svnLENOVO:pn81CG:pvrMIIX520-12IKB:rvnLENOVO:rnLNVNB161216:rvrSDK0J40688WIN:cvnLENOVO:ct32:cvrMIIX520-12IKB: dmi.product.family: MIIX 520-12IKB dmi.product.name: 81CG dmi.product.sku: LENOVO_MT_81CG_BU_idea_FM_MIIX 520-12IKB dmi.product.version: MIIX 520-12IKB dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: 3C:6A:A7:BB:B7:63 ACL MTU: 1021:5 SCO MTU: 96:6 UP RUNNING PSCAN ISCAN RX bytes:213889 acl:13940 sco:0 events:310 errors:0 TX bytes:40352 acl:45 sco:0 commands:249 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1912940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1896167] Re: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B (using the FKMS driver)
Seems to be fixed now using full KMS. Full KMS required both: * Kernel >= 5.10.7 * Bug 1918110 to be fixed, which it now is. ** Package changed: mutter (Ubuntu) => flash-kernel (Ubuntu) ** Changed in: flash-kernel (Ubuntu) Status: Triaged => Fix Released ** Changed in: linux-raspi (Ubuntu) Status: Triaged => Fix Released ** Summary changed: - Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B (using the FKMS driver) + Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B -- 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/1896167 Title: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B Status in flash-kernel package in Ubuntu: Fix Released Status in linux-raspi package in Ubuntu: Fix Released Bug description: Heavy screen tearing in Wayland sessions on Raspberry Pi 4-B when using the FMKS driver, meaning you have: dtoverlay=vc4-fkms-v3d To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1896167/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921452] Re: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB-Audio.pcm.iec958_device
@seb128, sorry about this, a new version of debdiff for Groovy uploaded, thanks. ** Patch added: "alsa-lib_1.2.3.2-1ubuntu3.2.debdiff" https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1921452/+attachment/5485477/+files/alsa-lib_1.2.3.2-1ubuntu3.2.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1921452 Title: [SRU] alsa-lib: conf: USB - add "Cmedia Audio" to USB- Audio.pcm.iec958_device Status in OEM Priority Project: In Progress Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: In Progress Status in alsa-lib source package in Groovy: In Progress Status in alsa-lib source package in Hirsute: Fix Released Bug description: [Impact] On Cmedia Audio, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Where problems will occur] "Cmedia Audio" is the sound card name of this usb audio dongle, and this string is got from usb string descriptor, that is to say the "Cmedia Audio" is hard-coded in the firmware of that usb dongle. Not all Cmedia usb audio dongle use "Cmedia Audio", most of the dongles don't set string descriptor, then the audio driver sets a generic name "USB Audio Device" for them, if a dongle has string descriptor, it may have different string like "C-Media USB Headphone Set", and all dongles I met before don't have SPDIF interface. So If this SRU could introduce regression, it will happen on a Cmedia usb audio dongle which also hard-codes the "Cmedia Audio" in the string descriptor and it has SPDIF interface on it, after this SRU, users couldn't find the SPDIF playback device from the gnome-sound-setting. But this regression chance is very low since it is very rare a cmedia usb audio dongle uses "Cmedia Audio" in the string descriptor and it is very rare a usb audio dongle has SPDIF interface. So far we haven't met such a cmedia usb audio dongle. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1921452/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1921769] Re: Backport mlx5e fix for tunnel offload
** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1921769 Title: Backport mlx5e fix for tunnel offload Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-azure source package in Bionic: In Progress Status in linux source package in Focal: In Progress Status in linux-azure source package in Focal: In Progress Status in linux source package in Groovy: Incomplete Status in linux-azure source package in Groovy: Confirmed Status in linux source package in Hirsute: Incomplete Status in linux-azure source package in Hirsute: Confirmed Bug description: [SRU Justification] We've discovered an issue on Ubuntu 20.04 when used with Kubernetes CNIs that perform offloading using Geneve that causes the kernel to panic on Azure instances with accelerated networking with the following errors: [ 307.561223] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 0x3d4, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 307.573864] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5 [ 307.764902] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x200, ci 0x3d7, sqn 0x2c5, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 307.777332] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2c5 [ 322.814393] mlx5_core 0001:00:02.0 enP1s1: Error cqe on cqn 0x218, ci 0x1a7, sqn 0x2bd, opcode 0xd, syndrome 0x2, vendor syndrome 0x68 [ 322.826685] mlx5_core 0001:00:02.0 enP1s1: ERR CQE on SQ: 0x2bd NVIDIA fixed this issue in https://github.com/torvalds/linux/commit/5ccc0ecda9e8a67add654d93d7e0ac4346c0fa22 , so we're looking to have this backported to at least the linux-azure package. [Test Plan] Spin up a Kubernetes CNI that uses Geneve offloading [Where problems could occur] Its possible some traffic won't get geneve acceleration. This patch has been backported to v5.10.y and v5.11.y To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1921769/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
