[Kernel-packages] [Bug 1878138] [NEW] wifi problemas rtlbe8822be
Public bug reported: Mi servicio de wifi no funciona bien de deshabilita sola ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yesid 2249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 00:30:50 2020 InstallationDate: Installed on 2019-11-21 (172 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. X405UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-11 (0 days ago) dmi.bios.date: 05/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X405UA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X405UA 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.:bvrX405UA.203:bd05/05/2017:svnASUSTeKCOMPUTERINC.:pnX405UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX405UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X405UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878138 Title: wifi problemas rtlbe8822be Status in linux package in Ubuntu: New Bug description: Mi servicio de wifi no funciona bien de deshabilita sola ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yesid 2249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue May 12 00:30:50 2020 InstallationDate: Installed on 2019-11-21 (172 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: ASUSTeK COMPUTER INC. X405UA ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-11 (0 days ago) dmi.bios.date: 05/05/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X405UA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X405UA 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.:bvrX405UA.203:bd05/05/2017:svnASUSTeKCOMPUTERINC.:pnX405UA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX405UA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: X dmi.product.name: X405UA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878138/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work
Please use hid-tools' hid-recorder on the Touchpad's hidraw node to collect log. [1] https://gitlab.freedesktop.org/libevdev/hid-tools -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1866423] Re: [arm64] Enable USB support on Amlogic Meson GXL & GXM platforms
[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/1866423 Title: [arm64] Enable USB support on Amlogic Meson GXL & GXM platforms Status in linux package in Ubuntu: Expired Bug description: Please enable the following configs in Ubuntu Focal to fully enable USB support for the Amlogic Meson GXL & GXM (Amlogic S805X, S905X, S912) in Linux 5.4 CONFIG_PHY_MESON_GXL_USB2 CONFIG_PHY_MESON_GXL_USB3 CONFIG_USB_DWC3_OF_SIMPLE Some devices rely on USB support in order to load additional files to boot the system and installer. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866423/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867066] Re: [Dell XPS M1530] Touchpad issues
[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/1867066 Title: [Dell XPS M1530] Touchpad issues Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xserver-xorg-input-libinput package in Ubuntu: Expired Bug description: Good evening all I just change the laptop from lenovo to dell and can not find out how make work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button and an external mouse neither. The bluetooth will never work again untill re-installing an OS from micro-horror-soft, switching up the bluetooth module and re-installing ubuntu back. But I still love Linux ! I will appreciate if you help me, in the meantime i keep searching by myself in the ubuntu's forum how to fix my issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 23:49:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e] InstallationDate: Installed on 2020-03-06 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS M1530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash acpi_osi=!Windows 2012 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1867066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867034] Re: No keyboard backlight on ASUS VivoBook S14
[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/1867034 Title: No keyboard backlight on ASUS VivoBook S14 Status in linux package in Ubuntu: Expired Bug description: i couldnt turn on my keyboard light even i tried the xset command. My laptop is asus vivobook s14.. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867034/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866745] Re: Extreme slow Ubuntu startup
[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/1866745 Title: Extreme slow Ubuntu startup Status in linux package in Ubuntu: Expired Bug description: With the latest live release, starting takes around 4:30 to get to the jingle and around 5:40 to get Ubuntu up and running. With the version of 24-01-2020 instead 0:47 and 1:08 respectively. The boot time with the latest releases is exaggerated. Please check and correct the problem. Thank you. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1866745/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867066] Re: [Dell XPS M1530] Touchpad issues
[Expired for libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: libinput (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/1867066 Title: [Dell XPS M1530] Touchpad issues Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xserver-xorg-input-libinput package in Ubuntu: Expired Bug description: Good evening all I just change the laptop from lenovo to dell and can not find out how make work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button and an external mouse neither. The bluetooth will never work again untill re-installing an OS from micro-horror-soft, switching up the bluetooth module and re-installing ubuntu back. But I still love Linux ! I will appreciate if you help me, in the meantime i keep searching by myself in the ubuntu's forum how to fix my issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 23:49:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e] InstallationDate: Installed on 2020-03-06 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS M1530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash acpi_osi=!Windows 2012 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1867066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867066] Re: [Dell XPS M1530] Touchpad issues
[Expired for xserver-xorg-input-libinput (Ubuntu) because there has been no activity for 60 days.] ** Changed in: xserver-xorg-input-libinput (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/1867066 Title: [Dell XPS M1530] Touchpad issues Status in libinput package in Ubuntu: Expired Status in linux package in Ubuntu: Expired Status in xserver-xorg-input-libinput package in Ubuntu: Expired Bug description: Good evening all I just change the laptop from lenovo to dell and can not find out how make work the touchpad. Can not use two-finger scroll, pgdn/up, right primary button and an external mouse neither. The bluetooth will never work again untill re-installing an OS from micro-horror-soft, switching up the bluetooth module and re-installing ubuntu back. But I still love Linux ! I will appreciate if you help me, in the meantime i keep searching by myself in the ubuntu's forum how to fix my issues. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-88.88-generic 4.15.18 Uname: Linux 4.15.0-88-generic x86_64 NonfreeKernelModules: nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 340.107 Thu May 24 21:54:01 PDT 2018 GCC version: gcc version 7.4.0 (Ubuntu 7.4.0-1ubuntu1~18.04.1) .proc.driver.nvidia.warnings.fbdev: Your system is not currently configured to drive a VGA console on the primary VGA device. The NVIDIA Linux graphics driver requires the use of a text-mode VGA console. Use of other console drivers including, but not limited to, vesafb, may result in corruption and stability problems, and is not supported. .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Mar 11 23:49:44 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia-340, 340.107, 4.15.0-88-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation G84M [GeForce 8600M GT] [10de:0407] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Dell G84M [GeForce 8600M GT] [1028:022e] InstallationDate: Installed on 2020-03-06 (5 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. XPS M1530 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-88-generic root=UUID=d2388a4a-3b22-4fb6-af07-913d081f1cab ro quiet splash acpi_osi=!Windows 2012 vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/19/2008 dmi.bios.vendor: Dell Inc. dmi.bios.version: A12 dmi.board.name: 0D501F dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA12:bd11/19/2008:svnDellInc.:pnXPSM1530:pvr:rvnDellInc.:rn0D501F:rvr:cvnDellInc.:ct8:cvr: dmi.product.name: XPS M1530 dmi.sys.vendor: Dell Inc. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libinput/+bug/1867066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867142] Re: bluetooth device does not apear in lsusb or lspci
[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/1867142 Title: bluetooth device does not apear in lsusb or lspci Status in linux package in Ubuntu: Expired Bug description: Not able to pair a bluetooth device in ubuntu 19. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-40-generic 5.3.0-40.32 ProcVersionSignature: Ubuntu 5.3.0-40.32-generic 5.3.18 Uname: Linux 5.3.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ilegra0247 1514 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Mar 12 09:51:26 2020 InstallationDate: Installed on 2020-01-29 (42 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 0c45:671e Microdia Integrated_Webcam_HD Bus 001 Device 003: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 3583 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic root=UUID=e65185c6-9a25-4b6e-aac1-efe7e6330450 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-40-generic N/A linux-backports-modules-5.3.0-40-generic N/A linux-firmware1.183.4 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/11/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0T0MC0 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd07/11/2019:svnDellInc.:pnInspiron3583:pvr:rvnDellInc.:rn0T0MC0:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 3583 dmi.product.sku: 08CA dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867142/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in linux package in Ubuntu: Invalid Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
Again May 11 15:49:59 rudy-ThinkPad-T590 kernel: [ 4727.312939] i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 May 11 15:49:59 rudy-ThinkPad-T590 kernel: [ 4727.313946] i915 :00:02.0: Resetting rcs0 for hang on rcs0 May 12 05:48:08 rudy-ThinkPad-T590 kernel: [11927.393097] i915 :00:02.0: Resetting rcs0 for hang on rcs0 May 12 05:50:08 rudy-ThinkPad-T590 kernel: [12047.397104] i915 :00:02.0: Resetting rcs0 for hang on rcs0 May 12 06:04:00 rudy-ThinkPad-T590 kernel: [12879.363685] i915 :00:02.0: Resetting rcs0 for hang on rcs0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17
[Kernel-packages] [Bug 1877536] Re: BlueZ 5.54 release
Same update, with a nicer changelog. ** Attachment added: "bluez_5.54-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+attachment/5370123/+files/bluez_5.54-0ubuntu1.debian.tar.xz ** Attachment removed: "bluez_5.54-0ubuntu1.debian.tar.xz" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+attachment/5368222/+files/bluez_5.54-0ubuntu1.debian.tar.xz -- 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/1877536 Title: BlueZ 5.54 release Status in bluez package in Ubuntu: In Progress Bug description: Release BlueZ 5.54 to groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877536/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
Here's the part that looks important; the whole dmesg is in the attachment. Thanks [ 761.730488] dnone_free_ramge: nblks = 0, trunc = 1, len = 18446744073709551615, blkshift = 0 [ 761.730542] dnode_free_range: nblks == 0, len == 18446744073709551615 , off=0 [ 761.730543] range_tree_clear: size == 0 [ 761.730605] VERIFY(size != 0) failed [ 761.730625] PANIC at range_tree.c:307:range_tree_find_impl() [ 761.730653] Showing stack for process 23913 [ 761.730656] CPU: 31 PID: 23913 Comm: receive_writer Tainted: P OE 4.15.0-99-generic #100-Ubuntu [ 761.730657] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 761.730658] Call Trace: [ 761.730668] dump_stack+0x6d/0x8e [ 761.730679] spl_dumpstack+0x42/0x50 [spl] [ 761.730684] spl_panic+0xc8/0x110 [spl] [ 761.730690] ? fbcon_cursor+0x13e/0x1c0 [ 761.730695] ? atomic_notifier_call_chain+0x1a/0x20 [ 761.730700] ? vt_console_print+0x240/0x410 [ 761.730705] ? up+0x32/0x50 [ 761.730708] ? console_unlock+0x2a1/0x560 [ 761.730767] range_tree_find_impl+0x88/0x90 [zfs] [ 761.730769] ? printk+0x52/0x6e [ 761.730810] range_tree_clear+0x54/0x70 [zfs] [ 761.730843] dnode_free_range+0x15b/0x720 [zfs] [ 761.730874] dmu_object_free+0x75/0xc0 [zfs] [ 761.730904] dmu_free_long_object+0x9f/0xc0 [zfs] [ 761.730934] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 761.730963] receive_writer_thread+0x6d2/0xa60 [zfs] [ 761.730965] ? set_curr_task_fair+0x2b/0x60 [ 761.730970] ? spl_kmem_free+0x33/0x40 [spl] [ 761.730973] ? kfree+0x162/0x180 [ 761.731001] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 761.731006] thread_generic_wrapper+0x74/0x90 [spl] [ 761.731008] kthread+0x121/0x140 [ 761.731012] ? __thread_exit+0x20/0x20 [spl] [ 761.731014] ? kthread_create_worker_on_cpu+0x70/0x70 [ 761.731018] ret_from_fork+0x35/0x40 [ 967.430681] INFO: task txg_quiesce:4049 blocked for more than 120 seconds. [ 967.430739] Tainted: P OE4.15.0-99-generic #100-Ubuntu [ 967.430785] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.430836] txg_quiesce D0 4049 2 0x8000 [ 967.430840] Call Trace: [ 967.430853] __schedule+0x24e/0x880 [ 967.430858] schedule+0x2c/0x80 [ 967.430875] cv_wait_common+0x11e/0x140 [spl] [ 967.430885] ? wait_woken+0x80/0x80 [ 967.430893] __cv_wait+0x15/0x20 [spl] [ 967.431010] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.431078] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.431088] thread_generic_wrapper+0x74/0x90 [spl] [ 967.431093] kthread+0x121/0x140 [ 967.431099] ? __thread_exit+0x20/0x20 [spl] [ 967.431102] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.431107] ret_from_fork+0x35/0x40 [ 967.431140] INFO: task zfs:23834 blocked for more than 120 seconds. [ 967.431184] Tainted: P OE4.15.0-99-generic #100-Ubuntu [ 967.431229] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.431279] zfs D0 23834 23831 0x8080 [ 967.431282] Call Trace: [ 967.431286] __schedule+0x24e/0x880 [ 967.431290] schedule+0x2c/0x80 [ 967.431298] cv_wait_common+0x11e/0x140 [spl] [ 967.431303] ? wait_woken+0x80/0x80 [ 967.431310] __cv_wait+0x15/0x20 [spl] [ 967.431367] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.431438] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.431487] ? dbuf_rele+0x36/0x40 [zfs] [ 967.431555] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.431564] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.431571] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.431584] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.431590] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.431596] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.431660] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.431672] do_vfs_ioctl+0xa8/0x630 [ 967.431677] ? __audit_syscall_entry+0xbc/0x110 [ 967.431682] ? syscall_trace_enter+0x1da/0x2d0 [ 967.431685] SyS_ioctl+0x79/0x90 [ 967.431688] do_syscall_64+0x73/0x130 [ 967.431693] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 967.431696] RIP: 0033:0x7f4c273385d7 [ 967.431698] RSP: 002b:7ffed780e068 EFLAGS: 0246 ORIG_RAX: 0010 [ 967.431701] RAX: ffda RBX: 5a46 RCX: 7f4c273385d7 [ 967.431702] RDX: 7ffed780e080 RSI: 5a46 RDI: 0006 [ 967.431704] RBP: 7ffed780e080 R08: 7f4c2760de20 R09: [ 967.431705] R10: 55dc5929b010 R11: 0246 R12: 7ffed78116b0 [ 967.431707] R13: 0006 R14: 55dc592a2f10 R15: 000c [ 967.431722] INFO: task receive_writer:23913 blocked for more than 120 seconds. [ 967.431771] Tainted: P OE4.15.0-99-generic #100-Ubuntu [ 967.431816] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.431867] receive_writer D0 23913 2 0x8080 [ 967.431870] Call Trace: [ 967.431874] __schedule+0x24e/0x880 [
[Kernel-packages] [Bug 1877958] Re: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877958 Title: Do not treat unresolved test case in ftrace from ubuntu_kernel_selftests as failure Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: There are some test cases in ftrace from ubuntu_kernel_selftests that would need some kernel configs to be enabled. bug 1869347 bug 1869349 bug 1869349 We should not treat unresolved test case as a failure, as it's expected to fail with no correlated configs enabeled. https://github.com/torvalds/linux/commit/b730d668138cb3dd9ce78f8003986d1adae5523a #diff-33d74da785cbc5da20f71eb1af106d68 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1877958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878059] Re: ALC892 audio device not reachable after wake up
** Summary changed: - Audio device not reachable after wake up + ALC892 audio device not reachable after wake up ** Tags added: focal suspend-resume -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878059 Title: ALC892 audio device not reachable after wake up Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877871] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877932] Re: Bluetooth not connecting to last paired device when enabling bluetooth
** Package changed: pulseaudio (Ubuntu) => bluez (Ubuntu) ** Summary changed: - Bluetooth not connecting to last paired device when enabling bluetooth + Bluetooth not connecting to last paired device (Anker headset) when enabling bluetooth ** Changed in: bluez (Ubuntu) Status: Incomplete => New -- 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/1877932 Title: Bluetooth not connecting to last paired device (Anker headset) when enabling bluetooth Status in bluez package in Ubuntu: New Bug description: I am using a Dell Lattitude E7470 laptop. I am trying to connect a Bluetooth headset (Anker). I am seeing this issue with the latest upgrade to the Ubuntu 20.04 LTS version. I have a Bluetooth headset which is paired with the machine. Given the Bluetooth is enabled in the Ubuntu machine and I switch on my Bluetooth headset, the ubuntu machine does not automatically connect to this device anymore. It used to do it very easily with 18.04,19.04 and 19.10 ubuntu version. I have to do a variety of steps to get it connected: * turn off and on the headset. * turn off and on the laptop bluetooth. * try manully connecting to the device from the setting menu multiple times. * Sometimes it detects and get connected automatically as it should. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 2220 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 19:42:46 2020 InstallationDate: Installed on 2019-02-21 (444 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to focal on 2020-04-27 (13 days ago) dmi.bios.date: 10/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.8 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1877932/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877871] Re: X windows hnags following upgrade from 18.04 to 20.04
Thanks for the bug report. The log in comment #2 shows lots of radeon kernel errors so I am moving this bug to the kernel. ** Tags added: radeon ** Summary changed: - X windows hnags following upgrade from 18.04 to 20.04 + [radeon] X windows hangs following upgrade from 18.04 to 20.04 ** Package changed: xorg (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877871 Title: [radeon] X windows hangs following upgrade from 18.04 to 20.04 Status in linux package in Ubuntu: New Bug description: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877871/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877932] [NEW] Bluetooth not connecting to last paired device when enabling bluetooth
You have been subscribed to a public bug: I am using a Dell Lattitude E7470 laptop. I am trying to connect a Bluetooth headset (Anker). I am seeing this issue with the latest upgrade to the Ubuntu 20.04 LTS version. I have a Bluetooth headset which is paired with the machine. Given the Bluetooth is enabled in the Ubuntu machine and I switch on my Bluetooth headset, the ubuntu machine does not automatically connect to this device anymore. It used to do it very easily with 18.04,19.04 and 19.10 ubuntu version. I have to do a variety of steps to get it connected: * turn off and on the headset. * turn off and on the laptop bluetooth. * try manully connecting to the device from the setting menu multiple times. * Sometimes it detects and get connected automatically as it should. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: justin 2220 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 19:42:46 2020 InstallationDate: Installed on 2019-02-21 (444 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) PackageArchitecture: all ProcEnviron: LANGUAGE=en_GB:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_GB.UTF-8 SHELL=/usr/bin/zsh SourcePackage: alsa-driver Symptom: audio Title: Bluetooth sound card not detected UpgradeStatus: Upgraded to focal on 2020-04-27 (13 days ago) dmi.bios.date: 10/08/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.22.8 dmi.board.name: 0T6HHJ dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.22.8:bd10/08/2019:svnDellInc.:pnLatitudeE7470:pvr:rvnDellInc.:rn0T6HHJ:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: Latitude dmi.product.name: Latitude E7470 dmi.product.sku: 06DC dmi.sys.vendor: Dell Inc. ** Affects: bluez (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug focal -- Bluetooth not connecting to last paired device when enabling bluetooth https://bugs.launchpad.net/bugs/1877932 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez 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 1877871] [NEW] [radeon] X windows hangs following upgrade from 18.04 to 20.04
You have been subscribed to a public bug: Following an upgrade from 18.04 to 20.04 when I boot, X windows comes to a point where I get a white background with a bunch of colored dots. Nothing progresses from there. I can boot successfully by pressing escape after booting, going to advanced options, booting to 5.4.0-29 recovery mode. When that menu appears, I select "root". I press Enter for maintenance. When the root prompt appears I immediately type EXIT to return to the menu and then RESUME followed by OK. The system then starts the desktop properly. I would be happy to provide boot logs and/or Xorg.0.logs if desired. It appears to me that there are out of memory errors occurring along with some addressing issues. I am on an HP EliteBook 8570w laptop 15.6 G memory. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 10:22:37 2020 EcryptfsInUse: Yes InstallationDate: Installed on 2018-09-22 (595 days ago) InstallationMedia: Ubuntu 16.04.5 LTS "Xenial Xerus" - Release amd64 (20180731) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) VarLogDistupgradeAptlog: Log time: 2020-05-09 09:07:41.355959 Starting pkgProblemResolver with broken count: 0 Starting 2 pkgProblemResolver with broken count: 0 Done None ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade focal radeon -- [radeon] X windows hangs following upgrade from 18.04 to 20.04 https://bugs.launchpad.net/bugs/1877871 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 1877655] Re: [Dell Venue 11 Pro 7140] Trackpad does not work in Xorg sessions
Since you said the trackpad works in Wayland until you run Software Center, please: 1. Log into 'Ubuntu on Wayland'. 2. Make sure the trackpad works. 3. Open a Terminal and run: dmesg -w Leave it running but tap Enter several times to make some blank lines. 4. Open Software Centre. 5. Does the Terminal window now show any new messages? ** Summary changed: - Synaptic Trackpad does not work in Xorg sessions + [Dell Venue 11 Pro 7140] Trackpad does not work in Xorg sessions ** Package changed: xorg-server (Ubuntu) => linux (Ubuntu) ** Summary changed: - [Dell Venue 11 Pro 7140] Trackpad does not work in Xorg sessions + [Dell Venue 11 Pro 7140] Trackpad does not work -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877655 Title: [Dell Venue 11 Pro 7140] Trackpad does not work Status in libinput package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri:
[Kernel-packages] [Bug 1854485] Re: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series
Hi Alberto, can I use lutris/fortnite wil my NVIDIA 340.108 on ubuntu? I have failed the first time since the Volkan version was not updated. Thanks. Regards, Pietro -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1854485 Title: Introduce the new NVIDIA 440 series, and add 5.4 Linux compatibility to the 340 and 390 series Status in linux package in Ubuntu: Triaged Status in linux-restricted-modules package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-340 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-390 package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-440 package in Ubuntu: Fix Released Status in nvidia-settings package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Status in linux-restricted-modules source package in Bionic: Fix Released Status in nvidia-graphics-drivers-340 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-390 source package in Bionic: Fix Released Status in nvidia-graphics-drivers-440 source package in Bionic: Fix Released Status in nvidia-settings source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-restricted-modules source package in Eoan: Fix Released Status in nvidia-graphics-drivers-340 source package in Eoan: New Status in nvidia-graphics-drivers-390 source package in Eoan: Fix Released Status in nvidia-graphics-drivers-440 source package in Eoan: Fix Released Status in nvidia-settings source package in Eoan: Fix Released Bug description: [Impact] These releases provide both bug fixes and new features, and we would like to make sure all of our users have access to these improvements. See the changelog entry below for a full list of changes and bugs. [Test Case] The following development and SRU process was followed: https://wiki.ubuntu.com/NVidiaUpdates Certification test suite must pass on a range of hardware: https://git.launchpad.net/plainbox-provider-sru/tree/units/sru.pxu The QA team that executed the tests will be in charge of attaching the artifacts and console output of the appropriate run to the bug. nVidia maintainers team members will not mark ‘verification-done’ until this has happened. [Regression Potential] In order to mitigate the regression potential, the results of the aforementioned system level tests are attached to this bug. [Discussion] 440.40: * New upstream release: - Added support for the following GPU: Quadro T2000 with Max-Q Design - Added support for the __GL_SYNC_DISPLAY_DEVICE environment variable for Vulkan applications. - Fixed a bug that caused applications running directly on a display (such as VR HMDs) to tear when a G-SYNC or G-SYNC Compatible monitor is plugged in the system. - Fixed a bug in an error handling path that could cause a kernel crash while loading nvidia.ko. - Fixed driver installation failure on Oracle Linux 7.7 systems, where the NVIDIA kernel module failed to build with error "unknown type name 'vm_fault_t'". * Changes from the 440.36 series: - Added support for the following GPUs: o GeForce GTX 1650 SUPER o GeForce GTX 1660 SUPER - Fixed graphical corruption that can occur when using glslang SPIR-V Generator Version <= 2. - Fixed a bug that could cause the X server to crash when running applications using GLX indirect rendering. - Updated the Module.symvers sanity check, which is part of the NVIDIA kernel module build process, to accommodate the recent addition of a new field in the Module.symvers file format. This fixes the error "The Module.symvers file is missing [...]" seen during driver installation or DKMS rebuilds with Linux 5.4 RC kernels. - Fixed kernel module build problems with Linux kernel 5.4.0 release candidates. - Updated nvidia-bug-report.sh to collect information about X server crashes from coredumpctl, when available. - Updated the nvidia-drm kernel module for compatibility with the removal of the DRIVER_PRIME flag in recent Linux kernel versions. - Enabled parallel GLSL shader linking by default; i.e., allow GL_ARB_parallel_shader_compile to work without first calling glMaxShaderCompilerThreadsARB(). - Added support for HDMI 2.1 variable refresh rate (VRR) G-SYNC Compatible monitors on supported GPUs.For more details, see "Configuring Multiple Display Devices on One X Screen" in the README. Added support for the GLX_NV_multigpu_context and GL_NV_gpu_multicast extensions.For more details, see the "Configuring SLI and Multi-GPU FrameRendering"
[Kernel-packages] [Bug 1877655] [NEW] [Dell Venue 11 Pro 7140] Trackpad does not work in Xorg sessions
You have been subscribed to a public bug: I have a Dell Venue Pro 7140 with the keyboard/trackpad/extra battery dock. PopOS 20.04 fully updated. I have experienced this bug on stock Ubuntu 20.04 as well as Kubuntu 20.04. When at the login page, the trackpad and keyboard operate as they should. Once the login process is complete and the desktop is displayed, the keyboard still works as expected but the trackpad no longer controls the pointer. The touch display still functions as expected but the trackpad on the keyboard dock doesn't work. The attached document is my device list, here is the evtest: Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x6cb product 0x2819 version 0x111 Input device name: "Synaptics T Pad V 01.31 Touchpad" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 272 (BTN_LEFT) Event code 325 (BTN_TOOL_FINGER) Event code 330 (BTN_TOUCH) Event code 333 (BTN_TOOL_DOUBLETAP) Event code 334 (BTN_TOOL_TRIPLETAP) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value483 Min0 Max 1056 Resolution 12 Event code 1 (ABS_Y) Value266 Min0 Max 516 Resolution 12 Event code 47 (ABS_MT_SLOT) Value 0 Min0 Max2 Event code 53 (ABS_MT_POSITION_X) Value 0 Min0 Max 1056 Resolution 12 Event code 54 (ABS_MT_POSITION_Y) Value 0 Min0 Max 516 Resolution 12 Event code 55 (ABS_MT_TOOL_TYPE) Value 0 Min0 Max2 Event code 57 (ABS_MT_TRACKING_ID) Value 0 Min0 Max65535 Event type 4 (EV_MSC) Event code 5 (MSC_TIMESTAMP) Properties: Property type 0 (INPUT_PROP_POINTER) Property type 2 (INPUT_PROP_BUTTONPAD) Testing ... (interrupt to exit) I did try to remove xserver-xorg-input-synaptics, but it is not installed on 20.04. There is still an issue with Wayland and the trackpad, but it's different than Xorg so the problem may be in how Xorg is processing the trackpad (I honestly don't know) - in Wayland, it will work until I attempt to run the sofware center. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None DistUpgraded: Fresh install DistroCodename: focal DistroRelease: Pop!_OS 20.04 DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation HD Graphics 5300 [8086:161e] (rev 09) (prog-if 00 [VGA controller]) Subsystem: Dell HD Graphics 5300 [1028:066b] MachineType: Dell Inc. Venue 11 Pro 7140 Package: xorg-server (not installed) ProcKernelCmdLine: initrd=\EFI\Pop_OS-70755969-68c4-4da9-982b-a38628a19db0\initrd.img root=UUID=70755969-68c4-4da9-982b-a38628a19db0 ro quiet loglevel=0 systemd.show_status=false splash ProcVersionSignature: Ubuntu 5.4.0-7626.30~1588169883~20.04~bbe668a-generic 5.4.30 Tags: focal ubuntu ubuntu Uname: Linux 5.4.0-7626-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/10/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A17 dmi.board.name: 0XMVMH dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA17:bd09/10/2018:svnDellInc.:pnVenue11Pro7140:pvr:rvnDellInc.:rn0XMVMH:rvrA00:cvnDellInc.:ct8:cvr: dmi.product.name: Venue 11 Pro 7140 dmi.product.sku: 066B dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 ** Affects: libinput (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: apport-collected bot-comment focal ubuntu -- [Dell Venue 11 Pro 7140] Trackpad does not work in Xorg sessions https://bugs.launchpad.net/bugs/1877655 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 1876369] Re: [nouveau] garbled/frozen screen after waking from sleep mode
Thanks. Since there's nothing identifiable on that screen it seems like a kernel issue. Not the mutter issue I was thinking of. Please: 1. Reproduce the bug. 2. Reboot. 3. Run: journalctl -b-1 > prevboot.txt and attach the resulting text file here. ** Package changed: mutter (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876369 Title: [nouveau] garbled/frozen screen after waking from sleep mode Status in linux package in Ubuntu: Incomplete Bug description: Computer boots and runs normally until it goes into sleep mode. wehen trying to wake from sleep mode, screen is filled with what looks like frozen static on an old TV, then it locks up. I have to force power- off the computer and reboot to make it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 1 14:45:37 2020 DistUpgraded: 2020-04-28 09:50:34,578 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96CM [GeForce 9650M GT] [10de:064c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96CM [GeForce 9650M GT] [1043:1912] InstallationDate: Installed on 2018-04-28 (734 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d4a14cd2-2bf0-4a55-a605-f421a799c4eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 1 14:38:54 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1876369/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876369] [NEW] [nouveau] garbled/frozen screen after waking from sleep mode
You have been subscribed to a public bug: Computer boots and runs normally until it goes into sleep mode. wehen trying to wake from sleep mode, screen is filled with what looks like frozen static on an old TV, then it locks up. I have to force power-off the computer and reboot to make it work again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: compiz CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0' CompositorUnredirectFSW: true CurrentDesktop: Unity:Unity7:ubuntu Date: Fri May 1 14:45:37 2020 DistUpgraded: 2020-04-28 09:50:34,578 ERROR got error from PostInstallScript ./xorg_fix_proprietary.py (g-exec-error-quark: Failed to execute child process “./xorg_fix_proprietary.py” (No such file or directory) (8)) DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation G96CM [GeForce 9650M GT] [10de:064c] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. G96CM [GeForce 9650M GT] [1043:1912] InstallationDate: Installed on 2018-04-28 (734 days ago) InstallationMedia: Ubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) MachineType: ASUSTeK Computer Inc. M70Vn ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d4a14cd2-2bf0-4a55-a605-f421a799c4eb ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 12/21/2009 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 206 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: M70Vn dmi.board.vendor: ASUSTeK Computer Inc. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK Computer Inc. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr206:bd12/21/2009:svnASUSTeKComputerInc.:pnM70Vn:pvr1.0:rvnASUSTeKComputerInc.:rnM70Vn:rvr1.0:cvnASUSTeKComputerInc.:ct10:cvr1.0: dmi.product.name: M70Vn dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK Computer Inc. version.compiz: compiz 1:0.9.14.1+20.04.20200211-0ubuntu1 version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.4-2ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.6-1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 xserver.bootTime: Fri May 1 14:38:54 2020 xserver.configfile: default xserver.errors: xserver.logfile: /var/log/Xorg.0.log xserver.version: 2:1.20.8-2ubuntu2 xserver.video_driver: modeset ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 apport-bug compiz-0.9 focal nouveau ubuntu -- [nouveau] garbled/frozen screen after waking from sleep mode https://bugs.launchpad.net/bugs/1876369 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 1870189] Re: initramfs does not get loaded
Thanks for the information @vorlon. I think that makes sense. What would be the solution for booting focal-server-cloudimg-amd64.img with libvirt (virt-install) (so, not on Azure, as the OP was; so, I think the issue is now fractured into two separate issues with same underlying cause)? Thanks. -- 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/1870189 Title: initramfs does not get loaded Status in grub2 package in Ubuntu: Won't Fix Status in linux-azure package in Ubuntu: Confirmed Bug description: A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by “do-release-upgrade –d”. Then the latest Ubuntu v5.6 kernel was installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a reboot was performed, a panic with the v5.6 kernel occured because the rootfs can not be found. It turns out by default, initramfs does not get loaded: /boot/grub/grub.cfg: menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3d2737e8- b95a-42bf-bac1-bb6fb4cda87f' { … if [ "${initrdfail}" = 1 ]; then linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic initrd/boot/initrd.img-5.6.0-050600-generic else linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic panic=-1 #Dexuan: here the initrd line is missing! fi initrdfail } As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit the “fail to mount rootfs” panic and the kernel will automatically reboot…. Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots for the 2nd time, the kernel should successfully boot up. Next, when the kernel boots for the 3rd time, it panics again since the userspace program resets initrdfail to 0, and next time when the kernel boots, it can boot up successfully -- this “panic/success/panic/success” pattern repeats forever… The linux-azure kernels are not affected since they have the vmbus driver and storage drivers built-in (i.e. “=y”): /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m The v5.6 kernel uses =m rather than =y, so is affected here. It looks the setting may be intentional, but we should not assume a customer kernel must have the necessary vmbus/storage drivers built-in. This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 19.04 as well?) on Azure. We installed a Ubuntu 20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1826403] Re: Ethernet won't connect when cable is plugged in at boot
This is now resolved on my system. Thanks for following up. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1826403 Title: Ethernet won't connect when cable is plugged in at boot Status in linux package in Ubuntu: Incomplete Bug description: When booting Ubuntu 19.04 with the Ethernet cable plugged in, after boot, network manager won't connect. Unplugging and plugging back in the cable with the system running doesn't work to establish a connection. The workaround is to boot with the cable unplugged, then to plug it in after boot. This problem emerged immediately following an upgrade from 18.10 to 19.04. On the first boot networking was fine, but from the first reboot a networking connection through the Ethernet cable couldn't be established if the cable was plugged in at boot. This issue is also described here: https://askubuntu.com/questions/1135412/updated-to-19-04-and-no- ethernet-now/1135726#1135726 and here: https://ubuntu- mate.community/t/19-04-ethernet-wired-connection-refuses-to-connect- when-plugged-in-before-boot/19333/6 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: network-manager 1.16.0-0ubuntu2 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Apr 25 21:50:27 2019 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto enp4s0f1 auto lo iface lo inet loopback InstallationDate: Installed on 2018-11-23 (153 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.11.1 dev enp4s0f1 proto dhcp metric 100 169.254.0.0/16 dev enp4s0f1 scope link metric 1000 192.168.11.0/24 dev enp4s0f1 proto kernel scope link src 192.168.11.13 metric 100 NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=false WWANEnabled=true SourcePackage: network-manager UpgradeStatus: Upgraded to disco on 2019-04-25 (0 days ago) mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2019-04-25T20:03:28.380204 nmcli-dev: DEVICETYPE STATEIP4-CONNECTIVITY IP6-CONNECTIVITY DBUS-PATH CONNECTIONCON-UUID CON-PATH enp4s0f1 ethernet connectedfull limited /org/freedesktop/NetworkManager/Devices/2 Automatic connection e906293b-df71-435b-8909-7d88ca006540 /org/freedesktop/NetworkManager/ActiveConnection/1 wlp3s0wifi unavailable limited limited /org/freedesktop/NetworkManager/Devices/3 ---- -- loloopback unmanagedunknown unknown /org/freedesktop/NetworkManager/Devices/1 ---- -- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.16.0 connected started full enabled enabled disabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826403/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Yes, the design here is that, since we provide custom kernels for our cloud partners which have all the drivers needed to boot built in, loading an initrd is a waste of time at boot. If someone is using a kernel other than the one we provide for the cloud, or in the case of a bug, the system will still boot (slower) after a panic and a reboot to try again with the initrd. Removing this functionality would be a pessimization. The vast majority of Ubuntu instances in Azure are expected to be booted with the provided linux-azure kernel, which does not require an initrd. Canonical does not support the use of other kernels on Azure. And if someone needs to use a different kernel on an instance without the double-boot process, they can edit the /etc/default/grub.d/40-force-partuuid.cfg config file that is provided with the image at the same time they are installing the different kernel to get the previous behavior. ** Changed in: grub2 (Ubuntu) Status: Confirmed => Won't Fix -- 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/1870189 Title: initramfs does not get loaded Status in grub2 package in Ubuntu: Won't Fix Status in linux-azure package in Ubuntu: Confirmed Bug description: A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by “do-release-upgrade –d”. Then the latest Ubuntu v5.6 kernel was installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a reboot was performed, a panic with the v5.6 kernel occured because the rootfs can not be found. It turns out by default, initramfs does not get loaded: /boot/grub/grub.cfg: menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3d2737e8- b95a-42bf-bac1-bb6fb4cda87f' { … if [ "${initrdfail}" = 1 ]; then linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic initrd/boot/initrd.img-5.6.0-050600-generic else linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic panic=-1 #Dexuan: here the initrd line is missing! fi initrdfail } As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit the “fail to mount rootfs” panic and the kernel will automatically reboot…. Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots for the 2nd time, the kernel should successfully boot up. Next, when the kernel boots for the 3rd time, it panics again since the userspace program resets initrdfail to 0, and next time when the kernel boots, it can boot up successfully -- this “panic/success/panic/success” pattern repeats forever… The linux-azure kernels are not affected since they have the vmbus driver and storage drivers built-in (i.e. “=y”): /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m The v5.6 kernel uses =m rather than =y, so is affected here. It looks the setting may be intentional, but we should not assume a customer kernel must have the necessary vmbus/storage drivers built-in. This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 19.04 as well?) on Azure. We installed a Ubuntu 20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878059] Re: Audio device not reachable after wake up
The kernel's log snipped... ** Attachment added: "kernel_censored.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878059/+attachment/5370110/+files/kernel_censored.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878059 Title: Audio device not reachable after wake up Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878059] Re: Audio device not reachable after wake up
It is hard to reproduce this situation, because it only occurs sometimes I noticed. Can I call the 'apport-collect 1878059' more often (until this behaviour occurs)? If not - I'll attach a kernel's log between a 'systemctl suspend' and playing sounds at the wrong device. I hope this helps for now. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878059 Title: Audio device not reachable after wake up Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
> In my case, it's not even my system though: it's Canonical's system; It's a fresh download of a cloudimg from https://cloud- images.ubuntu.com/focal/ which has the issue, so it can't because I didn't build the image right, because I didn't build the image at all. that's correct, you didn't do anything wrong; the cloud-images for focal have the /etc/default/grub.d/40-force-partuuid.cfg file built-in. > So how would this be able to help? What is the rationale behind the new initrdfail design and 40-force-partuuid.cfg? Thanks. I'm not sure what the original rationale was, as I wasn't involved in those discussions, although my rough understanding is it's intended to try to speed up boot time. @vorlon may know more about the reason behind it. -- 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/1870189 Title: initramfs does not get loaded Status in grub2 package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Bug description: A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by “do-release-upgrade –d”. Then the latest Ubuntu v5.6 kernel was installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a reboot was performed, a panic with the v5.6 kernel occured because the rootfs can not be found. It turns out by default, initramfs does not get loaded: /boot/grub/grub.cfg: menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3d2737e8- b95a-42bf-bac1-bb6fb4cda87f' { … if [ "${initrdfail}" = 1 ]; then linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic initrd/boot/initrd.img-5.6.0-050600-generic else linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic panic=-1 #Dexuan: here the initrd line is missing! fi initrdfail } As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit the “fail to mount rootfs” panic and the kernel will automatically reboot…. Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots for the 2nd time, the kernel should successfully boot up. Next, when the kernel boots for the 3rd time, it panics again since the userspace program resets initrdfail to 0, and next time when the kernel boots, it can boot up successfully -- this “panic/success/panic/success” pattern repeats forever… The linux-azure kernels are not affected since they have the vmbus driver and storage drivers built-in (i.e. “=y”): /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m The v5.6 kernel uses =m rather than =y, so is affected here. It looks the setting may be intentional, but we should not assume a customer kernel must have the necessary vmbus/storage drivers built-in. This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 19.04 as well?) on Azure. We installed a Ubuntu 20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1208993] Re: Ubuntu slows down and hangs while copying file from/to USB
My day was saved by #107 comment, I tried everything mentioned in this issue, and always get a lagged mouse!, mi machine es a laptop lenovo L480 12GB RAM, with SSD ( a very capable machine), after I deactivate my swap partition (20GB) (swapoff -a) my system starts working as a champ, thanks @peterrus (petorrus)! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1208993 Title: Ubuntu slows down and hangs while copying file from/to USB Status in linux package in Ubuntu: Confirmed Bug description: Hi While copying many and large files to and from a USB drive, the system becomes incredibly slow and sometimes hangs. I watched the system monitor while it was running slowly but cpu was not above 50% at any time, the same for memory. I'm using the "WD my passport" HD with a USB3 port of my "ASUS K55VD" laptop. Description: Ubuntu 13.04 Release: 13.04 nautilus: Installed: 1:3.6.3-0ubuntu16 Candidate: 1:3.6.3-0ubuntu16 Version table: *** 1:3.6.3-0ubuntu16 0 500 http://ubuntu-archive.mirror.nucleus.be/ raring/main amd64 Packages 100 /var/lib/dpkg/status Steps to reproduce: 1) Aquire many large files (like your totally legit moviecollection) 2) Copy files to external HD 3) Open your browser and be sad when your system becomes incredibly slow after a few minutes This is my first bugreport so if I'm missing something, please tell me. ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: nautilus 1:3.6.3-0ubuntu16 ProcVersionSignature: Ubuntu 3.8.0-27.40-generic 3.8.13.4 Uname: Linux 3.8.0-27-generic x86_64 ApportVersion: 2.9.2-0ubuntu8.1 Architecture: amd64 Date: Tue Aug 6 22:56:34 2013 EcryptfsInUse: Yes ExecutablePath: /usr/bin/nautilus GsettingsChanges: b'org.gnome.nautilus.window-state' b'geometry' b"'656x715+154+151'" b'org.gnome.nautilus.window-state' b'maximized' b'true' InstallationDate: Installed on 2013-05-31 (67 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64 (20130424) MarkForUpload: True SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1208993/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872863] Re: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module
I have confirmed that the fix in -proposed fixes the issue for me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872863 Title: QEMU/KVM display is garbled when booting from kernel EFI stub due to missing bochs-drm module Status in kmod package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Status in kmod source package in Bionic: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: BugLink: https://bugs.launchpad.net/bugs/1872863 [Impact] A recent grub2 SRU, LP #1864533, now forces the kernel to boot via the kernel EFI stub whenever EFI is enabled. This causes problems for QEMU/KVM virtual machines which use the VGA=std video device, as the efifb driver yields an unreadable garbled screen. See the attached image. The correct framebuffer driver to use in this situation is bochs-drm, and modprobing it from a HWE kernel fixes the issues. bochs-drm is missing from Bionic since CONFIG_DRM_BOCHS was disabled in LP #1378648 due to bochs-drm causing problems in a PowerKVM machine. This problem appears to be fixed now, and bochs-drm has been re-enabled for Disco and up, in LP #1795857 and has been proven safe. This has also come up again in LP #1823152, as well as chatter on LP #1795857 to get this enabled on Bionic. The customer which is experiencing this issue cannot switch to VGA=qxl as a workaround, and must use VGA=std, hence I suggest we re-enable bochs-drm for Bionic. [Fix] I noticed on Focal, if you boot, the framebuffer is initially efifb: [ 0.603716] efifb: probing for efifb [ 0.603733] efifb: framebuffer at 0xc000, using 1876k, total 1875k [ 0.603735] efifb: mode is 800x600x32, linelength=3200, pages=1 [ 0.603736] efifb: scrolling: redraw [ 0.603738] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0 [ 0.604462] Console: switching to colour frame buffer device 100x37 [ 0.605829] fb0: EFI VGA frame buffer device This soon changes to bochs-drm about a second later: [ 0.935988] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 0: 0xc000 -> 0xc0ff [ 0.937023] bochs-drm :00:01.0: remove_conflicting_pci_framebuffers: bar 2: 0xc1c8c000 -> 0xc1c8cfff [ 0.937776] checking generic (c000 1d5000) vs hw (c000 100) [ 0.937776] fb0: switching to bochsdrmfb from EFI VGA [ 0.939085] Console: switching to colour dummy device 80x25 [ 0.939117] bochs-drm :00:01.0: vgaarb: deactivate vga console [ 0.939210] [drm] Found bochs VGA, ID 0xb0c5. [ 0.939212] [drm] Framebuffer size 16384 kB @ 0xc000, mmio @ 0xc1c8c000. [ 0.941955] lpc_ich :00:1f.0: I/O space for GPIO uninitialized [ 0.942069] [TTM] Zone kernel: Available graphics memory: 2006780 KiB [ 0.942081] [TTM] Initializing pool allocator [ 0.942089] [TTM] Initializing DMA pool allocator [ 0.943026] virtio_blk virtio2: [vda] 20971520 512-byte logical blocks (10.7 GB/10.0 GiB) [ 0.944019] [drm] Found EDID data blob. [ 0.944162] [drm] Initialized bochs-drm 1.0.0 20130925 for :00:01.0 on minor 0 [ 0.944979] fbcon: bochs-drmdrmfb (fb0) is primary device [ 0.947712] Console: switching to colour frame buffer device 128x48 On bionic, the framebuffer never changes from efifb, since the bochs- drm kernel module is not built, and it is also present on the module banlist in /etc/modprobe.d/blacklist-framebuffer.conf bochs-drm needs to be enabled to be built in the kernel config, and removed from the module blacklist in kmod. [Testcase] Create a new QEMU/KVM virtual machine, I used virt-manager. Before you install the OS, check the box to modify settings before install. In the "Overview" tab, enable EFI by setting the firmware to "UEFI x86_64: /usr/share/OVMF/OVMF_CODE.secboot.fd". Set the video device to qxl while you install Bionic. Once the install is done, reboot, do a "apt update" and "apt upgrade", to ensure you have grub2 2.02-2ubuntu8.15 installed. Shut the VM down, and set the video device to VGA. Or VGA=std if you use the QEMU command line. Start the VM up, and the screen will be garbled. See attached picture. If you install my test packages, which are available here: https://launchpad.net/~mruffell/+archive/ubuntu/sf272653-test Instructions to install (on a bionic system): 1) Enable bionic-proposed 2) sudo apt-get update 3) sudo apt install linux-image-unsigned-4.15.0-96-generic linux-modules-4.15.0-96-generic linux-modules-extra-4.15.0-96-generic linux-headers-4.15.0-96-generic linux-headers-4.15.0-96 libkmod2 kmod 4) sudo reboot 5) uname -rv 4.15.0-96-generic #97+TEST272653v20200409b1-Ubuntu SMP Thu Apr 9 04:09:18 UTC 2020 If you reboot, the screen will be perfectly readable, since the bochs- drm driver will be in use. [Regression Potential] We are enabling a
[Kernel-packages] [Bug 1872001] Re: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0
I had the issue with Mint cinnamon desktop running kernel 5.3.0-46-generic. Reverted back to 5.3.0-45-generic and it was resolved. I noticed it mostly when using Webstorm IDE, although I don't think it was specific to this application. Intermittent but very frequent. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872001 Title: 5.3.0-46-generic - i915 - frequent GPU hangs / resets rcs0 Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: Hi, Since update to HWE kernel 5.3.0-46-generic I am experiencing frequent (every couple of minutes) GPU hangs and reset manifesting as 2-3 seconds freezes of the GUI (other than the mouse pointer). No particular triggers identified although have Chrome / Chromium running with Hardware Acceleration enabled does appear to increase the frequency. I have seen incidences of these hangs in jounralctl output using previous kernels in the 5.3.0-xx series but they were very infrequent (one or twice in a week of daily usage) System Info steve@steve-Inspiron-5580:~$ inxi -SCGxxxz System:Host: steve-Inspiron-5580 Kernel: 5.3.0-46-generic x86_64 bits: 64 compiler: gcc v: 7.5.0 Desktop: Cinnamon 4.4.8 wm: muffin 4.4.2 dm: LightDM 1.26.0 Distro: Linux Mint 19.3 Tricia base: Ubuntu 18.04 bionic CPU: Topology: Quad Core model: Intel Core i5-8265U bits: 64 type: MT MCP arch: Kaby Lake rev: B L2 cache: 6144 KiB flags: avx avx2 lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 28800 Speed: 1173 MHz min/max: 400/3900 MHz Core speeds (MHz): 1: 800 2: 800 3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 Graphics: Device-1: Intel vendor: Dell driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:3ea0 Display: x11 server: X.Org 1.20.5 driver: modesetting unloaded: fbdev,vesa resolution: 1920x1080~60Hz OpenGL: renderer: Mesa DRI Intel UHD Graphics (Whiskey Lake 3x8 GT2) v: 4.5 Mesa 19.2.8 compat-v: 3.0 direct render: Yes steve@steve-Inspiron-5580:~$ journalctl -b | grep i915 Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: deactivate vga console Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) Apr 10 06:15:17 steve-Inspiron-5580 kernel: [drm] Initialized i915 1.6.0 20190619 for :00:02.0 on minor 0 Apr 10 06:15:17 steve-Inspiron-5580 kernel: fbcon: i915drmfb (fb0) is primary device Apr 10 06:15:17 steve-Inspiron-5580 kernel: i915 :00:02.0: fb0: i915drmfb frame buffer device Apr 10 06:15:17 steve-Inspiron-5580 kernel: snd_hda_intel :00:1f.3: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: GPU HANG: ecode 9:0:0x, hang on rcs0 Apr 10 06:16:28 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:31:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:37:48 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 Apr 10 06:40:46 steve-Inspiron-5580 kernel: i915 :00:02.0: Resetting rcs0 for hang on rcs0 I note another user has reported similar issues on the same kernel at https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861395/comments/52 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: steve 3920 F pulseaudio /dev/snd/pcmC0D0p: steve 3920 F...m pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.3 HibernationDevice: RESUME=none InstallationDate: Installed on 2019-12-27 (104 days ago) InstallationMedia: Linux Mint 19.3 "Tricia" - Release amd64 20191213 MachineType: Dell Inc. Inspiron 5580 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-46-generic root=UUID=b0eaa5bb-0276-42d4-938f-ee6ce1627906 ro usb_storage.quirks=0bc2:2320: quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-46.38~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-46-generic N/A linux-backports-modules-5.3.0-46-generic N/A linux-firmware1.173.17 Tags: tricia Uname: Linux 5.3.0-46-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 07/02/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version:
[Kernel-packages] [Bug 1854298] Re: ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in upstream testsuite
** Tags added: sru-20200427 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1854298 Title: ubuntu_unionmount_ovlfs failed on X/T-LTS-X with latest update in upstream testsuite Status in ubuntu-kernel-tests: Triaged Status in linux-signed package in Ubuntu: Confirmed Bug description: A bisect shows this test is failing since commit 2104e51db38 (Simplify initialization of __upper) The test will fail with: *** *** ./run --ov --ts=0 rmtree *** TEST rmtree.py:4: Recursive remove populated lower dir with lower files - rmtree /mnt/a/dir100 *** *** ./run --ov --ts=0 rmtree-new *** TEST rmtree-new.py:4: Recursive remove populated lower dir with new subdir ./run --mkdir /mnt/a/dir100/b 0755 - rmtree /mnt/a/dir100 *** *** ./run --ov --ts=0 hard-link *** TEST hard-link.py:10: Hard link file ./run --link /mnt/a/foo100 /mnt/a/no_foo100 stderr: /mnt/a/foo100: File unexpectedly on upper layer For the complete test log, please refer the attachment. HEAD now is 1724ef2 ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-169-generic 4.4.0-169.198 ProcVersionSignature: User Name 4.4.0-169.198-generic 4.4.197 Uname: Linux 4.4.0-169-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.21 Architecture: amd64 Date: Thu Nov 28 04:21:52 2019 SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1854298/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833028] Re: fanotify06 from ubuntu_ltp_syscalls failed
** Tags added: sru-20200427 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1833028 Title: fanotify06 from ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Confirmed Status in linux source package in Disco: Fix Released Bug description: == SRU Justification == fanotify06 test from ubuntu_ltp_syscalls reported that test #1 for overlayfs has received more than one expected event: <<>> tag=fanotify06 stime=1560747299 cmdline="fanotify06" contacts="" analysis=exit <<>> incrementing stop tst_device.c:231: INFO: Using test device LTP_DEV='/dev/loop2' tst_mkfs.c:90: INFO: Formatting /dev/loop2 with ext2 opts='' extra opts='' mke2fs 1.44.6 (5-Mar-2019) tst_test.c:1112: INFO: Timeout per run is 0h 05m 00s fanotify06.c:169: INFO: Test #0: Fanotify merge mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=1136 fd=15 fanotify06.c:230: PASS: group 8 got no event fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:208: FAIL: group 0 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 1 got more than one event (48 > 24) fanotify06.c:208: FAIL: group 2 got more than one event (48 > 24) fanotify06.c:220: FAIL: group 3 got event fanotify06.c:220: FAIL: group 4 got event fanotify06.c:220: FAIL: group 5 got event fanotify06.c:220: FAIL: group 6 got event fanotify06.c:220: FAIL: group 7 got event fanotify06.c:220: FAIL: group 8 got event Summary: passed 9 failed 9 skipped 0 warnings 0 This duplicated event was generated with operations on files with "fake" path. == Fix == * d9899030 (ovl: do not generate duplicate fsnotify events for "fake" path) This patch can be cherry-picked into Disco. Older kernels are not affected by this issue (without commit d1d04ef8) == Test == Test kernel could be found here: https://people.canonical.com/~phlin/kernel/lp-1833028-fanotify06-ovl/ Verified on a KVM node, the fanotify06 test will pass with this patched disco kernel: fanotify06.c:169: INFO: Test #1: Fanotify merge overlayfs mount mark fanotify06.c:147: PASS: group 0 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 1 got event: mask 2 pid=5997 fd=30 fanotify06.c:147: PASS: group 2 got event: mask 2 pid=5997 fd=30 fanotify06.c:230: PASS: group 3 got no event fanotify06.c:230: PASS: group 4 got no event fanotify06.c:230: PASS: group 5 got no event fanotify06.c:230: PASS: group 6 got no event fanotify06.c:230: PASS: group 7 got no event fanotify06.c:230: PASS: group 8 got no event == Regression Potential == Low, fix limited to the overlayfs and just corrects the flag behaviour with "fake" path. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-16-generic 5.0.0-16.17 ProcVersionSignature: User Name 5.0.0-16.17-generic 5.0.8 Uname: Linux 5.0.0-16-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 17 04:37 seq crw-rw 1 root audio 116, 33 Jun 17 04:37 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27 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: Mon Jun 17 04:40:18 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-5.0.0-16-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro RelatedPackageVersions: linux-restricted-modules-5.0.0-16-generic N/A linux-backports-modules-5.0.0-16-generic N/A linux-firmware1.178.1 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:
[Kernel-packages] [Bug 1878075] [NEW] Request to blacklist floppy for images on Azure
Public bug reported: After booting, there's an error message in dmesg: "blk_update_request: I/O error, dev fd0, sector 0" There’s no point in having a floppy driver, and the “I/O error dev fd0 sector 0” messages are distracting where there is no real issue. Blacklisting floppy can avoid this error. Adding a file into the /etc/modprobe.d directory is one approach. You can name the file whatever you want that ends with .conf, and the contents just need to be “blacklist floppy”. Using a separate file means you don’t have to edit any existing files, so it’s easy to update an existing image. However, another approach might be needed if the floppy driver is initramfs. ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: New -- 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/1878075 Title: Request to blacklist floppy for images on Azure Status in linux-azure package in Ubuntu: New Bug description: After booting, there's an error message in dmesg: "blk_update_request: I/O error, dev fd0, sector 0" There’s no point in having a floppy driver, and the “I/O error dev fd0 sector 0” messages are distracting where there is no real issue. Blacklisting floppy can avoid this error. Adding a file into the /etc/modprobe.d directory is one approach. You can name the file whatever you want that ends with .conf, and the contents just need to be “blacklist floppy”. Using a separate file means you don’t have to edit any existing files, so it’s easy to update an existing image. However, another approach might be needed if the floppy driver is initramfs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1878075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
Hey Dan, thanks for getting back. In my case, it's not even my system though: it's Canonical's system; It's a fresh download of a cloudimg from https://cloud-images.ubuntu.com/focal/ which has the issue, so it can't because I didn't build the image right, because I didn't build the image at all. So how would this be able to help? What is the rationale behind the new initrdfail design and 40-force-partuuid.cfg? Thanks. -- 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/1870189 Title: initramfs does not get loaded Status in grub2 package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Bug description: A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by “do-release-upgrade –d”. Then the latest Ubuntu v5.6 kernel was installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a reboot was performed, a panic with the v5.6 kernel occured because the rootfs can not be found. It turns out by default, initramfs does not get loaded: /boot/grub/grub.cfg: menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3d2737e8- b95a-42bf-bac1-bb6fb4cda87f' { … if [ "${initrdfail}" = 1 ]; then linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic initrd/boot/initrd.img-5.6.0-050600-generic else linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic panic=-1 #Dexuan: here the initrd line is missing! fi initrdfail } As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit the “fail to mount rootfs” panic and the kernel will automatically reboot…. Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots for the 2nd time, the kernel should successfully boot up. Next, when the kernel boots for the 3rd time, it panics again since the userspace program resets initrdfail to 0, and next time when the kernel boots, it can boot up successfully -- this “panic/success/panic/success” pattern repeats forever… The linux-azure kernels are not affected since they have the vmbus driver and storage drivers built-in (i.e. “=y”): /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m The v5.6 kernel uses =m rather than =y, so is affected here. It looks the setting may be intentional, but we should not assume a customer kernel must have the necessary vmbus/storage drivers built-in. This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 19.04 as well?) on Azure. We installed a Ubuntu 20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878098] Re: Xenial update: 4.4.221 upstream stable release
All patches applied cleanly. ** Description changed: + SRU Justification - 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: - 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: + 4.4.221 upstream stable release + from git://git.kernel.org/ -4.4.221 upstream stable release -from git://git.kernel.org/ + The following patches from the 4.4.221 stable release shall be applied: + * ext4: fix extent_status fragmentation for plain files + * ALSA: hda - Fix incorrect usage of IS_REACHABLE() + * net: ipv4: emulate READ_ONCE() on ->hdrincl bit-field in raw_sendmsg() + * net: ipv4: avoid unused variable warning for sysctl + * crypto: mxs-dcp - make symbols 'sha1_null_hash' and 'sha256_null_hash' static + * vti4: removed duplicate log message. + * scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login + * ceph: return ceph_mdsc_do_request() errors from __get_parent() + * ceph: don't skip updating wanted caps when cap is stale + * pwm: rcar: Fix late Runtime PM enablement + * scsi: iscsi: Report unbind session event when the target has been removed + * ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() + * kernel/gcov/fs.c: gcov_seq_next() should increase position index + * ipc/util.c: sysvipc_find_ipc() should increase position index + * s390/cio: avoid duplicated 'ADD' uevents + * pwm: renesas-tpu: Fix late Runtime PM enablement + * pwm: bcm2835: Dynamically allocate base + * ipv6: fix restrict IPV6_ADDRFORM operation + * macvlan: fix null dereference in macvlan_device_event() + * net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node + * net/x25: Fix x25_neigh refcnt leak when receiving frame + * tcp: cache line align MAX_TCP_HEADER + * team: fix hang in team_mode_get() + * xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish + * ALSA: hda: Remove ASUS ROG Zenith from the blacklist + * iio: xilinx-xadc: Fix ADC-B powerdown + * iio: xilinx-xadc: Fix clearing interrupt when enabling trigger + * iio: xilinx-xadc: Fix sequencer configuration for aux channels in simultaneous mode + * fs/namespace.c: fix mountpoint reference counter race + * USB: sisusbvga: Change port variable from signed to unsigned + * USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70 RGB RAPIDFIRE + * drivers: usb: core: Don't disable irqs in usb_sg_wait() during URB submit. + * drivers: usb: core: Minimize irq disabling in usb_sg_cancel() + * USB: core: Fix free-while-in-use bug in the USB S-Glibrary + * USB: hub: Fix handling of connect changes during sleep + * ALSA: usx2y: Fix potential NULL dereference + * ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif + * ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices + * KVM: Check validity of resolved slot when searching memslots + * KVM: VMX: Enable machine check support for 32bit targets + * tty: hvc: fix buffer overflow during hvc_alloc(). + * tty: rocket, avoid OOB access + * usb-storage: Add unusual_devs entry for JMicron JMS566 + * audit: check the length of userspace generated audit records + * ASoC: dapm: fixup dapm kcontrol widget + * ARM: imx: provide v7_cpu_resume() only on ARM_CPU_SUSPEND=y + * staging: comedi: dt2815: fix writing hi byte of analog output + * staging: comedi: Fix comedi_device refcnt leak in comedi_open + * staging: vt6656: Fix drivers TBTT timing counter. + * staging: vt6656: Power save stop wake_up_count wrap around. + * UAS: no use logging any details in case of ENODEV + * UAS: fix deadlock in error handling and PM flushing work + * usb: f_fs: Clear OS Extended descriptor counts to zero in ffs_data_reset() + * remoteproc: Fix wrong rvring index computation + * sctp: use right member as the param of list_for_each_entry + * fuse: fix possibly missed wake-up after abort + * mtd: cfi: fix deadloop in cfi_cmdset_0002.c do_write_buffer + * usb: gadget: udc: bdc: Remove unnecessary NULL checks in bdc_req_complete + * net/cxgb4: Check the return from t4_query_params properly + * perf/core: fix parent pid/tid in task exit events + * bpf, x86: Fix encoding for lower 8-bit registers in BPF_STX BPF_B + * scsi: target: fix PR IN / READ FULL
[Kernel-packages] [Bug 1870189] Re: initramfs does not get loaded
You may have a file /etc/default/grub.d/40-force-partuuid.cfg in your system, that sets the grub var GRUB_FORCE_PARTUUID. If so, you can just comment out that line, or remove the file, and run 'sudo update-grub'. Your /boot/grub/grub.cfg should then no longer have the initrd-less boot with panic backup. -- 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/1870189 Title: initramfs does not get loaded Status in grub2 package in Ubuntu: Confirmed Status in linux-azure package in Ubuntu: Confirmed Bug description: A Gen-1 Ubuntu 19.10 VM on Azure was created and upgraded to Ubuntu 20.04 by “do-release-upgrade –d”. Then the latest Ubuntu v5.6 kernel was installed from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.6/. As soon as a reboot was performed, a panic with the v5.6 kernel occured because the rootfs can not be found. It turns out by default, initramfs does not get loaded: /boot/grub/grub.cfg: menuentry 'Ubuntu' --class ubuntu --class gnu-linux --class gnu --class os $menuentry_id_option 'gnulinux-simple-3d2737e8- b95a-42bf-bac1-bb6fb4cda87f' { … if [ "${initrdfail}" = 1 ]; then linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic initrd/boot/initrd.img-5.6.0-050600-generic else linux /boot/vmlinuz-5.6.0-050600-generic root=PARTUUID=bc3d472f-401e-4774-affa-df1acba65a73 ro console=tty1 console=ttyS0 earlyprintk=ttyS0 ignore_loglevel sysrq_always_enabled unknown_nmi_panic panic=-1 #Dexuan: here the initrd line is missing! fi initrdfail } As we can see, Ubuntu only uses the initrd.img if initrdfail=1. Normally, initrdfail = 0, so when we boot the v5.6 kernel for the first time, we must hit the “fail to mount rootfs” panic and the kernel will automatically reboot…. Also, the “initrdfail” here marks initrdfail=1, so when the kernel boots for the 2nd time, the kernel should successfully boot up. Next, when the kernel boots for the 3rd time, it panics again since the userspace program resets initrdfail to 0, and next time when the kernel boots, it can boot up successfully -- this “panic/success/panic/success” pattern repeats forever… The linux-azure kernels are not affected since they have the vmbus driver and storage drivers built-in (i.e. “=y”): /boot/config-5.3.0-1013-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.3.0-1013-azure:CONFIG_HYPERV=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV_STORAGE=y /boot/config-5.4.0-1006-azure:CONFIG_HYPERV=y /boot/config-5.6.0-050600-generic:CONFIG_HYPERV_STORAGE=m /boot/config-5.6.0-050600-generic:CONFIG_HYPERV=m The v5.6 kernel uses =m rather than =y, so is affected here. It looks the setting may be intentional, but we should not assume a customer kernel must have the necessary vmbus/storage drivers built-in. This issue only happens to the Ubuntu Marketplace image (19.10 and maybe 19.04 as well?) on Azure. We installed a Ubuntu 20.04 VM from the .iso file from http://cdimage.ubuntu.com/daily-live/pending/ and don’t see the strange grub issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1870189/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878059] 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 1878059 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/1878059 Title: Audio device not reachable after wake up Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878059] Re: Audio device not reachable after wake up
there are some known nvidia/hdmi issue with the current kernel, reassigning ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878059 Title: Audio device not reachable after wake up Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878059/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878059] [NEW] Audio device not reachable after wake up
You have been subscribed to a public bug: Ubuntu 20.04, Gnome shell On older Ubuntu releases (<= 19.10), all is working fine. After waking up from suspend mode when I play music or a video, the system changed playing sound at my monitor speakers, detected as „card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1]“. Here is the full list: $ LANG=C aplay -l List of PLAYBACK Hardware Devices card 0: PCH [HDA Intel PCH], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: PCH [HDA Intel PCH], device 1: ALC892 Digital [ALC892 Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 7: HDMI 1 [HDMI 1] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 8: HDMI 2 [HDMI 2] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: NVidia [HDA NVidia], device 9: HDMI 3 [HDMI 3] Subdevices: 1/1 Subdevice #0: subdevice #0 I can only choose the HDMI device in gnome-control-center or pavucontrol. The other devices are gone, why what ever. When I restart the pulseaudio process, all devices will come back: $ sudo killall -9 pulseaudio # (many times, because pa restarts itself) $ /usr/bin/pulseaudio --daemonize=no --log-target=journal ^Z [1]+ Angehalten /usr/bin/pulseaudio --daemonize=no --log-target=journal $ bg 1 This behavior is new in 20.04. Before I establish the behavior of pulseaudio, I logged off and on again and all devices are shown. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- Audio device not reachable after wake up https://bugs.launchpad.net/bugs/1878059 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 1752772] Re: r8169 ethernet card don't work after returning from suspension
Seeing this with r8152 on 20.04 (Regolith 1.4) with kernel 5.4.0-29 Will try reloading the driver after my next resume. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in Linux: New Status in linux package in Ubuntu: Fix Released Status in linux-kernel-headers package in Ubuntu: Confirmed Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1861462] Re: Lenovo Thinkpad X1 Carbon 7th Gen doesn't suspend and resume
I updated to 20.04 and now I have this bug too. Kernel 5.4.26-050426-generic. Anybody aware of a fix? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1861462 Title: Lenovo Thinkpad X1 Carbon 7th Gen doesn't suspend and resume Status in linux-5.4 package in Ubuntu: Fix Released Status in linux-5.4 source package in Focal: Fix Released Bug description: Steps: 1. Install Ubuntu 20.04 daily image (tested Jan 29th, 2020 image) using default options. 2. apt update 3. apt upgrade 4. reboot so the machine is in pristine state 5. Close lid 6. Machine doesn't suspend (the light on the laptop power button doesn't pulsate) 7. Open the lid. The system doesn't respond and display is off 8. the only option is to power down the laptop and restart it. 9. upon restarting, Apport doesn't complain (this report was filed manually using ubuntu-bug) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 CurrentDesktop: GNOME Date: Thu Jan 30 18:56:41 2020 InstallationDate: Installed on 2020-01-30 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124) SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-5.4/+bug/1861462/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876459] Re: windows 1909 drivers update breaks ALC294 sound
fix is here https://bugzilla.kernel.org/show_bug.cgi?id=207553 ** Bug watch added: Linux Kernel Bug Tracker #207553 https://bugzilla.kernel.org/show_bug.cgi?id=207553 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876459 Title: windows 1909 drivers update breaks ALC294 sound Status in linux package in Ubuntu: Confirmed Bug description: Hello! SHORT VERSION: Recent windows drivers initialize ALC294 with 24bit 48000HZ, after rebooting to linux it produce garbaged sound (it decay every second, very strange effect). If you reboot from windows 10 1909 directly to linux it broken. You have to turn power off complete to reset the device. LONG VERSION: I recently install recent version of windows on separate partition and got garbaged sound on booth OS! My old version of windows was 1803 and everying was ok, I updated to 1909 and it got broken sound. Probably due to some firmware / configs / updates on sound chip. I let Windows to update drivers and notice my sound card driver got replaced by realtek drivers and sound got fixed on windows! But linux still not working propertly! also-info.sh shows two devices: http://alsa-project.org/db/?f=6d80e374011ccba05d32c8a6e6bde57316cbf06d This how it was on booth Linux and Windows 1810 before update. Windows also used to show two devices "AMD High Definition Audio Device", "High Definition Audio Device". Something tells me alsa detect cards correctly. But now, something changed and alsa need to update configs... Now Windows shows two devices: "AMD High Definition Audio Device" and second "Realtek(R) Audio". AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 Realtek Semiconductor Corp./6.0.8757.1/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.16.0.86/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 High Definition Audio Controller/10.0.18362.1 /PCI\VEN_1022_15E3_1B111043_00\4&28056CF2&0&0641 High Definition Audio Controller/10.0.18362.1/PCI\VEN_1002_15DE_15DE1002_00\4&28056CF2&0&0141 As you can see from new windows drivers it detects two devices 1002:AA01 and 10ec:0294, but alsa keep detecting 1002:15de and 1022:15e3 On Ubuntu machine sound still completely garbaged and sounds like broken speakers. My headphones makes even stranger sounds. Not sure what to do. I found several links about this issue here: https://github.com/torvalds/linux/commit/60083f9e94b2f28047d71ed778adf89357c1a8fb https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1850439 https://askubuntu.com/questions/1175095/asus-zenbook-ux534f-no-sound- from-speakers-headphones/1186977 Windows 1909 without updates shows those id's: AMD High Definition Audio Device/10.0.1.10/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.18362.356/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 Windows 1803 without updates (old external installation, I still can boot here, and confirming those drivers produce exactly same sound issues like on linux): AMD High Definition Audio Device/10.0.1.6/HDAUDIO\FUNC_01_1002_AA01_00AA0100& REV_1007\5&14BACE15&0&0001 High Definition Audio Device/10.0.17134.1006/HDAUDIO\FUNC_01_10EC_0294_10431B11& REV_1000\5&7195807&0&0001 AMD Audio CoProcessor/1.17.0.94/PCI\VEN_1022_15E2_15E21022_00\4&280 56CF2&0&0541 Also, this sound card requires few addtitional actions to perform from here: https://wiki.archlinux.org/index.php/ASUS_Zenbook_UX390 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: axet 1433 F pulseaudio /dev/snd/controlC0: axet 1433 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 16:25:01 2020 MachineType: ASUSTeK COMPUTER INC. ZenBook UX431DA_UM431DA ProcEnviron: LANGUAGE=en_US TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=/dev/mapper/vg0-root ro acpi_enforce_resources=lax PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/2019 dmi.bios.vendor: American
[Kernel-packages] [Bug 1878098] [NEW] Xenial update: 4.4.221 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: 4.4.221 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) 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/1878098 Title: Xenial update: 4.4.221 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Xenial: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.221 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873594] Re: sporadic black screen freeze on lenovo e595 Ryzen 3700U
Also freeze occurs with "nomodeset" -> So it is NOT valid workaround. More freezes if i am on battery only. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873594 Title: sporadic black screen freeze on lenovo e595 Ryzen 3700U Status in linux package in Ubuntu: Confirmed Bug description: Hi, i have sporadic black screen freeze on my lenovo e595 3700U during reboot. The only workaround till now is add "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT Problem occure also on linux-image-unsigned-5.6.5-050605-generic_5.6.5-050605.202004171629_amd64 and linux-image-unsigned-5.4.28-050428-generic_5.4.28-050428.202003250833_amd64 19.10 was working with 5.0 kernel regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gizzmo 1345 F pulseaudio /dev/snd/controlC1: gizzmo 1345 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Apr 18 21:28:37 2020 InstallationDate: Installed on 2020-04-18 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgkubuntu-root ro nomodeset ip=dhcp RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW 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.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873594] Re: sporadic black screen freeze on lenovo e595 Ryzen 3700U
Also workaround kernel on 20.4: 5.3.18-050318-generic #201912181133 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873594 Title: sporadic black screen freeze on lenovo e595 Ryzen 3700U Status in linux package in Ubuntu: Confirmed Bug description: Hi, i have sporadic black screen freeze on my lenovo e595 3700U during reboot. The only workaround till now is add "nomodeset" to GRUB_CMDLINE_LINUX_DEFAULT Problem occure also on linux-image-unsigned-5.6.5-050605-generic_5.6.5-050605.202004171629_amd64 and linux-image-unsigned-5.4.28-050428-generic_5.4.28-050428.202003250833_amd64 19.10 was working with 5.0 kernel regards ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: gizzmo 1345 F pulseaudio /dev/snd/controlC1: gizzmo 1345 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sat Apr 18 21:28:37 2020 InstallationDate: Installed on 2020-04-18 (0 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 002: ID 0bda:b023 Realtek Semiconductor Corp. Bluetooth Radio Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20NFCTO1WW ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-24-generic root=/dev/mapper/vgkubuntu-root ro nomodeset ip=dhcp RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/30/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R11ET36W (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NFCTO1WW 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.modalias: dmi:bvnLENOVO:bvrR11ET36W(1.16):bd03/30/2020:svnLENOVO:pn20NFCTO1WW:pvrThinkPadE595:rvnLENOVO:rn20NFCTO1WW:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E595 dmi.product.name: 20NFCTO1WW dmi.product.sku: LENOVO_MT_20NF_BU_Think_FM_ThinkPad E595 dmi.product.version: ThinkPad E595 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873594/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877890] Re: System Hangs when trying to kill a Window
Dear Sirs, I just wish you to be aware of one fact with my supplying you with the apport information today. Last night after another Hangup in the same place in mwait_idle, I thought that maybe the problem is something to do with this module. I came across an option at Boot time called "idle=nomwait" Thinking that maybe putting this option into the kernel at boot time may fix the problem that's what I did when I had to re-boot yesterday. So I just want you to be aware that that option was NOT being used during the original Hang Up problems. I don't know if that effects the information that I just sent you or not but I wanted you to be aware of that. Frank Krauss -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version:
[Kernel-packages] [Bug 1877890] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370027/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post
[Kernel-packages] [Bug 1877890] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370026/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1877890] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370028/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to
[Kernel-packages] [Bug 1877890] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370025/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1877890] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370021/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1877890] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370022/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1877890] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370019/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1877890] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370023/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages
[Kernel-packages] [Bug 1877890] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370020/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1877890] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370024/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1877890] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370029/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: fkrauss1808 F pulseaudio /dev/snd/controlC0: fkrauss1808 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2020-04-20 (20 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) IwConfig: ens2 no wireless extensions. lono wireless extensions. 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 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-51-generic N/A linux-backports-modules-5.3.0-51-generic N/A linux-firmware1.173.17 RfKill: Tags: bionic Uname: Linux 5.3.0-51-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 02/08/2010 dmi.bios.vendor: Intel Corp. dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: DG31PR dmi.board.vendor: Intel Corporation dmi.board.version: AAD97573-306 dmi.chassis.type: 3 dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: To manage notifications about this bug go to:
[Kernel-packages] [Bug 1877890] Re: System Hangs when trying to kill a Window
apport information ** Tags added: apport-collected ** Description changed: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) + --- + ProblemType: Bug + ApportVersion: 2.20.9-0ubuntu7.14 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC1: fkrauss1808 F pulseaudio + /dev/snd/controlC0: fkrauss1808 F pulseaudio + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 18.04 + InstallationDate: Installed on 2020-04-20 (20 days ago) + InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) + IwConfig: + ens2 no wireless extensions. + + lono wireless extensions. + 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 nouveaudrmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-51-generic root=UUID=b52c713d-a2a9-4b17-8eed-79a031a415e8 ro quiet splash zswap.enabled=1 zswap.compressor=lz4 crashkernel=512M-:192M vt.handoff=1 idle=nomwait + ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 + RelatedPackageVersions: + linux-restricted-modules-5.3.0-51-generic N/A + linux-backports-modules-5.3.0-51-generic N/A + linux-firmware1.173.17 + RfKill: + + Tags: bionic + Uname: Linux 5.3.0-51-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm audio cdrom dip lpadmin plugdev sambashare sudo video + _MarkForUpload: True + dmi.bios.date: 02/08/2010 + dmi.bios.vendor: Intel Corp. + dmi.bios.version: PRG3110H.86A.0070.2010.0208.1351 + dmi.board.asset.tag: To be filled by O.E.M. + dmi.board.name: DG31PR + dmi.board.vendor: Intel Corporation + dmi.board.version: AAD97573-306 + dmi.chassis.type: 3 + dmi.modalias: dmi:bvnIntelCorp.:bvrPRG3110H.86A.0070.2010.0208.1351:bd02/08/2010:svn:pn:pvr:rvnIntelCorporation:rnDG31PR:rvrAAD97573-306:cvn:ct3:cvr: ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1877890/+attachment/5370018/+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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Confirmed Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very
[Kernel-packages] [Bug 1876449] Re: Apple external Trackpad event timestamps are jittery
Reported upstream: https://www.spinics.net/lists/linux- input/msg67383.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1876449 Title: Apple external Trackpad event timestamps are jittery Status in linux package in Ubuntu: Confirmed Bug description: Using a vanilla installation of Ubuntu 20.04, the timestamps of input events from my Apple "Magic Trackpad" - 1st generation, connected over Bluetooth - are jittery. This is a regression, the timestamps were fine when using Ubuntu 19.10. I bisected the bug. - The problem starts with upstream kernel commit 3b51c44bd693 ("Input: allow drivers specify timestamp for input events"). After that commit, the same timestamp is always emitted. - This was partially fixed in commit 4370b231d100 ("Input: reset device timestamp on sync"), however ever since then the timestamps are jittery. The problem still exists in the current upstream 'master' (commit c45e8bccecaf). The following patch fixes the bug, however this is obviously a hack. It effectively reverts commit 3b51c44bd693: diff --git a/drivers/input/input.c b/drivers/input/input.c index 3cfd2c18eebd..8890195547d6 100644 --- a/drivers/input/input.c +++ b/drivers/input/input.c @@ -1958,7 +1958,7 @@ ktime_t *input_get_timestamp(struct input_dev *dev) { const ktime_t invalid_timestamp = ktime_set(0, 0); - if (!ktime_compare(dev->timestamp[INPUT_CLK_MONO], invalid_timestamp)) + // if (!ktime_compare(dev->timestamp[INPUT_CLK_MONO], invalid_timestamp)) input_set_timestamp(dev, ktime_get()); return dev->timestamp; Steps to reproduce -- I used the following script as a reproducer. It relies on libinput- debug-events. This script measures the time delta between consecutive input events, then prints a "histogram" of these deltas. #!/bin/bash # log file name logFile=${1:-~/Downloads/`uname -r`} echo logFile=$logFile if [[ "$1" == '' ]]; then echo record # log some events sudo libinput debug-events | grep POINTER | tee $logFile fi # process the results lastN=0 for f in `cat $logFile | awk '{print $3}' | sed "s/s//g" | sed "s/+//g"`; do echo "$f-$lastN" | bc; lastN=$f; done | sort | uniq -c 1. Pair an external Apple Trackpad over Blutooth. 2. Run the above script 3. Move your finger in circles on the touchpad for a few seconds 4. Press ctrl+c An example output of this script before the regression -- 2 .010 371 .011 127 .012 1 .876 The above output means that: 2 times the delta was 10ms, 371 times 11ms, 127 times 12ms and 1 time 876ms. This corresponds well with the Trackpad's ~90Hz polling rate. An example output of this script after the regression - 3 .003 12 .004 16 .005 14 .006 21 .007 16 .008 20 .009 13 .010 359 .011 47 .012 20 .013 17 .014 21 .015 14 .016 16 .017 15 .018 2 .019 1 .020 38 .022 21 .023 1 1.060 I suspect that other input devices might be affected as well. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-28-generic 5.4.0-28.32 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yariv 1783 F pulseaudio CasperMD5CheckResult: skip Date: Sat May 2 13:58:34 2020 InstallationDate: Installed on 2019-07-13 (293 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: Gigabyte Technology Co., Ltd. Z170X-UD5 TH ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-28-generic root=UUID=6deee348-bb50-4b88-837b-108413e4d8f2 ro quiet splash btusb.enable_autosuspend=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-28 (3 days ago) dmi.bios.date: 03/09/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F22g dmi.board.asset.tag: Default string dmi.board.name: Z170X-UD5 TH-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1871688] Re: LIO hanging in iscsit_free_session and iscsit_stop_session
The Xenial system that I installed the binary packages from the proposed Bionic repository on has been running properly and stable since the 7th. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871688 Title: LIO hanging in iscsit_free_session and iscsit_stop_session Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: The target subsystem (LIO) can hang if multiple threads try to destroy iSCSI sessions simultaneously. This is reproducible on systems that have multiple targets with initiators regularly connecting/disconnecting. This may happen when a "targetcli iscsi/iqn.../tpg1 disable" command is executed when a logout operation is underway. The iscsi target doesn't handle such events in a correct way: two or more threads may end up sleeping while waiting for the driver to close the remaining connections on the session. When the connections are closed, the driver wakes up only the first thread that will then proceed to destroy the session structure. The remaining threads are blocked there forever, waiting on a completion synchronization mechanism that doesn't exist in memory anymore because it has been freed by the first thread. Note that if the blocked threads are somehow forced to wake up, they will try to free the same iSCSI session structure destroyed by the first thread, causing double frees, memory corruptions, etc. The driver has been reorganized so the concurrent threads will set a flag in the session structure to notify the driver that the session should be destroyed; then, they wait for the driver to close the remaining connections. When the connections are all closed, the driver will wake up all the threads and will wait for the refcount of the iSCSI session structure to reach zero. When the last thread wakes up, the refcount is decreased to zero and the driver can proceed to destroy the session structure because no one is referencing it anymore. I've witnessed this happening on hundreds of Ubuntu 16.04.5 systems. It is a regression, because this did not occur several years ago. Unfortunately, I don't have detailed records from that far back to determine exactly which kernel I was running that was not affected by this bug (I believe it was either 4.8.x or 4.10.x). I've attached the requested uname, version_signature, dmesg, and lspci from my system. However, I've seen this happen on a wide array of hardware: 2 to 24 cores, 8GB to 256GB RAM, both AMD and Intel CPUs, onboard storage and PCIe SAS cards, etc. This has been fixed in the upstream master branch, but it hasn't yet been backported to "-stable". To fix this in the Ubuntu kernel, these three commits should be backported: * https://github.com/torvalds/linux/commit/e49a7d994379278d3353d7ffc7994672752fb0ad * https://github.com/torvalds/linux/commit/57c46e9f33da530a2485fa01aa27b6d18c28c796 * https://github.com/torvalds/linux/commit/626bac73371eed79e2afa2966de393da96cf925e I'd like these commits to be added to the xenial, bionic, and focal kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1871688/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878073] [NEW] Eoan update: upstream stable patchset 2020-05-11
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: upstream stable patchset 2020-05-11 Ported from the following upstream stable releases: v4.19.119, v5.4.36 from git://git.kernel.org/ ext4: fix extent_status fragmentation for plain files bpftool: Fix printing incorrect pointer in btf_dump_ptr UBUNTU: [Config] updateconfigs for ARM64_ERRATUM_1542419 arm64: errata: Hide CTR_EL0.DIC on systems affected by Neoverse-N1 #1542419 arm64: Fake the IminLine size on systems affected by Neoverse-N1 #1542419 arm64: compat: Workaround Neoverse-N1 #1542419 for compat user-space arm64: Silence clang warning on mismatched value/register sizes watchdog: reset last_hw_keepalive time at start scsi: lpfc: Fix kasan slab-out-of-bounds error in lpfc_unreg_login scsi: lpfc: Fix crash in target side cable pulls hitting WAIT_FOR_UNREG ceph: return ceph_mdsc_do_request() errors from __get_parent() ceph: don't skip updating wanted caps when cap is stale pwm: rcar: Fix late Runtime PM enablement scsi: iscsi: Report unbind session event when the target has been removed ASoC: Intel: atom: Take the drv->lock mutex before calling sst_send_slot_map() nvme: fix deadlock caused by ANA update wrong locking kernel/gcov/fs.c: gcov_seq_next() should increase position index selftests: kmod: fix handling test numbers above 9 ipc/util.c: sysvipc_find_ipc() should increase position index kconfig: qconf: Fix a few alignment issues s390/cio: avoid duplicated 'ADD' uevents loop: Better discard support for block devices Revert "powerpc/64: irq_work avoid interrupt when called with hardware irqs enabled" pwm: renesas-tpu: Fix late Runtime PM enablement pwm: bcm2835: Dynamically allocate base perf/core: Disable page faults when getting phys address ASoC: Intel: bytcr_rt5640: Add quirk for MPMAN MPWIN895CL tablet drm/amd/display: Not doing optimize bandwidth if flip pending. virtio-blk: improve virtqueue error to BLK_STS scsi: smartpqi: fix call trace in device discovery PCI/ASPM: Allow re-enabling Clock PM f2fs: fix to avoid memory leakage in f2fs_listxattr cxgb4: fix adapter crash due to wrong MC size cxgb4: fix large delays in PTP synchronization ipv6: fix restrict IPV6_ADDRFORM operation macsec: avoid to set wrong mtu macvlan: fix null dereference in macvlan_device_event() net: bcmgenet: correct per TX/RX ring statistics net: netrom: Fix potential nr_neigh refcnt leak in nr_add_node net: stmmac: dwmac-meson8b: Add missing boundary to RGMII TX clock array net/x25: Fix x25_neigh refcnt leak when receiving frame sched: etf: do not assume all sockets are full blown tcp: cache line align MAX_TCP_HEADER team: fix hang in team_mode_get() vrf: Fix IPv6 with qdisc and xfrm net: dsa: b53: Lookup VID in ARL searches when VLAN is enabled net: dsa: b53: Fix ARL register definitions net: dsa: b53: Rework ARL bin logic net: dsa: b53: b53_arl_rw_op() needs to select IVL or SVL xfrm: Always set XFRM_TRANSFORMED in xfrm{4,6}_output_finish vrf: Check skb for XFRM_TRANSFORMED flag mlxsw: Fix some IS_ERR() vs NULL bugs KEYS: Avoid false positive ENOMEM error on key read ALSA: hda: Remove ASUS ROG Zenith from the blacklist ALSA: usb-audio: Add static mapping table for ALC1220-VB-based mobos ALSA: usb-audio: Add connector notifier delegation iio: core: remove extra semi-colon from devm_iio_device_register() macro iio: st_sensors: rely on odr mask to know if odr can be set iio: adc: stm32-adc: fix sleep in atomic context iio: xilinx-xadc: Fix ADC-B powerdown iio: xilinx-xadc: Fix clearing interrupt when enabling trigger iio: xilinx-xadc: Fix sequencer configuration for aux channels in simultaneous mode iio: xilinx-xadc: Make sure not exceed maximum samplerate USB: sisusbvga: Change port variable from signed to unsigned USB: Add USB_QUIRK_DELAY_CTRL_MSG and USB_QUIRK_DELAY_INIT for Corsair K70 RGB RAPIDFIRE USB: early: Handle AMD's spec-compliant identifiers, too USB: core: Fix free-while-in-use bug in the USB S-Glibrary USB: hub: Fix handling of connect changes during sleep vmalloc: fix remap_vmalloc_range() bounds checks mm/hugetlb: fix a addressing exception caused by huge_pte_offset mm/ksm: fix NULL pointer dereference when KSM zero page is enabled tools/vm: fix cross-compile build ALSA: usx2y: Fix potential NULL dereference ALSA: hda/realtek - Fix unexpected init_amp override ALSA: hda/realtek - Add new codec supported for ALC245 ALSA: usb-audio: Fix usb audio refcnt leak when getting spdif ALSA: usb-audio: Filter out unsupported sample rates on Focusrite devices tpm/tpm_tis: Free IRQ if probing fails
[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
That patch fixed the problem for me as well! 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/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers Status in linux package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 20.04 LTS, the only way of hearing audio is through headphones. The sound settings tab doesn't even show any other output option other than "Dummy output" . I have already checked other versions and everything works perfectly when I downgrade to Ubuntu 19.10, so I think this is a version related bug. Just to reiterate my laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have looked up solutions online for 2 days and none has worked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 19:04:06 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877488] Re: External mouse movement wakes computer from hibernate
You can disable wakeup by modifying "/proc/acpi/wakeup" in Linux 1. get all wakeup sources - "cat /proc/acpi/wakeup" The results are something like Device S-state Status Sysfs node PEG0 S4*enabled pci::00:01.0 PEGP S4*disabled pci::01:00.0 PEG1 S4*disabled PEGP S4*disabled ... XHC S3*enabled pci::00:14.0 ... 2. find out which USB maps to your logitech mouse. You probably need trial and error couple times. The above example is XHC which is USB3 controller which is capable of waking up from S3, S2 and S1. Your will differ. 3. disable it by "echo XHC | sudo tee /proc/acpi/wakeup" (assuming XHC is the one). finally, you can disable it automatically by rc.local (like https://vpsfix.com/community/server-administration/no-etc-rc-local-file- on-ubuntu-18-04-heres-what-to-do/) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877488 Title: External mouse movement wakes computer from hibernate Status in linux package in Ubuntu: Incomplete Bug description: When the computer is suspended, moving the mouse (External logitech) causes the computer to come out of hibernation. I can tell because the Legion logo lights up. After a little while (minute?) it evidently suspends again because the logo turns off again. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: ubuntu-release-upgrader-core 1:20.04.19 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Thu May 7 19:07:34 2020 InstallationDate: Installed on 2020-03-12 (56 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lisa 1854 F pulseaudio /dev/snd/controlC0: lisa 1854 F pulseaudio /dev/snd/pcmC0D0p: lisa 1854 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-03-12 (57 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200306) MachineType: LENOVO 81T2 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 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-30-generic root=UUID=51068ea2-6b38-4cfc-a75f-4f404cd04685 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 RelatedPackageVersions: linux-restricted-modules-5.4.0-30-generic N/A linux-backports-modules-5.4.0-30-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-30-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip lpadmin lxd plugdev sambashare sudo vboxusers _MarkForUpload: True dmi.bios.date: 11/23/2019 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN35WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y545 PG0 dmi.modalias: dmi:bvnLENOVO:bvrBHCN35WW:bd11/23/2019:svnLENOVO:pn81T2:pvrLegionY545PG0:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegionY545PG0: dmi.product.family: Legion Y545 PG0 dmi.product.name: 81T2 dmi.product.sku: LENOVO_MT_81T2_BU_idea_FM_Legion Y545 PG0 dmi.product.version: Legion Y545 PG0 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877488/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877870] Re: ACPI errors
This is usually the result of duplicated name declaration in ACPI BIOS, and there are usually no harms. An ACPI dump (sudo acpidump > acpi.log) will be helpful for further analysis. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877870 Title: ACPI errors Status in linux package in Ubuntu: Confirmed Bug description: Hi, i have a bunch of acpi errors showing up on the log. this one repeats a lot: ACPI BIOS Error (bug): Failure creating named object [\_SB.PCI0.XHC.RHUB.SS09._UPC], AE_ALREADY_EXISTS (20190816/dswload2-323) my bios is updated (from windows, on april 3, 2020) currently running ubuntu 20.04 with kernel 5.4.0-29-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pkillpeers 1879 F pulseaudio /dev/snd/controlC0: pkillpeers 1879 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun May 10 16:24:50 2020 InstallationDate: Installed on 2020-05-07 (3 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 003: ID 0408:5300 Quanta Computer, Inc. HP Wide Vision HD Camera Bus 001 Device 002: ID 046d:c07e Logitech, Inc. G402 Gaming Mouse Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP OMEN by HP Laptop 15-dc0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=c93b8267-6fe4-492f-ad94-1252537b50fb 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/23/2020 dmi.bios.vendor: AMI dmi.bios.version: F.12 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 84DB dmi.board.vendor: HP dmi.board.version: 93.24 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAMI:bvrF.12:bd03/23/2020:svnHP:pnOMENbyHPLaptop15-dc0xxx:pvr:rvnHP:rn84DB:rvr93.24:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP OMEN dmi.product.name: OMEN by HP Laptop 15-dc0xxx dmi.product.sku: 4ML16EA#AB9 dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877870/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861925] Re: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255
@esanya, Thanks for updating the results. Hopefully the HW failure is the root cause of the brightness problem that acer can fix. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861925 Title: BrightnessOutofRange: Actual brightness for amdgpu_bl0 not in range 0..255 Status in linux package in Ubuntu: Incomplete Bug description: Hi, I have a acer aspire a315-41 laptop, it has BIOS 1.15, Ubuntu 19.10, Kernel stock 5.3, and 5.5.0. I have a problem with the Backlight. I can not control. According to: https://wiki.ubuntu.com/Kernel/Debugging/Backlight It is : Backlight control does not work, but there are entries in /sys/class/backlight. The problem is as far I could find: sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat brightness 135 sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat actual_brightness 43500 sanya@Aspire-A315-41:/sys/class/backlight/amdgpu_bl0$ cat max_brightness 255 The brightness read from the HW is not in the range, and when I change the brightness by the keys the value in the brightness file changes too, but the actual_brightness is stuck at the value 43500... I have tried all the steps mentioned in https://wiki.ubuntu.com/Kernel/Debugging/Backlight Actually I have tried all these kernel startup parameter variants without luck: GRUB_CMDLINE_LINUX_DEFAULT="" #GRUB_CMDLINE_LINUX_DEFAULT="video.use_native_backlight=1" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=" #GRUB_CMDLINE_LINUX_DEFAULT="video.use_bios_initial_backlight=0" #GRUB_CMDLINE_LINUX_DEFAULT="amdgpu.dcfeaturemask=0x4 amdgpu.abmlevel=2" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_backlight=video amdgpu.abmlevel=1" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=Linux acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=video" #GRUB_CMDLINE_LINUX_DEFAULT="acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" #GRUB_CMDLINE_LINUX_DEFAULT="i8042.nopnp acpi_osi=! acpi_osi=\"Windows 2009\" acpi_backlight=vendor" I guess the fwts has found also this as an error: autobrightness: Automated LCD brightness test. Test 1 of 2: Test for maximum and actual brightness. PASSED: Test 1, Maximum brightness for amdgpu_bl0 is 255 which is sane. FAILED [HIGH] BrightnessOutofRange: Test 1, Actual brightness for amdgpu_bl0 not in range 0..255. Test 2 of 2: Change actual brightness. FAILED [MEDIUM] BrightnessMismatch: Test 2, 256 brightness levels did not match the brightnesss level just set for backlight amdgpu_bl0. The failed brightness levels were: 0-255. It would be great if someone could help set the HW brightness back to the normal range. If you need any more debug files please let me know! Thanks, Regards, Sandor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-11 13:29 EDT--- (In reply to comment #14) > The commits landed in between in linux-next (not tagged yet, but that's > fine). > So it's all brand new stuff ... > I think the chance it not very high that they are just cleanly > cherry-pick-able - having the other PCI changes in mind, too. > > I guess you are thinking about backporting them to focal master-next? > $ git clone > https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal > --branch master-next --single-branch focal-master-next Yes I agree. I will work with Pierre to provide backports. I think a HWE might be an option should we discuss what this would entail here or on another channel? The reason for opening this issue even before this hit Linus' tree or we have backports done was exactly this opening up of discussions how to best proceed with this. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874056] Comment bridged from LTC Bugzilla
--- Comment From niklas.schne...@ibm.com 2020-05-11 13:24 EDT--- (In reply to comment #15) > Compiles now on 18.04 with 2nd backport instead of the cherry-pick. I think this was meant for "[UBUNTU 18.04] zpcictl --reset - contribution for kernel and s390-tools" right? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874056 Title: [UBUNTU 20.04] s390x/pci: enumerate pci functions per physical adapter Status in Ubuntu on IBM z Systems: Incomplete Status in linux package in Ubuntu: New Bug description: Today, the enumeration of PCI functions on s390x does not reflect which functions belongs to which physical adapter. Layout of a PCI function address on Linux: :00:00.0 ::. On s390x, each function is presented as individual root complex today, e.g.: PCHID 0100 VF1 :00:00.0 PCHID 0100 VF23 0001:00:00.0 PCHID 0200 VF1 0002:00:00.0 OCHID 0100 VF17 0003:00:00.0 On other platforms, the addresses correctly reflect the actual HW configuration. Some device drivers (mlx5 for Mellanox adapters) group functions of one physical adapter by checking which PCI functions have identical values for ::. We need to use the same enumeration scheme to achieve this functionality on s390x. In this case, the two physical functions of a Mellanox adapter need to get function number 0 and 1, and all virtual functions need to use the same : numbers with function/device numbers counting up. Required result (example with 4 VFs per PF): PCHID 0100 PF 0 :00:00.0 PCHID 0100 PF 1 :00:00.1 PCHID 0100 PF 0 VF 0 :00:00.2 PCHID 0100 PF 0 VF 1 :00:00.3 PCHID 0100 PF 0 VF 2 :00:00.4 PCHID 0100 PF 0 VF 3 :00:00.5 PCHID 0100 PF 1 VF 0 :00:00.6 PCHID 0100 PF 1 VF 1 :00:00.7 PCHID 0100 PF 1 VF 2 :00:00.8 PCHID 0100 PF 1 VF 3 :00:00.9 PCHID 0200 PF 0 0001:00:00.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1874056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877890] 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 1877890 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/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Incomplete Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877890] Re: System Hangs when trying to kill a Window
** Package changed: ubuntu-release-upgrader (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877890 Title: System Hangs when trying to kill a Window Status in linux package in Ubuntu: Incomplete Bug description: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877890/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878045] Re: doing dist-upgrade got error related do Broadcom
** Package changed: ubuntu-release-upgrader (Ubuntu) => bcmwl (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl in Ubuntu. https://bugs.launchpad.net/bugs/1878045 Title: doing dist-upgrade got error related do Broadcom Status in bcmwl package in Ubuntu: New Bug description: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcmwl/+bug/1878045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877890] [NEW] System Hangs when trying to kill a Window
You have been subscribed to a public bug: Dear Sirs, I'm a long term user of Ubuntu, I run a Client/Server system that my clients expect to be very stable. I ran under Trust Tahr for a long while with great success and no Hangups at all. I recently upgraded to Bionic Beaver and I find that I have a number of Hangups. They seem to occur mostly when switching between different users. The latest one that occurred last night that I want to show you here was caused by something else. I was watching a video from Youtube under Firefox. At the end of it I clicked the upper right hand button of the window to kill the screen. At this point the system froze on me. I could move the mouse around but none of the keys worked. I used the SysrRq - Magic Key combination to get the following information ALT + PrtScrn, ALT + CREISUB The system re-booted and gave me the following files in /var/crash 4096 May 9 23:38 202005092338 349 May 10 11:01 kexec_cmd 25387 May 9 23:39 linux-image-5.3.0-51-generic-202005092338.crash 69696 May 9 23:38 dmesg.202005092338 291014103 May 9 23:38 dump.202005092338 I used the crash program with the Symbols file and in the backtrace section under the exception line it says: exception RIP mwait_idle+132 in the disassembly of mwait_idle the line at +132 is mov%gs:0x72774cb4(%rip),%r12d# 0x10350 Any information that I can supply to you I will be glad to in order to aid you in solving this problem. I'm fairly computer literate and so I can follow any directions that you want to give to me. I have enjoyed using Ubutnu for many years but I do need a Stable environment for my Development work and for my users satisfaction. Yours truly, Frank Krauss ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: ubuntu-release-upgrader-core 1:18.04.37 ProcVersionSignature: Ubuntu 5.3.0-51.44~18.04.2-generic 5.3.18 Uname: Linux 5.3.0-51-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 CrashDB: ubuntu CurrentDesktop: ubuntu:GNOME Date: Sun May 10 13:19:54 2020 InstallationDate: Installed on 2020-04-20 (19 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: ubuntu-release-upgrader Symptom: release-upgrade UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic dist-upgrade -- System Hangs when trying to kill a Window https://bugs.launchpad.net/bugs/1877890 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 1878045] [NEW] doing dist-upgrade got error related do Broadcom
You have been subscribed to a public bug: I had a working 20.04 installation running, including the Broadcom Wifi. After upgrade to 20.10 the Broadcom Wifi is not working. I tried several suggestions and always end to an error similiar to this one: ... Building initial module for 5.4.0-30-generic ERROR (dkms apport): kernel package linux-headers-5.4.0-30-generic is not supported Error! Application of patch 0028-add-support-for-linux-5.6.patch failed. Check /var/lib/dkms/bcmwl/6.30.223.271+bdcom/build/ for more information. dpkg: error processing package bcmwl-kernel-source (--configure): installed bcmwl-kernel-source package post-installation script subprocess returned error exit status 6 Errors were encountered while processing: bcmwl-kernel-source E: Sub-process /usr/bin/dpkg returned an error code (1) ... ProblemType: Bug DistroRelease: Ubuntu 20.10 Package: ubuntu-release-upgrader-core 1:20.10.1 ProcVersionSignature: Ubuntu 5.4.0-30.34-generic 5.4.34 Uname: Linux 5.4.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu33 Architecture: amd64 CasperMD5CheckResult: skip CrashDB: ubuntu Date: Mon May 11 17:16:43 2020 InstallationDate: Installed on 2020-02-22 (78 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) PackageArchitecture: all SourcePackage: ubuntu-release-upgrader Symptom: dist-upgrade UpgradeStatus: Upgraded to groovy on 2020-05-07 (3 days ago) VarLogDistupgradeXorgFixuplog: INFO:root:/usr/bin/do-release-upgrade running INFO:root:No xorg.conf, exiting mtime.conffile..etc.update-manager.release-upgrades: 2020-05-07T09:26:37.178586 ** Affects: bcmwl (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug dist-upgrade groovy third-party-packages -- doing dist-upgrade got error related do Broadcom https://bugs.launchpad.net/bugs/1878045 You received this bug notification because you are a member of Kernel Packages, which is subscribed to bcmwl 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 1878037] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878037 Title: package linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 failed to install/upgrade: kunde inte skapa ny fil "/var/lib/dpkg/info/linux- modules-extra-5.4.0-29-generic.list-new": Operationen inte tillåten Status in linux package in Ubuntu: Confirmed Bug description: Installed a new graphics card due to wrecked old Nvidia Quadro. The new graphic card is a Radeon RX 580, 8 GB GDDR5 and this is the fiorst startup of an Ubuntu 20.04 system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: linux-modules-5.4.0-29-generic:amd64: Install linux-image-5.4.0-29-generic:amd64: Install linux-modules-extra-5.4.0-29-generic:amd64: Install linux-image-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bandola1714 F pulseaudio CasperMD5CheckResult: skip Date: Thu May 7 06:51:23 2020 ErrorMessage: kunde inte skapa ny fil "/var/lib/dpkg/info/linux-modules-extra-5.4.0-29-generic.list-new": Operationen inte tillåten InstallationDate: Installed on 2019-03-10 (428 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: linux Title: package linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 failed to install/upgrade: kunde inte skapa ny fil "/var/lib/dpkg/info/linux-modules-extra-5.4.0-29-generic.list-new": Operationen inte tillåten UpgradeStatus: Upgraded to focal on 2020-04-23 (18 days ago) dmi.bios.date: 05/07/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.05 dmi.board.name: 3396 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqElite8300CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 CMT dmi.product.sku: B0F38ET#UUW dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878037/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels
Awaiting final results for Bionic -main respin for SRU 2020.04.27 -- 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/1862588 Title: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-signed-oracle-5.0 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-signed-oracle-5.0 source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in linux-aws source package in Disco: New Status in linux-gcp source package in Disco: New Status in linux-signed-oracle-5.0 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Status in linux-signed-oracle-5.0 source package in Eoan: New Bug description: [Impact] Running seccomp kernel selftests will fail. [Test case] Run linux/tools/testing/selftests/seccomp/seccomp_bpf. On failure: seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic On success: [ RUN ] global.user_notification_basic [ OK ] global.user_notification_basic [Regression potential] The test is checking that the given structure which the kernel will write to is all zeroes. It's doing it because it wants userspace to have the possibility in the future to give data there indicating support for an extension that might be developed in the future. As the test is there right now, not applying the breaking uABI fix might cause us to miss applications that would break in future kernels. As the backport for that is prone for more regression potential, we are deciding to revert the new test. == Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64) [ RUN ] global.user_notification_basic seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic This cannot be reproduced with the kselftest in older kernel, probably a test case issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16 ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21 Uname: Linux 5.0.0-1011-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Mon Feb 10 05:17:54 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle-5.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878040] [NEW] Focal update: v5.4.40 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.4.40 upstream stable release from git://git.kernel.org/ vhost: vsock: kick send_pkt worker once device is started drm/bridge: analogix_dp: Split bind() into probe() and real bind() ASoC: topology: Check return value of soc_tplg_create_tlv ASoC: topology: Check return value of soc_tplg_*_create ASoC: topology: Check soc_tplg_add_route return value ASoC: topology: Check return value of pcm_new_ver ASoC: topology: Check return value of soc_tplg_dai_config selftests/ipc: Fix test failure seen after initial test run ASoC: sgtl5000: Fix VAG power-on handling ASoC: topology: Fix endianness issue usb: dwc3: gadget: Properly set maxpacket limit ASoC: rsnd: Fix parent SSI start/stop in multi-SSI mode ASoC: rsnd: Fix HDMI channel mapping for multi-SSI mode ASoC: codecs: hdac_hdmi: Fix incorrect use of list_for_each_entry remoteproc: qcom_q6v5_mss: fix a bug in q6v5_probe() drm/amdgpu: Correctly initialize thermal controller for GPUs with Powerplay table v0 (e.g Hawaii) wimax/i2400m: Fix potential urb refcnt leak net: stmmac: fix enabling socfpga's ptp_ref_clock net: stmmac: Fix sub-second increment ASoC: rsnd: Don't treat master SSI in multi SSI setup as parent ASoC: rsnd: Fix "status check failed" spam for multi-SSI cifs: protect updating server->dstaddr with a spinlock scripts/config: allow colons in option strings for sed cifs: do not share tcons with DFS tracing: Fix memory leaks in trace_events_hist.c lib/mpi: Fix building for powerpc with clang mac80211: sta_info: Add lockdep condition for RCU list usage net: bcmgenet: suppress warnings on failed Rx SKB allocations net: systemport: suppress warnings on failed Rx SKB allocations drm/i915: Extend WaDisableDARBFClkGating to icl,ehl,tgl sctp: Fix SHUTDOWN CTSN Ack in the peer restart case Revert "software node: Simplify software_node_release() function" hexagon: clean up ioremap hexagon: define ioremap_uc ALSA: hda: Match both PCI ID and SSID for driver blacklist x86/kvm: fix a missing-prototypes "vmread_error" platform/x86: GPD pocket fan: Fix error message when temp-limits are out of range ACPI: PM: s2idle: Fix comment in acpi_s2idle_prepare_late() mac80211: add ieee80211_is_any_nullfunc() cgroup, netclassid: remove double cond_resched libbpf: Fix readelf output parsing for Fedora mm/mremap: Add comment explaining the untagging behaviour of mremap() Revert "drm/amd/display: setting the DIG_MODE to the correct value." tools headers UAPI: Sync copy of arm64's asm/unistd.h with the kernel sources udp: document udp_rcv_segment special case for looped packets PM / devfreq: Add missing locking while setting suspend_freq Linux 5.4.40 UBUNTU: upstream stable to v5.4.40 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - 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: - 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.4.40 upstream stable release + from git://git.kernel.org/ -v5.4.40 upstream stable release -from git://git.kernel.org/ + vhost: vsock: kick send_pkt worker once device is started + drm/bridge: analogix_dp: Split bind() into probe() and real bind() +
[Kernel-packages] [Bug 1878037] [NEW] package linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 failed to install/upgrade: kunde inte skapa ny fil "/var/lib/dpkg/info/linux-modules-extra-5.4.0-29-gener
Public bug reported: Installed a new graphics card due to wrecked old Nvidia Quadro. The new graphic card is a Radeon RX 580, 8 GB GDDR5 and this is the fiorst startup of an Ubuntu 20.04 system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: linux-modules-5.4.0-29-generic:amd64: Install linux-image-5.4.0-29-generic:amd64: Install linux-modules-extra-5.4.0-29-generic:amd64: Install linux-image-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bandola1714 F pulseaudio CasperMD5CheckResult: skip Date: Thu May 7 06:51:23 2020 ErrorMessage: kunde inte skapa ny fil "/var/lib/dpkg/info/linux-modules-extra-5.4.0-29-generic.list-new": Operationen inte tillåten InstallationDate: Installed on 2019-03-10 (428 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: linux Title: package linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 failed to install/upgrade: kunde inte skapa ny fil "/var/lib/dpkg/info/linux-modules-extra-5.4.0-29-generic.list-new": Operationen inte tillåten UpgradeStatus: Upgraded to focal on 2020-04-23 (18 days ago) dmi.bios.date: 05/07/2012 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: K01 v02.05 dmi.board.name: 3396 dmi.board.vendor: Hewlett-Packard dmi.chassis.type: 3 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrK01v02.05:bd05/07/2012:svnHewlett-Packard:pnHPCompaqElite8300CMT:pvr:rvnHewlett-Packard:rn3396:rvr:cvnHewlett-Packard:ct3:cvr: dmi.product.family: 103C_53307F G=D dmi.product.name: HP Compaq Elite 8300 CMT dmi.product.sku: B0F38ET#UUW dmi.sys.vendor: Hewlett-Packard ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package 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/1878037 Title: package linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 failed to install/upgrade: kunde inte skapa ny fil "/var/lib/dpkg/info/linux- modules-extra-5.4.0-29-generic.list-new": Operationen inte tillåten Status in linux package in Ubuntu: New Bug description: Installed a new graphics card due to wrecked old Nvidia Quadro. The new graphic card is a Radeon RX 580, 8 GB GDDR5 and this is the fiorst startup of an Ubuntu 20.04 system. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 AptOrdering: linux-modules-5.4.0-29-generic:amd64: Install linux-image-5.4.0-29-generic:amd64: Install linux-modules-extra-5.4.0-29-generic:amd64: Install linux-image-generic:amd64: Install NULL: ConfigurePending Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: bandola1714 F pulseaudio CasperMD5CheckResult: skip Date: Thu May 7 06:51:23 2020 ErrorMessage: kunde inte skapa ny fil "/var/lib/dpkg/info/linux-modules-extra-5.4.0-29-generic.list-new": Operationen inte tillåten InstallationDate: Installed on 2019-03-10 (428 days ago) InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) IwConfig: eno1 no wireless extensions. lono wireless extensions. MachineType: Hewlett-Packard HP Compaq Elite 8300 CMT ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=/dev/mapper/ubuntu--gnome--vg-root ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: /usr/bin/python2.7, Python 2.7.18rc1, python-is-python2, 2.7.17-4 RelatedPackageVersions: grub-pc 2.04-1ubuntu26 RfKill: SourcePackage: linux Title: package linux-modules-extra-5.4.0-29-generic 5.4.0-29.33 failed
[Kernel-packages] [Bug 1873288] Re: wireguard-tools should NOT recommend wireguard-dkms
Indeed, install wireguard-tools on Focal doesn't pull the wireguard-dkms package. I believe only 2) and 3) from comment 9 remain to be addressed. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta in Ubuntu. https://bugs.launchpad.net/bugs/1873288 Title: wireguard-tools should NOT recommend wireguard-dkms Status in linux-meta package in Ubuntu: Fix Released Status in wireguard package in Ubuntu: Confirmed Bug description: With 20.04, the wireguard-dkms is not strictly needed as the wireguard.ko is now shipped with kernel packages. # apt-cache show wireguard-tools | grep Recommends Recommends: nftables | iptables, wireguard-dkms (>= 0.0.20191219) | wireguard-modules (>= 0.0.20171001) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta/+bug/1873288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877887] Re: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
** Description changed: I am encountering some very bizarre and difficult to reliably replicate issues. I am using a Focusrite Scarlett 2i2 USB audio interface, and am having a number of issues that I did not have in older version of ubuntu (these issues started occuring sometime in 19.04-19.10, can't remember which). I am having three major issues. Number one is, if USB autosuspend is enabled, it will stop working completely until reboot after anywhere from a few minutes to several hours. Reconnecting the device does not fix it and it seems to not power on at all, with dmesg reporting a "usb_set_interface failed -110" error. Sometimes this bug can be recreated by manually disconnecting and reconnecting the device, however I was unable to replicate it in this manner at the time of filing the bug. + + EDIT: Ignore the two more issue below, however I'm leaving them in the + post in case they end up being relevant. Another (presumably related) issue I am having is that if I reconnect the device and it doesn't fail, it outputs very crackly audio, as if the bitrate or sample rate were set incorrectly. This persists until a restart of pulseaudio. Previously, I had a similar bug where it would randomly start doing the crackly audio thing until reconnecting the device and in this case a restart of pulse did *not* fix the problem. I am unsure if this issue still happens as it was fairly rare. The third problem is that sometimes when performing a suspend/wake cycle, the interface will power cycle several times, in intervals of 15-30 seconds or so before staying on properly. As previously mentioned, these issues are fairly new and did not occur in older versions of ubuntu. I have confirmed that the audio interface works fine under windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 14:09:28 2020 InstallationDate: Installed on 2020-05-08 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB-Audio - microKEY-37 Symptom_PulseAudioLog: - + Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-08 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: - enp37s0 no wireless extensions. - - lono wireless extensions. + enp37s0 no wireless extensions. + + lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=6108192f-9dc3-480d-9a32-517609064dcd ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 RelatedPackageVersions: - linux-restricted-modules-5.4.0-29-generic N/A - linux-backports-modules-5.4.0-29-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-29-generic N/A + linux-backports-modules-5.4.0-29-generic N/A + linux-firmware1.187 RfKill: - + Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: sudo WifiSyslog: - + _MarkForUpload: True dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1847816] Re: storage autopkgtest always fails with linux-{kvm, azure, etc} kernels that don't include scsi_debug module
This bug was fixed in the package systemd - 229-4ubuntu21.28 --- systemd (229-4ubuntu21.28) xenial; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/t/storage: - fix buggy test (LP: #1831459) - without scsi_debug, skip test (LP: #1847816) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232-network-DHCP-ignore-error-in-setting-hostname-when-i.patch: - do not let invalid hostname break dhcpv4 (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:17:40 -0400 ** Changed in: systemd (Ubuntu Xenial) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1847816 Title: storage autopkgtest always fails with linux-{kvm,azure,etc} kernels that don't include scsi_debug module Status in autopkgtest-cloud: Fix Released Status in linux-kvm package in Ubuntu: New Status in systemd package in Ubuntu: Fix Released Status in linux-kvm source package in Xenial: New Status in systemd source package in Xenial: Fix Released Status in linux-kvm source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux-kvm source package in Disco: New Status in systemd source package in Disco: Won't Fix Status in linux-kvm source package in Eoan: New Status in systemd source package in Eoan: Fix Released Status in linux-kvm source package in Focal: New Status in systemd source package in Focal: Fix Released Bug description: Note: this bug touches on multiple packages: - autopkgtest-cloud: merge request open to install 'modules-extra' package - systemd: update autopkgtest to skip test if scsi_debug module isn't available (SRU template below is for this change) - linux-kvm: has CONFIG_SCSI_DEBUG unset, but would be good to have scsi_debug module built for this kernel [SRU template for systemd] [impact] the 'storage' autopkgtest requires the 'scsi_debug' module, and if it can't load it (and it's not built-in), the test fails. On some custom kernels, this module is included in the new 'linux-modules-extra-*' deb which isn't installed by default, so the test always fails when doing a reverse-dep autopkgtest using such a kernel's meta pkg. Additionally, some custom kernels, like linux-kvm, have SCSI_DEBUG disabled entirely; for those kernels, it will never be possible to load the scsi_debug module and the test should be skipped. [test case] run the 'storage' autopkgtest with a custom kernel that doesn't provide the scsi_debug module in the standard linux-modules deb, or check the autopkgtest.u.c history, for example: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-focal/focal/amd64/s/systemd/20191209_150835_237a5@/log.gz [regression potential] as this modifies one of the autopkgtest --setup-commands, a regression would most likely cause immediate test failure due to failing to install the proper linux-* debs. For the systemd 'storage' test change, this only skips the test if the scsi_debug module can't be loaded (and isn't already present, i.e. loaded or built-in). Any regression potential from that is low, but likely would involve incorrect test skips and/or missing valid problems due to skipping the test. [scope] systemd in all releases needs to have its 'storage' test updated To manage notifications about this bug go to: https://bugs.launchpad.net/autopkgtest-cloud/+bug/1847816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877154] 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 1877154 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/1877154 Title: [Nvidia HDMI] After suspend to ram sound output device changes from HDMI to S/PDIF Status in linux package in Ubuntu: Incomplete Bug description: After suspend to RAM sound device changes from default HDMI to S/PDIF. After changing it again to HDMI right speaker stops to respond. I can hear only the sound from left speaker during sound test from the settings menu. After the first wake from suspend you can find in messages from dmesg: [ 68.362807] pcieport :00:01.3: PME: Spurious native interrupt! [ 68.527845] nvme nvme0: 15/0/0 default/read/poll queues [ 68.533836] snd_hda_intel :0a:00.1: spurious response 0x8000:0x0, last cmd=0x6f2f03 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaroslaw 2972 F pulseaudio /dev/snd/controlC1: jaroslaw 2972 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 18:32:10 2020 InstallationDate: Installed on 2020-05-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [AB350N-Gaming WIFI, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875252] Re: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers
@Hui Wang (hui.wang) Verified. Applied the patch for regression by Kai-Heng Feng (kaihengfeng). Bug #1876238 (duplicate of bug #1875252). Dell Inspiron 1525. URL for the patch: https://launchpad.net/~kaihengfeng/+archive/ubuntu /fix-lp1869819 Audio is working fine now. Checked rebooting multiple times. No issues now. Thank you very much. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875252 Title: Ubuntu 20.04 LTS update causing no sound coming from built-in speakers Status in linux package in Ubuntu: Confirmed Bug description: After updating to Ubuntu 20.04 LTS, the only way of hearing audio is through headphones. The sound settings tab doesn't even show any other output option other than "Dummy output" . I have already checked other versions and everything works perfectly when I downgrade to Ubuntu 19.10, so I think this is a version related bug. Just to reiterate my laptop is a DELL Inspiron 14 3420.The sound card showing in alsamixer window is HDA Intel PCH, and the chip is Cirrus Logic CS4213. I have looked up solutions online for 2 days and none has worked. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: george 1499 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 19:04:06 2020 InstallationDate: Installed on 2020-04-26 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. Inspiron 3420 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=ec9a2552-c1da-44bd-9967-5be8bc6da075 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-26 (0 days ago) dmi.bios.date: 09/28/2012 dmi.bios.vendor: Dell Inc. dmi.bios.version: A05 dmi.board.name: 04XGDT dmi.board.vendor: Dell Inc. dmi.board.version: A05 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: Not Specified dmi.modalias: dmi:bvnDellInc.:bvrA05:bd09/28/2012:svnDellInc.:pnInspiron3420:pvrNotSpecified:rvnDellInc.:rn04XGDT:rvrA05:cvnDellInc.:ct8:cvrNotSpecified: dmi.product.name: Inspiron 3420 dmi.product.sku: To be filled by O.E.M. dmi.product.version: Not Specified dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776654] Re: systemd upstream sysusers tests fails
This bug was fixed in the package systemd - 237-3ubuntu10.40 --- systemd (237-3ubuntu10.40) bionic; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1839290-Change-job-mode-of-manager-triggered-restarts-to-JOB.patch: - when restarting service after failure, replace existing queued jobs (LP: #1839290) * d/p/lp1867421-70-mouse.hwdb-Set-DPI-for-MS-Classic-IntelliMouse.patch: - fix resolution of IntelliMouse (LP: #1867421) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/p/lp1862232/0001-network-add-more-log-messages-in-configuring-DHCP4-c.patch, d/p/lp1862232/0002-network-add-more-log-messages-in-configuring-DHCP6-c.patch, d/p/lp1862232/0003-network-also-check-that-Hostname-is-a-valid-DNS-doma.patch, d/p/lp1862232/0004-network-use-free_and_replace.patch, d/p/lp1862232/0005-network-DHCP-ignore-error-in-setting-hostname-when-i.patch, d/p/lp1862232/0006-man-mention-that-Hostname-for-DHCP-must-be-a-valid-D.patch, d/p/lp1862232/0007-resolve-fix-error-handling-of-dns_name_is_valid.patch: - do not fail network setup if hostname is not valid (LP: #1862232) * d/t/systemd-fsckd: Skip test on arm64 (LP: #1870194) * d/p/lp1870589-seccomp-rework-how-the-S-UG-ID-filter-is-installed.patch: - fix test-seccomp failure (LP: #1870589) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 10:12:49 -0400 ** Changed in: systemd (Ubuntu Bionic) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Released Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877154] Re: [Nvidia HDMI] After suspend to ram sound output device changes from HDMI to S/PDIF
Thanks! Upstream wrote 'There was a known regression in Nvidia HDMI, and it must have been fixed in the latest 5.7-rc. It might be that stable trees are still behind, so please check with the latest 5.7-rc.' So it could be a kernel issue ** Package changed: alsa-driver (Ubuntu) => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877154 Title: [Nvidia HDMI] After suspend to ram sound output device changes from HDMI to S/PDIF Status in linux package in Ubuntu: New Bug description: After suspend to RAM sound device changes from default HDMI to S/PDIF. After changing it again to HDMI right speaker stops to respond. I can hear only the sound from left speaker during sound test from the settings menu. After the first wake from suspend you can find in messages from dmesg: [ 68.362807] pcieport :00:01.3: PME: Spurious native interrupt! [ 68.527845] nvme nvme0: 15/0/0 default/read/poll queues [ 68.533836] snd_hda_intel :0a:00.1: spurious response 0x8000:0x0, last cmd=0x6f2f03 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaroslaw 2972 F pulseaudio /dev/snd/controlC1: jaroslaw 2972 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 18:32:10 2020 InstallationDate: Installed on 2020-05-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [AB350N-Gaming WIFI, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877154] [NEW] [Nvidia HDMI] After suspend to ram sound output device changes from HDMI to S/PDIF
You have been subscribed to a public bug: After suspend to RAM sound device changes from default HDMI to S/PDIF. After changing it again to HDMI right speaker stops to respond. I can hear only the sound from left speaker during sound test from the settings menu. After the first wake from suspend you can find in messages from dmesg: [ 68.362807] pcieport :00:01.3: PME: Spurious native interrupt! [ 68.527845] nvme nvme0: 15/0/0 default/read/poll queues [ 68.533836] snd_hda_intel :0a:00.1: spurious response 0x8000:0x0, last cmd=0x6f2f03 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jaroslaw 2972 F pulseaudio /dev/snd/controlC1: jaroslaw 2972 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed May 6 18:32:10 2020 InstallationDate: Installed on 2020-05-03 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:NVidia failed Symptom_Card: GP106 High Definition Audio Controller - HDA NVidia Symptom_Jack: Digital Out, HDMI Symptom_Type: None of the above Title: [AB350N-Gaming WIFI, Nvidia GPU 84 HDMI/DP, Digital Out, HDMI] Playback problem UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F50a dmi.board.asset.tag: Default string dmi.board.name: AB350N-Gaming WIFI-CF dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF50a:bd11/27/2019:svnGigabyteTechnologyCo.,Ltd.:pnAB350N-GamingWIFI:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnAB350N-GamingWIFI-CF:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: AB350N-Gaming WIFI dmi.product.sku: Default string dmi.product.version: Default string dmi.sys.vendor: Gigabyte Technology Co., Ltd. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- [Nvidia HDMI] After suspend to ram sound output device changes from HDMI to S/PDIF https://bugs.launchpad.net/bugs/1877154 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 1776654] Re: systemd upstream sysusers tests fails
This bug was fixed in the package systemd - 242-7ubuntu3.8 --- systemd (242-7ubuntu3.8) eoan; urgency=medium * d/t/logind: skip if nonexistent /sys/power/state (LP: #1862657) * d/p/lp1859862-network-Do-not-disable-IPv6-by-writing-to-sysctl.patch: - enable ipv6 when needed (LP: #1859862) * d/p/lp1858412-journalctl-allow-running-vacuum-on-remote-journals-t.patch: - allow vacuuming journal 'root' dir (LP: #1858412) * d/rules: use meson --print-errorlogs instead of cat testlog - (LP: #1870811) * d/p/lp1776654-test-Synchronize-journal-before-reading-from-it.patch: - sync journal before reading from it (LP: #1776654) * d/p/lp1837914-journal-do-not-trigger-assertion-when-journal_file_c.patch: - do not crash if NULL passted to journal destructor (LP: #1837914) * d/e/initramfs-tools/hooks/udev: - Follow symlinks when finding link files to copy into initramfs (LP: #1868892) -- Dan Streetman Mon, 20 Apr 2020 09:44:51 -0400 ** Changed in: systemd (Ubuntu Eoan) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Released Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776654] Update Released
The verification of the Stable Release Update for systemd has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776654 Title: systemd upstream sysusers tests fails Status in linux package in Ubuntu: Invalid Status in systemd package in Ubuntu: Fix Committed Status in linux source package in Bionic: Invalid Status in systemd source package in Bionic: Fix Committed Status in linux source package in Cosmic: Invalid Status in linux source package in Eoan: Invalid Status in systemd source package in Eoan: Fix Released Status in linux source package in Focal: Invalid Status in systemd source package in Focal: Fix Released Bug description: [impact] TEST-21-SYSUSERS autopkgtest fails [test case] see original description [regression potential] any regression would be limited to incorrect pass/fail of TEST-21-SYSUSERS [scope] TEST-21-SYSUSERS does not exist in Xenial, it is first contained in Bionic. This is needed for B, E, and F. [original description] https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-cosmic-canonical-kernel-team- bootstrap/cosmic/amd64/s/systemd/20180613_003352_38c07@/log.gz == TEST-21-SYSUSERS == make: Entering directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' TEST CLEANUP: Sysuser-related tests TEST SETUP: Sysuser-related tests TEST RUN: Sysuser-related tests *** Running test-1.input *** Running test-2.input *** Running test-3.input *** Running test-4.input *** Running test unhappy-1.input --- /var/tmp/systemd-test.TjNA7s/tmp/err 2018-06-13 00:22:12.805061468 + +++ unhappy-1.expected-err2018-01-28 15:58:17.0 + @@ -1 +1 @@ -Creating user xxx (n/a) with uid 312 and gid 310. +Failed to parse UID: '99': Numerical result out of range Unexpected error output for unhappy-1.input Creating user xxx (n/a) with uid 312 and gid 310. make: *** [run] Error 1 Makefile:4: recipe for target 'run' failed make: Leaving directory '/tmp/autopkgtest.phv1ss/build.sqb/src/test/TEST-21-SYSUSERS' FAILED TESTS: test/TEST-21-SYSUSERS autopkgtest [00:22:13]: test upstream: ---] upstream FAIL non-zero exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776654/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835660] Re: initramfs unpacking failed
Same problem here in Ubuntu (Focal) no matter the kernelversion, even with custom compiled kernels (wich is what I use) The problem was however easy fixed, as per earlier description, with changing compression by editing /etc/initramfs-tools/initramfs.conf to use gzip and then do "sudo update-initramfs -u". -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835660 Title: initramfs unpacking failed Status in initramfs-tools package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: "initramfs unpacking failed: Decoding failed", message appears on boot up. If I "update-initramfs" using gzip instead of lz, then boot up passes without decoding failed message. --- However, we currently believe that the decoding error reported in dmesg is actually harmless and has no impact on usability on the system. Switching from lz4 to gzip compression, simply papers over the warning, without any benefits, and slows down boot. Kernel should be fixed to correctly parse lz4 compressed initrds, or at least lower the warning, to not be user visible as an error. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1835660/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862588] Re: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag 'verification-needed-bionic' to 'verification-failed- bionic'. If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: verification-needed-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/1862588 Title: user_notification_basic in seccomp of ubuntu_kernel_selftest failed on Bionic-5.0 Kernels Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Invalid Status in linux-aws package in Ubuntu: New Status in linux-gcp package in Ubuntu: New Status in linux-signed-oracle-5.0 package in Ubuntu: New Status in linux source package in Bionic: Invalid Status in linux-aws source package in Bionic: New Status in linux-gcp source package in Bionic: New Status in linux-signed-oracle-5.0 source package in Bionic: New Status in linux source package in Disco: Fix Committed Status in linux-aws source package in Disco: New Status in linux-gcp source package in Disco: New Status in linux-signed-oracle-5.0 source package in Disco: New Status in linux source package in Eoan: Fix Committed Status in linux-aws source package in Eoan: New Status in linux-gcp source package in Eoan: New Status in linux-signed-oracle-5.0 source package in Eoan: New Bug description: [Impact] Running seccomp kernel selftests will fail. [Test case] Run linux/tools/testing/selftests/seccomp/seccomp_bpf. On failure: seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic On success: [ RUN ] global.user_notification_basic [ OK ] global.user_notification_basic [Regression potential] The test is checking that the given structure which the kernel will write to is all zeroes. It's doing it because it wants userspace to have the possibility in the future to give data there indicating support for an extension that might be developed in the future. As the test is there right now, not applying the breaking uABI fix might cause us to miss applications that would break in future kernels. As the backport for that is prone for more regression potential, we are deciding to revert the new test. == Issue found on Oracle Bionic 5.0 (oracle : 5.0.0-1011.16 : amd64) [ RUN ] global.user_notification_basic seccomp_bpf.c:3149:global.user_notification_basic:Expected -1 (18446744073709551615) == ret (0) seccomp_bpf.c:3150:global.user_notification_basic:Expected EINVAL (22) == errno (0) global.user_notification_basic: Test failed at step #3 [ FAIL ] global.user_notification_basic This cannot be reproduced with the kselftest in older kernel, probably a test case issue. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-1011-oracle 5.0.0-1011.16 ProcVersionSignature: User Name 5.0.0-1011.16-oracle 5.0.21 Uname: Linux 5.0.0-1011-oracle x86_64 ApportVersion: 2.20.9-0ubuntu7.10 Architecture: amd64 Date: Mon Feb 10 05:17:54 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-oracle-5.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1862588/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
Both fixes are in v4.19.0 and later ** Also affects: iproute2 (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: iproute2 (Ubuntu) Status: New => Fix Released ** Changed in: iproute2 (Ubuntu Bionic) Status: New => Triaged ** Changed in: iproute2 (Ubuntu Bionic) Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: iproute2 (Ubuntu) Assignee: Canonical Kernel Team (canonical-kernel-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: New Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873961] Re: tc filter show tcp_flags wrong mask value
** Changed in: iproute2 (Ubuntu) Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: ubuntu-power-systems Assignee: Canonical Server Team (canonical-server) => Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to iproute2 in Ubuntu. Matching subscriptions: iproute2 https://bugs.launchpad.net/bugs/1873961 Title: tc filter show tcp_flags wrong mask value Status in The Ubuntu-power-systems project: New Status in iproute2 package in Ubuntu: Fix Released Status in iproute2 source package in Bionic: Triaged Bug description: ---Problem Description--- Problem Descriptions "tc" utility does not show correct TC rule's tcp_flags mask correctly in current "iproute2" package shipped on Genesis. # dpkg -l |grep iproute2 ii iproute2 4.15.0-2ubuntu1 ppc64el networking and traffic control tools ---Steps to Reproduce--- Steps to reproduce the problem: 1) Add a tc rule to the testing VF (i.e. p0v2_r): # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 2 skip_sw action mirred egress redirect dev p0v0_r 2) Validate the added TC rule: # tc filter show dev p0v2_r root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 22 /* <--- Wrong */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen 3) If we add the tcp_flags using explicit mask 0x7: # tc filter add dev p0v2 protocol ip parent : pref 5 chain 1 handle 0x1 flower src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff ip_proto tcp tcp_flags 0x2/7 skip_sw action mirred egress redirect dev p0v0_r After that, using "tc filter show dev p0v2_r root" to verify, we still see the same output (tcp_flags 22) as shown in 2) above, which is wrong. Userspace tool common name: tc The userspace tool has the following bit modes: 64-bit Userspace package: iproute2 == Fixes: There are 2 patches to fix the issue: patch 1: commit b85076cd74e77538918d35992b1a9cd17ff86af8 Author: Stephen Hemminger Date: Tue Sep 11 08:29:33 2018 -0700 lib: introduce print_nl Common pattern in iproute commands is to print a line seperator in non-json mode. Make that a simple function. /* This patch declares global variable "const char *_SL_ = "\n";" in lib/utils.c to be used by 2nd patch */ patch 2: commit e8bd395508cead5a81c2bebd9d3705a9e41ea8bc Author: Keara Leibovitz Date: Thu Jul 26 09:45:30 2018 -0400 tc: fix bugs for tcp_flags and ip_attr hex output Fix hex output for both the ip_attr and tcp_flags print functions. With the above 2 patches pull in, the new "tc" utility will show the correct tcp_flags mask: # tc filter show dev p0v2 root filter protocol ip pref 5 flower chain 1 filter protocol ip pref 5 flower chain 1 handle 0x1 src_mac 00:00:00:00:4e:2f/00:00:00:ff:ff:ff eth_type ipv4 ip_proto tcp tcp_flags 0x2/7 /* <--- Correct */ skip_sw in_hw action order 1: mirred (Egress Redirect to device p0v0_r) stolen This bug affects tc in Ubuntu 18.04.1 stock image. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1873961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861070] Re: Raspberry Pi 4B: USB OTG is not working
** Also affects: linux-raspi (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux-raspi (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux-raspi (Ubuntu Eoan) ** No longer affects: linux-raspi2 (Ubuntu Focal) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861070 Title: Raspberry Pi 4B: USB OTG is not working Status in linux-raspi package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: Triaged Status in linux-raspi2 source package in Eoan: Fix Released Status in linux-raspi source package in Focal: New Bug description: [Impact] On the RPI4B board, the usb-c power port could also work as a USB OTG mode, but we set the dwc2 driver to the host mode unconditionally, now set it to dual_role mode, then it could work in host/otg/peripheal mode. [Fix] Set USB_DWC2_DUAL_ROLE=y, USB_DWC2_HOST=n [Test Case] set the dtoverlay=dwc2,dr_mode=[otg|peripheral] in the config.txt, and isnmod the g_ether or g_cdc, on the host machine, we could see RPI4B work as a usb device. Because physical port limitation, could test dr_mode=host. [Regression Risk] Low, our eoan kernel choose dwc_otg driver for this port by default, very very few users will choose dwc2 driver, and the dwc2 driver is not enabled by default in our kernel. And bug reporter and I already tested that the peripheral mode works after this change. I am using Raspberry Pi 4B (4GB) and want to make use of the OTG functionality (g_ether). I cross checked with Raspbian to make sure it is not a hardware issue. Extract from dmesg of Ubuntu 19.10.1 with latest updates applied as of Jan 26th, 2020 via "apt-get update" and "apt-get full-upgrade": ... [1.514262] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [1.517365] dwc_otg: FIQ enabled [1.517376] dwc_otg: NAK holdoff enabled [1.517386] dwc_otg: FIQ split-transaction FSM enabled [1.517399] Module dwc_common_port init ... [6.358332] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [6.358388] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [6.358545] dwc2 fe98.usb: Configuration mismatch. dr_mode forced to host [6.409098] dwc2 fe98.usb: DWC OTG Controller [6.409399] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [6.409432] dwc2 fe98.usb: irq 23, io mem 0xfe98 ... [ 111.796714] udc-core: couldn't find an available UDC - added [g_ether] to list of pending drivers I think it is that "Configuration mismatch. dr_mode forced to host" log entry telling me that the port is acting as HOST mode instead of OTG mode. I have try putting these in usercfg.txt "dtoverlay=dwc2" "dtoverlay=dwc2,dr_mode=otg" "dtoverlay=dwc2,dr_mode=peripheral" and it will give the same result, no OTG functionality. On the same hardware running Raspbian Buster, it initialise successfully. Corresponding dmesg: ... [0.567531] dwc_otg: version 3.00a 10-AUG-2012 (platform bus) [0.570391] dwc_otg: FIQ enabled [0.570400] dwc_otg: NAK holdoff enabled [0.570409] dwc_otg: FIQ split-transaction FSM enabled [0.570421] Module dwc_common_port init ... [2.507634] dwc2 fe98.usb: fe98.usb supply vusb_d not found, using dummy regulator [2.511011] dwc2 fe98.usb: Linked as a consumer to regulator.0 [2.514450] dwc2 fe98.usb: fe98.usb supply vusb_a not found, using dummy regulator [2.731860] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm=1 [2.735511] dwc2 fe98.usb: dwc2_check_params: Invalid parameter lpm_clock_gating=1 [2.735522] dwc2 fe98.usb: dwc2_check_params: Invalid parameter besl=1 [2.735533] dwc2 fe98.usb: dwc2_check_params: Invalid parameter hird_threshold_en=1 [2.735582] dwc2 fe98.usb: EPs: 8, dedicated fifos, 4080 entries in SPRAM [2.752511] dwc2 fe98.usb: DWC OTG Controller [2.752554] dwc2 fe98.usb: new USB bus registered, assigned bus number 3 [2.752601] dwc2 fe98.usb: irq 36, io mem 0xfe98 ... [2.848843] g_ether gadget: Ethernet Gadget, version: Memorial Day 2008 [2.851601] g_ether gadget: g_ether ready [2.854580] dwc2 fe98.usb: bound driver g_ether [2.998525] dwc2 fe98.usb: new device is high-speed [3.075025] dwc2 fe98.usb: new device is high-speed [3.139338] dwc2 fe98.usb: new address 10 [3.154010] g_ether gadget: high-speed config #1: CDC Ethernet (ECM) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1861070/+subscriptions -- Mailing
[Kernel-packages] [Bug 1874257] Re: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS
Yeah Dan, thanks for chiming in. In particular that would be at least (but not lmited to) the changes: 8.04 Rework DTLS MTU detection. (#10) 7.08 Support automatic DTLS MTU detection with OpenSSL. 7.07 Automatic DTLS MTU detection. Ubuntu has these newer versions. Bionic 18.04 is on 7.08 and the most recent LTS Focal is at 8.05. The current development release is at the latest 8.09 of openconnect. These are new features added in 7.07 and 7.08 - IMHO they do not qualify for a SRU release into Xenial [1] - especially since you can "get away" with a config change that mitigates the issue. [1]: https://wiki.ubuntu.com/StableReleaseUpdates ** Also affects: openssh (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: openconnect (Ubuntu Xenial) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Xenial) ** No longer affects: openssh (Ubuntu Xenial) ** Changed in: openssh (Ubuntu) Status: Confirmed => Invalid ** Changed in: openconnect (Ubuntu Xenial) Status: New => Confirmed ** Changed in: openconnect (Ubuntu) Status: Confirmed => Fix Released ** Changed in: openconnect (Ubuntu Xenial) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874257 Title: SSH fails with connection timed out - in VPN and hangs here "expecting SSH2_MSG_KEX_ECDH_REPLY" + Ubuntu 16.04.6 LTS Status in linux package in Ubuntu: Invalid Status in openconnect package in Ubuntu: Fix Released Status in openssh package in Ubuntu: Invalid Status in openconnect source package in Xenial: Confirmed Bug description: Hello Team, SSH timeout issue, once connect to VPN. Environment == Dell XPS 9570 Ubuntu 16.04.6 Xenial Xerus) kernel - 4.15.0-55-generic $dpkg -l | grep -i openssh ii openssh-client 1:7.2p2-4ubuntu2.8 --> ii openssh-server 1:7.2p2-4ubuntu2.8 ii openssh-sftp-server 1:7.2p2-4ubuntu2.8 VPN tunnel info vpn0 Link encap:UNSPEC HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 inet addr:IP P-t-P:xx Mask:255.255.252.0 inet6 addr: fe80::b8e2:bea4:2e62:fe08/64 Scope:Link UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1406 Metric:1 RX packets:962 errors:0 dropped:0 overruns:0 frame:0 TX packets:1029 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:87839 (87.8 KB) TX bytes:238740 (238.7 KB) Issue Unable to connect to any host via ssh or sftp after VPN connection Tried = Reinstalled the openssh-client package and still no luck. May I know why the default cipher is not taking/hanging? Please let me know . There were no recent changes. Workaround === Able to connect to ssh / sftp $ssh -c aes128-ctr user@IP Below is the debug ssh client logs === == $ssh -vvv user@ip OpenSSH_7.2p2 Ubuntu-4ubuntu2.8, OpenSSL 1.0.2g 1 Mar 2016 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: resolving "IP" port 22 debug2: ssh_connect_direct: needpriv 0 debug1: Connecting to IP [IP] port 22. debug1: Connection established. debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_rsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_dsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ecdsa-cert type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519 type -1 debug1: key_load_public: No such file or directory debug1: identity file /home/user/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_7.2p2 Ubuntu-4ubuntu2.8 debug1: Remote protocol version 2.0, remote software version OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 debug1: match: OpenSSH_7.6p1 Ubuntu-4ubuntu0.3 pat OpenSSH* compat 0x0400 debug2: fd 3 setting O_NONBLOCK debug1: Authenticating to IP:22 as 'user' debug3: send packet: type 20 debug1: SSH2_MSG_KEXINIT sent debug3: receive packet: type 20 debug1: SSH2_MSG_KEXINIT received debug2: local client KEXINIT proposal debug2: KEX algorithms:
[Kernel-packages] [Bug 1877422] Re: Wifi is not showing on my HP 15s 0091tu laptop
I'm having the same experience. I thought it might be a duplicate of 1838133 (a regression in this case, since that one has been fixed). My wireless adapter is an RTL8822BE which shows up in lspci and lshw -C network, although under the 5.4.0-28 kernel lshw shows it as disabled (it appears to work for a few seconds after startup). dsmeg shows some issues with changing the power mode of the device although I am too much of a noob to understand it. The issue is also present in the 20.04 live CD. In this case Wifi is initially working and I can see wireless networks, but as soon as a I connect to a network it dissappears. Rolling back to 19.10 under kernel 5.3.0.51 fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877422 Title: Wifi is not showing on my HP 15s 0091tu laptop Status in linux package in Ubuntu: Confirmed Bug description: Wireless network is not showing on my HP 15s 0091tu laptop. I have installed rtl8822be wifi driver and insecure the boot mode. Still its not showing after restart ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-29-generic 5.4.0-29.33 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: tanvir 1432 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu May 7 23:14:04 2020 InstallationDate: Installed on 2020-04-28 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: ppp0 no wireless extensions. eno1 no wireless extensions. lono wireless extensions. Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0408:5365 Quanta Computer, Inc. HP TrueVision HD Camera Bus 001 Device 002: ID 09da:2403 A4Tech Co., Ltd. 2.4G Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: HP HP Laptop 15s-du0xxx ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=a808b44a-d509-4cd9-a034-d16a74acf3ef ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-29-generic N/A linux-backports-modules-5.4.0-29-generic N/A linux-firmware1.187 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/22/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.05 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85EF dmi.board.vendor: HP dmi.board.version: 36.19 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.05:bd03/22/2019:svnHP:pnHPLaptop15s-du0xxx:pvrType1ProductConfigId:rvnHP:rn85EF:rvr36.19:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15s-du0xxx dmi.product.sku: 7NH34PA#UUF dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1877422/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877575] Re: kernel crash with 0010:ovl_open_realfile+0x4a/0x150 [overlay] in Qemu with focal daily
This is reported against 5.4.0-30.34 (in the guest I assume). Per [1] that date window is the change from 2020-05-08 12:58:43 Published Focal proposedmaindevel 5.4.0-31.35 2020-05-08 13:00:19 Superseded Focal proposedmaindevel 5.4.0-30.34 2020-05-05 12:18:15 Published Focal securitymaindevel 5.4.0-29.33 2020-05-04 19:13:24 Published Focal updates maindevel 5.4.0-29.33 Given the crash it is either the new proposed kernel if it is in there or something in how the overlayfs is created (that is where the crashes are). I checked myself the images from [2][3][4] and they all worked for me. This boots for example: $ sudo qemu-system-x86_64 -m 1024 -cpu host -smp 4 -enable-kvm -hda focal-server-cloudimg-amd64-20200507.img -boot d -curses @Jobel/Paride - could you add which images and which commandline you used? [1]: https://launchpad.net/ubuntu/+source/linux/+publishinghistory [2]: https://cloud-images.ubuntu.com/focal/20200505/focal-server-cloudimg-amd64.img [3]: https://cloud-images.ubuntu.com/focal/20200506/focal-server-cloudimg-amd64.img [4]: https://cloud-images.ubuntu.com/focal/20200507/focal-server-cloudimg-amd64.img ** Changed in: qemu (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/1877575 Title: kernel crash with 0010:ovl_open_realfile+0x4a/0x150 [overlay] in Qemu with focal daily Status in linux package in Ubuntu: Confirmed Status in qemu package in Ubuntu: Incomplete Bug description: Focal daily 20200507 (started earlier) Kernel is 5.4.0-30.34 Kernel crashes on boot in Qemu with: [4.019922] RIP: 0010:ovl_open_realfile+0x4a/0x150 [overlay] [4.022101] Code: 44 8b 6f 40 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 49 8b 7e 28 41 81 cd 00 00 04 04 e8 9d d4 ff ff 49 89 c7 48 8b 45 c8 <48> 8b 40 68 48 81 78 60 62 6a 65 6a 0f 84 a6 00 00 00 65 48 8b 04 [4.027487] RSP: 0018:ac44c0707c08 EFLAGS: 00010202 [4.029424] RAX: 0f230ca096f12900 RBX: 9e44e9c2eaa0 RCX: 0001 [4.031645] RDX: 9e44ea9ae540 RSI: 9e44e9c2eaa0 RDI: 9e44fb281f00 [4.033811] RBP: ac44c0707c50 R08: 9e44e9e3cc00 R09: [4.036428] R10: 9e44ea9ae540 R11: R12: 9e44f9ec9c00 [4.038737] R13: 04048002 R14: 9e44eaa51b00 R15: 9e44e9e3cc00 [4.046087] FS: 7f91962a6600() GS:9e44fbb0() knlGS: [4.051277] CS: 0010 DS: ES: CR0: 80050033 [4.055455] CR2: 56295fbc4a59 CR3: 000169c8 CR4: 06e0 [4.059614] general protection fault: [#4] SMP NOPTI [4.061700] CPU: 1 PID: 360 Comm: cp Tainted: G D 5.4.0-30-generic #34-Ubuntu [4.063016] Hardware name: QEMU Standard PC (Q35 + ICH9, 2009), BIOS 1.13.0-1ubuntu1 04/01/2014 [4.063016] RIP: 0010:ovl_open_realfile+0x4a/0x150 [overlay] [4.063016] Code: 44 8b 6f 40 65 48 8b 04 25 28 00 00 00 48 89 45 d0 31 c0 49 8b 7e 28 41 81 cd 00 00 04 04 e8 9d d4 ff ff 49 89 c7 48 8b 45 c8 <48> 8b 40 68 48 81 78 60 62 6a 65 6a 0f 84 a6 00 00 00 65 48 8b 04 [4.063016] RSP: 0018:ac44c0373c08 EFLAGS: 00010206 [4.063016] RAX: 1579f0d048c0c300 RBX: 9e44eaa3f478 RCX: [4.063016] RDX: RSI: 9e44eaa3f478 RDI: 9e44fb281f00 [4.063016] RBP: ac44c0373c50 R08: 9e44fb3ac6c0 R09: [4.063016] R10: 0001 R11: 007461642e73 R12: 9e44f9b2d700 [4.063016] R13: 04048000 R14: 9e44fa3d65c0 R15: 9e44fb3ac6c0 [4.063016] FS: 7f91962a6600() GS:9e44fbb0() knlGS: [4.063016] CS: 0010 DS: ES: CR0: 80050033 [4.063016] CR2: 56295fbc4a59 CR3: 000169c8 CR4: 06e0 [4.063016] Call Trace: [4.063016] ? ovl_llseek+0x120/0x120 [overlay] [4.063016] ovl_open+0x57/0x90 [overlay] [4.063016] do_dentry_open+0x143/0x3a0 [4.063016] vfs_open+0x2d/0x30 [4.063016] do_last+0x194/0x900 [4.063016] path_openat+0x8d/0x290 [4.063016] do_filp_open+0x91/0x100 [4.063016] ? __alloc_fd+0x46/0x150 [4.063016] do_sys_open+0x17e/0x290 [4.063016] __x64_sys_openat+0x20/0x30 [4.124120] do_syscall_64+0x57/0x190 [4.124120] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [4.124120] RIP: 0033:0x7f91961c3d1b [4.124120] Code: 25 00 00 41 00 3d 00 00 41 00 74 4b 64 8b 04 25 18 00 00 00 85 c0 75 67 44 89 e2 48 89 ee bf 9c ff ff ff b8 01 01 00 00 0f 05 <48> 3d 00 f0 ff ff 0f 87 91 00 00 00 48 8b 4c 24 28 64 48 33 0c 25 [4.124120] RSP: 002b:7ffebc71f1b0 EFLAGS: 0246 ORIG_RAX: 0101 [4.124120] RAX:
[Kernel-packages] [Bug 1877887] Re: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while
> Does using the snd_hda_intel.power_save=0 kernel option makes a difference to the sound cracking issue? (https://wiki.ubuntu.com/Kernel/KernelBootParameters). It does not appear to make a difference. > Also by USB suspend do you mean btusb.enable_autosuspend=y/n ? I set usbcore.autosuspend=-1 in the kernel parameters. However I'm not entirely sure it's fixed the issue, as sometimes it can take quite a long time to pop up. It has not happened since I disabled it, and have had about 12 of uptime since. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1877887 Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while Status in linux package in Ubuntu: Confirmed Bug description: I am encountering some very bizarre and difficult to reliably replicate issues. I am using a Focusrite Scarlett 2i2 USB audio interface, and am having a number of issues that I did not have in older version of ubuntu (these issues started occuring sometime in 19.04-19.10, can't remember which). I am having three major issues. Number one is, if USB autosuspend is enabled, it will stop working completely until reboot after anywhere from a few minutes to several hours. Reconnecting the device does not fix it and it seems to not power on at all, with dmesg reporting a "usb_set_interface failed -110" error. Sometimes this bug can be recreated by manually disconnecting and reconnecting the device, however I was unable to replicate it in this manner at the time of filing the bug. Another (presumably related) issue I am having is that if I reconnect the device and it doesn't fail, it outputs very crackly audio, as if the bitrate or sample rate were set incorrectly. This persists until a restart of pulseaudio. Previously, I had a similar bug where it would randomly start doing the crackly audio thing until reconnecting the device and in this case a restart of pulse did *not* fix the problem. I am unsure if this issue still happens as it was fairly rare. The third problem is that sometimes when performing a suspend/wake cycle, the interface will power cycle several times, in intervals of 15-30 seconds or so before staying on properly. As previously mentioned, these issues are fairly new and did not occur in older versions of ubuntu. I have confirmed that the audio interface works fine under windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip Date: Sun May 10 14:09:28 2020 InstallationDate: Installed on 2020-05-08 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_Card: USB-Audio - microKEY-37 Symptom_PulseAudioLog: Symptom_Type: Sound works for a while, then breaks Title: [USB-Audio - Scarlett 2i2 USB, playback] fails after a while UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/19/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P5.40 dmi.board.name: AB350 Gaming K4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP5.40:bd12/19/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnAB350GamingK4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.sku: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-08 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) IwConfig: enp37s0 no wireless extensions. lono wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-29-generic root=UUID=6108192f-9dc3-480d-9a32-517609064dcd ro rootflags=subvol=@ quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 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: Tags: focal Uname:
[Kernel-packages] [Bug 1690085]
Hi folks! For those who are looking for a solution or already found a solution, there is a new update of AGESA rolling out. The new version 1.0.0.4 claims: * Improved system stability when switching through ACPI power states. It has arrived on my Asus PRIME B350M days ago, I have upgraded and kept default optimised BIOS settings. When I used ZenState to check cpu status, the C6 state is now: C6 State - Package - Enabled C6 State - Core - Disabled Previously they were all enabled, I guessed the new AGESA release finally solved this problem from source? I will report back days later to see if the system still hangs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Expired Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty