[Kernel-packages] [Bug 1889926] Re: Can't access gpio mapped memory on focal armhf server on pi
** Also affects: linux-raspi (Ubuntu Focal)
Importance: Undecided
Status: New
** Changed in: linux-raspi (Ubuntu)
Status: New => Invalid
** Changed in: linux-raspi (Ubuntu Focal)
Status: New => Triaged
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi in Ubuntu.
https://bugs.launchpad.net/bugs/1889926
Title:
Can't access gpio mapped memory on focal armhf server on pi
Status in linux-raspi package in Ubuntu:
Invalid
Status in linux-raspi source package in Focal:
Triaged
Bug description:
On released (and apt updated) 20.04 armhf preinstalled server on
Pi3B+, we cannot use pigpio C program to access memory map for gpio.
Customer says the same code works fine on 18.04.
ubuntu@ubuntu:~$ sudo ./pigpio/kyle.o
2020-07-31 18:36:11 initPeripherals: mmap gpio failed (Operation not
permitted)
Details on code below, but the executable is attached, and the
customer says this fairly represents their code usage.
ubuntu@ubuntu:~/pigpio$ uname -a
Linux ubuntu 5.4.0-1015-raspi #15-Ubuntu SMP Fri Jul 10 05:37:25 UTC 2020
armv7l armv7l armv7l GNU/Linux
We thought perhaps these kernel configs were involved:
CONFIG_DEVMEM=y
CONFIG_ARCH_HAS_DEVMEM_IS_ALLOWED=y
CONFIG_STRICT_DEVMEM=y
... and we modified the kernel cmdline with the following, but the result was
the same.
iomem=relaxed strict-devmem=0
The program is simply this https://github.com/joan2937/pigpio/ with make &
make install
then this c file:
#include
#include
#include
int main(void){
gpioInitialise();
}
built with gcc -Wall -I/home/ubuntu/pigpio -pthread -o kyle.o kyle.c
-lpigpio -lrt
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/1889926/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
To add to above: When the error is on, running `sudo lshw` causes the program to hang: fox:~% sudo lshw USB<-- program hang like 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/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Incomplete Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856608] Re: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad?
I can confirm this issue in 20.04 linux-image-5.4.0-42. This message only appear for my usb3.1 gen1 type-c hub when it is connected on boot. If I re-plug the hub after boot, the message stops. It doesn't appear for another connected usb3 type-a hub. In /var/log/syslog, it prints every 4 seconds: Aug 3 01:57:37 fox kernel: [ 6020.600964] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Aug 3 01:57:41 fox kernel: [ 6024.672925] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Aug 3 01:57:45 fox kernel: [ 6028.744888] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Aug 3 01:57:49 fox kernel: [ 6032.816854] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856608 Title: [Regression] usb usb2-port2: Cannot enable. Maybe the USB cable is bad? Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Incomplete Bug description: This appears to be a regression between 4.15.0-70.79 and 4.15.0-72.81. This bug was fixed by simply reverting the offending change. Bug 1859873 tracks root causing the issue and reapplying the change w/ any necessary fixes. [Impact] USB port unusable and boot time takes ~5 minutes longer to complete. Kernel emits messages like: usb usb2-port2: Cannot enable. Maybe the USB cable is bad? [Test Case] dmesg | grep "Cannot enable" [Fix] [Regression Risk] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856608/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890096] Re: Realtek RTL8822BE [10ec:b822] subsystem [103c:831b] purge skb(s) not reported by firmware
** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Assignee: (unassigned) => You-Sheng Yang (vicamo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890096 Title: Realtek RTL8822BE [10ec:b822] subsystem [103c:831b] purge skb(s) not reported by firmware Status in linux package in Ubuntu: Confirmed Bug description: Aug 03 00:35:20 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:21 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:24 kernel: rtw_pci :01:00.0: failed to send h2c command Aug 03 00:35:37 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:40 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:40 kernel: rtw_pci :01:00.0: firmware failed to restore hardware setting Aug 03 00:35:41 kernel: [ cut here ] Aug 03 00:35:41 kernel: purge skb(s) not reported by firmware Aug 03 00:35:41 kernel: WARNING: CPU: 7 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:162 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Aug 03 00:35:41 kernel: Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_hd> Aug 03 00:35:41 kernel: wmi_bmof videodev dell_wmi_descriptor drm_kms_helper ucsi_acpi mei_me mc processor_thermal_device i2c_algo_bit hid_multitouch typec_ucsi fb_sys_fops intel_rapl_common ecdh_gener> Aug 03 00:35:41 kernel: CPU: 7 PID: 0 Comm: swapper/7 Not tainted 5.4.0-42-generic #46-Ubuntu Aug 03 00:35:41 kernel: Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 Aug 03 00:35:41 kernel: RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Aug 03 00:35:41 kernel: Code: 0f 1f 44 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 98 e9 1d c1 e8 f6 16 d4 c9 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 dd 5c 77 ca 48> Aug 03 00:35:41 kernel: RSP: 0018:ba0d00288e48 EFLAGS: 00010286 Aug 03 00:35:41 kernel: RAX: RBX: a0c7a03097f8 RCX: 0006 Aug 03 00:35:41 kernel: RDX: 0007 RSI: 0082 RDI: a0c7a75d78c0 Aug 03 00:35:41 kernel: RBP: ba0d00288e60 R08: 03c4 R09: 0004 Aug 03 00:35:41 kernel: R10: R11: 0001 R12: a0c7a75dba80 Aug 03 00:35:41 kernel: R13: a0c7a03097f8 R14: c1160090 R15: a0c7a03097f8 Aug 03 00:35:41 kernel: FS: () GS:a0c7a75c() knlGS: Aug 03 00:35:41 kernel: CS: 0010 DS: ES: CR0: 80050033 Aug 03 00:35:41 kernel: CR2: 7fc77dfd4000 CR3: 00024e80a003 CR4: 003606e0 Aug 03 00:35:41 kernel: Call Trace: Aug 03 00:35:41 kernel: Aug 03 00:35:41 kernel: call_timer_fn+0x32/0x130 Aug 03 00:35:41 kernel: __run_timers.part.0+0x180/0x280 Aug 03 00:35:41 kernel: ? timerqueue_add+0x9b/0xb0 Aug 03 00:35:41 kernel: ? enqueue_hrtimer+0x3d/0x90 Aug 03 00:35:41 kernel: ? recalibrate_cpu_khz+0x10/0x10 Aug 03 00:35:41 kernel: ? ktime_get+0x3e/0xa0 Aug 03 00:35:41 kernel: run_timer_softirq+0x2a/0x50 Aug 03 00:35:41 kernel: __do_softirq+0xe1/0x2d6 Aug 03 00:35:41 kernel: ? hrtimer_interrupt+0x13b/0x220 Aug 03 00:35:41 kernel: irq_exit+0xae/0xb0 Aug 03 00:35:41 kernel: smp_apic_timer_interrupt+0x7b/0x140 Aug 03 00:35:41 kernel: apic_timer_interrupt+0xf/0x20 Aug 03 00:35:41 kernel: Aug 03 00:35:41 kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Aug 03 00:35:41 kernel: Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 12 6c 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d> Aug 03 00:35:41 kernel: RSP: 0018:ba0d00113e38 EFLAGS: 0246 ORIG_RAX: ff13 Aug 03 00:35:41 kernel: RAX: a0c7a75ead00 RBX: 8c559c00 RCX: 001f Aug 03 00:35:41 kernel: RDX: RSI: 471c7c22 RDI: Aug 03 00:35:41 kernel: RBP: ba0d00113e78 R08: 01e6725fec9b R09: 0001 Aug 03 00:35:41 kernel: R10: a0c7a75e9a00 R11: a0c7a75e99e0 R12: a0c7a75f5700 Aug 03 00:35:41 kernel: R13: 0006 R14: 0006 R15: a0c7a75f5700 Aug 03 00:35:41 kernel: ? cpuidle_enter_state+0xa1/0x450 Aug 03 00:35:41 kernel: cpuidle_enter+0x2e/0x40 Aug 03 00:35:41 kernel: call_cpuidle+0x23/0x40 Aug 03 00:35:41 kernel: do_idle+0x1dd/0x270 Aug 03 00:35:41 kernel: cpu_startup_entry+0x20/0x30 Aug 03 00:35:41 kernel: start_secondary+0x167/0x1c0 Aug 03 00:35:41 kernel: secondary_startup_64+0xa4/0xb0 Aug 03 00:35:41 kernel: ---[ end trace fc1e06321e14fd73 ]--- Aug
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
** Changed in: linux (Ubuntu) Assignee: (unassigned) => koba (kobako) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: Confirmed Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890096] Re: Realtek RTL8822BE [10ec:b822] subsystem [103c:831b] purge skb(s) not reported by firmware
Looks like it's a duplicate of already expired bug 1850502. Since I'm able to reproduce this by playing YouTube video streaming, I'm to set that bug as a duplicate of this instead. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1890096 Title: Realtek RTL8822BE [10ec:b822] subsystem [103c:831b] purge skb(s) not reported by firmware Status in linux package in Ubuntu: New Bug description: Aug 03 00:35:20 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:21 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:24 kernel: rtw_pci :01:00.0: failed to send h2c command Aug 03 00:35:37 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:40 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:40 kernel: rtw_pci :01:00.0: firmware failed to restore hardware setting Aug 03 00:35:41 kernel: [ cut here ] Aug 03 00:35:41 kernel: purge skb(s) not reported by firmware Aug 03 00:35:41 kernel: WARNING: CPU: 7 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:162 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Aug 03 00:35:41 kernel: Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_hd> Aug 03 00:35:41 kernel: wmi_bmof videodev dell_wmi_descriptor drm_kms_helper ucsi_acpi mei_me mc processor_thermal_device i2c_algo_bit hid_multitouch typec_ucsi fb_sys_fops intel_rapl_common ecdh_gener> Aug 03 00:35:41 kernel: CPU: 7 PID: 0 Comm: swapper/7 Not tainted 5.4.0-42-generic #46-Ubuntu Aug 03 00:35:41 kernel: Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 Aug 03 00:35:41 kernel: RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Aug 03 00:35:41 kernel: Code: 0f 1f 44 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 98 e9 1d c1 e8 f6 16 d4 c9 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 dd 5c 77 ca 48> Aug 03 00:35:41 kernel: RSP: 0018:ba0d00288e48 EFLAGS: 00010286 Aug 03 00:35:41 kernel: RAX: RBX: a0c7a03097f8 RCX: 0006 Aug 03 00:35:41 kernel: RDX: 0007 RSI: 0082 RDI: a0c7a75d78c0 Aug 03 00:35:41 kernel: RBP: ba0d00288e60 R08: 03c4 R09: 0004 Aug 03 00:35:41 kernel: R10: R11: 0001 R12: a0c7a75dba80 Aug 03 00:35:41 kernel: R13: a0c7a03097f8 R14: c1160090 R15: a0c7a03097f8 Aug 03 00:35:41 kernel: FS: () GS:a0c7a75c() knlGS: Aug 03 00:35:41 kernel: CS: 0010 DS: ES: CR0: 80050033 Aug 03 00:35:41 kernel: CR2: 7fc77dfd4000 CR3: 00024e80a003 CR4: 003606e0 Aug 03 00:35:41 kernel: Call Trace: Aug 03 00:35:41 kernel: Aug 03 00:35:41 kernel: call_timer_fn+0x32/0x130 Aug 03 00:35:41 kernel: __run_timers.part.0+0x180/0x280 Aug 03 00:35:41 kernel: ? timerqueue_add+0x9b/0xb0 Aug 03 00:35:41 kernel: ? enqueue_hrtimer+0x3d/0x90 Aug 03 00:35:41 kernel: ? recalibrate_cpu_khz+0x10/0x10 Aug 03 00:35:41 kernel: ? ktime_get+0x3e/0xa0 Aug 03 00:35:41 kernel: run_timer_softirq+0x2a/0x50 Aug 03 00:35:41 kernel: __do_softirq+0xe1/0x2d6 Aug 03 00:35:41 kernel: ? hrtimer_interrupt+0x13b/0x220 Aug 03 00:35:41 kernel: irq_exit+0xae/0xb0 Aug 03 00:35:41 kernel: smp_apic_timer_interrupt+0x7b/0x140 Aug 03 00:35:41 kernel: apic_timer_interrupt+0xf/0x20 Aug 03 00:35:41 kernel: Aug 03 00:35:41 kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Aug 03 00:35:41 kernel: Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 12 6c 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d> Aug 03 00:35:41 kernel: RSP: 0018:ba0d00113e38 EFLAGS: 0246 ORIG_RAX: ff13 Aug 03 00:35:41 kernel: RAX: a0c7a75ead00 RBX: 8c559c00 RCX: 001f Aug 03 00:35:41 kernel: RDX: RSI: 471c7c22 RDI: Aug 03 00:35:41 kernel: RBP: ba0d00113e78 R08: 01e6725fec9b R09: 0001 Aug 03 00:35:41 kernel: R10: a0c7a75e9a00 R11: a0c7a75e99e0 R12: a0c7a75f5700 Aug 03 00:35:41 kernel: R13: 0006 R14: 0006 R15: a0c7a75f5700 Aug 03 00:35:41 kernel: ? cpuidle_enter_state+0xa1/0x450 Aug 03 00:35:41 kernel: cpuidle_enter+0x2e/0x40 Aug 03 00:35:41 kernel: call_cpuidle+0x23/0x40 Aug 03 00:35:41 kernel: do_idle+0x1dd/0x270 Aug 03 00:35:41 kernel: cpu_startup_entry+0x20/0x30 Aug 03 00:35:41 kernel: start_secondary+0x167/0x1c0 Aug 03 00:35:41 kernel: secondary_startup_64+0xa4/0xb0 Aug 03 00:35:41 kernel: ---[ end trace fc1e06321e14fd73 ]--- Aug 03 00:36:07 wpa_supplicant[777]:
[Kernel-packages] [Bug 1890096] [NEW] Realtek RTL8822BE [10ec:b822] subsystem [103c:831b] purge skb(s) not reported by firmware
Public bug reported: Aug 03 00:35:20 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:21 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:24 kernel: rtw_pci :01:00.0: failed to send h2c command Aug 03 00:35:37 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:40 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:35:40 kernel: rtw_pci :01:00.0: firmware failed to restore hardware setting Aug 03 00:35:41 kernel: [ cut here ] Aug 03 00:35:41 kernel: purge skb(s) not reported by firmware Aug 03 00:35:41 kernel: WARNING: CPU: 7 PID: 0 at drivers/net/wireless/realtek/rtw88/tx.c:162 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Aug 03 00:35:41 kernel: Modules linked in: ccm rfcomm cmac algif_hash algif_skcipher af_alg bnep nls_iso8859_1 snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_generic snd_sof_pci snd_sof_intel_hd> Aug 03 00:35:41 kernel: wmi_bmof videodev dell_wmi_descriptor drm_kms_helper ucsi_acpi mei_me mc processor_thermal_device i2c_algo_bit hid_multitouch typec_ucsi fb_sys_fops intel_rapl_common ecdh_gener> Aug 03 00:35:41 kernel: CPU: 7 PID: 0 Comm: swapper/7 Not tainted 5.4.0-42-generic #46-Ubuntu Aug 03 00:35:41 kernel: Hardware name: Dell Inc. Inspiron 7380/, BIOS 1.1.0 08/08/2018 Aug 03 00:35:41 kernel: RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Aug 03 00:35:41 kernel: Code: 0f 1f 44 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 98 e9 1d c1 e8 f6 16 d4 c9 <0f> 0b 4c 8d 6b d8 4c 89 ef e8 dd 5c 77 ca 48> Aug 03 00:35:41 kernel: RSP: 0018:ba0d00288e48 EFLAGS: 00010286 Aug 03 00:35:41 kernel: RAX: RBX: a0c7a03097f8 RCX: 0006 Aug 03 00:35:41 kernel: RDX: 0007 RSI: 0082 RDI: a0c7a75d78c0 Aug 03 00:35:41 kernel: RBP: ba0d00288e60 R08: 03c4 R09: 0004 Aug 03 00:35:41 kernel: R10: R11: 0001 R12: a0c7a75dba80 Aug 03 00:35:41 kernel: R13: a0c7a03097f8 R14: c1160090 R15: a0c7a03097f8 Aug 03 00:35:41 kernel: FS: () GS:a0c7a75c() knlGS: Aug 03 00:35:41 kernel: CS: 0010 DS: ES: CR0: 80050033 Aug 03 00:35:41 kernel: CR2: 7fc77dfd4000 CR3: 00024e80a003 CR4: 003606e0 Aug 03 00:35:41 kernel: Call Trace: Aug 03 00:35:41 kernel: Aug 03 00:35:41 kernel: call_timer_fn+0x32/0x130 Aug 03 00:35:41 kernel: __run_timers.part.0+0x180/0x280 Aug 03 00:35:41 kernel: ? timerqueue_add+0x9b/0xb0 Aug 03 00:35:41 kernel: ? enqueue_hrtimer+0x3d/0x90 Aug 03 00:35:41 kernel: ? recalibrate_cpu_khz+0x10/0x10 Aug 03 00:35:41 kernel: ? ktime_get+0x3e/0xa0 Aug 03 00:35:41 kernel: run_timer_softirq+0x2a/0x50 Aug 03 00:35:41 kernel: __do_softirq+0xe1/0x2d6 Aug 03 00:35:41 kernel: ? hrtimer_interrupt+0x13b/0x220 Aug 03 00:35:41 kernel: irq_exit+0xae/0xb0 Aug 03 00:35:41 kernel: smp_apic_timer_interrupt+0x7b/0x140 Aug 03 00:35:41 kernel: apic_timer_interrupt+0xf/0x20 Aug 03 00:35:41 kernel: Aug 03 00:35:41 kernel: RIP: 0010:cpuidle_enter_state+0xc5/0x450 Aug 03 00:35:41 kernel: Code: ff e8 bf 08 81 ff 80 7d c7 00 74 17 9c 58 0f 1f 44 00 00 f6 c4 02 0f 85 65 03 00 00 31 ff e8 12 6c 87 ff fb 66 0f 1f 44 00 00 <45> 85 ed 0f 88 8f 02 00 00 49 63 cd 4c 8b 7d> Aug 03 00:35:41 kernel: RSP: 0018:ba0d00113e38 EFLAGS: 0246 ORIG_RAX: ff13 Aug 03 00:35:41 kernel: RAX: a0c7a75ead00 RBX: 8c559c00 RCX: 001f Aug 03 00:35:41 kernel: RDX: RSI: 471c7c22 RDI: Aug 03 00:35:41 kernel: RBP: ba0d00113e78 R08: 01e6725fec9b R09: 0001 Aug 03 00:35:41 kernel: R10: a0c7a75e9a00 R11: a0c7a75e99e0 R12: a0c7a75f5700 Aug 03 00:35:41 kernel: R13: 0006 R14: 0006 R15: a0c7a75f5700 Aug 03 00:35:41 kernel: ? cpuidle_enter_state+0xa1/0x450 Aug 03 00:35:41 kernel: cpuidle_enter+0x2e/0x40 Aug 03 00:35:41 kernel: call_cpuidle+0x23/0x40 Aug 03 00:35:41 kernel: do_idle+0x1dd/0x270 Aug 03 00:35:41 kernel: cpu_startup_entry+0x20/0x30 Aug 03 00:35:41 kernel: start_secondary+0x167/0x1c0 Aug 03 00:35:41 kernel: secondary_startup_64+0xa4/0xb0 Aug 03 00:35:41 kernel: ---[ end trace fc1e06321e14fd73 ]--- Aug 03 00:36:07 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS Aug 03 00:36:23 wpa_supplicant[777]: wlp1s0: CTRL-EVENT-BEACON-LOSS ... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1369 F pulseaudio CasperMD5CheckResult: skip Date: Mon Aug 3 00:59:46 2020 InstallationDate: Installed on 2020-06-13 (50 days ago) InstallationMedia: Ubuntu 20.04 LTS
[Kernel-packages] [Bug 1850502] Re: RTL8822BE Bluetooth disconnects with error CTRL-EVENT-BEACON-LOSS - rtw88
** Tags added: hwe-networking-wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850502 Title: RTL8822BE Bluetooth disconnects with error CTRL-EVENT-BEACON-LOSS - rtw88 Status in linux package in Ubuntu: Expired Bug description: Hi, Os: Ubuntu 19.10 kernel :5.3.0-23-generic driver: rtw88 Wifi HW module: RTL8822BE 02:00.0 Network controller: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter Subsystem: AzureWave RTL8822BE 802.11a/b/g/n/ac WiFi adapter Kernel driver in use: rtw_pci Kernel modules: rtwpci I am facing intermittent Bluetooth disconnection issue when connected to a Bluetooth speaker, my Bluetooth speaker disconnects with error "wlp2s0: CTRL-EVENT-BEACON-LOSS" (kernel: 5.3.0-23-generic), also audio shutters when music played via android phone and getting this error in Syslog "[pulseaudio] module-loopback.c: Too many underruns, increasing latency to 205.00 ms". But Bluetooth works perfectly fine with kernel 4.19.67 (Debian 10.2 ) The only difference was in kernel 4.19.67 the driver loaded was r8822be, so the issue is with the driver rtw_pci which is loaded in kernel: 5.3.0-23 ?? Please find the log below Nov 18 08:29:04 Asus-VivoBook wpa_supplicant[751]: wlp2s0: CTRL-EVENT-BEACON-LOSS Nov 18 08:29:57 Asus-VivoBook kernel: [ 3456.258679] rtw_pci :02:00.0: firmware failed to restore hardware setting Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794656] [ cut here ] Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794659] purge skb(s) not reported by firmware Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794724] WARNING: CPU: 3 PID: 3116 at /home/ubuntu/rtlwifi_new/tx.c:163 rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794725] Modules linked in: cmac ccm rfcomm bnep nls_iso8859_1 x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel snd_hda_codec_hdmi kvm snd_hda_codec_realtek irqbypass snd_soc_skl snd_hda_codec_generic ledtrig_audio snd_soc_hdac_hda snd_hda_ext_core snd_soc_skl_ipc snd_soc_sst_ipc snd_soc_sst_dsp snd_soc_acpi_intel_match snd_soc_acpi snd_soc_core snd_compress crct10dif_pclmul ac97_bus crc32_pclmul snd_pcm_dmaengine snd_hda_intel ghash_clmulni_intel snd_hda_codec mei_hdcp snd_hda_core snd_hwdep intel_rapl_msr snd_pcm i915 rtwpci(OE) uvcvideo rtw88(OE) btusb btrtl snd_seq_midi snd_seq_midi_event btbcm aesni_intel videobuf2_vmalloc snd_rawmidi joydev btintel videobuf2_memops mac80211 snd_seq drm_kms_helper videobuf2_v4l2 aes_x86_64 videobuf2_common crypto_simd cryptd snd_seq_device snd_timer cfg80211 rtsx_usb_ms glue_helper bluetooth processor_thermal_device asus_nb_wmi intel_cstate drm snd memstick intel_rapl_perf input_leds videodev intel_xhci_usb_role_switch spi_pxa2xx_platform Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794789] serio_raw i2c_algo_bit asus_wmi libarc4 dw_dmac mc wmi_bmof intel_rapl_common mei_me dw_dmac_core sparse_keymap ecdh_generic soundcore ecc fb_sys_fops 8250_dw syscopyarea roles hid_multitouch mei sysfillrect intel_soc_dts_iosf sysimgblt idma64 virt_dma intel_pch_thermal int3403_thermal int340x_thermal_zone int3400_thermal mac_hid acpi_pad acpi_thermal_rel sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 rtsx_usb_sdmmc rtsx_usb usbhid hid_generic i2c_i801 ahci libahci intel_lpss_pci i2c_hid intel_lpss hid wmi pinctrl_sunrisepoint video pinctrl_intel Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794839] CPU: 3 PID: 3116 Comm: chrome Tainted: G OE 5.3.0-23-generic #25-Ubuntu Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794841] Hardware name: ASUSTeK COMPUTER INC. VivoBook_ASUSLaptop X412UA/X412UA, BIOS X412UA.303 06/03/2019 Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794856] RIP: 0010:rtw_tx_report_purge_timer+0x25/0x60 [rtw88] Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794860] Code: 00 00 00 00 00 0f 1f 44 00 00 8b 47 f0 85 c0 75 01 c3 55 48 89 e5 41 55 41 54 53 48 89 fb 48 c7 c7 20 d3 d6 c0 e8 16 95 99 ee <0f> 0b 4c 8d 6b d8 4c 89 ef e8 fd d9 39 ef 48 8d 7b e0 49 89 c4 e8 Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794863] RSP: :b5ba00180e48 EFLAGS: 00010286 Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794867] RAX: RBX: 9d6509c8dc90 RCX: 0006 Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794870] RDX: 0007 RSI: 0082 RDI: 9d6512b97440 Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794872] RBP: b5ba00180e60 R08: 03a1 R09: 0004 Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794875] R10: R11: 0001 R12: 9d6512b9b600 Nov 18 08:29:58 Asus-VivoBook kernel: [ 3456.794877] R13: 9d6509c8dc90 R14: c0d01db0 R15: 9d6509c8dc90 Nov 18 08:29:58 Asus-VivoBook kernel: [
[Kernel-packages] [Bug 1889342] Re: Thunderbolt Dock Loses Monitors
I upgraded my kernel to 5.6.0-1020-oem in order to test. The issue is better then, but not resolved. When using the lock screen one out of the two monitors is lost. This errors are in dmesg: [257474.965612] [drm:intel_dp_link_training_clock_recovery [i915]] *ERROR* failed to get link status [257474.974761] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889342 Title: Thunderbolt Dock Loses Monitors Status in linux package in Ubuntu: Confirmed Bug description: After a suspend or locking the only way to regain external monitors is to unplug and replug the thunderbolt dock back in. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: john 2682 F pulseaudio /dev/snd/controlC0: john 2682 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jul 29 00:22:26 2020 DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-focal-amd64-20200502-85 InstallationDate: Installed on 2020-07-13 (15 days ago) InstallationMedia: Ubuntu 20.04 "Focal" - Build amd64 LIVE Binary 20200502-05:58 MachineType: Dell Inc. XPS 13 9300 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=5e141eb0-e03b-4c39-b826-f94e0d2715ea ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/08/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.0.11 dmi.board.name: 0WX9VX dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.0.11:bd05/08/2020:svnDellInc.:pnXPS139300:pvr:rvnDellInc.:rn0WX9VX:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9300 dmi.product.sku: 096D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1889342/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1877192] Re: RTL8723bs bluetooth not working on 20.04
[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/1877192 Title: RTL8723bs bluetooth not working on 20.04 Status in linux package in Ubuntu: Expired Bug description: I have Ubuntu 20.04 installed on atom-based tablet ACER Aspire Switch 10. And bluetooth does not work. In fact it looks like ubuntu does not recognize bluetooth HW at all. But the system does have bluetooth module which under windows is recognized as RTK8723 (ACPI\RTK8723\some-id) At the same time WiFi works without issues (the same module, if I am not mistaken). $ lsb_release -d Description:Ubuntu 20.04 LTS $ uname -vr 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 $ dmesg | grep -i 8723 [8.087918] r8723bs: module is from the staging directory, the quality is unknown, you have been warned. [8.088914] r8723bs: module verification failed: signature and/or required key missing - tainting kernel [8.092667] RTL8723BS: module init start [8.092671] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40 [8.092673] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40 [8.303955] RTL8723BS: rtw_ndev_init(wlan0) [8.304653] RTL8723BS: module init ret =0 [ 13.200223] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin [ 17.832536] RTL8723BS: rtw_set_802_11_connect(wlan0) fw_state = 0x0008 [ 17.889893] RTL8723BS: start auth [ 17.892815] RTL8723BS: auth success, start assoc [ 17.901012] RTL8723BS: rtw_cfg80211_indicate_connect(wlan0) BSS not found !! [ 17.901053] RTL8723BS: assoc success [ 17.913846] RTL8723BS: send eapol packet [ 17.939873] RTL8723BS: send eapol packet [ 17.942652] RTL8723BS: set pairwise key camid:4, addr:50:c7:bf:31:a1:fa, kid:0, type:AES [ 17.944712] RTL8723BS: set group key camid:5, addr:50:c7:bf:31:a1:fa, kid:1, type:TKIP $ rfkill list all 0: acer-wireless: Wireless LAN Soft blocked: no Hard blocked: no 1: acer-bluetooth: Bluetooth Soft blocked: no Hard blocked: no 2: phy0: Wireless LAN Soft blocked: no Hard blocked: no --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: user 1288 F pulseaudio /dev/snd/controlC0: user 1288 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-24 (13 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lspci-vt: -[:00]-+-00.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register +-02.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display +-14.0 Intel Corporation Atom Processor Z36xxx/Z37xxx, Celeron N2000 Series USB xHCI +-1a.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine \-1f.0 Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 06cb:2968 Synaptics, Inc. Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/1p, 5000M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 480M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/4p, 480M |__ Port 3: Dev 3, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 3, If 1, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Acer Aspire SW5-012 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=140a1a3c-1a0a-4aab-b323-f621e6497a7e ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 StagingDrivers: r8723bs Tags: focal staging Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 03/01/2016 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: V1.20 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Fendi2 dmi.board.vendor: Acer dmi.board.version: V1.20 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version:
[Kernel-packages] [Bug 1881213] Re: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work
[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/1881213 Title: System hangs at reboot or poweroff. kworker blocked at dp_altmode_work Status in linux package in Ubuntu: Expired Bug description: Expected: System reboots/powers off. Actual: System hangs with the plymouth bootsplash with the Kubuntu logo. Pressing escape shows `[OK] Reached target Reboot`. `journalctl -b -1` shows at the end. ``` May 28 16:33:21 jordan-ThinkPad systemd[1]: Shutting down. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Syncing filesystems and block devices. May 28 16:33:21 jordan-ThinkPad systemd-shutdown[1]: Sending SIGTERM to remaining processes... May 28 16:33:21 jordan-ThinkPad systemd-journald[454]: Journal stopped ``` Letting the computer continue to idle, an error message shows up. I've attached a picture because the error message does not show up in any logs. Possibly a duplicate of https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1872817, though the other user did not mention the same symptoms. Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Thu May 28 16:53:34 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu DkmsStatus: acpi-call, 1.1.0, 5.4.0-31-generic, x86_64: installed acpi-call, 1.1.0, 5.4.0-33-generic, x86_64: installed ExtraDebuggingInterest: No GraphicsCard: NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f] InstallationDate: Installed on 2020-05-22 (6 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20QVCTO1WW ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=0a60aa5c-2eea-49a2-9e8e-966068e76491 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/07/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2OET44W (1.31 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QVCTO1WW dmi.board.vendor: LENOVO dmi.board.version: 0B98417 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2OET44W(1.31):bd05/07/2020:svnLENOVO:pn20QVCTO1WW:pvrThinkPadX1ExtremeGen2:rvnLENOVO:rn20QVCTO1WW:rvr0B98417WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme Gen2 dmi.product.name: 20QVCTO1WW dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme Gen2 dmi.product.version: ThinkPad X1 Extreme Gen2 dmi.sys.vendor: LENOVO 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* 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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890050] Re: Mouse malfunction when launching steam
And your kernel log shows similar problems. It might be a problem with the motherboard, a specific USB port, or with the mouse. ** Changed in: libinput (Ubuntu) Status: Incomplete => Invalid ** Changed in: xserver-xorg-input-libinput (Ubuntu) Status: Incomplete => Invalid ** No longer affects: libinput (Ubuntu) ** No longer affects: xserver-xorg-input-libinput (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/1890050 Title: Mouse malfunction when launching steam Status in linux package in Ubuntu: Incomplete Bug description: When launching Steam mouse automatically stops working. Only way to fix it is closing Steam and plugging the mouse again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 19:30:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d6] InstallationDate: Installed on 2020-01-29 (185 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A15 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1555f7ff-6084-4156-b1cd-6e9c57ec0e76 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD PLUS (MS-7A15) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd10/28/2016:svnMSI:pnMS-7A15:pvr1.0:rvnMSI:rnH110MPRO-VDPLUS(MS-7A15):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A15 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890050] Re: Mouse malfunction when launching steam
The attached XorgLog.txt shows the mouse is repeatedly: [ 28256.417] (II) event4 - USB OPTICAL MOUSE: device removed So this might be a hardware problem or a kernel bug. Try plugging it into a different port, or try a different mouse. ** Package changed: xorg (Ubuntu) => xserver-xorg-input-libinput (Ubuntu) ** Also affects: libinput (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: libinput (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-input-libinput (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/1890050 Title: Mouse malfunction when launching steam Status in linux package in Ubuntu: Incomplete Bug description: When launching Steam mouse automatically stops working. Only way to fix it is closing Steam and plugging the mouse again. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.4.0-42.46~18.04.1-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 BootLog: Error: [Errno 13] Brak dostępu: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 19:30:32 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: NVIDIA Corporation GP107 [GeForce GTX 1050 Ti] [10de:1c82] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP107 [GeForce GTX 1050 Ti] [1043:85d6] InstallationDate: Installed on 2020-01-29 (185 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 009: ID 15d9:0a4c Trust International B.V. USB+PS/2 Optical Mouse Bus 001 Device 005: ID 413c:2101 Dell Computer Corp. SmartCard Reader Keyboard Bus 001 Device 004: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: MSI MS-7A15 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=pl_PL.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=1555f7ff-6084-4156-b1cd-6e9c57ec0e76 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/28/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.40 dmi.board.asset.tag: Default string dmi.board.name: H110M PRO-VD PLUS (MS-7A15) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.40:bd10/28/2016:svnMSI:pnMS-7A15:pvr1.0:rvnMSI:rnH110MPRO-VDPLUS(MS-7A15):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7A15 dmi.product.sku: Default string dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2~18.04.1 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~18.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~18.04.1 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890050/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889941] Re: AMD Navi10 GPU powerplay issues when using two DisplayPort connectors
** Bug watch added: gitlab.freedesktop.org/drm/amd/-/issues #929 https://gitlab.freedesktop.org/drm/amd/-/issues/929 ** Also affects: linux via https://gitlab.freedesktop.org/drm/amd/-/issues/929 Importance: Unknown Status: Unknown ** Summary changed: - AMD Navi10 GPU powerplay issues when using two DisplayPort connectors + [amdgpu] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors ** Package changed: xorg (Ubuntu) => xserver-xorg-video-amdgpu (Ubuntu) ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags added: amdgpu ** Tags added: multimonitor -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889941 Title: [amdgpu] AMD Navi10 GPU powerplay issues when using two DisplayPort connectors Status in Linux: Unknown Status in linux package in Ubuntu: New Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: Connecting two displayport monitors to a 5700XT causes flickering on one of the screens, issue appears to be occurring upstream and is being tracked here: https://gitlab.freedesktop.org/drm/amd/-/issues/929 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jul 31 21:45:59 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1002:731f] (rev c1) (prog-if 00 [VGA controller]) Subsystem: XFX Pine Group Inc. Navi 10 [Radeon RX 5600 OEM/5600 XT / 5700/5700 XT] [1682:5701] InstallationDate: Installed on 2020-06-28 (33 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=f17edc40-7eaf-4768-977d-f0e067db9b04 ro amdgpu.noretry=0 processor.max_cstate=5 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2020 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1407 dmi.board.asset.tag: Default string dmi.board.name: TUF GAMING X570-PLUS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1407:bd04/01/2020:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnTUFGAMINGX570-PLUS:rvrRevX.0x:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.2 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: https://bugs.launchpad.net/linux/+bug/1889941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875099] Re: RTL8822BE Wifi [10ec:b822] subsystem [17aa:b023] crashes on 20.04 on Lenovo Legion Y530
** Tags added: crash eoan hwe-networking-wifi wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875099 Title: RTL8822BE Wifi [10ec:b822] subsystem [17aa:b023] crashes on 20.04 on Lenovo Legion Y530 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu Mate to 20.04 , my wifi crashed on Lenovo legion Y530. The strange thing is that it connects to the network, i have internet for some time (usually between 1 and 10 minutes) and then it disconnects. After that, the applet shows me something like device not ready and i can only restart the computer to connect. Then it crashes again... I also tried a fresh install with the same results. I used 19.04 and 19.10 on the same laptop as my primary operating system and wifi worked flawlessly. Since I do my work on this laptop i was forced to downgrade back to 19.10 for now. This is my lshw -C network (from 19.10 If I remember correctly it was RTL8822BE also in 20.04) *-network description: Wireless interface product: RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:07:00.0 logical name: wlp7s0 version: 00 serial: dc:a2:66:80:7d:7d width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtw_pci driverversion=5.3.0-46-generic firmware=N/A ip=192.168.0.146 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:141 ioport:4000(size=256) memory:a430-a430 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:08:00.0 logical name: enp8s0 version: 15 serial: 8c:16:45:e9:e9:a8 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:17 ioport:3000(size=256) memory:a4204000-a4204fff memory:a420-a4203fff and my lspci -nnk | grep -A2 0280 07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: Lenovo RTL8822BE 802.11a/b/g/n/ac WiFi adapter [17aa:b023] Kernel driver in use: rtw_pci If you think it is necessary, I can try to install 20.04 on an external hard drive and give you some more info from there. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: campus 1207 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81FV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2ba3f662-50a5-4db8-a5e1-ddaf5e09d5a9 ro 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 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8JCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y530-15ICH dmi.modalias: dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH: dmi.product.family: Legion Y530-15ICH dmi.product.name: 81FV dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH dmi.product.version: Lenovo Legion Y530-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1875099/+subscriptions -- Mailing list:
[Kernel-packages] [Bug 1887294] Re: [nvidia] Display freeze
Can you please test nvidia driver version 450? It is available here: https://launchpad.net/~oem-solutions-group/+archive/ubuntu/nvidia- driver-staging?field.series_filter=focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1887294 Title: [nvidia] Display freeze Status in nvidia-graphics-drivers-440 package in Ubuntu: New Bug description: The display is completely frozen, and no signal is output to the monitors. There is also no signal when switching to a console (Ctr- Alt-F1). I have normal access via SSH. It happens about once in 14 days. Only happens when turning the display off or on (about once in 15 screen power cycles). nvidia-smi still works (via SSH; without any options) DISPLAY=:1 xset dpms force on hangs indefinitely. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia .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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.100 Fri May 29 08:45:51 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Sun Jul 12 17:47:58 2020 DistUpgraded: 2020-05-17 13:48:43,365 DEBUG entry '# deb [arch=amd64] https://repo.skype.com/deb stable main # disabled on upgrade to focal' was disabled (unknown mirror) DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.100, 5.4.0-39-generic, x86_64: installed nvidia, 440.100, 5.4.0-40-generic, x86_64: installed (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) (WARNING! Diff between built and installed module!) v4l2loopback, 0.12.3, 5.4.0-39-generic, x86_64: installed v4l2loopback, 0.12.3, 5.4.0-40-generic, x86_64: installed ExtraDebuggingInterest: Yes GpuHangFrequency: Very infrequently GraphicsCard: NVIDIA Corporation GP106 [GeForce GTX 1060 6GB] [10de:1c03] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GP106 [GeForce GTX 1060 6GB] [1043:85ae] InstallationDate: Installed on 2016-07-27 (1445 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) MachineType: System manufacturer System Product Name ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to focal on 2020-05-17 (56 days ago) dmi.bios.date: 04/17/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3601 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8C WS dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev 1.xx dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3601:bd04/17/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnP8CWS:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer 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.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx 20.0.8-0ubuntu1~20.04.1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A xserver.bootTime: Tue Jul 7 22:02:38 2020 xserver.configfile: default xserver.logfile: /var/log/Xorg.0.log xserver.outputs: xserver.version: 2:1.20.8-2ubuntu2.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-440/+bug/1887294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1888331] Re: Wakeup the system by touching the touchpad
** Tags removed: verification-needed-focal
** Tags added: verification-done-focal
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1888331
Title:
Wakeup the system by touching the touchpad
Status in HWE Next:
New
Status in linux-oem-5.6 package in Ubuntu:
New
Status in linux-oem-5.6 source package in Focal:
Fix Committed
Bug description:
[Impact]
Can't wake up by touching the touchpad.
[Fix]
1.gpio: With 'commit 461c1a7d4733 ("gpiolib: override irq_enable/disable")'
gpiolib overrides irqchip's irq_enable and irq_disable callbacks. If
irq_disable
callback is implemented then genirq takes unlazy path to disable irq.
Underlying irqchip
may not want to implement irq_disable callback to lazy disable irq
when client drivers invokes disable_irq(). By overriding irq_disable
callback,
gpiolib ends up always unlazy disabling IRQ.
Allow gpiolib to lazy disable IRQs by overriding irq_disable callback only
if irqchip implemented irq_disable. In cases where irq_disable is not
implemented irq_mask is overridden. Similarly override irq_enable callback
only if irqchip implemented irq_enable otherwise irq_unmask is overridden.
2. hid: Many laptops can be woken up from Suspend-to-Idle by touchpad. This is
also the default behavior on other OSes.
However, if touchpad and touchscreen contact to each other when lid is
closed, wakeup events can be triggered inadventertly.
So let's disable the wakeup by default, but enable the wakeup capability
so users can enable it at their own discretion.
[test]
With the patch and manually enable HID's power/wakeup, the system can wake up
by touching the touchpad.
[Regression Potential]
Low. The two patches are already landed in the upstream.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1888331/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
** Changed in: pulseaudio (Ubuntu) Assignee: Marcelo Pires (marcelo-pires-silva) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in PulseAudio: Unknown Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null) index :
[Kernel-packages] [Bug 1888375] Re: Restart the machine successfully after suspend
** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1888375 Title: Restart the machine successfully after suspend Status in HWE Next: New Status in linux-oem-5.6 package in Ubuntu: New Status in linux-oem-5.6 source package in Focal: Fix Committed Bug description: [Impact] After suspend then restart, the System would hang during shutdown. [Fix] The commit has pushed to upstream but still wait for the maintainer of IOMMU to apply. https://lore.kernel.org/linux-iommu/20200721001713.24282-1-baolu...@linux.intel.com/ Skip the TE disabling for the quirky gfx dedicated iommu and the system would not hang during shutdown. [test] With the patch, the machine restart successfully. [Regression Potential] low, the patch just skip the TE disabling and wouldn't affect the normal usage. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1888375/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886366] Re: USB External Drive Stalls and Timeouts
Seems to be fixed on kernel 5.7.0. so I'm closing for now as it has not happened for the last 2 weeks and the timeout would occur every 2 to 3 days before. ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1886366 Title: USB External Drive Stalls and Timeouts Status in linux package in Ubuntu: Fix Released Bug description: Not sure of the package naming for the Linux Kernel. However since version 4.15.0.28 I've been getting timeouts like this in dmesg: [63075.835488] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [63075.835491] scsi_eh_7 D0 273 2 0x80004000 [63075.835494] Call Trace: [63075.835504] __schedule+0x2b9/0x6c0 [63075.835507] schedule+0x42/0xb0 [63075.835510] schedule_preempt_disabled+0xe/0x10 [63075.835513] __mutex_lock.isra.0+0x182/0x4f0 [63075.835515] ? __switch_to_asm+0x40/0x70 [63075.835517] ? __switch_to_asm+0x34/0x70 [63075.835519] ? __switch_to_asm+0x34/0x70 [63075.835520] ? __switch_to_asm+0x40/0x70 [63075.835523] __mutex_lock_slowpath+0x13/0x20 [63075.835526] mutex_lock+0x2e/0x40 [63075.835531] device_reset+0x22/0x50 [usb_storage] [63075.835535] scsi_eh_ready_devs+0x56c/0xa30 [63075.835540] ? __pm_runtime_resume+0x60/0x80 [63075.835543] scsi_error_handler+0x432/0x500 [63075.835548] kthread+0x104/0x140 [63075.835550] ? scsi_eh_get_sense+0x210/0x210 [63075.835553] ? kthread_park+0x80/0x80 [63075.83] ret_from_fork+0x35/0x40 The drive works fine on kernels 4.15.0.28 and older. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: nick 2943 F pulseaudio /dev/snd/controlC0: nick 2943 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=UUID=2e62fe89-0a58-42ff-95bd-80760e43753b InstallationDate: Installed on 2014-12-31 (2014 days ago) InstallationMedia: Lubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2) IwConfig: eth0 no wireless extensions. lono wireless extensions. MachineType: System manufacturer System Product Name NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=f21814d2-6d82-426b-a5e0-cb4734f1a929 ro quiet splash init=/lib/systemd/systemd vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions: linux-restricted-modules-5.4.0-40-generic N/A linux-backports-modules-5.4.0-40-generic N/A linux-firmware1.187.1 RfKill: Tags: focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-06-29 (7 days ago) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/17/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 3506 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: P8Z68-V LE dmi.board.vendor: ASUSTeK Computer INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr3506:bd01/17/2012:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP8Z68-VLE:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886366/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850130] Re: zpools fail to import after reboot on fresh install of eoan
Howtofixit 1) replace “Exec zfs mount -a” to “Exec zpool import -a” in systemd service file for zfs 2) uncomment “#zfs” to “zfs” in /lib/modules-load/somefile 3) make snapshot for pool with problems, attach snapshot as pool to required path Now I'm not near my laptop so I don't remember exactly. I'll write to you tomorrow. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1850130 Title: zpools fail to import after reboot on fresh install of eoan Status in grub2 package in Ubuntu: Confirmed Status in zfs-linux package in Ubuntu: Fix Released Status in grub2 source package in Focal: Confirmed Status in zfs-linux source package in Focal: Fix Released Bug description: Fresh installation of stock Ubuntu 19.10 Eoan with experimental root on ZFS. System has existing zpools with data. Installation is uneventful. First boot with no problems. Updates applied. No other changes from fresh installation. Reboot. External pool 'tank' imports with no errors. Reboot. External pool has failed to import on boot. In contrast bpool and rpool are ok. Manually re-import 'tank' with no issues. I can see both 'tank' and its path in /dev/disk/by-id/ in /etc/zfs/zpool.cache. Reboot. 'tank' has failed to import on boot. It is also missing from /etc/zfs/zpool.cache. Is it possible that the cache is being re- generated on reboot, and the newly imported pools are getting erased from it? I can re-import the pools again manually with no issues, but they don't persist between re-boots. Installing normally on ext4 this is not an issue and data pools import automatically on boot with no further effort. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1850130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
I do not use standard Ubuntu at the moment. So, I cannot say for it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 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:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887728] Re: [amdgpu] Scrumbled screen after standby on encrypted system
I installed Manjaro KDE and I saw the issue there either even if I tried 2 newer kernel versions there. I installed today a fresh conpy of Kubuntu 20.04 again. The problem is the same. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887728 Title: [amdgpu] Scrumbled screen after standby on encrypted system Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: New Bug description: I use Kubuntu 20.04 on an encrypted disk (LVM). Problem: After a standby when you wake up the system with the standby button again, the screen is for a short moment "scrambled" then the login dialog is presented and one can log in. This scrambled screen is only a cosmetic problem, but it does not fit the overall good design of the system. That's why I think it should be fixed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: KDE Date: Wed Jul 15 23:50:54 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: No GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Picasso [1002:15d8] (rev d2) (prog-if 00 [VGA controller]) Subsystem: Lenovo Picasso [17aa:5125] InstallationDate: Installed on 2020-07-14 (1 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20NKS01Y00 ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/vgkubuntu-root ro quiet splash iommu=soft vt.handoff=7 SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/19/2020 dmi.bios.vendor: LENOVO dmi.bios.version: R12ET50W(1.20 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NKS01Y00 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:bvrR12ET50W(1.20):bd02/19/2020:svnLENOVO:pn20NKS01Y00:pvrThinkPadT495:rvnLENOVO:rn20NKS01Y00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T495 dmi.product.name: 20NKS01Y00 dmi.product.sku: LENOVO_MT_20NK_BU_Think_FM_ThinkPad T495 dmi.product.version: ThinkPad T495 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.8-0ubuntu1~20.04.1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-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: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887728/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890055] 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/1890055 Title: linux-image-5.4.0-42-generic 5.4.0-42.26 Status in linux package in Ubuntu: Confirmed Bug description: backlight (brightness does not work) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abdr 2227 F pulseaudio /dev/snd/controlC0: abdr 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 00:38:12 2020 InstallationDate: Installed on 2020-07-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81SX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=7dda4531-e9b1-482c-bcec-a96bcf0a3b42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN36WW:bd02/10/2020:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890055] [NEW] linux-image-5.4.0-42-generic 5.4.0-42.26
Public bug reported: backlight (brightness does not work) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abdr 2227 F pulseaudio /dev/snd/controlC0: abdr 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 00:38:12 2020 InstallationDate: Installed on 2020-07-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81SX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=7dda4531-e9b1-482c-bcec-a96bcf0a3b42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN36WW:bd02/10/2020:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO ** 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/1890055 Title: linux-image-5.4.0-42-generic 5.4.0-42.26 Status in linux package in Ubuntu: New Bug description: backlight (brightness does not work) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-42-generic 5.4.0-42.46 ProcVersionSignature: Ubuntu 5.4.0-42.46-generic 5.4.44 Uname: Linux 5.4.0-42-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: abdr 2227 F pulseaudio /dev/snd/controlC0: abdr 2227 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Aug 3 00:38:12 2020 InstallationDate: Installed on 2020-07-28 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81SX ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-42-generic root=UUID=7dda4531-e9b1-482c-bcec-a96bcf0a3b42 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-42-generic N/A linux-backports-modules-5.4.0-42-generic N/A linux-firmware1.187.2 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BHCN36WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion Y540-15IRH dmi.modalias: dmi:bvnLENOVO:bvrBHCN36WW:bd02/10/2020:svnLENOVO:pn81SX:pvrLegionY540-15IRH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLegionY540-15IRH: dmi.product.family: Legion Y540-15IRH dmi.product.name: 81SX dmi.product.sku: LENOVO_MT_81SX_BU_idea_FM_Legion Y540-15IRH dmi.product.version: Legion Y540-15IRH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890055/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
@ccheney better open a new bug because this one accumulates too much info from unrelated problems -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2.80:bd08/13/2019:svnMicro-StarInternationalCo.,Ltd.:pnMS-7B16:pvr1.0:rvnMicro-StarInternationalCo.,Ltd.:rnB360GAMINGPROCARBON(MS-7B16):rvr1.0:cvnMicro-StarInternationalCo.,Ltd.:ct3:cvr1.0: dmi.product.family: Default string dmi.product.name: MS-7B16 dmi.product.version: 1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1
[Kernel-packages] [Bug 1852001] Re: KDE GUI freeze on high disk IO
@ccheney Regardless if my crashes are gone, my experience is that having a swap file in recent Linux is deadly. If Linux starts swapping only a little then it's hardly usable any more. I believe this is because of the algorithm that decides which pages to remove from memory. Your observation with 50% RAM could be related to VMLIM. VMLIM says how much of the RAM may be used for programs. By default this is half your RAM. The other half is for cache and buff only. (as I understood, this may be inaccurate). Try other values for VMLIM. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852001 Title: KDE GUI freeze on high disk IO Status in linux package in Ubuntu: Confirmed Bug description: I've got massive problems with GUI on my PC. The attached logs are from the following setting: - high disk load (f3write) - kernel 4.15.0-1050-oem (the only 4x kernel available in eoan) - no swap available These are the parameters (disk load, kernel, swap) I am fiddling with to find out the cause, see below. In general - the problem happens once a day with any 5.0 or 5.3 kernel from eoan repo - more likely to happen with high disk or CPU load, but not necessarily. - less likely with the 4.x kernel mentioned above. I just installed the following kernels from kernel-ppa: 5.3.10-050310-generic 5.4.0-050400rc6-generic 5.4.0-997-generic (drm-intel-next) Now I am waiting for the freeze to occur again. The problem started about half a year ago. There have been three changes that happened at the time and could be the cause - switch to kernel 5.x - update to Ubuntu 19.4 - swapped motherboard, CPU and RAM. The hassle started with the following scenario, repeated often: - high disk load - PC becomes laggy - soon dies/freezes The longer I waited, the deeper the lockdown went. but I don't know the exact details. The first cause I found was kswapd running amok and take the system with it. Workaround: add swap space. Now the problem shifted: Whenever I got high disk load (eg dd 100 GB of data) the kernel swaps likle crazy and makes the GUI first lag soon freeze. but no excessive CPU load any more, as kswapd does not go crazy. Again I found a workaround: the above mentioned 4.x kernel. In this case the GUI lags as expected from a heavily swapping system. nothing more. but still sometimes the GUI simply freezes (the error reported at the top) Another workaround is to completely remove swap. Let's see what happens, if kswapd goes amok again. I am not sure as how these problems are related. I did extensive hardware check like - memtest86 newest version, no "may be vulnerable to high frequency row hammering" - smart do you suggest any burn in test suites? thanks ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 4.15.0-1050.57-oem 4.15.18 Uname: Linux 4.15.0-1050-oem x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 Date: Sun Nov 10 15:55:14 2019 DistUpgraded: 2019-10-19 13:35:30,394 DEBUG entry '# deb http://ppa.launchpad.net/brandonsnider/cdrtools/ubuntu cosmic main # disabled on upgrade to eoan' was disabled (unknown mirror) DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: virtualbox, 6.0.14, 5.3.0-18-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-19-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation UHD Graphics 630 (Desktop 9 Series) [8086:3e98] (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] UHD Graphics 630 (Desktop 9 Series) [1462:7b16] InstallationDate: Installed on 2017-12-16 (693 days ago) InstallationMedia: Kubuntu 17.10 "Artful Aardvark" - Release amd64 (20171017.1) MachineType: Micro-Star International Co., Ltd. MS-7B16 ProcEnviron: LANGUAGE=en_US:en TERM=linux PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-1050-oem root=UUID=ca93bfbd-335a-4cc7-9d0f-f0da18447497 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display Title: Xorg freeze UpgradeStatus: Upgraded to eoan on 2019-10-19 (22 days ago) dmi.bios.date: 08/13/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 2.80 dmi.board.asset.tag: Default string dmi.board.name: B360 GAMING PRO CARBON (MS-7B16) dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: 1.0 dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Micro-Star International Co., Ltd. dmi.chassis.version: 1.0 dmi.modalias:
[Kernel-packages] [Bug 1859756] Re: [hns3-0115] add 8 BD limit for tx flow
** Changed in: kunpeng920/ubuntu-18.04 Status: In Progress => Fix Committed ** Changed in: kunpeng920 Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859756 Title: [hns3-0115] add 8 BD limit for tx flow Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Fix Committed Status in kunpeng920 ubuntu-18.04-hwe series: Fix Released Status in kunpeng920 ubuntu-20.04 series: Fix Released Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Committed Bug description: [Impact] We get reports that iscsi and spark tests fail on hns3 [Fix] Cherry-pick/backport patches from upstream. net: hns3: add 8 BD limit for tx flow net: hns3: avoid mult + div op in critical data path net: hns3: remove some ops in struct hns3_nic_ops net: hns3: fix for not calculating tx bd num correctly net: hns3: unify maybe_stop_tx for TSO and non-TSO case net: hns3: add check for max TX BD num for tso and non-tso case net: hns3: fix for TX queue not restarted problem net: hns3: fix a use after free problem in hns3_nic_maybe_stop_tx() [Test] No known way to reproduce it in our lab. Regression test only. [Regression Potential] Patchset only affects hns3 driver. Minimal risk for other drivers and platform. [Bug Description] A single transmit packet can span up to 8 descriptors, TSO transmit packet can be stored up to 63 descriptors and each segment within the TSO should be spanned up to 8 descriptors. If the packet needs more than 8 BD, and the total size of every 7 continuous frags more than MSS, HW does not support it, and it need driver makes SKB Linearized. [Actual Results] iscsi and bigdata spark test OK [Expected Results] iscsi and bigdata spark test OK [Reproducibility] Inevitably [Additional information] Hardware: D06 Firmware: NA Kernel: NA DTS2018091810050 [Resolution] SW use skb_copy to merge frag; 51e8439f3496 net: hns3: add 8 BD limit for tx flow 5f543a54eec0 net: hns3: fix for not calculating tx bd num correctly To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1859756/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
For crashes after suspend add: rcu_nocbs=0-N(number of cores -1) and idle=nowait as grub parameters update-grub and reboot you also need kernel 5.4 or higher with latest stable firmware. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808736] Re: Saving crash report failed
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Tags removed: cosmic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1808736 Title: Saving crash report failed Status in Ubuntu MATE: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In response to a error window stating that there is a problem with Caja (other than the memory leak that eats up move than 8GB of RAM). I clicked report to developers. See additional screen shot. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-12-generic 4.18.0-12.13 ProcVersionSignature: Ubuntu 4.18.0-12.13-generic 4.18.17 Uname: Linux 4.18.0-12-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: robert 2807 F pulseaudio /dev/snd/controlC0: robert 2807 F pulseaudio CurrentDesktop: MATE Date: Sun Dec 16 22:06:41 2018 InstallationDate: Installed on 2018-12-16 (0 days ago) InstallationMedia: Ubuntu-MATE 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.2) MachineType: System manufacturer System Product Name ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-12-generic root=UUID=737f341d-e214-40a2-b2a3-5a8b1b7ed378 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-12-generic N/A linux-backports-modules-4.18.0-12-generic N/A linux-firmware 1.175.1 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1301 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: A88XM-A dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: Rev X.0x dmi.chassis.asset.tag: Asset-1234567890 dmi.chassis.type: 3 dmi.chassis.vendor: Chassis Manufacture dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1301:bd04/01/2014:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKCOMPUTERINC.:rnA88XM-A:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To be filled by O.E.M. dmi.product.name: System Product Name dmi.product.sku: SKU dmi.product.version: System Version dmi.sys.vendor: System manufacturer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1808736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875099] Re: RTL8822BE Wifi [10ec:b822] subsystem [17aa:b023] crashes on 20.04 on Lenovo Legion Y530
** Tags removed: crash eoan hwe-networking-wifi wifi -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875099 Title: RTL8822BE Wifi [10ec:b822] subsystem [17aa:b023] crashes on 20.04 on Lenovo Legion Y530 Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu Mate to 20.04 , my wifi crashed on Lenovo legion Y530. The strange thing is that it connects to the network, i have internet for some time (usually between 1 and 10 minutes) and then it disconnects. After that, the applet shows me something like device not ready and i can only restart the computer to connect. Then it crashes again... I also tried a fresh install with the same results. I used 19.04 and 19.10 on the same laptop as my primary operating system and wifi worked flawlessly. Since I do my work on this laptop i was forced to downgrade back to 19.10 for now. This is my lshw -C network (from 19.10 If I remember correctly it was RTL8822BE also in 20.04) *-network description: Wireless interface product: RTL8822BE 802.11a/b/g/n/ac WiFi adapter vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:07:00.0 logical name: wlp7s0 version: 00 serial: dc:a2:66:80:7d:7d width: 64 bits clock: 33MHz capabilities: pm msi pciexpress bus_master cap_list ethernet physical wireless configuration: broadcast=yes driver=rtw_pci driverversion=5.3.0-46-generic firmware=N/A ip=192.168.0.146 latency=0 link=yes multicast=yes wireless=IEEE 802.11 resources: irq:141 ioport:4000(size=256) memory:a430-a430 *-network description: Ethernet interface product: RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller vendor: Realtek Semiconductor Co., Ltd. physical id: 0 bus info: pci@:08:00.0 logical name: enp8s0 version: 15 serial: 8c:16:45:e9:e9:a8 capacity: 1Gbit/s width: 64 bits clock: 33MHz capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation configuration: autonegotiation=on broadcast=yes driver=r8169 firmware=rtl8168h-2_0.0.2 02/26/15 latency=0 link=no multicast=yes port=MII resources: irq:17 ioport:3000(size=256) memory:a4204000-a4204fff memory:a420-a4203fff and my lspci -nnk | grep -A2 0280 07:00.0 Network controller [0280]: Realtek Semiconductor Co., Ltd. RTL8822BE 802.11a/b/g/n/ac WiFi adapter [10ec:b822] Subsystem: Lenovo RTL8822BE 802.11a/b/g/n/ac WiFi adapter [17aa:b023] Kernel driver in use: rtw_pci If you think it is necessary, I can try to install 20.04 on an external hard drive and give you some more info from there. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: campus 1207 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: MATE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-05-09 (0 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81FV NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-29-generic root=UUID=2ba3f662-50a5-4db8-a5e1-ddaf5e09d5a9 ro 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 Tags: focal Uname: Linux 5.4.0-29-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/18/2018 dmi.bios.vendor: LENOVO dmi.bios.version: 8JCN43WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion Y530-15ICH dmi.modalias: dmi:bvnLENOVO:bvr8JCN43WW:bd07/18/2018:svnLENOVO:pn81FV:pvrLenovoLegionY530-15ICH:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrLenovoLegionY530-15ICH: dmi.product.family: Legion Y530-15ICH dmi.product.name: 81FV dmi.product.sku: LENOVO_MT_81FV_BU_idea_FM_Legion Y530-15ICH dmi.product.version: Lenovo Legion Y530-15ICH dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1875099/+subscriptions -- Mailing
[Kernel-packages] [Bug 1889780] 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 1889780 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 ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889780 Title: Unable to change screen resolution after upgrade to 5.4.0-42-generic Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: When booting using 5.4.0-42-generic kernel, screen resolution is fixed at 640x480 and there is no way to change it. Booting using 5.3.0-62-generic works fine. In "Displays", the dropdowns for Resolution only has 640x480 for selection. For Refresh Rate and Rotation there are no selections under dropdown. OS - 18.04 LTS Kernel - 5.4.0-42 previous 5.3.0-62-generic Dell Monitor NVIDIA GeForce GT 1030 CPU is AMD Ryzen 5 2600 X Socket AM4 Questions: How will I find out that this bug has been fixed? I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU work or are there specific video cards I should look at? Is there a site that recommends video cards for Linux? Thanks, Dave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1889780] Re: Unable to change screen resolution after upgrade to 5.4.0-42-generic
** Tags added: bionic ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1889780 Title: Unable to change screen resolution after upgrade to 5.4.0-42-generic Status in Ubuntu MATE: New Status in linux package in Ubuntu: Incomplete Bug description: When booting using 5.4.0-42-generic kernel, screen resolution is fixed at 640x480 and there is no way to change it. Booting using 5.3.0-62-generic works fine. In "Displays", the dropdowns for Resolution only has 640x480 for selection. For Refresh Rate and Rotation there are no selections under dropdown. OS - 18.04 LTS Kernel - 5.4.0-42 previous 5.3.0-62-generic Dell Monitor NVIDIA GeForce GT 1030 CPU is AMD Ryzen 5 2600 X Socket AM4 Questions: How will I find out that this bug has been fixed? I understand the issue is the NVIDIA proprietary drivers. Will any AMD GPU work or are there specific video cards I should look at? Is there a site that recommends video cards for Linux? Thanks, Dave To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1889780/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874567] Re: [nvidia] Rotating secondary monitor to portrait fails, results in landscape
Regarding bug mentioned in Side note 2 of #20 Comment (https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1874567/comments/20) I face the same issue, and am able to fix it via the fractional scaling method. I was able to reproduce this over two separate clean installs on my machine. Also following #20 comment helped solved the display rotating issue. Thank you devs for the fix. Regards -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1874567 Title: [nvidia] Rotating secondary monitor to portrait fails, results in landscape Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Won't Fix Status in mutter package in Ubuntu: Fix Released Status in nvidia-graphics-drivers-340 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-435 package in Ubuntu: Won't Fix Status in nvidia-graphics-drivers-440 package in Ubuntu: Won't Fix Status in gnome-control-center source package in Focal: Won't Fix Status in mutter source package in Focal: Fix Committed Status in nvidia-graphics-drivers-340 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-435 source package in Focal: Won't Fix Status in nvidia-graphics-drivers-440 source package in Focal: Won't Fix Bug description: [ Impact ] I have two monitors, with the secondary one rotated in a portrait orientation. Using the nvidia 440 drivers, the orientation is not applied when configuring in gnome settings (the displays go blank for a second, and then reappear in landscape orientation). Using nvidia settings, I can set the monitor rotation and offset correctly, however these settings do not persist on next boot (even when selecting to save to xorg.conf). When using the nouveau drivers, the orientation is applied correctly in gnome settings, and is persisted. [ Test case ] 1. Install nvidia drivers 2. Configure an external monitor to be in portrait mode in gnome-control-center 3. Apply the configuration 4. Expect configuration is properly working [ Regression potential ] Wrong screen size is set and panning is used. ProblemType: BugDistroRelease: 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 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2) ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: GNOME Date: Fri Apr 24 08:30:41 2020 DistUpgraded: 2020-04-20 18:27:13,972 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: focal DistroVariant: ubuntu DkmsStatus: nvidia, 440.64, 5.4.0-26-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation GK106 [GeForce GTX 660] [10de:11c0] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] GK106 [GeForce GTX 660] [1462:2871] InstallationDate: Installed on 2018-05-01 (723 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Shuttle Inc. SZ77 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=d2c17cee-7c37-429f-9cbb-9484a159f182 ro quiet splash vt.handoff=7SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to focal on 2020-04-20 (3 days ago) dmi.bios.date: 10/13/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1.13 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: FZ77 dmi.board.vendor: Shuttle Inc. dmi.board.version: 1.0 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.:bvr1.13:bd10/13/2014:svnShuttleInc.:pnSZ77:pvr1.0:rvnShuttleInc.:rnFZ77:rvr1.0:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: SZ77 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: Shuttle Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri
[Kernel-packages] [Bug 1888570] Re: poweroff not working after apt upgrade
OMG, Your comment: "#19 and forward assume..." Points into the right direction. When I install the "good" kernel-DEBs You provided the problem pops up... This happens although the "real" kernel deb (linux-image-unsigned-5.3.0-61-generic_5.3.0-61.55_amd64.deb) was not installed due to conflicts against my signed kernel of the same version. I then compare the snapshots made by SystemBack of these two versions. There are a lot of differences mainly the initrd (in boot) and althougth all *.ko inside modules. I remember that every try to install something that resuts in a kernel update (dkms and/or update-initrd) the problem ocurs. I therefore do a manual sudo update-initramfs -k all -u without installing anything else. -> Problem pops up! This happens even when I use my oldest system snapshot I have :-( So how to proceed ? (I am thinking about doing a fresh install of Ubuntu 20.4 LTS, but have to check if all tools I use will be available... FreeCad wasn't the first time I checked). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1888570 Title: poweroff not working after apt upgrade Status in linux package in Ubuntu: Confirmed Bug description: System-Information: Description: Ubuntu 18.04.4 LTS Release: 18.04 ## Working packages: - Kernel 5.3.0.61.114 - linux-firmware 1.173.18 Problem occurs when upgrading (anyone of) these packages - Kernel 5.3.0-62.56 - linux-firmware 1.173.19 I use an Acer Aspire E5-771G Notebook with a fresh installation of Ubuntu 18.04. Till the last upgrade everything works as expected. The last upgrade brings two new kernel versions (as mentioned above). Now the system stucks at the very end of the power down sequence. Even SysReq-O will not work (only SysReq-B will work). Because I use Systemback, I time shift to the previous system and then install package by package to see what will bring in the problem. If I install any of the mentioned kernel updates the problem will show up. I had ask the above question on "askubuntu.com". I was directed to upgrade the BIOS, But even after doing so the problem still persist. I am not sure if I do it right (APT pinning). I currently create a file /etc/apt/prefereces.d/kernel. I add an entry for every of the following packages to block the version mentioned above (Pin: version: Pin-Priority: -1): linux-generic-hwe-18.04 linux-headers-generic-hwe-18.04 linux-image-generic-hwe-18.04 linux-modules-nvidia-440-generic-hwe-18.04 linux-firmware After doing so "apt list --upgradeable" will not list the packages in question and the PC will power down normally (and SysReq-O WILL work). In the meanwhile there are newer versions of the kernel online, so the above mentioned pinning will allow the newer kernels to get installed and the problem will show up again. So I block these versions too. BTW: Due to the stuck I am able to see some other error messages that are not reported in the journal. The very last 3-5 lines show: shutdown [1]: Failed to wait for process: Protocol error These lines are present although in the working kernels, but hard to see, because the system powers down some ms after these lines are displayed! This problem seams to be solved more than one year ago in the upstream kernel! --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: gneiss 1929 F pulseaudio /dev/snd/controlC0: gneiss 1929 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-05-02 (448 days ago) InstallationMedia: MachineType: Acer Aspire E5-771G NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: LANG=de_DE.UTF-8 SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= PATH=(custom, no user) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-61-generic root=UUID=0b245afe-758b-4e45-a473-ad2077260d8f ro noplymouth resume=UUID=79a9e809-6ba1-491b-acfc-1816057c2dee ProcVersionSignature: Ubuntu 5.3.0-61.55~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-61-generic N/A linux-backports-modules-5.3.0-61-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-61-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip input lpadmin plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 09/02/2015 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.23 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: EA70_HB dmi.board.vendor: Acer dmi.board.version: Type2 - A01 Board Version
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
For crashes after suspend add: rcu_nocbs=0-N(number of cores -1) and idle=nowait as grub parameters update-grub and reboot you also need 5.4 or higher. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878951] Re: [nvidia] Hotplugging HDMI monitor is ignored, needs to be manually re-enabled
Workaround for me was to use external USB-C to HDMI adapter and plug the USB-C to the computer. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1878951 Title: [nvidia] Hotplugging HDMI monitor is ignored, needs to be manually re- enabled Status in mutter package in Ubuntu: New Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: Steps to reproduce: 1. Successfully connect AOC u2879vf external display by attaching HDMI cable 2. Remove the cable, output switches to the built-in display and external display goes black 3. Reconnect the HDMI cable again What is expected: The external screen should display the image (as in step 1) What happened instead: The system thinks the display is connected (see the xrandr output), but the external display is still black (no signal). The clumsy workaround is to use Super+P to switch to "built-in display only" and then back to "joint". After that, the external monitor comes back. xrandr outputs: Step 1 Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.00*+ 59.9450.0029.9829.9725.0023.98 1920x2160 59.99 1920x1080 60.0059.9450.00 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-1 connected 1920x1080+909+2160 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) Step 2 Screen 0: minimum 8 x 8, current 1920 x 1080, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 disconnected (normal left inverted right x axis y axis) DP-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) Step 3 Screen 0: minimum 8 x 8, current 3840 x 3240, maximum 32767 x 32767 DP-0 disconnected (normal left inverted right x axis y axis) HDMI-0 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 621mm x 341mm 3840x2160 60.00*+ 59.9450.0029.9829.9725.0023.98 1920x2160 59.99 1920x1080 60.0059.9450.00 1680x1050 59.95 1440x900 59.89 1280x1024 75.0260.02 1280x960 60.00 1280x720 60.0059.9450.00 1024x768 75.0370.0760.00 800x600 75.0072.1960.3256.25 720x576 50.00 720x480 59.94 640x480 75.0072.8159.9459.93 DP-1 connected 1920x1080+1097+2160 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.03*+ 40.02 DP-2 disconnected (normal left inverted right x axis y axis) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-29.33-generic 5.4.30 Uname: Linux 5.4.0-29-generic x86_64 NonfreeKernelModules: nvidia_modeset 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.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 440.64 Fri Feb 21 01:17:26 UTC 2020 GCC version: ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri May 15 17:43:16 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: NVIDIA Corporation TU117GLM [Quadro T2000 Mobile / Max-Q] [10de:1fb8] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Hewlett-Packard Company TU117GLM [Quadro T2000 Mobile / Max-Q] [103c:8611] InstallationDate: Installed on 2020-05-11 (3 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: HP HP ZBook 15 G6 ProcKernelCmdLine:
[Kernel-packages] [Bug 1690085]
Even with screensavers enabled and displays never going to sleep; I just experienced a crash on idle. Here's the logs (https://pastebin.com/D7SEJn9J). I did change the display configuration just before leaving my desk (with xrandr) which explain some of these logs. But I can see nothing from the kernel etc. The system just dies. On 7/24/20 4:17 AM, bugzilla-dae...@bugzilla.kernel.org wrote: > https://bugzilla.kernel.org/show_bug.cgi?id=196683 > > Victor Queiroz (victorcqueir...@gmail.com) changed: > > What|Removed |Added > > CC||victorcqueir...@gmail.com > > --- Comment #703 from Victor Queiroz (victorcqueir...@gmail.com) --- > I'm also experiencing severe and constant crashes with a Ryzen 5 3600X. I > also > had problems with my Ryzen 7 1700 and I was confident that the problem was > never going to have problems again with my Ryzen 5 3600X, but I was wrong. > > First months everything was fine, and after reinstalling the system, > everything > went wrong. Crashes daily and constantly. I had a critical Git repository > corrupted (luckily I could recover things in time), but it completely > destroyed > my experience with my PC and actually become a financial gap as I use the > computer to work on. > > Not sure what to do. I've decided to try until the end of this year not to > have > more crashes, but as a Linux user, I'm unsure I will ever think about buying > AMD again. I will always remember about the hassle and lost years I had with > this. > > Sometimes all you want to do is to have a great experience with your Linux > computer and BOOM, a hard freeze that requires manually turning the computer > off. It's ridiculous. To be honest, I expected much more from AMD. I hope > they'll fix it ASAP, we can't stand this anymore. Intel becomes our only > option > with this problem. > > I also opened an issue where I'm posting updates about my problems: > https://bugzilla.kernel.org/show_bug.cgi?id=208615 > -- You 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:
[Kernel-packages] [Bug 1776563] Re: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash
I still get freezes when resuming from suspend when using kde and opengl as a compositor, but this is not related to this issure, or is it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776563 Title: Acer Aspire A315 IOAPIC failure on Ubuntu 18.04, kernel hangs, can't load, kernel freeze (AMD Ryzen 5/Radeon/Raven) / AMDGPU Hybrid crash Status in amd: Fix Released Status in Linux: Fix Released Status in linux package in Ubuntu: Triaged Bug description: CPU: Ryzen 5 2500U VGA: Radeon 535 Notebook: Acer Aspire A315 This is a brand new notebook on the market with Ryzen 5/Radeon. The default kernel of Ubuntu(18.04) hangs at loading with message: tsc: Refined TSC clocksource calibration: 1996.250 MHz clocksource: tsc: mask: 0x max_cycles: (...), max_idle_ns: (...) Soft lockup Using pci=noacpi kernel parameter kernel loads without any problem but my notebook produces more heat than on Win10. If I know right Acer notebooks need ACPI to the correct power management. The same thing happens on mainline 4.17,4.18rc1-2. BIOS upgrade to the latest version: 1.08 hasn't helped This problem has been reported upstream: https://bugzilla.kernel.org/show_bug.cgi?id=200087 The latest correctly working kernel was 4.13.* but the heat problem was present with this too. To manage notifications about this bug go to: https://bugs.launchpad.net/amd/+bug/1776563/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875236] Re: Different kernel gives different RAM results
After installing updates EFI boot order's changed - Ubuntu now the first (previously Windows was the first). And now when booting Ubuntu recognizes all available memory (both 5.8 and 5.4 kernels). When I boot Windows as second in EFI boot order - Windows shows only 1.7 Gb available memory. So It seems that there is a bug in BIOS of my laptop ** Attachment added: "dmesg_5.8.0_w_first_boot_order.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875236/+attachment/5397915/+files/dmesg_5.8.0_w_first_boot_order.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/1875236 Title: Different kernel gives different RAM results Status in linux package in Ubuntu: Confirmed Bug description: Kernel from installed distro doesn't recognize all available memory on my laptop (Acer Swift 5 SF514-54T-59VD, Ubuntu Focal Fossa 20.04). When I load Linux distro (Focal Fossa 20.04 release) from installation USB-stick Kernel detects all memory (over 7Gb, part of memory used by graphic, on laptop installed 8Gb memory). Kernel from installed distro shows only 1.5 Gb available memory. Output of commands for installed system: $ lsb_release -a; uname -a; free -m No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux mxmaki 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 1628 806 110 163 711 498 Swap: 2047 24 2023 Output of commands for system from installation USB-stick: $ lsb_release -a; uname -a; free -m Distributor ID: Ubuntu Description: Ubuntu 20.04 LTS Release: 20.04 Codename: focal Linux ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux total used free shared buff/cache available Mem: 7641 763 3323 675 3554 5903 Swap: 0 0 0 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-18 (9 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200417) MachineType: Acer Swift SF514-54T Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-26-generic root=UUID=52fa8c38-ee95-4b49-834a-f21af8e7e904 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 12/19/2019 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.13 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: Yebisu_IL dmi.board.vendor: IL dmi.board.version: V1.13 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.13:bd12/19/2019:svnAcer:pnSwiftSF514-54T:pvrV1.13:rvnIL:rnYebisu_IL:rvrV1.13:cvnAcer:ct10:cvrChassisVersion: dmi.product.family: Swift 5 dmi.product.name: Swift SF514-54T dmi.product.sku: dmi.product.version: V1.13 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875236/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890023] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1890023/+attachment/5397904/+files/ProcEnviron.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/1890023 Title: Cheese is failing to start WebCam Status in linux package in Ubuntu: Confirmed Bug description: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.sku: Surface_Pro_1796 dmi.product.version: 1240D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Package: linux (not installed) Tags: focal wayland-session Uname: Linux 5.7.11-surface x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1890023] Re: Cheese is failing to start WebCam
apport information ** Tags added: apport-collected ** Description changed: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.sku: Surface_Pro_1796 dmi.product.version: 1240D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.4 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-07-10 (22 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: linux (not installed) + Tags: focal wayland-session + Uname: Linux 5.7.11-surface x86_64 + UnreportableReason: The running kernel is not an Ubuntu kernel + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo + _MarkForUpload: True ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1890023/+attachment/5397903/+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/1890023 Title: Cheese is failing to start WebCam Status in linux package in Ubuntu: Confirmed Bug description: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias:
[Kernel-packages] [Bug 1890023] 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 1890023 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/1890023 Title: Cheese is failing to start WebCam Status in linux package in Ubuntu: Incomplete Bug description: Cheese is failing to start WebCam and throws the below error. eese:15219): cheese-WARNING **: 11:07:46.807: Device '/dev/video11' has no supported format: gstv4l2object.c(3752): gst_v4l2_object_set_format_full (): /GstCameraBin:camerabin/GstWrapperCameraBinSrc:camera_source/GstBin:bin18/GstV4l2Src:v4l2src1: Call to TRY_FMT failed for NV12 @ 5120x3840: Invalid argument Operating System: Ubuntu 20.04.1 LTS Kernel: Linux 5.7.11-surface ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: cheese 3.34.0-1build1 Uname: Linux 5.7.11-surface x86_64 ApportVersion: 2.20.11-0ubuntu27.4 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Aug 2 11:03:16 2020 InstallationDate: Installed on 2020-07-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Microsoft Corporation Surface Pro ProcEnviron: LANGUAGE=en_IN:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash RelatedPackageVersions: cheese3.34.0-1build1 cheese-common 3.34.0-1build1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03.24.2020 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 235.3192.768 dmi.board.name: Surface Pro dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr235.3192.768:bd03.24.2020:svnMicrosoftCorporation:pnSurfacePro:pvr1240D0B09F5C09P38S01E0:rvnMicrosoftCorporation:rnSurfacePro:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro dmi.product.sku: Surface_Pro_1796 dmi.product.version: 1240D:0B:09F:5C:09P:38S:01E:0 dmi.sys.vendor: Microsoft Corporation lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bluetooth and Wireless LAN Composite Device Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1890023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
