[Kernel-packages] [Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
Hi Elvis, Guilherme Guilherme, I went and had a look at what was built into 5.4.0-39-generic, and the commit "nfs: fix NULL deference in nfs4_get_valid_delegation" wasn't there. >From what I can see looking at the git tree located at: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/?h=master-next The commit is there: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next&id=4cb9edb12735c41f48dff1741bf17e99384f55e3 But it is currently untagged, on master-next. From the changelog of 5.4.0-40-generic, we can see it is listed there: https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal/commit/?h=master-next&id=96bef2d870f538dd0849a0f8d7e343a01ce6bbf0 So I am expecting the fix to land in 5.4.0-40-generic which should be tagged shortly, and likely built and pushed to -proposed early next week as a part of the next SRU cycle. Elvis, this is why 5.4.0-39-generic is still broken, since the fix will likely arrive in 5.4.0-40-generic. If you like, we can make you a test kernel with the fix so you can double check the patch really fixes your problems. It seems 5.4.0-39-generic is in -updates now, but it is untagged. If it is tagged tomorrow, either myself or Guilherme will build you a test kernel. ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: New => Fix Committed ** Changed in: linux (Ubuntu Focal) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation Status in linux package in Ubuntu: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: We are getting the following on an NFSv4 client running focal (kernel 5.4.0-33.37): [296787.347971] BUG: unable to handle page fault for address: ffb0 [296787.350255] #PF: supervisor read access in kernel mode [296787.352315] #PF: error_code(0x) - not-present page [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 [296787.355798] Oops: [#2] SMP NOPTI [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P D OE 5.4.0-33-generic #37-Ubuntu [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 10/04/2019 [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc] [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246 [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: [296787.370648] RDX: 8000 RSI: RDI: [296787.372559] RBP: b7b1634a7da0 R08: R09: 8080808080808080 [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 9ef781f22600 [296787.376330] R13: R14: 9efe1db4bc00 R15: c0cc2950 [296787.378220] FS: () GS:9ef78fc4() knlGS: [296787.380165] CS: 0010 DS: ES: CR0: 80050033 [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 [296787.384031] Call Trace: [296787.385985] nfs4_open_prepare+0x89/0x1e0 [nfsv4] [296787.387973] rpc_prepare_task+0x1f/0x30 [sunrpc] [296787.389971] __rpc_execute+0x8c/0x3a0 [sunrpc] [296787.391903] rpc_async_schedule+0x30/0x50 [sunrpc] [296787.393787] process_one_work+0x1eb/0x3b0 [296787.395617] worker_thread+0x4d/0x400 [296787.397431] kthread+0x104/0x140 [296787.399166] ? process_one_work+0x3b0/0x3b0 [296787.400868] ? kthread_park+0x90/0x90 [296787.402518] ret_from_fork+0x1f/0x40 [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore k10temp ccp ipmi
[Kernel-packages] [Bug 1810130] Re: ic2-HTIX5288
*** This bug is a duplicate of bug 1884288 *** https://bugs.launchpad.net/bugs/1884288 ** This bug has been marked a duplicate of bug 1884288 LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810130 Title: ic2-HTIX5288 Status in linux package in Ubuntu: Expired Bug description: touchpad not working Ubuntu Disco Dingo (development branch) WINBOOK 13 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: docmint2172 F pulseaudio /dev/snd/controlC1: docmint2172 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 31 00:55:26 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230) MachineType: AXDIA International GmbH WINBOOK 13 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset i8042.nomux=1 i8042.reset RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2017 dmi.bios.vendor: WINBOOK 13 dmi.bios.version: 1.6 dmi.board.asset.tag: Default string dmi.board.name: K132 dmi.board.vendor: AXDIA International GmbH dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: WINBOOK 13 dmi.product.sku: WINBOOK13-K132-02 dmi.product.version: Default string dmi.sys.vendor: AXDIA International GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885033] Re: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04)
Hi, what's your `sudo acpi_listen` output when pressed Fn-F6? And what's the output of `cat /sys/devices/pci:00/:00:1f.0/PNP0C09:00/VPC2004:00/touchpad`? You mentioned it doesn't change, but what's the output exactly? ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885033 Title: Touchpad switch not working (Lenovo IdeaPad L340-15IRH, Kubuntu 20.04) Status in linux package in Ubuntu: Incomplete Bug description: The touchpad switch, Fn-F6, does not work for me. It does work on Windows 10 (dual boot) The touchpad works well, but I can only set the option in System Conguration. See launchpad answer : https://answers.launchpad.net/ubuntu/+question/691511 Kubuntu 20.04 Lenovo IdeaPad L340-15IRH - Type 81LK --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: yann 1350 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-02-20 (125 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f2:b604 Chicony Electronics Co., Ltd Integrated Camera (1280x720@30) Bus 001 Device 002: ID 093a:2510 Pixart Imaging, Inc. Optical Mouse Bus 001 Device 004: ID 0cf3:e500 Qualcomm Atheros Communications Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 81LK NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=0ac30ea3-dc16-4323-a1a3-acea99fa90b5 ro quiet splash resume=/dev/nvme0n1p6 vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-05-14 (41 days ago) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/10/2020 dmi.bios.vendor: LENOVO dmi.bios.version: BGCN29WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: NO DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad L340-15IRH Gaming dmi.modalias: dmi:bvnLENOVO:bvrBGCN29WW:bd02/10/2020:svnLENOVO:pn81LK:pvrIdeaPadL340-15IRHGaming:rvnLENOVO:rnLNVNB161216:rvrNODPK:cvnLENOVO:ct10:cvrIdeaPadL340-15IRHGaming: dmi.product.family: IdeaPad L340-15IRH Gaming dmi.product.name: 81LK dmi.product.sku: LENOVO_MT_81LK_BU_idea_FM_IdeaPad L340-15IRH Gaming dmi.product.version: IdeaPad L340-15IRH Gaming dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1885033/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1810130] Re: ic2-HTIX5288
This is not necessarily a duplicate of bug 1884288 for they don't share the same symptoms judging from the information available till now. This one has: [8.928368] i2c_hid i2c-HTIX5288:00: failed to reset device. [ 15.072321] i2c_hid i2c-HTIX5288:00: failed to reset device. [ 21.216318] i2c_hid i2c-HTIX5288:00: failed to reset device. [ 27.360347] i2c_hid i2c-HTIX5288:00: failed to reset device. [ 28.384325] i2c_hid i2c-HTIX5288:00: can't add hid device: -61 [ 28.386852] i2c_hid: probe of i2c-HTIX5288:00 failed with error -61 ** This bug is no longer a duplicate of bug 1884288 LapBook Pro touchpad (HTIX5288:00) sometimes does not work when machine is restarted -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1810130 Title: ic2-HTIX5288 Status in linux package in Ubuntu: Expired Bug description: touchpad not working Ubuntu Disco Dingo (development branch) WINBOOK 13 ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-4.18.0-11-generic 4.18.0-11.12 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu14 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: docmint2172 F pulseaudio /dev/snd/controlC1: docmint2172 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Dec 31 00:55:26 2018 InstallationDate: Installed on 2018-12-30 (0 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20181230) MachineType: AXDIA International GmbH WINBOOK 13 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=ea66942b-3d65-4c18-a99e-d02e31358a42 ro recovery nomodeset i8042.nomux=1 i8042.reset RelatedPackageVersions: linux-restricted-modules-4.18.0-11-generic N/A linux-backports-modules-4.18.0-11-generic N/A linux-firmware 1.176 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/27/2017 dmi.bios.vendor: WINBOOK 13 dmi.bios.version: 1.6 dmi.board.asset.tag: Default string dmi.board.name: K132 dmi.board.vendor: AXDIA International GmbH dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnWINBOOK13:bvr1.6:bd11/27/2017:svnAXDIAInternationalGmbH:pnWINBOOK13:pvrDefaultstring:rvnAXDIAInternationalGmbH:rnK132:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: Notebook dmi.product.name: WINBOOK 13 dmi.product.sku: WINBOOK13-K132-02 dmi.product.version: Default string dmi.sys.vendor: AXDIA International GmbH To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1810130/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884900] Re: Touchpad not working
P: /devices/platform/i8042/serio1 L: 0 E: DEVPATH=/devices/platform/i8042/serio1 E: SUBSYSTEM=serio E: SERIO_TYPE=01 E: SERIO_PROTO=00 E: SERIO_ID=00 E: SERIO_EXTRA=00 E: MODALIAS=serio:ty01pr00id00ex00 E: SERIO_FIRMWARE_ID=PNP: DLL0597 PNP0f13 Please append following kernel boot parameters, reboot and attach output of `journalctl -b`: "dyndbg=file drivers/input/* +pt" i8042.debug=1 log_buf_len=32M For detailed steps, please see https://askubuntu.com/questions/19486 /how-do-i-add-a-kernel-boot-parameter. ** Tags added: hwe-touchpad ** 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/1884900 Title: Touchpad not working Status in linux package in Ubuntu: Incomplete Bug description: Dear Sir, I have updated ubuntu 18.04 to 20.04 in the last 4 days. My laptop's touchpad worked well in the last system, but when I have updated it to 20.04 then touchpad not working, when I started my laptop. I have use a mouse. When I have start my laptop with connected mouse then touchpad not work. but, when I have started a laptop without connected with mouse then touchpad worked. Solve this issue properly. Thank you... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spshubham 1767 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 12:53:16 2020 HibernationDevice: RESUME=UUID=473a994d-cd87-4373-94ae-e2ff8edce101 InstallationDate: Installed on 2020-06-18 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=13763414-9331-414c-b5ad-ef7d3fa37ff2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-20 (3 days ago) dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron3521:pvrA16:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884997] Re: no touchpad detected, not working at all
** 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/1884997 Title: no touchpad detected, not working at all Status in linux package in Ubuntu: Incomplete Bug description: hello, i bought a new pc and installed ubuntu 20.04 and windows 10 on it. on ubuntu os my touchpad doesn't work at all, since installation process but it does on windows. the pc is a lenovo pc and one of the latest released one. when i plug in a usb mouse the mouse works fine but the touchpad still don't. it even doesn't show the touchpad when i type in (1) "cat /proc/bus/input/devices". only the usb mouse twice. i tryed a lot and don't know how to help myself any further. i attached a file "devices" where printed my output of (1). thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabian 1032 F pulseaudio /dev/snd/pcmC0D0p: fabian 1032 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:21:17 2020 InstallationDate: Installed on 2020-06-17 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a65a602e-ae73-4354-94f9-2f99e2bff055 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885072] [NEW] [SRU][OEM-5.6/U] Fix r8117 firmware base issue
Public bug reported: [Impact] Realtek 8117 failed to work after loading firmware on 5.5+ kernel. [Fix] Firmware should reset ocp_base, but not on r8117. Correct the ocp_base in the driver. Then it works well. [Test] Verified on hardware, link status is OK, iperf test result is good. [Regression Potential] Low. Fixed issue, cherry-picked from maintainer's tree. Due to 5.4- kernel needs more patches, SRU the fix on 5.5+ kernel first. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: oem-priority originate-from-1880781 originate-from-1881081 sutton ** Tags added: oem-priority originate-from-1881081 sutton ** Tags added: originate-from-1880781 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885072 Title: [SRU][OEM-5.6/U] Fix r8117 firmware base issue Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: [Impact] Realtek 8117 failed to work after loading firmware on 5.5+ kernel. [Fix] Firmware should reset ocp_base, but not on r8117. Correct the ocp_base in the driver. Then it works well. [Test] Verified on hardware, link status is OK, iperf test result is good. [Regression Potential] Low. Fixed issue, cherry-picked from maintainer's tree. Due to 5.4- kernel needs more patches, SRU the fix on 5.5+ kernel first. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1885072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884997] Re: no touchpad detected, not working at all
Please append following kernel boot parameters, reboot and attach output of `journalctl -b`: "dyndbg=file drivers/input/* +pt" i8042.debug=1 i8042.nopnp=1 log_buf_len=32M For detailed steps, please see https://askubuntu.com/questions/19486 /how-do-i-add-a-kernel-boot-parameter. ** 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/1884997 Title: no touchpad detected, not working at all Status in linux package in Ubuntu: Incomplete Bug description: hello, i bought a new pc and installed ubuntu 20.04 and windows 10 on it. on ubuntu os my touchpad doesn't work at all, since installation process but it does on windows. the pc is a lenovo pc and one of the latest released one. when i plug in a usb mouse the mouse works fine but the touchpad still don't. it even doesn't show the touchpad when i type in (1) "cat /proc/bus/input/devices". only the usb mouse twice. i tryed a lot and don't know how to help myself any further. i attached a file "devices" where printed my output of (1). thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabian 1032 F pulseaudio /dev/snd/pcmC0D0p: fabian 1032 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:21:17 2020 InstallationDate: Installed on 2020-06-17 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a65a602e-ae73-4354-94f9-2f99e2bff055 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884981] Re: The touchpad soesn't work at all
Please append following kernel boot parameters, reboot and attach output of `journalctl -b`: "dyndbg=file drivers/input/* +pt" i8042.debug=1 i8042.nopnp=1 log_buf_len=32M For detailed steps, please see https://askubuntu.com/questions/19486 /how-do-i-add-a-kernel-boot-parameter. ** Tags added: hwe-touchpad ** 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/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Incomplete Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885072] 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 1885072 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885072 Title: [SRU][OEM-5.6/U] Fix r8117 firmware base issue Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Realtek 8117 failed to work after loading firmware on 5.5+ kernel. [Fix] Firmware should reset ocp_base, but not on r8117. Correct the ocp_base in the driver. Then it works well. [Test] Verified on hardware, link status is OK, iperf test result is good. [Regression Potential] Low. Fixed issue, cherry-picked from maintainer's tree. Due to 5.4- kernel needs more patches, SRU the fix on 5.5+ kernel first. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1885072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** 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/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 1884897] Re: touchpad not working (not in the lsit of my devices) I use a laptop chuwi
[1.913078] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vdd not found, using dummy regulator [1.913100] i2c_hid i2c-HTIX5288:00: i2c-HTIX5288:00 supply vddl not found, using dummy regulator [1.915051] i2c_hid i2c-HTIX5288:00: weird size of HID descriptor (2) You'll need a BIOS/firmware update to fix this first. ** Tags added: hwe-touchpad ** 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/1884897 Title: touchpad not working (not in the lsit of my devices) I use a laptop chuwi Status in linux package in Ubuntu: Incomplete Bug description: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0003 Vendor=0c45 Product=6366 Version=0100 N: Name="USB 2.0 Camera: USB Camera" P: Phys=usb-:00:15.0-7/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-7/1-7:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=046d Product=4008 Version=0111 N: Name="Logitech M185" P: Phys=usb-:00:15.0-6/input1:1 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-6/1-6:1.1/0003:046D:C52F.0002/0003:046D:4008.0003/input/input23 U: Uniq=4008-03-e8-c0-b4 H: Handlers=kbd mouse0 event14 B: PROP=0 B: EV=1f B: KEY=3f000301ff 0 0 48317aff32d bfd6 0001 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1943 B: ABS=1 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-26-generic
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Ok... Problem is solved by ... puling out POWER from monitor! It is weird but for some reason when i unplugged monitor from power and pulled it again it start showing my screen. It is weird but to be honest I've tried so many things before and nothing helped... I've changed drivers few times... so many restarts... I've even changed hdmi cabel. I assume that monitor is OK because it showed grub/spash screen and when I tried run older linux kernel it showd text on second screen. Not sure what went wrong... maybe something with strength of hdmi signal? Screen still turns black every few minutes for ~second but at least it works. Thanks :) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
* When I pulled monitor from power and plugged it again it start showing my screen. (I should read it before i clicked POST. ... yea. There is no 'edit' here... I have to remember that) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884899] Re: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0
Cannot reproduce this very issue with the fallback Kernel. Linux sisc-ws 5.4.0-33-generic #37-Ubuntu SMP Thu May 21 12:53:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Instead, seeing some issues with nouveau. See attached dmesg output with older kernel ** Attachment added: "dmesg_5.4.0-33-generic.log" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884899/+attachment/5386974/+files/dmesg_5.4.0-33-generic.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884899 Title: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0 Status in linux package in Ubuntu: Confirmed Bug description: After login into the gnome session, the session freezes, either instantly or after a few seconds ( only mouse is working ). The Oops does not occur on every startup. After a few restarts, the kernel Oops does not occur anymore during the complete session. Dell Perfomance Checks ( including memory checks ) did not show any failures. BIOS is uptodate ( 1.16.2 for Dell Precision 5530 ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: scsi 3876 F pulseaudio /dev/snd/controlC1: scsi 3876 F pulseaudio /dev/snd/controlC0: scsi 3876 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 09:00:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-10 (530 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2c719e60-4d36-4042-aa72-aa62403b19a1 ro acpi_osi=Linux-Dell-Video alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-04 (50 days ago) WifiSyslog: dmi.bios.date: 04/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.2 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.2:bd04/21/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Verified oem-5.6 1012. ** Tags removed: verification-needed-focal ** Tags added: verification-done-focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/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: In Progress 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 Committed Status in linux source package in Groovy: In Progress 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 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 40 00 0f kernel: RSP: 0018:b5f5c00fbcf8 EFLAGS: 00010
[Kernel-packages] [Bug 1884691] Re: Power button don’t work
Hi, by "power button" do you mean the physical power button on your ultrabook, or the power button on GNOME menu? ** 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/1884691 Title: Power button don’t work Status in linux package in Ubuntu: Incomplete Bug description: The power button hasn’t worked for a while (it was supposed to turn off, but it doesn’t respond and nothing appears). I already tried it through dconf but it didn’t work and also the power settings, the power button is already set to turn off. Note: when it is set to suspend it suspends and when it is set to do nothing, nothing happens (of course) ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: neto 1320 F pulseaudio /dev/snd/pcmC0D0p: neto 1320 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: Budgie:GNOME Date: Mon Jun 22 22:20:30 2020 InstallationDate: Installed on 2020-02-28 (115 days ago) InstallationMedia: Ubuntu-Budgie 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: SAMSUNG ELECTRONICS CO., LTD. 530U3C/530U4C/532U3C ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=7949306b-901a-4602-8b3f-ce5078d80526 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-09 (44 days ago) dmi.bios.date: 07/22/2015 dmi.bios.vendor: Phoenix Technologies Ltd. dmi.bios.version: P13ABH dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: NP530U3C-AD5BR dmi.board.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.board.version: FAB1 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 9 dmi.chassis.vendor: SAMSUNG ELECTRONICS CO., LTD. dmi.chassis.version: 0.1 dmi.modalias: dmi:bvnPhoenixTechnologiesLtd.:bvrP13ABH:bd07/22/2015:svnSAMSUNGELECTRONICSCO.,LTD.:pn530U3C/530U4C/532U3C:pvr0.1:rvnSAMSUNGELECTRONICSCO.,LTD.:rnNP530U3C-AD5BR:rvrFAB1:cvnSAMSUNGELECTRONICSCO.,LTD.:ct9:cvr0.1: dmi.product.family: ChiefRiver System dmi.product.name: 530U3C/530U4C/532U3C dmi.product.sku: System SKUNumber dmi.product.version: 0.1 dmi.sys.vendor: SAMSUNG ELECTRONICS CO., LTD. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884691/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884897] [NEW] touchpad not working (not in the lsit of my devices) I use a laptop chuwi
Public bug reported: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0003 Vendor=0c45 Product=6366 Version=0100 N: Name="USB 2.0 Camera: USB Camera" P: Phys=usb-:00:15.0-7/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-7/1-7:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=046d Product=4008 Version=0111 N: Name="Logitech M185" P: Phys=usb-:00:15.0-6/input1:1 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-6/1-6:1.1/0003:046D:C52F.0002/0003:046D:4008.0003/input/input23 U: Uniq=4008-03-e8-c0-b4 H: Handlers=kbd mouse0 event14 B: PROP=0 B: EV=1f B: KEY=3f000301ff 0 0 48317aff32d bfd6 0001 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1943 B: ABS=1 B: MSC=10 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 4794 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 07:17:56 2020 Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 0c45:6366 Microdia USB 2.0 Camera Bus 001 Device 005: ID 046d:c52f Logitech, Inc. Unifying Receiver Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub 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
[Kernel-packages] [Bug 1884897] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884897 Title: touchpad not working (not in the lsit of my devices) I use a laptop chuwi Status in linux package in Ubuntu: Confirmed Bug description: I: Bus=0019 Vendor= Product=0005 Version= N: Name="Lid Switch" P: Phys=PNP0C0D/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/device:03/PNP0C09:00/PNP0C0D:00/input/input0 U: Uniq= H: Handlers=event0 B: PROP=0 B: EV=21 B: SW=1 I: Bus=0019 Vendor= Product=0001 Version= N: Name="Power Button" P: Phys=PNP0C0C/button/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0C0C:00/input/input1 U: Uniq= H: Handlers=kbd event1 B: PROP=0 B: EV=3 B: KEY=10 0 I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0019 Vendor= Product=0006 Version= N: Name="Video Bus" P: Phys=LNXVIDEO/video/input0 S: Sysfs=/devices/LNXSYSTM:00/LNXSYBUS:00/PNP0A08:00/LNXVIDEO:00/input/input3 U: Uniq= H: Handlers=kbd event3 B: PROP=0 B: EV=3 B: KEY=3e000b 0 0 0 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID events" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input4 U: Uniq= H: Handlers=rfkill kbd event4 B: PROP=0 B: EV=13 B: KEY=810003 504000 1e29400020 0 B: MSC=10 I: Bus=0019 Vendor= Product= Version= N: Name="Intel HID 5 button array" P: Phys= S: Sysfs=/devices/platform/INT33D5:00/input/input5 U: Uniq= H: Handlers=kbd event5 B: PROP=0 B: EV=13 B: KEY=2 0 0 0 0 1 0 201c 0 B: MSC=10 I: Bus=0003 Vendor=0c45 Product=6366 Version=0100 N: Name="USB 2.0 Camera: USB Camera" P: Phys=usb-:00:15.0-7/button S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-7/1-7:1.0/input/input6 U: Uniq= H: Handlers=kbd event6 B: PROP=0 B: EV=3 B: KEY=10 0 0 0 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Mic" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input7 U: Uniq= H: Handlers=event7 B: PROP=0 B: EV=21 B: SW=10 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH Headphone" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input8 U: Uniq= H: Handlers=event8 B: PROP=0 B: EV=21 B: SW=4 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=3" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input9 U: Uniq= H: Handlers=event9 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=7" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input10 U: Uniq= H: Handlers=event10 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=8" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input11 U: Uniq= H: Handlers=event11 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=9" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input12 U: Uniq= H: Handlers=event12 B: PROP=0 B: EV=21 B: SW=140 I: Bus= Vendor= Product= Version= N: Name="HDA Intel PCH HDMI/DP,pcm=10" P: Phys=ALSA S: Sysfs=/devices/pci:00/:00:0e.0/sound/card0/input13 U: Uniq= H: Handlers=event13 B: PROP=0 B: EV=21 B: SW=140 I: Bus=0003 Vendor=046d Product=4008 Version=0111 N: Name="Logitech M185" P: Phys=usb-:00:15.0-6/input1:1 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-6/1-6:1.1/0003:046D:C52F.0002/0003:046D:4008.0003/input/input23 U: Uniq=4008-03-e8-c0-b4 H: Handlers=kbd mouse0 event14 B: PROP=0 B: EV=1f B: KEY=3f000301ff 0 0 48317aff32d bfd6 0001 130ff38b17c000 677bfad9415fed 19ed6804400 1002 B: REL=1943 B: ABS=1 B: MSC=10 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 4794 F pulseau
[Kernel-packages] [Bug 1884899] [NEW] Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0
Public bug reported: After login into the gnome session, the session freezes, either instantly or after a few seconds ( only mouse is working ). The Oops does not occur on every startup. After a few restarts, the kernel Oops does not occur anymore during the complete Dell Perfomance Checks ( including memory checks ) did not show any failures. BIOS is uptodate ( 1.16.2 for Dell Precision 5530 ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: scsi 3876 F pulseaudio /dev/snd/controlC1: scsi 3876 F pulseaudio /dev/snd/controlC0: scsi 3876 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 09:00:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-10 (530 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2c719e60-4d36-4042-aa72-aa62403b19a1 ro acpi_osi=Linux-Dell-Video alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-04 (50 days ago) WifiSyslog: dmi.bios.date: 04/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.2 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.2:bd04/21/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal kernel-oops third-party-packages ** Attachment added: "dmesg log with kernel oops" https://bugs.launchpad.net/bugs/1884899/+attachment/5386667/+files/dmesg.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884899 Title: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0 Status in linux package in Ubuntu: New Bug description: After login into the gnome session, the session freezes, either instantly or after a few seconds ( only mouse is working ). The Oops does not occur on every startup. After a few restarts, the kernel Oops does not occur anymore during the complete Dell Perfomance Checks ( including memory checks ) did not show any failures. BIOS is uptodate ( 1.16.2 for Dell Precision 5530 ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: scsi 3876 F pulseaudio /dev/snd/controlC1: scsi 3876 F pulseaudio /dev/snd/controlC0: scsi 3876 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 09:00:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-10 (530 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2c719e60-4d36-4042-aa72-aa62403b19a1 ro acpi_osi=Linux-Dell-Video alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-04 (50 days ago) WifiSyslog: dmi.bios.date: 04/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.2 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.
[Kernel-packages] [Bug 1874519] Re: ZFS installation on Raspberry Pi is problematic
https://lists.ubuntu.com/archives/kernel-team/2020-June/111366.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to zfs-linux in Ubuntu. https://bugs.launchpad.net/bugs/1874519 Title: ZFS installation on Raspberry Pi is problematic Status in zfs-linux package in Ubuntu: Triaged Bug description: Version: Ubuntu Server 20.04 - preinstalled 64-bit image for Raspberry Pi. ZFS on the Pi under 20.04 is currently a bit problematic. Upon issuing the command 'zpool status', I'm helpfully directed to install zfsutils-linux. When I do this, it complains that it cannot find the ZFS module, then errors out. Worse than that, the zfsutils-linux package does not depend on the zfs-dkms package, so it doesn't attempt to build the ZFS kernel modules automatically. The workaround is to install zfs-dkms, which builds the required kernel modules. (Once this has been done, the usual errors when installing the zfsutils-linux package, caused by there being no ZFS pools on the system, can be worked around by creating a zpool, then rerunning 'sudo apt install zfsutils-linux', as with previous versions of Ubuntu and Debian). I have not tested on other hardware platforms - this problem may also exist on other platforms where the user has not selected to install to ZFS. I have selected 'zfsutils' as the affected package, which is not the name of an actual current package, since launchpad won't let me submit the bug without selecting a package, however it's not clear to me that the problem is caused by that package. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1874519/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884899] Re: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0
** Description changed: After login into the gnome session, the session freezes, either instantly or after a few seconds ( only mouse is working ). The Oops does not occur on every startup. After a few restarts, the kernel Oops - does not occur anymore during the complete + does not occur anymore during the complete session. Dell Perfomance Checks ( including memory checks ) did not show any failures. BIOS is uptodate ( 1.16.2 for Dell Precision 5530 ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC2: scsi 3876 F pulseaudio - /dev/snd/controlC1: scsi 3876 F pulseaudio - /dev/snd/controlC0: scsi 3876 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC2: scsi 3876 F pulseaudio + /dev/snd/controlC1: scsi 3876 F pulseaudio + /dev/snd/controlC0: scsi 3876 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 09:00:05 2020 DistributionChannelDescriptor: - # This is a distribution channel descriptor - # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor - canonical-oem-somerville-xenial-amd64-osp1-20171027-1 + # This is a distribution channel descriptor + # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor + canonical-oem-somerville-xenial-amd64-osp1-20171027-1 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-10 (530 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2c719e60-4d36-4042-aa72-aa62403b19a1 ro acpi_osi=Linux-Dell-Video alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-37-generic N/A - linux-backports-modules-5.4.0-37-generic N/A - linux-firmware1.187 + linux-restricted-modules-5.4.0-37-generic N/A + linux-backports-modules-5.4.0-37-generic N/A + linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-04 (50 days ago) WifiSyslog: - + dmi.bios.date: 04/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.2 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.2:bd04/21/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884899 Title: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0 Status in linux package in Ubuntu: New Bug description: After login into the gnome session, the session freezes, either instantly or after a few seconds ( only mouse is working ). The Oops does not occur on every startup. After a few restarts, the kernel Oops does not occur anymore during the complete session. Dell Perfomance Checks ( including memory checks ) did not show any failures. BIOS is uptodate ( 1.16.2 for Dell Precision 5530 ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: scsi 3876 F pulseaudio /dev/snd/controlC1: scsi 3876 F pulseaudio /dev/snd/controlC0: scsi 3876 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 09:00:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-10 (530 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2c719e60-4d36-4042-aa72-aa62403b19a1 ro acpi_osi=Linux-Dell-Video alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 RelatedPackageVersions:
[Kernel-packages] [Bug 1884899] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884899 Title: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0 Status in linux package in Ubuntu: Confirmed Bug description: After login into the gnome session, the session freezes, either instantly or after a few seconds ( only mouse is working ). The Oops does not occur on every startup. After a few restarts, the kernel Oops does not occur anymore during the complete session. Dell Perfomance Checks ( including memory checks ) did not show any failures. BIOS is uptodate ( 1.16.2 for Dell Precision 5530 ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: scsi 3876 F pulseaudio /dev/snd/controlC1: scsi 3876 F pulseaudio /dev/snd/controlC0: scsi 3876 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 09:00:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-10 (530 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2c719e60-4d36-4042-aa72-aa62403b19a1 ro acpi_osi=Linux-Dell-Video alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-04 (50 days ago) WifiSyslog: dmi.bios.date: 04/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.2 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.2:bd04/21/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752194] Re: Intel GPU tools crash with "Couldn't map MMIO region"
Ubuntu 18, Intel(R) UHD Graphics 620 $ sudo intel_gpu_top (intel_gpu_top:832) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145: (intel_gpu_top:832) intel-mmio-CRITICAL: Failed assertion: !(error != 0) (intel_gpu_top:832) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted (intel_gpu_top:832) intel-mmio-CRITICAL: Couldn't map MMIO region Stack trace: #0 [_init+0x7b87] #1 [_init+0x5420] #2 [_init+0xe85] #3 [__libc_start_main+0xe7] #4 [_init+0x1c92] Test (null) failed. DEBUG (intel_gpu_top:832) intel-chipset-DEBUG: Test requirement passed: pci_dev (intel_gpu_top:832) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145: (intel_gpu_top:832) intel-mmio-CRITICAL: Failed assertion: !(error != 0) (intel_gpu_top:832) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted (intel_gpu_top:832) intel-mmio-CRITICAL: Couldn't map MMIO region (intel_gpu_top:832) igt-core-INFO: Stack trace: (intel_gpu_top:832) igt-core-INFO: #0 [_init+0x7b87] (intel_gpu_top:832) igt-core-INFO: #1 [_init+0x5420] (intel_gpu_top:832) igt-core-INFO: #2 [_init+0xe85] (intel_gpu_top:832) igt-core-INFO: #3 [__libc_start_main+0xe7] (intel_gpu_top:832) igt-core-INFO: #4 [_init+0x1c92] END FAIL (-1.000s) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to intel-gpu-tools in Ubuntu. https://bugs.launchpad.net/bugs/1752194 Title: Intel GPU tools crash with "Couldn't map MMIO region" Status in intel-gpu-tools package in Ubuntu: Confirmed Bug description: Trying to run anything in intel-gpu-tools (tested intel_gpu_top, intel_gpu_time and intel_backlight) on my laptop (which has hybrid graphics, GTX 760m (proprietary nvidia driver not installed right now) + Intel 4th gen iGPU) as root yields the following output: (intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145: (intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0) (intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted (intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region Stack trace: #0 [_init+0x1753f] #1 [_init+0xc978] #2 [_init+0x118d] #3 [__libc_start_main+0xf1] #4 [_init+0x1fba] #5 [+0x1fba] Test (null) failed. DEBUG (intel_gpu_top:23021) intel-chipset-DEBUG: Test requirement passed: pci_dev (intel_gpu_top:23021) intel-mmio-CRITICAL: Test assertion failure function intel_mmio_use_pci_bar, file ../../lib/intel_mmio.c:145: (intel_gpu_top:23021) intel-mmio-CRITICAL: Failed assertion: !(error != 0) (intel_gpu_top:23021) intel-mmio-CRITICAL: Last errno: 1, Operation not permitted (intel_gpu_top:23021) intel-mmio-CRITICAL: Couldn't map MMIO region (intel_gpu_top:23021) igt-core-INFO: Stack trace: (intel_gpu_top:23021) igt-core-INFO: #0 [_init+0x1753f] (intel_gpu_top:23021) igt-core-INFO: #1 [_init+0xc978] (intel_gpu_top:23021) igt-core-INFO: #2 [_init+0x118d] (intel_gpu_top:23021) igt-core-INFO: #3 [__libc_start_main+0xf1] (intel_gpu_top:23021) igt-core-INFO: #4 [_init+0x1fba] (intel_gpu_top:23021) igt-core-INFO: #5 [+0x1fba] END FAIL (-1.000s) Happens under bot Wayland and XOrg. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: intel-gpu-tools 1.20-1ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13 Uname: Linux 4.13.0-32-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.7 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Feb 28 00:30:15 2018 InstallationDate: Installed on 2015-11-25 (825 days ago) InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) SourcePackage: intel-gpu-tools UpgradeStatus: Upgraded to artful on 2017-11-01 (118 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-gpu-tools/+bug/1752194/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884899] Re: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0
** Tags added: 201807-26342 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884899 Title: Kernel Oops - unable to handle kernel NULL pointer dereference; RIP is at 0010:set_root+0x27/0xc0 Status in linux package in Ubuntu: Confirmed Bug description: After login into the gnome session, the session freezes, either instantly or after a few seconds ( only mouse is working ). The Oops does not occur on every startup. After a few restarts, the kernel Oops does not occur anymore during the complete session. Dell Perfomance Checks ( including memory checks ) did not show any failures. BIOS is uptodate ( 1.16.2 for Dell Precision 5530 ). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: scsi 3876 F pulseaudio /dev/snd/controlC1: scsi 3876 F pulseaudio /dev/snd/controlC0: scsi 3876 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 09:00:05 2020 DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-xenial-amd64-osp1-20171027-1 EcryptfsInUse: Yes InstallationDate: Installed on 2019-01-10 (530 days ago) InstallationMedia: Ubuntu 16.04 "Xenial" - Build amd64 LIVE Binary 20171027-10:57 MachineType: Dell Inc. Precision 5530 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=2c719e60-4d36-4042-aa72-aa62403b19a1 ro acpi_osi=Linux-Dell-Video alx.enable_wol=1 mem_sleep_default=deep quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-05-04 (50 days ago) WifiSyslog: dmi.bios.date: 04/21/2020 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.16.2 dmi.board.name: 0N0DK2 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.16.2:bd04/21/2020:svnDellInc.:pnPrecision5530:pvr:rvnDellInc.:rn0N0DK2:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Precision dmi.product.name: Precision 5530 dmi.product.sku: 087D dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884899/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882717] Re: fanotify10 test case 16 failed on focal
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882717 Title: fanotify10 test case 16 failed on focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: This is a new test cases added recently: https://github.com/linux-test-project/ltp/commit/997d87d544042ded4b858377c95a90e1c12036b8 fanotify10.c:347: INFO: Test #16: ignore child exec events created on a specific mount point fanotify10.c:306: PASS: group 0 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 1 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 2 got event: mask 1020 pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Same here: Ubuntu 20.04 Asus ROG GL552V Intel Core i7-6700HQ nvidia GeForce GTX 960M / driver version: 435.21 Monitor shows Asus splashscreen properly (before os starts) Monitor stays black (but is detected by system) It seams to not be detected by graphics card (but not sure now) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] [NEW] Very slow boot with kernel 5.4.0-37-generic
Public bug reported: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Hardinfo report from System profiler and benchmarking." https://bugs.launchpad.net/bugs/1884910/+attachment/5386718/+files/hardinfo_report.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/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: New Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1882717] Re: fanotify10 test case 16 failed on focal
Affecting 5.0 kernel as well. ** Tags added: 5.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1882717 Title: fanotify10 test case 16 failed on focal Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: New Status in linux source package in Focal: New Bug description: This is a new test cases added recently: https://github.com/linux-test-project/ltp/commit/997d87d544042ded4b858377c95a90e1c12036b8 fanotify10.c:347: INFO: Test #16: ignore child exec events created on a specific mount point fanotify10.c:306: PASS: group 0 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 1 got event: mask 1020 pid=40813 fd=30 fanotify10.c:306: PASS: group 2 got event: mask 1020 pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 0 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 1 got event: mask 1020 (expected 1000) pid=40813 fd=30 fanotify10.c:296: FAIL: group 2 got event: mask 1020 (expected 1000) pid=40813 fd=30 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1882717/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] 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 1884910 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Re: Very slow boot with kernel 5.4.0-37-generic
apport information ** Tags added: apport-collected ** Description changed: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. - [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, - disabling MSI: last cmd=0x20bf8100 + [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu27.3 + Architecture: amd64 + AudioDevicesInUse: + USERPID ACCESS COMMAND + /dev/snd/controlC0: ianb 2420 F pulseaudio + CasperMD5CheckResult: skip + CurrentDesktop: LXQt + DistroRelease: Ubuntu 20.04 + InstallationDate: Installed on 2019-12-06 (200 days ago) + InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) + MachineType: Chillblast WAP PRO + Package: linux (not installed) + ProcFB: 0 i915drmfb + ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 + ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 + RelatedPackageVersions: + linux-restricted-modules-5.4.0-37-generic N/A + linux-backports-modules-5.4.0-37-generic N/A + linux-firmware1.187 + Tags: focal + Uname: Linux 5.4.0-37-generic x86_64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: adm cdrom dip lpadmin plugdev sudo + _MarkForUpload: True + dmi.bios.date: 08/15/2019 + dmi.bios.vendor: American Megatrends Inc. + dmi.bios.version: GB3V35 + dmi.board.asset.tag: Default string + dmi.board.name: GB3 + dmi.board.vendor: IP3 Tech + dmi.board.version: Default string + dmi.chassis.asset.tag: Default string + dmi.chassis.type: 35 + dmi.chassis.vendor: IP3 + dmi.chassis.version: Default string + dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: + dmi.product.family: Mini PC + dmi.product.name: WAP PRO + dmi.product.sku: CBFUSWAPPRO + dmi.product.version: Default string + dmi.sys.vendor: Chillblast ** Attachment added: "AlsaInfo.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386723/+files/AlsaInfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://lau
[Kernel-packages] [Bug 1884910] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386724/+files/CRDA.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Lspci-vt.txt
apport information ** Attachment added: "Lspci-vt.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386728/+files/Lspci-vt.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386731/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386727/+files/Lspci.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386736/+files/ProcModules.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386734/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386735/+files/ProcInterrupts.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386729/+files/Lsusb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386730/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386733/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386726/+files/IwConfig.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386738/+files/RfKill.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386737/+files/PulseList.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386725/+files/CurrentDmesg.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386732/+files/ProcCpuinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
@Stéphane, I have now followed your steps from commant #38 (was using the official ubuntu image before with cloud-init and that does a initrd-less boot first which is successful for me) but this does not show me the error you see either. And a break=top does work (with some complaints about tty1 which is expected due to the missing efi-fb). I double-checked the initramfs compression setting and that is lz4. This is rather weird. I will try on a different hw but that really should not be relevant. For double checking: which LXD version are you using? I am on the focal/stable/4.0 stream: lxd4.0.115682 4.0/stable/… canonical✓ - -- 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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 -
[Kernel-packages] [Bug 1884910] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386739/+files/UdevDb.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884910] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1884910/+attachment/5386740/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884910 Title: Very slow boot with kernel 5.4.0-37-generic Status in linux package in Ubuntu: Incomplete Bug description: Booting on Lubuntu 20.04LTS is very slow when using kernel 5.4.0-37-generic, but OK with 5.4.0-33-generic.Delay seems to be due to this or similar error messages which are repeated many times before timing out. [ 62.776599] snd_hda_intel :00:0e.0: No response from codec, disabling MSI: last cmd=0x20bf8100 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: ianb 2420 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: LXQt DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2019-12-06 (200 days ago) InstallationMedia: Lubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017.1) MachineType: Chillblast WAP PRO Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=cae501ec-3727-4d42-8fbb-d21cdb1dd5a5 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 Tags: focal Uname: Linux 5.4.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo _MarkForUpload: True dmi.bios.date: 08/15/2019 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GB3V35 dmi.board.asset.tag: Default string dmi.board.name: GB3 dmi.board.vendor: IP3 Tech dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: IP3 dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGB3V35:bd08/15/2019:svnChillblast:pnWAPPRO:pvrDefaultstring:rvnIP3Tech:rnGB3:rvrDefaultstring:cvnIP3:ct35:cvrDefaultstring: dmi.product.family: Mini PC dmi.product.name: WAP PRO dmi.product.sku: CBFUSWAPPRO dmi.product.version: Default string dmi.sys.vendor: Chillblast To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884910/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Hm, and maybe also relevant: what kind of pool is used? My setup was "lxd init --auto" which is a file based image backend. -- 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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98 0047, LDTR - IDTR - 3F2D8018 0FFF, TR - F
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Ok, so with the same software versions installed but on a different hw platform, I did at least once get this incomplete write error. The working box is an AMD/BIOS one and the non-working an Intel/EFI. Not sure why that has any impact. -- 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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 2501, R12 - 0004, R13 - 3E80F100 R14 - , R15 - DS - 0030, ES - 0030, FS - 0030 GS - 0030, SS - 0030 CR0 - 80010033, CR2 - , CR3 - 3FC01000 CR4 - 0668, CR8 - DR0 - , DR1 - , DR2 - DR3 - , DR6 - 0FF0, DR7 - 0400 GDTR - 3FBEEA98
[Kernel-packages] [Bug 1801743] Re: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10
I have the same issue. Unfortunately it's now Ubuntu 20.04 and kernel 5.4.0 and it still happens. My laptop is Lenovo Thinkpad T440p. First issue that was happening all the time was that the touchpad didn't work after waking from suspend. But it was better known issue with some fixes with the help of some scripts. This is harder as it's now happening always but only sometimes and I haven't figured out robust steps to reproduce this issue. It just happens sporadically but when it happens only hard reset helps. My laptop has also Intel CPU and nVidia graphics card so that's something that is common I suppose. If anything else is needed I could provide more information. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801743 Title: Suspend fails in Kubuntu 18.04 but works fine in Kubuntu 17.10 Status in linux package in Ubuntu: Confirmed Bug description: After upgrading to kubuntu 18.04 resuming from suspend fails in most cases on my laptop. When trying to resume the power LED is turned on, but the screen stays black and the system does not respond at all. Switching to another virtual terminal is not possible and closing the lid again does not show any effect. The hardware is a Dell Latitude e7440 with core i7 4600U and intel graphics only. The only way to change the status is a hard shut-down by long pressing the power button. The last message in kern.log is: PM: suspend entry (deep) The described problem is similar to bug #1774950. However, the latter is considered to be fixed with kernel 4.15.0-38 while my problem persists with this kernel. Output of 'sudo lspci -vnvn' is attached, the result of 'cat /proc/version_signature' is: Ubuntu 4.15.0-38.41-generic 4.15.18 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: graeser2116 F pulseaudio /dev/snd/controlC0: graeser2116 F pulseaudio CurrentDesktop: KDE DistributionChannelDescriptor: # This is a distribution channel descriptor # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-precise-amd64-20130203-1 DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes HibernationDevice: RESUME=none InstallationDate: Installed on 2014-03-20 (1690 days ago) InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50 MachineType: Dell Inc. Latitude E7440 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-38-generic root=UUID=25e09413-4977-401f-a034-0465b444518b ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-38.41-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-38-generic N/A linux-backports-modules-4.15.0-38-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-38-generic x86_64 UpgradeStatus: Upgraded to bionic on 2018-10-15 (20 days ago) UserGroups: adm cdrom dip docker lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 02/02/2015 dmi.bios.vendor: Dell Inc. dmi.bios.version: A14 dmi.board.name: 0WK2DM dmi.board.vendor: Dell Inc. dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvrA14:bd02/02/2015:svnDellInc.:pnLatitudeE7440:pvr01:rvnDellInc.:rn0WK2DM:rvr:cvnDellInc.:ct9:cvr: dmi.product.name: Latitude E7440 dmi.product.version: 01 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1801743/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
Thank you Bjorn, 1) do you suggest building my own kernel locally according to here https://wiki.ubuntu.com/Kernel/BuildYourOwnKernel or do you have any specific kernel to use (like from PPA ? 2) I will get AIDA info for you, meanwhile, I'm already having this output from hwinfo64 windows app (attached) - maybe it helps already (?) many thanks, really appreciate your 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/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 1867155] Re: P8 node modoc will reboot automatically when running the sru_misc test suite
This issue is striking us again with 5.3.0-60.54 on modoc. ** Tags added: sru-20200608 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1867155 Title: P8 node modoc will reboot automatically when running the sru_misc test suite Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Confirmed Bug description: Tested with 5 attempts, 4 hangs around the following test in ubuntu_kernel_selftests net sub-category: # selftests: net: reuseport_bpf_cpu First attempt: 23:21:32 DEBUG| [stdout] ok 2 selftests: net: reuseport_bpf_cpu 23:21:32 DEBUG| [stdout] # selftests: net: reuseport_bpf_numa 23:21:32 DEBUG| [stdout] # IPv4 UDP (hang here) Second attempt: 10:17:35 DEBUG| [stdout] ok 1 selftests: net: reuseport_bpf 10:17:35 DEBUG| [stdout] # selftests: net: reuseport_bpf_cpu 10:17:35 DEBUG| [stdout] # IPv4 UDP 10:17:35 DEBUG| [stdout] # send cpu 0, receive socket 0 (line skipped) 10:17:35 DEBUG| [stdout] # send cpu 159, receive socket 159 10:17:35 DEBUG| [stdout] # IPv6 TCP (hang here) Third attempt failed because of test timeout: 12:46:16 DEBUG| [stdout] # [FAIL] 12:46:16 DEBUG| [stdout] # 12:46:16 DEBUG| [stdout] # running psock_tpacket test 12:46:16 DEBUG| [stdout] # 13:14:13 INFO | Timer expired (1800 sec.), nuking pid 161853 Fourth attempt: 07:41:51 DEBUG| [stdout] # selftests: net: reuseport_bpf_cpu 07:41:51 DEBUG| [stdout] # IPv4 UDP 07:41:51 DEBUG| [stdout] # send cpu 0, receive socket 0 (lines skipped) 07:41:51 DEBUG| [stdout] # send cpu 159, receive socket 159 07:41:51 DEBUG| [stdout] # IPv6 UDP 07:41:51 DEBUG| [stdout] # send cpu 0, receive socket 0 07:41:51 DEBUG| [stdout] # send cpu 1, receive socket 1 (lines skipped) 07:41:51 DEBUG| [stdout] # send cpu 157, receive socket 157 07:41:51 DEBUG| [stdout] # send cpu 159, receive socket 159 07:41:51 DEBUG| [stdout] # IPv4 TCP (test hang here) Fifth attempt: 04:29:17 DEBUG| [stdout] ok 1 selftests: net: reuseport_bpf 04:29:17 DEBUG| [stdout] # selftests: net: reuseport_bpf_cpu 04:29:17 DEBUG| [stdout] # IPv4 UDP 04:29:17 DEBUG| [stdout] # send cpu 0, receive socket 0 (lines skipped) 04:29:17 DEBUG| [stdout] # send cpu 159, receive socket 159 04:29:17 DEBUG| [stdout] # IPv6 UDP 04:29:17 DEBUG| [stdout] # send cpu 0, receive socket 0 (lines skipped) 04:29:17 DEBUG| [stdout] # send cpu 159, receive socket 159 04:29:17 DEBUG| [stdout] # IPv4 TCP 04:29:17 DEBUG| [stdout] # send cpu 0, receive socket 0 (lines skipped) 04:29:17 DEBUG| [stdout] # send cpu 15, receive socket 15 (test hang here) I tried to run tests in this sru-misc suite in the following order: 'hwclock', 'ubuntu_bpf', 'ubuntu_bpf_jit', 'ubuntu_kernel_selftests', 'ubuntu_lxc', 'ubuntu_seccomp', 'ubuntu_unionmount_ovlfs', 'ubuntu_cts_kernel', 'ubuntu_kvm_unit_tests', One by one on this node, but I can't reproduce this issue. I tried to watch dmesg when this happens, but there is no information there, the system will be reboot automatically silently. This is what you can see from syslog after reboot: Mar 12 04:27:39 modoc kernel: [ 536.668305] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.684547] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.700907] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.717246] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.719288] page:c00c00c4f000 refcount:1 mapcount:0 mapping:c00f8cfe0fd1 index:0x7611c3e Mar 12 04:27:39 modoc kernel: [ 536.719289] anon Mar 12 04:27:39 modoc kernel: [ 536.719291] flags: 0x3800080024(uptodate|active|swapbacked) Mar 12 04:27:39 modoc kernel: [ 536.719294] raw: 003800080024 5deadbeef100 5deadbeef122 c00f8cfe0fd1 Mar 12 04:27:39 modoc kernel: [ 536.719295] raw: 07611c3e 0001 c00fcfd1c000 Mar 12 04:27:39 modoc kernel: [ 536.719296] page dumped because: unmovable page Mar 12 04:27:39 modoc kernel: [ 536.719296] page->mem_cgroup:c00fcfd1c000 Mar 12 04:27:39 modoc kernel: [ 536.735465] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.751848] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.768210] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.784450] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.800756] Injecting error (-12) to MEM_GOING_OFFLINE Mar 12 04:27:39 modoc kernel: [ 536.817006]
[Kernel-packages] [Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
attaching hwinfo log... ** Attachment added: "win_hwinfo64.log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+attachment/5386772/+files/win_hwinfo64.log.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/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 1884288] Re: [LapBook Pro] Touchpad sometimes does not work when machine is restarted
Unfortunately event 3 is not the touchpad, nor is 4, see below: EVENT 3: Input device name: "Intel HID events" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 69 (KEY_NUMLOCK) Event code 102 (KEY_HOME) Event code 104 (KEY_PAGEUP) Event code 107 (KEY_END) Event code 109 (KEY_PAGEDOWN) Event code 113 (KEY_MUTE) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) Event code 142 (KEY_SLEEP) Event code 164 (KEY_PLAYPAUSE) Event code 166 (KEY_STOPCD) Event code 224 (KEY_BRIGHTNESSDOWN) Event code 225 (KEY_BRIGHTNESSUP) Event code 240 (KEY_UNKNOWN) Event code 247 (KEY_RFKILL) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) EVENT 4: Input device name: "Intel HID 5 button array" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 114 (KEY_VOLUMEDOWN) Event code 115 (KEY_VOLUMEUP) Event code 116 (KEY_POWER) Event code 125 (KEY_LEFTMETA) Event code 240 (KEY_UNKNOWN) Event code 561 (?) Event type 4 (EV_MSC) Event code 4 (MSC_SCAN) The rest do not appear to relate to the 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/1884288 Title: [LapBook Pro] Touchpad sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 sometimes does not work when machine is restarted
I restarted the laptop again to see if it helps and it is back working. I am not sure if this helps but when I move the touchpad around and pressing the left and right during the startup screen it seems it may help, I am not sure if this is complete nonsense or not. It is now listed in the evtest: No device specified, trying to scan all of /dev/input/event* Available devices: /dev/input/event0: Lid Switch /dev/input/event1: Power Button /dev/input/event2: AT Translated Set 2 keyboard /dev/input/event3: HTIX5288:00 0911:5288 UNKNOWN /dev/input/event4: HTIX5288:00 0911:5288 Touchpad /dev/input/event5: HTIX5288:00 0911:5288 UNKNOWN /dev/input/event6: Intel HID events /dev/input/event7: Intel HID 5 button array /dev/input/event8: USB 2.0 Camera: USB Camera /dev/input/event9: Video Bus /dev/input/event10: HDA Intel PCH Mic /dev/input/event11: HDA Intel PCH Headphone /dev/input/event12: HDA Intel PCH HDMI/DP,pcm=3 /dev/input/event13: HDA Intel PCH HDMI/DP,pcm=7 /dev/input/event14: HDA Intel PCH HDMI/DP,pcm=8 /dev/input/event15: HDA Intel PCH HDMI/DP,pcm=9 /dev/input/event16: HDA Intel PCH HDMI/DP,pcm=10 I can confirm event 4 is indeed the touchpad as lots of extra information appears when event 4 is investigated when touchpad is in use. -- You 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 sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 sometimes does not work when machine is restarted
I restarted laptop twice without touching touchpad until I get user login screen and worked fine. However, on another reboot, I touched the touchpad several times during the startup screen and it is not working again. I am not sure if this helps in the testing of this. Anyway, it is back to the non-working state, that is not to say that it will start working again with yet another reboot. -- You 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 sometimes does not work when machine is restarted Status in linux package in Ubuntu: Incomplete 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884288/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878670] Re: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2)
Dell and Ubuntu have certified a few days ago the XPS 2020 9300 for 20.04 I guess I am going to move from 18.04 to 20.04 in a few days, a week at most I hope this problem will be fixed there :/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878670 Title: Reproduceable i915 gpu hang Intel Iris Plus Graphics (Ice Lake 8x8 GT2) Status in OEM Priority Project: Incomplete Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Bug description: The system freezes frequently then logs out. If happens at apparently random times, and using no particular app. Extract of syslog is attached. Requested info is below: 1) release Ubuntu 18.04.2 LTS (beaver-osp1-melisa X30) 2) package version gnome-session: Installeret: (ingen) Kandidat:3.28.1-0ubuntu3 Versionstabel: 3.28.1-0ubuntu3 500 500 http://dk.archive.ubuntu.com/ubuntu bionic-updates/universe amd64 Packages 3.28.1-0ubuntu2 500 500 http://dk.archive.ubuntu.com/ubuntu bionic/universe amd64 Packages 3) Gnome shouldn't crash 4) Gnome crashed To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1878670/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1881699] Re: No analog output
No improvements with latest version in groovy (1:13.99.1-1ubuntu7) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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 3) would be helpful to try the kernel boot parameter dyndbg=... provided in my current kernel (5.4.0-37-generic)? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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 1447664] Re: 14e4:1687 broadcom tg3 network driver disconnects under high load
I did not apply the patch in #13, but I did try disabling highdma with ethtool (essentially what the patch makes permanent) and that had no effect for me (at least not on the kernel I was using at the time). I did try the patch in #40 and that had no effect for me either. The only thing I've found that keeps my Broadcom 5762 alive without disconnecting is the kernel parameter "iommu=pt". I'm just finally grateful to have found a workaround so I can keep this server wired and not have to rely on its wireless only. I can't help but think we are chasing a moving target across so many kernel versions since this issue was first reported. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1447664 Title: 14e4:1687 broadcom tg3 network driver disconnects under high load Status in linux package in Ubuntu: Fix Released Bug description: The tg3 broadcom network driver that binds with chipset 5762 goes offline and unable to recover (even with tg3 watchdog timeout) when network transmit is under high load. Call trace: https://launchpadlibrarian.net/204185480/dmesg When this happens, only a reboot would be able to fix it. Sometimes, however, bringing the interface offline and online (via ifconfig) would recover networking. I've also tested with the latest tg3 driver (dec 2014 version) and networking is still problematic. I have also disabled TSO, GSO etc... with ethtool and the bug still surfaces. This bug may be related to the integrated Firmware. Here is the procedure to replicate the issue because it is hard to replicate it under moderate network load. 1. Bootup a machine with a broadcom 5762 NIC (ie. HP DeskElite 705) using a Ubuntu/Kubunu Live CD 14.04-15.04. 2. from another machine: start 5 sessions, repetitively copy (scp with public key authentication) a 70 meg file back and forth to the tg3 machine in each session. (not sure if this is necessary) 3. create a 1GB file on the tg3 machine, with something like dd if=/dev/urandom of=/my/test/file bs=1024 count=$((1024*1000)) 4. from another machine: repetitively scp copy that 1GB file from the tg3 machine. This can be done with something like: while [ 0 ]; do scp -i /my/scp/private.key u...@ip.of.tg3:/my/test/file /tmp done; Networking will mostly goes offline in about 10-30 minutes. WORKAROUND: Add udev rule to make the changes permanent in /etc/udev/rules.d/80-tg3-fix.rules : ACTION=="add", SUBSYSTEM=="net", ATTRS{vendor}=="0x14e4", ATTRS{device}=="0x1687", RUN+="/sbin/ethtool -K %k highdma off" ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: linux-image-3.19.0-15-generic 3.19.0-15.15 ProcVersionSignature: Ubuntu 3.19.0-15.15-generic 3.19.3 Uname: Linux 3.19.0-15-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: kubuntu3748 F pulseaudio /dev/snd/controlC0: kubuntu3748 F pulseaudio CasperVersion: 1.360 Date: Thu Apr 23 11:16:24 2015 IwConfig: eth0 no wireless extensions. lono wireless extensions. LiveMediaBuild: Kubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422) MachineType: Hewlett-Packard HP EliteDesk 705 G1 MT ProcEnviron: LANGUAGE= TERM=xterm PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz.efi file=/cdrom/preseed/hostname.seed boot=casper maybe-ubiquity quiet splash --- PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-3.19.0-15-generic N/A linux-backports-modules-3.19.0-15-generic N/A linux-firmware 1.143 RfKill: SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/22/2014 dmi.bios.vendor: Hewlett-Packard dmi.bios.version: L06 v02.15 dmi.board.asset.tag: 2UA5041TG4 dmi.board.name: 2215 dmi.board.vendor: Hewlett-Packard dmi.chassis.asset.tag: 2UA5041TG4 dmi.chassis.type: 6 dmi.chassis.vendor: Hewlett-Packard dmi.modalias: dmi:bvnHewlett-Packard:bvrL06v02.15:bd10/22/2014:svnHewlett-Packard:pnHPEliteDesk705G1MT:pvr:rvnHewlett-Packard:rn2215:rvr:cvnHewlett-Packard:ct6:cvr: dmi.product.name: HP EliteDesk 705 G1 MT dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1447664/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.lau
[Kernel-packages] [Bug 1884232] Re: touchpad doesn't work at all on ACER Spin 5
ad 2) here you have AIDA64 ACPI report ** Attachment added: "aida64_ACPIreport.log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+attachment/5386798/+files/aida64_ACPIreport.log.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/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 1884232] Re: touchpad doesn't work at all on ACER Spin 5
and here Device Resources Report ** Attachment added: "aida64_DeviceResources_report.log.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884232/+attachment/5386799/+files/aida64_DeviceResources_report.log.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/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 1884232] Re: touchpad doesn't work at all on ACER Spin 5
1) Sorry, I don't have a PPA or similar kernel image for you to try. 2) I expected that Windows would move 00:1f.5 BAR 0 to be inside the windows reported by the PCI0 _CRS, but the AIDA64 report shows otherwise: B00 D1F F05: Intel Ice Point-LP PCH - SPI (Flash) Controller Offset 000: 86 80 A4 34 06 04 00 00 30 00 80 0C 00 00 00 00 Offset 010: 00 00 01 FE 00 00 00 00 00 00 00 00 00 00 00 00 BAR 0 is at offset 0x10, and it still contains the value BIOS put there (0xfe01). I don't know why Linux couldn't find space for 00:1f.5 BAR 0. Tracing the resource assignment code with 'dyndbg="file drivers/pci/* +p"' and possibly some new trace messages might give a clue. When Linux fails to assign space, it tries to revert to the BIOS assignment ("BAR 0: trying firmware assignment [mem 0xfe01-0xfe010fff]"). Apparently we declined to use that BIOS assignment because it "conflicts with Reserved [mem 0xfc80-0xfe7f]". Perhaps Linux should ignore that conflict. That "Reserved [mem 0xfc80-0xfe7f]" comes from the E820 map, and the Linux handling of that map is somewhat haphazard. -- You 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 1881699] Re: No analog output
@Hui, could you check if that's a known issue? J-B mentioned it was an issue Carbon X1 7g users are talking about -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881699 Title: No analog output Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: After a fresh boot and login, there is no analog output. Only HDMI and bluetooth are available. It becomes available when I kill pulseaudio with 'pulseaudio -k' but the sound indicator only shows 'dummy' output and I cannot control the output from the sound settings or the sound indicator. ProblemType: Bug DistroRelease: Ubuntu 20.10 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 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: j-lallement 184080 F pulseaudio /dev/snd/controlC1: j-lallement 184080 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Jun 2 06:32:09 2020 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu36 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: j-lallement 3669 F pulseaudio /dev/snd/controlC0: j-lallement 3669 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.10 InstallationDate: Installed on 2020-05-31 (1 days ago) InstallationMedia: Ubuntu 20.10 "Groovy Gorilla" - Alpha amd64 (20200527) MachineType: Intel(R) Client Systems NUC10i7FNH NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: pulseaudio 1:13.99.1-1ubuntu3 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu_huyn9u@/vmlinuz-5.4.0-26-generic root=ZFS=rpool/ROOT/ubuntu_huyn9u ro snd-intel-dspcfg.dsp_driver=1 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 RelatedPackageVersions: linux-restricted-modules-5.4.0-26-generic N/A linux-backports-modules-5.4.0-26-generic N/A linux-firmware1.187 Tags: groovy Uname: Linux 5.4.0-26-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/21/2019 dmi.bios.vendor: Intel Corp. dmi.bios.version: FNCML357.0032.2019.1021.1624 dmi.board.asset.tag: Default string dmi.board.name: NUC10i7FNB dmi.board.vendor: Intel Corporation dmi.board.version: K61360-302 dmi.chassis.asset.tag: Default string dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrFNCML357.0032.2019.1021.1624:bd10/21/2019:svnIntel(R)ClientSystems:pnNUC10i7FNH:pvrK61081-302:rvnIntelCorporation:rnNUC10i7FNB:rvrK61360-302:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: FN dmi.product.name: NUC10i7FNH dmi.product.sku: BXNUC10i7FNH dmi.product.version: K61081-302 dmi.sys.vendor: Intel(R) Client Systems To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1881699/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884546] Re: Lenovo T440s hangs on the dock when unsleeping the monitor
This kernel also shows continuous rendering artifact on the native LCD screen, such as the windows underneath the current active window appear as flickering ghosts. No problems on the previous released kernel. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884546 Title: Lenovo T440s hangs on the dock when unsleeping the monitor Status in linux package in Ubuntu: Confirmed Bug description: This issue has been a persistent but infrequent problem for many years with the T440s. It only occurs when the laptop is docked. I have reported this bug several times. However, with the current kernel release, 5.4.0-37, this occurs at least once a day. The kern.log lines are: Jun 21 16:44:23 magpie kernel: [13992.853712] [drm:intel_set_cpu_fifo_underrun_r eporting [i915]] *ERROR* uncleared fifo underrun on pipe B Jun 21 16:44:23 magpie kernel: [13992.853749] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun Jun 21 17:17:00 magpie kernel: [15950.119066] [drm:intel_set_cpu_fifo_underrun_reporting [i915]] *ERROR* uncleared fifo underrun on pipe B Jun 21 17:17:00 magpie kernel: [15950.119101] [drm:intel_cpu_fifo_underrun_irq_handler [i915]] *ERROR* CPU pipe B FIFO underrun ^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@^@ followed by a dead hang. The pattern is the same each time. My current work around is to use the previous version of the released kernel, 5.4.0-33, which does not have this issue. I'm hoping someone has an idea. It's very frustrating. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: weinberg 3505 F pulseaudio /dev/snd/controlC1: weinberg 3505 F pulseaudio /dev/snd/controlC0: weinberg 3505 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Mon Jun 22 10:02:42 2020 EcryptfsInUse: Yes HibernationDevice: RESUME=UUID=8d33a538-4ec4-418d-b277-be1a9a1c1113 InstallationDate: Installed on 2018-03-12 (832 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180114) MachineType: LENOVO 20ARA0S100 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=b6683bc1-7dd5-4afd-8e70-f69253403b71 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-04-24 (58 days ago) dmi.bios.date: 03/19/2014 dmi.bios.vendor: LENOVO dmi.bios.version: GJET74WW (2.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20ARA0S100 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Not Available dmi.modalias: dmi:bvnLENOVO:bvrGJET74WW(2.24):bd03/19/2014:svnLENOVO:pn20ARA0S100:pvrThinkPadT440s:rvnLENOVO:rn20ARA0S100:rvrNotDefined:cvnLENOVO:ct10:cvrNotAvailable: dmi.product.family: ThinkPad T440s dmi.product.name: 20ARA0S100 dmi.product.sku: LENOVO_MT_20AR_BU_Think_FM_ThinkPad T440s dmi.product.version: ThinkPad T440s dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884635] Re: lxc 1:4.0.2-0ubuntu1 ADT test failure with linux-5.8 5.8.0-1.2
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884635 Title: lxc 1:4.0.2-0ubuntu1 ADT test failure with linux-5.8 5.8.0-1.2 Status in linux package in Ubuntu: Incomplete Status in lxc package in Ubuntu: Invalid Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/l/lxc/20200619_210334_814e1@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/l/lxc/20200619_213805_39c53@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/l/lxc/20200619_210431_b275f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/l/lxc/20200619_210417_54a16@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884635] 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 1884635 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884635 Title: lxc 1:4.0.2-0ubuntu1 ADT test failure with linux-5.8 5.8.0-1.2 Status in linux package in Ubuntu: Incomplete Status in lxc package in Ubuntu: Invalid Bug description: Testing failed on: amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/amd64/l/lxc/20200619_210334_814e1@/log.gz arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/arm64/l/lxc/20200619_213805_39c53@/log.gz ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/ppc64el/l/lxc/20200619_210431_b275f@/log.gz s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-canonical-kernel-team-bootstrap/groovy/s390x/l/lxc/20200619_210417_54a16@/log.gz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884635/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884981] [NEW] The touchpad soesn't work at all
Public bug reported: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description:Ubuntu 20.04 LTS Release:20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal ** Attachment added: "The devices" https://bugs.launchpad.net/bugs/1884981/+attachment/5386818/+files/devices -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: New Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884981] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884981 Title: The touchpad soesn't work at all Status in linux package in Ubuntu: Confirmed Bug description: I had Windows 10 on the device and the touch pad was working perfectly, but when I set up Ubuntu 20.04 with Windows, in both OCs the touch pad stopped working at all. It doesn't appear /proc/bus/input/devices file. $ lsb_release -rd Description: Ubuntu 20.04 LTS Release: 20.04 ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: danila 1249 F pulseaudio /dev/snd/controlC0: danila 1249 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:00:28 2020 InstallationDate: Installed on 2020-06-24 (0 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81YM ProcFB: 0 EFI VGA ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=c7036847-2fbc-429d-b113-30e6cc776647 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/25/2020 dmi.bios.vendor: LENOVO dmi.bios.version: DTCN18WW(V1.04) dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: No DPK dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 5 14ARE05 dmi.modalias: dmi:bvnLENOVO:bvrDTCN18WW(V1.04):bd03/25/2020:svnLENOVO:pn81YM:pvrIdeaPad514ARE05:rvnLENOVO:rnLNVNB161216:rvrNoDPK:cvnLENOVO:ct10:cvrIdeaPad514ARE05: dmi.product.family: IdeaPad 5 14ARE05 dmi.product.name: 81YM dmi.product.sku: LENOVO_MT_81YM_BU_idea_FM_IdeaPad 5 14ARE05 dmi.product.version: IdeaPad 5 14ARE05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884981/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873809] Re: Make linux-kvm bootable in LXD VMs
Alright, at least partially understanding things now. So it looks like "Decoding failed" happens generally on some platforms (and I do not understand still why this is). The difference between the generic kernel and the kvm kernel is that the kvm kernel has a built-in BLK_DEV_RAM of size (4096) whereas the generic kernel uses a module for that. It looks like only if BLK_DEV_RAM=y is set, the code which populates the initial rootfs does try to flush and refill the ramdisk device. Otherwise the partially expanded rootfs is retained. And I guess the ramdisk size is set to small so we get the incomplete write there. I guess the solution (which does not solve the decode failure) is to change the kvm kernel config to BLK_DEV_RAM=m CONFIG_BLK_DEV_RAM_SIZE=65536 -- 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/1873809 Title: Make linux-kvm bootable in LXD VMs Status in cloud-images: Invalid Status in linux-kvm package in Ubuntu: Triaged Status in linux-kvm source package in Focal: Fix Committed Bug description: The `disk-kvm.img` images which are to be preferred when run under virtualization, currently completely fail to boot under UEFI. A workaround was put in place such that LXD instead will pull generic- based images until this is resolved, this however does come with a much longer boot time (as the kernel panics, reboots and then boots) and also reduced functionality from cloud-init, so we'd still like this fixed in the near future. To get things behaving, it looks like we need the following config options to be enable in linux-kvm: - CONFIG_EFI_STUB - CONFIG_VSOCKETS - CONFIG_VIRTIO_VSOCKETS - CONFIG_VIRTIO_VSOCKETS_COMMON == Rationale == We'd like to be able to use the linux-kvm based images for LXD, those will directly boot without needing the panic+reboot behavior of generic images and will be much lighter in general. We also need the LXD agent to work, which requires functional virtio vsock. == Test case == - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-lxd.tar.xz - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - lxc image import focal-server-cloudimg-amd64-lxd.tar.xz focal-server-cloudimg-amd64-disk-kvm.img --alias bug1873809 - lxc launch bug1873809 v1 - lxc console v1 - - - lxc exec v1 bash To validate a new kernel, you'll need to manually repack the .img file and install the new kernel in there. == Regression potential == I don't know who else is using those kvm images right now, but those changes will cause a change to the kernel binary such that it contains the EFI stub bits + a signature. This could cause some (horribly broken) systems to no longer be able to boot that kernel. Though considering that such a setup is common to our other kernels, this seems unlikely. Also, this will be introducing virtio vsock support which again, could maybe confused some horribly broken systems? In either case, the kernel conveniently is the only package which ships multiple versions concurently, so rebooting on the previous kernel is always an option, mitigating some of the risks. -- Details from original report -- User report on the LXD side: https://github.com/lxc/lxd/issues/7224 I've reproduced this issue with: - wget http://cloud-images.ubuntu.com/focal/current/focal-server-cloudimg-amd64-disk-kvm.img - qemu-system-x86_64 -bios /usr/share/ovmf/OVMF.fd -hda focal-server-cloudimg-amd64-disk-kvm.img -m 1G On the graphical console, you'll see EDK2 load (TianoCore) followed by basic boot messages and then a message from grub (error: can't find command `hwmatch`). Those also appear on successful boots of other images so I don't think there's anything concerning that. However it'll hang indefinitely and eat up all your CPU. Switching to the text console view (serial0), you'll see the same issue as that LXD report: BdsDxe: failed to load Boot0001 "UEFI QEMU DVD-ROM QM3 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Secondary,Master,0x0): Not Found BdsDxe: loading Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) BdsDxe: starting Boot0002 "UEFI QEMU HARDDISK QM1 " from PciRoot(0x0)/Pci(0x1,0x1)/Ata(Primary,Master,0x0) error: can't find command `hwmatch'. e X64 Exception Type - 0D(#GP - General Protection) CPU Apic ID - ExceptionData - RIP - 3FF2DA12, CS - 0038, RFLAGS - 00200202 RAX - AFAFAFAFAFAFAFAF, RCX - 3E80F108, RDX - AFAFAFAFAFAFAFAF RBX - 0398, RSP - 3FF1C638, RBP - 3FF34360 RSI - 3FF343B8, RDI - 1000 R8 - 3E80F108, R9 - 3E815B98, R10 - 0065 R11 - 00
[Kernel-packages] [Bug 1884997] [NEW] no touchpad detected, not working at all
Public bug reported: hello, i bought a new pc and installed ubuntu 20.04 and windows 10 on it. on ubuntu os my touchpad doesn't work at all, since installation process but it does on windows. the pc is a lenovo pc and one of the latest released one. when i plug in a usb mouse the mouse works fine but the touchpad still don't. it even doesn't show the touchpad when i type in (1) "cat /proc/bus/input/devices". only the usb mouse twice. i tryed a lot and don't know how to help myself any further. i attached a file "devices" where printed my output of (1). thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabian 1032 F pulseaudio /dev/snd/pcmC0D0p: fabian 1032 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:21:17 2020 InstallationDate: Installed on 2020-06-17 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a65a602e-ae73-4354-94f9-2f99e2bff055 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 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/1884997 Title: no touchpad detected, not working at all Status in linux package in Ubuntu: New Bug description: hello, i bought a new pc and installed ubuntu 20.04 and windows 10 on it. on ubuntu os my touchpad doesn't work at all, since installation process but it does on windows. the pc is a lenovo pc and one of the latest released one. when i plug in a usb mouse the mouse works fine but the touchpad still don't. it even doesn't show the touchpad when i type in (1) "cat /proc/bus/input/devices". only the usb mouse twice. i tryed a lot and don't know how to help myself any further. i attached a file "devices" where printed my output of (1). thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabian 1032 F pulseaudio /dev/snd/pcmC0D0p: fabian 1032 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:21:17 2020 InstallationDate: Installed on 2020-06-17 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a65a602e-ae73-4354-94f9-2f99e2bff055 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 d
[Kernel-packages] [Bug 1871721] Re: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop)
Hi slovic. If you see the nvidia-settings you probably can see the second monitor is detected by the Nvidia card. I think this is a problem of Intel, 'cause the second monitor's connected via HDMI, which is connected to Intel GPU. Please click on "this bug affects me too" so we can make see it to more people. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-440 in Ubuntu. https://bugs.launchpad.net/bugs/1871721 Title: Second Monitor on HDMI blank screen with Nvidia & Ubuntu 20.04? (ASUS Laptop) Status in kernel-package package in Ubuntu: Confirmed Status in mesa package in Ubuntu: Confirmed Status in mesa-utils package in Ubuntu: Confirmed Status in nouveau-firmware package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-440 package in Ubuntu: Confirmed Status in xserver-xorg-video-intel package in Ubuntu: Confirmed Bug description: I installed Ubuntu 20.04 on my ASUS laptop with Intel+Nvidia with propietary drivers of Nvidia (I have 440.64 rn) and I connected a second monitor to use it, but I saw that I cannot use it, I just see a blank screen. I tried with a TV of my room and same. The funny part is when I start the laptop to work, I can see the logo of my BIOS and the ASUS logo in the second monitor, even the grub, but after that I can't see nothing. When I reduce the resolution of the second monitor (800x600) then works, but even with that sometimes blinks to black again. On W10 for example it works perfectly, so I deduce it's not 'cause my HDMI. I tried with nouveau drivers and I have the same results btw. Laptop Asus with: Graphic card Nvidia GTX960M Processor Intel i5 6300 I tried with Nvidia Prime to Nvidia, Intel and On-demand. None of them works. All of them with Xorg. I have this with xrandr: Screen 0: minimum 8 x 8, current 2720 x 1080, maximum 16384 x 16384 eDP-1-1 connected primary 1920x1080+0+0 (normal left inverted right x axis y axis) 344mm x 193mm 1920x1080 60.00*+ 59.9759.9659.93 1680x1050 59.9559.88 1600x1024 60.17 1400x1050 59.98 1600x900 59.9959.9459.9559.82 1280x1024 60.02 1440x900 59.89 1400x900 59.9659.88 1280x960 60.00 1440x810 60.0059.97 1368x768 59.8859.85 1360x768 59.8059.96 1280x800 59.9959.9759.8159.91 1152x864 60.00 1280x720 60.0059.9959.8659.74 1024x768 60.0460.00 960x720 60.00 928x696 60.05 896x672 60.01 1024x576 59.9559.9659.9059.82 960x600 59.9360.00 960x540 59.9659.9959.6359.82 800x600 60.0060.3256.25 840x525 60.0159.88 864x486 59.9259.57 800x512 60.17 700x525 59.98 800x450 59.9559.82 640x512 60.02 720x450 59.89 700x450 59.9659.88 640x480 60.0059.94 720x405 59.5158.99 684x384 59.8859.85 680x384 59.8059.96 640x400 59.8859.98 576x432 60.06 640x360 59.8659.8359.8459.32 512x384 60.00 512x288 60.0059.92 480x270 59.6359.82 400x300 60.3256.34 432x243 59.9259.57 320x240 60.05 360x202 59.5159.13 320x180 59.8459.32 DP-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-1 disconnected (normal left inverted right x axis y axis) HDMI-1-2 connected 800x600+1920+0 (normal left inverted right x axis y axis) 1600mm x 900mm 1920x1080 60.00 + 50.0059.9430.0025.0024.0029.97 23.98 1920x1080i60.0050.0059.94 1280x1024 60.02 1360x768 60.02 1152x864 59.97 1280x720 59.8160.0050.0059.94 1024x768 60.00 800x600 60.32* 720x576 50.00 720x576i 50.00 720x480 60.0059.94 640x480 60.0059.94 720x400 70.08 DP-1-2 disconnected (normal left inverted right x axis y axis) HDMI-1-3 disconnected (normal left inverted right x axis y axis) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kernel-package/+bug/1871721/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884997] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884997 Title: no touchpad detected, not working at all Status in linux package in Ubuntu: Confirmed Bug description: hello, i bought a new pc and installed ubuntu 20.04 and windows 10 on it. on ubuntu os my touchpad doesn't work at all, since installation process but it does on windows. the pc is a lenovo pc and one of the latest released one. when i plug in a usb mouse the mouse works fine but the touchpad still don't. it even doesn't show the touchpad when i type in (1) "cat /proc/bus/input/devices". only the usb mouse twice. i tryed a lot and don't know how to help myself any further. i attached a file "devices" where printed my output of (1). thanks for any help. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: fabian 1032 F pulseaudio /dev/snd/pcmC0D0p: fabian 1032 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 18:21:17 2020 InstallationDate: Installed on 2020-06-17 (6 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) MachineType: LENOVO 81WE ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=a65a602e-ae73-4354-94f9-2f99e2bff055 ro i8042.reset quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 03/06/2020 dmi.bios.vendor: LENOVO dmi.bios.version: EMCN13WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40700 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: IdeaPad 3 15IIL05 dmi.modalias: dmi:bvnLENOVO:bvrEMCN13WW:bd03/06/2020:svnLENOVO:pn81WE:pvrIdeaPad315IIL05:rvnLENOVO:rnLNVNB161216:rvrSDK0J40700WIN:cvnLENOVO:ct10:cvrIdeaPad315IIL05: dmi.product.family: IdeaPad 3 15IIL05 dmi.product.name: 81WE dmi.product.sku: LENOVO_MT_81WE_BU_idea_FM_IdeaPad 3 15IIL05 dmi.product.version: IdeaPad 3 15IIL05 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884281] Re: UC20 images do not use predictable interface names on RPi4
UC20 only uses predictable names. It is intentional to use stable names. There is nothing in the gadget about it. But rather kernel drivers, dtb, udev. eth0 name is a bug. And it means udev failed to establish a predictable name for it. I think we either need to add an additional policy file for it, to at least use mac based name and/or work with kernel & upstream to positively identify it. ** Also affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Package changed: linux-raspi2 (Ubuntu) => linux-raspi (Ubuntu) ** Also affects: systemd (Ubuntu) Importance: Undecided Status: New -- 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/1884281 Title: UC20 images do not use predictable interface names on RPi4 Status in snapd: Triaged Status in linux-raspi package in Ubuntu: New Status in systemd package in Ubuntu: New Bug description: Image tested: http://cdimage.ubuntu.com/ubuntu-core/20/dangerous- beta/pending/ubuntu-core-20-arm64+raspi.img.xz Boot the image and check the naming of the ethernet interfaces. On most devices (amd64, rpi3 etc) systemd predicatable interface naming is applied e.g. enxb827eb7d1eee. However on specifically RPi4 devices traditional naming is used e.g. eth0, eth1. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1884281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1878377] Re: USB keyboard doesn't work with rpi3 (armhf)
** No longer affects: pi2-kernel-snap -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi in Ubuntu. https://bugs.launchpad.net/bugs/1878377 Title: USB keyboard doesn't work with rpi3 (armhf) Status in snapd: Invalid Status in linux-raspi package in Ubuntu: Confirmed Status in linux-raspi source package in Focal: Confirmed Bug description: Testing armhf image (ubuntu-core-20-armhf+raspi.img.xz) which download from http://cdimage.ubuntu.com/ubuntu-core/20/beta/20200512.3/ on Raspberry pi 3B After booting into system, the screen shows "Press enter to configure", press enter key on USB keyboard no respond. Try to connect USB keyboard via USB hub also doesn't work. To manage notifications about this bug go to: https://bugs.launchpad.net/snapd/+bug/1878377/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884900] [NEW] Touchpad not working
You have been subscribed to a public bug: Dear Sir, I have updated ubuntu 18.04 to 20.04 in the last 4 days. My laptop's touchpad worked well in the last system, but when I have updated it to 20.04 then touchpad not working, when I started my laptop. I have use a mouse. When I have start my laptop with connected mouse then touchpad not work. but, when I have started a laptop without connected with mouse then touchpad worked. Solve this issue properly. Thank you... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spshubham 1767 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 12:53:16 2020 HibernationDevice: RESUME=UUID=473a994d-cd87-4373-94ae-e2ff8edce101 InstallationDate: Installed on 2020-06-18 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=13763414-9331-414c-b5ad-ef7d3fa37ff2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-20 (3 days ago) dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron3521:pvrA16:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A16 dmi.sys.vendor: Dell Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug focal -- Touchpad not working https://bugs.launchpad.net/bugs/1884900 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883008] Re: Displaylink USB3 HDMI Adapter does not resume after suspending
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Canonical Desktop Team (canonical-desktop-team) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883008 Title: Displaylink USB3 HDMI Adapter does not resume after suspending Status in linux package in Ubuntu: Confirmed Bug description: Hi I recently updated to Ubuntu 20.04 and my Display Link USB adapter worked finw at first. Recently it does not resume operation after suspending the system: Plugging Adapter into USB Port: [380431.001721] usb 3-10: new high-speed USB device number 35 using xhci_hcd [380431.026448] usb 3-10: New USB device found, idVendor=17e9, idProduct=4301, bcdDevice=35.81 [380431.026450] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [380431.026451] usb 3-10: Product: USB3.0 UHD HDMI Adapter [380431.026452] usb 3-10: Manufacturer: DisplayLink [380431.026453] usb 3-10: SerialNumber: 000100110005089 [380431.031513] usb 3-10: Warning! Unlikely big volume range (=511), cval->res is probably wrong. [380431.031515] usb 3-10: [13] FU [DisplayLink Audio Playback Volume] ch = 2, val = -8176/0/16 [380431.534305] evdi: [D] evdi_painter_connect:644 (dev=-1) Process is trying to connect [380431.534307] evdi: [I] Task 290879 (DesktopManagerE) of process 290871 (DisplayLinkMana) [380431.534310] evdi: [D] evdi_painter_connect:694 (dev=1) Connected with 7f108832 [380431.534313] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629174] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629177] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid [380431.629361] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629362] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid [380432.193645] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380432.193654] evdi: [D] evdi_painter_mode_changed_notify:622 (dev=1) Notifying mode changed: 2560x1440@60; bpp 32; [380432.193655] evdi: [D] evdi_log_pixel_format:586 pixel format XR24 little-endian (0x34325258) [380432.193656] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380432.745156] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380432.745159] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid <<<>>> [380482.624749] r8169 :03:00.0 eth1: Link is Down [380482.700233] r8169 :02:00.0 eth0: Link is Down [380482.898291] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 3 [380483.575664] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380486.062394] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 3 [380496.978102] PM: suspend entry (deep) [380497.022677] Filesystems sync: 0.044 seconds [380497.023039] Freezing user space processes ... (elapsed 0.004 seconds) done. [380497.027494] OOM killer disabled. [380497.027495] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [380497.029186] printk: Suspending console(s) (use no_console_suspend to debug) [380497.047859] serial 00:06: disabled [380497.048271] serial 00:05: disabled [380497.062541] sd 1:0:0:0: [sda] Synchronizing SCSI cache [380497.062709] sd 1:0:0:0: [sda] Stopping disk [380497.870726] ACPI: Preparing to enter system sleep state S3 [380497.871533] PM: Saving platform NVS memory [380497.871612] Disabling non-boot CPUs ... [380497.872595] IRQ 23: no longer affine to CPU1 [380497.872602] IRQ 26: no longer affine to CPU1 [380497.873630] smpboot: CPU 1 is now offline [380497.877693] IRQ 16: no longer affine to CPU2 [380497.877698] IRQ 18: no longer affine to CPU2 [380497.877710] IRQ 33: no longer affine to CPU2 [380497.878752] smpboot: CPU 2 is now offline [380497.883528] IRQ 28: no longer affine to CPU3 [380497.883535] IRQ 29: no longer affine to CPU3 [380497.884567] smpboot: CPU 3 is now offline [380497.889485] ACPI: Low-level resume complete [380497.889528] PM: Restoring platform NVS memory [380497.892085] Enabling non-boot CPUs ... [380497.892130] x86: Booting SMP configuration: [380497.892131] smpboot: Booting Node 0 Processor 1 APIC 0x2 [380497.894113] CPU1 is up [380497.894144] smpboot: Booting Node 0 Processor 2 APIC 0x4 [380497.896160] CPU2 is up [380497.896185] smpboot: Booting Node 0 Processor 3 APIC 0x6 [380497.898263] CPU3 is up [380497.899479] ACPI: Waking up from system sleep state S3 [380497.919826] pcieport :00:1c.0: pciehp: Slot(0): Card present [380497.920685] sd 1:0:0:0: [sda] Starting disk [380497.922039] serial 00:05: activated [380497.923404] serial 00:06: activated [380498.234677] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [380498.235359] ata2.00: supports DRM functions an
[Kernel-packages] [Bug 1884900] Re: Touchpad not working
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884900 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: Dear Sir, I have updated ubuntu 18.04 to 20.04 in the last 4 days. My laptop's touchpad worked well in the last system, but when I have updated it to 20.04 then touchpad not working, when I started my laptop. I have use a mouse. When I have start my laptop with connected mouse then touchpad not work. but, when I have started a laptop without connected with mouse then touchpad worked. Solve this issue properly. Thank you... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spshubham 1767 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 12:53:16 2020 HibernationDevice: RESUME=UUID=473a994d-cd87-4373-94ae-e2ff8edce101 InstallationDate: Installed on 2020-06-18 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=13763414-9331-414c-b5ad-ef7d3fa37ff2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-20 (3 days ago) dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron3521:pvrA16:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884900] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884900 Title: Touchpad not working Status in linux package in Ubuntu: Confirmed Bug description: Dear Sir, I have updated ubuntu 18.04 to 20.04 in the last 4 days. My laptop's touchpad worked well in the last system, but when I have updated it to 20.04 then touchpad not working, when I started my laptop. I have use a mouse. When I have start my laptop with connected mouse then touchpad not work. but, when I have started a laptop without connected with mouse then touchpad worked. Solve this issue properly. Thank you... ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-37-generic 5.4.0-37.41 ProcVersionSignature: Ubuntu 5.4.0-37.41-generic 5.4.41 Uname: Linux 5.4.0-37-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: spshubham 1767 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jun 24 12:53:16 2020 HibernationDevice: RESUME=UUID=473a994d-cd87-4373-94ae-e2ff8edce101 InstallationDate: Installed on 2020-06-18 (5 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Dell Inc. Inspiron 3521 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_IN SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-37-generic root=UUID=13763414-9331-414c-b5ad-ef7d3fa37ff2 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-37-generic N/A linux-backports-modules-5.4.0-37-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-06-20 (3 days ago) dmi.bios.date: 05/24/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: A16 dmi.board.name: 0JYTX5 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A16 dmi.modalias: dmi:bvnDellInc.:bvrA16:bd05/24/2018:svnDellInc.:pnInspiron3521:pvrA16:rvnDellInc.:rn0JYTX5:rvrA00:cvnDellInc.:ct8:cvrA16: dmi.product.family: 103C_5335KV dmi.product.name: Inspiron 3521 dmi.product.sku: Inspiron 3521 dmi.product.version: A16 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1884900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1553669] Re: Annoying "call from" message when connecting Bose devices
I can confirm that the error persist on Ubuntu 20.04 LTS with headphones LE-Bose AE2 SoundLink. Disabling voice prompts (as Daniel van Vugt mentioned in comment #8) helps a lot, but still there is a whistle but no "call from" voice anymore. -- 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/1553669 Title: Annoying "call from" message when connecting Bose devices Status in bluez package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: Confirmed Bug description: I have a bluetooth Bose OE SoundLink working on Kubuntu 15.10 but each time I initially connect to listen to an audio or video, I hear an annoying "Call from" on my headset. My headset seems to think a connection to a phone call is taking place. This is annoying because the audio will start to play and after a little while the "call from" voice talks over the audio. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1553669/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885010] [NEW] NULL deference in nfs4_get_valid_delegation
Public bug reported: We are getting the following on an NFSv4 client running focal (kernel 5.4.0-33.37): [296787.347971] BUG: unable to handle page fault for address: ffb0 [296787.350255] #PF: supervisor read access in kernel mode [296787.352315] #PF: error_code(0x) - not-present page [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 [296787.355798] Oops: [#2] SMP NOPTI [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P D OE 5.4.0-33-generic #37-Ubuntu [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 10/04/2019 [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc] [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246 [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: [296787.370648] RDX: 8000 RSI: RDI: [296787.372559] RBP: b7b1634a7da0 R08: R09: 8080808080808080 [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 9ef781f22600 [296787.376330] R13: R14: 9efe1db4bc00 R15: c0cc2950 [296787.378220] FS: () GS:9ef78fc4() knlGS: [296787.380165] CS: 0010 DS: ES: CR0: 80050033 [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 [296787.384031] Call Trace: [296787.385985] nfs4_open_prepare+0x89/0x1e0 [nfsv4] [296787.387973] rpc_prepare_task+0x1f/0x30 [sunrpc] [296787.389971] __rpc_execute+0x8c/0x3a0 [sunrpc] [296787.391903] rpc_async_schedule+0x30/0x50 [sunrpc] [296787.393787] process_one_work+0x1eb/0x3b0 [296787.395617] worker_thread+0x4d/0x400 [296787.397431] kthread+0x104/0x140 [296787.399166] ? process_one_work+0x3b0/0x3b0 [296787.400868] ? kthread_park+0x90/0x90 [296787.402518] ret_from_fork+0x1f/0x40 [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm glue_helper xfrm_algo [296787.404232] drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu [296787.421858] CR2: ffb0 [296787.423680] ---[ end trace 2cf3edda87955a36 ]--- [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246 [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: [296787.434922] RDX: 8000 RSI: RDI: [296787.436810] RBP: b7b1615e3da0 R08: R09: 8080808080808080 [296787.438673] R10: 9ef26a0b8c6c R11: 0018 R12: 9ef7817cfa00 [296787.440539] R13: 0004 R14: 9ef8bdeb0400 R15: c0cc2950 [296787.442400] FS: () GS:9ef78fc4() knlGS: [296787.444289] CS: 0010 DS: ES: CR0: 80050033 [296787.446126] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 The problem is a known issue which has been fixed upstream: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=29fe839976266bc7c55b927360a1daae57477723 The patch is a simple 2 line fix. Would be great if you could do an SRU and add that upstream patch. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchp
[Kernel-packages] [Bug 1885010] 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 1885010 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation Status in linux package in Ubuntu: Incomplete Bug description: We are getting the following on an NFSv4 client running focal (kernel 5.4.0-33.37): [296787.347971] BUG: unable to handle page fault for address: ffb0 [296787.350255] #PF: supervisor read access in kernel mode [296787.352315] #PF: error_code(0x) - not-present page [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 [296787.355798] Oops: [#2] SMP NOPTI [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P D OE 5.4.0-33-generic #37-Ubuntu [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 10/04/2019 [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc] [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246 [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: [296787.370648] RDX: 8000 RSI: RDI: [296787.372559] RBP: b7b1634a7da0 R08: R09: 8080808080808080 [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 9ef781f22600 [296787.376330] R13: R14: 9efe1db4bc00 R15: c0cc2950 [296787.378220] FS: () GS:9ef78fc4() knlGS: [296787.380165] CS: 0010 DS: ES: CR0: 80050033 [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 [296787.384031] Call Trace: [296787.385985] nfs4_open_prepare+0x89/0x1e0 [nfsv4] [296787.387973] rpc_prepare_task+0x1f/0x30 [sunrpc] [296787.389971] __rpc_execute+0x8c/0x3a0 [sunrpc] [296787.391903] rpc_async_schedule+0x30/0x50 [sunrpc] [296787.393787] process_one_work+0x1eb/0x3b0 [296787.395617] worker_thread+0x4d/0x400 [296787.397431] kthread+0x104/0x140 [296787.399166] ? process_one_work+0x3b0/0x3b0 [296787.400868] ? kthread_park+0x90/0x90 [296787.402518] ret_from_fork+0x1f/0x40 [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm glue_helper xfrm_algo [296787.404232] drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu [296787.421858] CR2: ffb0 [296787.423680] ---[ end trace 2cf3edda87955a36 ]--- [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246 [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: [296787.434922] RDX: 8000 RSI: RDI: [296787.436810] RBP: f
[Kernel-packages] [Bug 1885011] [NEW] Eoan update: upstream stable patchset 2020-06-24
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-06-24 Ported from the following upstream stable releases: v4.19.128, v5.4.46 from git://git.kernel.org/ devinet: fix memleak in inetdev_init() l2tp: add sk_family checks to l2tp_validate_socket l2tp: do not use inet_hash()/inet_unhash() net: usb: qmi_wwan: add Telit LE910C1-EUX composition NFC: st21nfca: add missed kfree_skb() in an error path vsock: fix timeout in vsock_accept() net: check untrusted gso_size at kernel entry USB: serial: qcserial: add DW5816e QDL support USB: serial: usb_wwan: do not resubmit rx urb on fatal errors USB: serial: option: add Telit LE910C1-EUX compositions iio: vcnl4000: Fix i2c swapped word reading. usb: musb: start session in resume for host port usb: musb: Fix runtime PM imbalance on error vt: keyboard: avoid signed integer overflow in k_ascii tty: hvc_console, fix crashes on parallel open/close staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK CDC-ACM: heed quirk also in error handling nvmem: qfprom: remove incorrect write support uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned Revert "net/mlx5: Annotate mutex destroy for root ns" net/mlx5: Fix crash upon suspend/resume net: stmmac: enable timestamp snapshot for required PTP packets in dwmac v5.10a nfp: flower: fix used time of merge flow statistics net: be more gentle about silly gso requests coming from user USB: serial: ch341: add basis for quirk detection iio:chemical:sps30: Fix timestamp alignment iio:chemical:pms7003: Fix timestamp alignment and prevent data leak. iio: adc: stm32-adc: fix a wrong error message when probing interrupts UBUNTU: upstream stable to v4.19.128, v5.4.46 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2020-06-24 -upstream stable patchset 2020-06-24 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.19.128, v5.4.46 + + from git://git.kernel.org/ + + devinet: fix memleak in inetdev_init() + l2tp: add sk_family checks to l2tp_validate_socket + l2tp: do not use inet_hash()/inet_unhash() + net: usb: qmi_wwan: add Telit LE910C1-EUX composition + NFC: st21nfca: add missed kfree_skb() in an error path + vsock: fix timeout in vsock_accept() + net: check untrusted gso_size at kernel entry + USB: serial: qcserial: add DW5816e QDL support + USB: serial: usb_wwan: do not resubmit rx urb on fatal errors + USB: serial: option: add Telit LE910C1-EUX compositions + iio: vcnl4000: Fix i2c swapped word reading. + usb: musb: start session in resume for host port + usb: musb: Fix runtime PM imbalance on error + vt: keyboard: avoid signed integer overflow in k_ascii + tty: hvc_console, fix crashes on parallel open/close + staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK + CDC-ACM: heed quirk also in error handling + nvmem: qfprom: remove incorrect write support + uprobes: ensure that uprobe->offset
[Kernel-packages] [Bug 1884255] Re: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working
Spotify and Totem working, after modifying the /etc/pulse/daemon.conf file add / modified in: ; default-sample-format = s24le ; default-sample-rate = 192000 YouTube, on the other hand, sometimes works, sometimes not. Most of the time it doesn't work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1884255 Title: [AMD/ATI] SBx00 Azalia (Intel HDA) Audio Ubuntu 20.04 not working Status in linux package in Ubuntu: Confirmed Status in pulseaudio package in Ubuntu: New Bug description: When you start playing some audio, the sound disappears. 00:14.2 Audio device: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) Subsystem: ASUSTeK Computer Inc. M5A78L LE Kernel driver in use: snd_hda_intel Kernel modules: snd_hda_intel uname -a Linux Marcelo-STI-FX6300 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux alsa-info !! !!ALSA Information Script v 0.4.65 !! !!Script ran on: Fri Jun 19 13:38:12 UTC 2020 !!Linux Distribution !!-- Ubuntu 20.04 LTS \n \l DISTRIB_ID=Ubuntu DISTRIB_DESCRIPTION="Ubuntu 20.04 LTS" NAME="Ubuntu" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 20.04 LTS" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies /privacy-policy" UBUNTU_CODENAME=focal !!DMI Information !!--- Manufacturer: System manufacturer Product Name: System Product Name Product Version: System Version Firmware Version: 1201 Board Vendor: ASUSTeK Computer INC. Board Name:M5A78L-M LX/BR !!ACPI Device Status Information !!--- /sys/bus/acpi/devices/ATK0110:00/status15 /sys/bus/acpi/devices/PNP0103:00/status15 /sys/bus/acpi/devices/PNP0400:00/status15 /sys/bus/acpi/devices/PNP0501:00/status15 /sys/bus/acpi/devices/PNP0C0C:00/status11 /sys/bus/acpi/devices/PNP0C0F:00/status9 /sys/bus/acpi/devices/PNP0C0F:01/status9 /sys/bus/acpi/devices/PNP0C0F:02/status9 /sys/bus/acpi/devices/PNP0C0F:03/status9 /sys/bus/acpi/devices/PNP0C0F:04/status9 /sys/bus/acpi/devices/PNP0C0F:05/status9 /sys/bus/acpi/devices/PNP0C0F:06/status9 /sys/bus/acpi/devices/PNP0C0F:07/status9 /sys/bus/acpi/devices/device:20/status 15 /sys/bus/acpi/devices/device:21/status 15 !!Kernel Information !!-- Kernel release:5.4.0-37-generic Operating System: GNU/Linux Architecture: x86_64 Processor: x86_64 SMP Enabled: Yes !!ALSA Version !! Driver version: k5.4.0-37-generic Library version:1.2.3 Utilities version: 1.2.2 !!Loaded ALSA modules !!--- snd_hda_intel !!Sound Servers on this system !! Pulseaudio: Installed - Yes (/usr/bin/pulseaudio) Running - Yes !!Soundcards recognised by ALSA !!- 0 [SB ]: HDA-Intel - HDA ATI SB HDA ATI SB at 0xfe9f4000 irq 16 !!PCI Soundcards installed in the system !!-- 00:14.2 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] SBx00 Azalia (Intel HDA) [1002:4383] Subsystem: ASUSTeK Computer Inc. M5A78L LE [1043:8445] !!Modprobe options (Sound related) !! snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_atiixp_modem: index=-2 snd_intel8x0m: index=-2 snd_via82xx_modem: index=-2 snd_usb_audio: index=-2 snd_usb_caiaq: index=-2 snd_usb_ua101: index=-2 snd_usb_us122l: index=-2 snd_usb_usx2y: index=-2 snd_cmipci: mpu_port=0x330 fm_port=0x388 snd_pcsp: index=-2 snd_usb_audio: index=-2 snd_hda_intel: model=auto snd_hda_intel: dmic detect=0 !!Loaded sound module options !!--- !!Module: snd_hda_intel align_buffer_size : -1 bdl_pos_adj : -1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1,-1 beep_mode : N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N,N dmic_detect : Y enable : Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y,Y enable_msi : -1 id : (null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(null),(nul
[Kernel-packages] [Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
Hi Elvis, thanks for you report! I've verified, and this fix is present on Focal kernel tag "Ubuntu-5.4.0-38.42" - can you give a try with our proposed kernel (currently it's version 5.4.0-39)? See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Cheers, Guilherme ** Changed in: linux (Ubuntu) Status: Incomplete => Fix Committed ** Changed in: linux (Ubuntu) Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation Status in linux package in Ubuntu: Fix Committed Bug description: We are getting the following on an NFSv4 client running focal (kernel 5.4.0-33.37): [296787.347971] BUG: unable to handle page fault for address: ffb0 [296787.350255] #PF: supervisor read access in kernel mode [296787.352315] #PF: error_code(0x) - not-present page [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 [296787.355798] Oops: [#2] SMP NOPTI [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P D OE 5.4.0-33-generic #37-Ubuntu [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 10/04/2019 [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc] [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246 [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: [296787.370648] RDX: 8000 RSI: RDI: [296787.372559] RBP: b7b1634a7da0 R08: R09: 8080808080808080 [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 9ef781f22600 [296787.376330] R13: R14: 9efe1db4bc00 R15: c0cc2950 [296787.378220] FS: () GS:9ef78fc4() knlGS: [296787.380165] CS: 0010 DS: ES: CR0: 80050033 [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 [296787.384031] Call Trace: [296787.385985] nfs4_open_prepare+0x89/0x1e0 [nfsv4] [296787.387973] rpc_prepare_task+0x1f/0x30 [sunrpc] [296787.389971] __rpc_execute+0x8c/0x3a0 [sunrpc] [296787.391903] rpc_async_schedule+0x30/0x50 [sunrpc] [296787.393787] process_one_work+0x1eb/0x3b0 [296787.395617] worker_thread+0x4d/0x400 [296787.397431] kthread+0x104/0x140 [296787.399166] ? process_one_work+0x3b0/0x3b0 [296787.400868] ? kthread_park+0x90/0x90 [296787.402518] ret_from_fork+0x1f/0x40 [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm glue_helper xfrm_algo [296787.404232] drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu [296787.421858] CR2: ffb0 [296787.423680] ---[ end trace 2cf3edda87955a36 ]--- [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246 [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: [296787.434922] RDX: 8000 RSI: RDI: [296787.436810] RBP: b7b1615e3da0 R08: R09: 8080808080808080 [296787.438673] R10: 9ef26a0b8c6c R11: 0018 R12: 9ef7817cfa00 [296787.440539] R1
[Kernel-packages] [Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
Thanks Guilherme, shame on me for not even checking that :) I will try with 5.4.0-39 and report back. It takes a while for our workload to run before it starts hitting the issue, but I can give a somewhat confident answer in an hour or so. By tomorrow I will be very sure. I'm optimistic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation Status in linux package in Ubuntu: Fix Committed Bug description: We are getting the following on an NFSv4 client running focal (kernel 5.4.0-33.37): [296787.347971] BUG: unable to handle page fault for address: ffb0 [296787.350255] #PF: supervisor read access in kernel mode [296787.352315] #PF: error_code(0x) - not-present page [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 [296787.355798] Oops: [#2] SMP NOPTI [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P D OE 5.4.0-33-generic #37-Ubuntu [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 10/04/2019 [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc] [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246 [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: [296787.370648] RDX: 8000 RSI: RDI: [296787.372559] RBP: b7b1634a7da0 R08: R09: 8080808080808080 [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 9ef781f22600 [296787.376330] R13: R14: 9efe1db4bc00 R15: c0cc2950 [296787.378220] FS: () GS:9ef78fc4() knlGS: [296787.380165] CS: 0010 DS: ES: CR0: 80050033 [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 [296787.384031] Call Trace: [296787.385985] nfs4_open_prepare+0x89/0x1e0 [nfsv4] [296787.387973] rpc_prepare_task+0x1f/0x30 [sunrpc] [296787.389971] __rpc_execute+0x8c/0x3a0 [sunrpc] [296787.391903] rpc_async_schedule+0x30/0x50 [sunrpc] [296787.393787] process_one_work+0x1eb/0x3b0 [296787.395617] worker_thread+0x4d/0x400 [296787.397431] kthread+0x104/0x140 [296787.399166] ? process_one_work+0x3b0/0x3b0 [296787.400868] ? kthread_park+0x90/0x90 [296787.402518] ret_from_fork+0x1f/0x40 [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm glue_helper xfrm_algo [296787.404232] drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu [296787.421858] CR2: ffb0 [296787.423680] ---[ end trace 2cf3edda87955a36 ]--- [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246 [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: [296787.434922] RDX: 8000 RSI: RDI: [296787.436810] RBP: b7b1615e3da0 R08: R09: 8080808080808080 [296787.438673] R10: 9ef26a0b8c6c R11: 0018 R12: 9ef7817cfa00 [296787.440539] R13: 0004 R14: 9ef8bdeb0400 R15: c0cc2950 [296787.442400] FS: () GS:9ef78fc4() knlGS: [2967
[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf
Kernel SRU request submitted: https://lists.ubuntu.com/archives/kernel-team/2020-June/thread.html#111487 Updating status to 'In Progress'. ** Description changed: + SRU Justification: + == + + [Impact] + + * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters + reported with lscpumf are not usable with 'perf stat -e'. + + * 'lscpumf -c' provides a list of available counters, but the following + are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR + + * 'perf list' is also not offering these counters. + + * On the kernel side this is fixed with the following upstream accepted + commit: + + [Fix] + + * d68d5d51dc898895b4e15bea52e5668ca9e76180 d68d5d51dc898895b + "s390/cpum_cf: Add new extended counters for IBM z15" + + [Test Case] + + * Requires the fix/patch of the perf tool, as mentioned in the bug, too. + + * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in + LPAR is needed where the counters are enabled in the activation profile. + + * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, + DFLT_CC, DFLT_CCERROR are listed + + * Use 'perf stat -e' to enable amd make use of these counters. + + [Regression Potential] + + * The regression can be considered as low, since: + + * it's architecture specific (s390x) + + * limited to IBM z15 hardware + + * and only additional (s390x) hardware counters are defined and added. + + [Other] + + * This requires a patch to be included into the perf itself, too - + please see bug description for more details. + + * Since this patch is upstream in kernel 5.7 it will automatically land + in groovy. + + __ + ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e - + ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux - - Machine Type = z15 8561 - + + Machine Type = z15 8561 + ---Steps to Reproduce--- - lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR + lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. - - A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. + A solution will be a backport to 20.04, and tried to made available for + next SRU , code needed before 06-12. Addl Info from Dev: - I have downloaded the following repository + I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 ** Changed in: linux (Ubuntu Focal) Status: New => In Progress ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: ubuntu-z-systems Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * d68d5d51dc898895b4e15bea52e5668ca9e76180 d68d5d51dc898895b "s390/cpum_cf: Add new extended counters for IBM z15" [Test Case] * Requires the fix/patch of the perf tool, as mentioned in the bug, too. * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only addi
[Kernel-packages] [Bug 1885010] Re: NULL deference in nfs4_get_valid_delegation
Thanks Elvis, no hurries. And no need to be ashamed, there's a bunch of tags/trees, and this is not released yet (just on proposed), so we're here to help =) Cheers, Guilherme -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1885010 Title: NULL deference in nfs4_get_valid_delegation Status in linux package in Ubuntu: Fix Committed Bug description: We are getting the following on an NFSv4 client running focal (kernel 5.4.0-33.37): [296787.347971] BUG: unable to handle page fault for address: ffb0 [296787.350255] #PF: supervisor read access in kernel mode [296787.352315] #PF: error_code(0x) - not-present page [296787.354137] PGD 15bf00e067 P4D 15bf00e067 PUD 15bf010067 PMD 0 [296787.355798] Oops: [#2] SMP NOPTI [296787.357271] CPU: 49 PID: 605315 Comm: kworker/u131:3 Tainted: P D OE 5.4.0-33-generic #37-Ubuntu [296787.358756] Hardware name: GIGABYTE G291-Z20-00/MZ21-G20-00, BIOS F06 10/04/2019 [296787.360274] Workqueue: rpciod rpc_async_schedule [sunrpc] [296787.361790] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.363281] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.366780] RSP: 0018:b7b1634a7d98 EFLAGS: 00010246 [296787.368740] RAX: 9ef2958e9b00 RBX: 9ef59f91 RCX: [296787.370648] RDX: 8000 RSI: RDI: [296787.372559] RBP: b7b1634a7da0 R08: R09: 8080808080808080 [296787.374441] R10: 9ef731e9d26c R11: 0018 R12: 9ef781f22600 [296787.376330] R13: R14: 9efe1db4bc00 R15: c0cc2950 [296787.378220] FS: () GS:9ef78fc4() knlGS: [296787.380165] CS: 0010 DS: ES: CR0: 80050033 [296787.382076] CR2: ffb0 CR3: 001a2799c000 CR4: 003406e0 [296787.384031] Call Trace: [296787.385985] nfs4_open_prepare+0x89/0x1e0 [nfsv4] [296787.387973] rpc_prepare_task+0x1f/0x30 [sunrpc] [296787.389971] __rpc_execute+0x8c/0x3a0 [sunrpc] [296787.391903] rpc_async_schedule+0x30/0x50 [sunrpc] [296787.393787] process_one_work+0x1eb/0x3b0 [296787.395617] worker_thread+0x4d/0x400 [296787.397431] kthread+0x104/0x140 [296787.399166] ? process_one_work+0x3b0/0x3b0 [296787.400868] ? kthread_park+0x90/0x90 [296787.402518] ret_from_fork+0x1f/0x40 [296787.404158] Modules linked in: rpcsec_gss_krb5 auth_rpcgss nfsv4 nfs lockd grace sunrpc xt_nat xt_tcpudp veth xt_conntrack xt_MASQUERADE nf_conntrack_netlink nfnetlink xfrm_user xt_addrtype iptable_filter iptable_nat nf_nat nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 libcrc32c bpfilter br_netfilter bridge stp llc aufs overlay md4 cmac nls_utf8 cifs libarc4 fscache libdes binfmt_misc snd_hda_codec_hdmi amd64_edac_mod edac_mce_amd ipmi_ssif nls_iso8859_1 kvm_amd kvm snd_hda_intel snd_intel_dspcfg snd_hda_codec snd_seq_midi snd_seq_midi_event snd_hda_core snd_rawmidi snd_hwdep snd_pcm snd_seq snd_seq_device snd_timer ucsi_ccg snd typec_ucsi typec soundcore k10temp ccp ipmi_si mac_hid nvidia_uvm(OE) sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 mlx5_ib nvidia_drm(POE) nvidia_modeset(POE) ib_uverbs ib_core nvidia(POE) crct10dif_pclmul crc32_pclmul ghash_clmulni_intel ast drm_vram_helper aesni_intel i2c_algo_bit crypto_simd ixgbe cryptd ttm glue_helper xfrm_algo [296787.404232] drm_kms_helper mlx5_core dca mdio syscopyarea sysfillrect sysimgblt fb_sys_fops nvme pci_hyperv_intf drm tls nvme_core mlxfw ahci ipmi_devintf i2c_piix4 libahci ipmi_msghandler i2c_nvidia_gpu [296787.421858] CR2: ffb0 [296787.423680] ---[ end trace 2cf3edda87955a36 ]--- [296787.425547] RIP: 0010:nfs4_get_valid_delegation+0xd/0x30 [nfsv4] [296787.427389] Code: 89 ef e8 06 c0 f9 ff e9 ec fd ff ff 90 0f 1f 44 00 00 55 48 89 e5 f0 80 4f 48 08 5d c3 0f 1f 44 00 00 55 31 f6 48 89 e5 41 54 <4c> 8b 67 b0 4c 89 e7 e8 07 f9 ff ff 84 c0 b8 00 00 00 00 4c 0f 44 [296787.431172] RSP: 0018:b7b1615e3d98 EFLAGS: 00010246 [296787.433050] RAX: 9ee9faf45ec0 RBX: 9ef16c5dd000 RCX: [296787.434922] RDX: 8000 RSI: RDI: [296787.436810] RBP: b7b1615e3da0 R08: R09: 8080808080808080 [296787.438673] R10: 9ef26a0b8c6c R11: 0018 R12: 9ef7817cfa00 [296787.440539] R13: 0004 R14: 9ef8bdeb0400 R15: c0cc2950 [296787.442400] FS: () GS:9ef78fc4() knlGS: [296787.444289] CS: 0010 DS: ES: CR0: 80050033 [296787.446126] CR2: ffb0 CR3: 0
[Kernel-packages] [Bug 1881096] Re: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf
But 'perf tool' patch (linux-tools-common, linux-tools-$(uname -r) ) still needed! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1881096 Title: [UBUNTU 20.04] Deflate counters reported by lscpumf are not valid or available with perf Status in Ubuntu on IBM z Systems: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Focal: In Progress Bug description: SRU Justification: == [Impact] * With perf from Ubuntu 20.04 on IBM z15 hardware, some counters reported with lscpumf are not usable with 'perf stat -e'. * 'lscpumf -c' provides a list of available counters, but the following are not usable: DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR * 'perf list' is also not offering these counters. * On the kernel side this is fixed with the following upstream accepted commit: [Fix] * d68d5d51dc898895b4e15bea52e5668ca9e76180 d68d5d51dc898895b "s390/cpum_cf: Add new extended counters for IBM z15" [Test Case] * Requires the fix/patch of the perf tool, as mentioned in the bug, too. * An IBM z15 (or LinuxONE III) system with Ubuntu 20.04 installed in LPAR is needed where the counters are enabled in the activation profile. * Use 'perf list' to determine if the counters DFLT_ACCESS, DFLT_CYCLES, DFLT_CC, DFLT_CCERROR are listed * Use 'perf stat -e' to enable amd make use of these counters. [Regression Potential] * The regression can be considered as low, since: * it's architecture specific (s390x) * limited to IBM z15 hardware * and only additional (s390x) hardware counters are defined and added. [Other] * This requires a patch to be included into the perf itself, too - please see bug description for more details. * Since this patch is upstream in kernel 5.7 it will automatically land in groovy. __ ---Problem Description--- ubuntu 20.04: perf on z15: some counters reported with lscpumf are not usable with perf stat -e ---uname output--- Linux ubu204 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:57:22 UTC 2020 s390x s390x s390x GNU/Linux Machine Type = z15 8561 ---Steps to Reproduce--- lscpumf -c gives a list of available counters, but a few of them are not usable: DFLT_ACCESS,DFLT_CYCLES,DFLT_CC,DFLT_CCERROR perf list is also not offering these counters. A solution will be a backport to 20.04, and tried to made available for next SRU , code needed before 06-12. Addl Info from Dev: I have downloaded the following repository https://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux/+git/focal and checked out branch master-next. Both patches appended apply without warning and the compilation showed no error. For the perf tool: e7950166e40271c02 perf vendor events s390: Add new deflate counters for IBM z15 For the s390 kernel d68d5d51dc898895b s390/cpum_cf: Add new extended counters for IBM z15 All accepted for kernel 5.7 rc1 Please include both patches into Ubuntu 20.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1881096/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883874] Re: dkms-build: downloads fail in private PPAs
This bug was fixed in the package linux - 5.4.0-39.43 --- linux (5.4.0-39.43) focal; urgency=medium * dkms-build: downloads fail in private PPAs (LP: #1883874) - dkms-build: apt-cache policy elides username:password information * Packaging resync (LP: #1786013) - update dkms package versions -- Kleber Sacilotto de Souza Fri, 19 Jun 2020 11:56:47 +0200 ** Changed in: linux (Ubuntu Focal) Status: In Progress => Fix Released ** Changed in: linux (Ubuntu Eoan) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883874 Title: dkms-build: downloads fail in private PPAs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: We currently using apt-cache policy to obtain the local URLs this eliminates username and password data. We need the URLs intact in order to build in private PPAs. Switch URL source. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883874] Re: dkms-build: downloads fail in private PPAs
This bug was fixed in the package linux - 5.3.0-61.55 --- linux (5.3.0-61.55) eoan; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions * dkms-build: downloads fail in private PPAs (LP: #1883874) - dkms-build: apt-cache policy elides username:password information -- Kleber Sacilotto de Souza Fri, 19 Jun 2020 12:35:40 +0200 ** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883874 Title: dkms-build: downloads fail in private PPAs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: We currently using apt-cache policy to obtain the local URLs this eliminates username and password data. We need the URLs intact in order to build in private PPAs. Switch URL source. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883874] Re: dkms-build: downloads fail in private PPAs
This bug was fixed in the package linux - 4.15.0-108.109 --- linux (4.15.0-108.109) bionic; urgency=medium * Packaging resync (LP: #1786013) - update dkms package versions * dkms-build: downloads fail in private PPAs (LP: #1883874) - dkms-build: apt-cache policy elides username:password information -- Kleber Sacilotto de Souza Fri, 19 Jun 2020 13:07:28 +0200 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883874 Title: dkms-build: downloads fail in private PPAs Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Released Status in linux source package in Focal: Fix Released Bug description: We currently using apt-cache policy to obtain the local URLs this eliminates username and password data. We need the URLs intact in order to build in private PPAs. Switch URL source. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883874/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788928] Re: psmouse: after sleep/suspend thinkpad touchpad not functional
*** This bug is a duplicate of bug 1786574 *** https://bugs.launchpad.net/bugs/1786574 I face the same issue with a lenovo thinkpad t420. After suspending the left mouse button does not work. Everything else works fine. I tried your suggestions with uncommenting i2c_i801 and adding "psmouse.synaptics_intertouch=0" to grub. First I tried uncommenting; this did not work. Then I added "psmouse.." to grub and keep i2c_i801 uncommented; this did not work. After that I tried only addind "psmouse.." to grub which also did not work. I also tried to delete and add psmouse and i2c_i801 from kernel with modprobe. Also no changes. Another strange thing is, if I run "xinput list" and choose the id of "SynPS/2 Synaptics TouchPad" and run "xinput --test 11" I get the following result after pressing left button (1) first and then right button (3): button press 1 button release 1 button press 3 button release 3 So it seems that the system is notified about it.. Here are some details about the system: $ cat /proc/cmdline BOOT_IMAGE=/boot/vmlinuz-5.3.0-59-generic root=UUID=4a0ef122-9e1d-4b72-bcd7-928b326d1a9e ro quiet splash psmouse.synaptics_intertouch=0 vt.handoff=1 $ uname -a Linux devicename 5.3.0-59-generic #53~18.04.1-Ubuntu SMP Thu Jun 4 14:58:26 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux $ cat /etc/os-release NAME="Ubuntu" VERSION="18.04.4 LTS (Bionic Beaver)" ID=ubuntu ID_LIKE=debian PRETTY_NAME="Ubuntu 18.04.4 LTS" VERSION_ID="18.04" HOME_URL="https://www.ubuntu.com/"; SUPPORT_URL="https://help.ubuntu.com/"; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"; VERSION_CODENAME=bionic UBUNTU_CODENAME=bionic Finally one thing which works independently from both changes (i2c_i801 and modifying grub) is to switch to another tty like pressing CTRL+ALT+F3 and switching back with CTRL+ALT+F2. But I do not have any idea, what is loaded or unloaded after doing this. Let me know if you need more details.. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788928 Title: psmouse: after sleep/suspend thinkpad touchpad not functional Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: Summary: The touchpad after sleep/suspend of my ThinkPad X1 will not function correctly. Expected Behavior: After sleep/suspend scroll works correctly. Actual Behavior: Unable to scroll or correctly click on a window and move it without reloading the driver Steps to reproduce: 1. Install Bionic on Thinkpad X1 (4.15.0-32-generic) 2. Open something to scroll (e.g. browser, terminal, etc.) 3. Close lid 4. Re-open lid once sleeping/suspended 5. Try to scroll and note that it does not work Workaround: Run the following after re-opening the lid $ sudo modprobe psmouse -r; sudo modprobe psmouse dmesg on reload: [12753.847050] psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4758] [12753.879362] psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1096..] [12753.879375] psmouse serio1: synaptics: Trying to set up SMBus access [12753.882246] psmouse serio1: synaptics: SMbus companion is not ready yet [12753.944774] psmouse serio1: synaptics: Touchpad model: 1, fw: 8.1, id: 0x1e2b1, caps: 0xf003a3/0x943300/0x12e800/0x1, board id: 3072, fw id: 1795685 [12753.944791] psmouse serio1: synaptics: serio: Synaptics pass-through port at isa0060/serio1/input0 [12753.985102] input: SynPS/2 Synaptics TouchPad as /devices/platform/i8042/serio1/input/input24 [12754.619594] psmouse serio5: trackpoint: IBM TrackPoint firmware: 0x0e, buttons: 3/3 [12754.823238] input: TPPS/2 IBM TrackPoint as /devices/platform/i8042/serio1/serio5/input/input25 --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: powersj2506 F pulseaudio /dev/snd/controlC0: powersj2506 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=40a4eb28-4454-44f0-a377-ea611ce685bb InstallationDate: Installed on 2018-02-19 (185 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180214) Lsusb: Bus 001 Device 002: ID 8087:8001 Intel Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 002 Device 002: ID 04f2:b45d Chicony Electronics Co., Ltd Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20BSCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=e
[Kernel-packages] [Bug 1878726] Re: Live USB Installer not working Samsung Notebook 9 Pro 15"
Older version Live USBs work. I am currently running on a Live Backup 19.10 to write this. I am only having an issue with 20.04. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1878726 Title: Live USB Installer not working Samsung Notebook 9 Pro 15" Status in linux package in Ubuntu: Confirmed Bug description: Live USB made from ubuntu-20.04-desktop-amd64 fails to boot. System hangs with watchdog: BUG: soft lockup - CPU# and rcu: INFO: rcu_sched self-detected stall on CPU. System specs: Intel(R) i7-7500U running AMD discrete graphics Have tested the Live USB on other systems with no problems, appears to be hardware related with the Samsung Notebook 9 Pro and other systems (Dell, etc.) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1878726/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883008] Re: Displaylink USB3 HDMI Adapter does not resume after suspending
** Changed in: linux (Ubuntu) Assignee: Canonical Desktop Team (canonical-desktop-team) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1883008 Title: Displaylink USB3 HDMI Adapter does not resume after suspending Status in linux package in Ubuntu: Confirmed Bug description: Hi I recently updated to Ubuntu 20.04 and my Display Link USB adapter worked finw at first. Recently it does not resume operation after suspending the system: Plugging Adapter into USB Port: [380431.001721] usb 3-10: new high-speed USB device number 35 using xhci_hcd [380431.026448] usb 3-10: New USB device found, idVendor=17e9, idProduct=4301, bcdDevice=35.81 [380431.026450] usb 3-10: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [380431.026451] usb 3-10: Product: USB3.0 UHD HDMI Adapter [380431.026452] usb 3-10: Manufacturer: DisplayLink [380431.026453] usb 3-10: SerialNumber: 000100110005089 [380431.031513] usb 3-10: Warning! Unlikely big volume range (=511), cval->res is probably wrong. [380431.031515] usb 3-10: [13] FU [DisplayLink Audio Playback Volume] ch = 2, val = -8176/0/16 [380431.534305] evdi: [D] evdi_painter_connect:644 (dev=-1) Process is trying to connect [380431.534307] evdi: [I] Task 290879 (DesktopManagerE) of process 290871 (DisplayLinkMana) [380431.534310] evdi: [D] evdi_painter_connect:694 (dev=1) Connected with 7f108832 [380431.534313] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629174] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629177] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid [380431.629361] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380431.629362] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid [380432.193645] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380432.193654] evdi: [D] evdi_painter_mode_changed_notify:622 (dev=1) Notifying mode changed: 2560x1440@60; bpp 32; [380432.193655] evdi: [D] evdi_log_pixel_format:586 pixel format XR24 little-endian (0x34325258) [380432.193656] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380432.745156] evdi: [D] evdi_detect:90 (dev=1) poll connector state: connected [380432.745159] evdi: [D] evdi_painter_get_edid_copy:240 (dev=1) EDID valid <<<>>> [380482.624749] r8169 :03:00.0 eth1: Link is Down [380482.700233] r8169 :02:00.0 eth0: Link is Down [380482.898291] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 3 [380483.575664] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 0 [380486.062394] evdi: [D] evdi_painter_dpms_notify:559 (dev=1) Notifying dpms mode: 3 [380496.978102] PM: suspend entry (deep) [380497.022677] Filesystems sync: 0.044 seconds [380497.023039] Freezing user space processes ... (elapsed 0.004 seconds) done. [380497.027494] OOM killer disabled. [380497.027495] Freezing remaining freezable tasks ... (elapsed 0.001 seconds) done. [380497.029186] printk: Suspending console(s) (use no_console_suspend to debug) [380497.047859] serial 00:06: disabled [380497.048271] serial 00:05: disabled [380497.062541] sd 1:0:0:0: [sda] Synchronizing SCSI cache [380497.062709] sd 1:0:0:0: [sda] Stopping disk [380497.870726] ACPI: Preparing to enter system sleep state S3 [380497.871533] PM: Saving platform NVS memory [380497.871612] Disabling non-boot CPUs ... [380497.872595] IRQ 23: no longer affine to CPU1 [380497.872602] IRQ 26: no longer affine to CPU1 [380497.873630] smpboot: CPU 1 is now offline [380497.877693] IRQ 16: no longer affine to CPU2 [380497.877698] IRQ 18: no longer affine to CPU2 [380497.877710] IRQ 33: no longer affine to CPU2 [380497.878752] smpboot: CPU 2 is now offline [380497.883528] IRQ 28: no longer affine to CPU3 [380497.883535] IRQ 29: no longer affine to CPU3 [380497.884567] smpboot: CPU 3 is now offline [380497.889485] ACPI: Low-level resume complete [380497.889528] PM: Restoring platform NVS memory [380497.892085] Enabling non-boot CPUs ... [380497.892130] x86: Booting SMP configuration: [380497.892131] smpboot: Booting Node 0 Processor 1 APIC 0x2 [380497.894113] CPU1 is up [380497.894144] smpboot: Booting Node 0 Processor 2 APIC 0x4 [380497.896160] CPU2 is up [380497.896185] smpboot: Booting Node 0 Processor 3 APIC 0x6 [380497.898263] CPU3 is up [380497.899479] ACPI: Waking up from system sleep state S3 [380497.919826] pcieport :00:1c.0: pciehp: Slot(0): Card present [380497.920685] sd 1:0:0:0: [sda] Starting disk [380497.922039] serial 00:05: activated [380497.923404] serial 00:06: activated [380498.234677] ata2: SATA link up 6.0 Gbps (SStatus 133 SControl 300) [380498.235359] ata2.00: supports DRM functions an
[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake
The attached file contains two screen shots: - power_limit_before.png (old version thermald/now 1.9.1-1ubuntu0.1 amd64) - power_limit_after.png (new version thermald/now 1.9.1-1ubuntu0.2 amd64) Under "stress" workload, the max power consumed is capped below 9W. With the new version it is maintaining up to 15W. So the proposed version ignored PPCC power limit of 9W. ** Attachment added: "power_limits.tar.xz" https://bugs.launchpad.net/ubuntu/focal/+source/thermald/+bug/1874933/+attachment/5386871/+files/power_limits.tar.xz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1874933 Title: Performance workaround for Dell 7390 2-in-1 Ice Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Bug description: == SRU justification focal == As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4 kernel. The 5.4 kernel added support for "Processor thermal device", for Ice Lake, which will expose the power tables (via PPCC). This system default "max RAPL long term power limit" is 15W. But this power table is specifying as 9W. So thermald will limit power to 9W. If dptfxtract is executed, then power limit will be higher than power up value, but most of the users will use out of the box setup. So this need a workaround. This workaround will ignore any power limit less than the power up power limit. This is addressed in thermald 2.1 with two commits: https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861 I know 20.04 LTS uses 1.9.1. I can assist in backport if required. == Fix == Two upstream commits to ease backporting: - eeadf7d2efe Restore to min state on deactivation without depending on hardware state - 9a6dc27879a Clean up the code and documentation Two upstream commits for the fix: - f7db4342933 Avoid polling power in non PPCC case - c3461690eaf Ignore invalid PPCC max power limit == Test case == Open two terminals: -In the first terminal run the following command: "sudo turbostat --show PkgWatt" -In the second terminal run some all CPU busy workload, like stress-ng or mprime After few seconds turbostat will show that power is capped around 9W. Install the updated thermald, and repeat. Now with this fix the power should be capped around 15W. == Regression Potential == This fix involves changing the power limits logic so there is a potential that this may affect change the throttling behaviour of other systems with poorly defined PPCC power tables because it now ignores the power limits less than the power up limits. Users will see their machines run faster and hence active cooling may crank up (e.g. fans) but I think the speed improvement outweighs the noise factor. Note that these changes are already in thermald 2.1 that is now in Ubuntu Groovy 20.10. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1874933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1874933] Re: Performance workaround for Dell 7390 2-in-1 Ice Lake
Used version #apt list | grep thermald thermald/now 1.9.1-1ubuntu0.2 amd64 [installed,local] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to thermald in Ubuntu. https://bugs.launchpad.net/bugs/1874933 Title: Performance workaround for Dell 7390 2-in-1 Ice Lake Status in thermald package in Ubuntu: Fix Released Status in thermald source package in Focal: Fix Committed Bug description: == SRU justification focal == As reported here: https://www.phoronix.com/forums/forum/linux-graphics-x-org-drivers/intel-linux/1174225-dell-xps-7390-intel-ice-lake-performance-hit-hard-by-a-linux-kernel-regression?view=stream This primarily impacts "Ubuntu 20.04 LTS (Focal Fossa)." as it switched to 5.4 kernel. The 5.4 kernel added support for "Processor thermal device", for Ice Lake, which will expose the power tables (via PPCC). This system default "max RAPL long term power limit" is 15W. But this power table is specifying as 9W. So thermald will limit power to 9W. If dptfxtract is executed, then power limit will be higher than power up value, but most of the users will use out of the box setup. So this need a workaround. This workaround will ignore any power limit less than the power up power limit. This is addressed in thermald 2.1 with two commits: https://github.com/intel/thermal_daemon/commit/f7db434293387c965e8d9141608f855893740e3a https://github.com/intel/thermal_daemon/commit/c3461690eafb7304bf59a39fb02955a5154b3861 I know 20.04 LTS uses 1.9.1. I can assist in backport if required. == Fix == Two upstream commits to ease backporting: - eeadf7d2efe Restore to min state on deactivation without depending on hardware state - 9a6dc27879a Clean up the code and documentation Two upstream commits for the fix: - f7db4342933 Avoid polling power in non PPCC case - c3461690eaf Ignore invalid PPCC max power limit == Test case == Open two terminals: -In the first terminal run the following command: "sudo turbostat --show PkgWatt" -In the second terminal run some all CPU busy workload, like stress-ng or mprime After few seconds turbostat will show that power is capped around 9W. Install the updated thermald, and repeat. Now with this fix the power should be capped around 15W. == Regression Potential == This fix involves changing the power limits logic so there is a potential that this may affect change the throttling behaviour of other systems with poorly defined PPCC power tables because it now ignores the power limits less than the power up limits. Users will see their machines run faster and hence active cooling may crank up (e.g. fans) but I think the speed improvement outweighs the noise factor. Note that these changes are already in thermald 2.1 that is now in Ubuntu Groovy 20.10. --- To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/thermald/+bug/1874933/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1885023] [NEW] Focal update: v5.4.48 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.48 upstream stable release from git://git.kernel.org/ ACPI: GED: use correct trigger type field in _Exx / _Lxx handling drm/amdgpu: fix and cleanup amdgpu_gem_object_close v4 ath10k: Fix the race condition in firmware dump work queue drm: bridge: adv7511: Extend list of audio sample rates media: staging: imgu: do not hold spinlock during freeing mmu page table media: imx: imx7-mipi-csis: Cleanup and fix subdev pad format handling crypto: ccp -- don't "select" CONFIG_DMADEVICES media: vicodec: Fix error codes in probe function media: si2157: Better check for running tuner in init objtool: Ignore empty alternatives spi: spi-mem: Fix Dual/Quad modes on Octal-capable devices drm/amdgpu: Init data to avoid oops while reading pp_num_states. arm64/kernel: Fix range on invalidating dcache for boot page tables libbpf: Fix memory leak and possible double-free in hashmap__clear spi: pxa2xx: Apply CS clk quirk to BXT x86,smap: Fix smap_{save,restore}() alternatives sched/fair: Refill bandwidth before scaling net: atlantic: make hw_get_regs optional net: ena: fix error returning in ena_com_get_hash_function() efi/libstub/x86: Work around LLVM ELF quirk build regression ath10k: remove the max_sched_scan_reqs value arm64: cacheflush: Fix KGDB trap detection media: staging: ipu3: Fix stale list entries on parameter queue failure rtw88: fix an issue about leak system resources spi: dw: Zero DMA Tx and Rx configurations on stack ACPICA: Dispatcher: add status checks block: alloc map and request for new hardware queue arm64: insn: Fix two bugs in encoding 32-bit logical immediates block: reset mapping if failed to update hardware queue count drm: rcar-du: Set primary plane zpos immutably at initializing lockdown: Allow unprivileged users to see lockdown status ixgbe: Fix XDP redirect on archs with PAGE_SIZE above 4K platform/x86: dell-laptop: don't register micmute LED if there is no token MIPS: Loongson: Build ATI Radeon GPU driver as module Bluetooth: Add SCO fallback for invalid LMP parameters error kgdb: Disable WARN_CONSOLE_UNLOCKED for all kgdb kgdb: Prevent infinite recursive entries to the debugger pmu/smmuv3: Clear IRQ affinity hint on device removal ACPI/IORT: Fix PMCG node single ID mapping handling mips: Fix cpu_has_mips64r1/2 activation for MIPS32 CPUs spi: dw: Enable interrupts in accordance with DMA xfer mode clocksource: dw_apb_timer: Make CPU-affiliation being optional clocksource: dw_apb_timer_of: Fix missing clockevent timers media: dvbdev: Fix tuner->demod media controller link btrfs: account for trans_block_rsv in may_commit_transaction btrfs: do not ignore error from btrfs_next_leaf() when inserting checksums ARM: 8978/1: mm: make act_mm() respect THREAD_SIZE batman-adv: Revert "disable ethtool link speed detection when auto negotiation off" ice: Fix memory leak ice: Fix for memory leaks and modify ICE_FREE_CQ_BUFS mmc: meson-mx-sdio: trigger a soft reset after a timeout or CRC error Bluetooth: btmtkuart: Improve exception handling in btmtuart_probe() spi: dw: Fix Rx-only DMA transfers x86/kvm/hyper-v: Explicitly align hcall param for kvm_hyperv_exit net: vmxnet3: fix possible buffer overflow caused by bad DMA value in vmxnet3_get_rss() x86: fix vmap arguments in map_irq_stack staging: android: ion: use vmap instead of vm_map_ram ath10k: fix kernel null pointer dereference media: staging/intel-ipu3: Implement lock for stream on/off operations spi: Respect DataBitLength field of SpiSerialBusV2() ACPI resource brcmfmac: fix wrong location to get firmware feature regulator: qcom-rpmh: Fix typos in pm8150 and pm8150l tools api fs: Make xxx__mountpoint() more scalable e1000: Distribute switch variables for initialization dt-bindings: display: mediatek: control dpi pins mode to avoid leakage drm/mediatek: set dpi pin mode to gpio low to avoid leakage current audit: fix a net reference leak in audit_send_reply() media: dvb: return -EREMOTEIO on i2c transfer failure. media: platform: fcp: Set appropriate DMA parameters MIPS: Make sparse_init() using top-down allocation ath10k: add flush tx packets for SDIO chip Bluetooth: btbcm: Add 2 missing models to subver tables audit: fix a net reference leak in audit_list_rules_send() Drivers: hv: vmbus: Always handle the VMBus messages on CPU0 dpaa2-eth: fix return codes used in ndo_setup_tc netfilter: nft_nat: return EOPNOTSUPP if type or flags are not supported selftests/bpf: Fix memory leak in extract_build_id() net: bcmgenet: set Rx mode before starting netif net: bcmgenet: Fix WoL wit