[Kernel-packages] [Bug 1875263] Re: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan
The microphone is broken on the certfieid Dell Inspiron 7591, Dell Inspiron 7590, and Dell Inspiron 3590. due to missing this new firmware. We need to verify and land the solution ASAP. ** Changed in: linux-firmware (Ubuntu Bionic) Importance: Undecided => Critical ** Changed in: linux-firmware (Ubuntu) Importance: High => Critical ** Also affects: oem-priority Importance: Undecided Status: New ** Changed in: oem-priority Importance: Undecided => Critical ** Changed in: oem-priority Assignee: (unassigned) => Kai-Chuan Hsieh (kchsieh) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1875263 Title: linux-firmware: missing sof-cfl.ri symbol link for Bionic and Eoan Status in OEM Priority Project: New Status in linux-firmware package in Ubuntu: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: [Impact] some ubuntu eoan/bionic users reported that the audio driver failed to initialize, then the audio didn't work. I checked the dmesg, found the sof driver planed to load sof-cfl.ri, but there is no this firmware under eoan or bionic. [Fix] I consulted with Intel audio team, they told me that the coffeelake platform could share the firmware with cnl/whl platoforms, so we could build a symbol link sof-cfl->sof-cnl. [Test Case] A couple of ubuntu users already tested it on Dell and Asus coffeelake laptops, it worked well. [Regression Risk] Low, users already tested it, and Intel audio team confirmed it is safe. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1875263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882360] Re: wifi commanders have dessapeared
Please install rtl8821ce-dkms. Linux kernel doesn't support it (yet). ** Changed in: linux (Ubuntu) Importance: Undecided => Wishlist -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882360 Title: wifi commanders have dessapeared Status in linux package in Ubuntu: Confirmed Bug description: wifi has desapeared from the computer. Its a hp intel corei7, 8th gen. When updating to ubuntu 20.04 the controllers have gone- I have tried every patch i found but no idea how to do it. I have never asked anything in this forum, i donñt know how should do make the questiones ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-31-generic 5.4.0-31.35 ProcVersionSignature: Ubuntu 5.4.0-31.35-generic 5.4.34 Uname: Linux 5.4.0-31-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ret2180 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jun 6 15:46:25 2020 InstallationDate: Installed on 2019-10-09 (241 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) IwConfig: lono wireless extensions. eno1 no wireless extensions. usb0 no wireless extensions. MachineType: HP HP Pavilion Laptop 15-cs0xxx ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-31-generic root=/dev/mapper/ubuntu--vg-root ro recovery nomodeset i8042.nomux=1 i8042.reset RelatedPackageVersions: linux-restricted-modules-5.4.0-31-generic N/A linux-backports-modules-5.4.0-31-generic N/A linux-firmware1.187 RfKill: 0: hci0: Bluetooth Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/06/2018 dmi.bios.vendor: Insyde dmi.bios.version: F.04 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 84BE dmi.board.vendor: HP dmi.board.version: 02.12 dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.04:bd07/06/2018:svnHP:pnHPPavilionLaptop15-cs0xxx:pvrType1ProductConfigId:rvnHP:rn84BE:rvr02.12:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Pavilion dmi.product.name: HP Pavilion Laptop 15-cs0xxx dmi.product.sku: 4XH01EA#UUZ dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1882360/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886140] Re: drm_vram_helper crash when launching graphical.target with MGA G200e
BTW, it's certified in xenial[1]. I tried bionic desktop and it works good. [1] https://certification.ubuntu.com/hardware/201811-26640 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886140 Title: drm_vram_helper crash when launching graphical.target with MGA G200e Status in linux package in Ubuntu: New Bug description: [Description] The drm_vram_helper crash when launching display manager with MGA G200e. [Steps to reproduce] 0. Connect to a monitor via VGA 1. Install focal desktop image (5.4.0-21-generic) 2. Power on system and boot to multi-user.target 3. systemctl isolate graphical.target [Expect result] System launch GDM without problems [Actual result] System hang and monitor keep purple screen 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 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Fri Jul 3 13:27:53 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Lenovo ThinkSystem ST250 -[7Y45CTO1WW]- ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=68fd62d3-1204-4f51-a3b4-b35919882e7f ro systemd.unit=multi-user.target 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2020 dmi.bios.vendor: Lenovo dmi.bios.version: -[ISE116D-2.10]- dmi.board.asset.tag: none dmi.board.name: -[7Y45CTO1WW]- dmi.board.vendor: Lenovo dmi.board.version: none dmi.chassis.asset.tag: none dmi.chassis.type: 7 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.modalias: dmi:bvnLenovo:bvr-[ISE116D-2.10]-:bd04/24/2020:svnLenovo:pnThinkSystemST250-[7Y45CTO1WW]-:pvr03:rvnLenovo:rn-[7Y45CTO1WW]-:rvrnone:cvnLenovo:ct7:cvrnone: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem ST250 -[7Y45CTO1WW]- dmi.product.sku: 7Y45CTO1WW dmi.product.version: 03 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863086] Re: unkillable process (kernel NULL pointer dereference)
The fix has been released in the form of 5.4.0-40-generic on focal, and 5.3.0-62-generic on Eoan. ** Changed in: linux (Ubuntu Eoan) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863086 Title: unkillable process (kernel NULL pointer dereference) Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: If process that listens socket on any port crashes (segmentation fault) it becomes unkillable. Kill command does not kill this process. Port that listen crashed process never be freed. journalctl shows error: Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip 55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000] Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address: 0020 Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0 Feb 13 13:28:09 vbun04 kernel: Oops: [#1] SMP NOPTI Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G OE 5.3.0-29-generic #31-Ubuntu Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30 Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: 9d4b76995100 RCX: 1afc Feb 13 13:28:09 vbun04 kernel: RDX: RSI: b464c2c5fc68 RDI: Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 R09: b464c2c5fbe0 Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11: R12: 9d4b7b3df540 Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14: R15: b9f15920 Feb 13 13:28:09 vbun04 kernel: FS: 7f6c91911540() GS:9d4b7db0() knlGS: Feb 13 13:28:09 vbun04 kernel: CS: 0010 DS: ES: CR0: 80050033 Feb 13 13:28:09 vbun04 kernel: CR2: 0020 CR3: 723ac003 CR4: 000606e0 Feb 13 13:28:09 vbun04 kernel: Call Trace: Feb 13 13:28:09 vbun04 kernel: ? wake_up_state+0x10/0x20 Feb 13 13:28:09 vbun04 kernel: ? __send_signal+0x1eb/0x3f0 Feb 13 13:28:09 vbun04 kernel: get_signal+0x159/0x880 Feb 13 13:28:09 vbun04 kernel: do_signal+0x34/0x280 Feb 13 13:28:09 vbun04 kernel: ? bad_area+0x47/0x50 Feb 13 13:28:09 vbun04 kernel: exit_to_usermode_loop+0xbf/0x160 Feb 13 13:28:09 vbun04 kernel: prepare_exit_to_usermode+0x77/0xa0 Feb 13 13:28:09 vbun04 kernel: retint_user+0x8/0x8 Feb 13 13:28:09 vbun04 kernel: RIP: 0033:0x55ec3a6bf11e Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: RSP: 002b:7ffd88899fb0 EFLAGS: 00010217 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: RCX: 7f6c918424eb Feb 13 13:28:09 vbun04 kernel: RDX: 0010 RSI: 000a RDI: 0003 Feb 13 13:28:09 vbun04 kernel: RBP: 0003 R08: R09: 7f6c919331f0 Feb 13 13:28:09 vbun04 kernel: R10: R11: 0217 R12: 55ec3a6bf150 Feb 13 13:28:09 vbun04 kernel: R13: 7ffd8889a0b0 R14: R15: Feb 13 13:28:09 vbun04 kernel: Modules linked in: vboxsf(OE) nls_utf8 isofs vboxvideo(OE) intel_rapl_msr intel_rapl_common crct10dif_pclmul vmwgfx crc32_pclmul ghash_clmulni_intel aesni_intel ttm drm_kms_helper a Feb 13 13:28:09 vbun04 kernel: CR2: 0020 Feb 13 13:28:09 vbun04 kernel: ---[ end trace 278d665c8727286a ]--- Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30 Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f Feb 13
[Kernel-packages] [Bug 1886140] Re: drm_vram_helper crash when launching graphical.target with MGA G200e
** Summary changed: - drm_vram_helper crash when launching DM with MGA G200e + drm_vram_helper crash when launching graphical.target with MGA G200e -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886140 Title: drm_vram_helper crash when launching graphical.target with MGA G200e Status in linux package in Ubuntu: New Bug description: [Description] The drm_vram_helper crash when launching display manager with MGA G200e. [Steps to reproduce] 0. Connect to a monitor via VGA 1. Install focal desktop image (5.4.0-21-generic) 2. Power on system and boot to multi-user.target 3. systemctl isolate graphical.target [Expect result] System launch GDM without problems [Actual result] System hang and monitor keep purple screen 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 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Fri Jul 3 13:27:53 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Lenovo ThinkSystem ST250 -[7Y45CTO1WW]- ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=68fd62d3-1204-4f51-a3b4-b35919882e7f ro systemd.unit=multi-user.target 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2020 dmi.bios.vendor: Lenovo dmi.bios.version: -[ISE116D-2.10]- dmi.board.asset.tag: none dmi.board.name: -[7Y45CTO1WW]- dmi.board.vendor: Lenovo dmi.board.version: none dmi.chassis.asset.tag: none dmi.chassis.type: 7 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.modalias: dmi:bvnLenovo:bvr-[ISE116D-2.10]-:bd04/24/2020:svnLenovo:pnThinkSystemST250-[7Y45CTO1WW]-:pvr03:rvnLenovo:rn-[7Y45CTO1WW]-:rvrnone:cvnLenovo:ct7:cvrnone: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem ST250 -[7Y45CTO1WW]- dmi.product.sku: 7Y45CTO1WW dmi.product.version: 03 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1872984] Re: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic
Does cold boot help? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1872984 Title: RTL8822BE network driver rtl_wifi crashes on boot in Focal Fossa 20.04 - 5.4.0-21-generic and mainline 5.7.0-050700rc1-generic Status in linux package in Ubuntu: Invalid Bug description: RTL8822BE crashes after rtw_pci starts on boot after kernel update to 5.4.0-21 (fails to read DBI register -- see attached dmesg). Issue is still present on latest mainline kernel version 5.7.0-050700rc1-generic . [ 10.627501] rtw_pci :3a:00.0: start vif 5c:ea:1d:b6:17:11 on port 0 [ 10.714544] [ cut here ] [ 10.714545] failed to read DBI register, addr=0x0719 [ 10.714577] WARNING: CPU: 0 PID: 939 at drivers/net/wireless/realtek/rtw88/pci.c:1156 rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714577] Modules linked in: (see attached dmesg) [ 10.714614] CPU: 0 PID: 939 Comm: wpa_supplicant Not tainted 5.7.0-050700rc1-generic #202004122032 [ 10.714614] Hardware name: LENOVO 81CU/LNVNB161216, BIOS 7KCN22WW(V1.03) 01/23/2018 [ 10.714616] RIP: 0010:rtw_dbi_read8.constprop.0+0xaa/0xc0 [rtwpci] [ 10.714617] Code: 03 00 00 48 8b 40 50 e8 24 c3 4b e0 5b 41 5c 41 88 45 00 31 c0 41 5d 5d c3 be 19 07 00 00 48 c7 c7 70 73 94 c0 e8 bb de 75 df <0f> 0b b8 fb ff ff ff 5b 41 5c 41 5d 5d c3 0f 1f 84 00 00 00 00 00 [ 10.714618] RSP: 0018:b466007e7880 EFLAGS: 00010282 [ 10.714618] RAX: RBX: RCX: 0007 [ 10.714619] RDX: 0007 RSI: 0092 RDI: 933cc9e19c80 [ 10.714619] RBP: b466007e7898 R08: 03d2 R09: 0004 [ 10.714620] R10: R11: 0001 R12: 933cbdf31ea0 [ 10.714620] R13: b466007e78af R14: 933cbdf35bc8 R15: [ 10.714622] FS: 7fbcedc6efc0() GS:933cc9e0() knlGS: [ 10.714622] CS: 0010 DS: ES: CR0: 80050033 [ 10.714623] CR2: 563278766000 CR3: 0002be7a4002 CR4: 003606f0 [ 10.714623] Call Trace: [ 10.714627] rtw_pci_link_ps+0x4e/0x90 [rtwpci] [ 10.714630] ? _raw_spin_unlock_bh+0x1e/0x20 [ 10.714637] rtw_leave_ips+0x1f/0x80 [rtw88] [ 10.714640] rtw_ops_config+0xa3/0xe0 [rtw88] [ 10.714658] ieee80211_hw_config+0x95/0x390 [mac80211] [ 10.714669] ieee80211_recalc_idle+0x27/0x30 [mac80211] [ 10.714679] __ieee80211_start_scan+0x334/0x750 [mac80211] [ 10.714688] ieee80211_request_scan+0x30/0x50 [mac80211] [ 10.714699] ieee80211_scan+0x5c/0xa0 [mac80211] [ 10.714719] nl80211_trigger_scan+0x59a/0x6c0 [cfg80211] [ 10.714722] genl_rcv_msg+0x1a8/0x470 [ 10.714724] ? ep_poll_callback+0x2a0/0x2c0 [ 10.714725] ? genl_family_rcv_msg_attrs_parse+0x100/0x100 [ 10.714726] netlink_rcv_skb+0x50/0x120 [ 10.714728] genl_rcv+0x29/0x40 [ 10.714729] netlink_unicast+0x1a8/0x250 [ 10.714730] netlink_sendmsg+0x233/0x460 [ 10.714739] ? _copy_from_user+0x31/0x60 [ 10.714750] sock_sendmsg+0x65/0x70 [ 10.714751] sys_sendmsg+0x212/0x280 [ 10.714752] ? copy_msghdr_from_user+0x5c/0x90 [ 10.714755] ? __check_object_size+0x4d/0x150 [ 10.714756] ___sys_sendmsg+0x81/0xc0 [ 10.714757] ? __check_object_size+0x4d/0x150 [ 10.714759] ? unix_ioctl+0x99/0x180 [ 10.714760] ? sock_getsockopt+0x198/0xc04 [ 10.714761] ? sock_do_ioctl+0x47/0x140 [ 10.714763] ? __cgroup_bpf_run_filter_setsockopt+0xae/0x2c0 [ 10.714765] ? _cond_resched+0x19/0x30 [ 10.714767] ? aa_sk_perm+0x43/0x1b0 [ 10.714768] __sys_sendmsg+0x5c/0xa0 [ 10.714770] __x64_sys_sendmsg+0x1f/0x30 [ 10.714772] do_syscall_64+0x57/0x1b0 [ 10.714773] entry_SYSCALL_64_after_hwframe+0x44/0xa9 [ 10.714774] RIP: 0033:0x7fbcedffb5b7 [ 10.714775] Code: 64 89 02 48 c7 c0 ff ff ff ff eb bb 0f 1f 80 00 00 00 00 f3 0f 1e fa 64 8b 04 25 18 00 00 00 85 c0 75 10 b8 2e 00 00 00 0f 05 <48> 3d 00 f0 ff ff 77 51 c3 48 83 ec 28 89 54 24 1c 48 89 74 24 10 [ 10.714776] RSP: 002b:7fff88e22288 EFLAGS: 0246 ORIG_RAX: 002e [ 10.714777] RAX: ffda RBX: 5632787355d0 RCX: 7fbcedffb5b7 [ 10.714777] RDX: RSI: 7fff88e222c0 RDI: 0006 [ 10.714778] RBP: 563278761380 R08: 0004 R09: 563278761380 [ 10.714778] R10: 7fff88e22394 R11: 0246 R12: 5632787354e0 [ 10.714779] R13: 7fff88e222c0 R14: 7fff88e22394 R15: 563278766710 [ 10.714780] ---[ end trace f00c16109236af6f ]--- [ 10.714782] rtw_pci :3a:00.0: failed to read ASPM, ret=-5 Device is unable to scan for networks and error occurs when attempting to turn on/off wifi in settings: [ 302.451636] rtw_pci :3a:00.0: stop vif
[Kernel-packages] [Bug 1847937] Re: 'gpu has fallen off the bus' after return from suspend
If default suspend method is s2idle but deep was chosen instead, expect to see buggy behavior. If this issue happen under s2idle, please file a new bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1847937 Title: 'gpu has fallen off the bus' after return from suspend Status in linux package in Ubuntu: Fix Released Bug description: With this message the only way to resume work is to reboot the system using power button. With kernel linux-image-5.3.0-13-generic everything is OK. Problem appeared afer upgrade to linux-image-5.3.0-17-generic and still happens in linux-image-5.3.0-18-generic. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: player 4451 F pulseaudio /dev/snd/controlC1: player 4451 F pulseaudio /dev/snd/controlC0: player 4451 F pulseaudio CurrentDesktop: KDE Date: Mon Oct 14 01:27:04 2019 HibernationDevice: RESUME=UUID=a58bb700-5818-4ca6-8351-fd4e5e28ea9e MachineType: LENOVO 20BG0016US ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-13-generic root=UUID=d0c33b75-6f04-4d53-bc3b-91924e3bcf91 ro quiet splash vga=current loglevel=0 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-08 (5 days ago) WifiSyslog: dmi.bios.date: 05/30/2018 dmi.bios.vendor: LENOVO dmi.bios.version: GNET88WW (2.36 ) dmi.board.asset.tag: Not Available dmi.board.name: 20BG0016US dmi.board.vendor: LENOVO dmi.board.version: 0B98401 Pro dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGNET88WW(2.36):bd05/30/2018:svnLENOVO:pn20BG0016US:pvrThinkPadW540:rvnLENOVO:rn20BG0016US:rvr0B98401Pro:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad W540 dmi.product.name: 20BG0016US dmi.product.sku: LENOVO_MT_20BG dmi.product.version: ThinkPad W540 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1847937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)
** Attachment added: "extracted DSDT table" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+attachment/5389274/+files/dsdt.dsl -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885573 Title: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) Status in linux package in Ubuntu: Confirmed Bug description: My laptop's touchpad is not recognized by current linux kernel (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat /proc/bus/input/devices'. 1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB) 2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is ALPS, Elan or Synatics 3. Problem occured for the first time during installation and then it continued after installation was complete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mrozwod1597 F pulseaudio /dev/snd/pcmC0D0p: mrozwod1597 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 16:06:14 2020 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN14WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)
** 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/1885573 Title: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) Status in linux package in Ubuntu: Confirmed Bug description: My laptop's touchpad is not recognized by current linux kernel (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat /proc/bus/input/devices'. 1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB) 2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is ALPS, Elan or Synatics 3. Problem occured for the first time during installation and then it continued after installation was complete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mrozwod1597 F pulseaudio /dev/snd/pcmC0D0p: mrozwod1597 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 16:06:14 2020 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN14WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874464] Re: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out
Would it be possible for you to do a reverse kernel bisection? First, find the first -rc kernel works and the last -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 new $(the working version you found) $ git bisect old $(the non-working version found) $ make localmodconfig $ make -j`nproc` deb-pkg Install the newly built kernel, then reboot with it. If it doesn’t work, $ git bisect old Otherwise, $ git bisect new Repeat to "make -j`nproc` deb-pkg" until you find the commit fixes the issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1874464 Title: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Status in linux package in Ubuntu: Incomplete Status in linux source package in Focal: Incomplete Status in linux source package in Groovy: Incomplete Bug description: Running focal on a desktop, I accidentally clicked "Enable networking" in nm-applet, disabling my networking. When I clicked it again to reenable it, my networking did not return. After unsuccessfully poking at it for a while, I rebooted and saw the below (and still no networking). `rmmod r8169; modprobe r8169` had no (apparent) effect, nor did further reboots. I rebooted onto two different kernels, both exhibited the same behaviour: 5.4.0-21-generic, 5.4.0-26-generic. I was finally only able to restore networking by _rebooting into Windows_ and then rebooting back into Ubuntu. (My supposition is that NetworkManager/the kernel set *waves hands* something on the network card that persists across boots when it was disabled, and that wasn't correctly unset when I reenabled networking (or on following boots), but Windows _does_ correctly handle that case on boot, and reset it to a working state.) Apr 23 10:07:43 surprise kernel: [ cut here ] Apr 23 10:07:43 surprise kernel: NETDEV WATCHDOG: enp5s0 (r8169): transmit queue 0 timed out Apr 23 10:07:43 surprise kernel: WARNING: CPU: 9 PID: 0 at net/sched/sch_generic.c:447 dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO) zcommon(PO) znvpair(PO) spl(O) zlua(PO) xt_comment dummy xt_CHECKSUM xt_MASQUERADE xt_conntrack ipt_REJECT nf_reject_ipv4 xt_tcpudp ip6table_mangle ip6table_nat iptable_mangle iptable_nat nf_> Apr 23 10:07:43 surprise kernel: autofs4 btrfs xor zstd_compress raid6_pq libcrc32c dm_crypt hid_microsoft ff_memless hid_logitech_hidpp hid_logitech_dj hid_generic usbhid hid nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel drm_km> Apr 23 10:07:43 surprise kernel: CPU: 9 PID: 0 Comm: swapper/9 Tainted: P OE 5.4.0-26-generic #30-Ubuntu Apr 23 10:07:43 surprise kernel: Hardware name: Gigabyte Technology Co., Ltd. B450M DS3H/B450M DS3H-CF, BIOS F4 01/25/2019 Apr 23 10:07:43 surprise kernel: RIP: 0010:dev_watchdog+0x258/0x260 Apr 23 10:07:43 surprise kernel: Code: 85 c0 75 e5 eb 9f 4c 89 ff c6 05 bf 06 e8 00 01 e8 6d bb fa ff 44 89 e9 4c 89 fe 48 c7 c7 50 6d a3 b4 48 89 c2 e8 83 3f 71 ff <0f> 0b eb 80 0f 1f 40 00 0f 1f 44 00 00 55 48 89 e5 41 57 49 89 d7 Apr 23 10:07:43 surprise kernel: RSP: 0018:a90d40378e30 EFLAGS: 00010286 Apr 23 10:07:43 surprise kernel: RAX: RBX: 8a7578b00400 RCX: Apr 23 10:07:43 surprise kernel: RDX: 8a758ee67740 RSI: 8a758ee578c8 RDI: 0300 Apr 23 10:07:43 surprise kernel: RBP: a90d40378e60 R08: 8a758ee578c8 R09: 0004 Apr 23 10:07:43 surprise kernel: R10: R11: 0001 R12: 0001 Apr 23 10:07:43 surprise kernel: R13: R14: 8a758cadc480 R15: 8a758cadc000 Apr 23 10:07:43 surprise kernel: FS: () GS:8a758ee4() knlGS: Apr 23 10:07:43 surprise kernel: CS: 0010 DS: ES: CR0: 80050033 Apr 23 10:07:43 surprise kernel: CR2: 7f4d2000d5eb CR3: 0003fcfe2000 CR4: 003406e0 Apr 23 10:07:43 surprise kernel: Call Trace: Apr 23 10:07:43 surprise kernel: Apr 23 10:07:43 surprise kernel: ? pfifo_fast_enqueue+0x150/0x150 Apr 23 10:07:43 surprise kernel: call_timer_fn+0x32/0x130 Apr 23 10:07:43 surprise kernel: __run_timers.part.0+0x180/0x280 Apr 23 10:07:43 surprise kernel: ? tick_sched_handle+0x33/0x60 Apr 23 10:07:43 surprise kernel: ? tick_sched_timer+0x3d/0x80 Apr 23 10:07:43 surprise kernel: ? ktime_get+0x3e/0xa0 Apr 23 10:07:43 surprise kernel: run_timer_softirq+0x2a/0x50 Apr 23 10:07:43 surprise kernel: __do_softirq+0xe1/0x2d6 Apr 23 10:07:43 surprise kernel: ? hrtimer_interrupt+0x13b/0x220
[Kernel-packages] [Bug 1882312] Re: RAID5 reshape stuck due to same badblock on multiple devices
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/ If mainline kernel doesn't work please raise the issue to mailing list. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882312 Title: RAID5 reshape stuck due to same badblock on multiple devices Status in linux package in Ubuntu: Confirmed Bug description: Linux [hostname removed] 5.3.0-55-generic #49-Ubuntu SMP Thu May 21 12:47:19 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Ubuntu release: 19.10 (although the same issue is present in 18.04 and 20.04 as well). A RAID5 reshape from 3 to 4 devices got stuck: md127 : active raid5 sde1[5] sdd1[4] sdc1[0] sdf1[3] 7813769216 blocks super 1.2 level 5, 512k chunk, algorithm 2 [4/4] [] [>] reshape = 1.8% (72261116/3906884608) finish=1663133.7min speed=38K/sec bitmap: 0/30 pages [0KB], 65536KB chunk with the following stack trace: [54979.996871] INFO: task md127_reshape:7090 blocked for more than 1208 seconds. [54979.996922] Tainted: P OE 5.3.0-55-generic #49-Ubuntu [54979.996967] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [54979.997018] md127_reshape D0 7090 2 0x80004080 [54979.997019] Call Trace: [54979.997022] __schedule+0x2b9/0x6c0 [54979.997023] schedule+0x42/0xb0 [54979.997027] reshape_request+0x878/0x950 [raid456] [54979.997028] ? wait_woken+0x80/0x80 [54979.997030] raid5_sync_request+0x302/0x3b0 [raid456] [54979.997032] md_do_sync.cold+0x3ef/0x999 [54979.997034] ? ecryptfs_write_begin+0x70/0x280 [54979.997034] ? __switch_to_asm+0x40/0x70 [54979.997035] ? __switch_to_asm+0x34/0x70 [54979.997035] ? __switch_to_asm+0x40/0x70 [54979.997036] ? __switch_to_asm+0x34/0x70 [54979.997036] ? __switch_to_asm+0x40/0x70 [54979.997037] ? __switch_to_asm+0x34/0x70 [54979.997038] md_thread+0x97/0x160 [54979.997040] kthread+0x104/0x140 [54979.997040] ? md_start_sync+0x60/0x60 [54979.997041] ? kthread_park+0x80/0x80 [54979.997042] ret_from_fork+0x35/0x40 No other hardware errors were reported and the reshape got stuck at somewhat different blocks every time it was restarted (all within the same vicinity of each others). It turns out that md had injected the same exact sector into the badblock log of multiple devices at some point before the reshape was started. This could be seen with "mdadm --examine-badblocks /dev/sdXY". The original cause for the badblocks entries was probably a loose cable as the reported sectors were fully readable with the "dd" and "badblocks" command. The problem was eventually resolved by removing the badblock log on the RAID5 device using "mdadm --assemble /dev/md0 --update=force-no- bbl". Having removed the badblock log, reshape progressed beyond the previously troublesome area of blocks. I would have expected at least an error message in the kernel log rather than just a "hung task" message, probably before the reshape was allowed to be initiated (aka early termination). Furthermore, it would be beneficial if mdadm could allow the badblock log to be cleared for a device rather than removed on the array with "update=force-no-bbl". --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.3.0-55-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.11-0ubuntu8.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D2', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=/dev/mapper/vg0-swap IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: System manufacturer System Product Name NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: LC_CTYPE=en_US.UTF-8 TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine:
[Kernel-packages] [Bug 1886140] [NEW] drm_vram_helper crash when launching DM with MGA G200e
Public bug reported: [Description] The drm_vram_helper crash when launching display manager with MGA G200e. [Steps to reproduce] 0. Connect to a monitor via VGA 1. Install focal desktop image (5.4.0-21-generic) 2. Power on system and boot to multi-user.target 3. systemctl isolate graphical.target [Expect result] System launch GDM without problems [Actual result] System hang and monitor keep purple screen 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 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Fri Jul 3 13:27:53 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Lenovo ThinkSystem ST250 -[7Y45CTO1WW]- ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=68fd62d3-1204-4f51-a3b4-b35919882e7f ro systemd.unit=multi-user.target 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2020 dmi.bios.vendor: Lenovo dmi.bios.version: -[ISE116D-2.10]- dmi.board.asset.tag: none dmi.board.name: -[7Y45CTO1WW]- dmi.board.vendor: Lenovo dmi.board.version: none dmi.chassis.asset.tag: none dmi.chassis.type: 7 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.modalias: dmi:bvnLenovo:bvr-[ISE116D-2.10]-:bd04/24/2020:svnLenovo:pnThinkSystemST250-[7Y45CTO1WW]-:pvr03:rvnLenovo:rn-[7Y45CTO1WW]-:rvrnone:cvnLenovo:ct7:cvrnone: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem ST250 -[7Y45CTO1WW]- dmi.product.sku: 7Y45CTO1WW dmi.product.version: 03 dmi.sys.vendor: Lenovo ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886140 Title: drm_vram_helper crash when launching DM with MGA G200e Status in linux package in Ubuntu: New Bug description: [Description] The drm_vram_helper crash when launching display manager with MGA G200e. [Steps to reproduce] 0. Connect to a monitor via VGA 1. Install focal desktop image (5.4.0-21-generic) 2. Power on system and boot to multi-user.target 3. systemctl isolate graphical.target [Expect result] System launch GDM without problems [Actual result] System hang and monitor keep purple screen 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 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CasperMD5CheckResult: skip Date: Fri Jul 3 13:27:53 2020 InstallationDate: Installed on 2020-07-03 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Lenovo ThinkSystem ST250 -[7Y45CTO1WW]- ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-40-generic root=UUID=68fd62d3-1204-4f51-a3b4-b35919882e7f ro systemd.unit=multi-user.target 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 RfKill: SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/24/2020 dmi.bios.vendor: Lenovo dmi.bios.version: -[ISE116D-2.10]- dmi.board.asset.tag: none dmi.board.name: -[7Y45CTO1WW]- dmi.board.vendor: Lenovo dmi.board.version: none dmi.chassis.asset.tag: none dmi.chassis.type: 7 dmi.chassis.vendor: Lenovo dmi.chassis.version: none dmi.modalias: dmi:bvnLenovo:bvr-[ISE116D-2.10]-:bd04/24/2020:svnLenovo:pnThinkSystemST250-[7Y45CTO1WW]-:pvr03:rvnLenovo:rn-[7Y45CTO1WW]-:rvrnone:cvnLenovo:ct7:cvrnone: dmi.product.family: ThinkSystem dmi.product.name: ThinkSystem ST250 -[7Y45CTO1WW]- dmi.product.sku: 7Y45CTO1WW dmi.product.version: 03 dmi.sys.vendor: Lenovo To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886140/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885742] Re: USB devices unable to suspend, error -16
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885742 Title: USB devices unable to suspend, error -16 Status in linux package in Ubuntu: Incomplete Bug description: Unable to suspend, error -16 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 4.15.0-108.109-generic 4.15.18 Uname: Linux 4.15.0-108-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.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 390.138 Thu May 14 01:01:53 PDT 2020 GCC version: gcc version 7.5.0 (Ubuntu 7.5.0-3ubuntu1~18.04) ApportVersion: 2.20.9-0ubuntu7.15 Architecture: amd64 CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Tue Jun 30 20:57:50 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: nvidia, 390.138, 4.15.0-108-generic, x86_64: installed ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller [8086:0416] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Lenovo 4th Gen Core Processor Integrated Graphics Controller [17aa:3801] NVIDIA Corporation GK107M [GeForce GT 755M] [10de:0fcd] (rev a1) (prog-if 00 [VGA controller]) Subsystem: Lenovo GK107M [GeForce GT 755M] [17aa:3801] InstallationDate: Installed on 2018-08-29 (670 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: LENOVO 20217 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-108-generic root=UUID=2674d4c6-6617-45bc-bd72-c1ecec60a6e9 ro quiet splash nouveau.modeset=0 vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 1/30/2015 dmi.bios.vendor: LENOVO dmi.bios.version: 74CN47WW(V3.08) dmi.board.asset.tag: No Asset Tag dmi.board.name: VIQY0Y1 dmi.board.vendor: LENOVO dmi.board.version: 3194STD dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo IdeaPad Y510P dmi.modalias: dmi:bvnLENOVO:bvr74CN47WW(V3.08):bd1/30/2015:svnLENOVO:pn20217:pvrLenovoIdeaPadY510P:rvnLENOVO:rnVIQY0Y1:rvr3194STD:cvnLENOVO:ct10:cvrLenovoIdeaPadY510P: dmi.product.family: IDEAPAD dmi.product.name: 20217 dmi.product.version: Lenovo IdeaPad Y510P dmi.sys.vendor: LENOVO version.compiz: compiz N/A 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.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.19.6-1ubuntu4.4 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.0.1-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885742/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844247] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
This was actually fixed in Disco version 5.0.0-32.34 by bug 1845390.
** Changed in: linux (Ubuntu Disco)
Status: Won't Fix => Fix Released
** Changed in: linux (Ubuntu Eoan)
Status: Fix Committed => Invalid
** Changed in: linux (Ubuntu Focal)
Status: Fix Committed => 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/1844247
Title:
BT advertising packet wakes up the system from S3 and suspend-to-idle
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Invalid
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:
Invalid
Status in linux source package in Focal:
Invalid
Bug description:
[Impact]
The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1844247/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844247] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
This was actually fixed in Bionic version 4.15.0-66.75 by bug 1845266.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844247
Title:
BT advertising packet wakes up the system from S3 and suspend-to-idle
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Invalid
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:
Invalid
Status in linux source package in Focal:
Invalid
Bug description:
[Impact]
The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1844247/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844247] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
The fix commit 1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable
the usb-wakeup feature"") is included in v5.3 or above.
** Changed in: hwe-next
Status: New => Fix Released
** Changed in: linux (Ubuntu)
Status: Fix Committed => Invalid
** Changed in: linux (Ubuntu Bionic)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844247
Title:
BT advertising packet wakes up the system from S3 and suspend-to-idle
Status in HWE Next:
Fix Released
Status in linux package in Ubuntu:
Invalid
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:
Invalid
Status in linux source package in Focal:
Invalid
Bug description:
[Impact]
The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1844247/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886061] Re: Geth crashing, EXT4-error
Does nvme_core.default_ps_max_latency_us=0 help? ** 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/1886061 Title: Geth crashing, EXT4-error Status in linux package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04 LTS Release: 20.04 dpkg: Installed: 1.19.7ubuntu3 Candidate: 1.19.7ubuntu3 Version table: *** 1.19.7ubuntu3 500 500 http://no.archive.ubuntu.com/ubuntu focal/main amd64 Packages 100 /var/lib/dpkg/status Ubuntu Software 3.36.1 I tried running Geth on my computer. I have tried to run this manny times, but i keep getting a Ext4-fs error on my Nvme. I have tried to use the "nvme_core.default_ps_max_latency_us=6000" and "nvme_core.default_ps_max_latency_us=5500" but it keep crashing when i open Geth. I really have no ide how to use ubuntu so I have to apologize, but the crash report came up when i opened Geth this time so i tried to send it like this. If there is more info you need, i also apologize for not stating that here. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: william1642 F pulseaudio /dev/snd/controlC2: william1642 F pulseaudio /dev/snd/controlC1: william1642 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Jul 2 16:16:33 2020 InstallationDate: Installed on 2020-06-27 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8i7HNK ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=704d6e62-8bb8-4a2a-a495-aece2c2bdc6a ro quiet splash nvme_core.default_ps_max_latency_us=5500 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/12/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: HNKBLi70.86A.0059.2019.1112.1124 dmi.board.name: NUC8i7HNB dmi.board.vendor: Intel Corporation dmi.board.version: J68197-602 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrHNKBLi70.86A.0059.2019.1112.1124:bd11/12/2019:svnIntel(R)ClientSystems:pnNUC8i7HNK:pvrJ71486-603:rvnIntelCorporation:rnNUC8i7HNB:rvrJ68197-602:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: HN dmi.product.name: NUC8i7HNK dmi.product.version: J71486-603 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
it's a good start and we are closer to solve this problem -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853277] Re: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices
Hi Cristian Waimann, Sorry for the belated response. From the log, it's a good start and we Can you please attach `lsmod`? Is i2c-hid or hid-multitouch in blacklist? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853277 Title: Lenovo ThinkBook 14-IML Touchpad not showing up in /proc/bus/input/devices Status in linux package in Ubuntu: Confirmed Bug description: This is happening on a ThinkBook 14 IML 20RV. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-18-generic 5.3.0-18.19+1 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 Uname: Linux 5.3.0-18-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 1848 F pulseaudio CasperVersion: 1.427 CurrentDesktop: ubuntu:GNOME Date: Wed Nov 20 11:10:52 2019 LiveMediaBuild: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: LENOVO 20RV ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/username.seed quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.3.0-18-generic N/A linux-backports-modules-5.3.0-18-generic N/A linux-firmware1.183 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/10/2019 dmi.bios.vendor: LENOVO dmi.bios.version: CJCN21WW dmi.board.name: LVA/LVAB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.modalias: dmi:bvnLENOVO:bvrCJCN21WW:bd10/10/2019:svnLENOVO:pn20RV:pvrLenovoThinkBook14-IML:rvnLENOVO:rnLVA/LVAB:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvr: dmi.product.family: ThinkBook 14-IML dmi.product.name: 20RV dmi.product.sku: LENOVO_MT_20RV_BU_idea_FM_ThinkBook 14-IML dmi.product.version: Lenovo ThinkBook 14-IML dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853277/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1875199] Re: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all
Hmm, it does seems to be a PulseAudio regression. Can you please test 20.04 based Mint? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1875199 Title: [NUC8CCHK][HDA-Intel - HDA Intel PCH, playback] No sound at all Status in linux package in Ubuntu: Incomplete Bug description: No sound output. Only a 'Dummy' audio output device is listed in the Gnome Sound application. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: pulseaudio 1:13.99.1-1ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sun Apr 26 12:12:49 2020 InstallationDate: Installed on 2020-04-25 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: pulseaudio Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:PCH successful Symptom_Card: Built-in Audio - HDA Intel PCH Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1205 F pulseaudio Symptom_PulsePlaybackTest: PulseAudio playback test failed Symptom_Type: No sound at all Title: [HDA-Intel - HDA Intel PCH, playback] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: rboerner 1215 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-25 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Intel(R) Client Systems NUC8CCHK 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-28-generic root=UUID=afbb0f64-e729-46a8-82e4-a060e9e729c4 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-28-generic N/A linux-backports-modules-5.4.0-28-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-28-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/25/2020 dmi.bios.vendor: Intel Corp. dmi.bios.version: CHAPLCEL.0048.2020.0225.1640 dmi.board.name: NUC8CCHB dmi.board.vendor: Intel Corporation dmi.board.version: K44767-502 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrCHAPLCEL.0048.2020.0225.1640:bd02/25/2020:svnIntel(R)ClientSystems:pnNUC8CCHK:pvrK44798-502:rvnIntelCorporation:rnNUC8CCHB:rvrK44767-502:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: CH dmi.product.name: NUC8CCHK dmi.product.sku: BKNUC8CCHKR dmi.product.version: K44798-502 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1875199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1660887] Re: package linux-base 4.0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux-tools-common 4.4.0-59.80
DistroRelease: Kali 2016.2 linux-base (4.5) Thank you for taking the time to report this bug and trying to help make Ubuntu better. However, it seems that you are not using a software package provided by the official Ubuntu repositories. Because of this the Ubuntu project can not support or fix your particular bug. Please report this bug to the provider of the software package. Thanks! If you are interested in learning more about software repositories and Ubuntu, check https://help.ubuntu.com/community/Repositories. ** Changed in: linux-base (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-base in Ubuntu. https://bugs.launchpad.net/bugs/1660887 Title: package linux-base 4.0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux-tools-common 4.4.0-59.80 Status in linux-base package in Ubuntu: Invalid Bug description: asdf ProblemType: Package DistroRelease: Kali 2016.2 Package: linux-base 4.5 ProcVersionSignature: Ubuntu 4.4.0-59.80-generic 4.4.35 Uname: Linux 4.4.0-59-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.5 Architecture: amd64 Date: Sun Jan 29 20:56:53 2017 Dependencies: ErrorMessage: trying to overwrite '/usr/bin/perf', which is also in package linux-tools-common 4.4.0-59.80 InstallationDate: Installed on 2016-09-30 (123 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) PackageArchitecture: all RelatedPackageVersions: dpkg 1.18.15kali1 apt 1.2.15ubuntu0.2 SourcePackage: linux-base Title: package linux-base 4.0ubuntu1 failed to install/upgrade: trying to overwrite '/usr/bin/perf', which is also in package linux-tools-common 4.4.0-59.80 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-base/+bug/1660887/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867455] Re: Having more than one AMD Radeon RX 580 installed will trigger a PCIe bus fatal error during boot.
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.8-rc3/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867455 Title: Having more than one AMD Radeon RX 580 installed will trigger a PCIe bus fatal error during boot. Status in linux package in Ubuntu: Confirmed Bug description: I have a Dell R920 with three MSI Radeon RX 580 8G V1 cards, if more than one of these cards is installed in the system, a bus fatal error will be generated causing the system to reset itself when the amdgpu module is loaded and it tries to initialize the device. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-modules-5.4.0-14-lowlatency 5.4.0-14.17 ProcVersionSignature: Ubuntu 5.4.0-14.17-lowlatency 5.4.18 Uname: Linux 5.4.0-14-lowlatency x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu20 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/controlC0', '/dev/snd/hwC0D0', '/dev/snd/pcmC0D9p', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: Date: Sat Mar 14 12:20:47 2020 Dependencies: MachineType: Dell Inc. PowerEdge R920 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 mgag200drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-14-lowlatency root=ZFS=rpool/ROOT/ubuntu ro intel_iommu=on iommu=pt root=ZFS=rpool/ROOT/ubuntu intremap=no_x2apic_optout ipv6.disable=1 mitigations=off PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-14-lowlatency N/A linux-backports-modules-5.4.0-14-lowlatency N/A linux-firmware 1.186 RfKill: SourcePackage: linux-5.4 UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 06/26/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.9.0 dmi.board.name: 0V7HD0 dmi.board.vendor: Dell Inc. dmi.board.version: A06 dmi.chassis.type: 23 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.9.0:bd06/26/2019:svnDellInc.:pnPowerEdgeR920:pvr:rvnDellInc.:rn0V7HD0:rvrA06:cvnDellInc.:ct23:cvr: dmi.product.name: PowerEdge R920 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1867455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[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
** Summary changed: - Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu + Intel Wireless 8260 [8086:24f3] Subsystem [8086:9010] Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu -- 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: New 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 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
The attachment "procps debdiff for Groovy" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) CONFIG_SECURITY_DMESG_RESTRICT=y in the kernel. 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. 3) Add a commented out '# kernel.dmesg_restrict = 0' to /etc/sysctl.d/10-kernel-hardening.conf For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable
[Kernel-packages] [Bug 1885496] Re: Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu
** Tags added: hwe-bluetooth -- 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: New 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: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0045.2016.0527.1055:bd05/27/2016:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-504:cvn:ct3:cvr: hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:F8:FA:D3 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:14600494 acl:95 sco:0
[Kernel-packages] [Bug 1869799] Re: no sound driver since 5.3.0.42 kernel
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1869799 Title: no sound driver since 5.3.0.42 kernel Status in linux package in Ubuntu: Expired Bug description: no sound driver since 5.3.0.42 kernel, 5.3.0.45 kernel doesn't solve the problem. i have only a dummy soundcard. no sound. 5.3.0.42 kernel works fine. my sound card is intel 100 / c230 hd audio To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1869799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886134] Re: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted
*** This bug is a duplicate of bug 1883976 *** https://bugs.launchpad.net/bugs/1883976 Please stop Sophos Antivirus while upgrading/installing kernel related packages: $ sudo systemctl stop sav-protect.service ** This bug has been marked a duplicate of bug 1883976 package linux-modules-extra-5.4.0-37-generic (not installed) failed to install/upgrade: impossible de créer le fichier « /var/lib/dpkg/info/linux-modules-extra-5.4.0-37-generic.list-new »: Opération non permise -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1886134 Title: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: Package failed to install in Ubuntu 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yashraj1905 F pulseaudio /dev/snd/controlC0: yashraj1905 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jul 3 08:58:49 2020 Dependencies: DuplicateSignature: package:linux-firmware:1.187 Unpacking linux-firmware (1.187.1) over (1.187) ... dpkg: error processing archive /tmp/apt-dpkg-install-u6WwHC/35-linux-firmware_1.187.1_all.deb (--unpack): unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-06-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20351 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=afb29fcd-1923-4732-8559-837e755561ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux-firmware Title: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82990WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrSDK0F82990WIN:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1886134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886134] Re: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted
*** This bug is a duplicate of bug 1883976 *** https://bugs.launchpad.net/bugs/1883976 ** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1886134 Title: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: Package failed to install in Ubuntu 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yashraj1905 F pulseaudio /dev/snd/controlC0: yashraj1905 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jul 3 08:58:49 2020 Dependencies: DuplicateSignature: package:linux-firmware:1.187 Unpacking linux-firmware (1.187.1) over (1.187) ... dpkg: error processing archive /tmp/apt-dpkg-install-u6WwHC/35-linux-firmware_1.187.1_all.deb (--unpack): unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-06-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20351 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=afb29fcd-1923-4732-8559-837e755561ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux-firmware Title: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82990WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrSDK0F82990WIN:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1886134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886134] [NEW] package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted
Public bug reported: Package failed to install in Ubuntu 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yashraj1905 F pulseaudio /dev/snd/controlC0: yashraj1905 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jul 3 08:58:49 2020 Dependencies: DuplicateSignature: package:linux-firmware:1.187 Unpacking linux-firmware (1.187.1) over (1.187) ... dpkg: error processing archive /tmp/apt-dpkg-install-u6WwHC/35-linux-firmware_1.187.1_all.deb (--unpack): unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-06-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20351 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=afb29fcd-1923-4732-8559-837e755561ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux-firmware Title: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82990WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo G50-70 dmi.modalias: dmi:bvnLENOVO:bvr9ACN28WW:bd09/23/2014:svnLENOVO:pn20351:pvrLenovoG50-70:rvnLENOVO:rnLancer5A2:rvrSDK0F82990WIN:cvnLENOVO:ct10:cvrLenovoG50-70: dmi.product.family: IDEAPAD dmi.product.name: 20351 dmi.product.sku: LENOVO_MT_20351_BU_idea_FM_Lenovo G50-70 dmi.product.version: Lenovo G50-70 dmi.sys.vendor: LENOVO ** Affects: linux-firmware (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1886134 Title: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted Status in linux-firmware package in Ubuntu: New Bug description: Package failed to install in Ubuntu 20.04 ProblemType: Package DistroRelease: Ubuntu 20.04 Package: linux-firmware 1.187 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.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: yashraj1905 F pulseaudio /dev/snd/controlC0: yashraj1905 F pulseaudio CasperMD5CheckResult: skip Date: Fri Jul 3 08:58:49 2020 Dependencies: DuplicateSignature: package:linux-firmware:1.187 Unpacking linux-firmware (1.187.1) over (1.187) ... dpkg: error processing archive /tmp/apt-dpkg-install-u6WwHC/35-linux-firmware_1.187.1_all.deb (--unpack): unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted ErrorMessage: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted InstallationDate: Installed on 2020-06-10 (22 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20351 PackageArchitecture: all ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=afb29fcd-1923-4732-8559-837e755561ce ro quiet splash vt.handoff=7 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: grub-pc 2.04-1ubuntu26 SourcePackage: linux-firmware Title: package linux-firmware 1.187 failed to install/upgrade: unable to open '/lib/firmware/yamaha/ds1_dsp.fw.dpkg-new': Operation not permitted UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/23/2014 dmi.bios.vendor: LENOVO dmi.bios.version: 9ACN28WW dmi.board.asset.tag: No Asset Tag dmi.board.name: Lancer 5A2 dmi.board.vendor: LENOVO dmi.board.version: SDK0F82990WIN
[Kernel-packages] [Bug 1883598] Re: efi: Restrict efivar_ssdt_load when the kernel is locked down
Looks like this has been addressed in bug 1884159: https://lists.ubuntu.com/archives/kernel-team/2020-June/111233.html https://lists.ubuntu.com/archives/kernel-team/2020-June/111200.html https://lists.ubuntu.com/archives/kernel-team/2020-June/111207.html I can see this patch in F/E/D/B As we don't have __init efivar_ssdt_setup() in xenial, do we still need this? Thanks ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883598 Title: efi: Restrict efivar_ssdt_load when the kernel is locked down Status in linux package in Ubuntu: Incomplete Bug description: Upstream git commit 1957a85b0032 needs to be backported to older releases: efi: Restrict efivar_ssdt_load when the kernel is locked down efivar_ssdt_load allows the kernel to import arbitrary ACPI code from an EFI variable, which gives arbitrary code execution in ring 0. Prevent that when the kernel is locked down. Code introduced in 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f break-fix: 475fb4e8b2fd1d7b406ff3a7d21bc89a1e6f 1957a85b0032a81e6482ca4aab883643b8dae06e To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883598/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1876707] Re: NULL pointer dereference in nvme reset work-queue when VMD raid mode and SecureBoot turned on simultaneously on TigerLake
Landed to unstable already. Wait groovy kernel to be uplifted to v5.7 or v5.8
from unstable to
automatically include this fix.
** Changed in: linux (Ubuntu Groovy)
Status: In Progress => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.6 in Ubuntu.
https://bugs.launchpad.net/bugs/1876707
Title:
NULL pointer dereference in nvme reset work-queue when VMD raid mode
and SecureBoot turned on simultaneously on TigerLake
Status in HWE Next:
New
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-5.6 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-oem-5.6 source package in Focal:
Fix Released
Status in linux source package in Groovy:
Confirmed
Status in linux-oem-5.6 source package in Groovy:
Invalid
Bug description:
[SRU Justfication]
[Impact]
On platforms with NVMe attached to VMD controller, enable SecureBoot
would also force enable iommu:
DMAR: Intel-IOMMU force enabled due to platform opt in
While devices behind the VMD controller, also a PCI bridge, maybe forced
to use a DMA domain by current Intel-IOMMU driver, this may break some
relationships between sub devices behind VMD controller and between the
VMD controller and its children devices, and finally caused undefined
system behavior.
On devices at hand, this results in kernel NULL dereference at
__intel_map_single called from nvme_reset_work and fails root device
lookup at boot.
kernel: BUG: kernel NULL pointer dereference, address: 0018
kernel: #PF: supervisor read access in kernel mode
kernel: #PF: error_code(0x) - not-present page
kernel: PGD 0 P4D 0
kernel: Oops: [#2] SMP NOPTI
kernel: CPU: 1 PID: 254 Comm: kworker/u8:4 Tainted: G D W
5.7.0-050700rc3-generic #202004262131
kernel: Hardware name: Dell Inc. Vostro 5402/, BIOS 0.1.2 04/13/2020
kernel: Workqueue: nvme-reset-wq nvme_reset_work [nvme]
kernel: RIP: 0010:__intel_map_single+0xa3/0x1a0
...
[Fix]
Patchset[1] currently landed in iommu/next beginning with commit
327d5b2fee91 ("iommu/vt-d: Allow 32bit devices to uses DMA domain")
gives the solution to this problem. However, it's based on a massive
subsystem rewrite in patchset[2], currently in iommu/next beginning with
commit 441ff2ff8327 ("Move default domain allocation to separate
function").
On v5.6, it also depends on yet a few more patch series landed in
v5.7-rc1 beginning with commit 098accf2da94 ("iommu: Use C99 flexible
array in fwspec") that rewrote private data access, changed struct
names, etc.
Yet a few additional patches included as fixes to above changes.
[1]:
https://lore.kernel.org/linux-iommu/7928dd48-93da-62f0-b455-6e6b248d0...@linux.intel.com/
[2]:
https://lore.kernel.org/linux-iommu/20200429133712.31431-1-j...@8bytes.org/
[Test Case]
Test on platforms with VMD/NVMe and enable SecureBoot. System should
boot normally rather than into initramfs emergency shell.
[Regression Potential]
For unstable, all the patches are from iommu-next and will probably be
merged in next few -rc releases, so should be safe to place a LOW here.
For oem-5.6, the fixing patchset is depending on iommu group setup
refactoring that touched almost every architecture/platform uses iommu
although we would only care amd64 among them. Even with follow-up fixes
included, this is still a 60-patches change and deserves some more
attention. Medium.
== Original Bug Description ==
This is found on a Dell TigerLake platform that when VMD raid mode is
turned on along with SecureBoot, either deploy mode or audit mode,
kernel dumps warnings and null pointer deref errors at boot. While it
happens, it blocks systemd-udevd worker processes until killed due to
timeout. System still boots to multi-users.target.
Kernel bisect shows commit e3560ee4cfb2 ("iommu/vt-d: Remove VMD child
device sanity check") merged in v5.6-rc1 is the first commit to fail,
and is still reproducible on v5.7-rc3.
kernel: Secure boot disabled
...
kernel: [ cut here ]
kernel: WARNING: CPU: 1 PID: 8 at drivers/iommu/intel-iommu.c:625
domain_get_iommu+0x4b/0x60
kernel: Modules linked in: rc_core r8169(+) intel_lpss nvme crc32_pclmul(+)
psmouse intel_ish_ipc(+) i2c_hid i2c_i801(+) realtek idma64 drm virt_dma
intel_ishtp vmd(+) nvme_core hid video wmi pinctrl_tigerlake pinctrl_intel
kernel: CPU: 1 PID: 8 Comm: kworker/u8:0 Not tainted 5.7.0-050700rc3-generic
#202004262131
kernel: Hardware name: Dell Inc. Vostro 5402/, BIOS 0.1.2 04/13/2020
kernel: Workqueue: nvme-reset-wq nvme_reset_work [nvme]
kernel: RIP: 0010:domain_get_iommu+0x4b/0x60
kernel: Code: eb 22 48 8d 50 01 48 39 c8 74 1b 48 89 d0 8b 74 87 04 48 63 d0
85 f6 74 e9 48 8b 05 ef 63 63 01 48 8b 04 d0 5d c3 31 c0 5d c3 <0f> 0b 31 c0 5d
c3 66
[Kernel-packages] [Bug 1864233] Re: Commits to resolve high network latency
** Changed in: linux-azure-4.15 (Ubuntu)
Status: New => Fix Released
** Changed in: linux-azure (Ubuntu)
Status: New => 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/1864233
Title:
Commits to resolve high network latency
Status in linux-azure package in Ubuntu:
Fix Released
Status in linux-azure-4.15 package in Ubuntu:
Fix Released
Status in linux-azure source package in Xenial:
Fix Released
Status in linux-azure-4.15 source package in Xenial:
Invalid
Status in linux-azure source package in Bionic:
Invalid
Status in linux-azure-4.15 source package in Bionic:
Fix Released
Bug description:
An issue has been identified with the NETVSC driver on Azure VMs. This
issues has been fixed by four patches, which are available in the
mainline kernel.
The issues is the following:
Outgoing traffic is sent from the guest to the Azure host over multiple
parallel channels. The issue causes the traffic to be unevenly balanced across
the channels, which results in a physical CPU on the Azure host becoming
overloaded. In turn, the network traffic on the overloaded channel experiences
significantly higher latency. This higher latency is causing issues for
customers.
This issue is resolved by the following four mainline commits:
71f21959dd55 ("hv_netvsc: Fix offset usage in netvsc_send_table()")
171c1fd98df3 ("hv_netvsc: Fix send_table offset in case of a host bug")
c39ea5cba5a2 ("hv_netvsc: Fix tx_table init in rndis_set_subchannel()")
b0689faa8efc ("hv_netvsc: Fix unwanted rx_table reset")
These four commits have been submitted to upstream stable.
We would like to request these commits in Azure kernels for Xenial and
Bionic
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1864233/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874685] Re: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash
Wait groovy kernel to be uplifted to v5.7 or v5.8 from unstable to automatically include this fix. ** Changed in: linux (Ubuntu Groovy) Status: In Progress => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1874685 Title: Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [8086:a0f0] subsystem id [1a56:1651] wireless adapter not found due to firmware crash Status in HWE Next: New 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: Invalid 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 Status in linux source package in Groovy: Confirmed Status in linux-oem-5.6 source package in Groovy: Fix Released Status in linux-oem-osp1 source package in Groovy: Invalid Bug description: [9.924130] iwlwifi :00:14.3: enabling device ( -> 0002) [ 10.031456] iwlwifi :00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 58.3.35.22 [ 10.031480] iwlwifi :00:14.3: Found debug destination: EXTERNAL_DRAM [ 10.031489] iwlwifi :00:14.3: Found debug configuration: 0 [ 10.033948] iwlwifi :00:14.3: loaded firmware version 50.3e391d3e.0 op_mode iwlmvm [ 10.218293] iwlwifi :00:14.3: Detected Killer(R) Wi-Fi 6 AX1650i 160MHz Wireless Network Adapter (201NGW), REV=0x354 [ 10.232843] iwlwifi :00:14.3: Applying debug destination EXTERNAL_DRAM [ 10.235398] iwlwifi :00:14.3: Allocated 0x0040 bytes for firmware monitor. [ 11.241180] iwlwifi :00:14.3: Collecting data: trigger 15 fired. [ 11.489274] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489293] iwlwifi :00:14.3: Status: 0x, count: -673266569 [ 11.489303] iwlwifi :00:14.3: Loaded firmware version: 50.3e391d3e.0 [ 11.489315] iwlwifi :00:14.3: 0x90F1F96A | ADVANCED_SYSASSERT [ 11.489323] iwlwifi :00:14.3: 0x7A7986FC | trm_hw_status0 [ 11.489331] iwlwifi :00:14.3: 0x09E990EC | trm_hw_status1 [ 11.489338] iwlwifi :00:14.3: 0x3073F272 | branchlink2 [ 11.489345] iwlwifi :00:14.3: 0xD569005D | interruptlink1 [ 11.489352] iwlwifi :00:14.3: 0xFEA17D01 | interruptlink2 [ 11.489359] iwlwifi :00:14.3: 0x4BBD0C7B | data1 [ 11.489367] iwlwifi :00:14.3: 0xB33DAF15 | data2 [ 11.489375] iwlwifi :00:14.3: 0xC8E4188F | data3 [ 11.489382] iwlwifi :00:14.3: 0xDEC3F4B3 | beacon time [ 11.489389] iwlwifi :00:14.3: 0xD5B7AAC7 | tsf low [ 11.489395] iwlwifi :00:14.3: 0x00073EAF | tsf hi [ 11.489402] iwlwifi :00:14.3: 0xB943A8DA | time gp1 [ 11.489409] iwlwifi :00:14.3: 0x6CCF8627 | time gp2 [ 11.489417] iwlwifi :00:14.3: 0x7944BDC6 | uCode revision type [ 11.489424] iwlwifi :00:14.3: 0x3C9DCF39 | uCode version major [ 11.489431] iwlwifi :00:14.3: 0xAF537547 | uCode version minor [ 11.489439] iwlwifi :00:14.3: 0xBC11442E | hw version [ 11.489447] iwlwifi :00:14.3: 0x160C9445 | board version [ 11.489453] iwlwifi :00:14.3: 0x276F21F6 | hcmd [ 11.489460] iwlwifi :00:14.3: 0x022688AB | isr0 [ 11.489466] iwlwifi :00:14.3: 0xEBF64685 | isr1 [ 11.489473] iwlwifi :00:14.3: 0x9D16A85F | isr2 [ 11.489480] iwlwifi :00:14.3: 0x606C870F | isr3 [ 11.489488] iwlwifi :00:14.3: 0x1B3967BF | isr4 [ 11.489495] iwlwifi :00:14.3: 0xFFBCEAB8 | last cmd Id [ 11.489503] iwlwifi :00:14.3: 0xAEB80995 | wait_event [ 11.489512] iwlwifi :00:14.3: 0x95AD6DCD | l2p_control [ 11.489518] iwlwifi :00:14.3: 0x06D3D9B3 | l2p_duration [ 11.489526] iwlwifi :00:14.3: 0x51B4EEA2 | l2p_mhvalid [ 11.489533] iwlwifi :00:14.3: 0x51B8C323 | l2p_addr_match [ 11.489540] iwlwifi :00:14.3: 0x81E0114B | lmpm_pmg_sel [ 11.489548] iwlwifi :00:14.3: 0xF4D75F29 | timestamp [ 11.489555] iwlwifi :00:14.3: 0x1AFE14FD | flow_handler [ 11.489635] iwlwifi :00:14.3: Start IWL Error Log Dump: [ 11.489643] iwlwifi :00:14.3: Status: 0x, count: 7 [ 11.489652] iwlwifi :00:14.3: 0x201013F1 | ADVANCED_SYSASSERT [ 11.489659] iwlwifi :00:14.3: 0x | umac branchlink1 [ 11.489666] iwlwifi :00:14.3: 0x80465E6A | umac branchlink2 [ 11.489674] iwlwifi :00:14.3: 0x | umac
[Kernel-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
Attached is a debdiff for procps on Groovy. It adds a commented out entry to 10-kernel-hardening.conf which users can use to disable the setting if they wish. ** Patch added: "procps debdiff for Groovy" https://bugs.launchpad.net/ubuntu/+source/util-linux/+bug/1886112/+attachment/5389194/+files/lp1886112_procps_groovy.debdiff -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) CONFIG_SECURITY_DMESG_RESTRICT=y in the kernel. 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. 3) Add a commented out '# kernel.dmesg_restrict = 0' to /etc/sysctl.d/10-kernel-hardening.conf For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by uncommenting the sysctl in /etc/sysctl.d/10-kernel-hardening.conf. To manage notifications about this bug go to:
[Kernel-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output
** Description changed: - target machine does not have built-in speaker, and the monitor does not - have an audio output (like d-sub VGA) + For linux kernel (oem-b): + + [Impact] + On a Dell machine without internal spk and internal mic, after freshly + install the bionic on it, and users plug a headset, the sound couldn't + output from headset. + + [Fix] + reverse the order of headset mic and headphone mic + + [Test Case] + freshly install the bionic with this patch on that dell machine, + plug headset and play sound, we could hear the sound from headset. + + [Regression Risk] + Low, this patch only affects the machine without internal mic and + internal spk, and I already tested this patch on the machine without + internal mic and internal spk, it worked well. + + + + target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. ** No longer affects: linux (Ubuntu) ** No longer affects: linux (Ubuntu Bionic) ** Also affects: linux-oem (Ubuntu) Importance: Undecided Status: New ** No longer affects: pulseaudio (Ubuntu Bionic) ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux-oem (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-oem (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux-oem package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in linux-oem source package in Bionic: New Status in pulseaudio source package in Bionic: New Bug description: For linux kernel (oem-b): [Impact] On a Dell machine without internal spk and internal mic, after freshly install the bionic on it, and users plug a headset, the sound couldn't output from headset. [Fix] reverse the order of headset mic and headphone mic [Test Case] freshly install the bionic with this patch on that dell machine, plug headset and play sound, we could hear the sound from headset. [Regression Risk] Low, this patch only affects the machine without internal mic and internal spk, and I already tested this patch on the machine without internal mic and internal spk, it worked well. target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 320875] Re: pulseaudio produces lots of log messages
This bug was fixed 11 years ago. Please open a new bug for any new problem you are having. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/320875 Title: pulseaudio produces lots of log messages Status in ALSA driver: New Status in linux package in Ubuntu: Fix Released Status in pulseaudio package in Ubuntu: Fix Released Bug description: Binary package hint: pulseaudio pulseaudio 0.9.14-0ubuntu1 produces these log messages: alsa-util.c: Cannot find fallback mixer control "PCM" or mixer control is no combination of switch/volume. alsa-util.c: snd_pcm_avail_update() returned a value that is exceptionally large: 412788 bytes (780 ms) Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. and thousands of this: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the PulseAudio developers. With pulseaudio 0.9.14-0ubuntu2 the error message changed to: module-alsa-sink.c: ALSA woke us up to write new data to the device, but there was actually nothing to write! Most likely this is an ALSA driver bug. Please report this issue to the ALSA developers. We were woken up with POLLOUT set -- however a subsequent snd_pcm_avail_update() returned 0. With pulseaudio 0.9.14-0ubuntu1 I have only these log messages, but no sound glitches any more. $ cat /proc/asound/cards 0 [Audigy2]: Audigy2 - Audigy 4 [SB0610] Audigy 4 [SB0610] (rev.0, serial:0x10211102) at 0x1000, irq 21 To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/320875/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882248] 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 1882248 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 ** Changed in: linux (Ubuntu Bionic) 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/1882248 Title: plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in pulseaudio source package in Bionic: New Bug description: target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885496] Re: Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu
bluetoothd still running is correct and not a bug. Also, rfkill appears to show that the GUI/BlueZ has disabled the kernel device as much as it can: 0: hci0: Bluetooth Soft blocked: yes So this is either a kernel bug or something missing from BlueZ's soft- blocking support. ** Changed in: bluez (Ubuntu) Importance: Undecided => Medium ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1885496 Title: Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu Status in bluez package in Ubuntu: New 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
[Kernel-packages] [Bug 1885496] 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 bluez in Ubuntu. https://bugs.launchpad.net/bugs/1885496 Title: Bluetooth is disabled in gui, but audio reciever's action button still controls Ubuntu Status in bluez package in Ubuntu: New 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: dmi:bvnIntelCorp.:bvrSYSKLi35.86A.0045.2016.0527.1055:bd05/27/2016:svn:pn:pvr:rvnIntelcorporation:rnNUC6i5SYB:rvrH81131-504:cvn:ct3:cvr: hciconfig: hci0:Type: Primary Bus: USB BD Address: 00:C2:C6:F8:FA:D3 ACL MTU: 1021:4 SCO MTU: 96:6 DOWN RX bytes:14600494 acl:95 sco:0
[Kernel-packages] [Bug 1882248] Re: plug headset won't proper reconfig ouput to it on machine with default output
** Also affects: oem-priority/bionic Importance: Undecided Status: New ** No longer affects: oem-priority/bionic ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: pulseaudio (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) ** Tags added: originate-from-1881842 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882248 Title: plug headset won't proper reconfig ouput to it on machine with default output Status in HWE Next: New Status in OEM Priority Project: Confirmed Status in linux package in Ubuntu: New Status in pulseaudio package in Ubuntu: New Status in linux source package in Bionic: New Status in pulseaudio source package in Bionic: New Bug description: target machine does not have built-in speaker, and the monitor does not have an audio output (like d-sub VGA) As first boot, there will be a "dummy output" in g-c-c. After plug-in headset, there will be a headset appear in g-c-c, but it won't be automatically selected even it's chosen in the pop-up window. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1882248/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
I think I have already been able to solve it. Attach the file. ** Attachment added: "acpidata.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884288/+attachment/5389187/+files/acpidata.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag:
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
I have found the following article but it is in Spanish. I don't know if what this article says you have already tried: https://ubunlog.com/no-te-funciona-bien-el-touchpad-en-plasma-prueba-esto/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Me from an error: sudo acpidump > acpidata.dat sudo: acpidump: command not found -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string
[Kernel-packages] [Bug 1730924]
Created attachment 290067 mwifiex crash log on SB1 with ps_on, 5GHzAP - power_save on - connected to 5GHz AP - connection instability (ping not responding) - firmware crashing eventually Journal log and devcoredump are included in the archive. I kept sending ping to 192.168.1.1 and the output was redirected to kmsg to show connection stability state. $ ping 192.168.1.1 | sudo tee /dev/kmsg [...] 64 bytes from 192.168.1.1: icmp_seq=5798 ttl=255 time=3.81 ms 64 bytes from 192.168.1.1: icmp_seq=5799 ttl=255 time=3.50 ms 64 bytes from 192.168.1.1: icmp_seq=5800 ttl=255 time=7.16 ms # # connection stopped suddenly # From 192.168.1.59 icmp_seq=5830 Destination Host Unreachable From 192.168.1.59 icmp_seq=5831 Destination Host Unreachable From 192.168.1.59 icmp_seq=5832 Destination Host Unreachable [...] From 192.168.1.59 icmp_seq=6019 Destination Host Unreachable From 192.168.1.59 icmp_seq=6020 Destination Host Unreachable From 192.168.1.59 icmp_seq=6025 Destination Host Unreachable # # connection started working again # 64 bytes from 192.168.1.1: icmp_seq=5801 ttl=255 time=230664 ms 64 bytes from 192.168.1.1: icmp_seq=5802 ttl=255 time=229660 ms 64 bytes from 192.168.1.1: icmp_seq=5803 ttl=255 time=228647 ms [...] 64 bytes from 192.168.1.1: icmp_seq=6082 ttl=255 time=7.24 ms 64 bytes from 192.168.1.1: icmp_seq=6083 ttl=255 time=80.0 ms 64 bytes from 192.168.1.1: icmp_seq=6084 ttl=255 time=6.73 ms # # firmware crashed suddenly # ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable ping: sendmsg: Network is unreachable [...] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730924]
(In reply to Pali Rohár from comment #127) > Hello! Hello! > Tsuchiya & Verdre: Do you have some fixes for instability issues when card > is in 5GHz AP mode? This is issue which we are observing on 88W8997 SDIO > wifi chips. Unfortunately, not yet. I'm using 5GHz AP with just power_save off. Maybe all what we can do about power_save and firmware crashing is submitting a journal log and devcoredump. I'll attach them in the next comment. > I described some problems related to power save mode, nl80211/cfg80211 layer > and mwifiex driver in email which I sent to linux-wireless mailing list: > https://lore.kernel.org/linux-wireless/20200609111544.v7u5ort3yk4s7coy@pali/ Thank you for letting us know! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730924]
Hi Ganapathi, We can't do anything about power_save and firmware crashing. So, I attached journal log and devcoredump when using with power_save on and 5GHz AP, containing 1) connection instability and 2) firmware crashing eventually. I hope it helps in debugging. 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/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730924]
Created attachment 290043 attachment-26841-0.html As of 6-DEC-2019, NXP has acquired Marvell’s Wireless business unit. You can now reach me at amitkumar.kar...@nxp.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1730924]
Hello! Tsuchiya & Verdre: Do you have some fixes for instability issues when card is in 5GHz AP mode? This is issue which we are observing on 88W8997 SDIO wifi chips. I described some problems related to power save mode, nl80211/cfg80211 layer and mwifiex driver in email which I sent to linux-wireless mailing list: https://lore.kernel.org/linux- wireless/20200609111544.v7u5ort3yk4s7coy@pali/ But I have not got any response about it yet and I think that without fixing those issues at cfg80211 layer we cannot fix mwifiex driver for power save mode. Andy, are you still able to help us with (generic/cfg80211) wireless part? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1730924 Title: Wifi does down "crash" in Surface Pro 4 Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: I have a Surface Pro 4. The wifi works well in principle, but unfortunately it drops every x minutes. The only way to fix it I've found is to reboot the computer. lsb_release -rd Description:Ubuntu 17.10 Release:17.10 ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: linux-image-4.13.0-16-generic 4.13.0-16.19 ProcVersionSignature: Ubuntu 4.13.0-16.19-generic 4.13.4 Uname: Linux 4.13.0-16-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: predatux 1537 F pulseaudio CurrentDesktop: KDE Date: Wed Nov 8 10:41:26 2017 HibernationDevice: RESUME=UUID=147af4ba-a4ce-41fe-a176-b36a1f6a590b Lsusb: Bus 002 Device 002: ID 045e:090c Microsoft Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 045e:07e8 Microsoft Corp. Bus 001 Device 003: ID 1286:204c Marvell Semiconductor, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Microsoft Corporation Surface Pro 4 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.13.0-16-generic root=UUID=125200b0-7377-4985-a217-15503781a525 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.13.0-16-generic N/A linux-backports-modules-4.13.0-16-generic N/A linux-firmware 1.169 SourcePackage: linux UpgradeStatus: Upgraded to artful on 2017-10-22 (16 days ago) dmi.bios.date: 02/24/2017 dmi.bios.vendor: Microsoft Corporation dmi.bios.version: 106.1624.768 dmi.board.name: Surface Pro 4 dmi.board.vendor: Microsoft Corporation dmi.chassis.type: 9 dmi.chassis.vendor: Microsoft Corporation dmi.modalias: dmi:bvnMicrosoftCorporation:bvr106.1624.768:bd02/24/2017:svnMicrosoftCorporation:pnSurfacePro4:pvrD0B08F1C03P38:rvnMicrosoftCorporation:rnSurfacePro4:rvr:cvnMicrosoftCorporation:ct9:cvr: dmi.product.family: Surface dmi.product.name: Surface Pro 4 dmi.product.version: D:0B:08F:1C:03P:38 dmi.sys.vendor: Microsoft Corporation To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1730924/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886112] Re: Enabling DMESG_RESTRICT in Groovy Onward
Kernel is fix-committed as per: Mailing list: https://lists.ubuntu.com/archives/ubuntu-devel/2020-July/041079.html Commit: https://kernel.ubuntu.com/git/ubuntu/unstable.git/commit/?id=25e6c851704a47c81e78e1a82530ac4b328098a6 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1886112 Title: Enabling DMESG_RESTRICT in Groovy Onward Status in linux package in Ubuntu: Fix Committed Status in procps package in Ubuntu: In Progress Status in util-linux package in Ubuntu: In Progress Status in linux source package in Groovy: Fix Committed Status in procps source package in Groovy: In Progress Status in util-linux source package in Groovy: In Progress Bug description: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) CONFIG_SECURITY_DMESG_RESTRICT=y in the kernel. 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. 3) Add a commented out '# kernel.dmesg_restrict = 0' to /etc/sysctl.d/10-kernel-hardening.conf For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by uncommenting the sysctl in /etc/sysctl.d/10-kernel-hardening.conf. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1886112/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to :
[Kernel-packages] [Bug 1886112] [NEW] Enabling DMESG_RESTRICT in Groovy Onward
Public bug reported: [Impact] This bug implements the enablement of CONFIG_SECURITY_DMESG_RESTRICT feature by default for Groovy onward, proposed to ubuntu-devel: https://lists.ubuntu.com/archives/ubuntu-devel/2020-June/041063.html The kernel log buffer contains a wealth of sensitive information, such as detailed call traces and kernel addresses found in register dumps in kernel oops messages. Exploit developers and attackers can leverage these information leaks to get past KASLR, and they can use the kernel log buffer to get instant feedback on their privilege escalation attacks, as failures will be shown as further oops messages, which attackers can use to fix and tune their programs until they work. Currently, if I create a new, unprivileged user on a Focal system, they cannot access /var/log/kern.log, /var/log/syslog or see system events in journalctl. But yet, they are given free reign to the kernel log buffer. $ sudo adduser dave $ su dave $ groups dave $ cat /var/log/kern.log cat: /var/log/kern.log: Permission denied $ cat /var/log/syslog cat: /var/log/syslog: Permission denied $ journalctl Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Jun 16 23:44:59 ubuntu systemd[2328]: Reached target Main User Target. Jun 16 23:44:59 ubuntu systemd[2328]: Startup finished in 69ms. $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... I propose that we restrict access to dmesg to users in group 'adm' like so: 1) CONFIG_SECURITY_DMESG_RESTRICT=y in the kernel. 2) Following changes to /bin/dmesg permissions in package 'util-linux' - Ownership changes to root:adm - Permissions changed to 0750 (-rwxr-x---) - Add cap_syslog capability to binary. 3) Add a commented out '# kernel.dmesg_restrict = 0' to /etc/sysctl.d/10-kernel-hardening.conf For most users, they will use the initial admin account, which is in the 'adm' group already, and will see no impact to these changes. If a log scraper type program needs access to dmesg, the user the daemon runs as can simply be added to the 'adm' group. [Testcase] Currently, all users can run /usr/bin/dmesg to view the kernel log buffer: $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... When the changes are applied, the default admin user will be able to view dmesg (since they are in group 'adm'), while new unprivileged users will not. $ whoami ubuntu $ groups ubuntu adm cdrom sudo dip plugdev $ dmesg [0.00] Linux version 5.4.0-34-generic (buildd at lcy01-amd64-014) (gcc version 9.3.0 (Ubuntu 9.3.0-10ubuntu2)) #38-Ubuntu SMP Mon May 25 15:46:55 UTC 2020 (Ubuntu 5.4.0-34.38-generic 5.4.41) [0.00] Command line: BOOT_IMAGE=/boot/vmlinuz-5.4.0-34-generic root=UUID=f9f909c3-782a-43c2-a59d-c789656b4188 ro ... $ sudo adduser dave $ su dave $ groups dave $ dmesg -bash: /usr/bin/dmesg: Permission denied [Regression Potential] Some users or log scraper type programs may need to view the kernel log buffer, or have access to dmesg. In this case, the underlying service user would need to be added to the 'adm' group. Users have the ability to disable DMESG_RESTRICT by uncommenting the sysctl in /etc/sysctl.d/10-kernel-hardening.conf. ** Affects: linux (Ubuntu) Importance: Undecided Status: Fix Committed ** Affects: procps (Ubuntu) Importance: Undecided Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: util-linux (Ubuntu) Importance: Undecided Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Fix Committed ** Affects: procps (Ubuntu Groovy) Importance: Undecided Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Affects: util-linux (Ubuntu Groovy) Importance: Undecided Assignee: Matthew Ruffell (mruffell) Status: In Progress ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Groovy) Status: New => Fix Committed ** Also affects: procps (Ubuntu) Importance: Undecided Status: New ** Changed in: procps (Ubuntu Groovy) Status: New => In Progress ** Changed in: procps (Ubuntu Groovy) Assignee: (unassigned) => Matthew Ruffell (mruffell) ** Also affects: util-linux
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Apologies, I meant .dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias:
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
@Califa, first run the following in terminal: sudo apt-get update sudo apt-get install acpi Then followed by: sudo acpidump > acpidata.dat You will then find the .day file saved in your home folder. I hope this will be of benefit to the developer(s) in trying to solve our problem. You have the touchpad working again in your video? If only it remained working after every restart :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version:
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Regardless of the above, watch the video at this link: https://photos.app.goo.gl/uZeUekJXSKyVpdiW9 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
@Ian, all in all, what I have to do is find the acpidata.dat file and attach it here, correct? Sorry, but I don't understand what is the purpose of attaching this file. Will the developers take it into account for something specific? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default
[Kernel-packages] [Bug 1872108] Re: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal
@Alejandro Miranda I've noticed the command moves the sound from the top speakers to the bottom. Sounds, no doubt, but seems to disable to speakers up top. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/1872108 Title: Bass not on working Lenovo ThinkPad X1 Carbon 7th gen running focal Status in alsa-ucm-conf package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1845677/comments/14 Audio works and the volume seems reasonable however the audio is noticeably missing bass giving everything a high treble sound. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-ucm-conf 1.2.2-1 ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Uname: Linux 5.4.0-21-generic x86_64 ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Fri Apr 10 09:17:33 2020 Dependencies: InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: alsa-ucm-conf UpgradeStatus: No upgrade log present (probably fresh install) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu26 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Dependencies: DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-04-08 (1 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200402) Package: linux PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27 Tags: focal Uname: Linux 5.4.0-21-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-ucm-conf/+bug/1872108/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
@Bjorn, bad news, I got stuck in compiling on this: """ ... BTF: .tmp_vmlinux.btf: pahole version v1.15 is too old, need at least v1.16 Failed to generate BTF for vmlinux Try to disable CONFIG_DEBUG_INFO_BTF ... """ I cannot compile newer Pahole (https://git.kernel.org/pub/scm/devel/pahole/pahole.git) since it gets interrupted with this error: """ ... CMake Error at CMakeLists.txt:55 (message): The submodules were not downloaded! GIT_SUBMODULE was turned off or failed. Please update submodules and try again. ... """ May I disable CONFIG_DEBUG_INFO_BTF as proposed? If so, where do I disable it? Thanks a lot #McZ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad doesn't work at all on ACER Spin 5 Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@ddstreet I'm not sure where upstream is going just yet. For Ubuntu; I think 1) Adjusting the bcache-tools patch to use the full path to bcache- super-show should change; 2) If we fix (1) then I think we can drop the systemd patch from a bug fixing perspective; on the openSUSE image I did testing on; the skip of the dev/disk/by-uuid symlink for backing devices does not *break* the /dev/bcache/by-uuid ; it was missing due to the updated 69-bcache.rules not working. 3) IMO, blkid should not report FS_UUID for bcache backing/cache devices since it's not a Filesystem; we could patch that in blkid directly instead; alternatively since older blkid's may or maynot emit FS_UUID for bcache backing/caching devices the patch to systemd we're caring will avoid creating a useless dev/disk/by-uuid symlink to those devices. -- 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 linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed 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 1840789] Re: bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
This fix has already been released as part of the kernel stable updates.
** Changed in: linux (Ubuntu Xenial)
Status: Incomplete => Opinion
** Changed in: linux (Ubuntu Xenial)
Status: Opinion => Fix Released
** Changed in: linux (Ubuntu Bionic)
Status: Incomplete => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1840789
Title:
bnx2x: fatal hardware error/reboot/tx timeout with LLDP enabled
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 Disco:
Won't Fix
Status in linux source package in Eoan:
Fix Released
Bug description:
[Impact]
* The bnx2x driver may cause hardware faults (leading to
panic/reboot) and other behaviors as transmit timeouts,
after commit 3968d38917eb ("bnx2x: Fix Multi-Cos.") is
introduced.
* This issue has been observed by an user shortly
after starting docker & kubelet, with adapters:
- Broadcom NetXtreme II BCM57800 [14e4:168a] from Dell [1028:1f5c]
- Broadcom NetXtreme II BCM57840 [14e4:16a1] from Dell [1028:1f79]
* If options to ignore hardware faults are used
(erst_disable=1 hest_disable=1 ghes.disable=1)
the system doesn't panic/reboot and continues
on to timeout on adapter stats, then transmit
timeouts, spewing some adapter firmware dumps,
but the network interface is non-functional.
* The issue only happened when LLDP is enabled
on the network switches, and crashdump shows
the bnx2x driver is stuck/waits for firmware
to complete the stop traffic command in LLDP
handling. Workaround used is to disable LLDP
in the network switches/ports.
* Analysis of the driver and firmware dumps
didn't help significantly towards finding
the root cause.
* Upstream/mainline recently just reverted the
patch, due to similar problem reports, while
looking for the root cause/proper fix.
[Test Case]
* No reproducible test case found outside
the user's systems/cluster, where it is
enough to start docker & kubelet & wait.
* The user verified test kernels for Xenial
and Bionic - the problem does not happen;
build-tested on Disco.
[Regression Potential]
* Users who significantly use/apply the non-default
traffic class (tc) / class of service (cos) might
possibly see performance changes (if any at all)
in such applications, however that's unclear now.
* This is a recent revert upstream (v5.3-rc'ish),
so there's chance things might change in this area.
* Nonetheless, the patch is authored by the driver
vendor, and made its way into stable kernels
(e.g., v5.2.8 which made Eoan/19.10 recently).
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840789/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1886105] [NEW] Disco update: upstream stable patchset 2020-07-02
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-02 Ported from the following upstream stable releases: v4.19.130, v.5.4.48 from git://git.kernel.org/ power: supply: bq24257_charger: Replace depends on REGMAP_I2C with select clk: sunxi: Fix incorrect usage of round_down() ASoC: tegra: tegra_wm8903: Support nvidia, headset property i2c: piix4: Detect secondary SMBus controller on AMD AM4 chipsets iio: pressure: bmp280: Tolerate IRQ before registering remoteproc: Fix IDR initialisation in rproc_alloc() clk: qcom: msm8916: Fix the address location of pll->config_reg backlight: lp855x: Ensure regulators are disabled on probe failure ASoC: davinci-mcasp: Fix dma_chan refcnt leak when getting dma type ARM: integrator: Add some Kconfig selections scsi: qedi: Check for buffer overflow in qedi_set_path() ALSA: hda/realtek - Introduce polarity for micmute LED GPIO ALSA: isa/wavefront: prevent out of bounds write in ioctl PCI: Allow pci_resize_resource() for devices on root bus scsi: qla2xxx: Fix issue with adapter's stopping state iio: bmp280: fix compensation of humidity f2fs: report delalloc reserve as non-free in statfs for project quota i2c: pxa: clear all master action bits in i2c_pxa_stop_message() clk: samsung: Mark top ISP and CAM clocks on Exynos542x as critical usblp: poison URBs upon disconnect serial: 8250: Fix max baud limit in generic 8250 port dm mpath: switch paths in dm_blk_ioctl() code path PCI: aardvark: Don't blindly enable ASPM L0s and don't write to read-only register ps3disk: use the default segment boundary vfio/pci: fix memory leaks in alloc_perm_bits() RDMA/mlx5: Add init2init as a modify command m68k/PCI: Fix a memory leak in an error handling path gpio: dwapb: Call acpi_gpiochip_free_interrupts() on GPIO chip de-registration mfd: wm8994: Fix driver operation if loaded as modules scsi: lpfc: Fix lpfc_nodelist leak when processing unsolicited event clk: clk-flexgen: fix clock-critical handling powerpc/perf/hv-24x7: Fix inconsistent output values incase multiple hv-24x7 events run nfsd: Fix svc_xprt refcnt leak when setup callback client failed PCI: vmd: Filter resource type bits from shadow register powerpc/crashkernel: Take "mem=" option into account pwm: img: Call pm_runtime_put() in pm_runtime_get_sync() failed case yam: fix possible memory leak in yam_init_driver NTB: ntb_pingpong: Choose doorbells based on port number NTB: Fix the default port and peer numbers for legacy drivers mksysmap: Fix the mismatch of '.L' symbols in System.map apparmor: fix introspection of of task mode for unconfined tasks ASoC: meson: add missing free_irq() in error path scsi: sr: Fix sr_probe() missing deallocate of device minor scsi: ibmvscsi: Don't send host info in adapter info MAD after LPM x86/purgatory: Disable various profiling and sanitizing options staging: greybus: fix a missing-check bug in gb_lights_light_config() arm64: dts: mt8173: fix unit name warnings scsi: qedi: Do not flush offload work if ARP not resolved ARM: dts: sun8i-h2-plus-bananapi-m2-zero: Fix led polarity gpio: dwapb: Append MODULE_ALIAS for platform driver scsi: qedf: Fix crash when MFW calls for protocol stats while function is still probing pinctrl: rza1: Fix wrong array assignment of rza1l_swio_entries firmware: qcom_scm: fix bogous abuse of dma-direct internals staging: gasket: Fix mapping refcnt leak when put attribute fails staging: gasket: Fix mapping refcnt leak when register/store fails ALSA: usb-audio: Improve frames size computation ALSA: usb-audio: Fix racy list management in output queue s390/qdio: put thinint indicator after early error slimbus: ngd: get drvdata from correct device thermal/drivers/ti-soc-thermal: Avoid dereferencing ERR_PTR usb: dwc3: gadget: Properly handle failed kick_transfer staging: sm750fb: add missing case while setting FB_VISUAL PCI: v3-semi: Fix a memory leak in v3_pci_probe() error handling paths i2c: pxa: fix i2c_pxa_scream_blue_murder() debug output serial: amba-pl011: Make sure we initialize the port.lock spinlock drivers: base: Fix NULL pointer exception in __platform_driver_probe() if a driver developer is foolish PCI: rcar: Fix incorrect programming of OB windows PCI/ASPM: Allow ASPM on links to PCIe-to-PCI/PCI-X Bridges scsi: qla2xxx: Fix warning after FC target reset power: supply: lp8788: Fix an error handling path in 'lp8788_charger_probe()' power: supply: smb347-charger: IRQSTAT_D is volatile scsi: mpt3sas: Fix double free warnings pinctrl: rockchip: fix memleak in
[Kernel-packages] [Bug 1816806] Re: Update ENA driver to version 2.0.3K
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1816806
Title:
Update ENA driver to version 2.0.3K
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux source package in Cosmic:
Fix Released
Status in linux source package in Disco:
Won't Fix
Bug description:
The following mainline commits are needed to update the Amazon ENA
driver to version 2.0.3K:
e76ad21d070f net: ena: fix crash during failed resume from hibernation
e1f1bd9bfbed net: ena: fix race between link up and device initalization
d9b8656da922 net: ena: update driver version from 2.0.2 to 2.0.3
All three commits are needed for {Xenial,Bionic,Cosmic}. Disco 4.19
already carries the first (e76a) so needs the other two.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816806/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
OK, compiling... once a while I see a warning like this: """ function 'walk_remove_by_peer.isra.0': /home/crysman/Downloads/kernels/unstable/drivers/net/wireguard/allowedips.c:121:1: warning: the frame size of 1032 bytes is larger than 1024 bytes [-Wframe-larger-than=] """ that is normal? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad doesn't work at all on ACER Spin 5 Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861941] Re: bcache by-uuid links disappear after mounting bcache0
@rbalint @raharper a commit is in the ubuntu-focal git repo for this: https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=3c228b1d9c5d83d7f0f7b7d8f2053a81de57f33c I was prepping focal for upload, but on reading the last few comments, should I revert that commit from the focal branch and upload the next systemd focal version without it? Or should it be included in the focal upload? Do we need to hold off on updating focal until it's resolved upstream? -- 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 linux package in Ubuntu: Incomplete Status in linux-signed package in Ubuntu: Confirmed 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 1845643] Re: test_maps in ubuntu_bpf failed on s390x Disco (libbpf: Error loading ELF section .BTF: -22. Ignored and continue.)
** Changed in: linux (Ubuntu Disco) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845643 Title: test_maps in ubuntu_bpf failed on s390x Disco (libbpf: Error loading ELF section .BTF: -22. Ignored and continue.) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Won't Fix Bug description: The ubuntu_bpf test failed on Disco s390x with: Failed to load SK_SKB parse prog stderr: libbpf: Error loading ELF section .BTF: -22. Ignored and continue. libbpf: object file doesn't contain bpf program To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845643/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
@Kai-Heng Feng, please see acpidata.dat attached. @Califa, please see https://sarata.com/manpages/acpidump.8.html ** Attachment added: "acpidata.dat" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884288/+attachment/5389157/+files/acpidata.dat -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
@Califa, also this: https://wiki.ubuntu.com/Kernel/Reference/ACPITricksAndTips Also, to address your doubt about CHUWI, I have also wondered exactly what you are saying, perhaps this acpidump is the first step in the right direction. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default
[Kernel-packages] [Bug 1884288] Re: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted
Please note, that acpidata.dat dump was ran with the touchpad working, should I run dump when touchpad is not working or does it matter? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884288 Title: LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted Status in linux package in Ubuntu: Confirmed Bug description: Touchpad completely ceases to work sometimes upon startup / restart. When this happens, I have to plug in an external mouse to navigate as touchpad is not even recognised as a device when I use xinput command in terminal. I removed and reinstalled xserver-xorg-input-synaptics which may have got it working again, although I am not too sure. When the trackpad is working, it's device name is listed as HTIX5288:00 0911:5288 Touchpad. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: xorg 1:7.7+19ubuntu14 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.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: skip CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 18:03:47 2020 DistUpgraded: Fresh install DistroCodename: focal DistroVariant: ubuntu ExtraDebuggingInterest: Yes, if not too technical GraphicsCard: Intel Corporation UHD Graphics 605 [8086:3185] (rev 03) (prog-if 00 [VGA controller]) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE.G140J.D8.E1.016.bin:bd11/29/2019:svn:pnLapBookPro:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct3:cvrDefaultstring: dmi.product.family: Default string dmi.product.name: LapBook Pro dmi.product.sku: Default string dmi.product.version: Default string version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.101-2 version.libgl1-mesa-dri: libgl1-mesa-dri 20.0.4-2ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.8-2ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200226-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ian1619 F pulseaudio CasperMD5CheckResult: skip DistroRelease: Ubuntu 20.04 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 008: ID 046d:c05a Logitech, Inc. M90/M100 Optical Mouse Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c549aad1-cbca-42d0-abc5-e73556f0921b ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.4.0-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: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 11/29/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E.G140J.D8.E1.016.bin dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 3 dmi.chassis.vendor: Default
[Kernel-packages] [Bug 1804481] Re: SecureBoot support for arm64
** Changed in: linux-meta (Ubuntu Disco) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1804481 Title: SecureBoot support for arm64 Status in linux package in Ubuntu: Fix Released Status in linux-meta package in Ubuntu: In Progress Status in linux-signed package in Ubuntu: Fix Released Status in linux-signed-hwe package in Ubuntu: Invalid Status in linux-signed-hwe-edge package in Ubuntu: New Status in shim package in Ubuntu: Fix Released Status in shim-signed package in Ubuntu: Fix Released Status in linux source package in Bionic: Triaged Status in linux-meta source package in Bionic: Triaged Status in linux-signed source package in Bionic: Triaged Status in linux-signed-hwe source package in Bionic: Fix Released Status in linux-signed-hwe-edge source package in Bionic: Fix Released Status in shim source package in Bionic: Fix Released Status in shim-signed source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Status in linux-meta source package in Cosmic: Triaged Status in linux-signed source package in Cosmic: Triaged Status in linux-signed-hwe source package in Cosmic: Invalid Status in linux-signed-hwe-edge source package in Cosmic: Invalid Status in shim source package in Cosmic: Fix Released Status in shim-signed source package in Cosmic: Triaged Status in linux source package in Disco: Fix Released Status in linux-meta source package in Disco: Won't Fix Status in linux-signed source package in Disco: Fix Released Status in linux-signed-hwe source package in Disco: Invalid Status in linux-signed-hwe-edge source package in Disco: Invalid Status in shim source package in Disco: Fix Released Status in shim-signed source package in Disco: Fix Released Bug description: [Impact] Ubuntu does not currently support SecureBoot for UEFI systems on arm64 platforms. [Test Case] See: https://wiki.ubuntu.com/UEFI/SecureBoot/Testing [Fix] - Introduce shim-signed for arm64 - Introduce grub-signed for arm64 - Produce signed linux kernels [Regression Risk] We're enabling new signed packages - regressions would most likely fall into packaging issues. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1804481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1811785] Re: NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
** Changed in: ndctl (Ubuntu Disco)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1811785
Title:
NVDIMM-N doesn't work properly on Dell EMC PowerEdge R840
Status in ndctl:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in ndctl package in Ubuntu:
Fix Released
Status in ndctl source package in Bionic:
Incomplete
Status in ndctl source package in Disco:
Won't Fix
Status in ndctl source package in Eoan:
Fix Released
Bug description:
On ubuntu 18.04.1 :
1°) With 4.15.0-43 two default namespaces in raw mode are visible
while there shouldn't be any but no settings change could be applied.
root@server:~# ndctl list -R
[
{
"dev":"region1",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":1,
"persistence_domain":"unknown"
},
{
"dev":"region0",
"size":103079215104,
"available_size":0,
"type":"pmem",
"numa_node":0,
"persistence_domain":"unknown"
}
]
root@server:~# ndctl list
[
{
"dev":"namespace1.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem1",
"numa_node":1
},
{
"dev":"namespace0.0",
"mode":"raw",
"size":103079215104,
"sector_size":512,
"blockdev":"pmem0",
"numa_node":0
}
]
root@server:~# ndctl create-namespace --reconfig=namespace1.0 --type=pmem
--mode=sector -f
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem10: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem7: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem9: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6: label area (1024) too small to host
(256 byte) labels
libndctl: sizeof_namespace_index: nmem6:
[Kernel-packages] [Bug 1802023] Re: hns3: map tx ring to tc
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802023 Title: hns3: map tx ring to tc Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Bug description: [Impact] hns3 supports hardware-based traffic classes. However, this requires that the driver map the classes to hardware rings during initialization. [Test Case] I don't have a way to verify that the hardware is behaving as programmed, so this is regression-tested only. [Fix] 1c77215480bcf net: hns3: Set tx ring' tc info when netdev is up [Regression Risk] Restricted to a single driver, which has been tested on the target SoC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1802023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844245] Re: Integrate Intel SGX driver into linux-azure
** Changed in: linux-azure (Ubuntu Disco) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1844245 Title: Integrate Intel SGX driver into linux-azure Status in linux package in Ubuntu: Fix Released Status in linux-azure package in Ubuntu: Fix Released Status in linux source package in Xenial: Fix Released 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: Fix Released Status in linux source package in Disco: Fix Released Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: Fix Released Status in linux-azure source package in Eoan: Fix Released Bug description: Intel is still trying to upstream the SGX driver, but in the meantime it would be desirable to have it available on the linux-azure kernel. The following version relies only on Kbuild: https://github.com/haimc-intel/SGXDataCenterAttestationPrimitives inker-ph1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1844245/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845641] Re: test_maps in ubuntu_bpf failed on i386 Disco ( run_parallel: Assertion `status == 0' failed.)
** Changed in: linux (Ubuntu Disco) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845641 Title: test_maps in ubuntu_bpf failed on i386 Disco ( run_parallel: Assertion `status == 0' failed.) Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Won't Fix Bug description: Like bug 1788580 for bionic, the ubuntu_bpf test failed on Disco i386 with: 9965. Fork 100 tasks to 'test_hashmap' 9966. Fork 100 tasks to 'test_hashmap_percpu' 9967. Fork 100 tasks to 'test_hashmap_sizes' 9968. Fork 100 tasks to 'test_hashmap_walk' 9969. helper_fill_hashmap(270):FAIL:failed to create hashmap err: Cannot allocate memory, flags: 0x0 9970. stderr: 9971. test_maps: test_maps.c:1286: __run_parallel: Assertion `status == 0' failed. 9972. 09/26 18:29:41 WARNI| test:0115| Programs crashed during test execution 9973. 09/26 18:29:41 WARNI| test:0117| Please verify /home/ubuntu/autotest/client/results/default/ubuntu_bpf.test_maps/debug/crash.test_maps.11955 for more info 9974. For the complete test log, please refer to the attachment. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839450] Re: ubuntu_ftrace_smoke_test failed on D-aws a1.medium arm64 instance
** Changed in: linux-aws (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1839450 Title: ubuntu_ftrace_smoke_test failed on D-aws a1.medium arm64 instance Status in ubuntu-kernel-tests: New Status in linux-aws package in Ubuntu: New Status in linux-aws source package in Disco: Won't Fix Bug description: Issue found on AWS ARM64 instance a1.medium, passed on the other 2 (a1.2xlarge / a1.large) Test failed with: FAILED (irq traces found must be > 32, got 18) PASSED (CONFIG_FUNCTION_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_FUNCTION_GRAPH_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_STACK_TRACER=y in /boot/config-5.0.0-1011-aws) PASSED (CONFIG_DYNAMIC_FTRACE=y in /boot/config-5.0.0-1011-aws) PASSED all expected /sys/kernel/debug/tracing files exist PASSED (function_graph in /sys/kernel/debug/tracing/available_tracers) PASSED (function in /sys/kernel/debug/tracing/available_tracers) PASSED (nop in /sys/kernel/debug/tracing/available_tracers) PASSED (function can be enabled) FAILED (irq traces found must be > 32, got 18) PASSED (function_graph can be enabled) PASSED (irq traces found must be > 32, got 9279) PASSED (tracer hwlat can be enabled (got 12 lines of tracing output)) PASSED (tracer blk can be enabled (got 2 lines of tracing output)) PASSED (tracer function_graph can be enabled (got 1374 lines of tracing output)) PASSED (tracer wakeup_dl can be enabled (got 2 lines of tracing output)) PASSED (tracer wakeup_rt can be enabled (got 66 lines of tracing output)) PASSED (tracer wakeup can be enabled (got 64 lines of tracing output)) PASSED (tracer function can be enabled (got 757 lines of tracing output)) Summary: 18 passed, 1 failed ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-1011-aws 5.0.0-1011.12 ProcVersionSignature: User Name 5.0.0-1011.12-aws 5.0.15 Uname: Linux 5.0.0-1011-aws aarch64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: arm64 Date: Thu Aug 8 10:56:19 2019 Ec2AMI: ami-0ac1a3bc4f5c85238 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2c Ec2InstanceType: a1.medium Ec2Kernel: unavailable Ec2Ramdisk: unavailable SourcePackage: linux-aws UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1839450/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1844247] Re: BT advertising packet wakes up the system from S3 and suspend-to-idle
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1844247
Title:
BT advertising packet wakes up the system from S3 and suspend-to-idle
Status in HWE Next:
New
Status in linux package in Ubuntu:
Fix Committed
Status in linux source package in Bionic:
Fix Committed
Status in linux source package in Disco:
Won't Fix
Status in linux source package in Eoan:
Fix Committed
Status in linux source package in Focal:
Fix Committed
Bug description:
[Impact]
The new feature added by below commit let BT device to wake up the system
from S3 or s2idle.
a0085f2510e8 ("Bluetooth: btusb: driver to enable the usb-wakeup feature")
But this feature also wakes up the system randomly from an unpaired BLE
device by its advertising packets.
[Fix]
There is no easy way to fix this and requires firmware update, so current
solution for this is to revert it.
1ffdb51f28e8 ("Revert "Bluetooth: btusb: driver to enable the usb-wakeup
feature"")
[Test]
Verified on machines which has paired BLE devices, and can't be waken up by
BT devices after entered suspended.
[Regression]
Yes, it reverts the feature by waking up system from s2idle by paired BT
devices, but this feature introduces regression, so I'd suggest to revert it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1844247/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812620] Re: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed
** Changed in: linux-aws (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-azure (Ubuntu Disco) Status: Confirmed => Won't Fix ** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1812620 Title: msg_zerocopy.sh in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux-aws package in Ubuntu: New Status in linux-azure package in Ubuntu: New Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Won't Fix Status in linux-azure source package in Disco: Won't Fix Status in linux source package in Eoan: New Status in linux-aws source package in Eoan: New Status in linux-azure source package in Eoan: New Bug description: This test will return 1 $ sudo ./msg_zerocopy.sh ipv4 tcp -t 1 ./msg_zerocopy: setaffinity 2 ./msg_zerocopy: setaffinity 3 $ echo $? 1 ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jan 21 07:41 seq crw-rw 1 root audio 116, 33 Jan 21 07:41 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 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: Date: Mon Jan 21 07:50:33 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-13-generic root=UUID=2a4b0342-a2dd-4feb-b3e2-9644ca1c4a60 ro console=ttyS0,115200n8 RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: Ubuntu-1.8.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-xenial dmi.modalias: dmi:bvnSeaBIOS:bvrUbuntu-1.8.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-xenial:cvnQEMU:ct1:cvrpc-i440fx-xenial: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-xenial dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839106] Re: disco/linux: 5.0.0-25.26 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1)
derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug
1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug
1840275 (linux-azure)
-- swm properties --
bugs-spammed: true
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Complete
phase-changed: Wednesday, 14. August 2019 05:21 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
trackers:
bionic/linux-hwe: bug 1839099
bionic/linux-oem-osp1: bug 1839101
disco/linux-aws: bug 1839072
disco/linux-azure: bug 1839352
disco/linux-gcp: bug 1839093
disco/linux-kvm: bug 1839096
disco/linux-raspi2: bug 1837563
disco/linux-snapdragon: bug 1837573
variant: debs
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1839106
Title:
disco/linux: 5.0.0-25.26 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-lrm series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Disco:
Won't Fix
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
backports: bug 1839099 (bionic/linux-hwe), bug 1839101 (bionic/linux-oem-osp1)
derivatives: bug 1837563 (linux-raspi2), bug 1837573 (linux-snapdragon), bug
1839072 (linux-aws), bug 1839093 (linux-gcp), bug 1839096 (linux-kvm), bug
1840275 (linux-azure)
-- swm properties --
bugs-spammed: true
packages:
lrm: linux-restricted-modules
main: linux
meta: linux-meta
signed: linux-signed
phase: Complete
phase-changed: Wednesday, 14. August 2019 05:21 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-hwe: bug 1839099
bionic/linux-oem-osp1: bug 1839101
disco/linux-aws: bug 1839072
disco/linux-azure: bug 1839352
disco/linux-gcp: bug 1839093
disco/linux-kvm: bug 1839096
disco/linux-raspi2: bug 1837563
disco/linux-snapdragon: bug 1837573
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839106/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839352] Re: disco/linux-azure: 5.0.0-1014.14 -proposed tracker
** Description changed:
This bug will contain status and test results related to a kernel source
(or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
phase: Complete
phase-changed: Wednesday, 14. August 2019 10:10 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
trackers:
bionic/linux-azure: bug 1839351
variant: debs
--
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/1839352
Title:
disco/linux-azure: 5.0.0-1014.14 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow certification-testing series:
Invalid
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow prepare-package-signed series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-security series:
Fix Released
Status in Kernel SRU Workflow promote-to-updates series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Fix Released
Status in Kernel SRU Workflow security-signoff series:
Fix Released
Status in Kernel SRU Workflow stakeholder-signoff series:
Fix Released
Status in Kernel SRU Workflow verification-testing series:
Fix Released
Status in linux-azure package in Ubuntu:
Invalid
Status in linux-azure source package in Disco:
Won't Fix
Bug description:
This bug will contain status and test results related to a kernel
source (or snap) as stated in the title.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
packages:
main: linux-azure
meta: linux-meta-azure
signed: linux-signed-azure
phase: Complete
phase-changed: Wednesday, 14. August 2019 10:10 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
trackers:
bionic/linux-azure: bug 1839351
variant: debs
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1839352/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1816425] Re: Use memblock quirk instead of delayed allocation for GICv3 LPI tables
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1816425 Title: Use memblock quirk instead of delayed allocation for GICv3 LPI tables Status in linux package in Ubuntu: Fix Committed Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Bug description: [Impact] The fix for LP: #1806766 has the issue that the persistent memory reservations for the GICv3 LPI tables may have been allocated an overwritten by the time we get to reserving them. This can continue to break kdump in certain conditions. [Test Case] sudo apt install linux-crashdump echo 'GRUB_CMDLINE_LINUX_DEFAULT="$GRUB_CMDLINE_LINUX_DEFAULT crashkernel=512M"' | \ sudo tee /etc/default/grub.d/kdump-tools.cfg sudo update-grub sudo reboot echo 1 | sudo tee /proc/sys/kernel/sysrq echo c | sudo tee /proc/sysrq-trigger [Fix] 582a32e708823 efi/arm: Revert "Defer persistent reservations until after paging_init()" 8a5b403d71aff arm64, mm, efi: Account for GICv3 LPI tables in static memblock reserve table [Regression Risk] The change in reserved regions only impacts arm64. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1816425/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813211] Re: Allow I/O schedulers to be loaded with modprobe in linux-azure
** Changed in: linux-azure (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1813211 Title: Allow I/O schedulers to be loaded with modprobe in linux-azure Status in linux-azure package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-azure source package in Bionic: Fix Released Status in linux-azure source package in Cosmic: Fix Released Status in linux-azure source package in Disco: Won't Fix Bug description: There was a previous request in bug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1671203 to limit the IO scheduler to NOOP in linux-azure. The other schedulers were turned off and NOOP was made the default. However with new upstream releases, new schedulers where added and linux-azure inherited the default config value for them from the master kernel. That's why there are some IO schedulers built as modules in the extra package (mq-deadline and kyber-iosched). In order to use those two modules, one needs to install the -extra package and modprobe the modules first: # tail /sys/block/sd*/queue/scheduler ==> /sys/block/sda/queue/scheduler <== [none] ==> /sys/block/sdb/queue/scheduler <== [none] # apt install linux-modules-extra-4.15.0-1036-azure # modprobe kyber-iosched # tail /sys/block/sd*/queue/scheduler ==> /sys/block/sda/queue/scheduler <== [none] kyber ==> /sys/block/sdb/queue/scheduler <== [none] kyber # modprobe mq-deadline # tail /sys/block/sd*/queue/scheduler ==> /sys/block/sda/queue/scheduler <== [none] kyber mq-deadline ==> /sys/block/sdb/queue/scheduler <== [none] kyber mq-deadline The schedulers cfq and deadline have been completely disabled in LP bug #1671203 so they cannot be added with modprobe. This is a request to move back the cfq and deadline schedulers along with the mq-deadline and kyber-iosched schedulers to the main linux- azure package (in other words, not in the -extra package) and allow the users to be able to modprobe the schedulers when needed. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1813211/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812843] Re: reuseport_dualstack in net from ubuntu_kernel_selftests failed on s390x
** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1812843 Title: reuseport_dualstack in net from ubuntu_kernel_selftests failed on s390x Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Won't Fix Bug description: This failure was only spotted on Bionic s390x, passed on other arches. $ sudo ./reuseport_dualstack UDP IPv4 created before IPv6 ./reuseport_dualstack: expected to receive on v4 socket but got v6 (1) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-44-generic 4.15.0-44.47 ProcVersionSignature: Ubuntu 4.15.0-44.47-generic 4.15.18 Uname: Linux 4.15.0-44-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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.9-0ubuntu7.5 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Tue Jan 22 11:22:40 2019 HibernationDevice: RESUME=UUID=caaee9b2-6bc1-4c8e-b26c-69038c092091 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lspci: Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: Error: [Errno 2] No such file or directory: '/proc/fb' ProcKernelCmdLine: root=UUID=c7d7bbcb-a039-4ead-abfe-7672dea0add4 crashkernel=196M RelatedPackageVersions: linux-restricted-modules-4.15.0-44-generic N/A linux-backports-modules-4.15.0-44-generic N/A linux-firmware 1.173.3 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812843/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812622] Re: fib related test in net from ubuntu_kernel_selftests failed
** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-aws (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-kvm (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812622 Title: fib related test in net from ubuntu_kernel_selftests failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-aws package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: New Status in linux source package in Disco: Won't Fix Status in linux-aws source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Status in linux source package in Eoan: New Status in linux-aws source package in Eoan: New Status in linux-kvm source package in Eoan: New Bug description: These tests: * fib_tests.sh * fib-onlink-tests.sh * fib_rule_tests.sh All failed on Cosmic KVM kernel with RTNETLINK answers: Operation not supported: selftests: net: fib_tests.sh Single path route test RTNETLINK answers: Operation not supported not ok 1..11 selftests: net: fib_tests.sh [FAIL] selftests: net: fib-onlink-tests.sh Configuring interfaces RTNETLINK answers: Operation not supported not ok 1..12 selftests: net: fib-onlink-tests.sh [FAIL] selftests: net: fib_rule_tests.sh RTNETLINK answers: Operation not supported not ok 1..16 selftests: net: fib_rule_tests.sh [FAIL] (works on generic Cosmic kernel) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-1006-kvm 4.18.0-1006.6 ProcVersionSignature: User Name 4.18.0-1006.6-kvm 4.18.17 Uname: Linux 4.18.0-1006-kvm x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 Date: Mon Jan 21 08:00:22 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812622/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1814373] Re: storage / luks / dmsetup regressed (or got better) on ppc64le
** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1814373 Title: storage / luks / dmsetup regressed (or got better) on ppc64le Status in linux package in Ubuntu: Confirmed Status in systemd package in Ubuntu: Confirmed Status in systemd source package in Xenial: Fix Released Status in linux source package in Bionic: New Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: New Status in systemd source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Status in systemd source package in Disco: Fix Released Status in linux source package in Eoan: Confirmed Status in systemd source package in Eoan: Confirmed Status in systemd package in Debian: Fix Released Bug description: in disco proposed with new systemd and v4.19 kernel it appears that dmsetup / cryptsetup storage either got better or worse. Devices take very long to activate, and sometimes remain in use during test clean up. This leads to udisks autopkgtest failing on ppc64le and systemd's "storage" autopkgtest is also failing. I've tried to make ppc64le test more resilient, but it's still odd that it became unstable in disco, and used to be rock solid on ppc64le. -- sru template for systemd upload: [impact] buffer overflow can cause memory corruption; this is seen in failed autopkgtests [test case] see comment 6 [regression potential] the patch is minimal and clearly correct; however the regression potential is around invalid/corrupted keys read from the keyring. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1814373/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812194] Re: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels
** Changed in: linux (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-kvm (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1812194 Title: RTNETLINK in net from ubuntu_kernel_selftests failed on KVM kernels Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux-kvm package in Ubuntu: New Status in linux source package in Bionic: Incomplete Status in linux-kvm source package in Bionic: New Status in linux source package in Cosmic: Incomplete Status in linux-kvm source package in Cosmic: Invalid Status in linux source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Bug description: This test failed because of the unsuccessful attempt to add a dummy device with ip link command: # devdummy="test-dummy0" # ip link add name "$devdummy" type dummy RTNETLINK answers: Operation not supported selftests: rtnetlink.sh RTNETLINK answers: Operation not supported Cannot find device "test-dummy0" FAIL: cannot add dummy interface not ok 1..10 selftests: rtnetlink.sh [FAIL] ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28 ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18 Uname: Linux 4.15.0-1028-kvm x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 Date: Thu Jan 17 10:21:02 2019 SourcePackage: linux-kvm UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1812176] Re: psock_tpacket from the net test in ubuntu_kernel_selftests failed on KVM kernels
** Changed in: linux-kvm (Ubuntu Disco)
Status: In Progress => Won't Fix
** Changed in: linux (Ubuntu Disco)
Status: Fix Committed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1812176
Title:
psock_tpacket from the net test in ubuntu_kernel_selftests failed on
KVM kernels
Status in ubuntu-kernel-tests:
Fix Released
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Xenial:
Fix Released
Status in linux-kvm source package in Xenial:
Fix Released
Status in linux source package in Bionic:
Fix Released
Status in linux-kvm source package in Bionic:
Fix Released
Status in linux source package in Disco:
Won't Fix
Status in linux-kvm source package in Disco:
Won't Fix
Bug description:
The psock_tpacket in the net test from ubuntu_kernel_selftests failed with
B-KVM
$ sudo ./psock_tpacket
test: TPACKET_V1 with PACKET_RX_RING open: No such file or directory
Look into the code, it seems that this file not found error is caused
by the attempt to access /proc/kallsyms in test_kernel_bit_width():
static int test_kernel_bit_width(void)
{
char in[512], *ptr;
int num = 0, fd;
ssize_t ret;
fd = open("/proc/kallsyms", O_RDONLY);
if (fd == -1) {
perror("open");
exit(1);
}
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: linux-image-4.15.0-1028-kvm 4.15.0-1028.28
ProcVersionSignature: User Name 4.15.0-1028.28-kvm 4.15.18
Uname: Linux 4.15.0-1028-kvm x86_64
ApportVersion: 2.20.9-0ubuntu7.5
Architecture: amd64
Date: Thu Jan 17 08:05:47 2019
SourcePackage: linux-kvm
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1812176/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810384] Re: 6113077cd319e747875ec71227d2b5cb54e08c76 in btrfs_kernel_fixes failed on B/C/D
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810384 Title: 6113077cd319e747875ec71227d2b5cb54e08c76 in btrfs_kernel_fixes failed on B/C/D Status in ubuntu-kernel-tests: Fix Released Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Won't Fix Bug description: Test failed with disk quota exceeded when trying to create subvolume, and error traces could be found in the kernel log. This patch exists in the Bionic kernel tree: https://kernel.ubuntu.com/git/ubuntu/ubuntu-bionic.git/commit/?id=6113077cd319e747875ec71227d2b5cb54e08c76 Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76 fix 6113077cd319e747875ec71227d2b5cb54e08c76 Btrfs: fix missing qgroup reservation before fallocating Steps to reproduce: mkfs.btrfs mount btrfs quota enable btrfs sub create /subv btrfs qgroup limit 10M /subv fallocate --length 20M /subv/data For the above example, fallocating will return successfully which is not expected, we try to fix it by doing qgroup reservation before fallocating. Create subvolume '/tmp/mnt-6113077cd319e747875ec71227d2b5cb54e08c76/subv' fallocate: fallocate failed: Disk quota exceeded Found kernel issue: [ 829.940603] Invoking test 6113077cd319e747875ec71227d2b5cb54e08c76 [ 830.001738] BTRFS: device fsid 134f6701-7984-42bc-affc-e423f4e6c750 devid 1 transid 5 /dev/loop0 [ 830.005573] BTRFS info (device loop0): disk space caching is enabled [ 830.005574] BTRFS info (device loop0): has skinny extents [ 830.005575] BTRFS info (device loop0): flagging fs with big metadata feature [ 830.006375] BTRFS info (device loop0): creating UUID tree [ 830.038054] BTRFS info (device loop0): qgroup scan completed (inconsistency flag cleared) [ 830.042133] WARNING: CPU: 1 PID: 15933 at /build/linux-oem-RkS9Vy/linux-oem-4.15.0/fs/btrfs/extent-tree.c:4433 btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs] [ 830.042133] Modules linked in: btrfs zstd_compress intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm irqbypass ppdev input_leds intel_cstate joydev intel_rapl_perf intel_pch_thermal parport_pc ipmi_si parport lpc_ich mac_hid ipmi_devintf ipmi_msghandler sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear i915 mgag200 crct10dif_pclmul crc32_pclmul ttm ghash_clmulni_intel pcbc igb drm_kms_helper hid_generic aesni_intel dca syscopyarea i2c_algo_bit sysfillrect aes_x86_64 sysimgblt fb_sys_fops crypto_simd ptp ahci usbhid glue_helper cryptd drm libahci hid pps_core video [last unloaded: zstd_compress] [ 830.042166] CPU: 1 PID: 15933 Comm: fallocate Not tainted 4.15.0-1030-oem #35-Ubuntu [ 830.042167] Hardware name: Intel Corporation S1200RP/S1200RP, BIOS S1200RP.86B.03.02.0003.070120151022 07/01/2015 [ 830.042176] RIP: 0010:btrfs_free_reserved_data_space_noquota+0xcb/0xe0 [btrfs] [ 830.042177] RSP: 0018:aa474a647d88 EFLAGS: 00010287 [ 830.042178] RAX: RBX: 0140 RCX: 0140 [ 830.042178] RDX: 0001 RSI: RDI: 8febd2814200 [ 830.042179] RBP: aa474a647db0 R08: 00027fc0 R09: c0877688 [ 830.042180] R10: 8feb877f R11: 0001 R12: 8febd2814200 [ 830.042180] R13: 8feb877f R14: 8feb1ff25f40 R15: 0140 [ 830.042181] FS: 7f7b7a10c540() GS:8febe084() knlGS: [ 830.042182] CS: 0010 DS: ES: CR0: 80050033 [ 830.042183] CR2: 7f7b79f4baa0 CR3: 00045a996004 CR4: 003606e0 [ 830.042184] DR0: DR1: DR2: [ 830.042184] DR3: DR6: fffe0ff0 DR7: 0400 [ 830.042185] Call Trace: [ 830.042194] btrfs_free_reserved_data_space+0x50/0x70 [btrfs] [ 830.042205] btrfs_fallocate+0x3f8/0x750 [btrfs] [ 830.042208] vfs_fallocate+0x144/0x260 [ 830.042209] SyS_fallocate+0x48/0x80 [ 830.042211] do_syscall_64+0x73/0x130 [ 830.042214] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 830.042215] RIP: 0033:0x7f7b79c13857 [ 830.042215] RSP: 002b:7ffc1ad01498 EFLAGS: 0246 ORIG_RAX: 011d [ 830.042216] RAX: ffda RBX: RCX: 7f7b79c13857 [ 830.042217] RDX: RSI: RDI: 0008 [ 830.042217]
[Kernel-packages] [Bug 1864041] Re: xen_netfront devices unresponsive after hibernation/resume
I've done additional testing with eoan with this ec2-hibinit-agent with improved test results. Setting to `verification-done-eoan`. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1864041 Title: xen_netfront devices unresponsive after hibernation/resume Status in ec2-hibinit-agent package in Ubuntu: Fix Released Status in linux-aws package in Ubuntu: New Status in ec2-hibinit-agent source package in Bionic: Fix Released Status in linux-aws source package in Bionic: New Status in ec2-hibinit-agent source package in Eoan: Fix Committed Status in linux-aws source package in Eoan: New Status in ec2-hibinit-agent source package in Focal: Fix Released Status in linux-aws source package in Focal: New Bug description: [Impact] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. [Test Case] 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. [Regression Potential] The workaround in ec2-hibinit-agent is reloading the xen_netfront kernel module before restarting systemd-networkd. If the kernel module is removed (for example when hitting LP: #1615381) the module reloading fails and the instance can not restore network connections. This is expected to a be very rare situation and the module reload is the best workaround the Kernel Team found to mitigate the original issue. The workaround also adds a 2 second delay before reloading the modules to let things settle a bit after resuming. The 2 seconds is very short compared to the overall time needed resuming an instance. [Original Bug Text] The xen_netfront device is sometimes unresponsive after a hibernate and resume event. This is limited to the c4, c5, m4, m5, r4, r5 instance families, all of which are xen based, and support hibernation. When the issue occurrs, the instance is inaccessible without a full restart. Debugging by running a process which outputs regularly to the serial console shows that the instance is still running. A workaround is to build the xen_netfront module separately and restart the module and networking during the resume handler. For example: modprobe -r xen_netfront modprobe xen_netfront systemctl restart systemd-networkd With this workaround in place, the unresponsive issue is no longer observed. To reproduce this problem: 1) Launch an c4, c5, m4, m5, r4, r5 instance type with a 5.0 or 5.3 kernel with on-demand hibernation support enabled. 2) Start a long-running process which generates messages to the serial console 3) Begin observing these messages on the console (using the AWS UI or CLI to grab a screenshot). 4) Suspend and resume the instance, continuing to refresh the console screenshot. 5) The screenshot should continue to show updates even if ssh access is no longer working. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 DistroRelease: Ubuntu 18.04 Ec2AMI: ami-0edf3b95e26a682df Ec2AMIManifest: (unknown) Ec2AvailabilityZone: us-west-2a Ec2InstanceType: m4.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable Package: linux-aws 4.15.0.1058.59 PackageArchitecture: amd64 ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash ProcVersionSignature: User Name 5.0.0-1025.28-aws 5.0.21 Tags: bionic ec2-images Uname: Linux 5.0.0-1025-aws x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dialout dip floppy lxd netdev plugdev sudo video _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ec2-hibinit-agent/+bug/1864041/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1809701] Re: cpu_hot_plug test in ubuntu_kernel_selftest failed on Moonshot ARM64
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809701 Title: cpu_hot_plug test in ubuntu_kernel_selftest failed on Moonshot ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Disco: Won't Fix Bug description: Test failed with "Operation not supported" when trying to offline a CPU: echo 0 > $SYSFS/devices/system/cpu/cpu$1/online This issue cannot be reproduced on CaviumThunderX ARM64 server, just the moonshots. $ sudo make -C linux/tools/testing/selftests TARGETS=cpu-hotplug run_tests make: Entering directory '/home/ubuntu/linux/tools/testing/selftests' make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make[1]: Nothing to be done for 'all'. make[1]: Leaving directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make[1]: Entering directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' TAP version 13 selftests: cpu-hotplug: cpu-on-off-test.sh pid 8132's current affinity mask: ff pid 8132's new affinity mask: 1 CPU online/offline summary: Cpus in online state: 0-7 Cpus in offline state: 0 Limited scope test: one hotplug cpu (leaves cpu in the original state): online to offline to online: cpu 7 ./cpu-on-off-test.sh: line 92: echo: write error: Operation not supported offline_cpu_expect_success 7: unexpected fail not ok 1..1 selftests: cpu-hotplug: cpu-on-off-test.sh [FAIL] make[1]: Leaving directory '/home/ubuntu/linux/tools/testing/selftests/cpu-hotplug' make: Leaving directory '/home/ubuntu/linux/tools/testing/selftests' The CPU hotplug config was enabled on this SUT: $ cat /boot/config-`uname -r` | grep HOTPLUG | grep CPU CONFIG_HOTPLUG_CPU=y CONFIG_ACPI_HOTPLUG_CPU=y # CONFIG_CPU_HOTPLUG_STATE_CONTROL is not set ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-13-generic 4.18.0-13.14 ProcVersionSignature: User Name 4.18.0-13.14-generic 4.18.17 Uname: Linux 4.18.0-13-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Dec 25 04:01 seq crw-rw 1 root audio 116, 33 Dec 25 04:01 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.1 Architecture: arm64 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: Date: Tue Dec 25 04:54:54 2018 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: console=ttyS0,9600n8r ro RelatedPackageVersions: linux-restricted-modules-4.18.0-13-generic N/A linux-backports-modules-4.18.0-13-generic N/A linux-firmware 1.175.1 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1809701/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
Yes, I think that kernel is fine. You can leave the i8042.nopnp=1 in your kernel command line parameters. Otherwise it looks right. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884232 Title: touchpad doesn't work at all on ACER Spin 5 Status in linux package in Ubuntu: Confirmed Bug description: Touchpad is not working at all on ACER Spin 5 SP513-54N. According to https://wiki.ubuntu.com/DebuggingTouchpadDetection#In_case_your_Touchpad_doesn.27t_work_at_all_.28No_response_from_the_Touchpad.29 I am creating this kernel bug issue. There are more issues, too, like touchscreen not working and Ubuntu not installable - see here if interrested https://askubuntu.com/questions/1251719/ I would like to run Ubuntu on this machine and I am willing to help with any debug or kernel tweaking... Please let me know. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic 5.4.0-26.30 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ubuntu 4195 F pulseaudio CasperMD5CheckResult: skip CasperVersion: 1.445 CurrentDesktop: ubuntu:GNOME Date: Fri Jun 19 10:44:58 2020 LiveMediaBuild: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: Acer Spin SP513-54N 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=/casper/vmlinuz file=/cdrom/preseed/username.seed maybe-ubiquity quiet splash --- RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2020 dmi.bios.vendor: Insyde Corp. dmi.bios.version: V1.00 dmi.board.name: Caboom_IL dmi.board.vendor: IL dmi.board.version: V1.00 dmi.chassis.type: 31 dmi.chassis.vendor: Acer dmi.chassis.version: V1.00 dmi.modalias: dmi:bvnInsydeCorp.:bvrV1.00:bd02/21/2020:svnAcer:pnSpinSP513-54N:pvrV1.00:rvnIL:rnCaboom_IL:rvrV1.00:cvnAcer:ct31:cvrV1.00: dmi.product.family: Spin 5 dmi.product.name: Spin SP513-54N dmi.product.sku: dmi.product.version: V1.00 dmi.sys.vendor: Acer To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885573] Re: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB)
** Attachment added: "ACPI tables dump" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+attachment/5389147/+files/acpidump.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885573 Title: Touchpad not recognized in laptop Lenovo Thinkbook 15-ILL (20SM000GPB) Status in linux package in Ubuntu: Confirmed Bug description: My laptop's touchpad is not recognized by current linux kernel (5.4.0-39-generic) in Ubuntu 20.04 LTS. I didn't find it in 'cat /proc/bus/input/devices'. 1. Laptop model: Lenovo Thinkbook 15-ILL (20SM000GPB) 2. Touchpad manufacturer: I wasn't able to find out, if the manufacturer is ALPS, Elan or Synatics 3. Problem occured for the first time during installation and then it continued after installation was complete. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-39-generic 5.4.0-39.43 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 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: mrozwod1597 F pulseaudio /dev/snd/pcmC0D0p: mrozwod1597 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 29 16:06:14 2020 InstallationDate: Installed on 2020-06-29 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 20SM ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-39-generic root=UUID=0923cf05-213a-4a18-8bb1-393e24835373 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-39-generic N/A linux-backports-modules-5.4.0-39-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/11/2019 dmi.bios.vendor: LENOVO dmi.bios.version: DJCN14WW dmi.board.name: LVAC/LVAD dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ThinkBook 15-IIL dmi.modalias: dmi:bvnLENOVO:bvrDJCN14WW:bd12/11/2019:svnLENOVO:pn20SM:pvrLenovoThinkBook15-IIL:rvnLENOVO:rnLVAC/LVAD:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrLenovoThinkBook15-IIL: dmi.product.family: Thinkbook 15-IIL dmi.product.name: 20SM dmi.product.sku: LENOVO_MT_20SM_BU_idea_FM_Thinkbook 15-IIL dmi.product.version: Lenovo ThinkBook 15-IIL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885573/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825429] Re: linux: -proposed tracker
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825429 Title: linux: -proposed tracker Status in Kernel SRU Workflow: Invalid Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-lrm series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Won't Fix Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1825430 (bionic/linux-hwe-edge) -- swm properties -- To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1825429/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820308] Re: linux-raspi2: 5.0.0-1004.4 -proposed tracker
** Changed in: linux-raspi2 (Ubuntu Disco)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1820308
Title:
linux-raspi2: 5.0.0-1004.4 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-release series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in linux-raspi2 package in Ubuntu:
Confirmed
Status in linux-raspi2 source package in Disco:
Won't Fix
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-master-bug: 1819759
packages:
main: linux-raspi2
meta: linux-meta-raspi2
phase: Ready for Release
phase-changed: Thursday, 21. March 2019 21:32 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820308/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1822937] Re: NVIDIA settings won't write to /etc/xorg
** Changed in: nvidia-settings (Ubuntu Disco) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-settings in Ubuntu. https://bugs.launchpad.net/bugs/1822937 Title: NVIDIA settings won't write to /etc/xorg Status in nvidia-settings package in Ubuntu: Fix Released Status in nvidia-settings source package in Disco: Won't Fix Bug description: I tried running it with root (`sudo nvidia-settings`) and without. I also generated an xorg file with `nvidia-xconfig`, and do the same thing, but it still won't work. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nvidia-settings 418.56-0ubuntu1 ProcVersionSignature: Ubuntu 5.0.0-8.9-generic 5.0.1 Uname: Linux 5.0.0-8-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.10-0ubuntu23 Architecture: amd64 CurrentDesktop: KDE Date: Wed Apr 3 00:33:48 2019 InstallationDate: Installed on 2019-04-02 (0 days ago) InstallationMedia: Kubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190326.1) SourcePackage: nvidia-settings UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-settings/+bug/1822937/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1817784] Re: libsas disks can have non-unique by-path names
** Changed in: linux (Ubuntu Disco) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1817784 Title: libsas disks can have non-unique by-path names Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Released Status in linux source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Released Status in linux source package in Disco: Won't Fix Bug description: [Impact] Multiple disks in a system can end up having the same BY_PATH name, making the corresponding symlinks in /dev/disk/by-path non-unique. This can result in a user performing an operation on the wrong disk, possibly resulting in data loss. [Test Case] $ ls -l /dev/disk/by-path/ total 0 lrwxrwxrwx 1 root root 9 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0 -> ../../sdb lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part1 -> ../../sdb1 lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part2 -> ../../sdb2 lrwxrwxrwx 1 root root 10 Feb 13 12:26 platform-HISI0162:01-sas-exp0x500e004aaa1f-phy0-lun-0-part3 -> ../../sdc3 Notice that there is no symlink for /dev/sdc. [Fix] ffeafdd2bf0b2 scsi: libsas: Fix rphy phy_identifier for PHYs with end devices attached [Regression Risk] This may change the by-path symlinks for disks on the system. While the new name would be the correct one - users maybe relying on the incorrect version. This could result in an unbootable system, requiring manual intervention to repair. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1817784/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1805806] Re: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1805806 Title: test_maps in ubuntu_bpf failed with "Failed sockmap unexpected timeout" on D ARM64 Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Cosmic: Won't Fix Status in linux source package in Disco: Won't Fix Bug description: This issue can be found on 2 different ARM64 node, TunderX Cavium node "starmie" and Moonshot "ms10-34-mcdivittB0-kernel" Running test_maps bpf test.. Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Fork 1024 tasks to 'test_update_delete' Fork 1024 tasks to 'test_update_delete' Fork 100 tasks to 'test_hashmap' Fork 100 tasks to 'test_hashmap_percpu' Fork 100 tasks to 'test_hashmap_sizes' Fork 100 tasks to 'test_hashmap_walk' Fork 100 tasks to 'test_arraymap' Fork 100 tasks to 'test_arraymap_percpu' Failed sockmap unexpected timeout ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: User Name
[Kernel-packages] [Bug 1809483] Re: iwlwifi not working with Intel AC 9260 on kernel 4.15
** Changed in: linux (Ubuntu Disco) Status: In Progress => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1809483 Title: iwlwifi not working with Intel AC 9260 on kernel 4.15 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Won't Fix Bug description: [ 22.201674] iwlwifi :70:00.0: Detected Intel(R) Dual Band Wireless AC 9260, REV=0x324 [ 22.208574] [ cut here ] [ 22.208575] kernel BUG at /build/linux-vxxS7y/linux-4.15.0/drivers/net/wireless/intel/iwlwifi/pcie/rx.c:425! [ 22.208578] invalid opcode: [#1] SMP NOPTI [ 22.208579] Modules linked in: iwlmvm(+) coretemp(+) snd_hda_codec_realtek snd_hda_codec_generic mac80211 snd_hda_intel snd_hda_codec kvm_intel snd_hda_core snd_hwdep snd_pcm kvm snd_seq_midi snd_seq_midi_event snd_rawmidi irqbypass uvcvideo mxm_wmi intel_wmi_thunderb olt wmi_bmof snd_seq iwlwifi crct10dif_pclmul videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_core crc32_pclmul btusb ghash_clmulni_intel videodev btrtl snd_seq_device btbcm btintel snd_timer intel_cstate media bluetooth snd cfg80211 intel_rapl_perf soundcore ecdh_generic psmouse sdhci_pci alx mdio sdhci i2c_i801 mei_me mei intel_hid sparse_keymap shpchp acpi_pad wmi sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt nvidia_drm(POE) nvidia_modeset(POE) nvidia(POE) aesni_intel aes_x86_64 crypto_simd [ 22.208598] cryptd glue_helper drm_kms_helper syscopyarea sysfillrect input_leds sysimgblt fb_sys_fops serio_raw drm ahci ipmi_devintf libahci ipmi_msghandler video mac_hid [ 22.208604] CPU: 4 PID: 767 Comm: modprobe Tainted: P OE 4.15.0-43-generic #46-Ubuntu [ 22.208605] Hardware name: Notebook P7xxTM1/P7xxTM1, BIOS 1.07.17 12/07/2018 [ 22.208610] RIP: 0010:iwl_pcie_rxq_alloc_rbs+0x1d0/0x1f0 [iwlwifi] [ 22.208610] RSP: 0018:b7fb43ccf8a8 EFLAGS: 00010286 [ 22.208612] RAX: dead0200 RBX: 99b9b8280078 RCX: e4b2e1c6ab60 [ 22.208612] RDX: 99b9b38b61a8 RSI: RDI: 99b9b8280078 [ 22.208613] RBP: b7fb43ccf8e8 R08: 99b9b38b61a8 R09: 007690c8 [ 22.208614] R10: R11: 99b9b8280050 R12: 99b9b828 [ 22.208614] R13: 99b9b38b0018 R14: e4b2e1c6a980 R15: 99b9b38b61d0 [ 22.208615] FS: 7fb8c9ec9540() GS:99b9be30() knlGS: [ 22.208616] CS: 0010 DS: ES: CR0: 80050033 [ 22.208617] CR2: 7f9440284648 CR3: 000873844001 CR4: 003606e0 [ 22.208618] DR0: DR1: DR2: [ 22.208619] DR3: DR6: fffe0ff0 DR7: 0400 [ 22.208619] Call Trace: [ 22.208623] _iwl_pcie_rx_init+0x252/0x710 [iwlwifi] [ 22.208626] iwl_pcie_rx_init+0x2d/0x3c0 [iwlwifi] [ 22.208631] ? iwl_mvm_nic_config+0xeb/0x120 [iwlmvm] [ 22.208635] iwl_trans_pcie_start_fw+0x2a1/0x6c0 [iwlwifi] [ 22.208639] iwl_mvm_load_ucode_wait_alive+0xec/0x2b0 [iwlmvm] [ 22.208640] ? 0xc198e000 [ 22.208644] iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208647] ? iwl_run_init_mvm_ucode+0x8e/0x330 [iwlmvm] [ 22.208650] ? iwl_wait_init_complete+0x20/0x20 [iwlmvm] [ 22.208654] iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208657] ? iwl_op_mode_mvm_start+0x649/0x920 [iwlmvm] [ 22.208660] _iwl_op_mode_start.isra.10+0x4c/0xa0 [iwlwifi] [ 22.208663] iwl_opmode_register+0x75/0xe0 [iwlwifi] [ 22.208664] ? 0xc19e8000 [ 22.208668] iwl_mvm_init+0x38/0x1000 [iwlmvm] [ 22.208671] do_one_initcall+0x52/0x19f [ 22.208672] ? _cond_resched+0x19/0x40 [ 22.208674] ? kmem_cache_alloc_trace+0xa6/0x1b0 [ 22.208676] ? do_init_module+0x27/0x209 [ 22.208678] do_init_module+0x5f/0x209 [ 22.208679] load_module+0x191e/0x1f10 [ 22.208681] ? ima_post_read_file+0x96/0xa0 [ 22.208682] SYSC_finit_module+0xfc/0x120 [ 22.208683] ? SYSC_finit_module+0xfc/0x120 [ 22.208685] SyS_finit_module+0xe/0x10 [ 22.208686] do_syscall_64+0x73/0x130 [ 22.208688] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 22.208689] RIP: 0033:0x7fb8c99ef839 [ 22.208690] RSP: 002b:7ffecf171ea8 EFLAGS: 0246 ORIG_RAX: 0139 [ 22.208691] RAX: ffda RBX: 55c40d7462f0 RCX: 7fb8c99ef839 [ 22.208691] RDX: RSI: 55c40c09cd2e RDI: 0001 [ 22.208692] RBP: 55c40c09cd2e R08: R09: [ 22.208693] R10: 0001 R11: 0246 R12: [ 22.208693] R13:
[Kernel-packages] [Bug 1802474] Re: test_map in ubuntu_bpf failed on D PowerPC
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1802474 Title: test_map in ubuntu_bpf failed on D PowerPC Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Won't Fix Bug description: The test_map test will fail with the following error on powerpc boxes: $ sudo ./test_maps libbpf: object file doesn't contain bpf program Failed to load SK_SKB parse prog ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12~18.04.1 ProcVersionSignature: Ubuntu 4.18.0-11.12~18.04.1-generic 4.18.12 Uname: Linux 4.18.0-11-generic ppc64le ApportVersion: 2.20.9-0ubuntu7.4 Architecture: ppc64el Date: Fri Nov 9 08:37:46 2018 ProcLoadAvg: 0.18 0.51 0.47 1/1615 14440 ProcSwaps: Filename TypeSizeUsedPriority /swap.img file 8388544 0 -2 ProcVersion: Linux version 4.18.0-11-generic (buildd@bos02-ppc64el-012) (gcc version 7.3.0 (Ubuntu 7.3.0-16ubuntu3)) #12~18.04.1-Ubuntu SMP Thu Oct 25 12:58:39 UTC 2018 SourcePackage: linux-signed-hwe-edge UpgradeStatus: No upgrade log present (probably fresh install) VarLogDump_list: total 0 cpu_cores: Number of cores present = 20 cpu_coreson: Number of cores online = 20 cpu_dscr: DSCR is 0 cpu_freq: min: 3.694 GHz (cpu 159) max: 3.695 GHz (cpu 1) avg: 3.694 GHz cpu_runmode: Could not retrieve current diagnostics mode, No kernel interface to firmware cpu_smt: SMT=8 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1802474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820075] Re: [Packaging] Improve config annotations check on custom kernels
** Changed in: linux-gcp (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1820075 Title: [Packaging] Improve config annotations check on custom kernels Status in linux-azure package in Ubuntu: Fix Released Status in linux-gcp package in Ubuntu: New Status in linux-oracle package in Ubuntu: Fix Released Status in linux-azure source package in Xenial: Fix Released Status in linux-gcp source package in Xenial: New Status in linux-oracle source package in Xenial: New Status in linux-azure source package in Bionic: Fix Released Status in linux-gcp source package in Bionic: Fix Released Status in linux-oracle source package in Bionic: New Status in linux-azure source package in Cosmic: Fix Released Status in linux-gcp source package in Cosmic: Fix Released Status in linux-oracle source package in Cosmic: New Status in linux-azure source package in Disco: Fix Released Status in linux-gcp source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Fix Released Bug description: [Impact] Currently for custom kernels, it's necessary to keep a separate annotations file that often gets out of sync with the corresponding file in debian.master/. The "debian/scripts/config-check" script can be changed to allow additional annotations files to act as overlays over the original annotations file, allowing custom kernels to override the policies just for the relevant configs. The proposal is to add support for an include directive in the annotations file so custom kernels can include the annotations file from its base kernel and override policies on a config basis. [Test Case] A kernel build should complete successfully after the change. [Regression Potential] Low regression potential since that's a change on the build process that doesn't affect the final kernel that is built. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1820075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820308] Re: linux-raspi2: 5.0.0-1004.4 -proposed tracker
** Description changed:
This bug is for tracking the upload package. This
bug will contain status and testing results related to that upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-master-bug: 1819759
+ packages:
+ main: linux-raspi2
+ meta: linux-meta-raspi2
phase: Ready for Release
phase-changed: Thursday, 21. March 2019 21:32 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
+ reason: {}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-raspi2 in Ubuntu.
https://bugs.launchpad.net/bugs/1820308
Title:
linux-raspi2: 5.0.0-1004.4 -proposed tracker
Status in Kernel SRU Workflow:
Fix Released
Status in Kernel SRU Workflow automated-testing series:
Fix Released
Status in Kernel SRU Workflow prepare-package series:
Fix Released
Status in Kernel SRU Workflow prepare-package-meta series:
Fix Released
Status in Kernel SRU Workflow promote-to-proposed series:
Fix Released
Status in Kernel SRU Workflow promote-to-release series:
Fix Released
Status in Kernel SRU Workflow regression-testing series:
Invalid
Status in linux-raspi2 package in Ubuntu:
Confirmed
Status in linux-raspi2 source package in Disco:
Won't Fix
Bug description:
This bug is for tracking the upload package.
This bug will contain status and testing results related to that
upload.
For an explanation of the tasks and the associated workflow see:
https://wiki.ubuntu.com/Kernel/kernel-sru-workflow
-- swm properties --
kernel-master-bug: 1819759
packages:
main: linux-raspi2
meta: linux-meta-raspi2
phase: Ready for Release
phase-changed: Thursday, 21. March 2019 21:32 UTC
proposed-announcement-sent: true
proposed-testing-requested: true
reason: {}
To manage notifications about this bug go to:
https://bugs.launchpad.net/kernel-sru-workflow/+bug/1820308/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824228] Re: ept test fails in kvm_unit_tests
** Changed in: linux-azure (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-kvm (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-oracle (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1824228 Title: ept test fails in kvm_unit_tests Status in ubuntu-kernel-tests: New Status in linux-azure package in Ubuntu: New Status in linux-kvm package in Ubuntu: New Status in linux-oracle package in Ubuntu: New Status in linux-azure source package in Disco: Won't Fix Status in linux-kvm source package in Disco: Won't Fix Status in linux-oracle source package in Disco: Won't Fix Status in linux-azure source package in Eoan: New Status in linux-kvm source package in Eoan: New Status in linux-oracle source package in Eoan: New Bug description: Reproducible: Yes, Series: cosmic Kernel: "linux-azure 4.18.0-1015.15" Steps: 1.) apt-get install -y build-essential cpu-checker qemu-kvm git gcc-multilib 2.) git clone --depth=1 https://git.kernel.org/pub/scm/virt/kvm/kvm-unit-tests.git 3.) cd kvm-unit-tests; ./configure; make 4.) sudo TESTNAME=ept TIMEOUT=90s ACCEL= ./x86/run x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append "ept_access*" timeout -k 1s --foreground 90s /usr/bin/qemu-system-x86_64 -nodefaults -device pc-testdev -device isa-debug-exit,iobase=0xf4,iosize=0x4 -vnc none -serial stdio -device pci-testdev -machine accel=kvm -kernel x86/vmx.flat -smp 1 -cpu host,host-phys-bits,+vmx -m 2560 -append ept_access* # -initrd /tmp/tmp.RcwfbGP5Ou enabling apic paging enabled cr0 = 80010011 cr3 = 477000 cr4 = 20 Test suite: ept_access_test_not_present Test suite: ept_access_test_read_only Test suite: ept_access_test_write_only Test suite: ept_access_test_read_write Test suite: ept_access_test_execute_only Test suite: ept_access_test_read_execute Test suite: ept_access_test_write_execute Test suite: ept_access_test_read_write_execute Test suite: ept_access_test_reserved_bits Test suite: ept_access_test_ignored_bits Test suite: ept_access_test_paddr_not_present_ad_disabled Test suite: ept_access_test_paddr_not_present_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_only_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff49 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff62 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ff7b 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x008b - ''''''''''''''1000'1011 - 139 RHS: 0x008a - ''''''''''''''1000'1010 - 138 STACK: 40f328 40f8fb 40fb0b 40ffa8 401577 4039d0 400312 Test suite: ept_access_test_paddr_read_only_ad_enabled Host skipping test: EPT AD bits not supported. Test suite: ept_access_test_paddr_read_write Test suite: ept_access_test_paddr_read_write_execute Test suite: ept_access_test_paddr_read_execute_ad_disabled EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS: 0x00aa - ''''''''''''''1010'1010 - 170 STACK: 40f328 40f8fb 40fb0b 40fde3 401577 4039d0 400312 EPT_VLT_RD expected FAIL: x86/vmx_tests.c:2380: Expectation failed: (expected_qual) == (qual) LHS: 0x00ab - ''''''''''''''1010'1011 - 171 RHS:
[Kernel-packages] [Bug 1822235] Re: All 29 tests in kvm-unit-test failed (timeouted) on i386
** Changed in: linux (Ubuntu Disco) Status: Confirmed => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1822235 Title: All 29 tests in kvm-unit-test failed (timeouted) on i386 Status in ubuntu-kernel-tests: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux source package in Disco: Won't Fix Bug description: All the available tests in kvm-unit-test have failed on Cosmic i386 with node "onza". They all timeout with the default 90 second threshold. TESTNAME=smptest TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 2 FAIL smptest (timeout; duration=90s) TESTNAME=smptest3 TIMEOUT=90s ACCEL= ./x86/run x86/smptest.flat -smp 3 FAIL smptest3 (timeout; duration=90s) TESTNAME=vmexit_cpuid TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'cpuid' FAIL vmexit_cpuid (timeout; duration=90s) TESTNAME=vmexit_vmcall TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'vmcall' FAIL vmexit_vmcall (timeout; duration=90s) TESTNAME=vmexit_mov_from_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_from_cr8' FAIL vmexit_mov_from_cr8 (timeout; duration=90s) TESTNAME=vmexit_mov_to_cr8 TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'mov_to_cr8' FAIL vmexit_mov_to_cr8 (timeout; duration=90s) TESTNAME=vmexit_inl_pmtimer TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'inl_from_pmtimer' FAIL vmexit_inl_pmtimer (timeout; duration=90s) TESTNAME=vmexit_ipi TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi' FAIL vmexit_ipi (timeout; duration=90s) TESTNAME=vmexit_ipi_halt TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 2 -append 'ipi_halt' FAIL vmexit_ipi_halt (timeout; duration=90s) TESTNAME=vmexit_ple_round_robin TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -append 'ple_round_robin' FAIL vmexit_ple_round_robin (timeout; duration=90s) TESTNAME=vmexit_tscdeadline TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline FAIL vmexit_tscdeadline (timeout; duration=90s) TESTNAME=vmexit_tscdeadline_immed TIMEOUT=90s ACCEL= ./x86/run x86/vmexit.flat -smp 1 -cpu qemu64,+x2apic,+tsc-deadline -append tscdeadline_immed FAIL vmexit_tscdeadline_immed (timeout; duration=90s) TESTNAME=smap TIMEOUT=90s ACCEL= ./x86/run x86/smap.flat -smp 1 -cpu host FAIL smap (timeout; duration=90s) TESTNAME=eventinj TIMEOUT=90s ACCEL= ./x86/run x86/eventinj.flat -smp 1 FAIL eventinj (timeout; duration=90s) TESTNAME=hypercall TIMEOUT=90s ACCEL= ./x86/run x86/hypercall.flat -smp 1 FAIL hypercall (timeout; duration=90s) TESTNAME=msr TIMEOUT=90s ACCEL= ./x86/run x86/msr.flat -smp 1 FAIL msr (timeout; duration=90s) TESTNAME=port80 TIMEOUT=90s ACCEL= ./x86/run x86/port80.flat -smp 1 FAIL port80 (timeout; duration=90s) TESTNAME=realmode TIMEOUT=90s ACCEL= ./x86/run x86/realmode.flat -smp 1 FAIL realmode (timeout; duration=90s) TESTNAME=s3 TIMEOUT=90s ACCEL= ./x86/run x86/s3.flat -smp 1 FAIL s3 (timeout; duration=90s) TESTNAME=sieve TIMEOUT=90s ACCEL= ./x86/run x86/sieve.flat -smp 1 FAIL sieve (timeout; duration=90s) TESTNAME=tsc TIMEOUT=90s ACCEL= ./x86/run x86/tsc.flat -smp 1 -cpu kvm64,+rdtscp FAIL tsc (timeout; duration=90s) TESTNAME=tsc_adjust TIMEOUT=90s ACCEL= ./x86/run x86/tsc_adjust.flat -smp 1 -cpu host FAIL tsc_adjust (timeout; duration=90s) TESTNAME=taskswitch TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch.flat -smp 1 FAIL taskswitch (timeout; duration=90s) TESTNAME=taskswitch2 TIMEOUT=90s ACCEL= ./x86/run x86/taskswitch2.flat -smp 1 FAIL taskswitch2 (timeout; duration=90s) TESTNAME=kvmclock_test TIMEOUT=90s ACCEL= ./x86/run x86/kvmclock_test.flat -smp 2 --append "1000 `date +%s`" FAIL kvmclock_test (timeout; duration=90s) TESTNAME=umip TIMEOUT=90s ACCEL= ./x86/run x86/umip.flat -smp 1 -cpu qemu64,+umip FAIL umip (timeout; duration=90s) TESTNAME=hyperv_synic TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_synic.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev FAIL hyperv_synic (timeout; duration=90s) TESTNAME=hyperv_connections TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_connections.flat -smp 2 -cpu kvm64,hv_vpindex,hv_synic -device hyperv-testdev FAIL hyperv_connections (timeout; duration=90s) TESTNAME=hyperv_stimer TIMEOUT=90s ACCEL= ./x86/run x86/hyperv_stimer.flat -smp 2 -cpu kvm64,hv_vpindex,hv_time,hv_synic,hv_stimer -device hyperv-testdev FAIL hyperv_stimer (timeout; duration=90s) ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-16-generic 4.18.0-16.17 ProcVersionSignature: User Name 4.18.0-16.17-generic 4.18.20 Uname: Linux 4.18.0-16-generic i686 AlsaDevices: total 0
[Kernel-packages] [Bug 1849825] Re: cpuset_inherit in controllers from ubuntu_ltp failed on D/E s390x LPAR
** Changed in: linux (Ubuntu Disco) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849825 Title: cpuset_inherit in controllers from ubuntu_ltp failed on D/E s390x LPAR Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Won't Fix Bug description: startup='Thu Oct 24 09:48:22 2019' cpuset_inherit 1 TPASS: cpus: Inherited information is right! cpuset_inherit 3 TFAIL: cpus: Test result - 0 Expected string - "EMPTY" cpuset_inherit 5 TFAIL: cpus: Test result - 0-3 Expected string - "EMPTY" cpuset_inherit 7 TPASS: mems: Inherited information is right! cpuset_inherit 9 TFAIL: mems: Test result - 0 Expected string - "EMPTY" cpuset_inherit 11 TFAIL: mems: Test result - 0 Expected string - "EMPTY" cpuset_inherit 13 TPASS: cpu_exclusive: Inherited information is right! cpuset_inherit 15 TPASS: cpu_exclusive: Inherited information is right! cpuset_inherit 17 TPASS: mem_exclusive: Inherited information is right! cpuset_inherit 19 TPASS: mem_exclusive: Inherited information is right! cpuset_inherit 21 TPASS: mem_hardwall: Inherited information is right! cpuset_inherit 23 TPASS: mem_hardwall: Inherited information is right! cpuset_inherit 25 TPASS: memory_migrate: Inherited information is right! cpuset_inherit 27 TPASS: memory_migrate: Inherited information is right! cpuset_inherit 29 TPASS: memory_spread_page: Inherited information is right! cpuset_inherit 31 TPASS: memory_spread_page: Inherited information is right! cpuset_inherit 33 TPASS: memory_spread_slab: Inherited information is right! cpuset_inherit 35 TPASS: memory_spread_slab: Inherited information is right! cpuset_inherit 37 TPASS: sched_load_balance: Inherited information is right! cpuset_inherit 39 TPASS: sched_load_balance: Inherited information is right! cpuset_inherit 41 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 43 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 45 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 47 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 49 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 51 TPASS: sched_relax_domain_level: Inherited information is right! cpuset_inherit 53 TPASS: sched_relax_domain_level: Inherited information is right! tag=cpuset_inherit stime=1571906902 dur=0 exit=exited stat=1 core=no cu=9 cs=31 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-33-generic 5.0.0-33.35 ProcVersionSignature: Ubuntu 5.0.0-33.35-generic 5.0.21 Uname: Linux 5.0.0-33-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair 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-0ubuntu27.1 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. CurrentDmesg: Date: Fri Oct 25 13:07:48 2019 HibernationDevice: RESUME=UUID=eae923f9-f5a4-41c0-b3e4-04786207dbaa IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: root=UUID=1a6af794-84a9-4034-a213-39506b9bb91c crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.178.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849825/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
