[Kernel-packages] [Bug 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11
In bug 1881319 we're having trouble with ELAN touchpads due to elants_i2c being marked built-in in this bug. I created a PPA in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1881319 that mark it back to m while preserving PINCTRL_CHERRYVIEW as y. So I'm crossing post this message to those had been affected to find some help from you for verification of this proposed change. Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630238 Title: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: 16.10 beta 2, as installed fresh, has working keyboard and touchscreen on my Acer Chromebook R11. However, after dist-upgrade they're lost, so touchscreen doesn't work and I need to use external keyboard. Looking at config diff, the likely culprit is: +CONFIG_PINCTRL_AMD=y CONFIG_PINCTRL_BAYTRAIL=y -CONFIG_PINCTRL_CHERRYVIEW=y -CONFIG_PINCTRL_INTEL=y -CONFIG_PINCTRL_BROXTON=y -CONFIG_PINCTRL_SUNRISEPOINT=y +CONFIG_PINCTRL_CHERRYVIEW=m +CONFIG_PINCTRL_INTEL=m +CONFIG_PINCTRL_BROXTON=m +CONFIG_PINCTRL_SUNRISEPOINT=m As indicated at https://github.com/GalliumOS/galliumos- distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.". So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to m instead of y causes at least the touchscreen regression, and probably the keyboard one too. --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timo 1922 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/21/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887487] [NEW] range bound deduction test in test_verifier from ubuntu_bpf failed on F-oem-5.6
Public bug reported: Issue found on 5.6.0-1020.20 Focal OEM kernel, this should not be considered as a regression since the test can't be built before this cycle (bug 1879360) #555/p jgt32: range bound deduction, reg op imm FAIL Unexpected success to load! verification time 69 usec stack depth 8 processed 21 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #556/p jgt32: range bound deduction, reg1 op reg2, reg1 unknown FAIL Unexpected success to load! verification time 95 usec stack depth 8 processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #557/p jle32: range bound deduction, reg1 op reg2, reg2 unknown FAIL Unexpected success to load! verification time 85 usec stack depth 8 processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Tags: 5.6 focal kqa-blocker oem sru-20200629 ubuntu-bpf ** Description changed: Issue found on 5.6.0-1020.20 Focal OEM kernel, this should not be considered as a regression since the test can't be built before this cycle (bug 1879360) - #555/p jgt32: range bound deduction, reg op imm FAIL - Unexpected success to load! - verification time 69 usec - stack depth 8 - processed 21 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 - #556/p jgt32: range bound deduction, reg1 op reg2, reg1 unknown FAIL - Unexpected success to load! - verification time 95 usec - stack depth 8 - processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 - #557/p jle32: range bound deduction, reg1 op reg2, reg2 unknown FAIL - Unexpected success to load! - verification time 85 usec - stack depth 8 - processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 + Unexpected success to load! + verification time 69 usec + stack depth 8 + processed 21 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 + #556/p jgt32: range bound deduction, reg1 op reg2, reg1 unknown FAIL + Unexpected success to load! + verification time 95 usec + stack depth 8 + processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 + #557/p jle32: range bound deduction, reg1 op reg2, reg2 unknown FAIL + Unexpected success to load! + verification time 85 usec + stack depth 8 + processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 ** Tags added: 5.6 focal kqa-blocker oem sru-20200629 ubuntu-bpf ** Also affects: linux-oem-5.6 (Ubuntu) Importance: Undecided Status: New ** Summary changed: - range bound deduction in test_verifier from ubuntu_bpf failed on F-oem-5.6 + range bound deduction test in test_verifier from ubuntu_bpf failed on F-oem-5.6 -- 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/1887487 Title: range bound deduction test in test_verifier from ubuntu_bpf failed on F-oem-5.6 Status in ubuntu-kernel-tests: New Status in linux-oem-5.6 package in Ubuntu: New Bug description: Issue found on 5.6.0-1020.20 Focal OEM kernel, this should not be considered as a regression since the test can't be built before this cycle (bug 1879360) #555/p jgt32: range bound deduction, reg op imm FAIL Unexpected success to load! verification time 69 usec stack depth 8 processed 21 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #556/p jgt32: range bound deduction, reg1 op reg2, reg1 unknown FAIL Unexpected success to load! verification time 95 usec stack depth 8 processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 #557/p jle32: range bound deduction, reg1 op reg2, reg2 unknown FAIL Unexpected success to load! verification time 85 usec stack depth 8 processed 22 insns (limit 100) max_states_per_insn 0 total_states 2 peak_states 2 mark_read 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1887487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1716857] Re: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg
Test on Intel Tiger Lake platform with nvidia dGPU (N17S-G5 PCI\VEN_10DE_1C94). Distribution: Ubuntu Codename: focal kernel: 5.6.0-1018-oem NV driver: 440.100 nvidia_drm modeset=1 gdm3: 3.34.1-1ubuntu1 xserver-xorg-core: 2:1.20.8-2ubuntu2.1 The device can detect external 4K/UHD monitor sucessfully by HDMI or DP. It seems the original issue is not able to reproduce on this machine. However, the modeset has to be enabled for https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1769857/comments/5, but it is disabled by default currently. ** Attachment added: "Attach my external monitors edid for reference" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+attachment/5392513/+files/philips-edid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1716857 Title: nvidia-drm.modeset=1, gdm3 and optimus laptop results in no external monitors detected by Xorg Status in gdm3 package in Ubuntu: Opinion Status in nvidia-graphics-drivers-375 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-435 package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Bug description: Context: 17.10 development packages, nvidia binary driver 375, modeset=1 for the nvidia driver. ubuntu desktop (gnome shell), fresh install ThinkPad W520 in Nvidia Optimus bios mode. Nvidia profile. Result: no external monitors are detected. xrandr does not even list them as disconnected (normally it would list five external disconnected monitors) lsmod shows that nvidia driver is loaded and the modesetting is working at some level because there is no tearing on the laptop panel Note: modeset=1 is the only way to get flicker-free graphics on the laptop panel. modeset=1 is not the default setting but it is highly desirable. It works if lightdm is used which is why I have reported this against gdm3 My sessions in this configuration have mostly crashed after a few minutes with a gdm3 fail whale message in syslog but nothing else looks interesting. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1716857/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887461] Re: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04
Ubuntu 14.04/Trusty has reached End of Life (EoL) for standard support and the nvidia package is not included in the Extended Security Maintenance plan: https://wiki.ubuntu.com/SecurityTeam/ESM/14.04#A14.04_Infrastructure_ESM_Packages It looks like you are trying to use this PPA: https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa They updated Nvidia-430 for Trusty a few days ago, as you said. It would probably have been better to contact the admin(s) of the PPA directly: https://launchpad.net/%7Egraphics-drivers/+contactuser But since you have already filled in the bug report here, I will subscribe the admins and see if there is any response/interest to this report. ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1887461 Title: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04 Status in nvidia-graphics-drivers-384 package in Ubuntu: Incomplete Bug description: when I did apt-get update && apt-get dist-upgrade, I saw that nvidia-430 package had the version 64 update that was just released a few days ago. After installing it, my system wouldn't boot to xwindows. Failsafe boot to gui wouldn't work either The error messages looked similar to this bug report for nvidia drivers: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 Here's what my xorg.[0,failsafe].log showed: [43.645] (++) Log file: "/var/log/Xorg.failsafe.log", Time: Mon Jul 13 18:41:16 2020 [43.645] (++) Using config file: "/etc/X11/xorg.conf.failsafe" [43.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [43.645] Parse error on line 7 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass.conf "OutputClass" is not a valid section name. [43.645] (EE) Problem parsing the config file [43.645] (EE) Error parsing the config file [43.645] (EE) Fatal server error: [43.645] (EE) no screens found(EE) I have a *directory* named what the file is looking for (at least now after I downgraded nvidia...) here is the contents: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf# cat nvidia-drm-outputclass.conf # This xorg.conf.d configuration snippet configures the X server to # automatically load the nvidia X driver when it detects a device driven by the # nvidia-drm.ko kernel module. Please note that this only works on Linux kernels # version 3.9 or higher with CONFIG_DRM enabled, and only if the nvidia-drm.ko # kernel module is loaded before the X server is started. Section "OutputClass" Identifier "nvidia" MatchDriver"nvidia-drm" Driver "nvidia" EndSection basically, in the progress of filing this bug report, I downgraded to nvidia-418 and my system was about to boot again. To me, that says that nvidia-430.64 at least on Ubuntu 14.04 has a regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1887461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866910] Comment bridged from LTC Bugzilla
--- Comment From sthou...@in.ibm.com 2020-07-14 03:23 EDT--- @Naveen: Any update from try of kernel 5.4.0.14 or newer? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1866910 Title: [Ubu 20.04][5.4.0-12-generic] Observed Kernel OOPS while running LTP Test in Regression_Bucket Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: == Comment: #0 - Naveen Kumar T - 2020-01-28 23:43:11 == ---Problem Description--- Observed Kernel OOPS while running LTP Test in Regression_Bucket ---uname output--- root@ltc-wcwsp3:~# uname -a Linux ltc-wcwsp3 5.4.0-12-generic #15-Ubuntu SMP Tue Jan 21 17:56:24 UTC 2020 ppc64le ppc64le ppc64le GNU/Linux Machine Type = Witherspoon DD2.3 Test Environment: - Hardware: Witherspoon DD2.3 - Disro: Ubu 20.04 - Kernel: 5.4.0-12-generic Console log: 00:44:50 KernelOOPS: Kernel OOPS (machine in state '6'): Oops: Kernel access of bad area, sig: 11 [#1] 00:44:50 [44921.236545] LE PAGE_SIZE=64K MMU=Radix SMP NR_CPUS=2048 NUMA PowerNV 00:44:50 [44921.236555] Modules linked in: slip serport nfsv3 nfs fscache sctp quota_v2 quota_tree brd nls_iso8859_1 ntfs exfat(C) xfs overlay lp parport_pc ppdev parport st iptable_filter bpfilter cfg80211 xsk_diag tcp_diag udp_diag raw_diag inet_diag unix_diag af_packet_diag netlink_diag macsec binfmt_misc nfsd auth_rpcgss nfs_acl lockd grace sunrpc dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua vmx_crypto joydev input_leds mac_hid ofpart cmdlinepart at24 ipmi_powernv ipmi_devintf powernv_flash opal_prd ipmi_msghandler ibmpowernv mtd uio_pdrv_genirq uio sch_fq_codel ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 multipath linear mlx5_ib ib_uverbs ib_core hid_generic usbhid hid nouveau bnx2x ast drm_vram_helper mlx5_core i2c_algo_bit ttm crct10dif_vpmsum drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops nvme drm nvme_core mdio tg3 libcrc32c ahci libahci tls drm_panel_orientation_quirks 00:44:50 [44921.236608] crc32c_vpmsum mlxfw [last unloaded: parport_pc] 00:44:50 [44921.236841] CPU: 140 PID: 1134354 Comm: pty03 Tainted: G C5.4.0-12-generic #15-Ubuntu 00:44:50 [44921.236854] NIP: c0163964 LR: c008139b02d4 CTR: c0163930 00:44:50 [44921.236875] REGS: c000201ab34d7800 TRAP: 0300 Tainted: G C (5.4.0-12-generic) 00:44:50 [44921.236887] MSR: 90009033 CR: 84004880 XER: 2004 00:44:50 [44921.236900] CFAR: c008139b309c DAR: 0020 DSISR: 4000 IRQMASK: 1 00:44:50 [44921.236900] GPR00: c008139b02d4 c000201ab34d7a90 c1a5ba00 0800 00:44:50 [44921.236900] GPR04: c01ffa46f400 0020 c00813751260 0800 00:44:50 [44921.236900] GPR08: 0001 c1a924f0 c000201b09452000 c008139b3088 00:44:50 [44921.236900] GPR12: c0163930 c000201fff5f7c00 7c1913f34410 00:44:50 [44921.236900] GPR16: 7c1913fc 7c1913f30320 7c1913caf240 7c1913f34420 00:44:50 [44921.236900] GPR20: 0008 00:44:50 [44921.236900] GPR24: 0ce690ad0288 0ce690ad02a8 c000201c09f97570 00:44:50 [44921.236900] GPR28: c000201b1336da00 ffe7 c000201b09452000 00:44:50 [44921.237006] NIP [c0163964] queue_work_on+0x34/0xb0 00:44:50 [44921.237027] LR [c008139b02d4] slip_write_wakeup+0x3c/0x60 [slip] 00:44:50 [44921.237046] Call Trace: 00:44:50 [44921.237063] [c000201ab34d7a90] [c000201ab34d7ae0] 0xc000201ab34d7ae0 (unreliable) 00:44:50 [44921.237096] [c000201ab34d7ac0] [c008139b02d4] slip_write_wakeup+0x3c/0x60 [slip] 00:44:50 [44921.237130] [c000201ab34d7ae0] [c08e53c0] tty_wakeup+0x90/0xe0 00:44:50 [44921.237173] [c000201ab34d7b10] [c08f84ac] pty_unthrottle+0x2c/0x60 00:44:50 [44921.237215] [c000201ab34d7b40] [c08f0500] tty_unthrottle+0x80/0xb0 00:44:50 [44921.237256] [c000201ab34d7b70] [c08f0bc0] __tty_perform_flush+0x130/0x150 00:44:50 [44921.237298] [c000201ab34d7ba0] [c08ec6cc] n_tty_ioctl+0x20c/0x2b0 00:44:50 [44921.237339] [c000201ab34d7bf0] [c08e8748] tty_ioctl+0x3f8/0xe80 00:44:50 [44921.237360] [c000201ab34d7d00] [c0494f8c] do_vfs_ioctl+0x96c/0xbe0 00:44:50 [44921.237381] [c000201ab34d7db0] [c04952c4] ksys_ioctl+0xc4/0x110 00:44:50 [44921.237411] [c000201ab34d7e00] [c0495338] sys_ioctl+0x28/0x80 00:44:50 [44921.237432] [c000201ab34d7e20] [c000b278] system_call+0x5c/0x68 00:44:50 [44921.237462] Instruction dump: 00:44:50 [44921.237479]
[Kernel-packages] [Bug 1887214] Re: [18.04 LTS] Somehow wifi network latency is too high (1000~3000 ms)
** Tags added: hwe-networking-wifi ** Summary changed: - [18.04 LTS] Somehow wifi network latency is too high (1000~3000 ms) + [18.04 LTS] Intel 8265 / 8275 [8086:24fd] Subsystem [8086:0010] Somehow wifi network latency is too high (1000~3000 ms) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887214 Title: [18.04 LTS] Intel 8265 / 8275 [8086:24fd] Subsystem [8086:0010] Somehow wifi network latency is too high (1000~3000 ms) Status in linux package in Ubuntu: Incomplete Bug description: [Problem description] Somehow wifi network latency is too high. (1000~3000 ms) DUT: - Product: Lenovo X1C6 - BIOS Information: Vendor: LENOVO Version: N23ET74W (1.49 ) Release Date: 06/03/2020 - Wifi information: Intel Wireless 8265 / 8275 driverversion=5.3.0-62-generic firmware=36.9f0a2d68.0 - OS: Ubuntu 18.04.4 LTS/Linux 5.3.0-62-generic/X86-64 [Test steps] 1. Boot up Ubuntu 18.04.4 LTS. 2. Open terminal. 3. To execute ping command, and target is in the local network. (For example: local gateway) 4. After few mins, I noticed that network latency will get worse. Sample output: 64 bytes from 192.168.1.1: icmp_seq=714 ttl=64 time=2.31 ms 64 bytes from 192.168.1.1: icmp_seq=715 ttl=64 time=1.61 ms 64 bytes from 192.168.1.1: icmp_seq=716 ttl=64 time=8.93 ms 64 bytes from 192.168.1.1: icmp_seq=717 ttl=64 time=59.0 ms 64 bytes from 192.168.1.1: icmp_seq=718 ttl=64 time=101 ms 64 bytes from 192.168.1.1: icmp_seq=719 ttl=64 time=155 ms 64 bytes from 192.168.1.1: icmp_seq=720 ttl=64 time=212 ms 64 bytes from 192.168.1.1: icmp_seq=721 ttl=64 time=347 ms 64 bytes from 192.168.1.1: icmp_seq=722 ttl=64 time=485 ms 64 bytes from 192.168.1.1: icmp_seq=723 ttl=64 time=663 ms 64 bytes from 192.168.1.1: icmp_seq=724 ttl=64 time=914 ms 64 bytes from 192.168.1.1: icmp_seq=725 ttl=64 time=1149 ms 64 bytes from 192.168.1.1: icmp_seq=726 ttl=64 time=1490 ms 64 bytes from 192.168.1.1: icmp_seq=727 ttl=64 time=1828 ms 64 bytes from 192.168.1.1: icmp_seq=728 ttl=64 time=2154 ms 64 bytes from 192.168.1.1: icmp_seq=729 ttl=64 time=2609 ms 64 bytes from 192.168.1.1: icmp_seq=730 ttl=64 time=2851 ms 64 bytes from 192.168.1.1: icmp_seq=731 ttl=64 time=2825 ms 64 bytes from 192.168.1.1: icmp_seq=732 ttl=64 time=2184 ms 64 bytes from 192.168.1.1: icmp_seq=733 ttl=64 time=2582 ms 64 bytes from 192.168.1.1: icmp_seq=734 ttl=64 time=1898 ms 64 bytes from 192.168.1.1: icmp_seq=735 ttl=64 time=1377 ms 5. Same machine when I switched to W10 then I didn't encounter this symptom. [Expected result] Wifi network latency should not over 2~3 ms at least. [Actual result] Wifi network latency is too high. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lawrence 2772 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-30 (772 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20KGS0FV00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=65f0f796-b6da-4d46-98a5-325713eee95b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-62-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: 06/03/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET74W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS0FV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET74W(1.49):bd06/03/2020:svnLENOVO:pn20KGS0FV00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS0FV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS0FV00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887345] Re: Remove "master" references from linux-gcp
** Package changed: linux-gcp (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887345 Title: Remove "master" references from linux-gcp Status in linux package in Ubuntu: Triaged Bug description: Since the "blacklist" "whitelist" "master" "slave" terminology is now officially banned by Linux, this terminology should be removed from this repo. Ref: https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/ Such files include: - /usr/src/linux-gcp-headers-5.4.0-1019/include/trace/events/fsi_master_ast_cf.h - /usr/src/linux-gcp-headers-5.4.0-1019/include/trace/events/fsi_master_gpio.h - /usr/src/linux-gcp-headers-5.4.0-1019/include/linux/i3c/master.h - /usr/src/linux-gcp-headers-5.4.0-1019/drivers/i3c/master - /usr/src/linux-gcp-headers-5.4.0-1019/drivers/w1/masters - /usr/src/linux-gcp-headers-5.4.0-1019/arch/m68k/include/asm/q40_master.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/spi/master.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/thrustmaster - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/snd/vmaster.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/w1/master - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/hid/thrustmaster.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/net/l3/master - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/dw/i3c/master.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/cdns/i3c/master.h - /usr/src/linux-gcp-headers-5.4.0-1018/include/trace/events/fsi_master_ast_cf.h - /usr/src/linux-gcp-headers-5.4.0-1018/include/trace/events/fsi_master_gpio.h - /usr/src/linux-gcp-headers-5.4.0-1018/include/linux/i3c/master.h - /usr/src/linux-gcp-headers-5.4.0-1018/drivers/i3c/master - /usr/src/linux-gcp-headers-5.4.0-1018/drivers/w1/masters - /usr/src/linux-gcp-headers-5.4.0-1018/arch/m68k/include/asm/q40_master.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/spi/master.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/thrustmaster - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/snd/vmaster.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/w1/master - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/hid/thrustmaster.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/net/l3/master - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/dw/i3c/master.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/cdns/i3c/master.h I didn't make the rules - It's up to you if you want to enforce them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu Focal) Importance: Undecided => Medium ** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] On the machine of Lenovo IdeaPad 5 15IIL05, the audio doesn't work, checking the dmesg, I found the audio driver fails to initialize because it fails on i915 audio codec probe. [Fix] backport 3 patches from mainline kernel, move the i915 audio codec init earlier. [Test Case] Boot the kernel with these 3 patches, check dmesg, there is no i915 audio codec probe error anymore, and audio driver initializes successfully, and input and output audio devices all work. [Regression Risk] Low, already tested these 3 patches on a couple of LENOVO dmic machines (cnl and cml machines), all work as well as before. On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 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-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1885693] Re: Unwanted reboot after screen is locked
After running "xset s off -dpms" I haven't seen any crashes for a few days. I used to have a few crashes every day when connecting to the dock. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885693 Title: Unwanted reboot after screen is locked Status in linux package in Ubuntu: Incomplete Bug description: After locking the screen to leave the computer for a few minutes, I come back to a computer that is freshly rebooted. It usually happens 1 out of 4 or 5 times when locking the screen. This only happens when my laptop (Lenovo T470s, also seen with T490) is connected to my USB-C dock. The problem has been observed with 18.04, 19.10 and 20.04. /var/log/syslog contains: Jun 30 10:47:05 jbn3 kernel: [33470.649606] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jun 30 10:47:23 jbn3 kernel: [33488.187142] [drm] Reducing the compressed framebuffer size. This may lead to less power savings than a non-reduced-size. Try to increase stolen memory size if available in BIOS. Jun 30 10:47:23 jbn3 kernel: [33488.419723] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in pixel_rate (expected 241500, found 482999) Jun 30 10:47:23 jbn3 kernel: [33488.419818] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in shared_dpll (expected a870403d, found 5108ff4b) Jun 30 10:47:23 jbn3 kernel: [33488.419902] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in dpll_hw_state.ctrl1 (expected 0x0003, found 0x0001) Jun 30 10:47:23 jbn3 kernel: [33488.419986] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in base.adjusted_mode.crtc_clock (expected 241500, found 482999) Jun 30 10:47:23 jbn3 kernel: [33488.420067] [drm:pipe_config_mismatch [i915]] *ERROR* mismatch in port_clock (expected 27, found 54) Jun 30 10:47:23 jbn3 kernel: [33488.420071] [ cut here ] Jun 30 10:47:23 jbn3 kernel: [33488.420072] pipe state doesn't match! Jun 30 10:47:23 jbn3 kernel: [33488.420249] WARNING: CPU: 0 PID: 2300 at drivers/gpu/drm/i915/display/intel_display.c:13158 verify_crtc_state+0x2ad/0x300 [i915] Jun 30 10:47:23 jbn3 kernel: [33488.420251] Modules linked in: xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xfrm_algo xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 bpfilter br_netfilter bridge stp llc hid_generic snd_usb_audio usbhid snd_usbmidi_lib hid cdc_ether r8152 vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) ccm aufs overlay bnep nls_iso8859_1 joydev intel_rapl_msr mei_hdcp cdc_mbim qcserial usb_wwan cdc_wdm usbserial cdc_ncm usbnet mii uvcvideo btusb btrtl snd_hda_codec_hdmi btbcm btintel intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp bluetooth kvm_intel snd_hda_codec_realtek snd_hda_codec_generic kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec intel_cstate rmi_smbus ecdh_generic rmi_core intel_rapl_perf ecc videobuf2_vmalloc snd_hda_core videobuf2_memops videobuf2_v4l2 snd_hwdep iwlmvm snd_seq_midi videobuf2_common snd_seq_midi_event mac80211 videodev intel_wmi_thunderbolt libarc4 snd_pcm input_leds iwlwifi Jun 30 10:47:23 jbn3 kernel: [33488.420310] snd_rawmidi mc serio_raw snd_seq wmi_bmof thinkpad_acpi nvram cfg80211 ledtrig_audio mei_me intel_xhci_usb_role_switch mei snd_seq_device intel_pch_thermal snd_timer ucsi_acpi typec_ucsi roles typec snd soundcore acpi_pad mac_hid sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt uas usb_storage i915 crct10dif_pclmul crc32_pclmul nvme ghash_clmulni_intel i2c_algo_bit aesni_intel crypto_simd cryptd glue_helper psmouse e1000e i2c_i801 nvme_core drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops thunderbolt drm wmi video Jun 30 10:47:23 jbn3 kernel: [33488.420358] CPU: 0 PID: 2300 Comm: Xorg Tainted: G OE 5.4.0-39-generic #43-Ubuntu Jun 30 10:47:23 jbn3 kernel: [33488.420360] Hardware name: LENOVO 20HF004MMX/20HF004MMX, BIOS N1WET59W (1.38 ) 04/22/2020 Jun 30 10:47:23 jbn3 kernel: [33488.420437] RIP: 0010:verify_crtc_state+0x2ad/0x300 [i915] Jun 30 10:47:23 jbn3 kernel: [33488.420441] Code: b6 45 bf e9 8d fe ff ff 80 3d 45 77 10 00 00 0f b6 f0 48 c7 c7 40 aa 85 c0 75 32 e8 1d 48 d5 ff e9 1e fe ff ff e8 6e 9e b1 ef <0f> 0b e9 1b ff ff ff e8 62 9e b1 ef 0f 0b e9 85 fe ff ff e8 56 9e Jun 30 10:47:23 jbn3 kernel: [33488.420444] RSP: 0018:b1b74290fa80 EFLAGS: 00010282 Jun 30 10:47:23 jbn3 kernel: [33488.420448] RAX: RBX: 97a35f0002b0 RCX: 0006 Jun 30 10:47:23 jbn3 kernel: [33488.420450] RDX: 0007 RSI: 0092 RDI: 97a3724178c0 Jun 30 10:47:23 jbn3 kernel:
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
Please try test kernel in https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1881319, which marks CONFIG_TOUCHSCREEN_ELAN as m only. We'll also need verification from users of bug 1630238 before committing to ubuntu kernel to prevent regression loop. This ppa is currently not yet available, but is supposed to finish to build in a couple of hours. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW 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: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1630238] Re: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11
Also filed new bug https://github.com/GalliumOS/galliumos- distro/issues/585 as the original https://github.com/GalliumOS /galliumos-distro/issues/270 is locked. ** Bug watch added: github.com/GalliumOS/galliumos-distro/issues #585 https://github.com/GalliumOS/galliumos-distro/issues/585 ** Bug watch added: github.com/GalliumOS/galliumos-distro/issues #270 https://github.com/GalliumOS/galliumos-distro/issues/270 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1630238 Title: [regression 4.8.0-14 -> 4.8.0-17] keyboard and touchscreen lost on Acer Chromebook R11 Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Yakkety: Fix Released Status in linux source package in Zesty: Fix Released Bug description: 16.10 beta 2, as installed fresh, has working keyboard and touchscreen on my Acer Chromebook R11. However, after dist-upgrade they're lost, so touchscreen doesn't work and I need to use external keyboard. Looking at config diff, the likely culprit is: +CONFIG_PINCTRL_AMD=y CONFIG_PINCTRL_BAYTRAIL=y -CONFIG_PINCTRL_CHERRYVIEW=y -CONFIG_PINCTRL_INTEL=y -CONFIG_PINCTRL_BROXTON=y -CONFIG_PINCTRL_SUNRISEPOINT=y +CONFIG_PINCTRL_CHERRYVIEW=m +CONFIG_PINCTRL_INTEL=m +CONFIG_PINCTRL_BROXTON=m +CONFIG_PINCTRL_SUNRISEPOINT=m As indicated at https://github.com/GalliumOS/galliumos- distro/issues/270, " in the GalliumOS 4.7.2 kernel we needed to add CONFIG_PINCTRL_CHERRYVIEW=y (must be y, not m) in addition to CONFIG_TOUCHSCREEN_ELAN to get the touchscreen working on CYAN.". So, the change of Intel related PINCTRLs (specifically the CHERRYVIEW one) to m instead of y causes at least the touchscreen regression, and probably the keyboard one too. --- ApportVersion: 2.20.3-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: timo 1922 F pulseaudio CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 InstallationDate: Installed on 2016-10-04 (0 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160922) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.8.0-17-generic root=UUID=7f6c179e-9a4c-4837-869e-0ef2f04a3d61 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-17.19-generic 4.8.0-rc7 RelatedPackageVersions: linux-restricted-modules-4.8.0-17-generic N/A linux-backports-modules-4.8.0-17-generic N/A linux-firmware1.161 Tags: yakkety Uname: Linux 4.8.0-17-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 08/21/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd08/21/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1630238/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1886269] Re: ps/2 mouse not working
Ok, thanks for your valuable suggestions. On Tue, 14 Jul, 2020, 10:35 You-Sheng Yang, <1886...@bugs.launchpad.net> wrote: > @Jatinderpal, couldn't get you. So you've reinstalled your system, get > upgraded, then is your PS/2 mouse working as expected now? If not, and > yet the kernel parameter still works for you, then you may choose not to > fix it and carry it forever. Leave this bug in INCOMPLETE state and it > will expire after 60 days. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1886269 > > Title: > ps/2 mouse not working > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > ps/2 mouse not working , gave some command in terminal , this bug came > out. > > See https://ark.intel.com/content/www/us/en/ark/products/39683/intel- > desktop-board-dg41rq.html > > ProblemType: Bug > DistroRelease: Ubuntu 18.04 > Package: xorg 1:7.7+19ubuntu7.1 > ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 > Uname: Linux 4.15.0-109-generic x86_64 > .tmp.unity_support_test.0: > > ApportVersion: 2.20.9-0ubuntu7.15 > Architecture: amd64 > CompositorRunning: None > CurrentDesktop: ubuntu:GNOME > Date: Sat Jul 4 19:25:07 2020 > DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: > './xorg_fix_proprietary.py' > DistroCodename: bionic > DistroVariant: ubuntu > GraphicsCard: >Intel Corporation 4 Series Chipset Integrated Graphics Controller > [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) > Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics > Controller [8086:d613] > InstallationDate: Installed on 2020-06-30 (4 days ago) > InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 > (20160420.1) > ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic > root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 > SourcePackage: xorg > UpgradeStatus: Upgraded to bionic on 2020-07-03 (1 days ago) > dmi.bios.date: 01/08/2009 > dmi.bios.vendor: Intel Corp. > dmi.bios.version: RQG4110H.86A.0009.2009.0108.1005 > dmi.board.asset.tag: To be filled by O.E.M. > dmi.board.name: DG41RQ > dmi.board.vendor: Intel Corporation > dmi.board.version: AAE54511-203 > dmi.chassis.type: 3 > dmi.modalias: > dmi:bvnIntelCorp.:bvrRQG4110H.86A.0009.2009.0108.1005:bd01/08/2009:svn:pn:pvr:rvnIntelCorporation:rnDG41RQ:rvrAAE54511-203:cvn:ct3:cvr: > version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 > version.libdrm2: libdrm2 2.4.101-2~18.04.1 > version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 > version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 > version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 > version.xserver-xorg-input-evdev: xserver-xorg-input-evdev > 1:2.10.5-1ubuntu1 > version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 > version.xserver-xorg-video-intel: xserver-xorg-video-intel > 2:2.99.917+git20171229-1 > version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 > xserver.bootTime: Fri Jul 3 08:17:23 2020 > xserver.configfile: default > xserver.errors: > > xserver.logfile: /var/log/Xorg.0.log > xserver.outputs: > > xserver.version: 2:1.18.4-0ubuntu0.8 > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886269/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886269 Title: ps/2 mouse not working Status in linux package in Ubuntu: Incomplete Bug description: ps/2 mouse not working , gave some command in terminal , this bug came out. See https://ark.intel.com/content/www/us/en/ark/products/39683/intel- desktop-board-dg41rq.html ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-109.110-generic 4.15.18 Uname: Linux 4.15.0-109-generic x86_64 .tmp.unity_support_test.0: ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Jul 4 19:25:07 2020 DistUpgraded: 2020-07-03 12:12:10,464 DEBUG Running PostInstallScript: './xorg_fix_proprietary.py' DistroCodename: bionic DistroVariant: ubuntu GraphicsCard: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:2e32] (rev 03) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation 4 Series Chipset Integrated Graphics Controller [8086:d613] InstallationDate: Installed on 2020-06-30 (4 days ago) InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-109-generic root=UUID=7093ceae-5eb7-497e-8809-023c282ce7a1 ro quiet splash vt.handoff=1 SourcePackage: xorg UpgradeStatus: Upgraded to
[Kernel-packages] [Bug 1886977] Re: [Toshiba Portege R830] Grid-like cursor movement on touchpad
** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886977 Title: [Toshiba Portege R830] Grid-like cursor movement on touchpad Status in linux package in Ubuntu: Incomplete Bug description: Moving cursor using touchpad goes in zigzag pattern, when moving diagonally. The laptop is Toshiba Portege R830 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: libinput10 1.10.4-1ubuntu0.18.04.1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 Uname: Linux 5.3.0-62-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CurrentDesktop: MATE Date: Thu Jul 9 17:35:34 2020 SourcePackage: libinput UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886977/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
** Description changed: + [Impact] + On the machine of Lenovo IdeaPad 5 15IIL05, the audio doesn't work, + checking the dmesg, I found the audio driver fails to initialize + because it fails on i915 audio codec probe. + + [Fix] + backport 3 patches from mainline kernel, move the i915 audio codec + init earlier. + + [Test Case] + Boot the kernel with these 3 patches, check dmesg, there is no + i915 audio codec probe error anymore, and audio driver initializes + successfully, and input and output audio devices all work. + + [Regression Risk] + Low, already tested these 3 patches on a couple of LENOVO dmic + machines (cnl and cml machines), all work as well as before. + + On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 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-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - XDG_RUNTIME_DIR= - LANG=en_US.UTF-8 - SHELL=/bin/bash + 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-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash 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 + linux-restricted-modules-5.4.0-40-generic N/A + linux-backports-modules-5.4.0-40-generic N/A + linux-firmware1.187.1 Tags: wayland-session focal Uname: Linux 5.4.0-40-generic x86_64 UpgradeStatus: No upgrade
[Kernel-packages] [Bug 1887397] Re: perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
** Bug watch added: Debian Bug tracker #964605
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964605
** Also affects: linux (Debian) via
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=964605
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1887397
Title:
perf build broken after updating to bintuils 2.34.90.20200706-1ubuntu1
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Groovy:
Incomplete
Status in linux package in Debian:
Unknown
Bug description:
After updating to binutils 2.34.90.20200706-1ubuntu1 Linux' perf build
is failing with the following error:
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
ignoring invalid character `@' in script
/usr/bin/ld:/tmp/autopkgtest.440kEd/build.N7g/src/debian/build/tools-perarch/tools/lib/traceevent/plugins/libtraceevent-dynamic-list:2:
syntax error in dynamic list
collect2: error: ld returned 1 exit status
The file mentioned in the error (libtraceevent-dynamic-list) contains
some '@' that ld doesn't seem to like:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail@@GLIBC_2.4;
free@@GLIBC_2.2.5;
memset@@GLIBC_2.2.5;
realloc@@GLIBC_2.2.5;
sprintf@@GLIBC_2.2.5;
strcmp@@GLIBC_2.2.5;
strdup@@GLIBC_2.2.5;
strncmp@@GLIBC_2.2.5;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
The same file generated in a Focal environment (w/ binutils
2.34-6ubuntu1) looks as following:
$ cat lib/traceevent/plugins/libtraceevent-dynamic-list
{
__stack_chk_fail;
free;
memset;
realloc;
sprintf;
strcmp;
strdup;
strncmp;
tep_find_any_field;
tep_find_field;
tep_find_function;
tep_find_function_address;
tep_get_field_raw;
tep_get_field_val;
tep_is_file_bigendian;
tep_is_local_bigendian;
tep_plugin_add_options;
tep_plugin_remove_options;
tep_print_func_field;
tep_print_num_field;
tep_read_number_field;
tep_register_comm;
tep_register_event_handler;
tep_register_print_function;
tep_unregister_event_handler;
tep_unregister_print_function;
trace_seq_printf;
trace_seq_putc;
trace_seq_puts;
trace_seq_terminate;
warning;
};
And here is the chunk of Makefile that is generating this file:
define do_generate_dynamic_list_file
symbol_type=`$(NM) -u -D $1 | awk 'NF>1 {print $$1}' | \
xargs echo "U w W" | tr 'w ' 'W\n' | sort -u | xargs echo`;\
if [ "$$symbol_type" = "U W" ];then \
(echo '{'; \
$(NM) -u -D $1 | awk 'NF>1 {print "\t"$$2";"}' | sort -u;\
echo '};'; \
) > $2; \
else\
(echo Either missing one of [$1] or bad version of $(NM))
1>&2;\
fi
My guess is that something changed in the output of `nm` to show the @
charaters that ld does not like.
This problem is currently breaking all kernel builds in Groovy.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887397/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887505] [NEW] GPE interrupt on Macbook Pro - kworker with high CPU usage
Public bug reported: Greetings, This issue is fixed by booting with the following kernel argument: acpi_mask_gpe=0x06 The effects of this bug were pretty devastating on the system; very slow and the fans were spinning very hard. Cores 0 and 1 were running at nearly 100% on an otherwise idle system. It seems that this bug is well documented: https://bugzilla.kernel.org/show_bug.cgi?id=117481 (2016) https://bugzilla.redhat.com/show_bug.cgi?id=1192856 (2015) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577629 (2016) I am new, so I am unsure whether it would be within the scope of Ubuntu to make it an option during installation to include device-specific kernel quirks for bugs such as this, and I wanted to check and see what the go is. If we know it is affecting a certain set of Macbook Pro's then would it be possible to detect the system and then add the kernel argument? Best, Nick ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 1865 F pulseaudio /dev/snd/controlC1: nick 1865 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 14 19:43:20 2020 InstallationDate: Installed on 2020-07-13 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:8289 Apple, Inc. Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 003: ID 05ac:0262 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,2 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e9ad07dc-6627-4a53-8cc5-b2f8967c933c ro quiet splash acpi_mask_gpe=0x06 vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 149.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-3CBD00234E554E41 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-3CBD00234E554E41 dmi.modalias: dmi:bvnAppleInc.:bvr149.0.0.0.0:bd09/17/2018:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41: dmi.product.family: Mac dmi.product.name: MacBookPro11,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal wayland-session -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887505 Title: GPE interrupt on Macbook Pro - kworker with high CPU usage Status in linux package in Ubuntu: New Bug description: Greetings, This issue is fixed by booting with the following kernel argument: acpi_mask_gpe=0x06 The effects of this bug were pretty devastating on the system; very slow and the fans were spinning very hard. Cores 0 and 1 were running at nearly 100% on an otherwise idle system. It seems that this bug is well documented: https://bugzilla.kernel.org/show_bug.cgi?id=117481 (2016) https://bugzilla.redhat.com/show_bug.cgi?id=1192856 (2015) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577629 (2016) I am new, so I am unsure whether it would be within the scope of Ubuntu to make it an option during installation to include device- specific kernel quirks for bugs such as this, and I wanted to check and see what the go is. If we know it is affecting a certain set of Macbook Pro's then would it be possible to detect the system and then add the kernel argument? Best, Nick ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 1865 F pulseaudio /dev/snd/controlC1: nick 1865 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop:
Re: [Kernel-packages] [Bug 1887340] Re: system freezes including keyboard and mouse whenever a CD is played
Okay. On Mon, 13 Jul 2020, 6:10 pm Kai-Heng Feng, <1887...@bugs.launchpad.net> wrote: > Please test latest mainline kernel: > https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ > > If latest kernel doesn't fix it then we need to bisect kernel. > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1887340 > > Title: > system freezes including keyboard and mouse whenever a CD is played > > To manage notifications about this bug go to: > https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887340/+subscriptions > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887340 Title: system freezes including keyboard and mouse whenever a CD is played Status in linux package in Ubuntu: Incomplete Bug description: Consistently, whenever a CD is played, the system freezes including keyboard and mouse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pks1207 F pulseaudio /dev/snd/controlC2: pks1207 F pulseaudio /dev/snd/controlC0: pks1207 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 11:42:33 2020 InstallationDate: Installed on 2020-01-06 (188 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=ff43ab9d-9612-4215-8f0c-d11964542c44 ro quiet splash vt.handoff=7 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-16 (57 days ago) dmi.bios.date: 05/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A88-M 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.:bvr1702:bd05/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. 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/1887340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887505] 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/1887505 Title: GPE interrupt on Macbook Pro - kworker with high CPU usage Status in linux package in Ubuntu: Confirmed Bug description: Greetings, This issue is fixed by booting with the following kernel argument: acpi_mask_gpe=0x06 The effects of this bug were pretty devastating on the system; very slow and the fans were spinning very hard. Cores 0 and 1 were running at nearly 100% on an otherwise idle system. It seems that this bug is well documented: https://bugzilla.kernel.org/show_bug.cgi?id=117481 (2016) https://bugzilla.redhat.com/show_bug.cgi?id=1192856 (2015) https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1577629 (2016) I am new, so I am unsure whether it would be within the scope of Ubuntu to make it an option during installation to include device- specific kernel quirks for bugs such as this, and I wanted to check and see what the go is. If we know it is affecting a certain set of Macbook Pro's then would it be possible to detect the system and then add the kernel argument? Best, Nick ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nick 1865 F pulseaudio /dev/snd/controlC1: nick 1865 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jul 14 19:43:20 2020 InstallationDate: Installed on 2020-07-13 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 006: ID 05ac:8289 Apple, Inc. Bus 001 Device 002: ID 0a5c:4500 Broadcom Corp. BCM2046B1 USB 2.0 Hub (part of BCM2046 Bluetooth) Bus 001 Device 003: ID 05ac:0262 Apple, Inc. Apple Internal Keyboard / Trackpad Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Apple Inc. MacBookPro11,2 ProcEnviron: LANGUAGE=en_AU:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_AU.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=e9ad07dc-6627-4a53-8cc5-b2f8967c933c ro quiet splash acpi_mask_gpe=0x06 vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/17/2018 dmi.bios.vendor: Apple Inc. dmi.bios.version: 149.0.0.0.0 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-3CBD00234E554E41 dmi.board.vendor: Apple Inc. dmi.board.version: MacBookPro11,2 dmi.chassis.type: 10 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-3CBD00234E554E41 dmi.modalias: dmi:bvnAppleInc.:bvr149.0.0.0.0:bd09/17/2018:svnAppleInc.:pnMacBookPro11,2:pvr1.0:rvnAppleInc.:rnMac-3CBD00234E554E41:rvrMacBookPro11,2:cvnAppleInc.:ct10:cvrMac-3CBD00234E554E41: dmi.product.family: Mac dmi.product.name: MacBookPro11,2 dmi.product.sku: System SKU# dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887345] Re: Remove "master" references from linux-gcp
** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887345 Title: Remove "master" references from linux-gcp Status in linux package in Ubuntu: Triaged Bug description: Since the "blacklist" "whitelist" "master" "slave" terminology is now officially banned by Linux, this terminology should be removed from this repo. Ref: https://www.zdnet.com/article/linux-team-approves-new-terminology-bans-terms-like-blacklist-and-slave/ Such files include: - /usr/src/linux-gcp-headers-5.4.0-1019/include/trace/events/fsi_master_ast_cf.h - /usr/src/linux-gcp-headers-5.4.0-1019/include/trace/events/fsi_master_gpio.h - /usr/src/linux-gcp-headers-5.4.0-1019/include/linux/i3c/master.h - /usr/src/linux-gcp-headers-5.4.0-1019/drivers/i3c/master - /usr/src/linux-gcp-headers-5.4.0-1019/drivers/w1/masters - /usr/src/linux-gcp-headers-5.4.0-1019/arch/m68k/include/asm/q40_master.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/spi/master.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/thrustmaster - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/snd/vmaster.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/w1/master - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/hid/thrustmaster.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/net/l3/master - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/dw/i3c/master.h - /usr/src/linux-headers-5.4.0-1018-gcp/include/config/cdns/i3c/master.h - /usr/src/linux-gcp-headers-5.4.0-1018/include/trace/events/fsi_master_ast_cf.h - /usr/src/linux-gcp-headers-5.4.0-1018/include/trace/events/fsi_master_gpio.h - /usr/src/linux-gcp-headers-5.4.0-1018/include/linux/i3c/master.h - /usr/src/linux-gcp-headers-5.4.0-1018/drivers/i3c/master - /usr/src/linux-gcp-headers-5.4.0-1018/drivers/w1/masters - /usr/src/linux-gcp-headers-5.4.0-1018/arch/m68k/include/asm/q40_master.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/spi/master.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/thrustmaster - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/snd/vmaster.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/w1/master - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/hid/thrustmaster.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/net/l3/master - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/dw/i3c/master.h - /usr/src/linux-headers-5.4.0-1019-gcp/include/config/cdns/i3c/master.h I didn't make the rules - It's up to you if you want to enforce them. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887214] Re: [18.04 LTS] Intel 8265 / 8275 [8086:24fd] Subsystem [8086:0010] Somehow wifi network latency is too high (1000~3000 ms)
Had tried with same 8265 chip running same firmware, can't really reproduce this. Is there any error message in dmesg log while network latency is raising? Do you use `ping -n` instead of `ping` only? Can you reproduce this with a separate wifi router? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887214 Title: [18.04 LTS] Intel 8265 / 8275 [8086:24fd] Subsystem [8086:0010] Somehow wifi network latency is too high (1000~3000 ms) Status in linux package in Ubuntu: Incomplete Bug description: [Problem description] Somehow wifi network latency is too high. (1000~3000 ms) DUT: - Product: Lenovo X1C6 - BIOS Information: Vendor: LENOVO Version: N23ET74W (1.49 ) Release Date: 06/03/2020 - Wifi information: Intel Wireless 8265 / 8275 driverversion=5.3.0-62-generic firmware=36.9f0a2d68.0 - OS: Ubuntu 18.04.4 LTS/Linux 5.3.0-62-generic/X86-64 [Test steps] 1. Boot up Ubuntu 18.04.4 LTS. 2. Open terminal. 3. To execute ping command, and target is in the local network. (For example: local gateway) 4. After few mins, I noticed that network latency will get worse. Sample output: 64 bytes from 192.168.1.1: icmp_seq=714 ttl=64 time=2.31 ms 64 bytes from 192.168.1.1: icmp_seq=715 ttl=64 time=1.61 ms 64 bytes from 192.168.1.1: icmp_seq=716 ttl=64 time=8.93 ms 64 bytes from 192.168.1.1: icmp_seq=717 ttl=64 time=59.0 ms 64 bytes from 192.168.1.1: icmp_seq=718 ttl=64 time=101 ms 64 bytes from 192.168.1.1: icmp_seq=719 ttl=64 time=155 ms 64 bytes from 192.168.1.1: icmp_seq=720 ttl=64 time=212 ms 64 bytes from 192.168.1.1: icmp_seq=721 ttl=64 time=347 ms 64 bytes from 192.168.1.1: icmp_seq=722 ttl=64 time=485 ms 64 bytes from 192.168.1.1: icmp_seq=723 ttl=64 time=663 ms 64 bytes from 192.168.1.1: icmp_seq=724 ttl=64 time=914 ms 64 bytes from 192.168.1.1: icmp_seq=725 ttl=64 time=1149 ms 64 bytes from 192.168.1.1: icmp_seq=726 ttl=64 time=1490 ms 64 bytes from 192.168.1.1: icmp_seq=727 ttl=64 time=1828 ms 64 bytes from 192.168.1.1: icmp_seq=728 ttl=64 time=2154 ms 64 bytes from 192.168.1.1: icmp_seq=729 ttl=64 time=2609 ms 64 bytes from 192.168.1.1: icmp_seq=730 ttl=64 time=2851 ms 64 bytes from 192.168.1.1: icmp_seq=731 ttl=64 time=2825 ms 64 bytes from 192.168.1.1: icmp_seq=732 ttl=64 time=2184 ms 64 bytes from 192.168.1.1: icmp_seq=733 ttl=64 time=2582 ms 64 bytes from 192.168.1.1: icmp_seq=734 ttl=64 time=1898 ms 64 bytes from 192.168.1.1: icmp_seq=735 ttl=64 time=1377 ms 5. Same machine when I switched to W10 then I didn't encounter this symptom. [Expected result] Wifi network latency should not over 2~3 ms at least. [Actual result] Wifi network latency is too high. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lawrence 2772 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-05-30 (772 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20KGS0FV00 Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-62-generic root=UUID=65f0f796-b6da-4d46-98a5-325713eee95b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 5.3.0-62.56~18.04.1-generic 5.3.18 RelatedPackageVersions: linux-restricted-modules-5.3.0-62-generic N/A linux-backports-modules-5.3.0-62-generic N/A linux-firmware1.173.18 Tags: bionic Uname: Linux 5.3.0-62-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: 06/03/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET74W (1.49 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KGS0FV00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET74W(1.49):bd06/03/2020:svnLENOVO:pn20KGS0FV00:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KGS0FV00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KGS0FV00 dmi.product.sku: LENOVO_MT_20KG_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887124] Re: [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq
A patched kernel (that I created during the SRU preparation and test compile) is available here: https://people.canonical.com/~fheimes/lp1887124/ for further testing. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887124 Title: [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: So, after this is now all upstream in mainline and I found some time to test this properly on Ubuntu, here is the backport request. Some time ago we noticed - Fedor Loshakov did - that our DIV and DIX support in zfcp broke at some point (by "broke" I mean, the kernel will unconditionally crash if one activates either DIF, or DIX, and attaches *any* LU). I tracked that down to a commit made for v5.4 (737eb78e82d5), but we didn't notice it back than, because our CI doesn't currently run with either DIV, nor DIX enabled (time allowing this is something we want to improve so we catch stuff like this earlier). It also turned out that the commit in v5.4 was not really the root-cause, and was only making the problem visible more easy. In short: zfcp used to allocate/add the shost object for a HBA before knowing all the HBA's capabilities, and we later patched the shost object to make more of the capabilities known - including the protection capabilities. Back when we still had the old blk queue, this worked fine; after scsi_mod switched to blk-mq and because requests are now all allocated during allocation time of the blk-mq tag-set, this doesn't work anymore. Changes we make later to the protection capabilities don't get reflected into the tag-set's requests, and they are missing parts. When we then try to send I/O, scsi_mod tries to access the protection payload data, who are not there, and it crashes the kernel. So instead, I now want to allocate/add the shost object for a HBA after we know all of its base capabilities. This solves the bug. Because we had this modus operandi for a very long time, I had to touch many places that assume the shost object was already allocated - explaining the rather big patchset for a 'fix'. And because this also involves/depends on code that went upstream in v5.5 and v5.7 we now have a rather complicated situation for backports of the fix. Nothing "just" applies. The easiest and most straight forward way to deal with that is to basically backport most everything that is involved - which is most of the stuff that went upstream since v5.5 for our driver. I complied a list of the upstream commits that would have to be picked in order to be merge-conflict free: 92953c6e0aa77 scsi: zfcp: signal incomplete or error for sync exchange config/port data 7e418833e6894 scsi: zfcp: diagnostics buffer caching and use for exchange port data 088210233e6fc scsi: zfcp: add diagnostics buffer for exchange config data a10a61e807b0a scsi: zfcp: support retrieval of SFP Data via Exchange Port Data 6028f7c4cd87c scsi: zfcp: introduce sysfs interface for diagnostics of local SFP transceiver 8155eb0785279 scsi: zfcp: implicitly refresh port-data diagnostics when reading sysfs 5a2876f0d1ef2 scsi: zfcp: introduce sysfs interface to read the local B2B-Credit 8a72db70b5ca3 scsi: zfcp: implicitly refresh config-data diagnostics when reading sysfs 48910f8c35cfd scsi: zfcp: move maximum age of diagnostic buffers into a per-adapter variable e76acc5194264 scsi: zfcp: proper indentation to reduce confusion in zfcp_erp_required_act a3fd4bfe85fbb scsi: zfcp: fix wrong data and display format of SFP+ temperature e05a10a055098 scsi: zfcp: expose fabric name as common fc_host sysfs attribute 538c6e910baea scsi: zfcp: wire previously driver-specific sysfs attributes also to fc_host 7e0e4e0958ef7 scsi: zfcp: fix fc_host attributes that should be unknown on local link down 185f2d2d595c2 scsi: zfcp: auto variables for dereferenced structs in open port handler a17c78460093a scsi: zfcp: report FC Endpoint Security in sysfs f0d26ae847489 scsi: zfcp: log FC Endpoint Security of connections 616da39e0060f scsi: zfcp: trace FC Endpoint Security of FCP devices and connections e53d92856e9f1 scsi: zfcp: enhance handling of FC Endpoint Security errors 42cabdaf103be scsi: zfcp: log FC Endpoint Security errors cec9cbac5244b scsi: zfcp: use fallthrough; 978857c7e367d scsi: zfcp: Move shost modification after QDIO (re-)open into fenced function bd1684817d7d8 scsi: zfcp: Move shost updates during xconfig data handling into fenced function 52e61fde5ec95 scsi: zfcp: Move fc_host updates during xport data handling into fenced function 990486f3a8508 scsi: zfcp: Fence fc_host
[Kernel-packages] [Bug 1887124] Re: [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq
** Description changed: So, after this is now all upstream in mainline and I found some time to test this properly on Ubuntu, here is the backport request. - Some time ago we noticed - Fedor Loshakov did - that our DIV and DIX support in - zfcp broke at some point (by "broke" I mean, the kernel will unconditionally - crash if one activates either DIF, or DIX, and attaches *any* LU). I tracked + Some time ago we noticed - Fedor Loshakov did - that our DIF and DIX support in + zfcp broke at some point (by "broke" I mean, the kernel will unconditionally + crash if one activates either DIF, or DIX, and attaches *any* LU). I tracked that down to a commit made for v5.4 (737eb78e82d5), but we didn't notice it - back than, because our CI doesn't currently run with either DIV, nor DIX + back than, because our CI doesn't currently run with either DIF, nor DIX enabled (time allowing this is something we want to improve so we catch stuff like this earlier). It also turned out that the commit in v5.4 was not really the root-cause, and was only making the problem visible more easy. In short: zfcp used to allocate/add the shost object for a HBA before knowing all the HBA's capabilities, and we later patched the shost object to make more of the capabilities known - including the protection capabilities. Back when we still had the old blk queue, this worked fine; after scsi_mod switched to blk-mq and because requests are now all allocated during allocation time of the blk-mq tag-set, this doesn't work anymore. Changes we make later to the protection capabilities don't get reflected into the tag-set's requests, and they are missing parts. When we then try to send I/O, scsi_mod tries to access the protection payload data, who are not there, and it crashes the kernel. So instead, I now want to allocate/add the shost object for a HBA after we know all of its base capabilities. This solves the bug. Because we had this modus operandi for a very long time, I had to touch many places that assume the shost object was already allocated - explaining the rather big patchset for a 'fix'. And because this also involves/depends on code that went upstream in v5.5 and v5.7 we now have a rather complicated situation for backports of the fix. Nothing "just" applies. The easiest and most straight forward way to deal with that is to basically backport most everything that is involved - which is most of the stuff that went upstream since v5.5 for our driver. I complied a list of the upstream commits that would have to be picked in order to be merge-conflict free: - 92953c6e0aa77 scsi: zfcp: signal incomplete or error for sync exchange config/port data - 7e418833e6894 scsi: zfcp: diagnostics buffer caching and use for exchange port data - 088210233e6fc scsi: zfcp: add diagnostics buffer for exchange config data - a10a61e807b0a scsi: zfcp: support retrieval of SFP Data via Exchange Port Data - 6028f7c4cd87c scsi: zfcp: introduce sysfs interface for diagnostics of local SFP transceiver - 8155eb0785279 scsi: zfcp: implicitly refresh port-data diagnostics when reading sysfs - 5a2876f0d1ef2 scsi: zfcp: introduce sysfs interface to read the local B2B-Credit - 8a72db70b5ca3 scsi: zfcp: implicitly refresh config-data diagnostics when reading sysfs - 48910f8c35cfd scsi: zfcp: move maximum age of diagnostic buffers into a per-adapter variable - e76acc5194264 scsi: zfcp: proper indentation to reduce confusion in zfcp_erp_required_act - a3fd4bfe85fbb scsi: zfcp: fix wrong data and display format of SFP+ temperature - e05a10a055098 scsi: zfcp: expose fabric name as common fc_host sysfs attribute - 538c6e910baea scsi: zfcp: wire previously driver-specific sysfs attributes also to fc_host - 7e0e4e0958ef7 scsi: zfcp: fix fc_host attributes that should be unknown on local link down - 185f2d2d595c2 scsi: zfcp: auto variables for dereferenced structs in open port handler - a17c78460093a scsi: zfcp: report FC Endpoint Security in sysfs - f0d26ae847489 scsi: zfcp: log FC Endpoint Security of connections - 616da39e0060f scsi: zfcp: trace FC Endpoint Security of FCP devices and connections - e53d92856e9f1 scsi: zfcp: enhance handling of FC Endpoint Security errors - 42cabdaf103be scsi: zfcp: log FC Endpoint Security errors - cec9cbac5244b scsi: zfcp: use fallthrough; - 978857c7e367d scsi: zfcp: Move shost modification after QDIO (re-)open into fenced function - bd1684817d7d8 scsi: zfcp: Move shost updates during xconfig data handling into fenced function - 52e61fde5ec95 scsi: zfcp: Move fc_host updates during xport data handling into fenced function - 990486f3a8508 scsi: zfcp: Fence fc_host updates during link-down handling - ac007adc4d2d9 scsi: zfcp: Move p-t-p port allocation to after xport data - 971f2abb4ca40 scsi: zfcp: Fence adapter status propagation for
[Kernel-packages] [Bug 1887124] Re: [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq
Changed bug title from: "[UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq" to "DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally" Not because the old title is wrong, just because to have a better title for the SRU request, that references this bug. ** Summary changed: - [UBUNTU 20.04] kernel panic with zfcp.dif=1 and zfcp.dix=1 - crash in scsi_queue_rq + [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887124 Title: [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: New Bug description: So, after this is now all upstream in mainline and I found some time to test this properly on Ubuntu, here is the backport request. Some time ago we noticed - Fedor Loshakov did - that our DIF and DIX support in zfcp broke at some point (by "broke" I mean, the kernel will unconditionally crash if one activates either DIF, or DIX, and attaches *any* LU). I tracked that down to a commit made for v5.4 (737eb78e82d5), but we didn't notice it back than, because our CI doesn't currently run with either DIF, nor DIX enabled (time allowing this is something we want to improve so we catch stuff like this earlier). It also turned out that the commit in v5.4 was not really the root-cause, and was only making the problem visible more easy. In short: zfcp used to allocate/add the shost object for a HBA before knowing all the HBA's capabilities, and we later patched the shost object to make more of the capabilities known - including the protection capabilities. Back when we still had the old blk queue, this worked fine; after scsi_mod switched to blk-mq and because requests are now all allocated during allocation time of the blk-mq tag-set, this doesn't work anymore. Changes we make later to the protection capabilities don't get reflected into the tag-set's requests, and they are missing parts. When we then try to send I/O, scsi_mod tries to access the protection payload data, who are not there, and it crashes the kernel. So instead, I now want to allocate/add the shost object for a HBA after we know all of its base capabilities. This solves the bug. Because we had this modus operandi for a very long time, I had to touch many places that assume the shost object was already allocated - explaining the rather big patchset for a 'fix'. And because this also involves/depends on code that went upstream in v5.5 and v5.7 we now have a rather complicated situation for backports of the fix. Nothing "just" applies. The easiest and most straight forward way to deal with that is to basically backport most everything that is involved - which is most of the stuff that went upstream since v5.5 for our driver. I complied a list of the upstream commits that would have to be picked in order to be merge-conflict free: 92953c6e0aa77 scsi: zfcp: signal incomplete or error for sync exchange config/port data 7e418833e6894 scsi: zfcp: diagnostics buffer caching and use for exchange port data 088210233e6fc scsi: zfcp: add diagnostics buffer for exchange config data a10a61e807b0a scsi: zfcp: support retrieval of SFP Data via Exchange Port Data 6028f7c4cd87c scsi: zfcp: introduce sysfs interface for diagnostics of local SFP transceiver 8155eb0785279 scsi: zfcp: implicitly refresh port-data diagnostics when reading sysfs 5a2876f0d1ef2 scsi: zfcp: introduce sysfs interface to read the local B2B-Credit 8a72db70b5ca3 scsi: zfcp: implicitly refresh config-data diagnostics when reading sysfs 48910f8c35cfd scsi: zfcp: move maximum age of diagnostic buffers into a per-adapter variable e76acc5194264 scsi: zfcp: proper indentation to reduce confusion in zfcp_erp_required_act a3fd4bfe85fbb scsi: zfcp: fix wrong data and display format of SFP+ temperature e05a10a055098 scsi: zfcp: expose fabric name as common fc_host sysfs attribute 538c6e910baea scsi: zfcp: wire previously driver-specific sysfs attributes also to fc_host 7e0e4e0958ef7 scsi: zfcp: fix fc_host attributes that should be unknown on local link down 185f2d2d595c2 scsi: zfcp: auto variables for dereferenced structs in open port handler a17c78460093a scsi: zfcp: report FC Endpoint Security in sysfs f0d26ae847489 scsi: zfcp: log FC Endpoint Security of connections 616da39e0060f scsi: zfcp: trace FC Endpoint Security of FCP devices and connections e53d92856e9f1 scsi: zfcp: enhance handling of FC Endpoint Security errors 42cabdaf103be scsi: zfcp: log FC Endpoint Security errors cec9cbac5244b
[Kernel-packages] [Bug 1875236] Re: Different kernel gives different RAM results
Good one: [0.00] BIOS-e820: [mem 0xff60-0x] reserved [0.00] BIOS-e820: [mem 0x0001-0x0002827f] usable Bad one: [0.00] BIOS-e820: [mem 0xff60-0x0002827f] reserved Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875236 Title: Different kernel gives different RAM results Status in linux package in Ubuntu: Incomplete 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 1884981] Re: The touchpad soesn't work at all
I am currently testing Mint 20 (based on 20.04) on an IdeaPad 5 14ARE05 with mainline 5.7.8-050708-generic and have the same error. I have attached my acpidump if it is helpful. ** Attachment added: "acpidump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+attachment/5392609/+files/acpidump -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) 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: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1592597] Re: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: linux (Ubuntu Trusty) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1592597 Title: 3.13.0-88-generic:amd64 fails to boot on Dell PowerEdge R630 Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Triaged Bug description: Following recent update to 3.13.0-88, R630 on Trusty panics on boot. Recovery boot just hangs. 3.13.0-87 was able to be booted normally once, then kernel panics on subsequent attempts. Booting is successful with the previously running kernel, 3.13.0-61. will upload an sosreport. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1592597/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881319] Re: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel)
@tim-richardson and @olepet there is a 14ARE05 bug discussion at #1884981 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881319 Title: Touchpad not recognized Lenovo IdeaPad 5 15ARE05 (probably falsely as touch panel) Status in linux package in Ubuntu: Confirmed Bug description: Touchpad isn't reacting at all ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: andreas1223 F pulseaudio /dev/snd/controlC0: andreas1223 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Fri May 29 18:05:01 2020 InstallationDate: Installed on 2020-05-29 (0 days ago) InstallationMedia: Ubuntu-Budgie 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YQ ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=4197e5c6-f903-46c3-bc16-3013c5650810 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: E7CN24WW 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: IdeaPad 5 15ARE05 dmi.modalias: dmi:bvnLENOVO:bvrE7CN24WW:bd03/25/2020:svnLENOVO:pn81YQ:pvrIdeaPad515ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad515ARE05: dmi.product.family: IdeaPad 5 15ARE05 dmi.product.name: 81YQ dmi.product.sku: LENOVO_MT_81YQ_BU_idea_FM_IdeaPad 5 15ARE05 dmi.product.version: IdeaPad 5 15ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881319/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852432] Re: i40e: Setting VF MAC address causes General Protection Fault
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu Focal) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852432 Title: i40e: Setting VF MAC address causes General Protection Fault Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: [Impact] * Creating SR-IOV enabled VMs in Openstack can sometimes trigger the GPF and leave system unusable [Test Case] * Continuously spin up VFs and set MAC address with e.g. ifconfig [Fix] * The fix updates the VSI pointer passed down to i40e_set_vf_mac function() if the adapter is still in reset, preventing the GPF. [Regression Potential] * Regression potential should be low, as we're now updating the VSI using the ID stored in the VF pointer * Regressions could arise from issues in VF creation or reset, as that would corrupt the new VSI pointer * Patch was validated and tested in a production environment To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852432/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834322] Re: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot
** Changed in: linux (Ubuntu) Status: In Progress => 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/1834322 Title: Losing port aggregate with 802.3ad port-channel/bonding aggregation on reboot Status in linux package in Ubuntu: Fix Released 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: Fix Released Bug description: We are losing port channel aggregation on reboot. After the reboot, /var/log/syslog contains the entries: [ 250.790758] bond2: An illegal loopback occurred on adapter (enp24s0f1np1) Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports [ 282.029426] bond2: An illegal loopback occurred on adapter (enp24s0f1np1) Check the configuration to verify that all adapters are connected to 802.3ad compliant switch ports Aggregator IDs of the slave interfaces are different: ubuntu@node-6:~$ cat /proc/net/bonding/bond2 Ethernet Channel Bonding Driver: v3.7.1 (April 27, 2011) Bonding Mode: IEEE 802.3ad Dynamic link aggregation Transmit Hash Policy: layer3+4 (1) MII Status: up MII Polling Interval (ms): 100 Up Delay (ms): 0 Down Delay (ms): 0 802.3ad info LACP rate: fast Min links: 0 Aggregator selection policy (ad_select): stable Slave Interface: enp24s0f1np1 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: b0:26:28:48:9f:51 Slave queue ID: 0 Aggregator ID: 1 Actor Churn State: none Partner Churn State: none Actor Churned Count: 0 Partner Churned Count: 0 Slave Interface: enp24s0f0np0 MII Status: up Speed: 1 Mbps Duplex: full Link Failure Count: 0 Permanent HW addr: b0:26:28:48:9f:50 Slave queue ID: 0 Aggregator ID: 2 Actor Churn State: churned Partner Churn State: churned Actor Churned Count: 1 Partner Churned Count: 1 The mismatch in "Aggregator ID" on the port is a symptom of the issue. If we do 'ip link set dev bond2 down' and 'ip link set dev bond2 up', the port with the mismatched ID appears to renegotiate with the port- channel and becomes aggregated. The other way to workaround this issue is to put bond ports down and bring up port enp24s0f0np0 first and port enp24s0f1np1 second. When I change the order of bringing the ports up (first enp24s0f1np1, and second enp24s0f0np0), the issue is still there. When the issue occurs, a port on the switch, corresponding to interface enp24s0f0np0 is in Suspended state. After applying the workaround the port is no longer in Suspended state and Aggregator IDs in /proc/net/bonding/bond2 are equal. I installed 5.0.0 kernel, the issue is still there. Operating System: Ubuntu 18.04.2 LTS (GNU/Linux 4.15.0-52-generic x86_64) ubuntu@node-6:~$ uname -a Linux node-6 4.15.0-52-generic #56-Ubuntu SMP Tue Jun 4 22:49:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ubuntu@node-6:~$ sudo lspci -vnvn https://pastebin.ubuntu.com/p/Dy2CKDbySC/ Hardware: Dell PowerEdge R740xd BIOS version: 2.1.7 sosreport: https://drive.google.com/open?id=1-eN7cZJIeu- AQBEU7Gw8a_AJTuq0AOZO ubuntu@node-6:~$ lspci | grep Ethernet | grep 10G https://pastebin.ubuntu.com/p/sqCx79vZWM/ ubuntu@node-6:~$ lspci -n | grep 18:00 18:00.0 0200: 14e4:16d8 (rev 01) 18:00.1 0200: 14e4:16d8 (rev 01) ubuntu@node-6:~$ modinfo bnx2x https://pastebin.ubuntu.com/p/pkmzsFjK8M/ ubuntu@node-6:~$ ip -o l https://pastebin.ubuntu.com/p/QpW7TjnT2v/ ubuntu@node-6:~$ ip -o a https://pastebin.ubuntu.com/p/MczKtrnmDR/ ubuntu@node-6:~$ cat /etc/netplan/98-juju.yaml https://pastebin.ubuntu.com/p/9cZpPc7C6P/ ubuntu@node-6:~$ sudo lshw -c network https://pastebin.ubuntu.com/p/gmfgZptzDT/ --- ProblemType: Bug AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jun 26 10:21 seq crw-rw 1 root audio 116, 33 Jun 26 10:21 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.6 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 18.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 1604:10c0 Tascam Bus 001 Device 003: ID 1604:10c0 Tascam Bus 001 Device 002: ID 1604:10c0 Tascam Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. PowerEdge R740xd Package: linux (not installed) PciMultimedia:
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help :
[Kernel-packages] [Bug 1807393] Re: nvme - Polling on timeout
** Changed in: linux (Ubuntu)
Status: In Progress => 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/1807393
Title:
nvme - Polling on timeout
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
[Impact]
* NVMe controllers potentially could miss to send an interrupt, specially
due to bugs in virtual devices(which are common those days - qemu has its
own NVMe virtual device, so does AWS). This would be a difficult to
debug situation, because NVMe driver only reports the request timeout,
not the reason.
* The upstream patch proposed to SRU here here, 7776db1ccc12
("NVMe/pci: Poll CQ on timeout") was designed to provide more information
in these cases, by pro-actively polling the CQEs on request timeouts, to
check if the specific request was completed and some issue (probably a
missed interrupt) prevented the driver to notice, or if the request really
wasn't completed, which indicates more severe issues.
* Although quite useful for debugging, this patch could help to mitigate
issues in cloud environments like AWS, in case we may have jitter in
request completion and the i/o timeout was set to low values, or even
in case of atypical bugs in the virtual NVMe controller. With this patch,
if polling succeeds the NVMe driver will continue working instead of
trying a reset controller procedure, which may lead to fails in the
rootfs - refer to https://launchpad.net/bugs/1788035.
[Test Case]
* It's a bit tricky to artificially create a situation of missed interrupt;
one idea was to implement a small hack in the NVMe qemu virtual device
that given a trigger in guest kernel, will induce the virtual device to
skip an interrupt. The hack patch is present in comment #1 below.
* To trigger such hack from guest kernel, all is needed is to issue a
raw admin command from nvme-cli: "nvme admin-passthru -o 0xff /dev/nvme0"
After that, just perform some I/Os to see one of them aborting - one could
use dd for this goal, like "dd if=/dev/zero of=/dev/nvme0n1 count=5".
[Regression Potential]
* There are no clear risks in adding such polling mechanism to the NVMe
driver; one bad thing that was neverreported but could happen with this patch
is the device could be in a bad state IRQ-wise that a reset would fix, but
the patch could cause all requests to be completed via polling, which
prevents the adapter reset. This is however a very hypothetical situation,
which would also happen in the mainline kernel (since it has the patch).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1807393/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1815033] Re: qlcnic: Firmware aborts/hangs in QLogic NIC
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1815033
Title:
qlcnic: Firmware aborts/hangs in QLogic NIC
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Released
Bug description:
[Impact]
* In multi-queue configurations for qlcnic driver, there is a corner case
in which TX queue zero is used at same time for regular data transmission
by one CPU while another uses the same queue descriptor for MAC
configuration.
* When such "race" indeed happens, it could lead to TX queue zero corruption,
triggering as net result firmware aborts/hangs out of nowhere. The following
kernel log messages were collected during the corruption event:
qlcnic :01:00.0: Pause control frames disabled on all ports
qlcnic :01:00.0: firmware hang detected
qlcnic :01:00.0: Dumping hw/fw registers
PEG_HALT_STATUS1: 0x40001502, PEG_HALT_STATUS2: 0x3de7a0,
PEG_NET_0_PC: 0x6d268, PEG_NET_1_PC: 0x6d2ac,
PEG_NET_2_PC: 0x149, PEG_NET_3_PC: 0x6e105,
PEG_NET_4_PC: 0x1e00b
[...]
qlcnic :01:00.0: Detected state change from DEV_NEED_RESET, skipping
ack check
* The following device is known to suffer from the issue (lspci output),
although a whole class of devices (named 82XX series from the vendor) are
susceptible to this:
01:00.0 Ethernet controller [0200]: QLogic Corp. cLOM8214 1/10GbE
Controller [1077:8020]
* The fix is the following patch, present in mainline kernel as well as
in supported stable branches:
c333fa0c4f22 ("qlcnic: fix Tx descriptor corruption on 82xx devices").
Link for the patch in Linus tree: http://git.kernel.org/linus/c333fa0c4f22
[Test Case]
* Unfortunately this is not easy to reproduce; we have a user report of
the issue with a pretty reliable reproducer - user is running a NFS
workload on top of the above PCI adapter. His problem goes away with
the patch proposed here to SRU. His problem happens in both kernels 4.4
and 4.15, and the patch fixes it for both of them.
(Notice this is a Bionic-only SRU, since Ubuntu 4.4 kernel got the patch
from Greg's supported stable branch).
[Regression Potential]
* The patch scope is restricted to a single driver, and the code itself
is self-contained - basically a restriction to specific tx_ring when
setting filters. There is potential for regressions in this path for
the driver which could cause different firmware issues for example,
but the user testing exhibited great reliability - without the patch
issue happens after ~6h of machine boot. With the patch the machine ran
for more than 8 days without issues.
* Also the patch is present in mainline kernel as well as supported
stable branches, and is already present in Ubuntu 4.4 kernel.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1815033/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814095] Re: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Nivedita Singhvi (niveditasinghvi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814095 Title: bnxt_en_po: TX timed out triggering Netdev Watchdog Timer Status in linux package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released Bug description: [Impact] The bnxt_en_bpo driver experienced tx timeouts causing the system to experience network stalls and fail to send data and heartbeat packets. The following 25Gb Broadcom NIC error was seen on Xenial running the 4.4.0-141-generic kernel on an amd64 host seeing moderate-heavy network traffic (just once): * The bnxt_en_po driver froze on a "TX timed out" error and triggered the Netdev Watchdog timer under load. * From kernel log: "NETDEV WATCHDOG: eno2d1 (bnxt_en_bpo): transmit queue 0 timed out" See attached kern.log excerpt file for full excerpt of error log. * Release = Xenial Kernel = 4.4.0-141-generic #167 eno2d1 = Product Name: Broadcom Adv. Dual 25Gb Ethernet * This caused the driver to reset in order to recover: "bnxt_en_bpo :19:00.1 eno2d1: TX timeout detected, starting reset task!" driver: bnxt_en_bpo version: 1.8.1 source: ubuntu/bnxt/bnxt.c: bnxt_tx_timeout() * The loss of connectivity and softirq stall caused other failures on the system. * The bnxt_en_po driver is the imported Broadcom driver pulled in to support newer Broadcom HW (specific boards) while the bnx_en module continues to support the older HW. The current Linux upstream driver does not compile easily with the 4.4 kernel (too many changes). * This upstream and bnxt_en driver fix is a likely solution: "bnxt_en: Fix TX timeout during netpoll" commit: 73f21c653f930f438d53eed29b5e4c65c8a0f906 This fix has not been applied to the bnxt_en_po driver version, but review of the code indicates that it is susceptible to the bug, and the fix would be reasonable. [Test Case] * Unfortunately, this is not easy to reproduce. Also, it is only seen on 4.4 kernels with newer Broadcom NICs supported by the bnxt_en_bpo driver. [Regression Potential] * The patch is restricted to the bpo driver, with very constrained scope - just the newest Broadcom NICs being used by the Xenial 4.4 kernel (as opposed to the hwe 4.15 etc. kernels, which would have the in-tree fixed driver). * The patch is very small and backport is fairly minimal and simple. * The fix has been running on the in-tree driver in upstream mainline as well as the Ubuntu Linux in-tree driver, although the Broadcom driver has a lot of lower level code that is different, this piece is still the same. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814095/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885033] Re: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04)
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885033 Title: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04) Status in linux package in Ubuntu: Incomplete Bug description: The touchpad switch, Fn-F6, does not work for me. It does work on Windows 10 (dual boot) The touchpad works well, but I can only set the option in System Conguration. See launchpad answer : https://answers.launchpad.net/ubuntu/+question/691511 Kubuntu 20.04 Lenovo IdeaPad L340-15IRH - Type 81LK --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yann 1350 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-20 (125 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81LK NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=0ac30ea3-dc16-4323-a1a3-acea99fa90b5 ro quiet splash resume=/dev/nvme0n1p6 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-14 (41 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN29WW 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: IdeaPad L340-15IRH Gaming dmi.modalias: dmi:bvnLENOVO:bvrBGCN29WW:bd02/10/2020:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887213] Re: Touchpad stopped working after upgrade: 18.04 => 20.04
P: /devices/platform/i8042/serio1 L: 0 E: DEVPATH=/devices/platform/i8042/serio1 E: SUBSYSTEM=serio E: SERIO_TYPE=01 E: SERIO_PROTO=00 E: SERIO_ID=00 E: SERIO_EXTRA=00 E: MODALIAS=serio:ty01pr00id00ex00 E: SERIO_FIRMWARE_ID=PNP: LEN200e PNP0f13 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887213 Title: Touchpad stopped working after upgrade: 18.04 => 20.04 Status in linux package in Ubuntu: Incomplete Bug description: > Laptop model directly from the sticker of the computer. Lenovo T450 ThinkPad > Manufacturer of the Touchpad. > When the symptom first appeared. Right after 18.04 => 20.04 upgrade. Touchpad never worked after upgrade. Nor movements, neither clicks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyga 2740 F pulseaudio /dev/snd/controlC0: cyga 2740 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 13:36:53 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d66c9dac-9065-401a-8f9a-3f208be7d2e6 InstallationDate: Installed on 2017-06-07 (1129 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20BV0005US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 acpi=force irqpoll quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-27 (13 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV0005US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BV0005US:pvrThinkPadT450:rvnLENOVO:rn20BV0005US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV0005US dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1869948] Re: Multiple Kexec in AWS Nitro instances fail
** Changed in: linux (Ubuntu)
Status: Fix Committed => Fix Released
** No longer affects: linux (Ubuntu Disco)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1869948
Title:
Multiple Kexec in AWS Nitro instances fail
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux source package in Focal:
Fix Released
Bug description:
[Impact]
* Currently, users cannot perform multiple kernel kexec loads on AWS Nitro
instances (KVM-based); after the 2nd or 3rd kexec, an initrd corruption is
observed, with the following signature:
Initramfs unpacking failed: junk within compressed archive
[...]
Kernel panic - not syncing: No working init found.
Try passing init= option to kernel. See Linux
Documentation/admin-guide/init.rst for guidance.
CPU: 0 PID: 1 Comm: swapper/0 Not tainted 5.5.0-rc7-gpiccoli+ #26 Hardware
name: Amazon EC2 t3.large/, BIOS 1.0 10/16/2017
Call Trace:
dump_stack+0x6d/0x9a
? csum_partial_copy_generic+0x150/0x170
panic+0x101/0x2e3
? do_execve+0x25/0x30
? rest_init+0xb0/0xb0
kernel_init+0xfb/0x100
ret_from_fork+0x35/0x40
* After investigation (see comment 2), it was noticed the Amazon ena
network driver doesn't provide a shutdown() handler, hence it could be
performing a DMA transaction to a previous valid address during boot,
which would then corrupt kernel memory. The following patch was
proposed and fixed the issue, allowing 1000 kexecs to be executed
successfully with no issues observed: 428c491332bc("net: ena: Add PCI
shutdown handler to allow safe kexec") [
git.kernel.org/linus/428c491332bc ].
* Hence, we are hereby requesting SRU for this patch. It was tested in
all supported series (4.4, 4.15 and 5.3) in Amazon Nitro instances
with success, and reviewed/acked by ena driver team and a kexec
developer from other distro. Worth mentioning that we proposed an
upstream multi-vendor discussion about this issue:
marc.info/?l=kexec=158299605013194
[Test case]
* The basic test procedure is about performing multiple kexecs
sequentially; AWS does not provide a full console, so in case of
failures one could check the instance screenshot or use pstore/ramoops
in order to collect dmesg after a crash in a preserved memory area.
The commands used to perform kexec are:
kexec -l --initrd --reuse-cmdline
systemctl kexec
Alternatively, one could user "--append=" instead of "--reuse-cmdline"
if a change in kexec command-line is desired; also, to execute the
kexec-loaded kernel both "kexec -e" and "systemctl kexec" are equally
valid.
* On comment 3 we proposed a script/approach to auto-test kexecs, used
here to perform 1000 kexecs with the proposed patch.
[Regression Potential]
* Although the patch proposed here introduce a PCI handler, it kept
the remove handler identical and based shutdown strongly on
ena_remove(), changing just netdev handling following other upstream
drivers. It was extensively tested and presented no issue. Also, it's
self-contained and affect only one driver, so any other cloud
providers or non-cloud environment wouldn't be even affected by the
patch.
* In case of a potential regression, it could manifest as a delay or
issue on reboot/shutdown path, only if ena driver is in use.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869948/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-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
** Changed in: nvidia-graphics-drivers-340 (Ubuntu Focal) Status: New => Won't Fix -- 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: Invalid Status in mutter source package in Focal: In Progress 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: 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. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 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=7 SourcePackage: 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 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/oem-priority/+bug/1874567/+subscriptions
[Kernel-packages] [Bug 1879333] Re: [nvidia] Black screen on loading latest system update
Still did it this morning after running updates and the reset. -- 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/1879333 Title: [nvidia] Black screen on loading latest system update Status in nvidia-graphics-drivers-440 package in Ubuntu: New Status in xorg-server package in Ubuntu: New Bug description: This bug has been around since 16.04 and still occurs with 18.04 when using nvidia drivers. When update required for the OS the black screen situation happens after the required reboot. Only way to regain desktop is to login via ssh terminal and run the commands listed here: https://askubuntu.com/questions/1129516/black-screen-at-boot-after- nvidia-driver-installation-on-ubuntu-18-04-2-lts sudo apt-get update sudo apt-get upgrade sudo apt-get purge nvidia* sudo apt autoremove sudo apt-get install dkms build-essential linux-headers-$(uname -r) echo "# Disable the default Nouveau kernel driver" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf echo "# -" | sudo tee -a /etc/modprobe.d/blacklist-nouveau.conf echo "blacklist nouveau" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "blacklist lbm-nouveau" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d /blacklist-nouveau.conf echo "alias nouveau off" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf echo "alias lbm-nouveau off" | sudo tee -a /etc/modprobe.d/blacklist- nouveau.conf cat /etc/modprobe.d/blacklist-nouveau.conf echo "options nouveau modeset=0" | sudo tee -a /etc/modprobe.d /nouveau-kms.conf cat /etc/modprobe.d/nouveau-kms.conf sudo update-initramfs -u sudo service lightdm stop sudo apt-get install nvidia-driver-440 lsmod | grep nvidia sudo lshw -c video | grep 'configuration' sudo reboot ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-101.102-generic 4.15.18 Uname: Linux 4.15.0-101-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.14 Architecture: amd64 BootLog: CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' Date: Mon May 18 08:44:05 2020 DistUpgraded: 2019-12-17 11:35:32,743 DEBUG icon theme changed, re-reading DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: bbswitch, 0.8, 4.15.0-101-generic, x86_64: installedError! Could not locate dkms.conf file. File: does not exist. bbswitch, 0.8, 4.15.0-99-generic, x86_64: installed ExtraDebuggingInterest: Yes GraphicsCard: Subsystem: ASRock Incorporation Atom/Celeron/Pentium Processor x5-E8000/J3xxx/N3xxx Integrated Graphics Controller [1849:22b1] NVIDIA Corporation GK208 [GeForce GT 630 Rev. 2] [10de:1284] (rev a1) (prog-if 00 [VGA controller]) Subsystem: ASUSTeK Computer Inc. GK208 [GeForce GT 630 Rev. 2] [1043:846a] InstallationDate: Installed on 2019-09-26 (234 days ago) InstallationMedia: Ubuntu 16.04.6 LTS "Xenial Xerus" - Release amd64 (20190227) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-101-generic root=UUID=89ea4739-64a1-4200-9626-c597e9d5a485 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to bionic on 2019-12-17 (152 days ago) dmi.bios.date: 02/27/2018 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.50 dmi.board.name: N3150M dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.50:bd02/27/2018:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnN3150M:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. version.compiz: compiz 1:0.9.13.1+18.04.20180302-0ubuntu1 version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.3 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.3 version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.10.5-1ubuntu1 version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2
[Kernel-packages] [Bug 1795659] Re: kernel panic using CIFS share in smb2_push_mandatory_locks()
** Changed in: linux (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1795659
Title:
kernel panic using CIFS share in smb2_push_mandatory_locks()
Status in linux package in Ubuntu:
Fix Released
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Invalid
Status in linux-azure source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-azure source package in Bionic:
Invalid
Status in linux source package in Cosmic:
Won't Fix
Status in linux-azure source package in Cosmic:
Invalid
Status in linux source package in Disco:
Fix Released
Status in linux-azure source package in Disco:
Invalid
Bug description:
NOTICE: The new patch merge is being worked on
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856949 - if you
face this issue, please report there!
[Impact]
* We got reports of a kernel crash in cifs module with the following
signature:
BUG: unable to handle kernel NULL pointer dereference at 0038
IP: smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
PGD 0 P4D 0
RIP: 0010:smb2_push_mandatory_locks+0x10e/0x3b0 [cifs]
Call Trace:
cifs_oplock_break+0x12f/0x3d0 [cifs]
process_one_work+0x14d/0x410
worker_thread+0x4b/0x460
kthread+0x105/0x140
[...]
* Low-level analysis (decodecode script output and the objdump of the
function) revealed that we are crashing in a NULL ptr dereference when
trying to access "cfile->tlink"; below, a snippet of the objdump at
function smb2_push_mandatory_locks():
[...]
mov0x10(%r14),%r15 # %r15 = cifsFileInfo *cfile
mov0x18(%r14),%rbx # %rbx = cifsLockInfo *li = (fdlocks->locks)
lea0x18(%r14),%r12
mov0x90(%r15),%rax # %rax = struct tcon_link *tlink (cfile->tlink)
cmp%r12,%rbx
mov0x38(%rax),%rax # <--- TRAP [trying to get cifs_tcon *tl_tcon]
[...]
* After discussing the issue with CIFS maintainers (Steve French and
Pavel Shilovsky) they suggested commit b98749cac4a6 ("CIFS: keep
FileInfo handle live during oplock break")
[http://git.kernel.org/linus/b98749cac4a6] as a fix for multiple
reports of this kind of crash.
* The fix was sent to stable kernels and is present in Ubuntu kernels
5.0 and newer. We are requesting the SRU for this patch here in order
to fix the crashes, after reports of successful testing with the patch
(see below section) and since the patch is restricted to the cifs
module scope and accepted on linux stable.
* Alternatively the issue is known to be avoided when oplocks are
disabled using "cifs.enable_oplocks=N" module parameter.
[Test case]
* Unfortunately we cannot reproduce the issue. The patch proposed here was
validated by us with xfstests (instructions followed from
https://wiki.samba.org/index.php/Xfstesting-cifs) and fio. Also, we
have a user report of test validation using LISA
(https://github.com/LIS/LISAv2).
* Using xfstest with the exclusions proposed in the link above we
managed to get the same results as a non-patched kernel, i.e., the
same tests failed in both kernels, we didn't get worse results with
the patch. Fio also didn't show noticeable performance regression with
the patch.
[Regression potential]
* The patch was validated by the cifs filesystem maintainers (in fact
they suggested its inclusion in Ubuntu) and by the aforementioned
tests; also, the scope is restricted to cifs only so the likelihood of
regressions is considered low.
* Due to the nature of the code modification (add a new reference of a
file handler and manipulate it in different places), I consider that
if we have a regression it'll manifest as deadlock/blocked tasks, not
something more serious like crashes or data corruption.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795659/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1764956] Re: Guests using IBRS incur a large performance penalty
** Changed in: linux (Ubuntu)
Status: In Progress => Fix Released
** Changed in: linux (Ubuntu Trusty)
Importance: Undecided => High
** Changed in: linux (Ubuntu Trusty)
Assignee: (unassigned) => Gavin Guo (mimi0213kimo)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1764956
Title:
Guests using IBRS incur a large performance penalty
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Trusty:
Fix Released
Status in linux source package in Xenial:
Fix Released
Bug description:
[Impact]
the IBRS would be mistakenly enabled in the host when the switching
from an IBRS-enabled VM and that causes the performance overhead in
the host. The other condition could also mistakenly disables the IBRS
in VM when context-switching from the host. And this could be
considered a CVE host.
[Fix]
The patch fixes the logic inside the x86_virt_spec_ctrl that it checks
the ibrs_enabled and _or_ the hostval with the SPEC_CTRL_IBRS as the
x86_spec_ctrl_base by default is zero. Because the upstream
implementation is not equal to the Xenial's implementation. Upstream
doesn't use the IBRS as the formal fix. So, by default, it's zero.
On the other hand, after the VM exit, the SPEC_CTRL register also
needs to be saved manually by reading the SPEC_CTRL MSR as the MSR
intercept is disabled by default in the hardware_setup(v4.4) and
vmx_init(v3.13). The access to SPEC_CTRL MSR in VM is direct and
doesn't trigger a trap. So, the vmx_set_msr() function isn't called.
The v3.13 kernel hasn't been tested. However, the patch can be viewed
at:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-trusty-amd64.git/log/?h=sf00191076-sru
The v4.4 patch:
http://kernel.ubuntu.com/git/gavinguo/ubuntu-xenial.git/log/?h=sf00191076-spectre-v2-regres-backport-juerg
[Test]
The patch has been tested on the 4.4.0-140.166 and works fine.
The reproducing environment:
Guest kernel version: 4.4.0-138.164
Host kernel version: 4.4.0-140.166
(host IBRS, guest IBRS)
- 1). (0, 1).
The case can be reproduced by the following instructions:
guest$ echo 1 | sudo tee /proc/sys/kernel/ibrs_enabled
1
host$ cat /proc/sys/kernel/ibrs_enabled
0
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
110001001010
Some of the IBRS bit inside the SPEC_CTRL MSR are mistakenly
enabled.
host$ taskset -c 5 stress-ng -c 1 --cpu-ops 2500
stress-ng: info: [11264] defaulting to a 86400 second run per stressor
stress-ng: info: [11264] dispatching hogs: 1 cpu
stress-ng: info: [11264] cache allocate: default cache size: 35840K
stress-ng: info: [11264] successful run completed in 33.48s
The host kernel didn't notice the IBRS bit is enabled. So, the situation
is the same as "echo 2 > /proc/sys/kernel/ibrs_enabled" in the host.
And running the stress-ng is a pure userspace CPU capability
calculation. So, the performance downgrades to about 1/3. Without the
IBRS enabled, it needs about 10s.
- 2). (1, 1) disables IBRS in host -> (0, 1) actually it becomes (0, 0).
The guest IBRS has been mistakenly disabled.
guest$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 2 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
host$ echo 0 | sudo tee /proc/sys/kernel/ibrs_enabled
host$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
guest$ for i in {0..55}; do sudo rdmsr 0x48 -p $i; done
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1764956/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845048] Re: Improve sysctl handling on kdump-tools
** Changed in: makedumpfile (Ubuntu) Status: Confirmed => In Progress ** Changed in: makedumpfile (Ubuntu Xenial) Status: Confirmed => Opinion ** Changed in: makedumpfile (Ubuntu Bionic) Status: Confirmed => In Progress ** Changed in: makedumpfile (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: makedumpfile (Ubuntu Focal) Status: Confirmed => In Progress ** Also affects: makedumpfile (Ubuntu Groovy) Importance: Medium Assignee: Guilherme G. Piccoli (gpiccoli) Status: In Progress ** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1845048 Title: Improve sysctl handling on kdump-tools Status in makedumpfile package in Ubuntu: In Progress Status in makedumpfile source package in Xenial: Opinion Status in makedumpfile source package in Bionic: In Progress Status in makedumpfile source package in Eoan: In Progress Status in makedumpfile source package in Focal: In Progress Status in makedumpfile source package in Groovy: In Progress Status in makedumpfile package in Debian: New Bug description: [impact] Documentation, and past behavior, for kdump-tools was that the KDUMP_SYSCTL variable in the /etc/default/kdump-tools file would be applied to the system kernel params at kdump 'load'. However this is no longer true, and those params are no longer applied to the system's kernel param settings. [test case] install linux-crashdump (and kdump-tools). Edit the /etc/default/kdump-tools file to set the KDUMP_SYSCTL param to something other than default, e.g.: KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" reboot, or unload/reload kdump, to pick up the changes to the file. Check if the panic_on_warn param is set: $ cat /proc/sys/kernel/panic_on_warn 0 the problem does not seem to be with sysctl, as manually calling it does work: $ KDUMP_SYSCTL="kernel.panic_on_oops=1 kernel.panic_on_warn=1" $ cat /proc/sys/kernel/panic_on_warn 0 $ sudo sysctl -w $KDUMP_SYSCTL kernel.panic_on_oops = 1 kernel.panic_on_warn = 1 $ cat /proc/sys/kernel/panic_on_warn 1 [regression potential] TBD To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1845048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887190/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe :
[Kernel-packages] [Bug 1887213] Re: Touchpad stopped working after upgrade: 18.04 => 20.04
** Tags added: hwe-touchpad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887213 Title: Touchpad stopped working after upgrade: 18.04 => 20.04 Status in linux package in Ubuntu: Incomplete Bug description: > Laptop model directly from the sticker of the computer. Lenovo T450 ThinkPad > Manufacturer of the Touchpad. > When the symptom first appeared. Right after 18.04 => 20.04 upgrade. Touchpad never worked after upgrade. Nor movements, neither clicks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyga 2740 F pulseaudio /dev/snd/controlC0: cyga 2740 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 13:36:53 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d66c9dac-9065-401a-8f9a-3f208be7d2e6 InstallationDate: Installed on 2017-06-07 (1129 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20BV0005US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 acpi=force irqpoll quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-27 (13 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV0005US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BV0005US:pvrThinkPadT450:rvnLENOVO:rn20BV0005US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV0005US dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1475204] Re: Fix kmalloc slab creation sequence
** Changed in: linux (Ubuntu) Status: Triaged => 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/1475204 Title: Fix kmalloc slab creation sequence Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Committed Status in linux source package in Utopic: Fix Committed Status in linux source package in Vivid: Fix Released Bug description: [Impact] commit 4066c33d0308f8 breaks booting under KVM https://lkml.org/lkml/2015/6/26/341 I can no longer boot Linus's tree under KVM using a 32-bit i386 build; it just hangs before any messages get sent to the serial console. This following commit breaks 32-bit and 64-bit x86 if you have CONFIG_SLAB enabled. When I switched to CONFIG_SLUB, the kernel boots. So it appears this commit is breaking kernel configurations with CONFIG_SLAB enabled. It bisects down to: commit 4066c33d0308f87e9a3b0c7fafb9141c0bfbfa77 Author: Gavin Guo Date: Wed Jun 24 16:55:54 2015 -0700 mm/slab_common: support the slub_debug boot option on specific object size The slub_debug=PU,kmalloc-xx cannot work because in the create_kmalloc_caches() the s->name is created after the create_kmalloc_cache() is called. The name is NULL in the create_kmalloc_cache() so the kmem_cache_flags() would not set the slub_debug flags to the s->flags. The fix here set up a kmalloc_names string array for the initialization purpose and delete the dynamic name creation of kmalloc_caches. [a...@linux-foundation.org: s/kmalloc_names/kmalloc_info/, tweak comment text] Signed-off-by: Gavin Guo Acked-by: Christoph Lameter Cc: Pekka Enberg Cc: David Rientjes Cc: Joonsoo Kim Signed-off-by: Andrew Morton Signed-off-by: Linus Torvalds [Fix] This is the regression of bug: BugLink: http://bugs.launchpad.net/bugs/1456952 and fixed by: [PATCH] Fix kmalloc slab creation sequence https://lkml.org/lkml/2015/6/29/231 This patch restores the slab creation sequence that was broken by commit 4066c33d0308f8 and also reverts the portions that introduced the KMALLOC_LOOP_XXX macros. Those can never really work since the slab creation is much more complex than just going from a minimum to a maximum number. The latest upstream kernel boots cleanly on my machine with a 64 bit x86 configuration under KVM using either SLAB or SLUB. [Test cases] Currently, the bug can't be reproduced on the Ubuntu kernel by enabling the slab allocator with i386 and x86_64 architecture. However, in case anyone will hit the bug, the patch should be applied in the Ubuntu kernel. [Regression potential] The patch is to fix the kmalloc_caches initialization sequence, that the 96, and 192 bytes kmem_cache should be enabled after the normal 2's exponential size kmem_cache. This should have low regression potential. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1475204/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882388] Re: Touchpad recognised as generic mouse
I suspended my laptop during the night; when I logged in again, the touchpad worked for a while, but eventually got back as a generic mouse (still mainline kernel). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882388 Title: Touchpad recognised as generic mouse Status in linux package in Ubuntu: Confirmed Bug description: I've just re-installed 20.04 (dual boot/windows 10) on my Lenovo ideapadY700. My laptop recognises touchpad as mouse. I have no other mouse plugged. Touchpad firmware: 2ul001af Lenovo ideapad700-15ISK BIOS version: CDCN54WW I'm new in Ubuntu and I don't know much... ```$ uname -a``` ```Linux nando-Lenovo 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux``` ```$ dmesg | grep psmouse``` ```[ 30.218871] psmouse serio1: elantech: synaptics_send_cmd query 0x01 failed. [ 30.218879] psmouse serio1: elantech: failed to query firmware version. [ 165.209816] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 216.923481] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 468.662298] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. [ 553.556484] psmouse serio1: Wheel Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away. ``` ```$ xinput``` ```⎡ Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ PS/2 Logitech Wheel Mouse id=14 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ Sleep Buttonid=10 [slave keyboard (3)] ↳ Lenovo EasyCamera: Lenovo EasyC id=11 [slave keyboard (3)] ↳ Ideapad extra buttons id=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] ``` ```$ cat /proc/bus/input/devices``` ```I: Bus=0011 Vendor=0002 Product=0001 Version=0063 N: Name="PS/2 Logitech Wheel Mouse" P: Phys=isa0060/serio1/input0 S: Sysfs=/devices/platform/i8042/serio1/input/input19 U: Uniq= H: Handlers=mouse0 event16 B: PROP=1 B: EV=7 B: KEY=7 0 0 0 0 B: REL=3 ``` I have read a lot of solutions; I tried to use xorg, but it didn't work. When I removed it, it worked for a day (only) and I decided erase and re-install Ubuntu. Please help! Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nando 1137 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 20:24:24 2020 InstallationDate: Installed on 2020-06-06 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 5986:0672 Acer, Inc Lenovo EasyCamera Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 80NV ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=eccd5181-f592-4fbf-a03f-3efbc86e693b ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/13/2017 dmi.bios.vendor: LENOVO dmi.bios.version: CDCN54WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: Allsparks 5A dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad Y700-15ISK dmi.modalias:
[Kernel-packages] [Bug 1887539] [NEW] [UBUNTU 18.04.4] Charmed Kubernetes local deployment failed for s390x because of etcd error
You have been subscribed to a public bug: Steps to reproduce: Clean Z LPAR machine. Followed official documentation https://ubuntu.com/kubernetes/docs/install-local. Actual results: Cluster did not start and hang in the follow state: # juju status Model Controller Cloud/Region Version SLA Timestamp k8slxd-controller localhost/localhost 2.8.1unsupported 16:11:10+02:00 AppVersion Status Scale Charm Store Rev OS Notes containerd 1.3.3maintenance 5 containerd jujucharms 80 ubuntu easyrsa3.0.1active 1 easyrsa jujucharms 318 ubuntu etcd 3.3.15 waiting 3 etcd jujucharms 521 ubuntu flannel0.11.0 blocked 5 flannel jujucharms 492 ubuntu kubeapi-load-balancer 1.14.0 active 1 kubeapi-load-balancer jujucharms 730 ubuntu exposed kubernetes-master 1.18.5 waiting 2 kubernetes-master jujucharms 850 ubuntu kubernetes-worker 1.18.5 blocked 3 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0*active idle 010.63.81.207 Certificate Authority connected. etcd/0* active idle 110.63.81.209 2379/tcp Errored with 0 known peers etcd/1waiting idle 210.63.81.36 Waiting to retry etcd registration etcd/2waiting idle 310.63.81.218 Waiting to retry etcd registration kubeapi-load-balancer/0* active idle 410.63.81.145 NGINX is ready kubernetes-master/0* waiting executing 510.63.81.239 Waiting for kube-api-endpoint relation containerd/4maintenance executing 10.63.81.239 (install) installing charm software flannel/4 blocked executing 10.63.81.239 (install) Waiting for etcd relation. kubernetes-master/1 waiting executing 610.63.81.213 Waiting for kube-api-endpoint relation containerd/3active executing 10.63.81.213 (leader-settings-changed) Container runtime available flannel/3 blocked executing 10.63.81.213 (leader-settings-changed) Waiting for etcd relation. kubernetes-worker/0 waiting executing 710.63.81.155 Waiting for cluster DNS. containerd/2active executing 10.63.81.155 (start) Container runtime available flannel/2 maintenance executing 10.63.81.155 Negotiating flannel network subnet. kubernetes-worker/1 blocked executing 810.63.81.53 (config-changed) Connect a container runtime. containerd/1active executing 10.63.81.53 (start) Container runtime available flannel/1 maintenance executing 10.63.81.53 Negotiating flannel network subnet. kubernetes-worker/2* blocked executing 910.63.81.219 Connect a container runtime. containerd/0* active idle10.63.81.219 Container runtime available flannel/0* maintenance executing 10.63.81.219 Negotiating flannel network subnet. Machine StateDNS Inst idSeries AZ Message 0started 10.63.81.207 juju-6e9ea7-0 bionic Running 1started 10.63.81.209 juju-6e9ea7-1 bionic Running 2started 10.63.81.36 juju-6e9ea7-2 bionic Running 3started 10.63.81.218 juju-6e9ea7-3 bionic Running 4started 10.63.81.145 juju-6e9ea7-4 bionic Running 5started 10.63.81.239 juju-6e9ea7-5 bionic Running 6started 10.63.81.213 juju-6e9ea7-6 bionic Running 7started 10.63.81.155 juju-6e9ea7-7 bionic Running 8started 10.63.81.53 juju-6e9ea7-8 bionic Running 9started 10.63.81.219 juju-6e9ea7-9 bionic Running After ssh to etcd/1 I can see error logs at /var/log/syslog: Jul 14 14:11:46 juju-6e9ea7-2 etcd.etcd[27280]: 2020-07-14 14:11:46.612925 E | etcdmain: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=s390x set. Jul 14 14:11:46 juju-6e9ea7-2 systemd[1]: snap.etcd.etcd.service: Main process exited, code=exited, status=1/FAILURE Jul 14 14:11:46 juju-6e9ea7-2 systemd[1]: snap.etcd.etcd.service: Failed with result 'exit-code'. ** Affects: linux (Ubuntu) Importance: Undecided
[Kernel-packages] [Bug 1879214] Re: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported
** Changed in: makedumpfile (Ubuntu) Assignee: (unassigned) => Ioanna Alifieraki (joalif) ** Tags added: sts -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1879214 Title: Package makedumpfile 1:1.6.7-1ubuntu2(arm64) failed to makedumpfile:calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported Status in makedumpfile package in Ubuntu: Confirmed Bug description: OS: Ubuntu 20.04 LTS kernel: 5.4.0-21-generic arch:arm64 Description: When testing kdump on Ubuntu 20.04 LTS (arm64), makedumpfile fails. The test steps are as follows: # echo 1> / proc / sys / kernel / sysrq # echo c> / proc / sysrq-trigger The error logs are as follows: [ 26.599161] kdump-tools[653]: Starting kdump-tools: [ 26.612761] kdump-tools[659]: Starting kdump-tools: [ 26.628565] kdump-tools[659]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.648621] kdump-tools[676]: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/2020050 [ 26.668445] kdump-tools[676]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 26.678199] kdump-tools[676]: get_machdep_info_arm64 [ 26.692518] kdump-tools[659]: get_machdep_info_arm64 [ 26.852221] hns3 :7d:00.0: get link status cmd failed -16 [ 94.351303] kdump-tools[659]: * kdump-tools: makedumpfile failed, * kdump-tools: saved vmcore in /var/crash/202005061048 [ 94.435510] kdump-tools[659]: * running makedumpfile --dump-dmesg /proc/vmcore /var/crash/202005061048/dmesg.202005061048 [ 94.457103] kdump-tools[688]: calculate_plat_config: PAGE SIZE 0x1000 and VA Bits 47 not supported [ 94.476228] kdump-tools[688]: get_machdep_info_arm64: Can't determine platform config values [ 94.485912] kdump-tools[688]: makedumpfile Failed. [ 94.500760] kdump-tools[659]: * kdump-tools: makedumpfile --dump-dmesg failed. dmesg content will be unavailable [ 94.520225] kdump-tools[659]: * kdump-tools: failed to save dmesg content in /var/crash/202005061048 [ 94.544205] kdump-tools[691]: Wed, 06 May 2020 10:49:42 -0400 [ 94.564597] kdump-tools[692]: Rebooting. [ 94.678709] reboot: Restarting systemlpc uart init Done To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1879214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838141] Re: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling.
Personally I've disabled pstate driver from kernel command line. Events like suspend, lid close and restart completely changes the behavior. While working on battery I sometimes will close the lid and when I open back CPU is at 4Ghz and battery gets drained in 30mins. Not to mention the heating. *It simply doesn't work.* The acpi driver is much better and battery life is great too. No lid/suspend issue so far. I'm on Ubuntu 20.04 stock kernel: Linux Predator-300 5.4.0-40-lowlatency #44-Ubuntu SMP PREEMPT Tue Jun 23 01:32:24 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838141 Title: intel_pstate not working. CPU frequency fixed at 800MHz. No cpu frequency scaling. Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Confirmed Bug description: intel_pstate not working. CPU frequency fixed at 800MHz. I've tried to modify frequency using "cpufreq-set" and also by directly writing to files in "/sys/devices/system/cpu/cpu0/cpufreq/*" to no success. I tried different versions of kernel, it started working on 4.17.0 but stopped working soon. These are the versions I tested. 5.2.3 - Not Working 5.1.0 - Not Working 4.19.60 - Not Working 4.18.20 - Not Working 4.17.19 - Not Working 4.17.10 - Not Working 4.17.5 - Not Working 4.17.3 - Not Working 4.17.2 - Working 4.17.1 - Working 4.17.0 - Working 4.16.18 - Not Working 4.15.0 - Not Working Please let me know if anything else is needed. thanks ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-55-generic 4.15.0-55.60 ProcVersionSignature: Ubuntu 4.15.0-55.60-generic 4.15.18 Uname: Linux 4.15.0-55-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: srijan 2219 F pulseaudio CurrentDesktop: KDE Date: Sat Jul 27 11:34:10 2019 InstallationDate: Installed on 2018-11-25 (243 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0bda:5621 Realtek Semiconductor Corp. Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Acer Predator PH315-51 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-55-generic root=UUID=a76bd009-8058-4e96-a8b5-a82b7fbe1ede ro acpi_backlight=vendor i915.modeset=1 i915.enable_guc=3 i915.enable_dc=2 i915.enable_fbc=1 nvme_core.default_ps_max_latency_us=1800 pcie_aspm=force i915.enable_psr=2 i915.disable_power_well=1 nmi_watchdog=0 RelatedPackageVersions: linux-restricted-modules-4.15.0-55-generic N/A linux-backports-modules-4.15.0-55-generic N/A linux-firmware 1.173.10 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) WifiSyslog: dmi.bios.date: 12/05/2018 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.24 dmi.board.asset.tag: Type2 - Board Serial Number dmi.board.name: Sienta_CFS dmi.board.vendor: CFL dmi.board.version: V1.24 dmi.chassis.type: 10 dmi.chassis.vendor: Acer dmi.chassis.version: V1.24 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.24:bd12/05/2018:svnAcer:pnPredatorPH315-51:pvrV1.24:rvnCFL:rnSienta_CFS:rvrV1.24:cvnAcer:ct10:cvrV1.24: dmi.product.family: Predator Helios 300 dmi.product.name: Predator PH315-51 dmi.product.version: V1.24 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883670] Re: Disable IEC958 on HP Thunderbolt Dock
current proposed version is 5.6.0.1020.17, let me wait for it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1883670 Title: Disable IEC958 on HP Thunderbolt Dock Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in alsa-lib package in Ubuntu: Fix Released Status in alsa-lib source package in Focal: Fix Released Status in alsa-lib source package in Groovy: Fix Released Bug description: [Impact] On HP Thunderbolt Dock, unusable SPDIF can be selected as output from PulseAudio. [Fix] Disable IEC958 (SPDIF) through ALSA UCM. [Test] With the UCM applied, `pactl` and audio panel in gnome-control-center no longer have SPDIF option. [Regression Potential] Low. This fix limits to the HP Thunderbolt Dock, other devices are unaffected. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1883670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887124] Re: [UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally
Kernel SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2020-July/thread.html#112024 Updating status to 'In Progress'. ** Description changed: + SRU Justification: + == + + [Impact] + + * DIF and DIX support in zfcp (s390x) is broken and the kernel crashes + unconditionally, in case one activates either zfcp DIF (data integrity + field) or DIX (data integrity extention) and attaches any LU. + + * zfcp used to allocate/add the shost object for a HBA, before knowing + all the HBA's capabilities. But later the shost object got patched to + make more of the capabilities known - including the protection + capabilities. + + * Changes that are later made to the protection capabilities don't get + reflected in the tag-set requests and are missing. + + * Now sending I/O, scsi_mod tries to access the protection payload data, + that isn't there, and the kernel crashes. + + [Fix] + + * The SRU request was created as pull request, so please pull starting + at 0b38938af911 to head / 9227405ee311 from + https://code.launchpad.net/~fheimes/+git/lp1887124 + + [Test Case] + + * Have a IBM Z or LInuxONE system (ideally on LPAR) in place that is + connected to a DS8xxx storage subsystem that supports, zfcp SCSI storage + with DIF and DIX. + + * Have an Ubuntu Server 20.04 installed in such a LPAR system. + + * Now enable DIF (zfcp.dif=1) or DIX (zfcp.dix=1) and connect the system + to a logical unit. + + * Monitor the system for any kernel crashes (/var/log/syslog and + /var/log/kern.log) - look for kernel panic in scsi_queue_rq. + + [Regression Potential] + + * Even if the modifications are substantial, the regression potnetial + can be considered as moderate. + + * This issue could be mainly tracked down to commit '737eb78e82d5' (made + for v5.4) that made the problem more visible. + + * With the old blk queue DIF/DIX worked fine, but after scsi_mod switched to blk-mq (and because requests are now + all allocated during allocation time of the blk-mq tag-set), it didn't worked anymore. + + * The solution is to allocate/add the shost object for a HBA after all + of its base capabilities are known. + + * Since the situation is like this for quite a while, several places in + the zfcp driver code (where it's assumed that the shost object was + correctly allocated) needed to be touched. + + * This is finally the reason (as well as the fact that some parts depend + on code that went upstream with the kernels 5.5 and 5.7) for this rather + big patchset for fixing DIF and DIX support in zfcp. + + * On the other hand side this entire set is now upstream accepted and + entirely included in 5.8 (and with that soon in groovy), and no + 5.4-specific (hand-crafted) backports are needed. + + * Also notice that all modifications are in the zfcp driver layer, hence + they are s390x specific, and with that limited to + /drivers/s390/scsi/zfcp_* + + * Finally the patches were already tested with a patched focal kernel + with DIF/DIX/NONE, with I/O, and local/remote cable pulls - switched and + point-to-point connected. No regressions were identified. + + [Other] + + * Alternatively the patches can also be cherry-picked from linux master with: + git cherry-pick 92953c6e0aa7~1..e76acc519426 + git cherry-pick a3fd4bfe85fb + git cherry-pick e05a10a05509~1..42cabdaf103b + git cherry-pick cec9cbac5244 + git cherry-pick 978857c7e367~1..d0dff2ac98dd + + * The following lists the individual commits - just for the reason of + completeness: + + * 92953c6e0aa77d4febcca6dd691e8192910c8a28 92953c6e0aa77 "scsi: zfcp: + signal incomplete or error for sync exchange config/port data" + + * 7e418833e68948cb9ed15262889173b7db2960cb 7e418833e6894 "scsi: zfcp: + diagnostics buffer caching and use for exchange port data" + + * 088210233e6fc039fd2c0bfe44b06bb94328d09e 088210233e6fc "scsi: zfcp: + add diagnostics buffer for exchange config data" + + * a10a61e807b0a226b78e2041843cbf0521bd0c35 a10a61e807b0a "scsi: zfcp: + support retrieval of SFP Data via Exchange Port Data" + + * 6028f7c4cd87cac13481255d7e35dd2c9207ecae 6028f7c4cd87c "scsi: zfcp: + introduce sysfs interface for diagnostics of local SFP transceiver" + + * 8155eb0785279728b6b2e29aba2ca52d16aa526f 8155eb0785279 "scsi: zfcp: + implicitly refresh port-data diagnostics when reading sysfs" + + * 5a2876f0d1ef26b76755749f978d46e4666013dd 5a2876f0d1ef2 "scsi: zfcp: + introduce sysfs interface to read the local B2B-Credit" + + * 8a72db70b5ca3c3feb3ca25519e8a9516cc60cfe 8a72db70b5ca3 "scsi: zfcp: + implicitly refresh config-data diagnostics when reading sysfs" + + * 48910f8c35cfd250d806f3e03150d256f40b6d4c 48910f8c35cfd "scsi: zfcp: + move maximum age of diagnostic buffers into a per-adapter variable" + + * e76acc51942649398660ca50655af5afecf29c42 e76acc5194264 "scsi: zfcp: + proper indentation to reduce confusion in zfcp_erp_required_act" + + * a3fd4bfe85fbb67cf4ec1232d0af625ece3c508b a3fd4bfe85fbb "scsi: zfcp: + fix
[Kernel-packages] [Bug 1820063] Re: [Hyper-V] KVP daemon fails to start on first boot of disco VM
Seeing this on bare metal (Dell R740xd) with Ubuntu 18.04 and linux- image-generic-hwe-18.04 (5.3.0-62-generic) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820063 Title: [Hyper-V] KVP daemon fails to start on first boot of disco VM Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Disco: Fix Released Bug description: SRU Justification Impact: The KVP daemon fails to start on first boot due to being started before the hv_kvp device appears. Fix: Update the hv-kvp-daemon service file to start the daemon after device node appears. Regression Potential: The changes are only to the hv-kvp-daemon service file and adding a udev rule, so the worst case regression would be that the service does not start. In testing the service did start as expected. Test Case: See comment #15. --- Launching a recent daily image of disco on azure results in a VM in which the hv-kvp-daemon.service fails to start: $ systemctl status -o cat hv-kvp-daemon.service ● hv-kvp-daemon.service - Hyper-V KVP Protocol Daemon Loaded: loaded (/lib/systemd/system/hv-kvp-daemon.service; enabled; vendor pr Active: failed (Result: exit-code) since Thu 2019-03-14 13:07:15 UTC; 11min a Main PID: 219 (code=exited, status=1/FAILURE) Started Hyper-V KVP Protocol Daemon. KVP starting; pid is:219 open /dev/vmbus/hv_kvp failed; error: 2 No such file or directory hv-kvp-daemon.service: Main process exited, code=exited, status=1/FAILURE hv-kvp-daemon.service: Failed with result 'exit-code'. The instance was created with: $ az vm create --resource-group [redacted] --image Canonical:UbuntuServer:19.04-DAILY:19.04.201903130 --size Standard_D2_v2 --name disco-0313 As best as I can tell, the /dev/vmbus/hv_kvp isn't available when the hv-kvp-daemon.service starts, but it is available a few seconds later. Manually starting the daemon once I can ssh in works. --- ProblemType: Bug AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: N/A DistroRelease: Ubuntu 19.04 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: MachineType: Microsoft Corporation Virtual Machine Package: linux (not installed) PciMultimedia: ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 hyperv_fb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-1011-azure root=PARTUUID=11894199-2ca2-4912-9c41-d28128744d57 ro console=tty1 console=ttyS0 panic=-1 ProcVersionSignature: User Name 4.18.0-1011.11-azure 4.18.20 RelatedPackageVersions: linux-restricted-modules-4.18.0-1011-azure N/A linux-backports-modules-4.18.0-1011-azure N/A linux-firmware N/A RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' Tags: disco uec-images Uname: Linux 4.18.0-1011-azure x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy netdev plugdev sudo video _MarkForUpload: True dmi.bios.date: 06/02/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 090007 dmi.board.name: Virtual Machine dmi.board.vendor: Microsoft Corporation dmi.board.version: 7.0 dmi.chassis.asset.tag: 7783-7084-3265-9085-8269-3286-77 dmi.chassis.type: 3 dmi.chassis.vendor: Microsoft Corporation dmi.chassis.version: 7.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr090007:bd06/02/2017:svnMicrosoftCorporation:pnVirtualMachine:pvr7.0:rvnMicrosoftCorporation:rnVirtualMachine:rvr7.0:cvnMicrosoftCorporation:ct3:cvr7.0: dmi.product.name: Virtual Machine dmi.product.uuid: 3b0f2160-7fc4-a646-904c-4248f04792d4 dmi.product.version: 7.0 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887539] Re: [UBUNTU 18.04.4] Charmed Kubernetes local deployment failed for s390x because of etcd error
** Package changed: linux (Ubuntu) => etcd (Ubuntu) ** Also affects: ubuntu-z-systems Importance: Undecided Status: New ** Changed in: ubuntu-z-systems Assignee: (unassigned) => Kubernetes Charmers (kubernetes) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887539 Title: [UBUNTU 18.04.4] Charmed Kubernetes local deployment failed for s390x because of etcd error Status in Ubuntu on IBM z Systems: New Status in etcd package in Ubuntu: New Bug description: Steps to reproduce: Clean Z LPAR machine. Followed official documentation https://ubuntu.com/kubernetes/docs/install-local. Actual results: Cluster did not start and hang in the follow state: # juju status Model Controller Cloud/Region Version SLA Timestamp k8slxd-controller localhost/localhost 2.8.1unsupported 16:11:10+02:00 AppVersion Status Scale Charm Store Rev OS Notes containerd 1.3.3maintenance 5 containerd jujucharms 80 ubuntu easyrsa3.0.1active 1 easyrsa jujucharms 318 ubuntu etcd 3.3.15 waiting 3 etcd jujucharms 521 ubuntu flannel0.11.0 blocked 5 flannel jujucharms 492 ubuntu kubeapi-load-balancer 1.14.0 active 1 kubeapi-load-balancer jujucharms 730 ubuntu exposed kubernetes-master 1.18.5 waiting 2 kubernetes-master jujucharms 850 ubuntu kubernetes-worker 1.18.5 blocked 3 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0*active idle 010.63.81.207 Certificate Authority connected. etcd/0* active idle 110.63.81.209 2379/tcp Errored with 0 known peers etcd/1waiting idle 210.63.81.36 Waiting to retry etcd registration etcd/2waiting idle 310.63.81.218 Waiting to retry etcd registration kubeapi-load-balancer/0* active idle 410.63.81.145 NGINX is ready kubernetes-master/0* waiting executing 510.63.81.239 Waiting for kube-api-endpoint relation containerd/4maintenance executing 10.63.81.239 (install) installing charm software flannel/4 blocked executing 10.63.81.239 (install) Waiting for etcd relation. kubernetes-master/1 waiting executing 610.63.81.213 Waiting for kube-api-endpoint relation containerd/3active executing 10.63.81.213 (leader-settings-changed) Container runtime available flannel/3 blocked executing 10.63.81.213 (leader-settings-changed) Waiting for etcd relation. kubernetes-worker/0 waiting executing 710.63.81.155 Waiting for cluster DNS. containerd/2active executing 10.63.81.155 (start) Container runtime available flannel/2 maintenance executing 10.63.81.155 Negotiating flannel network subnet. kubernetes-worker/1 blocked executing 810.63.81.53 (config-changed) Connect a container runtime. containerd/1active executing 10.63.81.53 (start) Container runtime available flannel/1 maintenance executing 10.63.81.53 Negotiating flannel network subnet. kubernetes-worker/2* blocked executing 910.63.81.219 Connect a container runtime. containerd/0* active idle10.63.81.219 Container runtime available flannel/0* maintenance executing 10.63.81.219 Negotiating flannel network subnet. Machine StateDNS Inst idSeries AZ Message 0started 10.63.81.207 juju-6e9ea7-0 bionic Running 1started 10.63.81.209 juju-6e9ea7-1 bionic Running 2started 10.63.81.36 juju-6e9ea7-2 bionic Running 3started 10.63.81.218 juju-6e9ea7-3 bionic Running 4started 10.63.81.145 juju-6e9ea7-4 bionic Running 5started 10.63.81.239 juju-6e9ea7-5 bionic Running 6started 10.63.81.213 juju-6e9ea7-6 bionic Running 7started 10.63.81.155 juju-6e9ea7-7 bionic
[Kernel-packages] [Bug 1887539] [NEW] [UBUNTU 18.04.4] Charmed Kubernetes local deployment failed for s390x because of etcd error
Public bug reported: Steps to reproduce: Clean Z LPAR machine. Followed official documentation https://ubuntu.com/kubernetes/docs/install-local. Actual results: Cluster did not start and hang in the follow state: # juju status Model Controller Cloud/Region Version SLA Timestamp k8slxd-controller localhost/localhost 2.8.1unsupported 16:11:10+02:00 AppVersion Status Scale Charm Store Rev OS Notes containerd 1.3.3maintenance 5 containerd jujucharms 80 ubuntu easyrsa3.0.1active 1 easyrsa jujucharms 318 ubuntu etcd 3.3.15 waiting 3 etcd jujucharms 521 ubuntu flannel0.11.0 blocked 5 flannel jujucharms 492 ubuntu kubeapi-load-balancer 1.14.0 active 1 kubeapi-load-balancer jujucharms 730 ubuntu exposed kubernetes-master 1.18.5 waiting 2 kubernetes-master jujucharms 850 ubuntu kubernetes-worker 1.18.5 blocked 3 kubernetes-worker jujucharms 682 ubuntu exposed Unit Workload Agent Machine Public address Ports Message easyrsa/0*active idle 010.63.81.207 Certificate Authority connected. etcd/0* active idle 110.63.81.209 2379/tcp Errored with 0 known peers etcd/1waiting idle 210.63.81.36 Waiting to retry etcd registration etcd/2waiting idle 310.63.81.218 Waiting to retry etcd registration kubeapi-load-balancer/0* active idle 410.63.81.145 NGINX is ready kubernetes-master/0* waiting executing 510.63.81.239 Waiting for kube-api-endpoint relation containerd/4maintenance executing 10.63.81.239 (install) installing charm software flannel/4 blocked executing 10.63.81.239 (install) Waiting for etcd relation. kubernetes-master/1 waiting executing 610.63.81.213 Waiting for kube-api-endpoint relation containerd/3active executing 10.63.81.213 (leader-settings-changed) Container runtime available flannel/3 blocked executing 10.63.81.213 (leader-settings-changed) Waiting for etcd relation. kubernetes-worker/0 waiting executing 710.63.81.155 Waiting for cluster DNS. containerd/2active executing 10.63.81.155 (start) Container runtime available flannel/2 maintenance executing 10.63.81.155 Negotiating flannel network subnet. kubernetes-worker/1 blocked executing 810.63.81.53 (config-changed) Connect a container runtime. containerd/1active executing 10.63.81.53 (start) Container runtime available flannel/1 maintenance executing 10.63.81.53 Negotiating flannel network subnet. kubernetes-worker/2* blocked executing 910.63.81.219 Connect a container runtime. containerd/0* active idle10.63.81.219 Container runtime available flannel/0* maintenance executing 10.63.81.219 Negotiating flannel network subnet. Machine StateDNS Inst idSeries AZ Message 0started 10.63.81.207 juju-6e9ea7-0 bionic Running 1started 10.63.81.209 juju-6e9ea7-1 bionic Running 2started 10.63.81.36 juju-6e9ea7-2 bionic Running 3started 10.63.81.218 juju-6e9ea7-3 bionic Running 4started 10.63.81.145 juju-6e9ea7-4 bionic Running 5started 10.63.81.239 juju-6e9ea7-5 bionic Running 6started 10.63.81.213 juju-6e9ea7-6 bionic Running 7started 10.63.81.155 juju-6e9ea7-7 bionic Running 8started 10.63.81.53 juju-6e9ea7-8 bionic Running 9started 10.63.81.219 juju-6e9ea7-9 bionic Running After ssh to etcd/1 I can see error logs at /var/log/syslog: Jul 14 14:11:46 juju-6e9ea7-2 etcd.etcd[27280]: 2020-07-14 14:11:46.612925 E | etcdmain: etcd on unsupported platform without ETCD_UNSUPPORTED_ARCH=s390x set. Jul 14 14:11:46 juju-6e9ea7-2 systemd[1]: snap.etcd.etcd.service: Main process exited, code=exited, status=1/FAILURE Jul 14 14:11:46 juju-6e9ea7-2 systemd[1]: snap.etcd.etcd.service: Failed with result 'exit-code'. ** Affects: ubuntu-z-systems Importance: Undecided Assignee: Kubernetes
[Kernel-packages] [Bug 1886188] Re: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation
** Changed in: linux (Ubuntu Groovy) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-riscv in Ubuntu. https://bugs.launchpad.net/bugs/1886188 Title: linux-libc-dev broken for crossbuilding, Multi-Arch:same violation Status in linux package in Ubuntu: Fix Committed Status in linux-riscv package in Ubuntu: Invalid Status in linux source package in Focal: In Progress Status in linux-riscv source package in Focal: In Progress Status in linux source package in Groovy: Fix Committed Status in linux-riscv source package in Groovy: Invalid Bug description: SRU Justificatoin Impact: Building linux-libc-dev for riscv64 from the linux-riscv package means that it can have a different version from the package on other architectures. This makes it uninstallable for cross building. Fix: Move the riscv64 linux-libc-dev build back to the main kernel package so that the version will match. Test Case: See below. Regression Potential: This could cause trouble if the main kernel package version is behind the linux-riscv package version, and may require artificially inflating the version of the linux package. Currently this is not necessary, but it needs to be kept in mind when preparing packages for upload with the fixes applied. --- # apt install linux-libc-dev:amd64 linux-libc-dev:riscv64 Reading package lists... Done Building dependency tree Reading state information... Done linux-libc-dev is already the newest version (5.4.0-26.30). Some packages could not be installed. This may mean that you have requested an impossible situation or if you are using the unstable distribution that some required packages have not yet been created or been moved out of Incoming. The following information may help to resolve the situation: The following packages have unmet dependencies: linux-libc-dev : Breaks: linux-libc-dev:riscv64 (!= 5.4.0-26.30) but 5.4.0-27.31 is to be installed linux-libc-dev:riscv64 : Breaks: linux-libc-dev (!= 5.4.0-27.31) but 5.4.0-26.30 is to be installed E: Unable to correct problems, you have held broken packages. $ rmadison -S linux-libc-dev | grep -e riscv64 -e amd64 | grep -e focal -e groovy linux-libc-dev | 5.4.0-24.28| focal| riscv64 linux-libc-dev | 5.4.0-26.30| focal| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-26.30| groovy | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-27.31| groovy | riscv64 linux-libc-dev | 5.4.0-28.32| focal-security | riscv64 linux-libc-dev | 5.4.0-28.32| focal-updates| riscv64 linux-libc-dev | 5.4.0-40.44| focal-security | amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| focal-updates| amd64, arm64, armhf, i386, ppc64el, s390x linux-libc-dev | 5.4.0-40.44| groovy-proposed | amd64, arm64, armhf, i386, ppc64el, s390x This is broken. linux-libc-dev must have identical content for common files, across all architectures, and must have identical version number. A few ways to fix this: * Either enforce that src:linux & src:linux-riscv are at the same version number. But then reasons for splitting riscv into a separate build dissappear * Make src:linux build _just_ the headers linux-libc-dev for risv64, and nothing else. And stop bulding linux-libc-dev form the src:linux- riscv package. Just like it does for i386. * Or create new src:linux-headers that only builds linux-libc-dev for all architectures, without building any kernels. This way for example, we could rev userspace headers to v5.8/v5.9 ahead of said kernel landing, to shake out build-failures / userspace issues, whilst the kernel itself is still baking in bootstrap/proposed PPA. This must be address in Focal and Groovy To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886188/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794877] Re: Crash in ixgbe, during tx packet xmit (while potentially changing queues number)
We couldn't reproduce the bug and reporter cannot help in providing data, so we're marking as invalid. If anybody ever reproduces that, please ping here and reopen. Thanks, Guilherme ** Changed in: linux (Ubuntu) Status: In Progress => Invalid ** Changed in: linux (Ubuntu Xenial) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794877 Title: Crash in ixgbe, during tx packet xmit (while potentially changing queues number) Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid Bug description: It was reported that ixgbe driver may crash with the following stack trace, while changing interrupt/queue configuration (probably using ethtool --set-channel): [28661.949147] init: irqbalance main process (19397) killed by TERM signal [28662.381154] ixgbe :04:00.0: removed PHC on eth4 [28662.502142] ixgbe :04:00.0: Multiqueue Enabled: Rx Queue count = 18, Tx Queue count = 18 [28662.588634] ixgbe :04:00.0: registered PHC device on eth4 [28662.689789] br-iscsi-left: port 1(eth4.4011) entered disabled state [28662.689951] br-sio-bel: port 1(eth4.4015) entered disabled state [28662.690039] br-sio-fel: port 1(eth4.4017) entered disabled state [28662.694227] ixgbe :04:00.0 eth4: NIC Link is Up 10 Gbps, Flow Control: RX/TX [28662.694506] br-iscsi-left: port 1(eth4.4011) entered forwarding state [28662.694519] br-iscsi-left: port 1(eth4.4011) entered forwarding state [28662.694596] br-sio-bel: port 1(eth4.4015) entered forwarding state [28662.694604] br-sio-bel: port 1(eth4.4015) entered forwarding state [28662.694651] br-sio-fel: port 1(eth4.4017) entered forwarding state [28662.694658] br-sio-fel: port 1(eth4.4017) entered forwarding state [28662.709921] ixgbe :04:00.1: removed PHC on eth5 [28662.834289] ixgbe :04:00.1: Multiqueue Enabled: Rx Queue count = 18, Tx Queue count = 18 [28662.915121] ixgbe :04:00.1: registered PHC device on eth5 [28663.018209] ixgbe :04:00.1 eth5: NIC Link is Up 10 Gbps, Flow Control: RX/TX [28663.018356] BUG: unable to handle kernel NULL pointer dereference at 0058 [28663.026266] IP: [] ixgbe_xmit_frame_ring+0x81/0xf50 [ixgbe] [28663.033491] PGD 800046bcc067 PUD 46bcd067 PMD 0 [28663.038562] Oops: [#1] SMP [28663.328921] Call Trace: [28663.334598] [28663.336551] [] ixgbe_xmit_frame+0x42/0x90 [ixgbe] [28663.349627] [] dev_hard_start_xmit+0x23d/0x400 [28663.358854] [] sch_direct_xmit+0xe4/0x1f0 [28663.367602] [] __qdisc_run+0x9b/0x1c0 [28663.376110] [] net_tx_action+0x15e/0x240 [28663.384673] [] __do_softirq+0xe6/0x2a0 [28663.392944] [] irq_exit+0x95/0xa0 [28663.400720] [] do_IRQ+0x56/0xe0 [28663.408338] [] common_interrupt+0xbf/0xbf [28663.416733] [28663.418680] [] ? worker_thread+0x18c/0x480 [28663.430363] [] ? rescuer_thread+0x310/0x310 [28663.438870] [] kthread+0xd8/0xf0 [28663.446368] [] ? kthread_park+0x60/0x60 [28663.454385] [] ret_from_fork+0x55/0x80 [28663.462286] [] ? kthread_park+0x60/0x60 [28663.470488] Code: 2a 41 83 e8 01 31 c0 45 0f b7 c0 49 83 c0 01 49 c1 e0 04 8b 74 07 3c 48 83 c0 10 8d 96 ff 3f 00 00 c1 ea 0e 01 d1 4c 39 c0 75 e8 <0f> b7 43 58 0f b7 73 5a 83 c1 03 31 d2 66 39 f0 66 0f 43 53 54 [28663.498992] RIP [] ixgbe_xmit_frame_ring+0x81/0xf50 [ixgbe] [28663.512112] RSP [28663.518217] CR2: 0058 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794877/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1771480] Re: WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90()
** Changed in: linux (Ubuntu) Status: Triaged => 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/1771480 Title: WARNING: CPU: 28 PID: 34085 at /build/linux- 90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: [impact] with a specific network configuration, a kernel WARNING is issued. [test case] configure a trusty system with e/n/i like this: auto bond0.2004 iface bond0.2004 inet manual mtu 9100 vlan-raw-device bond0 auto bond0 iface bond0 inet manual mtu 9100 bond-slaves eth1 eth2 bond-mode 802.3ad bond-miimon 100 bond-use-carrier 1 bond-lacp-rate fast bond-updelay 3000 bond-downdelay 1000 bond-ad-select bandwidth bond-xmit-hash-policy layer3+4 post-up sleep 45 auto br-mesh iface br-mesh inet static bridge_ports bond0.2004 address 192.168.210.3/24 auto eth1 iface eth1 inet manual mtu 9100 bond-master bond0 auto eth2 iface eth2 inet manual mtu 9100 bond-master bond0 adjusting the interface names as needed, of course. then reboot, and the kernel WARNING will appear in the dmesg. [regression potential] the kernel patch has the potential to incorrectly set, or incorrectly not set, features on devices. [other info] previous bug description: I have multiple instances of this dev_disable_lro error in kern.log. Also seeing this: systemd-udevd[1452]: timeout: killing 'bridge-network-interface' [2765] <4>May 1 22:56:42 xxx kernel: [ 404.520990] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:44 xxx kernel: [ 406.926429] bonding: bond0: Warning: No 802.3ad response from the link partner for any adapters in the bond <4>May 1 22:56:45 xxx kernel: [ 407.569020] [ cut here ] <4>May 1 22:56:45 xxx kernel: [ 407.569029] WARNING: CPU: 28 PID: 34085 at /build/linux-90Gc2C/linux-3.13.0/net/core/dev.c:1433 dev_disable_lro+0x87/0x90() <4>May 1 22:56:45 xxx kernel: [ 407.569032] netdevice: bond0.2004 <4>May 1 22:56:45 xxx kernel: [ 407.569032] failed to disable LRO! <4>May 1 22:56:45 xxx kernel: [ 407.569035] Modules linked in: 8021q garp mrp bridge stp llc bonding iptable_filter ip_tables x_tables nf_conntrack_proto_gre nf_conntrack_ipv6 nf_defrag_ipv6 nf_conntrack_ipv4 nf_defrag_ipv4 nf_conntrack ipmi_devintf mxm_wmi dcdbas x86_pkg_temp_thermal coretemp kvm_intel kvm crct10dif_pclmul crc32_pclmul ghash_clmulni_intel aesni_intel aes_x86_64 lrw gf128mul glue_helper ablk_helper cryptd lpc_ich mei_me mei ipmi_si shpchp wmi acpi_power_meter mac_hid xfs libcrc32c raid10 usb_storage raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq raid1 raid0 igb ixgbe i2c_algo_bit multipath ahci dca ptp libahci pps_core linear megaraid_sas mdio dm_multipath scsi_dh <4>May 1 22:56:45 xxx kernel: [ 407.569112] CPU: 28 PID: 34085 Comm: brctl Not tainted 3.13.0-142-generic #191-Ubuntu <4>May 1 22:56:45 xxx kernel: [ 407.569115] Hardware name: Dell Inc. PowerEdge R730xd/072T6D, BIOS 2.7.1 001/22/2018 <4>May 1 22:56:45 xxx kernel: [ 407.569118] 881fcc753c70 8172e7fc 881fcc753cb8 <4>May 1 22:56:45 xxx kernel: [ 407.569129] 0009 881fcc753ca8 8106afad 883fcc6f8000 <4>May 1 22:56:45 xxx kernel: [ 407.569139] 883fcc696880 883fcc6f8000 881fce82dd40 <4>May 1 22:56:45 xxx kernel: [ 407.569150] Call Trace: <4>May 1 22:56:45 xxx kernel: [ 407.569160] [] dump_stack+0x64/0x82 <4>May 1 22:56:45 xxx kernel: [ 407.569168] [] warn_slowpath_common+0x7d/0xa0 <4>May 1 22:56:45 xxx kernel: [ 407.569175] [] warn_slowpath_fmt+0x4c/0x50 <4>May 1 22:56:45 xxx kernel: [ 407.569183] [] dev_disable_lro+0x87/0x90 <4>May 1 22:56:45 xxx kernel: [ 407.569195] [] br_add_if+0x1f3/0x430 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569205] [] add_del_if+0x5d/0x90 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569215] [] br_dev_ioctl+0x5b/0x90 [bridge] <4>May 1 22:56:45 xxx kernel: [ 407.569223] [] dev_ifsioc+0x313/0x360 <4>May 1 22:56:45 xxx kernel: [ 407.569230] [] ? dev_get_by_name_rcu+0x69/0x90 <4>May 1 22:56:45 xxx kernel: [ 407.569237] [] dev_ioctl+0xe9/0x590 <4>May 1 22:56:45 xxx kernel: [ 407.569245] [] sock_do_ioctl+0x45/0x50 <4>May 1 22:56:45 xxx kernel: [ 407.569252] [] sock_ioctl+0x1f0/0x2c0 <4>May 1 22:56:45 xxx kernel: [ 407.569260] [] do_vfs_ioctl+0x2e0/0x4c0 <4>May 1 22:56:45 xxx kernel: [ 407.569267] [] ? fput+0xe/0x10 <4>May 1 22:56:45 xxx kernel: [ 407.569273] [] SyS_ioctl+0x81/0xa0 <4>May 1 22:56:45 xxx kernel: [ 407.569283] [] system_call_fastpath+0x2f/0x34 <4>May 1 22:56:45 xxx kernel: [
[Kernel-packages] [Bug 1861610] Re: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL'
No patch is working. SHTF already, I need to save the world tomorrow and my touchpad isn't working. If you aren't going to make it work just say it so I can do it myself. -- 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/1861610 Title: 'Elan touchpad' not detected on 'Lenovo ThinkBook 15 IIL' Status in linux package in Ubuntu: Confirmed Status in linux-oem-5.6 package in Ubuntu: Fix Released Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Released Status in linux-oem-5.6 source package in Bionic: Invalid Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux-oem-5.6 source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Status in linux-oem-5.6 source package in Focal: Fix Released Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification] [Impact] Touchpad function unavailable on some platforms with new ELAN touchpad HIDs. [Fix] https://lore.kernel.org/linux-input/000201d5a8bd$9fead3f0$dfc07bd0$@emc.com.tw/ required to match these currently unsupported IDs. [Test Case] 1. check if platform is affected, e.g. with ELAN0634: $ sudo acpidump | grep -C3 ELAN 2A060: 49 4E 54 31 70 0A 20 49 44 41 44 A4 84 53 42 46 INT1p.IDAD..SBF 2A070: 53 53 42 46 49 00 5B 82 42 0E 54 50 44 32 08 5F SSBFI.[.B.TPD2._ 2A080: 41 44 52 00 08 49 44 41 44 00 08 48 49 44 32 00 ADR..IDAD..HID2. 2A090: 08 5F 48 49 44 0D 45 4C 41 4E 30 36 33 34 00 08 ._HID.ELAN0634.. 2A0A0: 5F 43 49 44 0D 50 4E 50 30 43 35 30 00 08 5F 55 _CID.PNP0C50.._U 2A0B0: 49 44 01 14 4B 04 5F 44 53 4D 04 A0 3C 93 68 11 ID..K._DSM..<.h. 2A0C0: 13 0A 10 F7 F6 DF 3C 67 42 55 45 AD 05 B3 0A 3D ..https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861610/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1724614] Re: [KVM] Lower the default for halt_poll_ns to 200000 ns
** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Xenial) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1724614 Title: [KVM] Lower the default for halt_poll_ns to 20 ns Status in linux source package in Zesty: Won't Fix Status in linux source package in Groovy: New Bug description: [Environment] Distributor ID: Ubuntu Description: Ubuntu 16.04.3 LTS Release: 16.04 Codename: xenial Linux porygon 4.4.0-112-generic #135-Ubuntu SMP Fri Jan 19 11:48:36 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux [Description] We've identified a constant high (~90%) system time load at the host level when a VCPU in a KVM guest remains or switches/resumes in/from halt/idle state in a constant frequency, usually for a slightly smaller time than the default polling period. The halt polling mechanism has the intention to reduce latency in the cases on which the guest is quickly resumed saving a call to the scheduler. We've performed some testing by adjusting the /sys/module/kvm/parameters/halt_poll_ns value which defines the max time that should be spend polling before calling the scheduler to allow it to run other tasks (which defaults to 40 ns in Ubuntu). With the default value the tests shows that the load remains nearly on 90% on a VCPU that has a single task in the run queue. We've also tested altering the halt_poll_ns value to 20 ns and the results seems to drop the system time usage from 90% to ~25%. root@porygon:/home/ubuntu# echo 20 > /sys/module/kvm/parameters/halt_poll_ns root@porygon:/home/ubuntu# mpstat 1 -P 6 5 Linux 4.4.0-112-generic (porygon) 01/24/2018 _x86_64_(64 CPU) 02:06:08 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle 02:06:09 PM6 0.00 0.00 4.85 0.000.000.000.00 16.50 0.00 78.64 [...] Average: 6 0.00 0.00 4.26 0.000.000.000.00 17.83 0.00 77.91 root@porygon:/home/ubuntu# echo 40 > /sys/module/kvm/parameters/halt_poll_ns root@porygon:/home/ubuntu# mpstat 1 -P 6 5 Linux 4.4.0-112-generic (porygon) 01/24/2018 _x86_64_(64 CPU) 02:06:20 PM CPU %usr %nice %sys %iowait %irq %soft %steal %guest %gnice %idle 02:06:21 PM6 0.00 0.00 87.13 0.000.000.000.00 11.88 0.000.99 [...] Average: 6 0.00 0.00 89.59 0.000.000.000.008.45 0.001.96 [Reproducer] 1) Configure a KVM guest with a single pinned VCPU. 2) Run the following program (http://pastebin.ubuntu.com/25731919/) at the KVM guest. $ gcc test.c -lpthread -o test && ./test 250 0 3) Run mpstat at the host on the pinned CPU and compare the stats $ sudo mpstat 1 -P 6 5 [Fix] Change the halt polling max time to half of the current value. In some fio benchmarks, halt_poll_ns=40 caused CPU utilization to increase heavily even in cases where the performance improvement was small. In particular, bandwidth divided by CPU usage was as much as 60% lower. To some extent this is the expected effect of the patch, and the additional CPU utilization is only visible when running the benchmarks. However, halving the threshold also halves the extra CPU utilization (from +30-130% to +20-70%) and has no negative effect on performance. Signed-off-by: Paolo Bonzini * https://github.com/torvalds/linux/commit/b401ee0b85a53e89739ff68a5b1a0667d664afc9 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/zesty/+source/linux/+bug/1724614/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887213] Re: Touchpad stopped working after upgrade: 18.04 => 20.04
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887213 Title: Touchpad stopped working after upgrade: 18.04 => 20.04 Status in linux package in Ubuntu: Incomplete Bug description: > Laptop model directly from the sticker of the computer. Lenovo T450 ThinkPad > Manufacturer of the Touchpad. > When the symptom first appeared. Right after 18.04 => 20.04 upgrade. Touchpad never worked after upgrade. Nor movements, neither clicks. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: cyga 2740 F pulseaudio /dev/snd/controlC0: cyga 2740 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jul 11 13:36:53 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=d66c9dac-9065-401a-8f9a-3f208be7d2e6 InstallationDate: Installed on 2017-06-07 (1129 days ago) InstallationMedia: Ubuntu 16.04.2 LTS "Xenial Xerus" - Release amd64 (20170215.2) MachineType: LENOVO 20BV0005US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=/dev/mapper/ubuntu--vg-root ro cgroup_enable=memory swapaccount=1 acpi=force irqpoll quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-27 (13 days ago) dmi.bios.date: 07/08/2015 dmi.bios.vendor: LENOVO dmi.bios.version: JBET51WW (1.16 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BV0005US dmi.board.vendor: LENOVO dmi.board.version: SDK0E50510 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrJBET51WW(1.16):bd07/08/2015:svnLENOVO:pn20BV0005US:pvrThinkPadT450:rvnLENOVO:rn20BV0005US:rvrSDK0E50510WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad T450 dmi.product.name: 20BV0005US dmi.product.sku: LENOVO_MT_20BV_BU_Think_FM_ThinkPad T450 dmi.product.version: ThinkPad T450 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800873] Re: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command-line
** No longer affects: makedumpfile (Ubuntu Trusty) ** Changed in: makedumpfile (Ubuntu Xenial) Status: Confirmed => Won't Fix ** No longer affects: makedumpfile (Ubuntu Cosmic) ** No longer affects: makedumpfile (Ubuntu Disco) ** Also affects: makedumpfile (Ubuntu Groovy) Importance: Low Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed ** Also affects: makedumpfile (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: makedumpfile (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: makedumpfile (Ubuntu Eoan) Status: New => Confirmed ** Changed in: makedumpfile (Ubuntu Focal) Status: New => Confirmed ** Changed in: makedumpfile (Ubuntu Eoan) Importance: Undecided => Low ** Changed in: makedumpfile (Ubuntu Focal) Importance: Undecided => Low ** Changed in: makedumpfile (Ubuntu Eoan) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) ** Changed in: makedumpfile (Ubuntu Focal) Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1800873 Title: Add KDUMP_CMDLINE_REMOVE option to remove portions of kernel command- line Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Bug description: Currently kdump has an useful option to append parameters to the kdump kernel command-line, "KDUMP_CMDLINE_APPEND". Would be useful to have a reciprocal option which users could use to remove parameters without needing to rewrite the whole line. The option name proposed here is KDUMP_CMDLINE_REMOVE, which would tentatively "sed"-out the options from the kernel command-line before appending the new ones from KDUMP_CMDLINE_APPEND. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800873/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1800562] Re: Remove obsolete "nousb" option in kdump command-line for newer kernels
** No longer affects: makedumpfile (Ubuntu Cosmic)
** No longer affects: makedumpfile (Ubuntu Disco)
** Also affects: makedumpfile (Ubuntu Focal)
Importance: Undecided
Status: New
** Also affects: makedumpfile (Ubuntu Groovy)
Importance: High
Assignee: Guilherme G. Piccoli (gpiccoli)
Status: In Progress
** Changed in: makedumpfile (Ubuntu Focal)
Status: New => Confirmed
** Changed in: makedumpfile (Ubuntu Eoan)
Status: In Progress => Confirmed
** Changed in: makedumpfile (Ubuntu Groovy)
Status: In Progress => Confirmed
** Changed in: makedumpfile (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: makedumpfile (Ubuntu Groovy)
Importance: High => Medium
** Changed in: makedumpfile (Ubuntu Eoan)
Importance: High => Medium
** Changed in: makedumpfile (Ubuntu Bionic)
Importance: High => Medium
** Changed in: makedumpfile (Ubuntu Xenial)
Importance: High => Medium
** Changed in: makedumpfile (Ubuntu Focal)
Assignee: (unassigned) => Guilherme G. Piccoli (gpiccoli)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to makedumpfile in Ubuntu.
https://bugs.launchpad.net/bugs/1800562
Title:
Remove obsolete "nousb" option in kdump command-line for newer kernels
Status in makedumpfile package in Ubuntu:
Confirmed
Status in makedumpfile source package in Xenial:
Won't Fix
Status in makedumpfile source package in Bionic:
Confirmed
Status in makedumpfile source package in Eoan:
Confirmed
Status in makedumpfile source package in Focal:
Confirmed
Status in makedumpfile source package in Groovy:
Confirmed
Bug description:
[Impact]
* Kdump command-line include an obsolete "nousb" parameter by default, which
can cause a misimpression: users will think they are not booting with USB, but
they are.
* Since kernel v4.5, the correct parameter to disable USB subsystem
initialization is "usbcore.nousb" always (instead of "nousb" in case
the subsystem is built-in). This was changed by commit 097a9ea0e48
("usb: make "nousb" a clear module parameter").
* USB may be pretty essential in case for example kdump users need to
decrypt a disk under LUKS, and there's only an USB keyboard connected
to the system. Given the option is innocuous since Bionic, we should
just drop it to prevent confusion.
[Test Case]
1) Deploy a Disco VM e.g. with uvt-kvm
2) Install the kdump-tools package
3) Run `kdump-config test`and check for the 'nousb' parameter:
$ kdump-config test
...
kexec command to be used:
/sbin/kexec -p --command-line="BOOT_IMAGE=/boot/vmlinuz-4.15.0-45-generic
root=LABEL=cloudimg-rootfs ro console=tty1 console=ttyS0 nr_cpus=1
systemd.unit=kdump-tools.service irqpoll nousb ata_piix.prefer_ms_hyperv=0"
/var/lib/kdump/vmlinuz
[Regression Potential]
The regression potential is extremely low, since the "nousb" parameter
is not used since Bionic although is there. Any bugs we would have by
changing this are still valid by not removing the option - the
semantics with or without "nosub" is the same since from Bionic.
NOTICE we won't change Xenial, it can use kernel 4.4 which indeed
disables USB by taking the "nousb" parameter.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1800562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884981] Re: The touchpad soesn't work at all
Ok, possible to attach full dmesg with mainline kernel? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) 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: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851663] Re: Consistent autopkgtest failures on ppc64el/s390x
** No longer affects: makedumpfile (Ubuntu Disco) ** Also affects: makedumpfile (Ubuntu Groovy) Importance: Medium Assignee: Thadeu Lima de Souza Cascardo (cascardo) Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1851663 Title: Consistent autopkgtest failures on ppc64el/s390x Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Confirmed Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Bug description: Recently autopkgtest started to consistently fail in ppc64el / s390x. When testing manually, the kernel dump is collected and all works fine. By discussing with the package maintainer (Cascardo), it seems it started after a change in the instance type of the tests, to m1.large. This seems either a problem in the test infrastructure itself or a likely a "timing" problem in the test (i.e., requiring some pause or delay that is not currently enough). This demands investigation because those failures delay the package release for all arches, usually those releases contain important fixes. Also, the recurrent "workaround" is to mark the tests as "force- badtest" in ubuntu-hints for the 2 arches, which is in practice skipping the test, so those 2 arches are getting releases untested by the automatic infrastructure. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1851663/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878726] Re: Live USB Installer not working Samsung Notebook 9 Pro 15"
If the USB has enough storage, would it be possible for you to do a kernel bisection? First, find the last -rc kernel works and the first -rc kernel doesn’t work from http://kernel.ubuntu.com/~kernel-ppa/mainline/ Then, $ sudo apt build-dep linux $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git $ cd linux $ git bisect start $ git bisect good $(the working version you found) $ git bisect bad $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it still have the same issue, $ git bisect bad Otherwise, $ git bisect good Repeat to "make -j`nproc` deb-pkg" until you find the offending commit. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878726 Title: Live USB Installer not working Samsung Notebook 9 Pro 15" Status in linux package in Ubuntu: Incomplete Bug description: Live USB made from ubuntu-20.04-desktop-amd64 fails to boot. System hangs with watchdog: BUG: soft lockup - CPU# and rcu: INFO: rcu_sched self-detected stall on CPU. System specs: Intel(R) i7-7500U running AMD discrete graphics Have tested the Live USB on other systems with no problems, appears to be hardware related with the Samsung Notebook 9 Pro and other systems (Dell, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1749961] Re: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Confirmed ** Changed in: linux (Ubuntu Xenial) Status: In Progress => 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/1749961 Title: xhci_hcd: TRB DMA errors reported with ASMedia ASM1142 USB 3.1 Controller Status in linux package in Ubuntu: In Progress Status in linux source package in Trusty: Won't Fix Status in linux source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Focal: Confirmed Status in linux package in Debian: Confirmed Bug description: It was observed that while trying to use a 4K USB webcam connected to USB port provided by ASMedia ASM1142 USB 3.1 Controller, the webcam does not work and kernel log shows the following messages: [431.928016] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928021] xhci_hcd :12:00.0: Looking for event-dma 003f3330e020 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928024] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928026] xhci_hcd :12:00.0: Looking for event-dma 003f3330e030 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928027] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 [431.928029] xhci_hcd :12:00.0: Looking for event-dma 003f3330e050 trb-start 003f3330e000 trb-end 003f3330e000 seg-start 003f3330e000 seg-end 003f3330eff0 [431.928386] xhci_hcd :12:00.0: ERROR Transfer event TRB DMA ptr not part of current TD ep_index 2 comp_code 13 A similar issue was already reported on Launchpad: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1667750 The fix to this issue seems to be the following patch: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a109 Tests in our scenario with this patch proved still broken. Our next approach is to modify the patch a bit and re-test. This LP will be used to document our progress in the investigation. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1749961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working 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 1816743] Re: Add systemd's kdump service command-line regardless if user provides or not KDUMP_CMDLINE_APPEND
** Changed in: makedumpfile (Ubuntu Xenial) Status: Confirmed => Won't Fix ** No longer affects: makedumpfile (Ubuntu Cosmic) ** No longer affects: makedumpfile (Ubuntu Disco) ** Also affects: makedumpfile (Ubuntu Groovy) Importance: Low Assignee: Guilherme G. Piccoli (gpiccoli) Status: Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to makedumpfile in Ubuntu. https://bugs.launchpad.net/bugs/1816743 Title: Add systemd's kdump service command-line regardless if user provides or not KDUMP_CMDLINE_APPEND Status in makedumpfile package in Ubuntu: Confirmed Status in makedumpfile source package in Xenial: Won't Fix Status in makedumpfile source package in Bionic: Confirmed Status in makedumpfile source package in Eoan: Confirmed Status in makedumpfile source package in Focal: Confirmed Status in makedumpfile source package in Groovy: Confirmed Bug description: Since Xenial release, Ubuntu relies on systemd as its init system - there's a kdump service to prevent some other services to unnecessarily start in kdump environment. Problem: if we add something to KDUMP_CMDLINE_APPEND, the entry for kdump service, "systemd.unit=kdump-tools.service" is removed from the command-line. The user manually needs to add that, and this seems highly prone to error. We propose here to decouple the "systemd.unit=kdump-tools.service" parameter from KDUMP_CMDLINE_APPEND, so if user wants really to remove this option, they should used KDUMP_CMDLINE instead. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/makedumpfile/+bug/1816743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1616193] Re: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0
** Changed in: linux (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1616193 Title: 3.13: libvirtd: page allocation failure: order:4, mode:0x1040d0 Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Bug description: [Impact] * libvirtd is no longer able to open the vhost_net device. This causes the guest VM to hang. This happens if memory becomes fragmented to the point where vhost_net_open is not able to successfully kmalloc. * Gratuitous stack trace. libvirtd: page allocation failure: order:4, mode:0x1040d0 CPU: 14 PID: 82768 Comm: libvirtd Not tainted 3.13.0-85-generic #129-Ubuntu Hardware name: Dell Inc. PowerEdge R730/0599V5, BIOS 1.5.4 10/002/2015 88003b419990 8172b6a7 001040d0 88003b419a18 811580eb 88187fffce48 88003b4199b8 8115abd6 88003b4199e8 0286 Call Trace: [] dump_stack+0x64/0x82 [] warn_alloc_failed+0xeb/0x140 [] ? drain_local_pages+0x16/0x20 [] __alloc_pages_nodemask+0x980/0xb90 [] alloc_pages_current+0xa3/0x160 [] __get_free_pages+0xe/0x50 [] kmalloc_order_trace+0x2e/0xc0 [] vhost_net_open+0x29/0x1b0 [vhost_net] [] misc_open+0xb3/0x170 [] chrdev_open+0x9f/0x1d0 [] do_dentry_open+0x233/0x2e0 [] ? cdev_put+0x30/0x30 [] vfs_open+0x49/0x50 [] do_last+0x562/0x1370 [] path_openat+0xbb/0x670 [] do_filp_open+0x3a/0x90 [] ? __alloc_fd+0xa7/0x130 [] do_sys_open+0x129/0x2a0 [] SyS_open+0x1e/0x20 [] system_call_fastpath+0x1a/0x1f * justification: because cloud. * The patches fix this issue by allowing vhost_net_open to use vmalloc when kmalloc fails to find a sufficient page size. [Test Case] * Fragment Kernel memory. Write to Nic from within a kvm guest that uses a virtio nic. [Regression Potential] * Fix was implemented upstream in 3.15, and still exists. * The fix is fairly straightfoward given the stack trace and the upstream fix. * The fix is hard to verify, as it requires significant memory fragmentation, and an over-active guest. The users machine that was experiencing this has worked around this by removing VM's from the compute host, and using vfs.cache.pressure=600. [Other Info] * https://lkml.org/lkml/2013/1/23/492 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=23cc5a991c7a9fb7e6d6550e65cee4f4173111c5 * http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d04257b07f2362d4eb550952d5bf5f4241a8046d * I'm going on vacation, and Eric Desrochers will be following up on this in my absence. This is also the reason for submitting before receiving verification. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1616193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
After applying the latest update to Firefox and pulseaudio, the sound is working normally for now! Thank you. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working 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 : -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
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
I've removed the linux projects from this bug at it's been determined to not be a kernel issue (see comment 47 for a good summary). ** No longer affects: linux-signed (Ubuntu) ** No longer affects: linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1861941 Title: bcache by-uuid links disappear after mounting bcache0 Status in bcache-tools package in Ubuntu: Triaged Status in systemd package in Ubuntu: Fix Released Status in bcache-tools source package in Bionic: New Status in linux source package in Bionic: New Status in linux-signed source package in Bionic: New Status in systemd source package in Bionic: New Status in bcache-tools source package in Focal: Confirmed Status in linux source package in Focal: Invalid Status in linux-signed source package in Focal: Confirmed Status in systemd source package in Focal: Confirmed Status in bcache-tools source package in Groovy: Triaged Status in linux source package in Groovy: Incomplete Status in linux-signed source package in Groovy: Confirmed Status in systemd source package in Groovy: Fix Released Bug description: 1. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 2. root@ubuntu:~# lsb_release -rd Description: Ubuntu Focal Fossa (development branch) Release: 20.04 root@ubuntu:~# apt-cache policy linux-image-virtual linux-image-virtual: Installed: 5.4.0.12.15 Candidate: 5.4.0.12.15 Version table: *** 5.4.0.12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status root@ubuntu:~# apt-cache policy linux-image-5.4.0-12-generic linux-image-5.4.0-12-generic: Installed: 5.4.0-12.15 Candidate: 5.4.0-12.15 Version table: *** 5.4.0-12.15 500 500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status 3. mount /dev/bcache0 && ls -al /dev/bcache/by-uuid/ + ls -al /dev/bcache/by-uuid/ total 0 drwxr-xr-x 2 root root 60 Feb 4 23:31 . drwxr-xr-x 3 root root 60 Feb 4 23:31 .. lrwxrwxrwx 1 root root 13 Feb 4 23:31 abdfd1f6-44ce-4266-91db-24667b9ae51a -> ../../bcache0 4. root@ubuntu:~# ls -al /dev/bcache/by-uuid ls: cannot access '/dev/bcache/by-uuid': No such file or directory ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Tue Feb 4 23:31:52 2020 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bcache-tools/+bug/1861941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887573] [NEW] Eoan update: upstream stable patchset 2020-07-14
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2020-07-14 Ported from the following upstream stable releases: v4.19.131, v.5.4.50 from git://git.kernel.org/ block/bio-integrity: don't free 'buf' if bio_integrity_add_page() failed mtd: rawnand: marvell: Fix the condition on a return code net: sched: export __netdev_watchdog_up() fix a braino in "sparc32: fix register window handling in genregs32_[gs]et()" ALSA: hda/realtek - Enable micmute LED on and HP system ibmveth: Fix max MTU limit mld: fix memory leak in ipv6_mc_destroy_dev() net: bridge: enfore alignment for ethernet address net: fix memleak in register_netdevice() net: increment xmit_recursion level in dev_direct_xmit() net: usb: ax88179_178a: fix packet alignment padding rocker: fix incorrect error handling in dma_rings_init rxrpc: Fix notification call on completion of discarded calls sctp: Don't advertise IPv4 addresses if ipv6only is set on the socket tcp: don't ignore ECN CWR on pure ACK tcp: grow window for OOO packets only for SACK flows tg3: driver sleeps indefinitely when EEH errors exceed eeh_max_freezes ip6_gre: fix use-after-free in ip6gre_tunnel_lookup() net: phy: Check harder for errors in get_phy_id() ip_tunnel: fix use-after-free in ip_tunnel_lookup() sch_cake: don't try to reallocate or unshare skb unconditionally sch_cake: fix a few style nits tcp_cubic: fix spurious HYSTART_DELAY exit upon drop in min RTT sch_cake: don't call diffserv parsing code when it is not needed net: Fix the arp error in some cases net: Do not clear the sock TX queue in sk_set_socket() net: core: reduce recursion limit value USB: ohci-sm501: Add missed iounmap() in remove usb: dwc2: Postponed gadget registration to the udc class driver usb: add USB_QUIRK_DELAY_INIT for Logitech C922 USB: ehci: reopen solution for Synopsys HC bug usb: host: xhci-mtk: avoid runtime suspend when removing hcd xhci: Poll for U0 after disabling USB2 LPM usb: host: ehci-exynos: Fix error check in exynos_ehci_probe() usb: typec: tcpci_rt1711h: avoid screaming irq causing boot hangs ALSA: usb-audio: add quirk for Denon DCD-1500RE ALSA: usb-audio: add quirk for Samsung USBC Headset (AKG) ALSA: usb-audio: Fix OOB access of mixer element list scsi: zfcp: Fix panic on ERP timeout for previously dismissed ERP action xhci: Fix incorrect EP_STATE_MASK xhci: Fix enumeration issue when setting max packet size for FS devices. xhci: Return if xHCI doesn't support LPM cdc-acm: Add DISABLE_ECHO quirk for Microchip/SMSC chip loop: replace kill_bdev with invalidate_bdev IB/mad: Fix use after free when destroying MAD agent cifs/smb3: Fix data inconsistent when punch hole cifs/smb3: Fix data inconsistent when zero file range xfrm: Fix double ESP trailer insertion in IPsec crypto offload. ASoC: q6asm: handle EOS correctly efi/esrt: Fix reference count leak in esre_create_sysfs_entry. regualtor: pfuze100: correct sw1a/sw2 on pfuze3000 ASoC: fsl_ssi: Fix bclk calculation for mono channel ARM: dts: Fix duovero smsc interrupt for suspend x86/resctrl: Fix a NULL vs IS_ERR() static checker warning in rdt_cdp_peer_get() regmap: Fix memory leak from regmap_register_patch ARM: dts: NSP: Correct FA2 mailbox node rxrpc: Fix handling of rwind from an ACK packet RDMA/qedr: Fix KASAN: use-after-free in ucma_event_handler+0x532 RDMA/cma: Protect bind_list and listen_list while finding matching cm id ASoC: rockchip: Fix a reference count leak. RDMA/mad: Fix possible memory leak in ib_mad_post_receive_mads() net: qed: fix left elements count calculation net: qed: fix NVMe login fails over VFs net: qed: fix excessive QM ILT lines consumption cxgb4: move handling L2T ARP failures to caller ARM: imx5: add missing put_device() call in imx_suspend_alloc_ocram() usb: gadget: udc: Potential Oops in error handling code netfilter: ipset: fix unaligned atomic access net: bcmgenet: use hardware padding of runt frames i2c: fsi: Fix the port number field in status register i2c: core: check returned size of emulated smbus block read sched/deadline: Initialize ->dl_boosted sched/core: Fix PI boosting between RT and DEADLINE tasks sata_rcar: handle pm_runtime_get_sync failure cases ata/libata: Fix usage of page address by page_address in ata_scsi_mode_select_xlat function drm/amd/display: Use kfree() to free rgb_user in calculate_user_regamma_ramp() riscv/atomic: Fix sign extension for RV64I hwrng: ks-sa - Fix runtime PM imbalance on error ibmvnic: Harden device login requests net: alx: fix race condition in alx_remove s390/ptrace: fix
[Kernel-packages] [Bug 1885033] Re: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04)
Could you please explain what is missing for this bug to be considered complete? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885033 Title: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04) Status in linux package in Ubuntu: Incomplete Bug description: The touchpad switch, Fn-F6, does not work for me. It does work on Windows 10 (dual boot) The touchpad works well, but I can only set the option in System Conguration. See launchpad answer : https://answers.launchpad.net/ubuntu/+question/691511 Kubuntu 20.04 Lenovo IdeaPad L340-15IRH - Type 81LK --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yann 1350 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-20 (125 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81LK NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=0ac30ea3-dc16-4323-a1a3-acea99fa90b5 ro quiet splash resume=/dev/nvme0n1p6 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-14 (41 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN29WW 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: IdeaPad L340-15IRH Gaming dmi.modalias: dmi:bvnLENOVO:bvrBGCN29WW:bd02/10/2020:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555338] Re: Linux netfilter IPT_SO_SET_REPLACE memory corruption
** Changed in: linux-goldfish (Ubuntu Xenial) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-goldfish in Ubuntu. https://bugs.launchpad.net/bugs/1555338 Title: Linux netfilter IPT_SO_SET_REPLACE memory corruption Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: New Status in linux-goldfish package in Ubuntu: New Status in linux-keystone package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: New Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-keystone source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-keystone source package in Trusty: Fix Released Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-flo source package in Vivid: Won't Fix Status in linux-goldfish source package in Vivid: New Status in linux-keystone source package in Vivid: Invalid Status in linux-lts-quantal source package in Vivid: Won't Fix Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily: Invalid Status in linux-flo source package in Wily: New Status in linux-goldfish source package in Wily: New Status in linux-keystone source package in Wily: Invalid Status in linux-lts-quantal source package in Wily: Invalid Status in linux-lts-raring source package in Wily: Invalid
[Kernel-packages] [Bug 1887564] [NEW] Laptop XPS13 can't sleep Ubuntu 16.04.6 LTS when USB3 device is/was attached.
Public bug reported: (Ubuntu 4.4.0-185.215-generic 4.4.224) If I plug a USB3 device on the USB3 port then I can't send the laptop to sleep. (this happens with audio interface UMC404HD and Gbit Ethernet Adapter Trendnet) Instead it cancels the sleep process: Jul 13 10:24:22 xps kernel: [318785.373269] video LNXVIDEO:00: Restoring backlight state Jul 13 10:24:24 xps kernel: [318785.375145] PM: Syncing filesystems ... done. Jul 13 10:24:24 xps kernel: [318785.424201] PM: Preparing system for sleep (freeze) Jul 13 10:24:24 xps kernel: [318785.424337] Freezing user space processes ... (elapsed 0.001 seconds) done. Jul 13 10:24:24 xps kernel: [318785.426132] Freezing remaining freezable tasks ... (elapsed 0.037 seconds) done. Jul 13 10:24:24 xps kernel: [318785.463699] PM: Suspending system (freeze) Jul 13 10:24:24 xps kernel: [318785.463701] Suspending console(s) (use no_console_suspend to debug) Jul 13 10:24:24 xps kernel: [318785.463921] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 13 10:24:24 xps kernel: [318785.463971] sd 0:0:0:0: [sda] Stopping disk Jul 13 10:24:24 xps kernel: [318786.150701] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -16 Jul 13 10:24:24 xps kernel: [318786.150716] PM: Device usb4 failed to suspend async: error -16 Jul 13 10:24:24 xps kernel: [318786.150831] PM: Some devices failed to suspend, or early wake event detected Jul 13 10:24:24 xps kernel: [318786.166836] sd 0:0:0:0: [sda] Starting disk Jul 13 10:24:24 xps kernel: [318786.254775] rtc_cmos 00:01: System wakeup disabled by ACPI Jul 13 10:24:24 xps kernel: [318786.490641] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 13 10:24:24 xps kernel: [318786.513275] ata1.00: configured for UDMA/133 Jul 13 10:24:24 xps kernel: [318786.942366] PM: resume of devices complete after 791.556 msecs Jul 13 10:24:24 xps kernel: [318786.942703] PM: Finishing wakeup. Jul 13 10:24:24 xps kernel: [318786.942706] Restarting tasks ... done. Jul 13 10:24:24 xps systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Jul 13 10:24:24 xps kernel: [318786.967694] video LNXVIDEO:00: Restoring backlight state ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "lspci-vnvn.log" https://bugs.launchpad.net/bugs/1887564/+attachment/5392686/+files/lspci-vnvn.log ** Description changed: - If I plug a USB3 device on the USB3 port then I can't send the laptop to sleep. + If I plug a USB3 device on the USB3 port then I can't send the laptop to sleep. (this happens with audio interface UMC404HD and Gbit Ethernet Adapter Trendnet) Instead it cancels the sleep process: Jul 13 10:24:22 xps kernel: [318785.373269] video LNXVIDEO:00: Restoring backlight state Jul 13 10:24:24 xps kernel: [318785.375145] PM: Syncing filesystems ... done. Jul 13 10:24:24 xps kernel: [318785.424201] PM: Preparing system for sleep (freeze) Jul 13 10:24:24 xps kernel: [318785.424337] Freezing user space processes ... (elapsed 0.001 seconds) done. Jul 13 10:24:24 xps kernel: [318785.426132] Freezing remaining freezable tasks ... (elapsed 0.037 seconds) done. Jul 13 10:24:24 xps kernel: [318785.463699] PM: Suspending system (freeze) Jul 13 10:24:24 xps kernel: [318785.463701] Suspending console(s) (use no_console_suspend to debug) Jul 13 10:24:24 xps kernel: [318785.463921] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 13 10:24:24 xps kernel: [318785.463971] sd 0:0:0:0: [sda] Stopping disk Jul 13 10:24:24 xps kernel: [318786.150701] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -16 Jul 13 10:24:24 xps kernel: [318786.150716] PM: Device usb4 failed to suspend async: error -16 Jul 13 10:24:24 xps kernel: [318786.150831] PM: Some devices failed to suspend, or early wake event detected Jul 13 10:24:24 xps kernel: [318786.166836] sd 0:0:0:0: [sda] Starting disk Jul 13 10:24:24 xps kernel: [318786.254775] rtc_cmos 00:01: System wakeup disabled by ACPI Jul 13 10:24:24 xps kernel: [318786.490641] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 13 10:24:24 xps kernel: [318786.513275] ata1.00: configured for UDMA/133 Jul 13 10:24:24 xps kernel: [318786.942366] PM: resume of devices complete after 791.556 msecs Jul 13 10:24:24 xps kernel: [318786.942703] PM: Finishing wakeup. Jul 13 10:24:24 xps kernel: [318786.942706] Restarting tasks ... done. Jul 13 10:24:24 xps systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Jul 13 10:24:24 xps kernel: [318786.967694] video LNXVIDEO:00: Restoring backlight state ** Description changed: + (Ubuntu 4.4.0-185.215-generic 4.4.224) If I plug a USB3 device on the USB3 port then I can't send the laptop to sleep. (this happens with audio interface UMC404HD and Gbit Ethernet Adapter Trendnet) Instead it cancels the sleep process: Jul 13 10:24:22 xps kernel: [318785.373269] video LNXVIDEO:00: Restoring backlight state Jul 13
[Kernel-packages] [Bug 1885496] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu
Hi, Could you please attach a screenshot of the slider you are referring to? I believe you are confusing the slider's purpose. The slider is to make your bluetooth computer visible to be able to pair new devices, it does not disconnect existing devices. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete ** Changed in: bluez (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1885496 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu Status in bluez package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: Current behavior: In gnome-control-center I see the Bluetooth slider is set to Off and the status shows "Bluetooth Turned Off". My Bluetooth audio receiver which had previously been paired can still control VLC, or any other compatible media player with a Pause/Play button. If no compatible app is running then an error icon appears.[0] Expected behavior: when gnome-control-center Bluetooth shows Disabled, then no bluetooth device should be able to communicate with the computer. Security: This is way out of my wheelhouse, but if this goes beyond my use case, could this have security implications? Just the fact that the bluetooth subsystem is functional when the UI says it is not, seems like a bad sign, correct? EDIT: as a next step, when I enabled Bluetooth in gnome-control- center I see the device's status as "Disconnected" and the device does not appear as a possible sound output device in Sound settings. In this Bluetooth enabled state, the pause/play button still works. When I disable all Bluetooth, the pause/play button still works. EDIT2: I'm not sure what the gnome-control-center Bluetooth On/Off slider is supposed to do, but while gnome-control-center Bluetooth shows disabled the service is still running. $ service bluetooth status bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago Docs: man:bluetoothd(8) Main PID: 935 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38343) Memory: 3.0M CGroup: /system.slice/bluetooth.service └─935 /usr/lib/bluetooth/bluetoothd Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53 Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service. Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 initialized Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/sbc Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/sbc Jun 26 20:55:06 nyuk bluetoothd[935]: /org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready Jun 26 20:56:12 nyuk bluetoothd[935]: /org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through rfkill (0x12) Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through rfkill (0x12) [0] https://i.imgur.com/e2nM7hA.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 21:11:45 2020 InstallationDate: Installed on 2020-06-17 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055 dmi.board.asset.tag: �=\� dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation
[Kernel-packages] [Bug 1887564] 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 1887564 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/1887564 Title: Laptop XPS13 can't sleep Ubuntu 16.04.6 LTS when USB3 device is/was attached. Status in linux package in Ubuntu: Incomplete Bug description: (Ubuntu 4.4.0-185.215-generic 4.4.224) If I plug a USB3 device on the USB3 port then I can't send the laptop to sleep. (this happens with audio interface UMC404HD and Gbit Ethernet Adapter Trendnet) Instead it cancels the sleep process: Jul 13 10:24:22 xps kernel: [318785.373269] video LNXVIDEO:00: Restoring backlight state Jul 13 10:24:24 xps kernel: [318785.375145] PM: Syncing filesystems ... done. Jul 13 10:24:24 xps kernel: [318785.424201] PM: Preparing system for sleep (freeze) Jul 13 10:24:24 xps kernel: [318785.424337] Freezing user space processes ... (elapsed 0.001 seconds) done. Jul 13 10:24:24 xps kernel: [318785.426132] Freezing remaining freezable tasks ... (elapsed 0.037 seconds) done. Jul 13 10:24:24 xps kernel: [318785.463699] PM: Suspending system (freeze) Jul 13 10:24:24 xps kernel: [318785.463701] Suspending console(s) (use no_console_suspend to debug) Jul 13 10:24:24 xps kernel: [318785.463921] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 13 10:24:24 xps kernel: [318785.463971] sd 0:0:0:0: [sda] Stopping disk Jul 13 10:24:24 xps kernel: [318786.150701] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -16 Jul 13 10:24:24 xps kernel: [318786.150716] PM: Device usb4 failed to suspend async: error -16 Jul 13 10:24:24 xps kernel: [318786.150831] PM: Some devices failed to suspend, or early wake event detected Jul 13 10:24:24 xps kernel: [318786.166836] sd 0:0:0:0: [sda] Starting disk Jul 13 10:24:24 xps kernel: [318786.254775] rtc_cmos 00:01: System wakeup disabled by ACPI Jul 13 10:24:24 xps kernel: [318786.490641] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 13 10:24:24 xps kernel: [318786.513275] ata1.00: configured for UDMA/133 Jul 13 10:24:24 xps kernel: [318786.942366] PM: resume of devices complete after 791.556 msecs Jul 13 10:24:24 xps kernel: [318786.942703] PM: Finishing wakeup. Jul 13 10:24:24 xps kernel: [318786.942706] Restarting tasks ... done. Jul 13 10:24:24 xps systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Jul 13 10:24:24 xps kernel: [318786.967694] video LNXVIDEO:00: Restoring backlight state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881109] Re: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors.
I'm wondering if it would make sense (on top of comment #7: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881109/comments/7) to test this again with an updated kernel (that got patched to fix DIF and DIX), where the fix virtually updates the scsi/zfcp driver to the kernel 5.8 level? I'm having this bug in mind: LP 1887124 "[UBUNTU 20.04] DIF and DIX support in zfcp (s390x) is broken and the kernel crashes unconditionally" https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887124 A patched kernel to test is referenced here: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1887124/comments/1 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881109 Title: [Ubuntu 20.04] LPAR crashes in block layer under high stress. Might be triggered by scsi errors. Status in Ubuntu on IBM z Systems: New Status in linux package in Ubuntu: New Bug description: We can reproduce a crash in the block layer with lots of stress on lots of SCSI disks (on an XIV storage server). We seem to have several scsi stalls in the logs/errors (needs to be analyzed further) but in the end we do crash with this this calltrace. [20832.901147] Failing address: 7fe00dea8000 TEID: 7fe00dea8403 [20832.901159] Fault in home space mode while using kernel ASCE. [20832.901171] AS:01d3cccf400b R2:03fd0020800b R3:03fd0020c007 S:03fc1cc78800 P:0400 [20832.901264] Oops: 0011 ilc:2 [#1] SMP [20832.901280] Modules linked in: vhost_net vhost macvtap macvlan tap xfs xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 nf_tables nfnetlink ip6table_filter ip6_tables iptable_filter bpfilter bridge aufs overlay dm_service_time dm_multipath scsi_dh_rdac scsi_dh_emc scsi_dh_alua s390_trng chsc_sch eadm_sch vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio 8021q garp mrp stp llc sch_fq_codel drm drm_panel_orientation_quirks i2c_core ip_tables x_tables btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear dm_mirror dm_region_hash dm_log qeth_l2 pkey zcrypt crc32_vx_s390 ghash_s390 prng aes_s390 des_s390 libdes sha3_512_s390 sha3_256_s390 sha512_s390 sha256_s390 sha1_s390 sha_common zfcp scsi_transport_fc dasd_eckd_mod dasd_mod qeth qdio ccwgroup [20832.901516] CPU: 29 PID: 389709 Comm: CPU 0/KVM Kdump: loaded Not tainted 5.4.0-29-generic #33-Ubuntu [20832.901530] Hardware name: IBM 8561 T01 708 (LPAR) [20832.901542] Krnl PSW : 0404e0018000 01d3cbd559be (try_to_wake_up+0x4e/0x700) [20832.901575]R:0 T:1 IO:0 EX:0 Key:0 M:1 W:0 P:0 AS:3 CC:2 PM:0 RI:0 EA:3 [20832.901744] Krnl GPRS: 03fc917cd988 7fe0 7fe0001e 0003 [20832.901750] 004c 040003fd005a4600 0003 [20832.901753]0003 7fe00dea8454 7fe00dea7b00 [20832.901754]03f44bd9b300 01d3cc587088 7fe0021c7ae0 7fe0021c7a60 [20832.901767] Krnl Code: 01d3cbd559b2: 41902954la %r9,2388(%r2) 01d3cbd559b6: 582003acl %r2,940 #01d3cbd559ba: a718lhi %r1,0 >01d3cbd559be: ba129000cs %r1,%r2,0(%r9) 01d3cbd559c2: a77401c9brc 7,01d3cbd55d54 01d3cbd559c6: e310b0080004lg %r1,8(%r11) 01d3cbd559cc: b9800018ngr %r1,%r8 01d3cbd559d0: a774001fbrc 7,01d3cbd55a0e [20832.901784] Call Trace: [20832.901816] ([<01d3cc57e0ac>] cleanup_critical+0x0/0x474) [20832.901823] [<01d3cc1d16ba>] rq_qos_wake_function+0x8a/0xa0 [20832.901827] [<01d3cbd74bde>] __wake_up_common+0x9e/0x1b0 [20832.901829] [<01d3cbd750e4>] __wake_up_common_lock+0x94/0xe0 [20832.901830] [<01d3cbd7515a>] __wake_up+0x2a/0x40 [20832.901835] [<01d3cc1e8640>] wbt_done+0x90/0xe0 [20832.901837] [<01d3cc1d17be>] __rq_qos_done+0x3e/0x60 [20832.901841] [<01d3cc1bd5b0>] blk_mq_free_request+0xe0/0x140 [20832.901848] [<01d3cc35fc60>] dm_softirq_done+0x140/0x230 [20832.901849] [<01d3cc1bbfbc>] blk_done_softirq+0xbc/0xe0 [20832.901850] [<01d3cc57e710>] __do_softirq+0x100/0x360 [20832.901853] [<01d3cbd2525e>] irq_exit+0x9e/0xc0 [20832.901856] [<01d3cbcb0b18>] do_IRQ+0x78/0xb0 [20832.901859] [<01d3cc57dc28>] ext_int_handler+0x128/0x12c [20832.901860] [<01d3cc57d306>] sie_exit+0x0/0x46 [20832.901866]
[Kernel-packages] [Bug 1885496] Re: Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu
Ok, actually the slider is in fact to disable bluetooth completely, please ignore my previous comment. ** Changed in: bluez (Ubuntu) Status: Incomplete => Confirmed ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1885496 Title: Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Current behavior: In gnome-control-center I see the Bluetooth slider is set to Off and the status shows "Bluetooth Turned Off". My Bluetooth audio receiver which had previously been paired can still control VLC, or any other compatible media player with a Pause/Play button. If no compatible app is running then an error icon appears.[0] Expected behavior: when gnome-control-center Bluetooth shows Disabled, then no bluetooth device should be able to communicate with the computer. Security: This is way out of my wheelhouse, but if this goes beyond my use case, could this have security implications? Just the fact that the bluetooth subsystem is functional when the UI says it is not, seems like a bad sign, correct? EDIT: as a next step, when I enabled Bluetooth in gnome-control- center I see the device's status as "Disconnected" and the device does not appear as a possible sound output device in Sound settings. In this Bluetooth enabled state, the pause/play button still works. When I disable all Bluetooth, the pause/play button still works. EDIT2: I'm not sure what the gnome-control-center Bluetooth On/Off slider is supposed to do, but while gnome-control-center Bluetooth shows disabled the service is still running. $ service bluetooth status bluetooth.service - Bluetooth service Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled) Active: active (running) since Fri 2020-06-26 10:09:48 PDT; 2 days ago Docs: man:bluetoothd(8) Main PID: 935 (bluetoothd) Status: "Running" Tasks: 1 (limit: 38343) Memory: 3.0M CGroup: /system.slice/bluetooth.service └─935 /usr/lib/bluetooth/bluetoothd Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth daemon 5.53 Jun 26 10:09:48 nyuk systemd[1]: Started Bluetooth service. Jun 26 10:09:48 nyuk bluetoothd[935]: Starting SDP server Jun 26 10:09:48 nyuk bluetoothd[935]: Bluetooth management interface 1.14 initialized Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSink/sbc Jun 26 10:12:17 nyuk bluetoothd[935]: Endpoint registered: sender=:1.94 path=/MediaEndpoint/A2DPSource/sbc Jun 26 20:55:06 nyuk bluetoothd[935]: /org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd0: fd(37) ready Jun 26 20:56:12 nyuk bluetoothd[935]: /org/bluez/hci0/dev_0B_26_75_03_C0_80/sep1/fd1: fd(37) ready Jun 26 21:23:45 nyuk bluetoothd[935]: Failed to set mode: Blocked through rfkill (0x12) Jun 28 20:58:41 nyuk bluetoothd[935]: Failed to set mode: Blocked through rfkill (0x12) [0] https://i.imgur.com/e2nM7hA.png ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: bluez 5.53-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-39.43-generic 5.4.41 Uname: Linux 5.4.0-39-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jun 28 21:11:45 2020 InstallationDate: Installed on 2020-06-17 (11 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) InterestingModules: rfcomm bnep btusb bluetooth Lsusb: Bus 002 Device 003: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive Bus 002 Device 002: ID 152d:0567 JMicron Technology Corp. / JMicron USA Technology Corp. JMS567 SATA 6Gb/s bridge Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 8087:0a2b Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcEnviron: PATH=(custom, no username) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=7d791ec0-a9ea-415e-b7ec-6260b85b55f7 ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/27/2016 dmi.bios.vendor: Intel Corp. dmi.bios.version: SYSKLi35.86A.0045.2016.0527.1055 dmi.board.asset.tag: �=\� dmi.board.name: NUC6i5SYB dmi.board.vendor: Intel corporation dmi.board.version: H81131-504 dmi.chassis.type: 3 dmi.modalias:
[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev
** Description changed: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - - Dell latitude 5758 i5-5200 - - Dell latitude 5759 i5-6200 + - Dell inspiron 5758 i5-5200 (dearest-team) + - Dell inspiron 5759 i5-6200 (unknown-wealth) It's unknown yet whether there are others affected by 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/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: Incomplete Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell inspiron 5758 i5-5200 (dearest-team) - Dell inspiron 5759 i5-6200 (unknown-wealth) It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887324] 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 1887324 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/1887324 Title: wifi not working Status in linux package in Ubuntu: Incomplete Bug description: install driver tl-wn725n okela but not connect with wifi by command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
Where can I check to see when this fix has been pushed out as part of an Ubuntu update? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] On the machine of Lenovo IdeaPad 5 15IIL05, the audio doesn't work, checking the dmesg, I found the audio driver fails to initialize because it fails on i915 audio codec probe. [Fix] backport 3 patches from mainline kernel, move the i915 audio codec init earlier. [Test Case] Boot the kernel with these 3 patches, check dmesg, there is no i915 audio codec probe error anymore, and audio driver initializes successfully, and input and output audio devices all work. [Regression Risk] Low, already tested these 3 patches on a couple of LENOVO dmic machines (cnl and cml machines), all work as well as before. On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 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-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions:
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Hello!!! I installed the kernel above. I restarted the system and put some media to play via, Spotify, Totem. They worked normal. But when I started some media on YouTube through Firefox, the sound disappeared again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working 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)
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Hello!!! I installed the kernel above. I restarted the system and put some media to play via, Spotify, Totem. They will work normal. But when I started some media on YouTube through Firefox, the sound disappeared again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working 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)
[Kernel-packages] [Bug 1882517] Re: touchpad not working at all
Thanks for your suggestions. Unfortunately, the system won't boot without acpi=off. This is why I appended it to the kernel-parameters in the first place. So I can't boot up without it and then run some command. I could run the command with the system booted up with acpi off though. Would you want to see that? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882517 Title: touchpad not working at all Status in linux package in Ubuntu: Incomplete Bug description: following the instructions here: https://wiki.ubuntu.com/DebuggingTouchpadDetection laptop model directly from sticker on the computer: P6685-MD61086 MSN30024751 manufacturer of the touchpad: not sure, /proc/bus/input/devices of my prior system listed the touchpad as: I: Bus=0018 Vendor=2808 Product=0101 Version=0100 (for further information see the link provided in the following section) when the symptom first appeared: It appeared on numerous live systems. I was seeking for help on ask ubuntu (https://askubuntu.com/questions/1245783/problems-with-touchpad-in-ubuntu-20-04-with-acpi-off), but didn't receive any. So I installed xubuntu 20.04 nevertheless and I am now working without touchpad using both mouse and keyboard as replacements. The installation failed with the 20.04 xubuntu stick (with some grub error message), so I used an 18.04 xubuntu stick which worked. Afterwards I upgraded the system which also included some trouble with grub but I could leave grub as it was so that the system is now mostly functional (apart from the touchpad and that shutdowns do not really work, but that's not too bad). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-33-generic 5.4.0-33.37 ProcVersionSignature: Ubuntu 5.4.0-33.37-generic 5.4.34 Uname: Linux 5.4.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: arne 1053 F pulseaudio /dev/snd/pcmC0D0c: arne 1053 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Mon Jun 8 13:13:51 2020 InstallationDate: Installed on 2020-06-07 (1 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: MEDION P6685 MD61086 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-33-generic root=UUID=414b4949-378b-420c-a99b-90ab65ee68c4 ro quiet splash acpi=off vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-33-generic N/A linux-backports-modules-5.4.0-33-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-07 (0 days ago) dmi.bios.date: 03/15/2018 dmi.bios.vendor: INSYDE Corp. dmi.bios.version: 207 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: F15KKR dmi.board.vendor: MEDION dmi.board.version: 1.0 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: MEDION dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnINSYDECorp.:bvr207:bd03/15/2018:svnMEDION:pnP6685MD61086:pvr1.0:rvnMEDION:rnF15KKR:rvr1.0:cvnMEDION:ct10:cvrChassisVersion: dmi.product.family: P6685 dmi.product.name: P6685 MD61086 dmi.product.sku: ML-210008 30024751 dmi.product.version: 1.0 dmi.sys.vendor: MEDION To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882517/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555338] Re: Linux netfilter IPT_SO_SET_REPLACE memory corruption
** Changed in: linux-flo (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: linux-mako (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: linux-flo (Ubuntu) Status: New => Won't Fix ** Changed in: linux-goldfish (Ubuntu) Status: New => Won't Fix ** Changed in: linux-mako (Ubuntu) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-goldfish in Ubuntu. https://bugs.launchpad.net/bugs/1555338 Title: Linux netfilter IPT_SO_SET_REPLACE memory corruption Status in linux package in Ubuntu: Fix Released Status in linux-armadaxp package in Ubuntu: Invalid Status in linux-flo package in Ubuntu: Won't Fix Status in linux-goldfish package in Ubuntu: Won't Fix Status in linux-keystone package in Ubuntu: Invalid Status in linux-lts-quantal package in Ubuntu: Invalid Status in linux-lts-raring package in Ubuntu: Invalid Status in linux-lts-saucy package in Ubuntu: Invalid Status in linux-lts-trusty package in Ubuntu: Invalid Status in linux-lts-utopic package in Ubuntu: Invalid Status in linux-lts-vivid package in Ubuntu: Invalid Status in linux-lts-wily package in Ubuntu: Invalid Status in linux-lts-xenial package in Ubuntu: Invalid Status in linux-mako package in Ubuntu: Won't Fix Status in linux-manta package in Ubuntu: Invalid Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-snapdragon package in Ubuntu: Fix Released Status in linux-ti-omap4 package in Ubuntu: Invalid Status in linux source package in Precise: Fix Released Status in linux-armadaxp source package in Precise: Fix Released Status in linux-flo source package in Precise: Invalid Status in linux-goldfish source package in Precise: Invalid Status in linux-keystone source package in Precise: Invalid Status in linux-lts-quantal source package in Precise: Invalid Status in linux-lts-raring source package in Precise: Invalid Status in linux-lts-saucy source package in Precise: Invalid Status in linux-lts-trusty source package in Precise: Fix Released Status in linux-lts-utopic source package in Precise: Invalid Status in linux-lts-vivid source package in Precise: Invalid Status in linux-lts-wily source package in Precise: Invalid Status in linux-lts-xenial source package in Precise: Invalid Status in linux-mako source package in Precise: Invalid Status in linux-manta source package in Precise: Invalid Status in linux-raspi2 source package in Precise: Invalid Status in linux-snapdragon source package in Precise: Invalid Status in linux-ti-omap4 source package in Precise: Fix Released Status in linux source package in Trusty: Fix Released Status in linux-armadaxp source package in Trusty: Invalid Status in linux-flo source package in Trusty: Invalid Status in linux-goldfish source package in Trusty: Invalid Status in linux-keystone source package in Trusty: Fix Released Status in linux-lts-quantal source package in Trusty: Invalid Status in linux-lts-raring source package in Trusty: Invalid Status in linux-lts-saucy source package in Trusty: Invalid Status in linux-lts-trusty source package in Trusty: Invalid Status in linux-lts-utopic source package in Trusty: Fix Released Status in linux-lts-vivid source package in Trusty: Fix Released Status in linux-lts-wily source package in Trusty: Fix Released Status in linux-lts-xenial source package in Trusty: Fix Released Status in linux-mako source package in Trusty: Invalid Status in linux-manta source package in Trusty: Invalid Status in linux-raspi2 source package in Trusty: Invalid Status in linux-snapdragon source package in Trusty: Invalid Status in linux-ti-omap4 source package in Trusty: Invalid Status in linux source package in Vivid: Fix Released Status in linux-armadaxp source package in Vivid: Invalid Status in linux-flo source package in Vivid: Won't Fix Status in linux-goldfish source package in Vivid: New Status in linux-keystone source package in Vivid: Invalid Status in linux-lts-quantal source package in Vivid: Won't Fix Status in linux-lts-raring source package in Vivid: New Status in linux-lts-saucy source package in Vivid: Won't Fix Status in linux-lts-trusty source package in Vivid: Won't Fix Status in linux-lts-utopic source package in Vivid: Invalid Status in linux-lts-vivid source package in Vivid: Won't Fix Status in linux-lts-wily source package in Vivid: New Status in linux-lts-xenial source package in Vivid: New Status in linux-mako source package in Vivid: Won't Fix Status in linux-manta source package in Vivid: New Status in linux-raspi2 source package in Vivid: Won't Fix Status in linux-snapdragon source package in Vivid: New Status in linux-ti-omap4 source package in Vivid: Invalid Status in linux source package in Wily: Fix Released Status in linux-armadaxp source package in Wily:
[Kernel-packages] [Bug 1885033] Re: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04)
Hmm, somehow my comment didn't show up. Please install libinput-tools, run `sudo libinput debug-events`, press the hotkey and attach the output here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885033 Title: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04) Status in linux package in Ubuntu: Incomplete Bug description: The touchpad switch, Fn-F6, does not work for me. It does work on Windows 10 (dual boot) The touchpad works well, but I can only set the option in System Conguration. See launchpad answer : https://answers.launchpad.net/ubuntu/+question/691511 Kubuntu 20.04 Lenovo IdeaPad L340-15IRH - Type 81LK --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yann 1350 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-20 (125 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81LK NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=0ac30ea3-dc16-4323-a1a3-acea99fa90b5 ro quiet splash resume=/dev/nvme0n1p6 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-14 (41 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN29WW 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: IdeaPad L340-15IRH Gaming dmi.modalias: dmi:bvnLENOVO:bvrBGCN29WW:bd02/10/2020:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887324] Re: wifi not working
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887324 Title: wifi not working Status in linux package in Ubuntu: New Bug description: install driver tl-wn725n okela but not connect with wifi by command line To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887324/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886341] Re: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05)
I am pleased to report your patched kernel works for me as well. Excellent work! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886341 Title: Kernel Regression between 5.4.0-26 and 5.4.0-40 causes laptop internal audio devices to fail to load w/o unacceptable workaround (Lenovo IdeaPad 5 15IIL05) Status in linux package in Ubuntu: Fix Released Status in linux source package in Focal: In Progress Bug description: [Impact] On the machine of Lenovo IdeaPad 5 15IIL05, the audio doesn't work, checking the dmesg, I found the audio driver fails to initialize because it fails on i915 audio codec probe. [Fix] backport 3 patches from mainline kernel, move the i915 audio codec init earlier. [Test Case] Boot the kernel with these 3 patches, check dmesg, there is no i915 audio codec probe error anymore, and audio driver initializes successfully, and input and output audio devices all work. [Regression Risk] Low, already tested these 3 patches on a couple of LENOVO dmic machines (cnl and cml machines), all work as well as before. On Ubuntu 20.04, running kernel 5.4.0-40-generic, the internal speakers, headphone jack, and mic do not work at all. No audio devices appear in the Sound settings or in pavucontrol. By appending options snd_hda_intel dmic_detect=0 to /etc/modprobe.d/alsa-base.conf, I can get audio working, but the microphone (unsuprisingly) does not work. Appending options snd-intel-dspcfg dsp_driver=1 to alsa_base.conf as the same effect as dmic_detect=0. Attempts to fix with option snd_hda_intel device=generic or deveice=auto have had no effect. This bug does NOT manifest on 5.4.0-26-generic, the kernel version featured on the 20.04 live media. After installation, and updating to 5.4.0-40-generic, the bug manifests on the next boot. Note that the audio hardware seems to work properly w/o workaround on a small (< 5%) percentage of boots, but I have been unable to reproduce this. With the workaround enabled, inxi -A gives Audio: Device-1: Intel Smart Sound Audio driver: snd_hda_intel Sound Server: ALSA v: k5.4.0-40-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: jill 1374 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Jul 5 13:32:58 2020 InstallationDate: Installed on 2020-07-03 (2 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK 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-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/18/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DPCN40WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrDPCN40WW:bd03/18/2020:svnLENOVO:pn81YK:pvrIdeaPad515IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrIdeaPad515IIL05: dmi.product.family: IdeaPad 5 15IIL05 dmi.product.name: 81YK dmi.product.sku: LENOVO_MT_81YK_BU_idea_FM_IdeaPad 5 15IIL05 dmi.product.version: IdeaPad 5 15IIL05 dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 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-07-03 (5 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YK Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=dc3e058d-42fc-4de4-b94a-749c1295dc68 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 RelatedPackageVersions:
[Kernel-packages] [Bug 1883949] Re: dkms packages generate insecure MOK, allow potential lockdown bypass
** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883949 Title: dkms packages generate insecure MOK, allow potential lockdown bypass Status in linux package in Ubuntu: Invalid Bug description: When the first DKMS package is installed, apt will generate a machine owner key pair in /var/lib/shim-signed/mok/ and enroll it with the shim so that the dynamically build kernel modules can be validated. A password is requested, but only to validate the public key registration on the next reboot. The private key is only protected by 0600 permissions. An attacker who can escalate to root can later use this password-less MOK.priv file to sign their own modules and bypass the lockdown protections to escalate into the kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887564] Re: Laptop XPS13 can't sleep Ubuntu 16.04.6 LTS when USB3 device is/was attached.
You can disable USB3 wakeup by modifying "/proc/acpi/wakeup" 1. list all wakeup sources - cat /proc/acpi/wakeup 2. enable or disable by echo device name - for example, my USB3 is XHC - echo XHC | sudo tee /proc/acpi/wakeup 3. confirm changes - cat /proc/acpi/wakeup -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887564 Title: Laptop XPS13 can't sleep Ubuntu 16.04.6 LTS when USB3 device is/was attached. Status in linux package in Ubuntu: Incomplete Bug description: (Ubuntu 4.4.0-185.215-generic 4.4.224) If I plug a USB3 device on the USB3 port then I can't send the laptop to sleep. (this happens with audio interface UMC404HD and Gbit Ethernet Adapter Trendnet) Instead it cancels the sleep process: Jul 13 10:24:22 xps kernel: [318785.373269] video LNXVIDEO:00: Restoring backlight state Jul 13 10:24:24 xps kernel: [318785.375145] PM: Syncing filesystems ... done. Jul 13 10:24:24 xps kernel: [318785.424201] PM: Preparing system for sleep (freeze) Jul 13 10:24:24 xps kernel: [318785.424337] Freezing user space processes ... (elapsed 0.001 seconds) done. Jul 13 10:24:24 xps kernel: [318785.426132] Freezing remaining freezable tasks ... (elapsed 0.037 seconds) done. Jul 13 10:24:24 xps kernel: [318785.463699] PM: Suspending system (freeze) Jul 13 10:24:24 xps kernel: [318785.463701] Suspending console(s) (use no_console_suspend to debug) Jul 13 10:24:24 xps kernel: [318785.463921] sd 0:0:0:0: [sda] Synchronizing SCSI cache Jul 13 10:24:24 xps kernel: [318785.463971] sd 0:0:0:0: [sda] Stopping disk Jul 13 10:24:24 xps kernel: [318786.150701] dpm_run_callback(): usb_dev_suspend+0x0/0x20 returns -16 Jul 13 10:24:24 xps kernel: [318786.150716] PM: Device usb4 failed to suspend async: error -16 Jul 13 10:24:24 xps kernel: [318786.150831] PM: Some devices failed to suspend, or early wake event detected Jul 13 10:24:24 xps kernel: [318786.166836] sd 0:0:0:0: [sda] Starting disk Jul 13 10:24:24 xps kernel: [318786.254775] rtc_cmos 00:01: System wakeup disabled by ACPI Jul 13 10:24:24 xps kernel: [318786.490641] ata1: SATA link up 6.0 Gbps (SStatus 133 SControl 300) Jul 13 10:24:24 xps kernel: [318786.513275] ata1.00: configured for UDMA/133 Jul 13 10:24:24 xps kernel: [318786.942366] PM: resume of devices complete after 791.556 msecs Jul 13 10:24:24 xps kernel: [318786.942703] PM: Finishing wakeup. Jul 13 10:24:24 xps kernel: [318786.942706] Restarting tasks ... done. Jul 13 10:24:24 xps systemd[1]: systemd-suspend.service: Main process exited, code=exited, status=1/FAILURE Jul 13 10:24:24 xps kernel: [318786.967694] video LNXVIDEO:00: Restoring backlight state To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1887340] Re: system freezes including keyboard and mouse whenever a CD is played
Tested with kernel 5.7.8 ! Issue persists. On Tue, 14 Jul 2020, 3:50 pm Pankaj Kr Sharma, wrote: > Okay. > > On Mon, 13 Jul 2020, 6:10 pm Kai-Heng Feng, <1887...@bugs.launchpad.net> > wrote: > >> Please test latest mainline kernel: >> https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc5/ >> >> If latest kernel doesn't fix it then we need to bisect kernel. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1887340 >> >> Title: >> system freezes including keyboard and mouse whenever a CD is played >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1887340/+subscriptions >> > -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887340 Title: system freezes including keyboard and mouse whenever a CD is played Status in linux package in Ubuntu: Incomplete Bug description: Consistently, whenever a CD is played, the system freezes including keyboard and mouse. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: pks1207 F pulseaudio /dev/snd/controlC2: pks1207 F pulseaudio /dev/snd/controlC0: pks1207 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jul 13 11:42:33 2020 InstallationDate: Installed on 2020-01-06 (188 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: System manufacturer System Product Name ProcFB: 0 VESA VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=ff43ab9d-9612-4215-8f0c-d11964542c44 ro quiet splash vt.handoff=7 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: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-16 (57 days ago) dmi.bios.date: 05/01/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 1702 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: M5A88-M 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.:bvr1702:bd05/01/2013:svnSystemmanufacturer:pnSystemProductName:pvrSystemVersion:rvnASUSTeKComputerINC.:rnM5A88-M:rvrRevX.0x:cvnChassisManufacture:ct3:cvrChassisVersion: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: System Product Name dmi.product.sku: To Be Filled By O.E.M. 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/1887340/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874279] Re: failed to boot focal image in maas: /root.tmp.img: can't open blockdev
Seems to work in the latest images imported from the streams. ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874279 Title: failed to boot focal image in maas: /root.tmp.img: can't open blockdev Status in linux package in Ubuntu: Invalid Bug description: We have at least two systems in our lab that are seeing this problem. Both of them are able to boot other images (bionic, etc) just fine, and at least one of them was definitely booting focal earlier this week from the stream import in maas. But now, whenever we try to provision them with the focal image, it fails to boot for provisioning. I got someone to look at the console and take pictures (no serial or bmc on these, sorry) and they were dropped to busybox on boot. One error did jump out in dmesg: /root.tmp.img: can't open blockdev I'll also post the images of the screen for further details. There are other devices that boot the image from maas just fine, but I did try re-importing it just to be sure nothing was messed up with it. The two systems we're having problems with at the moment are: - Dell inspiron 5758 i5-5200 (dearest-team) - Dell inspiron 5759 i5-6200 (unknown-wealth) It's unknown yet whether there are others affected by this. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1874279/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
Hello Kernel 5.8-rc5 from https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.8-rc5/ does not resolve the problem. I tried to use below command to reattach all apport files, but it only attached one file, let me know if you need more files (and provide the appropriate command line !) apport-collect 1887190 Thanks Nicolas -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1887190 Title: MSFT Touchpad not working on Lenovo Legion-5 15ARH05 Status in linux package in Ubuntu: Confirmed Bug description: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO ---
[Kernel-packages] [Bug 1885033] Re: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04)
$ sudo libinput debug-events -event4 DEVICE_ADDED Video Bus seat0 default group1 cap:k -event3 DEVICE_ADDED Video Bus seat0 default group1 cap:k -event1 DEVICE_ADDED Power Button seat0 default group2 cap:k -event0 DEVICE_ADDED Lid Switchseat0 default group3 cap:S -event9 DEVICE_ADDED HDA NVidia HDMI/DP,pcm=3 seat0 default group4 cap: -event5 DEVICE_ADDED PixArt USB Optical Mouse seat0 default group5 cap:p left scroll-nat scroll-button -event6 DEVICE_ADDED Integrated Camera: Integrated C seat0 default group6 cap:k -event8 DEVICE_ADDED Elan Touchpad seat0 default group7 cap:pg size 104x68mm tap(dl off) left scroll-nat scroll-2fg-edge click-buttonareas-clickfinger dwt-on -event7 DEVICE_ADDED Ideapad extra buttons seat0 default group8 cap:k -event11 DEVICE_ADDED HDA Intel PCH Headphone seat0 default group4 cap: -event12 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=3 seat0 default group4 cap: -event13 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=7 seat0 default group4 cap: -event14 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=8 seat0 default group4 cap: -event15 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=9 seat0 default group4 cap: -event16 DEVICE_ADDED HDA Intel PCH HDMI/DP,pcm=10 seat0 default group4 cap: -event10 DEVICE_ADDED HDA Intel PCH Mic seat0 default group4 cap: -event2 DEVICE_ADDED AT Translated Set 2 keyboard seat0 default group9 cap:k # Pressing and releasing Fn (nothing) # Pressing Fn, pressing and releasing F6 (ie, pressing and releasing Fn+F6) (nothing) # Pressing and releasing F6 event2 KEYBOARD_KEY +10.435s *** (-1) pressed ^[[17~ event2 KEYBOARD_KEY +10.508s *** (-1) released # Pressing and releasing F5 event2 KEYBOARD_KEY +19.242s *** (-1) pressed ^[[15~ event2 KEYBOARD_KEY +19.306s *** (-1) released # Pressing and releasing Fn+F5 event2 KEYBOARD_KEY +19.726s *** (-1) pressed ^[[15~ event2 KEYBOARD_KEY +19.802s *** (-1) released # Pressing and releasing F7 event2 KEYBOARD_KEY +22.121s *** (-1) pressed ^[[18~ event2 KEYBOARD_KEY +22.203s *** (-1) released # Pressing and releasing Fn+F7 -event7 KEYBOARD_KEY +22.612s KEY_RFKILL (247) pressed event7 KEYBOARD_KEY +22.612s KEY_RFKILL (247) released # Pressing Ctrl+C -event2 KEYBOARD_KEY +25.287s *** (-1) pressed event2 KEYBOARD_KEY +25.503s *** (-1) pressed ^C BTW, the touchpad inputs are still registered when my computer has them off, but I guess that's just how KDE/Ubuntu works for cutting them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885033 Title: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04) Status in linux package in Ubuntu: Incomplete Bug description: The touchpad switch, Fn-F6, does not work for me. It does work on Windows 10 (dual boot) The touchpad works well, but I can only set the option in System Conguration. See launchpad answer : https://answers.launchpad.net/ubuntu/+question/691511 Kubuntu 20.04 Lenovo IdeaPad L340-15IRH - Type 81LK --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yann 1350 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-20 (125 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81LK NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=0ac30ea3-dc16-4323-a1a3-acea99fa90b5 ro quiet splash resume=/dev/nvme0n1p6 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-14 (41 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True
[Kernel-packages] [Bug 1887190] Re: MSFT Touchpad not working on Lenovo Legion-5 15ARH05
apport information ** Tags added: apport-collected ** Description changed: Hello The MSFT touchpad of this Lenovo Legion-5 15ARH05 laptop is not reacting at all (pointer and click never move when touchpad is touched). This has been reported by other users in various websites, with various linux systems including other Ubuntu systems, but I saw no launchpad bug so I post one. Example of websites covering the issue : - https://askubuntu.com/questions/1253830/lenovo-legion-5-touchpad (exactly the same laptop) - https://www.linux.org/threads/lenovo-legion-5-touchpad.29536/ (similar laptop) xinput indentifies it as MSFT0001:00 04F3:3140 Virtual core pointer id=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Touchpad id=17 [slave pointer (2)] ⎜ ↳ MSFT0001:00 04F3:3140 Mouse id=16 [slave pointer (2)] ⎜ ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=12 [slave pointer (2)] ⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Ideapad extra buttons id=15 [slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Integrated Camera: Integrated C id=10 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Consumer Controlid=19 [slave keyboard (3)] ↳ Power Buttonid=9[slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Wireless Radio Control id=13 [slave keyboard (3)] ↳ ITE Tech. Inc. ITE Device(8910) Keyboardid=14 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=18 [slave keyboard (3)] ↳ Video Bus id=8[slave keyboard (3)] Thanks a lot for your time. It does not help, but I can confirm what was reported on askubuntu by another user : the touchpad does work on Windows. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-40-generic 5.4.0-40.44 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: nicolas1567 F pulseaudio /dev/snd/controlC1: nicolas1567 F pulseaudio /dev/snd/controlC2: nicolas1567 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Jul 10 20:14:25 2020 InstallationDate: Installed on 2020-07-02 (8 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 82B5 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-40-generic root=UUID=d8898017-2821-434e-ab52-fec76ac93106 ro quiet splash vt.handoff=7 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 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/12/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EUCN19WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Legion 5 15ARH05 dmi.modalias: dmi:bvnLENOVO:bvrEUCN19WW:bd05/12/2020:svnLENOVO:pn82B5:pvrLenovoLegion515ARH05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoLegion515ARH05: dmi.product.family: Legion 5 15ARH05 dmi.product.name: 82B5 dmi.product.sku: LENOVO_MT_82B5_BU_idea_FM_Legion 5 15ARH05 dmi.product.version: Lenovo Legion 5 15ARH05 dmi.sys.vendor: LENOVO + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.3 + Architecture: amd64 + CasperMD5CheckResult: skip + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2020-07-02 (12 days ago) + InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) + Package: linux (not installed) + ProcEnviron: + TERM=xterm-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR= + LANG=fr_FR.UTF-8 + SHELL=/bin/bash + Tags: focal + Uname: Linux 5.8.0-050800rc5-generic x86_64 +
[Kernel-packages] [Bug 1880975] Re: Request to include two NUMA related commits in Azure kernels
** Also affects: linux-azure-4.15 (Ubuntu)
Importance: Undecided
Status: New
** Changed in: linux-azure-4.15 (Ubuntu Bionic)
Status: New => Fix Committed
** Changed in: linux-azure-4.15 (Ubuntu Eoan)
Status: New => Invalid
** Changed in: linux-azure-4.15 (Ubuntu Focal)
Status: New => Invalid
** Changed in: linux-azure (Ubuntu Bionic)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1880975
Title:
Request to include two NUMA related commits in Azure kernels
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-azure-4.15 package in Ubuntu:
New
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Committed
Status in linux-azure source package in Eoan:
Fix Committed
Status in linux-azure-4.15 source package in Eoan:
Invalid
Status in linux-azure source package in Focal:
Fix Committed
Status in linux-azure-4.15 source package in Focal:
Invalid
Bug description:
Microsoft would like to request the following two commits in all
releases supported on Azure:
999dd956d838 ("PCI: hv: Add support for protocol 1.3 and support
PCI_BUS_RELATIONS2")
f9ad0f361cf3 ("PCI: hv: Decouple the func definition in hv_dr_state from VSP
message")
These two commits will add support for PCI protocol version 1.3. This
will allow the host to pass NUMA node information for devices on the
bus. Currently it is assumed the NUMA node is 0, which these patches
will correct. This functionality will provide an increase in
performance, especially for HPC and AI workloads.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1880975/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1883676] Re: ZFS performance drops suddenly
1. free totalusedfree shared buff/cache available Mem:8025436 1255616 6457736 11780 312084 6512296 Swap: 1425404 0 1425404 2. cat /proc/spl/kstat/zfs/arcstats 12 1 0x01 98 26656 4085867100 20862566338548 nametype data hits48977275 misses 420770 demand_data_hits47154775 demand_data_misses 413760 demand_metadata_hits41810210 demand_metadata_misses 44292 prefetch_data_hits 4112 prefetch_data_misses4719 prefetch_metadata_hits 412178 prefetch_metadata_misses41999 mru_hits44041554 mru_ghost_hits 40 mfu_hits44923504 mfu_ghost_hits 40 deleted 431 mutex_miss 40 access_skip 49 evict_skip 4124 evict_not_enough40 evict_l2_cached 40 evict_l2_eligible 4396800 evict_l2_ineligible 48192 evict_l2_skip 40 hash_elements 420337 hash_elements_max 422033 hash_collisions 482157 hash_chains 4196 hash_chain_max 42 p 42054511616 c 44109023232 c_min 4256813952 c_max 44109023232 size41856513648 compressed_size 41349638144 uncompressed_size 41738882048 overhead_size 4446370304 hdr_size47828496 data_size 41709473792 metadata_size 486534656 dbuf_size 49437376 dnode_size 423086368 bonus_size 420152960 anon_size 4438411264 anon_evictable_data 40 anon_evictable_metadata 40 mru_size41186710528 mru_evictable_data 4908280320 mru_evictable_metadata 44658688 mru_ghost_size 40 mru_ghost_evictable_data40 mru_ghost_evictable_metadata40 mfu_size4170886656 mfu_evictable_data 4134954496 mfu_evictable_metadata 43134976 mfu_ghost_size 40 mfu_ghost_evictable_data40 mfu_ghost_evictable_metadata40 l2_hits 40 l2_misses 40 l2_feeds40 l2_rw_clash 40 l2_read_bytes 40 l2_write_bytes 40 l2_writes_sent 40 l2_writes_done 40 l2_writes_error 40 l2_writes_lock_retry40 l2_evict_lock_retry 40 l2_evict_reading40 l2_evict_l1cached 40 l2_free_on_write40 l2_abort_lowmem 40 l2_cksum_bad40 l2_io_error 40 l2_size 40 l2_asize40 l2_hdr_size 40 memory_throttle_count 40 memory_direct_count 40 memory_indirect_count 40 memory_all_bytes48218046464 memory_free_bytes 45230358528 memory_available_bytes 35101953024 arc_no_grow 40 arc_tempreserve 40 arc_loaned_bytes40 arc_prune 40 arc_meta_used 4147039856 arc_meta_limit 43081767424 arc_dnode_limit 4308176742 arc_meta_max4152895280 arc_meta_min416777216 async_upgrade_sync 459 demand_hit_predictive_prefetch 4484 demand_hit_prescient_prefetch 40 arc_need_free 40 arc_sys_free4128406976 arc_raw_size40 This behavior was observed on more than one machine, both small and large (the large was on AWS). Thanks, Andrey Gelman On Mon, Jul 13, 2020 at 5:45 PM Colin Ian King <1883...@bugs.launchpad.net> wrote: > It would be interesting in knowing the following data: > > 1. How much memory does the machine have when booted? > > run: free > > 2. What the arcstats look like when it goes slowly > > use: cat /proc/spl/kstat/zfs/arcstats > > thanks > > ** Changed in: zfs-linux (Ubuntu) >Status: Confirmed => Incomplete >
[Kernel-packages] [Bug 1887461] Re: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04
Hi Thanks for the update. After installing nvidia-430, I'm able to boot to gui, but I'm greeted with this message when I try to run steam (which I have set to autostart on boot) You are missing the following 32-bit libraries, and Steam may not run: libGL.so.1 So, I power down, wait a bit and reboot just to double check ... see same error, click ok do so googling, find this: https://steamcommunity.com/app/221410/discussions/0/1736635023062287934/ suggestions there don't help. try to run Steam anyway and I get this: OpenGL GLX context is not using direct rendering, which may cause performance problems. For more information visit https://support.steampowered.com/kb_article.php?ref=9938-EYZB-7457 so, I reinstall nvidia-418 and reboot... and steam works again. Hope that helps. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1887461 Title: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04 Status in nvidia-graphics-drivers-384 package in Ubuntu: Incomplete Bug description: when I did apt-get update && apt-get dist-upgrade, I saw that nvidia-430 package had the version 64 update that was just released a few days ago. After installing it, my system wouldn't boot to xwindows. Failsafe boot to gui wouldn't work either The error messages looked similar to this bug report for nvidia drivers: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 Here's what my xorg.[0,failsafe].log showed: [43.645] (++) Log file: "/var/log/Xorg.failsafe.log", Time: Mon Jul 13 18:41:16 2020 [43.645] (++) Using config file: "/etc/X11/xorg.conf.failsafe" [43.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [43.645] Parse error on line 7 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass.conf "OutputClass" is not a valid section name. [43.645] (EE) Problem parsing the config file [43.645] (EE) Error parsing the config file [43.645] (EE) Fatal server error: [43.645] (EE) no screens found(EE) I have a *directory* named what the file is looking for (at least now after I downgraded nvidia...) here is the contents: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf# cat nvidia-drm-outputclass.conf # This xorg.conf.d configuration snippet configures the X server to # automatically load the nvidia X driver when it detects a device driven by the # nvidia-drm.ko kernel module. Please note that this only works on Linux kernels # version 3.9 or higher with CONFIG_DRM enabled, and only if the nvidia-drm.ko # kernel module is loaded before the X server is started. Section "OutputClass" Identifier "nvidia" MatchDriver"nvidia-drm" Driver "nvidia" EndSection basically, in the progress of filing this bug report, I downgraded to nvidia-418 and my system was about to boot again. To me, that says that nvidia-430.64 at least on Ubuntu 14.04 has a regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1887461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1887461] Re: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04
The reported issue appears to be resolved, so marking 'Fix Released'. Again, Ubuntu 14.04 has reached EoL on standard support. If you do not have an Extended Support Agreement, you are running an unsupported and potentially insecure version of Ubuntu. ** Changed in: nvidia-graphics-drivers-384 (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-384 in Ubuntu. https://bugs.launchpad.net/bugs/1887461 Title: nvidia-430 amd64 430.64=0ubuntu0~gpu14.04.1 broke xwindows on Ubuntu 14.04 Status in nvidia-graphics-drivers-384 package in Ubuntu: Fix Released Bug description: when I did apt-get update && apt-get dist-upgrade, I saw that nvidia-430 package had the version 64 update that was just released a few days ago. After installing it, my system wouldn't boot to xwindows. Failsafe boot to gui wouldn't work either The error messages looked similar to this bug report for nvidia drivers: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1752053 Here's what my xorg.[0,failsafe].log showed: [43.645] (++) Log file: "/var/log/Xorg.failsafe.log", Time: Mon Jul 13 18:41:16 2020 [43.645] (++) Using config file: "/etc/X11/xorg.conf.failsafe" [43.645] (==) Using system config directory "/usr/share/X11/xorg.conf.d" [43.645] Parse error on line 7 of section OutputClass in file /usr/share/X11/xorg.conf.d/nvidia-drm-outputclass.conf "OutputClass" is not a valid section name. [43.645] (EE) Problem parsing the config file [43.645] (EE) Error parsing the config file [43.645] (EE) Fatal server error: [43.645] (EE) no screens found(EE) I have a *directory* named what the file is looking for (at least now after I downgraded nvidia...) here is the contents: /usr/share/X11/xorg.conf.d/50-nvidia-drm-outputclass.conf# cat nvidia-drm-outputclass.conf # This xorg.conf.d configuration snippet configures the X server to # automatically load the nvidia X driver when it detects a device driven by the # nvidia-drm.ko kernel module. Please note that this only works on Linux kernels # version 3.9 or higher with CONFIG_DRM enabled, and only if the nvidia-drm.ko # kernel module is loaded before the X server is started. Section "OutputClass" Identifier "nvidia" MatchDriver"nvidia-drm" Driver "nvidia" EndSection basically, in the progress of filing this bug report, I downgraded to nvidia-418 and my system was about to boot again. To me, that says that nvidia-430.64 at least on Ubuntu 14.04 has a regression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-384/+bug/1887461/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Firefox and pulseaudio* -- You 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 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 : -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 jackpoll_ms : 0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0,0
