[Kernel-packages] [Bug 1856134] Re: Support DPCD aux brightness control
** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Also affects: linux-oem-osp1 (Ubuntu Focal) Importance: Undecided Status: New ** No longer affects: linux (Ubuntu Bionic) ** No longer affects: linux-oem-osp1 (Ubuntu 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/1856134 Title: Support DPCD aux brightness control Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Status in linux-oem-osp1 package in Ubuntu: New Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Focal: Incomplete Bug description: [Impact] A new Dell platform using DPCD aux to adjust the brightness, we need to backport some patches which are still under discussing. [Fix] Here is the patchset we need. https://patchwork.freedesktop.org/series/69914/ [Test] Verified on new Dell platform which use DPCD aux to adjust brightness and also others which using pwm to adjust brightness, no regression found. [Regression Potential] Low, the new DPCD method only taken effect on the platforms which are listed in the quirk. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1856134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
@Wayne, Simply remove backport-iwlwifi-dkms on your Eoan system. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Confirmed Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854689] Re: BlueZ 5.52 release
This bug was fixed in the package bluez - 5.52-0ubuntu1 --- bluez (5.52-0ubuntu1) focal; urgency=medium * New upstream release 5.52 (LP: #1854689): - Fix issue with AVDTP session disconnect timeout handling. - Mark media endpoint APIs as stable interfaces. -- Daniel van Vugt Thu, 12 Dec 2019 09:42:09 +0100 ** Changed in: bluez (Ubuntu) Status: Fix Committed => Fix Released -- 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/1854689 Title: BlueZ 5.52 release Status in bluez package in Ubuntu: Fix Released Bug description: BlueZ 5.52 release: http://www.bluez.org/release-of-bluez-5-52/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856098] Re: Laptop suddenly keeps sending random (touchscreen?) input events
When the issue happens, the device goes crazy and it's impossible to perform any action. I have to close the lid (suspend), wait a few seconds, and open the lid (resume). -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856098 Title: Laptop suddenly keeps sending random (touchscreen?) input events Status in linux package in Ubuntu: Confirmed Bug description: Device: Dell Inspiron 7370 CID: 201704-25503 Ubuntu 19.10 with -proposed activated Kernel 5.3.0-23-generic #25-Ubuntu This laptop is equipped with a touchpad and a touchscreen. Sometimes, it goes crazy and starts sending random input events, as if I was franticly tapping the screen :) The only way I've found to stop that mess is to suspend/resume the device by closing the lid, waiting a few seconds, then opening the lid again. I checked in kernel logs and found that there is an input event created, that probably leads to the behavior I'm observing, and then I have to suspend the device: $ dmesg | grep " input\:" -A1 [41192.850576] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input68 [42711.124024] PM: suspend entry (deep) -- [100647.563448] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input111 [102513.121367] PM: suspend entry (deep) -- [113922.124463] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input122 [115707.625939] PM: suspend entry (deep) -- [118464.566206] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input127 [120923.291900] PM: suspend entry (deep) -- [121086.436845] input: E3:28:E9:21:94:78 as /devices/virtual/input/input130 [122565.426895] PM: suspend entry (deep) -- [122997.788106] input: E3:28:E9:21:94:78 as /devices/virtual/input/input135 [123737.137719] PM: suspend entry (deep) -- [126202.798058] input: E3:28:E9:21:94:78 as /devices/virtual/input/input140 [126233.937280] fwupd[9183]: segfault at ffc8 ip 7f7818d63dd0 sp 7fff6d462b30 error 5 in libxmlb.so.1.0.0[7f7818d5c000+11000] -- [130542.694828] input: E3:28:E9:21:94:78 as /devices/virtual/input/input151 [133343.589750] PM: suspend entry (deep) -- [133495.934919] input: E3:28:E9:21:94:78 as /devices/virtual/input/input156 [134604.582752] PM: suspend entry (deep) -- [134623.041244] input: E3:28:E9:21:94:78 as /devices/virtual/input/input159 [135678.503977] PM: suspend entry (deep) -- [135709.087771] input: E3:28:E9:21:94:78 as /devices/virtual/input/input162 [136322.841701] PM: suspend entry (deep) -- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 2050 F pulseaudio /dev/snd/pcmC0D0c: pieq 2050 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 07:16:25 2019 InstallationDate: Installed on 2019-07-02 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-19 (53 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856098] Re: Laptop suddenly keeps sending random (touchscreen?) input events
Does the erratic behavior happen without ever suspending the system? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856098 Title: Laptop suddenly keeps sending random (touchscreen?) input events Status in linux package in Ubuntu: Confirmed Bug description: Device: Dell Inspiron 7370 CID: 201704-25503 Ubuntu 19.10 with -proposed activated Kernel 5.3.0-23-generic #25-Ubuntu This laptop is equipped with a touchpad and a touchscreen. Sometimes, it goes crazy and starts sending random input events, as if I was franticly tapping the screen :) The only way I've found to stop that mess is to suspend/resume the device by closing the lid, waiting a few seconds, then opening the lid again. I checked in kernel logs and found that there is an input event created, that probably leads to the behavior I'm observing, and then I have to suspend the device: $ dmesg | grep " input\:" -A1 [41192.850576] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input68 [42711.124024] PM: suspend entry (deep) -- [100647.563448] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input111 [102513.121367] PM: suspend entry (deep) -- [113922.124463] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input122 [115707.625939] PM: suspend entry (deep) -- [118464.566206] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input127 [120923.291900] PM: suspend entry (deep) -- [121086.436845] input: E3:28:E9:21:94:78 as /devices/virtual/input/input130 [122565.426895] PM: suspend entry (deep) -- [122997.788106] input: E3:28:E9:21:94:78 as /devices/virtual/input/input135 [123737.137719] PM: suspend entry (deep) -- [126202.798058] input: E3:28:E9:21:94:78 as /devices/virtual/input/input140 [126233.937280] fwupd[9183]: segfault at ffc8 ip 7f7818d63dd0 sp 7fff6d462b30 error 5 in libxmlb.so.1.0.0[7f7818d5c000+11000] -- [130542.694828] input: E3:28:E9:21:94:78 as /devices/virtual/input/input151 [133343.589750] PM: suspend entry (deep) -- [133495.934919] input: E3:28:E9:21:94:78 as /devices/virtual/input/input156 [134604.582752] PM: suspend entry (deep) -- [134623.041244] input: E3:28:E9:21:94:78 as /devices/virtual/input/input159 [135678.503977] PM: suspend entry (deep) -- [135709.087771] input: E3:28:E9:21:94:78 as /devices/virtual/input/input162 [136322.841701] PM: suspend entry (deep) -- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 2050 F pulseaudio /dev/snd/pcmC0D0c: pieq 2050 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 07:16:25 2019 InstallationDate: Installed on 2019-07-02 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-19 (53 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854762] Re: eoan/linux: 5.3.0-25.27 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-hwe: bug 1856210, bug 1855309 + bionic/linux-hwe: bug 1855309, bug 1856210 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854762 Title: eoan/linux: 5.3.0-25.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1855309, bug 1856210 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854549] Re: [acc-1130]sync mainline kernel 5.5rc1 acc patchset into ubuntu HWE kernel branch
** Changed in: kunpeng920/ubuntu-20.04 Status: Triaged => In Progress ** Changed in: kunpeng920/ubuntu-20.04 Assignee: (unassigned) => Ike Panhc (ikepanhc) ** Changed in: kunpeng920/ubuntu-18.04 Status: Triaged => Won't Fix ** Changed in: kunpeng920/ubuntu-18.04-hwe Milestone: None => ubuntu-18.04.5 ** Changed in: kunpeng920/ubuntu-20.04 Milestone: None => ubuntu-20.04-ga ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Ike Panhc (ikepanhc) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854549 Title: [acc-1130]sync mainline kernel 5.5rc1 acc patchset into ubuntu HWE kernel branch Status in kunpeng920: Triaged Status in kunpeng920 ubuntu-18.04 series: Won't Fix Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Triaged Status in kunpeng920 ubuntu-19.10 series: Triaged Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Bug description: [Bug Description] enable 1620 acc function for kunpeng 920 [Steps to Reproduce] 1) 2) 3) [Actual Results] [Expected Results] [Reproducibility] [Additional information] (Firmware version, kernel version, affected hardware, etc. if required): [Resolution] MAINTAINERS: Add maintainer for HiSilicon trng V2 driver hw_random: add HiSilicon TRNG driver support MAINTAINERS: Add maintainer for HiSilicon SEC V2 driver crypto: hisilicon - add DebugFS for HiSilicon SEC Documentation: add DebugFS doc for HiSilicon SEC crypto: hisilicon - add SRIOV for HiSilicon SEC crypto: hisilicon - add HiSilicon SEC V2 driver crypto: hisilicon - use sgl API to get sgl dma addr and len crypto: hisilicon - replace #ifdef with IS_ENABLED for CONFIG_NUMA crypto: hisilicon - no need to check return value of debugfs_create functions crypto: hisilicon - fix to return sub-optimal device when best device has no qps crypto: hisilicon - add vfs_num module param for zip crypto: hisilicon - fix endianness verification problem of QM crypto: hisilicon - fix param should be static when not external. crypto: hisilicon - Fix using plain integer as NULL pointer crypto: hisilicon - tiny fix about QM/ZIP error callback print crypto: hisilicon: Fix misuse of GENMASK macro crypto: hisilicon - select NEED_SG_DMA_LENGTH in qm Kconfig crypto: hisilicon - misc fix about sgl crypto: hisilicon - fix large sgl memory allocation problem when disable smmu crypto: hisilicon - add sgl_sge_nr module param for zip crypto: hisilicon - merge sgl support to hisi_qm module crypto: hisilicon - allow compile-testing on x86 crypto: hisilicon - select CRYPTO_LIB_DES while compiling SEC driver To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1854549/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854657] Re: ACPI errors
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854657 Title: ACPI errors Status in linux package in Ubuntu: Confirmed Bug description: Refer to attachments. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: htpc 1609 F pulseaudio /dev/snd/controlC1: htpc 1609 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (34 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. lxcbr0no wireless extensions. enp3s0no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-MA780G-UD3H Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=0fa008d8-2279-4e78-9043-161b7f514243 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: wayland-session eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/13/2010 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F6b dmi.board.name: GA-MA780G-UD3H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF6b:bd07/13/2010:svnGigabyteTechnologyCo.,Ltd.:pnGA-MA780G-UD3H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-MA780G-UD3H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-MA780G-UD3H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1803600] Re: Elantech - Touchpad not working after upgrading to 18.10 from 18.04
Also a problem on my MSI GS43VR for 19.10 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1803600 Title: Elantech - Touchpad not working after upgrading to 18.10 from 18.04 Status in linux package in Ubuntu: Confirmed Bug description: Confirmed affected laptops: ThinkPad: L480 L580 P72 P52 When updating from 18.04 to 18.10 on a ThinkPad L480 the Elantech touchpad stopped working. This means it is not recognized at all. This problem occured after the first boot in 18.10 `dmesg | grep -i elantech` shows the following errors: [3.409043] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [3.427372] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [3.447275] psmouse serio1: elantech: Elan sample query result 00, 23, c8 [3.464905] psmouse serio1: elantech: Trying to set up SMBus access [5.576149] elan_i2c 0-0015: 0-0015 supply vcc not found, using dummy regulator [5.586505] elan_i2c 0-0015: failed to get resolution: -71 [5.586527] elan_i2c: probe of 0-0015 failed with error -71 uname: $ uname -a Linux test 4.18.0-10-generic #11-Ubuntu SMP Thu Oct 11 15:13:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux I found the following thread which solves the problem temporarly (and reports the same problem in Arch): https://bugs.archlinux.org/task/59714 Running the following command enables it again for the current session: sudo sh -c 'echo -n "elantech"> /sys/bus/serio/devices/serio1/protocol' dmesg afterwards: [ 569.522490] psmouse serio1: elantech: assuming hardware version 4 (with firmware version 0x5f3001) [ 569.544584] psmouse serio1: elantech: Synaptics capabilities query result 0x90, 0x18, 0x10. [ 569.565939] psmouse serio1: elantech: Elan sample query result 00, 23, c8 Before running the fix: $ cat /sys/bus/serio/devices/serio1/protocol ETSMBus and after: $ cat /sys/bus/serio/devices/serio1/protocol ETPS/2 After reboot the command has to be run again, of course. ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: xorg 1:7.7+19ubuntu8 ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12 Uname: Linux 4.18.0-11-generic x86_64 ApportVersion: 2.20.10-0ubuntu13.1 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins' CompositorRunning: None CurrentDesktop: KDE Date: Thu Nov 15 20:59:36 2018 DistUpgraded: 2018-11-10 09:56:53,358 DEBUG icon theme changed, re-reading DistroCodename: cosmic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.18, 4.15.0-38-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-10-generic, x86_64: installed virtualbox, 5.2.18, 4.18.0-11-generic, x86_64: installed GraphicsCard: Intel Corporation UHD Graphics 620 [8086:5917] (rev 07) (prog-if 00 [VGA controller]) Subsystem: Lenovo UHD Graphics 620 [17aa:506a] InstallationDate: Installed on 2018-08-06 (101 days ago) InstallationMedia: Xubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: LENOVO 20LS001AGE ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-11-generic root=UUID=a1f97298-a2b8-469d-80ed-7497c6e6 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: Upgraded to cosmic on 2018-11-10 (5 days ago) dmi.bios.date: 02/09/2018 dmi.bios.vendor: LENOVO dmi.bios.version: R0QET37W (1.14 ) dmi.board.asset.tag: Not Available dmi.board.name: 20LS001AGE dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrR0QET37W(1.14):bd02/09/2018:svnLENOVO:pn20LS001AGE:pvrThinkPadL480:rvnLENOVO:rn20LS001AGE:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad L480 dmi.product.name: 20LS001AGE dmi.product.sku: LENOVO_MT_20LS_BU_Think_FM_ThinkPad L480 dmi.product.version: ThinkPad L480 dmi.sys.vendor: LENOVO version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.95-1 version.libgl1-mesa-dri: libgl1-mesa-dri 18.2.4-0~b~padoka0 version.libgl1-mesa-glx: libgl1-mesa-glx 18.2.4-0~b~padoka0 version.xserver-xorg-core: xserver-xorg-core 2:1.20.1-3ubuntu2.1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:18.1.0-1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20171229-1ubuntu1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.15-3 To manage notifications about this bug go to:
[Kernel-packages] [Bug 1854819] Re: bionic/linux: 4.15.0-73.82 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 - xenial/linux-azure: bug 1854813, bug 1856203 + xenial/linux-azure: bug 1856203, bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854819 Title: bionic/linux: 4.15.0-73.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 xenial/linux-azure: bug 1856203, bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856202] Re: trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-trusty ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1856203 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Thursday, 12. December 2019 20:41 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 13. December 2019 00:33 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa signed:queued + promote-to-proposed: Pending -- ready for review replaces: bug 1854811 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856202 Title: trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1856203 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Friday, 13. December 2019 00:33 UTC reason: promote-to-proposed: Pending -- ready for review replaces: bug 1854811 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854813] Re: xenial/linux-azure: 4.15.0-1065.70 -proposed tracker
*** This bug is a duplicate of bug 1856203 *** https://bugs.launchpad.net/bugs/1856203 ** This bug has been marked a duplicate of bug 1856203 xenial/linux-azure: 4.15.0-1066.71 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1854813 Title: xenial/linux-azure: 4.15.0-1065.70 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Friday, 06. December 2019 12:32 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1854811 xenial/linux-azure/azure-kernel: bug 1854810 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854813/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Thursday, 12. December 2019 20:58 UTC + phase: Ready for Promote to Proposed + phase-changed: Friday, 13. December 2019 00:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa meta:queued,signed:queued - replaces: bug 1854813 + promote-to-proposed: Pending -- ready for review trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856203 Title: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Friday, 13. December 2019 00:32 UTC reason: promote-to-proposed: Pending -- ready for review trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855235] Re: Intel Wireless-AC 9560 Bluetooth, whenever connected to BLE devices, causes UI freeze when re-logging in after resumed from suspend
Verified 1.183.3/eoan-proposed, 1.178.7/disco-proposed, 1.173.14/bionic- proposed. ** Tags added: verification-done-bionic verification-done-disco verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1855235 Title: Intel Wireless-AC 9560 Bluetooth, whenever connected to BLE devices, causes UI freeze when re-logging in after resumed from suspend Status in HWE Next: New Status in linux-firmware package in Ubuntu: Confirmed Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Status in linux-firmware source package in Eoan: Fix Committed Bug description: [Steps to Reproduce] 1. Pair some Bluetooth BLE device. Open a terminal and run `dmesg -w` to make sure Bluetooth is receiving advertisement events and repeatedly printing: Bluetooth: hci0: advertising data len corrected ... 2. Turn off dim display/blank screen on idle in Settings 3. Shorten long idle suspend time to 2 minutes by: $ gsettings set org.gnome.settings-daemon.plugins.power \ sleep-inactive-ac-timeout 120 4. Idle wait for 2 minute and let system suspend. 5. Resume after 20 seconds suspend or so. [Expected result] System resumes normally. [Actual result] * Screen lighted up, sent to GDM greeter as expected, but UI freeze when pressed ENTER to submit filled account name/password. * No console switch is possible. * Kernel alive because rescue magic key is the only way to escape. * The last line in syslog is: kernel [...] PM: suspend entry (deep) * When Bluetooth is rfkilled, this issue is not happening. When Bluetooth has never paired to BLE devices, this issue is no happening, either. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20190418-59+beaver-osp1-loras+X21 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2019-12-02 (3 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 Package: linux-firmware 1.173.12 PackageArchitecture: all ProcVersionSignature: Ubuntu 5.0.0-1028.32-oem-osp1 5.0.21 Tags: bionic Uname: Linux 5.0.0-1028-oem-osp1 x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854329] Re: Synaptics Touchpad "loosing sync" on HP laptop
Maybe unload the wireless driver before collecting the 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/1854329 Title: Synaptics Touchpad "loosing sync" on HP laptop Status in linux package in Ubuntu: Confirmed Bug description: I have a problem with the touchpad on HP 15-db1041nm (AMD Ryzen 5 3500U). The touchpad freezes for a few seconds then resumes working. There are also freezes when typing where letters repeat, so instead of the letter r i get r. This may be a different and unrelated bug which I will open, but I'm mentioning as the built-in keyboard could be attached to the same bus? This is similar to bug #1803171, but on HP. I was instructed to report a new bug. Attached is dmesg | grep psmouse showing the sync problems that appear. Description: Ubuntu 19.10 Release: 19.10 --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) Package: linux (not installed) Tags: eoan Uname: Linux 5.4.0-050400-generic x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: milan 951 F pulseaudio /dev/snd/controlC0: milan 951 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-10-28 (30 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) IwConfig: lono wireless extensions. eno1 no wireless extensions. MachineType: HP HP Laptop 15-db1xxx Package: linux (not installed) ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-23-generic root=UUID=c6d5dded-989d-4d10-a52c-4e53aaaba9d2 ro mitigations=off quiet splash mitigations=off vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 RfKill: Tags: eoan Uname: Linux 5.3.0-23-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm audio cdrom dip lpadmin lxd plugdev sambashare sudo video _MarkForUpload: True dmi.bios.date: 06/27/2019 dmi.bios.vendor: Insyde dmi.bios.version: F.12 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 85EA dmi.board.vendor: HP dmi.board.version: 51.16 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: HP dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.12:bd06/27/2019:svnHP:pnHPLaptop15-db1xxx:pvrType1ProductConfigId:rvnHP:rn85EA:rvr51.16:cvnHP:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV HP Notebook dmi.product.name: HP Laptop 15-db1xxx dmi.product.sku: 6VK24EA#BED dmi.product.version: Type1ProductConfigId dmi.sys.vendor: HP To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1854329/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856202] Re: trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1856203 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 12. December 2019 20:41 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa signed:queued replaces: bug 1854811 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856202 Title: trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1856203 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 12. December 2019 20:41 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa signed:queued replaces: bug 1854811 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 12. December 2019 20:58 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait + promote-to-proposed: Pending -- builds not complete in ppa meta:queued,signed:queued replaces: bug 1854813 trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856203 Title: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 12. December 2019 20:58 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa meta:queued,signed:queued replaces: bug 1854813 trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845620] Re: stime01 from ubuntu_ltp_syscalls failed on D Power9
** Changed in: linux (Ubuntu Disco) Status: Incomplete => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Invalid ** Changed in: ubuntu-kernel-tests Status: New => In Progress ** Changed in: ubuntu-kernel-tests Assignee: (unassigned) => Thadeu Lima de Souza Cascardo (cascardo) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845620 Title: stime01 from ubuntu_ltp_syscalls failed on D Power9 Status in ubuntu-kernel-tests: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: Invalid Bug description: This failure can only be found on Disco Power9, passed on other arches. Probably a glitch that similar to the hwclock test failure (bug 1802233) tag=stime01 stime=1568943645 dur=-22 exit=exited stat=1 core=no cu=0 cs=0 startup='Fri Sep 20 01:40:45 2019' tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s stime_var.h:45: INFO: Testing libc stime() stime01.c:46: INFO: pt.tv_sec: 1568943675 stime01.c:47: PASS: system time was set to 1568943675 tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s stime_var.h:48: INFO: Testing SYS_stime syscall stime01.c:51: FAIL: system time not set to 1568943705 (got: 1568943660) tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s stime_var.h:51: INFO: Testing SYS_settimeofday syscall stime01.c:46: INFO: pt.tv_sec: 1568943690 stime01.c:47: PASS: system time was set to 1568943690 Summary: passed 2 failed 1 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854819] Re: bionic/linux: 4.15.0-73.82 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 - xenial/linux-azure: bug 1856203, bug 1854813 + xenial/linux-azure: bug 1856203 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854819 Title: bionic/linux: 4.15.0-73.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 xenial/linux-azure: bug 1856203 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855546] Re: Desktop freezes a while than logs out
Sounds like gnome-shell if frozen then get killed. ** Also affects: gnome-shell (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/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: New Status in linux package in Ubuntu: Confirmed Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855546] Re: Desktop freezes a while than logs out
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** 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/1855546 Title: Desktop freezes a while than logs out Status in gnome-shell package in Ubuntu: Incomplete Status in linux package in Ubuntu: Incomplete Bug description: In the last few months I often experience the following symptom. The Ubuntu desktop freezes for 2-3 minutes, then automatically logs out without any user interaction. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-72-generic 4.15.0-72.81 ProcVersionSignature: Ubuntu 4.15.0-72.81-generic 4.15.18 Uname: Linux 4.15.0-72-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: laca 2067 F pulseaudio /dev/snd/controlC2: laca 2067 F pulseaudio /dev/snd/controlC1: laca 2067 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Sat Dec 7 16:01:15 2019 HibernationDevice: RESUME=UUID=9b9553b2-3060-4b74-9890-16e50d306f43 InstallationDate: Installed on 2018-08-25 (469 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) MachineType: Dell Inc. Inspiron 5548 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-72-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-72-generic N/A linux-backports-modules-4.15.0-72-generic N/A linux-firmware 1.173.12 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/04/2014 dmi.bios.vendor: Dell Inc. dmi.bios.version: A02 dmi.board.name: 079JDM dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: A02 dmi.modalias: dmi:bvnDellInc.:bvrA02:bd12/04/2014:svnDellInc.:pnInspiron5548:pvrA02:rvnDellInc.:rn079JDM:rvrA00:cvnDellInc.:ct8:cvrA02: dmi.product.name: Inspiron 5548 dmi.product.version: A02 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1855546/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856202] Re: trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1856203 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 12. December 2019 20:41 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait replaces: bug 1854811 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856202 Title: trusty/linux-azure: 4.15.0-1066.71~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1856203 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 12. December 2019 20:41 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait replaces: bug 1854811 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855237] Re: Unable to reboot Disco on Ubuntu LPAR s390x (5.0.0-38)
Spent quite a bit of time on this and finally some progress. This is not a critical bug anymore as I can now successfully reboot my lpar with the -proposed kernel 5.0.0-38 for SRU Cycle 2019.12.02 During deployment of an lpar we configure DASD aliases via multipath, usually this is required for disk performance however in our lab we are always connecting to just 1 disk, so there is no need to i/o performance in the test lab. Also it is in question if DASD Aliases should not be used on an lpar as they may only be for Zvm's, is this a proper supported configuration? It would appear that having an active subchannel "chzdev -e 0.0.17e0-0.0." is what perhaps is leading to this reboot problem. The system actually is really "rebooting", it simply takes over 20 minutes to accomplish that task. Why so long? The assumption is that, once a channel is activated, the system will build udev rules and rebuild the initramfs. Thus during the reboot phase, the lpar must query each of the enabled disks to ensure they are ok. Oddly , we don't see a delay in a shutdown command either. This is just an assumption since I only see the problem once I activate host multipath via chzdev. This problem has never been seen or experienced in the past and is only isolated to this kernel. Xenial,Eoan -proposed both restart just fine (For this SRU cycle) It's possible that a commit made within this cycle has exposed this issue. However for now there is a valid workaround. In the lpar that Frank Heimes tested, he did NOT have multipathing configured as his system rebooted without any delays, just as I experienced after a fresh install (no multipathing configured) I'm going to leave the severity at Medium as Frank Heimes will obtaining more information about the disk multipathing on the lpar. To see if this possibly is the culprit. ** Changed in: linux (Ubuntu) Assignee: Sean Feole (sfeole) => (unassigned) ** Summary changed: - Unable to reboot Disco on Ubuntu LPAR s390x (5.0.0-38) + Extreme Delayed Reboot with Disco on Ubuntu LPAR s390x (5.0.0-38) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855237 Title: Extreme Delayed Reboot with Disco on Ubuntu LPAR s390x (5.0.0-38) Status in Ubuntu on IBM z Systems: Triaged Status in linux package in Ubuntu: Triaged Bug description: With the proposed Disco kernel (5.0.0-38) I can't reboot the s390x LPAR node s2lp4 When I tried to reboot the system it will render the system into a "Not operating" status. I tried to watch the output from the Integrated ASCII console and the Operating system messages from IBM Hardware Management Console. But there is nothing interesting there From Operating System Messages, it ends at: [ OK ] Reached target Final Step. [ OK ] Started Reboot. [ OK ] Reached target Reboot. And never proceed from this point. And HMC shows "Not operating" From Integrated ASCII console it just shows the login prompt, never prints any other message. Reboot works fine with older kernel (5.0.0-37) ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-38-generic 5.0.0-38.41 ProcVersionSignature: Ubuntu 5.0.0-38.41-generic 5.0.21 Uname: Linux 5.0.0-38-generic s390x NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair AlsaDevices: Error: command ['ls', '-l', '/dev/snd/'] failed with exit code 2: ls: cannot access '/dev/snd/': No such file or directory AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.4 Architecture: s390x ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' CRDA: Error: command ['iw', 'reg', 'get'] failed with exit code 1: nl80211 not found. Date: Thu Dec 5 06:46:12 2019 HibernationDevice: RESUME=UUID=eae923f9-f5a4-41c0-b3e4-04786207dbaa IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Error: command ['lsusb'] failed with exit code 1: PciMultimedia: ProcFB: ProcKernelCmdLine: root=UUID=1a6af794-84a9-4034-a213-39506b9bb91c crashkernel=196M BOOT_IMAGE=0 RelatedPackageVersions: linux-restricted-modules-5.0.0-38-generic N/A linux-backports-modules-5.0.0-38-generic N/A linux-firmware1.178.6 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-z-systems/+bug/1855237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 12. December 2019 20:58 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait replaces: bug 1854813 trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856203 Title: xenial/linux-azure: 4.15.0-1066.71 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Thursday, 12. December 2019 20:58 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait replaces: bug 1854813 trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1718227] Re: replacement of ifupdown with netplan needs integration for /etc/network/if{up, down}.d scripts
> For openvpn + systemd-resolve:
>
> With "up / down" openvpn config file commands you can wrap "systemd-
> resolve --set-dns=XXX" and update the given DNS servers.
There's a package for that: openvpn-systemd-resolved
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to ubuntu-fan in Ubuntu.
https://bugs.launchpad.net/bugs/1718227
Title:
replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
Status in aiccu package in Ubuntu:
Invalid
Status in aoetools package in Ubuntu:
New
Status in avahi package in Ubuntu:
New
Status in bind9 package in Ubuntu:
Invalid
Status in chrony package in Ubuntu:
Fix Released
Status in clamav package in Ubuntu:
Triaged
Status in controlaula package in Ubuntu:
Invalid
Status in ethtool package in Ubuntu:
Triaged
Status in guidedog package in Ubuntu:
New
Status in htpdate package in Ubuntu:
New
Status in ifenslave package in Ubuntu:
Won't Fix
Status in ifmetric package in Ubuntu:
Won't Fix
Status in ifupdown-multi package in Ubuntu:
New
Status in ifupdown-scripts-zg2 package in Ubuntu:
Invalid
Status in isatapd package in Ubuntu:
New
Status in lprng package in Ubuntu:
New
Status in miredo package in Ubuntu:
New
Status in mythtv package in Ubuntu:
New
Status in nplan package in Ubuntu:
New
Status in nss-pam-ldapd package in Ubuntu:
New
Status in ntp package in Ubuntu:
Won't Fix
Status in openntpd package in Ubuntu:
New
Status in openresolv package in Ubuntu:
Won't Fix
Status in openssh package in Ubuntu:
Fix Released
Status in openvpn package in Ubuntu:
Confirmed
Status in openvswitch package in Ubuntu:
Triaged
Status in postfix package in Ubuntu:
New
Status in quicktun package in Ubuntu:
New
Status in resolvconf package in Ubuntu:
New
Status in sendmail package in Ubuntu:
New
Status in shorewall-init package in Ubuntu:
New
Status in sidedoor package in Ubuntu:
New
Status in slrn package in Ubuntu:
New
Status in tinc package in Ubuntu:
New
Status in ubuntu-fan package in Ubuntu:
Fix Released
Status in ucarp package in Ubuntu:
New
Status in uml-utilities package in Ubuntu:
New
Status in uruk package in Ubuntu:
New
Status in vlan package in Ubuntu:
Won't Fix
Status in vzctl package in Ubuntu:
Triaged
Status in wide-dhcpv6 package in Ubuntu:
New
Status in wpa package in Ubuntu:
New
Bug description:
when network is configured with ifupdown, scripts in
/etc/network/ifup.d/ were called on network being brought up and
/etc/network/ifdown.d were called on network being brought down.
Any packages that shipped these hooks need to be verified to have the
same functionality under a netplan configured system.
# binpkgs=$(apt-file search /etc/network/if-up | sed 's,: .*,,' | sort -u)
# for i in $binpkgs; do
src=$(apt-cache show $i | awk '$1 == "Source:" { print $2; exit(0); }');
[ -z "$src" ] && src="$i"; echo $src; done | sort -u
aiccu
aoetools
avahi
bind9
chrony
clamav
controlaula
epoptes
ethtool
guidedog
htpdate
ifenslave
ifmetric
ifupdown-extra
ifupdown-multi
ifupdown-scripts-zg2
isatapd
lprng
miredo
mythtv-backend
nss-pam-ldapd
ntp
openntpd
openresolv
openssh
openvpn
postfix
quicktun
resolvconf
sendmail
shorewall-init
sidedoor
slrn
tinc
ubuntu-fan
ucarp
uml-utilities
uruk
vlan
vzctl
wide-dhcpv6
wpa
Related bugs:
* bug 1718227: replacement of ifupdown with netplan needs integration for
/etc/network/if{up,down}.d scripts
* bug 1713803: replacement of resolvconf with systemd needs integration
* bug 1717983: replacement of isc-dhcp-client with with systemd-networkd for
dhclient needs integration
ProblemType: Bug
DistroRelease: Ubuntu 17.10
Package: netplan (not installed)
ProcVersionSignature: Ubuntu 4.12.0-11.12-generic 4.12.5
Uname: Linux 4.12.0-11-generic x86_64
NonfreeKernelModules: zfs zunicode zavl zcommon znvpair
ApportVersion: 2.20.7-0ubuntu1
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Sep 19 10:53:08 2017
EcryptfsInUse: Yes
InstallationDate: Installed on 2015-07-23 (789 days ago)
InstallationMedia: Ubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150722.1)
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: plan
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/aiccu/+bug/1718227/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Err, here is the patch ** Patch added: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311922/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856161] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311961/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311957/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired
[Kernel-packages] [Bug 1856161] ProcCpuinfo.txt
apport information ** Attachment added: "ProcCpuinfo.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311956/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1854762] Re: eoan/linux: 5.3.0-25.27 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1855309 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854762 Title: eoan/linux: 5.3.0-25.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1855309 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856161] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311959/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1856161] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311958/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1856161] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311963/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311962/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311964/+files/WifiSyslog.txt ** Changed in: linux (Ubuntu) Status: Incomplete => 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12
[Kernel-packages] [Bug 1856161] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311960/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Hi Adrian, if booting from the kernel fails, it obviously hangs as there's no physical disk device to use. Is there a way to write or get the kernel messages to another device at this point? or is my only option to build on usb, then build a new patched kernel on the usb and boot from it ? Sorry, pushing the limits of my ability. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
For those who don't use Ubuntu, please see if reverting this helps: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=9da5a1092b13468839b1a864b126cacfb72ad016 For Ubuntu users please test the following kernel: https://people.canonical.com/~khfeng/lp1766076/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1 [279389.949982] usb usb3: Product: xHCI Host Controller [279389.949983] usb usb3: Manufacturer: Linux 4.15.0-15-generic xhci-hcd
[Kernel-packages] [Bug 1855461] Re: [linux-azure] SAUCE patch to "Fix skb protocol value in tpacket_fill_skb()"
** Also affects: linux-azure (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux-azure (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux-azure (Ubuntu Disco)
Status: New => Invalid
** Changed in: linux-azure (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux-azure (Ubuntu Xenial)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
** Changed in: linux-azure (Ubuntu Disco)
Assignee: (unassigned) => Marcelo Cerri (mhcerri)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1855461
Title:
[linux-azure] SAUCE patch to "Fix skb protocol value in
tpacket_fill_skb()"
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
In Progress
Status in linux-azure source package in Disco:
Invalid
Bug description:
The actual fix for this issue would be to backport two related patches
that were accepted upstream in Feb/March 2019. But doing a full
backport is complicated because of dependencies on other new code.
The two upstream commits are:
75c65772c3d1 ("net/packet: Ask driver for protocol if not provided by user")
18bed89107a4 ("af_packet: fix the tx skb protocol in raw sockets with
ETH_P_ALL")
Instead of a full backport of these patches, a SAUCE patch was
generated to avoid the complicated dependencies. The SAUCE patch is
attached to the bug.
Microsoft and the affected customer feel this patch is pretty small
and safe. Microsoft and the end customer have tested the backport and
confirmed that it solves the problem.
Backports are needed for both the 4.15.0 and the 5.0 azure kernels
that are used in Ubuntu 16.04 and Ubuntu 18.04 images in the Azure
Marketplace. The customer is using the 4.15 kernel from Ubuntu 16.04,
so getting this fix included there is fairly high priority, though not
“critical/emergency” level. Getting the fix included in the 5.0
kernel in Ubuntu 18.04 in the Azure Marketplace is low priority.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855461/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855978] Re: linux-firmware updates breaks Intel 9260 on Bionic
** Tags added: oem-priority originate-from-1856003 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1855978 Title: linux-firmware updates breaks Intel 9260 on Bionic Status in HWE Next: New Status in linux-firmware package in Ubuntu: Triaged Bug description: Bug 1852512 pulls new firmware blobs for 5.3 hwe kernel upgrade, and iwlwifi-9260-th-b0-jf-b0-46.ucode is included. This new version doesn't seem to be compatible with Bionic OEM kernels, and will fail WiFi initialization leaving the system booted without wireless connection. The previous version (1.173.12) has iwlwifi-9260-th-b0-jf-b0-43.ucode instead. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.13 ProcVersionSignature: Ubuntu 4.15.0-1065.75-oem 4.15.18 Uname: Linux 4.15.0-1065-oem x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 Date: Wed Dec 11 14:18:01 2019 Dependencies: DistributionChannelDescriptor: # This is the distribution channel descriptor for the OEM CDs # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor canonical-oem-somerville-bionic-amd64-20180608-47+berlinetta-cfl-r+X77 InstallationDate: Installed on 2019-07-11 (152 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20180608-09:38 PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855978/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Configured grub to show the grub menu and selection kernel 4.15.0-70-generic I got the touchpad to work again. The problem appeared with 4.15.0-72. I you can do that instead of installing a kernel from a non official source. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio device: Intel Corporation
[Kernel-packages] [Bug 1846214] Re: Freezes instead of suspending, most times
Thank you for following up, Kai-Heng. I downloaded these files: ``` -rw-r--r-- 1 mightyiam mightyiam 11M Dec 12 18:57 temp/linux-headers-5.5.0-050500rc1_5.5.0-050500rc1.201912081930_all.deb -rw-r--r-- 1 mightyiam mightyiam 1.2M Dec 12 18:42 temp/linux-headers-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb -rw-r--r-- 1 mightyiam mightyiam 8.6M Dec 12 18:43 temp/linux-image-unsigned-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb -rw-r--r-- 1 mightyiam mightyiam 50M Dec 12 18:48 temp/linux-modules-5.5.0-050500rc1-generic_5.5.0-050500rc1.201912081930_amd64.deb ``` And installed via `dpkg -i `. Then rebooted and made sure to select this 5.5 kernel in the GRUB boot menu. Suspend failed with the same symptoms 2 out of 5 times I tried. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846214 Title: Freezes instead of suspending, most times Status in linux package in Ubuntu: Confirmed Bug description: Hi and thank you for all your free software work. This system usually freezes instead of suspending. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-29-generic 5.0.0-29.31 ProcVersionSignature: Ubuntu 5.0.0-29.31-generic 5.0.21 Uname: Linux 5.0.0-29-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: mightyiam 2139 F pulseaudio /dev/snd/controlC0: mightyiam 2139 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 1 20:28:30 2019 MachineType: Micro-Star International Co., Ltd. GS60 2QE ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-29-generic root=/dev/mapper/ubuntu-encrypted_root_crypt ro splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-5.0.0-29-generic N/A linux-backports-modules-5.0.0-29-generic N/A linux-firmware1.178.3 SourcePackage: linux UpgradeStatus: Upgraded to disco on 2019-06-11 (112 days ago) dmi.bios.date: 02/22/2016 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E16H5IMS.111 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: MS-16H5 dmi.board.vendor: Micro-Star International Co., Ltd. dmi.board.version: REV:0.B dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 10 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE16H5IMS.111:bd02/22/2016:svnMicro-StarInternationalCo.,Ltd.:pnGS602QE:pvrREV1.0:rvnMicro-StarInternationalCo.,Ltd.:rnMS-16H5:rvrREV0.B:cvnToBeFilledByO.E.M.:ct10:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: GS60 2QE dmi.product.sku: To be filled by O.E.M. dmi.product.version: REV:1.0 dmi.sys.vendor: Micro-Star International Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846214/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855461] Re: [linux-azure] SAUCE patch to "Fix skb protocol value in tpacket_fill_skb()"
** Changed in: linux-azure (Ubuntu Disco)
Status: Invalid => New
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1855461
Title:
[linux-azure] SAUCE patch to "Fix skb protocol value in
tpacket_fill_skb()"
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
In Progress
Status in linux-azure source package in Disco:
New
Bug description:
The actual fix for this issue would be to backport two related patches
that were accepted upstream in Feb/March 2019. But doing a full
backport is complicated because of dependencies on other new code.
The two upstream commits are:
75c65772c3d1 ("net/packet: Ask driver for protocol if not provided by user")
18bed89107a4 ("af_packet: fix the tx skb protocol in raw sockets with
ETH_P_ALL")
Instead of a full backport of these patches, a SAUCE patch was
generated to avoid the complicated dependencies. The SAUCE patch is
attached to the bug.
Microsoft and the affected customer feel this patch is pretty small
and safe. Microsoft and the end customer have tested the backport and
confirmed that it solves the problem.
Backports are needed for both the 4.15.0 and the 5.0 azure kernels
that are used in Ubuntu 16.04 and Ubuntu 18.04 images in the Azure
Marketplace. The customer is using the 4.15 kernel from Ubuntu 16.04,
so getting this fix included there is fairly high priority, though not
“critical/emergency” level. Getting the fix included in the 5.0
kernel in Ubuntu 18.04 in the Azure Marketplace is low priority.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855461/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855461] Re: [linux-azure] SAUCE patch to "Fix skb protocol value in tpacket_fill_skb()"
** Changed in: linux-azure (Ubuntu Disco)
Status: New => In Progress
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-azure in Ubuntu.
https://bugs.launchpad.net/bugs/1855461
Title:
[linux-azure] SAUCE patch to "Fix skb protocol value in
tpacket_fill_skb()"
Status in linux-azure package in Ubuntu:
New
Status in linux-azure source package in Xenial:
In Progress
Status in linux-azure source package in Disco:
In Progress
Bug description:
The actual fix for this issue would be to backport two related patches
that were accepted upstream in Feb/March 2019. But doing a full
backport is complicated because of dependencies on other new code.
The two upstream commits are:
75c65772c3d1 ("net/packet: Ask driver for protocol if not provided by user")
18bed89107a4 ("af_packet: fix the tx skb protocol in raw sockets with
ETH_P_ALL")
Instead of a full backport of these patches, a SAUCE patch was
generated to avoid the complicated dependencies. The SAUCE patch is
attached to the bug.
Microsoft and the affected customer feel this patch is pretty small
and safe. Microsoft and the end customer have tested the backport and
confirmed that it solves the problem.
Backports are needed for both the 4.15.0 and the 5.0 azure kernels
that are used in Ubuntu 16.04 and Ubuntu 18.04 images in the Azure
Marketplace. The customer is using the 4.15 kernel from Ubuntu 16.04,
so getting this fix included there is fairly high priority, though not
“critical/emergency” level. Getting the fix included in the 5.0
kernel in Ubuntu 18.04 in the Azure Marketplace is low priority.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux-azure/+bug/1855461/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854819] Re: bionic/linux: 4.15.0-73.82 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 xenial/linux-azure: bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854819 Title: bionic/linux: 4.15.0-73.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 xenial/linux-azure: bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856166] Re: NVS 5200M not supported by 435, but is recommended by ubuntu-drivers
** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Assignee: (unassigned) => Alberto Milone (albertomilone) ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: New => Triaged ** Changed in: nvidia-graphics-drivers-435 (Ubuntu) Status: New => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1856166 Title: NVS 5200M not supported by 435, but is recommended by ubuntu-drivers Status in nvidia-graphics-drivers-430 package in Ubuntu: Triaged Status in nvidia-graphics-drivers-435 package in Ubuntu: Triaged Bug description: I have a Dell Laptop with a NVS 5200M (0DFC) and wondered why ubuntu- drivers recommend the nvidia-driver-435 (and also the wrong driver 430). It won't work with these drivers. $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd0DFCsv1028sd0535bc03sc00i00 vendor : NVIDIA Corporation model: GF108GLM [NVS 5200M] driver : nvidia-340 - distro non-free driver : nvidia-driver-435 - distro non-free recommended driver : nvidia-driver-430 - distro non-free driver : nvidia-driver-390 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 I found the modalias in the packages nvidia-driver-435 and also in the package of the nvidia-driver-430. In the Nvidia READMEs you can find that the NVS 5200M (0DFC) is only supported up to 390. I opened an issue on https://github.com/tseliot/nvidia-graphics- drivers/issues/36 and tseliot told me it could be a parsing problem of the Nvidia READMEs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1856166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854819] Re: bionic/linux: 4.15.0-73.82 -proposed tracker
automated-testing completed successfully with bionic/linux kernel 4.15.0-73.82 https://people.canonical.com/~kernel/status/adt-matrix/bionic-linux- meta.html The task needs to be flipped manually because of an issue with the network-manager package version removed from -updates, so the status will not be reported on the matrix until a new version is promoted. ** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854819 Title: bionic/linux: 4.15.0-73.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 xenial/linux-azure: bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
I would start with a working setup, presumably Ubuntu 18.04. Then get the latest stable kernel (note, it is possible -rc kernels are broken): git clone git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux- stable.git -b linux-5.4.y Patch it, build and install. Amend /etc/defaults/grub to have: GRUB_TIMEOUT_STYLE=menu GRUB_DISABLE_SUBMENU=y GRUB_TIMEOUT=10 GRUB_CMDLINE_LINUX_DEFAULT="" To have affect need to do: sudo update-grub Then you should at least be able to choose the kernel and see some messages. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845863] Re: vma05 in mm from ubuntu_ltp failed on 5.3 kernel
BTW the failure on Eoan generic kernel (5.3.0-25.27) can only be found on AMD64 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1845863 Title: vma05 in mm from ubuntu_ltp failed on 5.3 kernel Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-oracle package in Ubuntu: New Bug description: Test failed with: tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4 Need to check if it has something to do with AppArmor startup='Fri Sep 20 16:48:02 2019' vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vsyscall] reporting wrong vma05 1 TPASS: [vdso] backtrace complete vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Summary: passed 1 failed 1 skipped 0 warnings 0 tag=vma05 stime=1568998082 dur=0 exit=exited stat=1 core=no cu=23 cs=4 startup='Fri Sep 20 16:48:02 2019' vma05 1 TINFO: timeout per run is 0h 5m 0s vma05 1 TFAIL: [vsyscall] reporting wrong vma05 1 TPASS: [vdso] backtrace complete vma05 2 TINFO: AppArmor enabled, this may affect test results vma05 2 TINFO: it can be disabled with TST_DISABLE_APPARMOR=1 (requires super/root) vma05 2 TINFO: loaded AppArmor profiles: none Summary: passed 1 failed 1 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845863/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854689] Re: BlueZ 5.52 release
** Changed in: bluez (Ubuntu) Status: In Progress => Won't Fix ** Changed in: bluez (Ubuntu) Status: Won't Fix => Fix Committed -- 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/1854689 Title: BlueZ 5.52 release Status in bluez package in Ubuntu: Fix Committed Bug description: BlueZ 5.52 release: http://www.bluez.org/release-of-bluez-5-52/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1854689/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1766076] Re: USB over thunderbolt turns off every once in a while
The delay to connect the USB devices seems to be a feature of the new firmware or something - on MS-Windows it takes even longer, about 30 seconds for all the devices to finish connecting. Could it be that the xhci_hcd failure is caused by the fact that the dock is now so slow to respond? Anyway, that problem doesn't seem related to the "unknown event type 15" issue that this ticket is probably about, even though they both show "xHCI host not responding to stop endpoint command" - which is probably a symptom and not a cause. I'll be opening a new report for the thunderbolt connection issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1766076 Title: USB over thunderbolt turns off every once in a while Status in Dell Sputnik: New Status in linux package in Ubuntu: Incomplete Bug description: I'm using a USB hub in the Dell TB16 (240W) connected to a Dell Precision 5520 using Thunderbolt 3. Every so often (can be several times in an hour if I'm really unlucky, some days it is less of a problem), the USB hub disconnects from the computer and the devices connected to it lose power and stop responding. disconnecting and reconnecting the USB cables has no effect. I can restore functionality by instructing the xhci_hcd driver to unbind from the USB 3.0 Host Controller in the dock and to rebind to it using the commands: echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/unbind echo -n ":0e:00.0" > /sys/bus/pci/drivers/xhci_hcd/bind Here's the dmesg output when the USB hub disconnects: 279278.102701] xhci_hcd :0e:00.0: ERROR unknown event type 15 [279283.021802] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [279283.022145] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [279283.022161] r8152 4-1.2:1.0 enxd481d731b2b1: Tx status -108 [279283.022199] xhci_hcd :0e:00.0: HC died; cleaning up [279283.07] usb 3-1.5: Failed to suspend device, error -22 [279283.022234] usb 3-1: USB disconnect, device number 2 [279283.022235] usb 3-1.1: USB disconnect, device number 3 [279283.022236] usb 3-1.1.1: USB disconnect, device number 5 [279283.022237] usb 3-1.1.1.1: USB disconnect, device number 8 [279283.022238] usb 3-1.1.1.1.4: USB disconnect, device number 11 [279283.022326] usb 4-1: USB disconnect, device number 2 [279283.022328] usb 4-1.1: USB disconnect, device number 3 [279283.022329] usb 4-1.1.1: USB disconnect, device number 5 [279283.022998] usb 4-1.2: USB disconnect, device number 4 [279283.191217] usb 3-1.1.1.5: USB disconnect, device number 9 [279283.191730] usb 3-1.1.3: USB disconnect, device number 6 [279283.260810] usb 3-1.1.5: USB disconnect, device number 7 [279283.261350] usb 3-1.5: USB disconnect, device number 4 Here's dmesg output during the USB host controller reset: 279389.813889] xhci_hcd :0e:00.0: remove, state 1 [279389.813894] usb usb4: USB disconnect, device number 1 [279389.814103] xhci_hcd :0e:00.0: USB bus 4 deregistered [279389.814107] xhci_hcd :0e:00.0: remove, state 1 [279389.814110] usb usb3: USB disconnect, device number 1 [279389.881651] xhci_hcd :0e:00.0: USB bus 3 deregistered [279389.882133] xhci_hcd :0e:00.0: xHCI Host Controller [279389.882138] xhci_hcd :0e:00.0: new USB bus registered, assigned bus number 3 [279389.949391] xhci_hcd :0e:00.0: hcc params 0x0200e081 hci version 0x100 quirks 0x1410 [279389.949979] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002 [279389.949981] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[Kernel-packages] [Bug 1856163] Re: test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR
It looks like the test will trigger OOM, but the autotest gets killed this time. I tried with older 5.3.0-24 kernel, the test_maps passed one time, but the OOM error message can still be seen. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856163 Title: test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This issue can be reproduced with 5.3.0-24, so this is not a regression in this cycle. Reproduce rate: 3/3 On the s390x LPAR (s2lp4), the test_maps test from ubuntu_bpf will cause OOM and the following tests will be aborted. [ 591.755446] test_maps invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 [ 591.755451] CPU: 1 PID: 19054 Comm: test_maps Tainted: PW O 5.3.0-25-generic #27-Ubuntu [ 591.755452] Hardware name: IBM 2964 N63 400 (LPAR) [ 591.755453] Call Trace: [ 591.755460] ([<00023d11b98e>] show_stack+0x8e/0xd0) [ 591.755464] [<00023d995f6a>] dump_stack+0x8a/0xb8 [ 591.755469] [<00023d30e082>] dump_header+0x62/0x250 [ 591.755470] [<00023d30d152>] oom_kill_process+0x172/0x178 [ 591.755472] [<00023d30d322>] out_of_memory.part.0+0x1ca/0x4e0 [ 591.755473] [<00023d30df1e>] out_of_memory+0x6e/0xf8 [ 591.755477] [<00023d36af02>] __alloc_pages_slowpath+0xda2/0xeb0 [ 591.755478] [<00023d36b2b6>] __alloc_pages_nodemask+0x2a6/0x318 [ 591.755481] [<00023d387d6c>] alloc_pages_vma+0x104/0x1d8 [ 591.755482] [<00023d372ca4>] __read_swap_cache_async+0x18c/0x268 [ 591.755483] [<00023d372daa>] read_swap_cache_async+0x2a/0x60 [ 591.755485] [<00023d37300c>] swap_cluster_readahead+0x22c/0x2e8 [ 591.755486] [<00023d3734f8>] swapin_readahead+0x2d0/0x408 [ 591.755488] [<00023d34a14c>] do_swap_page+0x1f4/0x880 [ 591.755489] [<00023d34bf2c>] __handle_mm_fault+0x7f4/0x910 [ 591.755491] [<00023d34c10e>] handle_mm_fault+0xc6/0x1a0 [ 591.755492] [<00023d12c2bc>] do_exception+0x12c/0x3e0 [ 591.755494] [<00023d12d122>] do_dat_exception+0x2a/0x58 [ 591.755497] [<00023d9b67f0>] pgm_check_handler+0x1cc/0x220 [ 591.755497] Mem-Info: [ 591.755501] active_anon:0 inactive_anon:33 isolated_anon:6 active_file:59 inactive_file:93 isolated_file:3 unevictable:6786 dirty:0 writeback:2 unstable:0 slab_reclaimable:27072 slab_unreclaimable:44918 mapped:3670 shmem:0 pagetables:12555 bounce:0 free:19327 free_pcp:356 free_cma:0 [ 591.755505] Node 0 active_anon:0kB inactive_anon:132kB active_file:236kB inactive_file:372kB unevictable:27144kB isolated(anon):24kB isolated(file):12kB mapped:14680kB dirty:0kB writeback:8kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no [ 591.755505] Node 0 DMA free:57800kB min:2876kB low:4944kB high:7012kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:2097152kB managed:2097056kB mlocked:0kB kernel_stack:496kB pagetables:4964kB bounce:0kB free_pcp:620kB local_pcp:248kB free_cma:0kB [ 591.755509] lowmem_reserve[]: 0 13806 13806 [ 591.755511] Node 0 Normal free:19508kB min:19648kB low:33784kB high:47920kB active_anon:0kB inactive_anon:132kB active_file:0kB inactive_file:576kB unevictable:27144kB writepending:8kB present:14680064kB managed:14141200kB mlocked:27144kB kernel_stack:25040kB pagetables:45256kB bounce:0kB free_pcp:804kB local_pcp:120kB free_cma:0kB [ 591.755515] lowmem_reserve[]: 0 0 0 [ 591.755516] Node 0 DMA: 1*4kB (M) 5*8kB (UME) 6*16kB (UME) 2*32kB (M) 4*64kB (UME) 4*128kB (ME) 5*256kB (UME) 4*512kB (ME) 52*1024kB (UM) = 57548kB [ 591.755525] Node 0 Normal: 244*4kB (UME) 198*8kB (UMEH) 94*16kB (UMEH) 149*32kB (MEH) 31*64kB (UME) 10*128kB (UMEH) 2*256kB (MH) 2*512kB (MH) 5*1024kB (UM) = 18752kB [ 591.755534] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1024kB [ 591.755535] 3724 total pagecache pages [ 591.755536] 74 pages in swap cache [ 591.755537] Swap cache stats: add 98390, delete 98316, find 11531/42289 [ 591.755538] Free swap = 935816kB [ 591.755538] Total swap = 1001096kB [ 591.755539] 4194304 pages RAM [ 591.755540] 0 pages HighMem/MovableOnly [ 591.755540] 134740 pages reserved [ 591.755541] 0 pages cma reserved [ 591.755542] Unreclaimable slab info: [ 591.755542] Name Used Total [ 591.755614] nf_conntrack 128KB128KB [ 591.755680] abd_t 3KB 3KB [ 591.755682] zio_data_buf_16384 64KB
[Kernel-packages] [Bug 1856161] Re: Thunderbolt dock fails to connect USB devices
apport information ** Tags added: apport-collected ** Description changed: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId: d83854e8c81f5d47b0b99c8a3b42ae5127c75eb8 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: c0f73159-4fc0-509b-80f8-5f871f3751a8 Guid: be025b25-ca5c-546c-97c6-ee2160ba489d Guid: 190e8d7c-6bcf-5fab-94e7-4f8739eb90aa Summary:
[Kernel-packages] [Bug 1855900] Re: touchPad not detected
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 Seems a duplicate of bug 1854798. Please try bionic kernel 4.15.0-73 from the proposed channel. ** This bug has been marked a duplicate of bug 1854798 Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-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/1855900 Title: touchPad not detected Status in linux package in Ubuntu: Confirmed Bug description: The touchpad on lenovo x1 carbon 6th gen in not detected anymore after I updated the packages. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855900/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854547] Re: 【sas-1130】scsi: sd: define variable dif as unsigned int instead of bool
In focal-proposed too. ** Changed in: linux (Ubuntu Focal) Status: Confirmed => 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/1854547 Title: 【sas-1130】scsi: sd: define variable dif as unsigned int instead of bool Status in kunpeng920: Fix Committed Status in kunpeng920 ubuntu-18.04 series: Invalid Status in kunpeng920 ubuntu-18.04-hwe series: Fix Committed Status in kunpeng920 ubuntu-19.04 series: Invalid Status in kunpeng920 ubuntu-19.10 series: Fix Committed Status in kunpeng920 ubuntu-20.04 series: Fix Committed Status in kunpeng920 upstream-kernel series: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Eoan: Fix Committed Status in linux source package in Focal: Fix Committed Bug description: [Bug Description] DIF3 WILL not work when run fio test 【Steps to Reproduce] 1. Enable DIF/DIX for DIF3 disk 2. fio test [Actual Results] IO error when running IO; [ 781.032816] sd 5:0:0:0: [sdd] Disabling DIF Type 3 protection [ 781.112250] sd 5:0:0:0: [sdd] tag#72 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.112287] sd 5:0:0:0: [sdd] tag#72 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.112305] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.118429] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.204243] sd 5:0:0:0: [sdd] tag#77 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.204252] sd 5:0:0:0: [sdd] tag#77 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.204257] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.210365] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.296238] sd 5:0:0:0: [sdd] tag#82 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.296266] sd 5:0:0:0: [sdd] tag#82 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.296276] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.302384] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.309207] ldm_validate_partition_table(): Disk read failed. [ 781.392239] sd 5:0:0:0: [sdd] tag#87 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.392267] sd 5:0:0:0: [sdd] tag#87 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.392278] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.398386] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.484250] sd 5:0:0:0: [sdd] tag#92 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.484260] sd 5:0:0:0: [sdd] tag#92 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.484264] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.490371] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.576249] sd 5:0:0:0: [sdd] tag#97 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.576278] sd 5:0:0:0: [sdd] tag#97 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.576293] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.582399] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.668236] sd 5:0:0:0: [sdd] tag#102 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.668245] sd 5:0:0:0: [sdd] tag#102 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.668249] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.674354] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.681184] Dev sdd: unable to read RDB block 0 [ 781.764241] sd 5:0:0:0: [sdd] tag#121 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.764267] sd 5:0:0:0: [sdd] tag#121 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.764278] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.770386] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.856240] sd 5:0:0:0: [sdd] tag#126 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.856248] sd 5:0:0:0: [sdd] tag#126 CDB: Read(10) 28 00 00 00 00 00 00 00 08 00 [ 781.856253] print_req_error: I/O error, dev sdd, sector 0 flags 0 [ 781.862362] Buffer I/O error on dev sdd, logical block 0, async page read [ 781.948238] sd 5:0:0:0: [sdd] tag#131 FAILED Result: hostbyte=DID_ERROR driverbyte=DRIVER_OK [ 781.948264] sd 5:0:0:0: [sdd] tag#131 CDB: Read(10) 28 00 00 00 00 18 00 00 08 00 [ 781.948272] print_req_error: I/O error, dev sdd, sector 24 flags 0 [ 781.954467] Buffer I/O error on dev sdd, logical block 3, async page read [ 782.120252] sdd: unable to read partition table [Expected Results] IO running normally [Reproducibility] occasionally [Additional information] Hardware: D06 CS Firmware: NA+I59 Kernel: NA [Resolution] Variable dif in function sd_setup_read_write_cmnd() is the return value of function scsi_host_dif_capable() which returns dif
[Kernel-packages] [Bug 1848883] Re: (Lenovo S130-11IGM) emmc not working in 19.04
Here is an updated patch without the dependency on #include If it doesn't work, please provide kernel messages. ** Patch removed: "0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+attachment/5311741/+files/0001-mmc-sdhci-pci-Fix-premature-clock-gating-of-CQHCI-on.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848883 Title: (Lenovo S130-11IGM) emmc not working in 19.04 Status in linux package in Ubuntu: Confirmed Bug description: Hi, I don't think this is the same issue as ; https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1818407 although I have read a lot of issues with emmc disks. Booting from lubuntu CD1 19.04 takes about an hour before I get to the desktop. The installer runs through to the partitioning sections and is able to see the disk, but it fails to create the partitions. The laptop has a 32gb emmc disk. There is some kind of timeout during boot on the dhpci probe. The only OS/kernel match I have got to work on this device is Lubuntu/18.04 4.15.0-20 (every single function works). After installing 18.04 there is an auto update to 4.15.0-65 but the touchpad stops working so I defaulted grub back to -20 (this failure is not caused by libinput or synaptics drivers). Neither kernels have a working wifi module but rtl8821ce install fixes this so not an issue for me. Attaching as many logs as I can grab.. please let me know and I'll happily get any other requested logging. --- ProblemType: Bug ApportVersion: 2.20.10-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: lubuntu1434 F pulseaudio CasperVersion: 1.405 DistroRelease: Ubuntu 19.04 IwConfig: enp0s21f0u1 no wireless extensions. lono wireless extensions. LiveMediaBuild: Lubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81J1 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=C.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/casper/vmlinuz file=/cdrom/preseed/hostname.seed boot=casper quiet splash --- ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-13-generic N/A linux-backports-modules-5.0.0-13-generic N/A linux-firmware1.178 Tags: disco Uname: Linux 5.0.0-13-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True dmi.bios.date: 09/05/2019 dmi.bios.vendor: LENOVO dmi.bios.version: 9HCN27WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32802WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo ideapad S130-11IGM dmi.modalias: dmi:bvnLENOVO:bvr9HCN27WW:bd09/05/2019:svnLENOVO:pn81J1:pvrLenovoideapadS130-11IGM:rvnLENOVO:rnLNVNB161216:rvrSDK0R32802WIN:cvnLENOVO:ct10:cvrLenovoideapadS130-11IGM: dmi.product.family: ideapad S130-11IGM dmi.product.name: 81J1 dmi.product.sku: LENOVO_MT_81J1_BU_idea_FM_ideapad S130-11IGM dmi.product.version: Lenovo ideapad S130-11IGM dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848883/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852386] Re: no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026
Verified 5.3.0-25-generic/eoan-proposed. ** Tags removed: verification-needed-eoan ** Tags added: verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852386 Title: no HDMI video output since GDM greeter after linux-oem-osp1 version 5.0.0-1026 Status in HWE Next: New Status in linux package in Ubuntu: In Progress Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: Fix Released Status in linux source package in Eoan: Fix Committed Status in linux-oem-osp1 source package in Eoan: Fix Released Status in linux source package in Focal: In Progress Status in linux-oem-osp1 source package in Focal: Invalid Bug description: [SRU Justification: oem-osp1-bionic] [Impact] Bug 1849278 introduced a regression on some Comet Lake platforms that device may have no video output on HDMI port. [Fix] A currently in-review patch https://patchwork.freedesktop.org/patch/340416 should be applied to correct PCH's identity and restore HDMI output. [Test Case] 1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic kernels. 2. Boot affected platforms with HDMI cable connected to an external monitor. 3. Check if the monitor lights up when GDM service is started. This was verified in to victim platforms. [Regression Risk] Low. This should affects only systems with matching PCH hw that is currently affected by the regression to be fixed. == [SRU Justification: E/F/U] [Impact] Some Comet Lake platforms got i915 call trace dump due to the lake of support to its PCH id: [2.999233] [ cut here ] [2.999238] eDP powered off while attempting aux channel communication. [2.999338] WARNING: CPU: 2 PID: 296 at drivers/gpu/drm/i915/display/intel_dp.c:1148 intel_dp_aux_xfer+0x767/0x900 [i915] [2.999341] Modules linked in: i915(+) i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops drm r8169 ahci realtek libahci wmi video [2.999350] CPU: 2 PID: 296 Comm: systemd-udevd Not tainted 5.3.0-997-generic #201910072204 [2.999352] Hardware name: Dell Inc. OptiPlex 3280 AIO/, BIOS 99.00.08 10/01/2019 [2.999391] RIP: 0010:intel_dp_aux_xfer+0x767/0x900 [i915] [2.999394] Code: e8 ee b5 ff ff 84 c0 0f 85 ec f9 ff ff 48 8b 7d 80 e8 5d b6 ff ff 84 c0 0f 85 db f9 ff ff 48 c7 c7 50 22 5d c0 e8 84 ea b5 d1 <0f> 0b 48 8b 7d 80 48 8d 75 90 4c 8d ab a8 07 00 00 e8 63 b4 ff ff [2.999398] RSP: 0018:b740b5b8 EFLAGS: 00010286 [2.999400] RAX: RBX: 9bfa9dc2 RCX: 0396 [2.999402] RDX: 0001 RSI: 0082 RDI: 0246 [2.999404] RBP: b740b698 R08: 0396 R09: 0019 [2.999406] R10: 072e R11: b740b420 R12: 0004 [2.999408] R13: 9bfa9fbca120 R14: 9bfa9dc2 R15: 9bfa9dc207a8 [2.999410] FS: 7f0d8613a680() GS:9bfaaec8() knlGS: [2.999412] CS: 0010 DS: ES: CR0: 80050033 [2.999414] CR2: 7ffca955ae58 CR3: 00041e67e002 CR4: 003606e0 [2.999416] DR0: DR1: DR2: [2.999418] DR3: DR6: fffe0ff0 DR7: 0400 [2.999420] Call Trace: [2.999425] ? vprintk_default+0x29/0x50 [2.999464] intel_dp_aux_transfer+0x15e/0x220 [i915] [2.999472] drm_dp_dpcd_access+0x72/0x110 [drm_kms_helper] [2.999478] drm_dp_dpcd_read+0x33/0xc0 [drm_kms_helper] [2.999515] intel_dp_read_dpcd+0x41/0x130 [i915] [2.999551] intel_edp_init_connector+0x136/0x540 [i915] [2.999587] intel_dp_init_connector+0x47f/0x870 [i915] [2.999623] intel_ddi_init+0x425/0x590 [i915] [2.999660] intel_setup_outputs+0x8e4/0xc60 [i915] [Fix] Two patches to be backported to have correct support: * commit 37c92dc303dd "drm/i915: Add new CNL PCH ID seen on a CML platform" from drm-tip tree. * patch "https://patchwork.freedesktop.org/patch/340416; [Test Case] 1. Apply the patches to oem-osp1 kernel >= 1026 or Eoan/Focal generic kernels. 2. Boot affected platforms with HDMI cable connected to an external monitor. 3. Check if the monitor lights up when GDM service is started. This was verified in to victim platforms. [Regression Risk] Low. This should affects only systems with matching PCH hw that is currently affected by the regression to be fixed. == original bug description == This is a
[Kernel-packages] [Bug 1845620] Re: stime01 from ubuntu_ltp_syscalls failed on D Power9
Can be found on Eoan generic (5.3.0-25.27) P9 as well. This issue was not spotted on Eoan P8. ** Tags added: sru-20191202 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845620 Title: stime01 from ubuntu_ltp_syscalls failed on D Power9 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: This failure can only be found on Disco Power9, passed on other arches. Probably a glitch that similar to the hwclock test failure (bug 1802233) tag=stime01 stime=1568943645 dur=-22 exit=exited stat=1 core=no cu=0 cs=0 startup='Fri Sep 20 01:40:45 2019' tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s stime_var.h:45: INFO: Testing libc stime() stime01.c:46: INFO: pt.tv_sec: 1568943675 stime01.c:47: PASS: system time was set to 1568943675 tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s stime_var.h:48: INFO: Testing SYS_stime syscall stime01.c:51: FAIL: system time not set to 1568943705 (got: 1568943660) tst_test.c:1118: INFO: Timeout per run is 0h 05m 00s stime_var.h:51: INFO: Testing SYS_settimeofday syscall stime01.c:46: INFO: pt.tv_sec: 1568943690 stime01.c:47: PASS: system time was set to 1568943690 Summary: passed 2 failed 1 skipped 0 warnings 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845620/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856161] [NEW] Thunderbolt dock fails to connect USB devices
Public bug reported: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId: d83854e8c81f5d47b0b99c8a3b42ae5127c75eb8 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: c0f73159-4fc0-509b-80f8-5f871f3751a8 Guid: be025b25-ca5c-546c-97c6-ee2160ba489d Guid: 190e8d7c-6bcf-5fab-94e7-4f8739eb90aa Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created:
[Kernel-packages] [Bug 1855999] Re: alsa/hda/realtek: the line-out jack doens't work on a dell AIO
** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855999 Title: alsa/hda/realtek: the line-out jack doens't work on a dell AIO Status in HWE Next: New Status in linux package in Ubuntu: Triaged Bug description: [Impact] This is from an OEM bug, the line-out jack doesn't work on a Dell AIO machine. [Fix] apply the fixup ALC274_FIXUP_DELL_AIO_LINEOUT_VERB, and make the matching more generic. [Test Case] Booting the kernel with this patch, the line-out jack worked well. [Regression Risk] Low, just apply an existing fixup to a specific machine (dell with alc274 codec, and the pin 0x19 and 0x1a has the 0x4000 configuration). To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1855999/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856077] Re: Fix latency issue on Realtek Bluetooth
** Tags added: oem-priority originate-from-185 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1856077 Title: Fix latency issue on Realtek Bluetooth Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: New Bug description: [Impact] When multiple Bluetooth devices are connected to Realtek Bluetooth controller, the BT latency becomes really high, e.g. audio stutters, mouse lags. [Fix] The new Realtek Bluetooth firmware can fix the issue. [Test] Cold boot the system to reload the new firmware, and the issue is gone. [Regression Potential] Low. The firmware is already in Eoan. We also tested it on Bionic and haven't found any regression so far. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1856077/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848790] Re: USB not working under arm64 on Pi4 with 4G ram
(Does a dist-upgrade go from 19.10 to 19.10.1 or do I need to do a reinstall?) -- 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/1848790 Title: USB not working under arm64 on Pi4 with 4G ram Status in linux-raspi2 package in Ubuntu: Fix Released Status in linux-raspi2 source package in Eoan: Fix Released Bug description: Ubuntu 19.10 arm64 on a Raspberry Pi 4 does not recognize a keyboard which works successfully on the same Raspberry Pi 4 with Ubuntu 19.10 armhf. Both USB hubs (2 and 3) were tested, without the OS seeing the keyboard on either. Booting the arm64 image on a Raspberry Pi 3, the keyboard worked successfully. Output of lsusb under arm64 on a Pi 3: ubuntu@ubuntu:~$ lsusb Bus 001 Device 007: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 003: ID 0424:ec00 Standard Microsystems Corp. SMSC9512/9514 Fast Ethernet Adapter Bus 001 Device 002: ID 0424:9514 Standard Microsystems Corp. SMC9514 Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under armhf on a Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 413c:2106 Dell Computer Corp. Dell QuietKey Keyboard Bus 001 Device 002: ID 2109:3431 VIA Labs, Inc. Hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Output of lsusb under arm64 on the same Pi 4 (same keyboard attached): ubuntu@ubuntu:~$ lsusb Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub The fact even the VIA Labs hub doesn't show up (which is built in) suggests the kernel is (for some reason) unable to enumerate anything against the USB hubs. == Temporary Workaround == As noted by various people below, the following line can be added to the "usercfg.txt" file on the boot partition: total_mem=3072 This will limit the available RAM to 3Gb, but otherwise things should operate normally. Note that this bug does not affect Pi 4Bs with less than 4Gb of RAM. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1848790/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856161] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311955/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311953/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311952/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock
[Kernel-packages] [Bug 1856161] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311951/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1856161] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1856161/+attachment/5311954/+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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: New Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
@Wayne, TL;dr: simply remove backport-iwlwifi-dkms on your Eoan system with Intel AC 9260 installed. First, "the entire system will freeze" is to be resolved in bug 1855825, which will fix backport-iwlwifi-dkms in Eoan/Focal for generic Ubuntu, and Bionic for OEM projects. Eventually generic Bionic will have the fix in bug 1856024. Second, the association failure problem when backport-iwlwifi-dkms is installed is currently a known issue in my list. Probably there is already a bug for it, takes some time to filter they out. TBD. At last, this (1855637/1855825) issue is caused by a mainline patch backported to stable kernels, which modifies data structure layout, and while DKMS packages may carry a copy of kernel headers that it uses, such different data layout may cause unexpected behaviors, and in this case, it hangs your system. Ubuntu kernels will merge stable patches, so all Ubuntu kernels with this patch included are affected. So it follows, if you're running a slightly older kernel, it will be fine; if you don't use backport-iwlwifi-dkms, it will be fine, too. DKMS is created to include features/fixes that are not currently in generic kernel "at the time". So it's not always "newer" than generic 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/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Confirmed Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855952] Re: scsi: hisi_sas: Check sas_port before using it
Patch is sent for Eoan. https://lists.ubuntu.com/archives/kernel-team/2019-December/106340.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855952 Title: scsi: hisi_sas: Check sas_port before using it Status in kunpeng920: Triaged Status in kunpeng920 ubuntu-18.04 series: Triaged Status in kunpeng920 ubuntu-18.04-hwe series: Triaged Status in kunpeng920 ubuntu-19.04 series: Triaged Status in kunpeng920 ubuntu-19.10 series: Triaged Status in kunpeng920 ubuntu-20.04 series: In Progress Status in kunpeng920 upstream-kernel series: Fix Committed Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Triaged Status in linux source package in Disco: Triaged Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: [Impact] Potential NULL-pointer dereference. [Test Case] No known test case, but the issue is clear from code reading. [Fix] 8c39673d5474b scsi: hisi_sas: Check sas_port before using it [Regression Risk] Patch restricted to hisi_sas driver. To manage notifications about this bug go to: https://bugs.launchpad.net/kunpeng920/+bug/1855952/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856079] Re: Fix Realtek Bluetooth firmware download
** Changed in: linux-oem-osp1 (Ubuntu) Status: New => Invalid ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856079 Title: Fix Realtek Bluetooth firmware download Status in HWE Next: New Status in linux package in Ubuntu: Triaged Status in linux-oem-osp1 package in Ubuntu: Invalid Status in linux source package in Bionic: Won't Fix Status in linux-oem-osp1 source package in Bionic: New Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Won't Fix Bug description: [Impact] Realtek Bluetooth controller failed to download firmware larger than 32K. [Fix] Update btrtl firmware downloading logic to match the hardware behavior. [Test] Several cold boots to force load firmware, and it never fails after the fix. [Regression Potential] Low. It's a trivial fix and we've verified it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1856079/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856161] 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/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Confirmed Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid: 0a52c8c7-26d5-59a0-ae44-6b00e276d775 Guid: 51000744-2de6-5a52-8a86-d5f69fd73d34 Summary: Multi-Stream Transport Device Plugin: synapticsmst Flags:updatable|registered Vendor: Synaptics Version: 3.10.002 VersionFormat:triplet Icon: computer Created: 2019-12-12 Synaptics VMM3330 inside Dell WD15/TB16/TB18 wired Dock DeviceId:
[Kernel-packages] [Bug 1854798] Re: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic
Same problem here. Trackpad Synaptics TM3066-002 stopped working in Lenovo Yoga 900-13ISK after upgrade to kernel 4.15.0-72. When restarting with kernel 4.15.0-70 it works. I am eagerly waiting for the kernel update that is going to solve this problem! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854798 Title: Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Bug description: SRU justification = [Impact] Synaptics s3203 touchpad not working after update to kernel 4.15.0-72-generic [Fix] After applied commit "Input: synaptics-rmi4 - avoid processing unknown IRQs", no irq response from touchpad. This commit is depended on commit: "Input: synaptics-rmi4 - convert irq distribution to irq_domain" [Test] Verified on hardware, tests results are good. [Regression Potential] Low. Fix bug that introduced by stable release update. 2nd and 3rd patches are fixes for the 1st patch. These commits are already included by eoan kernel, so bionic 4.15 only. Original reports === environment: Dell Laptop XPS-9333 Device: # xinput --list ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ SYNAPTICS Synaptics Large Touch Screen id=9[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=12 [slave pointer (2)] ⎜ ↳ Ultrathin Touch Mouse id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Dell WMI hotkeysid=13 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=14 [slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ DELL Wireless hotkeys id=15 [slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] # xinput --list-props 12 Device 'Synaptics s3203': Device Enabled (142):1 Coordinate Transformation Matrix (144): 1.00, 0.00, 0.00, 0.00, 1.00, 0.00, 0.00, 0.00, 1.00 Device Accel Profile (270): 1 Device Accel Constant Deceleration (271):2.50 Device Accel Adaptive Deceleration (272):1.00 Device Accel Velocity Scaling (273): 9.712231 Synaptics Edges (304): 162, 3908, 133, 2339 Synaptics Finger (305): 25, 30, 0 Synaptics Tap Time (306):180 Synaptics Tap Move (307):209 Synaptics Tap Durations (308): 180, 180, 100 Synaptics ClickPad (309):1 Synaptics Middle Button Timeout (310): 0 Synaptics Two-Finger Pressure (311): 282 Synaptics Two-Finger Width (312):7 Synaptics Scrolling Distance (313): -95, 95 Synaptics Edge Scrolling (314): 0, 0, 0 Synaptics Two-Finger Scrolling (315):1, 1 Synaptics Move Speed (316): 1.00, 1.75, 0.042008, 0.00 Synaptics Off (317): 0 Synaptics Locked Drags (318):0 Synaptics Locked Drags Timeout (319):5000 Synaptics Tap Action (320): 0, 0, 0, 0, 1, 3, 2 Synaptics Click Action (321):1, 3, 2 Synaptics Circular Scrolling (322): 0 Synaptics Circular Scrolling Distance (323): 0.10 Synaptics Circular Scrolling Trigger (324): 0 Synaptics Circular Pad (325):0 Synaptics Palm Detection (326): 1 Synaptics Palm Dimensions (327): 10, 200 Synaptics Coasting Speed (328): 20.00, 50.00 Synaptics Pressure Motion (329): 30, 160 Synaptics Pressure Motion Factor (330): 1.00, 1.00 Synaptics Resolution Detect (331): 1 Synaptics Grab Event Device (332): 0 Synaptics Gestures (333):1 Synaptics Capabilities (334):1, 0, 0, 1, 1, 1, 0 Synaptics Pad Resolution (335): 42, 42 Synaptics Area (336):0, 0, 0, 0 Synaptics Soft Button Areas (337): 0, 0, 0, 0, 0, 0, 0, 0 Synaptics Noise Cancellation (338): 23, 23 Device Product ID (262): 1739, 10036 Device Node (263): "/dev/input/event5" # lspci 00:00.0 Host bridge: Intel Corporation Haswell-ULT DRAM Controller (rev 09) 00:02.0 VGA compatible controller: Intel Corporation Haswell-ULT Integrated Graphics Controller (rev 09) 00:03.0 Audio
[Kernel-packages] [Bug 1836167] Re: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes
Found on Eoan (5.3.0-25.27) with P8 node modoc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836167 Title: cpuhotplug03 in cpuhotplug from ubuntu_ltp failed on some testing nodes Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Disco: New Bug description: <<>> incrementing stop Name: cpuhotplug03 Date: Thu Jul 11 08:31:48 UTC 2019 Desc: Do tasks get scheduled to a newly on-lined CPU? CPU is 1 sh: echo: I/O error cpuhotplug03 1 TBROK: CPU1 cannot be offlined USER PID %CPU %MEMVSZ RSS TTY STAT START TIME COMMAND root 4642 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4643 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4644 0.0 0.0 2020 468 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4645 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4646 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4647 0.0 0.0 2020 480 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4648 0.0 0.0 2020 456 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4649 0.0 0.0 2020 508 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4650 0.0 0.0 2020 488 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4651 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4652 0.0 0.0 2020 484 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4653 0.0 0.0 2020 496 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4654 0.0 0.0 2020 464 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4655 0.0 0.0 2020 492 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4656 0.0 0.0 2020 448 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4657 0.0 0.0 2020 472 pts/0R08:31 0:00 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop root 4661 0.0 0.0 7540 648 pts/0S08:31 0:00 grep cpuhotplug_do_spin_loop cpuhotplug03 1 TINFO: Onlining CPU 1 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 1 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 3 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 7 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 6 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 4 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 2 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 0 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop 5 /bin/sh /opt/ltp/testcases/bin/cpuhotplug_do_spin_loop cpuhotplug03 1 TPASS: 2 cpuhotplug_do_spin_loop processes found onCPU1 <<>> initiation_status="ok" duration=1 termination_type=exited termination_id=2 corefile=no cutime=1060 cstime=9 <<>> Test passed on ThunderX ARM64, probably a test case issue. Steps to run this test: git clone --depth=1 https://github.com/linux-test-project/ltp.git cd ltp; make autotools; ./configure; make; sudo make install echo "cpuhotplug03 cpuhotplug03.sh -c 1 -l 1" > /tmp/jobs sudo /opt/ltp/runltp -f /tmp/jobs ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-25-generic 4.18.0-25.26 ProcVersionSignature: User Name 4.18.0-25.26-generic 4.18.20 Uname: Linux 4.18.0-25-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 11 06:57 seq crw-rw 1 root audio 116, 33 Jul 11 06:57 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu13.4 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq',
[Kernel-packages] [Bug 1856163] [NEW] test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR
Public bug reported: This issue can be reproduced with 5.3.0-24, so this is not a regression in this cycle. Reproduce rate: 3/3 On the s390x LPAR (s2lp4), the test_maps test from ubuntu_bpf will cause OOM and the following tests will be aborted. [ 591.755446] test_maps invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 [ 591.755451] CPU: 1 PID: 19054 Comm: test_maps Tainted: PW O 5.3.0-25-generic #27-Ubuntu [ 591.755452] Hardware name: IBM 2964 N63 400 (LPAR) [ 591.755453] Call Trace: [ 591.755460] ([<00023d11b98e>] show_stack+0x8e/0xd0) [ 591.755464] [<00023d995f6a>] dump_stack+0x8a/0xb8 [ 591.755469] [<00023d30e082>] dump_header+0x62/0x250 [ 591.755470] [<00023d30d152>] oom_kill_process+0x172/0x178 [ 591.755472] [<00023d30d322>] out_of_memory.part.0+0x1ca/0x4e0 [ 591.755473] [<00023d30df1e>] out_of_memory+0x6e/0xf8 [ 591.755477] [<00023d36af02>] __alloc_pages_slowpath+0xda2/0xeb0 [ 591.755478] [<00023d36b2b6>] __alloc_pages_nodemask+0x2a6/0x318 [ 591.755481] [<00023d387d6c>] alloc_pages_vma+0x104/0x1d8 [ 591.755482] [<00023d372ca4>] __read_swap_cache_async+0x18c/0x268 [ 591.755483] [<00023d372daa>] read_swap_cache_async+0x2a/0x60 [ 591.755485] [<00023d37300c>] swap_cluster_readahead+0x22c/0x2e8 [ 591.755486] [<00023d3734f8>] swapin_readahead+0x2d0/0x408 [ 591.755488] [<00023d34a14c>] do_swap_page+0x1f4/0x880 [ 591.755489] [<00023d34bf2c>] __handle_mm_fault+0x7f4/0x910 [ 591.755491] [<00023d34c10e>] handle_mm_fault+0xc6/0x1a0 [ 591.755492] [<00023d12c2bc>] do_exception+0x12c/0x3e0 [ 591.755494] [<00023d12d122>] do_dat_exception+0x2a/0x58 [ 591.755497] [<00023d9b67f0>] pgm_check_handler+0x1cc/0x220 [ 591.755497] Mem-Info: [ 591.755501] active_anon:0 inactive_anon:33 isolated_anon:6 active_file:59 inactive_file:93 isolated_file:3 unevictable:6786 dirty:0 writeback:2 unstable:0 slab_reclaimable:27072 slab_unreclaimable:44918 mapped:3670 shmem:0 pagetables:12555 bounce:0 free:19327 free_pcp:356 free_cma:0 [ 591.755505] Node 0 active_anon:0kB inactive_anon:132kB active_file:236kB inactive_file:372kB unevictable:27144kB isolated(anon):24kB isolated(file):12kB mapped:14680kB dirty:0kB writeback:8kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no [ 591.755505] Node 0 DMA free:57800kB min:2876kB low:4944kB high:7012kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:2097152kB managed:2097056kB mlocked:0kB kernel_stack:496kB pagetables:4964kB bounce:0kB free_pcp:620kB local_pcp:248kB free_cma:0kB [ 591.755509] lowmem_reserve[]: 0 13806 13806 [ 591.755511] Node 0 Normal free:19508kB min:19648kB low:33784kB high:47920kB active_anon:0kB inactive_anon:132kB active_file:0kB inactive_file:576kB unevictable:27144kB writepending:8kB present:14680064kB managed:14141200kB mlocked:27144kB kernel_stack:25040kB pagetables:45256kB bounce:0kB free_pcp:804kB local_pcp:120kB free_cma:0kB [ 591.755515] lowmem_reserve[]: 0 0 0 [ 591.755516] Node 0 DMA: 1*4kB (M) 5*8kB (UME) 6*16kB (UME) 2*32kB (M) 4*64kB (UME) 4*128kB (ME) 5*256kB (UME) 4*512kB (ME) 52*1024kB (UM) = 57548kB [ 591.755525] Node 0 Normal: 244*4kB (UME) 198*8kB (UMEH) 94*16kB (UMEH) 149*32kB (MEH) 31*64kB (UME) 10*128kB (UMEH) 2*256kB (MH) 2*512kB (MH) 5*1024kB (UM) = 18752kB [ 591.755534] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1024kB [ 591.755535] 3724 total pagecache pages [ 591.755536] 74 pages in swap cache [ 591.755537] Swap cache stats: add 98390, delete 98316, find 11531/42289 [ 591.755538] Free swap = 935816kB [ 591.755538] Total swap = 1001096kB [ 591.755539] 4194304 pages RAM [ 591.755540] 0 pages HighMem/MovableOnly [ 591.755540] 134740 pages reserved [ 591.755541] 0 pages cma reserved [ 591.755542] Unreclaimable slab info: [ 591.755542] Name Used Total [ 591.755614] nf_conntrack 128KB128KB [ 591.755680] abd_t 3KB 3KB [ 591.755682] zio_data_buf_16384 64KB 64KB [ 591.755683] zio_buf_16384 32KB 32KB [ 591.755695] mod_hash_entries 3KB 3KB [ 591.755697] spl_vn_file_cache 8KB 8KB [ 591.755699] spl_vn_cache 8KB 8KB [ 591.755740] scsi_sense_cache1592KB 1592KB [ 591.755741] qeth_buf 15KB 15KB [ 591.755743] qdio_q63KB 63KB [ 591.755746] RAWv6843KB 1000KB [ 591.755747] TCPv6 90KB 90KB [ 591.755749] mqueue_inode_cache 64KB 64KB [ 591.755750] fuse_request 47KB 47KB [ 591.755754] kioctx
[Kernel-packages] [Bug 1856161] 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 1856161 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: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856161 Title: Thunderbolt dock fails to connect USB devices Status in linux package in Ubuntu: Incomplete Bug description: Using Ubuntu eoan fully updated with kernel 5.3.0-24-generic on a Dell Precision 5520. When connecting a Dell Thunderbolt dock TB16, the USB bus connects very slowly (15~20 seconds) and sometimes does not connect at all and a failure is reported in dmesg: [ 117.834621] xhci_hcd :0e:00.0: xHCI host not responding to stop endpoint command. [ 117.850643] xhci_hcd :0e:00.0: Host halt failed, -110 [ 117.850644] xhci_hcd :0e:00.0: xHCI host controller not responding, assume dead [ 117.850679] xhci_hcd :0e:00.0: HC died; cleaning up [ 117.850717] xhci_hcd :0e:00.0: Timeout while waiting for configure endpoint command The slow connection seems to be a feature of the current updated firmware - the computer was not used for ~6 months due to a battery issue that was fixed, and after fixing the battery a new firmware was installed using the MS-Windows Dell software update utility. Both on Linux and MS-Windows the process of connecting the Thunderbolt dock completes after a much longer time than it used to in the beginning of the year. On the face of it it seems that the longer init process now hits timeouts in the xhci_hcd driver and depending on the exact timing often causes the xhci_hcd to give up and drop the USB Thunderbolt bus. This happens about 50% of the time, when connecting the Dock when the system is running, and a bit less when the system is booted or resumed from sleep when the dock is already connected. fwupdmgr report: -8<- Precision M5520 Thunderbolt Controller DeviceId: 51d36e5f8f25bea1d8707a72ab7b9386a98527ee Guid: c5364422-2ec3-5092-b30e-03bdb1a53e4a Summary: Unmatched performance for high-speed I/O Plugin: thunderbolt Flags:internal|updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 26.01 VersionFormat:pair Icon: computer Created: 2019-12-12 Dell Thunderbolt Cable DeviceId: aa4dfab63945b6e8ad913550d241978e3562f8bf ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: b4fd3cdf-4e3a-5090-a583-45367cfd6421 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Dell Thunderbolt Dock DeviceId: 64575ad9f31dbe3959942f4b2275c1c4d0ac2ac5 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 76cc74d4-f062-5b93-a11c-8d2a58a25848 Plugin: thunderbolt Flags:updatable|require-ac|registered Vendor: Dell VendorId: TBT:0x00D4 Version: 16.00 VersionFormat:pair Icon: audio-card Created: 2019-12-12 Precision 5520 System Firmware DeviceId: f4b6e3af5b4bf8ad1f2ed2922b76df457271 Guid: 34578c72-11dc-4378-bc7f-b643866f598c Plugin: uefi Flags: internal|updatable|require-ac|supported|registered|needs-reboot Checksum: SHA1(f5dfd993019fd1ab6bdcb718f13a27d6f77a9a90) Checksum: SHA256(a35b224919bebade597cfbce372a235c96cb4c5489738804aec117ed92e85717) Version: 0.1.16.0 VersionLowest:0.1.16.0 VersionFormat:quad Icon: computer Created: 2019-12-12 UpdateState: success Synaptics VMM3320 inside Dell WD15/TB16/TB18 wired Dock DeviceId: 7b3cbc344094ace839263dd4711c84ea99bb6dc3 ParentDeviceId: 84edf044a6b53037732cfc7591b65a8d36384cc9 Guid: 152a9833-41e6-5c21-9dde-0ff8984f3e20 Guid:
[Kernel-packages] [Bug 1856163] Status changed to Confirmed
This change was made by a bot. ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu Eoan) 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/1856163 Title: test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This issue can be reproduced with 5.3.0-24, so this is not a regression in this cycle. Reproduce rate: 3/3 On the s390x LPAR (s2lp4), the test_maps test from ubuntu_bpf will cause OOM and the following tests will be aborted. [ 591.755446] test_maps invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 [ 591.755451] CPU: 1 PID: 19054 Comm: test_maps Tainted: PW O 5.3.0-25-generic #27-Ubuntu [ 591.755452] Hardware name: IBM 2964 N63 400 (LPAR) [ 591.755453] Call Trace: [ 591.755460] ([<00023d11b98e>] show_stack+0x8e/0xd0) [ 591.755464] [<00023d995f6a>] dump_stack+0x8a/0xb8 [ 591.755469] [<00023d30e082>] dump_header+0x62/0x250 [ 591.755470] [<00023d30d152>] oom_kill_process+0x172/0x178 [ 591.755472] [<00023d30d322>] out_of_memory.part.0+0x1ca/0x4e0 [ 591.755473] [<00023d30df1e>] out_of_memory+0x6e/0xf8 [ 591.755477] [<00023d36af02>] __alloc_pages_slowpath+0xda2/0xeb0 [ 591.755478] [<00023d36b2b6>] __alloc_pages_nodemask+0x2a6/0x318 [ 591.755481] [<00023d387d6c>] alloc_pages_vma+0x104/0x1d8 [ 591.755482] [<00023d372ca4>] __read_swap_cache_async+0x18c/0x268 [ 591.755483] [<00023d372daa>] read_swap_cache_async+0x2a/0x60 [ 591.755485] [<00023d37300c>] swap_cluster_readahead+0x22c/0x2e8 [ 591.755486] [<00023d3734f8>] swapin_readahead+0x2d0/0x408 [ 591.755488] [<00023d34a14c>] do_swap_page+0x1f4/0x880 [ 591.755489] [<00023d34bf2c>] __handle_mm_fault+0x7f4/0x910 [ 591.755491] [<00023d34c10e>] handle_mm_fault+0xc6/0x1a0 [ 591.755492] [<00023d12c2bc>] do_exception+0x12c/0x3e0 [ 591.755494] [<00023d12d122>] do_dat_exception+0x2a/0x58 [ 591.755497] [<00023d9b67f0>] pgm_check_handler+0x1cc/0x220 [ 591.755497] Mem-Info: [ 591.755501] active_anon:0 inactive_anon:33 isolated_anon:6 active_file:59 inactive_file:93 isolated_file:3 unevictable:6786 dirty:0 writeback:2 unstable:0 slab_reclaimable:27072 slab_unreclaimable:44918 mapped:3670 shmem:0 pagetables:12555 bounce:0 free:19327 free_pcp:356 free_cma:0 [ 591.755505] Node 0 active_anon:0kB inactive_anon:132kB active_file:236kB inactive_file:372kB unevictable:27144kB isolated(anon):24kB isolated(file):12kB mapped:14680kB dirty:0kB writeback:8kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no [ 591.755505] Node 0 DMA free:57800kB min:2876kB low:4944kB high:7012kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:2097152kB managed:2097056kB mlocked:0kB kernel_stack:496kB pagetables:4964kB bounce:0kB free_pcp:620kB local_pcp:248kB free_cma:0kB [ 591.755509] lowmem_reserve[]: 0 13806 13806 [ 591.755511] Node 0 Normal free:19508kB min:19648kB low:33784kB high:47920kB active_anon:0kB inactive_anon:132kB active_file:0kB inactive_file:576kB unevictable:27144kB writepending:8kB present:14680064kB managed:14141200kB mlocked:27144kB kernel_stack:25040kB pagetables:45256kB bounce:0kB free_pcp:804kB local_pcp:120kB free_cma:0kB [ 591.755515] lowmem_reserve[]: 0 0 0 [ 591.755516] Node 0 DMA: 1*4kB (M) 5*8kB (UME) 6*16kB (UME) 2*32kB (M) 4*64kB (UME) 4*128kB (ME) 5*256kB (UME) 4*512kB (ME) 52*1024kB (UM) = 57548kB [ 591.755525] Node 0 Normal: 244*4kB (UME) 198*8kB (UMEH) 94*16kB (UMEH) 149*32kB (MEH) 31*64kB (UME) 10*128kB (UMEH) 2*256kB (MH) 2*512kB (MH) 5*1024kB (UM) = 18752kB [ 591.755534] Node 0 hugepages_total=0 hugepages_free=0 hugepages_surp=0 hugepages_size=1024kB [ 591.755535] 3724 total pagecache pages [ 591.755536] 74 pages in swap cache [ 591.755537] Swap cache stats: add 98390, delete 98316, find 11531/42289 [ 591.755538] Free swap = 935816kB [ 591.755538] Total swap = 1001096kB [ 591.755539] 4194304 pages RAM [ 591.755540] 0 pages HighMem/MovableOnly [ 591.755540] 134740 pages reserved [ 591.755541] 0 pages cma reserved [ 591.755542] Unreclaimable slab info: [ 591.755542] Name Used Total [ 591.755614] nf_conntrack 128KB128KB [ 591.755680] abd_t 3KB 3KB [ 591.755682] zio_data_buf_16384 64KB 64KB [ 591.755683]
[Kernel-packages] [Bug 1856163] Re: test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR
** Description changed: + This issue can be reproduced with 5.3.0-24, so this is not a regression + in this cycle. + Reproduce rate: 3/3 On the s390x LPAR (s2lp4), the test_maps test from ubuntu_bpf will cause OOM and the following tests will be aborted. [ 591.755446] test_maps invoked oom-killer: gfp_mask=0x100cca(GFP_HIGHUSER_MOVABLE), order=0, oom_score_adj=0 [ 591.755451] CPU: 1 PID: 19054 Comm: test_maps Tainted: PW O 5.3.0-25-generic #27-Ubuntu [ 591.755452] Hardware name: IBM 2964 N63 400 (LPAR) [ 591.755453] Call Trace: [ 591.755460] ([<00023d11b98e>] show_stack+0x8e/0xd0) - [ 591.755464] [<00023d995f6a>] dump_stack+0x8a/0xb8 - [ 591.755469] [<00023d30e082>] dump_header+0x62/0x250 - [ 591.755470] [<00023d30d152>] oom_kill_process+0x172/0x178 - [ 591.755472] [<00023d30d322>] out_of_memory.part.0+0x1ca/0x4e0 - [ 591.755473] [<00023d30df1e>] out_of_memory+0x6e/0xf8 - [ 591.755477] [<00023d36af02>] __alloc_pages_slowpath+0xda2/0xeb0 - [ 591.755478] [<00023d36b2b6>] __alloc_pages_nodemask+0x2a6/0x318 - [ 591.755481] [<00023d387d6c>] alloc_pages_vma+0x104/0x1d8 - [ 591.755482] [<00023d372ca4>] __read_swap_cache_async+0x18c/0x268 - [ 591.755483] [<00023d372daa>] read_swap_cache_async+0x2a/0x60 - [ 591.755485] [<00023d37300c>] swap_cluster_readahead+0x22c/0x2e8 - [ 591.755486] [<00023d3734f8>] swapin_readahead+0x2d0/0x408 - [ 591.755488] [<00023d34a14c>] do_swap_page+0x1f4/0x880 - [ 591.755489] [<00023d34bf2c>] __handle_mm_fault+0x7f4/0x910 - [ 591.755491] [<00023d34c10e>] handle_mm_fault+0xc6/0x1a0 - [ 591.755492] [<00023d12c2bc>] do_exception+0x12c/0x3e0 - [ 591.755494] [<00023d12d122>] do_dat_exception+0x2a/0x58 - [ 591.755497] [<00023d9b67f0>] pgm_check_handler+0x1cc/0x220 + [ 591.755464] [<00023d995f6a>] dump_stack+0x8a/0xb8 + [ 591.755469] [<00023d30e082>] dump_header+0x62/0x250 + [ 591.755470] [<00023d30d152>] oom_kill_process+0x172/0x178 + [ 591.755472] [<00023d30d322>] out_of_memory.part.0+0x1ca/0x4e0 + [ 591.755473] [<00023d30df1e>] out_of_memory+0x6e/0xf8 + [ 591.755477] [<00023d36af02>] __alloc_pages_slowpath+0xda2/0xeb0 + [ 591.755478] [<00023d36b2b6>] __alloc_pages_nodemask+0x2a6/0x318 + [ 591.755481] [<00023d387d6c>] alloc_pages_vma+0x104/0x1d8 + [ 591.755482] [<00023d372ca4>] __read_swap_cache_async+0x18c/0x268 + [ 591.755483] [<00023d372daa>] read_swap_cache_async+0x2a/0x60 + [ 591.755485] [<00023d37300c>] swap_cluster_readahead+0x22c/0x2e8 + [ 591.755486] [<00023d3734f8>] swapin_readahead+0x2d0/0x408 + [ 591.755488] [<00023d34a14c>] do_swap_page+0x1f4/0x880 + [ 591.755489] [<00023d34bf2c>] __handle_mm_fault+0x7f4/0x910 + [ 591.755491] [<00023d34c10e>] handle_mm_fault+0xc6/0x1a0 + [ 591.755492] [<00023d12c2bc>] do_exception+0x12c/0x3e0 + [ 591.755494] [<00023d12d122>] do_dat_exception+0x2a/0x58 + [ 591.755497] [<00023d9b67f0>] pgm_check_handler+0x1cc/0x220 [ 591.755497] Mem-Info: [ 591.755501] active_anon:0 inactive_anon:33 isolated_anon:6 - active_file:59 inactive_file:93 isolated_file:3 - unevictable:6786 dirty:0 writeback:2 unstable:0 - slab_reclaimable:27072 slab_unreclaimable:44918 - mapped:3670 shmem:0 pagetables:12555 bounce:0 - free:19327 free_pcp:356 free_cma:0 + active_file:59 inactive_file:93 isolated_file:3 + unevictable:6786 dirty:0 writeback:2 unstable:0 + slab_reclaimable:27072 slab_unreclaimable:44918 + mapped:3670 shmem:0 pagetables:12555 bounce:0 + free:19327 free_pcp:356 free_cma:0 [ 591.755505] Node 0 active_anon:0kB inactive_anon:132kB active_file:236kB inactive_file:372kB unevictable:27144kB isolated(anon):24kB isolated(file):12kB mapped:14680kB dirty:0kB writeback:8kB shmem:0kB shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 0kB writeback_tmp:0kB unstable:0kB all_unreclaimable? no [ 591.755505] Node 0 DMA free:57800kB min:2876kB low:4944kB high:7012kB active_anon:0kB inactive_anon:0kB active_file:0kB inactive_file:0kB unevictable:0kB writepending:0kB present:2097152kB managed:2097056kB mlocked:0kB kernel_stack:496kB pagetables:4964kB bounce:0kB free_pcp:620kB local_pcp:248kB free_cma:0kB [ 591.755509] lowmem_reserve[]: 0 13806 13806 [ 591.755511] Node 0 Normal free:19508kB min:19648kB low:33784kB high:47920kB active_anon:0kB inactive_anon:132kB active_file:0kB inactive_file:576kB unevictable:27144kB writepending:8kB present:14680064kB managed:14141200kB mlocked:27144kB kernel_stack:25040kB pagetables:45256kB bounce:0kB free_pcp:804kB local_pcp:120kB free_cma:0kB [ 591.755515] lowmem_reserve[]: 0 0 0 [ 591.755516] Node 0 DMA: 1*4kB (M) 5*8kB (UME) 6*16kB (UME) 2*32kB (M) 4*64kB (UME) 4*128kB (ME)
[Kernel-packages] [Bug 1856166] [NEW] NVS 5200M not supported by 435, but is recommended by ubuntu-drivers
Public bug reported: I have a Dell Laptop with a NVS 5200M (0DFC) and wondered why ubuntu- drivers recommend the nvidia-driver-435 (and also the wrong driver 430). It won't work with these drivers. $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd0DFCsv1028sd0535bc03sc00i00 vendor : NVIDIA Corporation model: GF108GLM [NVS 5200M] driver : nvidia-340 - distro non-free driver : nvidia-driver-435 - distro non-free recommended driver : nvidia-driver-430 - distro non-free driver : nvidia-driver-390 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 I found the modalias in the packages nvidia-driver-435 and also in the package of the nvidia-driver-430. In the Nvidia READMEs you can find that the NVS 5200M (0DFC) is only supported up to 390. I opened an issue on https://github.com/tseliot/nvidia-graphics- drivers/issues/36 and tseliot told me it could be a parsing problem of the Nvidia READMEs. ** Affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Also affects: nvidia-graphics-drivers-430 (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1856166 Title: NVS 5200M not supported by 435, but is recommended by ubuntu-drivers Status in nvidia-graphics-drivers-430 package in Ubuntu: New Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: I have a Dell Laptop with a NVS 5200M (0DFC) and wondered why ubuntu- drivers recommend the nvidia-driver-435 (and also the wrong driver 430). It won't work with these drivers. $ ubuntu-drivers devices == /sys/devices/pci:00/:00:01.0/:01:00.0 == modalias : pci:v10DEd0DFCsv1028sd0535bc03sc00i00 vendor : NVIDIA Corporation model: GF108GLM [NVS 5200M] driver : nvidia-340 - distro non-free driver : nvidia-driver-435 - distro non-free recommended driver : nvidia-driver-430 - distro non-free driver : nvidia-driver-390 - distro non-free driver : xserver-xorg-video-nouveau - distro free builtin $ lsb_release -rd Description:Ubuntu 18.04.3 LTS Release:18.04 I found the modalias in the packages nvidia-driver-435 and also in the package of the nvidia-driver-430. In the Nvidia READMEs you can find that the NVS 5200M (0DFC) is only supported up to 390. I opened an issue on https://github.com/tseliot/nvidia-graphics- drivers/issues/36 and tseliot told me it could be a parsing problem of the Nvidia READMEs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-430/+bug/1856166/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851829] Re: kernel trace found with ubuntu_bpf test on Eoan s390x LPAR
*** This bug is a duplicate of bug 1856163 ***
https://bugs.launchpad.net/bugs/1856163
It's the test_map test, see bug 1856163
** This bug has been marked a duplicate of bug 1856163
test_maps test from ubuntu_bpf will cause OOM on Eoan s390x LPAR
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1851829
Title:
kernel trace found with ubuntu_bpf test on Eoan s390x LPAR
Status in ubuntu-kernel-tests:
Triaged
Status in linux package in Ubuntu:
Incomplete
Status in linux source package in Eoan:
Incomplete
Bug description:
This trace can be seen right after you started the test on s390x LPAR.
**
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
** **
** trace_printk() being used. Allocating extra memory. **
** **
** This means that this is a DEBUG kernel and it is **
** unsafe for production use. **
** **
** If you see this message and you are not debugging**
** the kernel, report this immediately to your vendor! **
** **
** NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE NOTICE **
**
WARNING: CPU: 0 PID: 3159 at mm/page_alloc.c:4702
__alloc_pages_nodemask+0x25e/0x318
Modules linked in: xt_conntrack ipt_REJECT nf_reject_ipv4 ip6table_mangle
ip6table_nat nf_tables nfnetlink ip6table_filter ip6_tables iptable_mangle
xt_CHECKSUM iptable_nat xt_MASQUERADE xt_tcpudp bridge iptable_filter bpfilter
aufs overlay 8021q garp stp mrp llc openvswitch nsh nf_conncount nf_nat
nf_conntrack nf_defrag_ipv6 nf_defrag_ipv4 binfmt_misc zfs(PO) zunicode(PO)
zavl(PO) icp(PO) zlua(PO) zcommon(PO) znvpair(PO) spl(O) genwqe_card crc_itu_t
chsc_sch eadm_sch ctcm fsm vfio_ccw vfio_mdev mdev vfio_iommu_type1 vfio
sch_fq_codel nfsd auth_rpcgss nfs_acl lockd grace sunrpc ip_tables x_tables
btrfs zstd_compress zlib_deflate raid10 raid456 async_raid6_recov async_memcpy
async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 linear
dm_service_time pkey zcrypt crc32_vx_s390 ghash_s390 prng mlx4_en mlx4_ib
ib_uverbs aes_s390 ib_core ptp pps_core qeth_l2 des_s390 des_generic
sha512_s390 sha256_s390 sha1_s390 sha_common mlx4_core zfcp scsi_transport_fc
qeth qdio ccwgroup
dasd_eckd_mod dasd_mod scsi_dh_emc scsi_dh_rdac scsi_dh_alua dm_multipath
CPU: 0 PID: 3159 Comm: test_verifier Tainted: P O
5.3.0-21-generic #22-Ubuntu
Hardware name: IBM 2964 N63 400 (LPAR)
Krnl PSW : 0704c0018000 0002fb832c9e
(__alloc_pages_nodemask+0x25e/0x318)
R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3
Krnl GPRS: 0003b7efcac0 00040dc0 00040dc0
000a
000a
0002fb6386b8
003d0900 0dc0 03e00b067000
03e00b067000
0003a57a8000 02aa0d1b28e0 03e002b6bb28
03e002b6baa8
Krnl Code: 0002fb832c92: a7212000tmll%r2,8192
0002fb832c96: a774ff87brc 7,2fb832ba4
#0002fb832c9a: a7f40001brc 15,2fb832c9c
>0002fb832c9e: a789lghi%r8,0
0002fb832ca2: a7f4ff83brc 15,2fb832ba8
0002fb832ca6: a718lhi %r1,0
0002fb832caa: a7f4ff1bbrc 15,2fb832ae0
0002fb832cae: e3100344lg %r1,832
Call Trace:
([<03e002b6bb88>] 0x3e002b6bb88)
[<0002fb7ff3a0>] kmalloc_order_trace+0x40/0x100
[<0002fb6386b8>] bpf_int_jit_compile+0x70/0x240
[<0002fb7828ce>] bpf_prog_select_runtime+0x13e/0x190
[<0002fb78614c>] bpf_prog_load+0x2dc/0x6a8
[<0002fb786ca6>] __do_sys_bpf+0x78e/0x10c0
[<0002fbe82228>] system_call+0xdc/0x2c8
Last Breaking-Event-Address:
[<0002fb832c9a>] __alloc_pages_nodemask+0x25a/0x318
---[ end trace 1d8b7179967b64ff ]---
The test itself will get killed with oom-killer later, thus generating
a return code 137 for the test.
All the following tests in this test suite will be skipped.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1851829/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854762] Re: eoan/linux: 5.3.0-25.27 -proposed tracker
5.3.0-25.27 - generic Regression test CMPL, RTB. 57 / 60 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in amd64: ubuntu_kvm_unit_tests - realmode failed (bug 1850653) vmx (bug 1821394) vmx_apicv_test (bug 1827866) apic timeouted (bug 1748103) apic-split timeouted (bug 1821390) ubuntu_ltp - proc01 (bug 1829849) vma05 (bug 1845863) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuset_hotplug (bug 1834006) mkfs01_ext3_sh, mkfs01_ext4_sh, nm01_sh (bug 1853610) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_sysdig_smoke_test - Failed on 5.3 (bug 1844493) 51 / 54 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_bpf - Failed sockmap unexpected timeout on ARM64 (bug 1805806) ubuntu_kvm_unit_tests - gicv2-mmio-up and gicv2-mmio-3p failed on Moonshot ARM64 (bug 1802492) ubuntu_ltp - proc01 (bug 1829849) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) mkfs01_ext3_sh, mkfs01_ext4_sh, nm01_sh (bug 1853610) cpuhotplug03 (bug 1836167) cpuhotplug04 (bug 1836169) cpuhotplug06 (bug 1836170) crypto_user02 (bug 1837543) zram01 / zram02 / zram03 timeout (bug 1854706) 4 / 56 tests were run, missing: aio_dio_bugs, aiostress, ebizzy, fs_mark, fsx, iperf, ipv6connect, rmaptest, rtc, signaltest, synctest, ubuntu_aufs_smoke_test, ubuntu_blkdev_directio, ubuntu_blktrace_smoke_test, ubuntu_boot, ubuntu_btrfs_kernel_fixes, ubuntu_cts_kernel, ubuntu_docker_smoke_test, ubuntu_fan_smoke_test, ubuntu_ftrace_smoke_test, ubuntu_futex, ubuntu_kernel_selftests, ubuntu_kvm_smoke_test, ubuntu_kvm_unit_tests, ubuntu_leap_seconds, ubuntu_loop_smoke_test, ubuntu_ltp, ubuntu_ltp_syscalls, ubuntu_lttng_smoke_test, ubuntu_nbd_smoke_test, ubuntu_overlayfs_smoke_test, ubuntu_qrt_apparmor, ubuntu_qrt_kernel_aslr_collisions, ubuntu_qrt_kernel_hardening, ubuntu_qrt_kernel_panic, ubuntu_qrt_kernel_security, ubuntu_quota_smoke_test, ubuntu_ramfs_stress, ubuntu_seccomp, ubuntu_squashfs_smoke_test, ubuntu_stress_smoke_test, ubuntu_sysdig_smoke_test, ubuntu_unionmount_ovlfs, ubuntu_vfat_stress, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs, ubuntu_zfs_fstest, ubuntu_zfs_smoke_test, ubuntu_zfs_xfs_generic, ubuntu_zram_smoke_test, wb_kupdate Issue to note in ppc64le: ubuntu_lxc - Failed to download image index (bug 1839835) 45 / 56 tests were run, missing: hwclock, ubuntu_bpf, ubuntu_bpf_jit, ubuntu_cts_kernel, ubuntu_kernel_selftests, ubuntu_kvm_unit_tests, ubuntu_lxc, ubuntu_seccomp, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): ubuntu_kvm_smoke_test - failed to start KVM with uvtool on P8 (bug 1798358) ubuntu_ltp - proc01 (bug 1829849) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) mkfs01_ext3_sh, mkfs01_ext4_sh, nm01_sh (bug 1853610) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) ubuntu_sysdig_smoke_test - Failed on 5.3 (bug 1844493) 53 / 56 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P9): hwclock - hwclock test failed on Power9 due to 0.x sec differences / time out waiting for time change (bug 1802233) ubuntu_ltp - proc01 (bug 1829849) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuset_hotplug (bug 1834006) mkfs01_ext3_sh, mkfs01_ext4_sh, nm01_sh (bug 1853610) crypto_user02 (bug 1837543) zram01 / zram02 / zram03 timeout (bug 1854706) ubuntu_ltp_syscalls - stime01 (bug 1845620) ubuntu_lxc - Failed to download image index (bug 1839835) ubuntu_sysdig_smoke_test - Failed on 5.3 (bug 1844493) Issue to note in s390x (KVM): ubuntu_bpf - test_verifier failed with 'Failed to load prog' on D s390x (bug 1812176) ubuntu_ltp - proc01 (bug 1829849) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuacct_100_100 (bug 1829978) cpuset_hotplug (bug 1834006) hugemmap05* / hugemmap06 (bug 1851606) mkfs01_ext3_sh, mkfs01_ext4_sh, nm01_sh (bug 1853610) getaddrinfo_01 (bug 1829995) ubuntu_ltp_syscalls - msgstress03 (bug 1797341) ubuntu_sysdig_smoke_test - Failed on 5.3 (bug 1844493) 44 / 52 tests were run, missing: hwclock, ubuntu_bpf, ubuntu_bpf_jit, ubuntu_cts_kernel, ubuntu_kernel_selftests, ubuntu_kvm_unit_tests, ubuntu_lxc, ubuntu_seccomp Issue to note in s390x (Ubuntu on LPAR): ubuntu_bpf - OOM causing other tests failed to run (bug 1856163) ubuntu_ltp - proc01 (bug 1829849) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) cpuset_inherit (bug 1849825) cpuset_hotplug (bug 1834006) mkfs01_ext3_sh, mkfs01_ext4_sh, nm01_sh (bug 1853610) getaddrinfo_01 (bug 1829995) ubuntu_sysdig_smoke_test - Failed on 5.3 (bug 1844493) Issue to
[Kernel-packages] [Bug 1856203] [NEW] xenial/linux-azure: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Thursday, 12. December 2019 15:53 UTC reason: prepare-package: Pending -- version not specified replaces: bug 1854813 trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Confirmed ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Xenial) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1854819 kernel-sru-cycle-2019.12.02-3 xenial ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: kernel-release-tracking-bug xenial ** Also affects: linux-azure (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Xenial) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/certification-testing Assignee: (unassigned) => Canonical Hardware Certification (canonical-hw-cert) ** Changed in: kernel-sru-workflow/certification-testing Status: New => Invalid ** Changed in:
[Kernel-packages] [Bug 1855448] Re: focal/linux: 5.4.0-8.11 -proposed tracker
** Summary changed: - focal/linux: 5.4.0-8.9 -proposed tracker + focal/linux: 5.4.0-8.11 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855448 Title: focal/linux: 5.4.0-8.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Thursday, 12. December 2019 15:52 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- copy FAILED regression-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1855448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856202] [NEW] trusty/linux-azure: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1856203 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Thursday, 12. December 2019 15:53 UTC reason: prepare-package: Holding -- waiting for master bug replaces: bug 1854811 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: Invalid ** Affects: kernel-sru-workflow/certification-testing Importance: Medium Assignee: Canonical Hardware Certification (canonical-hw-cert) Status: Invalid ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-signing-to-proposed Importance: Medium Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-security Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/promote-to-updates Importance: Medium Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/security-signoff Importance: Medium Assignee: Canonical Security Team (canonical-security) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: kernel-sru-workflow/verification-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-azure (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-azure (Ubuntu Trusty) Importance: Medium Status: Confirmed ** Tags: kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-backport-of-1856203 kernel-sru-cycle-2019.12.02-3 trusty ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/certification-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-signing-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-security Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-updates Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/security-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/verification-testing Importance: Undecided Status: New ** Tags added: kernel-release-tracking-bug trusty ** Also affects: linux-azure (Ubuntu Trusty) Importance: Undecided Status: New ** Changed in: linux-azure (Ubuntu Trusty) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/automated-testing Status: New => Invalid ** Changed in: kernel-sru-workflow/certification-testing Importance: Undecided => Medium ** Changed in:
[Kernel-packages] [Bug 1855448] Re: focal/linux: 5.4.0-8.11 -proposed tracker
The following packages ended up in the wrong component in the Proposed pocket: linux-headers-oem-osp1 5.4.0.8.9 - is in universe instead of main linux-image-oem-osp1 5.4.0.8.9 - is in universe instead of main linux-oem-osp1 5.4.0.8.9 - is in universe instead of main linux-oem-osp1-tools-host 5.4.0.8.9 - is in universe instead of main linux-tools-oem-osp1 5.4.0.8.9 - is in universe instead of main Once this is fixed, set the promote-to-proposed to Fix Released again ** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package Assignee: Andrea Righi (arighi) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Andrea Righi (arighi) => Seth Forshee (sforshee) ** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Fix Committed ** Tags added: block-proposed-focal ** Tags added: block-proposed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => Incomplete ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Packaging - phase-changed: Friday, 06. December 2019 14:38 UTC + phase: Promote to Proposed + phase-changed: Thursday, 12. December 2019 15:52 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + automated-testing: Stalled -- testing FAILED + promote-to-proposed: Stalled -- copy FAILED + regression-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855448 Title: focal/linux: 5.4.0-8.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Incomplete Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Promote to Proposed phase-changed: Thursday, 12. December 2019 15:52 UTC reason: automated-testing: Stalled -- testing FAILED promote-to-proposed: Stalled -- copy FAILED regression-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1855448/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856202] Re: trusty/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + trusty/linux-azure: -proposed tracker ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1856203 + packages: + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Holding before Packaging + phase-changed: Thursday, 12. December 2019 15:53 UTC + reason: + prepare-package: Holding -- waiting for master bug replaces: bug 1854811 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856202 Title: trusty/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1856203 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Packaging phase-changed: Thursday, 12. December 2019 15:53 UTC reason: prepare-package: Holding -- waiting for master bug replaces: bug 1854811 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856202/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854819] Re: bionic/linux: 4.15.0-73.82 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 - xenial/linux-azure: bug 1854813 + xenial/linux-azure: bug 1856203, bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854819 Title: bionic/linux: 4.15.0-73.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Tuesday, 03. December 2019 15:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws: bug 1854802 bionic/linux-fips: bug 1854809 bionic/linux-gke-4.15: bug 1854804 bionic/linux-ibm-gt: bug 1854806 bionic/linux-kvm: bug 1854805 bionic/linux-oem: bug 1854797 bionic/linux-oracle: bug 1854808 bionic/linux-raspi2: bug 1854793 bionic/linux-snapdragon: bug 1854796 bionic/linux/pc-kernel: bug 1854790 bionic/linux/pc-lowlatency-kernel: bug 1854791 xenial/linux-azure: bug 1856203, bug 1854813 xenial/linux-gcp: bug 1854816 xenial/linux-hwe: bug 1854818 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854819/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1555351] Re: High load freezes ubuntu completely everytime (have to reboot)
This is a very well know issue (and frequently reported in all distros) in the way Linux handles i/o. One possible solution is to switch to the BFQ scheduler, e.g. seee https://old.reddit.com/r/Fedora/comments/ay7dkh/linux_large_transfers_freeze_system_high_io/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1555351 Title: High load freezes ubuntu completely everytime (have to reboot) Status in linux package in Ubuntu: Incomplete Bug description: Whenever an intensive application runs which consumes lots of memory or hard drive i/o, Ubuntu freezes completely. It is even impossible to kill the offending task. Only "solution" is then to wait for the application to finish, or restart PC. Windows doesn't have this issue as bad as Ubuntu, in that Windows is always somewhat responsive, and you can attempt to kill the intensive application to recover the system. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: linux-image-4.2.0-32-generic 4.2.0-32.37 ProcVersionSignature: Ubuntu 4.2.0-32.37-generic 4.2.8-ckt4 Uname: Linux 4.2.0-32-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 AudioDevicesInUse: Cannot stat file /proc/18210/fd/20: Input/output error USERPID ACCESS COMMAND /dev/snd/controlC0: cossio 2082 F pulseaudio /dev/snd/controlC1: cossio 2082 F pulseaudio CurrentDesktop: XFCE Date: Wed Mar 9 22:28:53 2016 HibernationDevice: RESUME=UUID=37d586ee-f517-4977-b9cd-189c200b0bac InstallationDate: Installed on 2015-08-03 (219 days ago) InstallationMedia: Xubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422.1) MachineType: ASUSTeK COMPUTER INC. X550LA ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.2.0-32-generic.efi.signed root=UUID=52be177f-a0ea-4053-be39-bbeaff1a22df ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-4.2.0-32-generic N/A linux-backports-modules-4.2.0-32-generic N/A linux-firmware1.149.3 SourcePackage: linux UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev' UpgradeStatus: Upgraded to wily on 2016-01-31 (38 days ago) dmi.bios.date: 04/01/2014 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: X550LA.505 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: X550LA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrX550LA.505:bd04/01/2014:svnASUSTeKCOMPUTERINC.:pnX550LA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnX550LA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: X550LA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1555351/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850540] Re: multi-zone raid0 corruption
Adding the block-proposed-* tags as per comment #11. ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan ** Tags added: block-proposed-bionic block-proposed-disco block-proposed-eoan verification-done verification-done-bionic verification-done-disco verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850540 Title: multi-zone raid0 corruption Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mdadm package in Ubuntu: Fix Released Status in linux source package in Precise: New Status in mdadm source package in Precise: New Status in linux source package in Trusty: Confirmed Status in mdadm source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Status in mdadm source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in mdadm source package in Bionic: Fix Committed Status in linux source package in Disco: Confirmed Status in mdadm source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Status in mdadm source package in Eoan: Fix Committed Status in linux source package in Focal: Confirmed Status in mdadm source package in Focal: Fix Released Status in mdadm package in Debian: Fix Released Bug description: Bug 1849682 tracks the temporarily revert of the fix for this issue, while this bug tracks the re-application of that fix once we have a full solution. [Impact] (cut & paste from https://marc.info/?l=linux-raid=157360088014027=2) An unintentional RAID0 layout change was introduced in the v3.14 kernel. This effectively means there are 2 different layouts Linux will use to write data to RAID0 arrays in the wild - the “pre-3.14” way and the “3.14 and later” way. Mixing these layouts by writing to an array while booted on these different kernel versions can lead to corruption. Note that this only impacts RAID0 arrays that include devices of different sizes. If your devices are all the same size, both layouts are equivalent, and your array is not at risk of corruption due to this issue. Unfortunately, the kernel cannot detect which layout was used for writes to pre-existing arrays, and therefore requires input from the administrator. This input can be provided via the kernel command line with the raid0.default_layout= parameter, or by setting the default_layout module parameter when loading the raid0 module. With a new enough version of mdadm (>= 4.2, or equivalent distro backports), you can set the layout version when assembling a stopped array. For example: mdadm --stop /dev/md0 mdadm --assemble -U layout-alternate /dev/md0 /dev/sda1 /dev/sda2 See the mdadm manpage for more details. Once set in this manner, the layout will be recorded in the array and will not need to be explicitly specified in the future. (The mdadm part of this SRU is for the above support ^) [Test Case] = mdadm = Confirm that a multi-zone raid0 created w/ older mdadm is able to be started on a fixed kernel by setting a layout. 1) Ex: w/ old kernel/mdadm: mdadm --create /dev/md0 --run --metadata=default \ --level=0 --raid-devices=2 /dev/vdb1 /dev/vdc1 2) Reboot onto fixed kernel & update mdadm 3) sudo mdadm --stop /dev/md0 && sudo mdadm --assemble -U layout-alternate \ /dev/md0 /dev/vdb1 /dev/vdc1 4) Confirm that the array autostarts on reboot 5) Confirm that w/ new kernel & new mdadm, a user can create and start an array in a backwards-compatible fashion (i.e. w/o an explicit layout). 6) Verify that 'mdadm --detail /dev/md0' displays the layout = linux = Similar to above, but using kernel command line options. [Regression Risk] The kernel side of things will break starting pre-existing arrays. That's intentional. The mdadm side will cause a regression in functionality where a user can no longer create multi-zone raid0s on kernels that do not yet have the raid0 layout patches. This is intentional, as such RAID arrays present a corruption risk. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-release-notes/+bug/1850540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856098] Re: Laptop suddenly keeps sending random (touchscreen?) input events
Is this bug filed right after the issue happened? I can see this error but it's in previous S3 cycle: [97672.131997] i2c_hid i2c-ELAN2097:00: i2c_hid_get_input: incomplete report (67/21845) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1856098 Title: Laptop suddenly keeps sending random (touchscreen?) input events Status in linux package in Ubuntu: Confirmed Bug description: Device: Dell Inspiron 7370 CID: 201704-25503 Ubuntu 19.10 with -proposed activated Kernel 5.3.0-23-generic #25-Ubuntu This laptop is equipped with a touchpad and a touchscreen. Sometimes, it goes crazy and starts sending random input events, as if I was franticly tapping the screen :) The only way I've found to stop that mess is to suspend/resume the device by closing the lid, waiting a few seconds, then opening the lid again. I checked in kernel logs and found that there is an input event created, that probably leads to the behavior I'm observing, and then I have to suspend the device: $ dmesg | grep " input\:" -A1 [41192.850576] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input68 [42711.124024] PM: suspend entry (deep) -- [100647.563448] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input111 [102513.121367] PM: suspend entry (deep) -- [113922.124463] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input122 [115707.625939] PM: suspend entry (deep) -- [118464.566206] input: E3:28:E9:21:6D:B6 as /devices/virtual/input/input127 [120923.291900] PM: suspend entry (deep) -- [121086.436845] input: E3:28:E9:21:94:78 as /devices/virtual/input/input130 [122565.426895] PM: suspend entry (deep) -- [122997.788106] input: E3:28:E9:21:94:78 as /devices/virtual/input/input135 [123737.137719] PM: suspend entry (deep) -- [126202.798058] input: E3:28:E9:21:94:78 as /devices/virtual/input/input140 [126233.937280] fwupd[9183]: segfault at ffc8 ip 7f7818d63dd0 sp 7fff6d462b30 error 5 in libxmlb.so.1.0.0[7f7818d5c000+11000] -- [130542.694828] input: E3:28:E9:21:94:78 as /devices/virtual/input/input151 [133343.589750] PM: suspend entry (deep) -- [133495.934919] input: E3:28:E9:21:94:78 as /devices/virtual/input/input156 [134604.582752] PM: suspend entry (deep) -- [134623.041244] input: E3:28:E9:21:94:78 as /devices/virtual/input/input159 [135678.503977] PM: suspend entry (deep) -- [135709.087771] input: E3:28:E9:21:94:78 as /devices/virtual/input/input162 [136322.841701] PM: suspend entry (deep) -- ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pieq 2050 F pulseaudio /dev/snd/pcmC0D0c: pieq 2050 F...m pulseaudio CurrentDesktop: ubuntu:GNOME Date: Thu Dec 12 07:16:25 2019 InstallationDate: Installed on 2019-07-02 (162 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:58f5 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 7370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-19 (53 days ago) dmi.bios.date: 04/23/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.14.0 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.14.0:bd04/23/2019:svnDellInc.:pnInspiron7370:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 7370 dmi.product.sku: 07E9 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856098/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856084] Re: Livelock between ZFS evict and writeback threads
** Also affects: zfs-linux (Ubuntu Focal) Importance: Medium Assignee: Heitor Alves de Siqueira (halves) Status: Confirmed ** Also affects: zfs-linux (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: zfs-linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: zfs-linux (Ubuntu Bionic) Status: New => Confirmed ** Changed in: zfs-linux (Ubuntu Disco) Status: New => Confirmed ** Changed in: zfs-linux (Ubuntu Bionic) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: zfs-linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: zfs-linux (Ubuntu Disco) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) ** Changed in: zfs-linux (Ubuntu Eoan) Assignee: (unassigned) => Heitor Alves de Siqueira (halves) -- 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/1856084 Title: Livelock between ZFS evict and writeback threads Status in zfs-linux package in Ubuntu: Confirmed Status in zfs-linux source package in Bionic: Confirmed Status in zfs-linux source package in Disco: Confirmed Status in zfs-linux source package in Eoan: Confirmed Status in zfs-linux source package in Focal: Confirmed Status in zfs-linux package in Debian: Unknown Bug description: Livelock between ZFS evict and writeback threads [Impact] ZIO pipeline stalls, causing ZFS workloads to hang indefinitely [Description] For certain ZFS workloads, we start seeing hung task timeouts in the kernel logs due to zil_commit() stalling. This is due to zfs_zget() not detecting whether a znode has been marked for deletion before attempting to access it, causing a constant "retry loop" in zfs_get_data() if that znode has been unlinked already. An example of the stack traces follows: [72742.051703] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [72742.070429] mysqld D0 5713 2881 0x0320 [72742.073220] Call Trace: [72742.075305] __schedule+0x24e/0x880 [72742.090436] schedule+0x2c/0x80 [72742.090438] schedule_preempt_disabled+0xe/0x10 [72742.090441] __mutex_lock.isra.5+0x276/0x4e0 [72742.090547] ? dmu_tx_destroy+0x105/0x130 [zfs] [72742.090555] __mutex_lock_slowpath+0x13/0x20 [72742.115374] ? __mutex_lock_slowpath+0x13/0x20 [72742.132266] mutex_lock+0x2f/0x40 [72742.134207] zil_commit_impl+0x1b0/0x1b30 [zfs] [72742.150428] ? spl_kmem_alloc+0x115/0x180 [spl] [72742.152622] ? mutex_lock+0x12/0x40 [72742.154819] ? zfs_refcount_add_many+0x9a/0x100 [zfs] [72742.171450] zil_commit+0xde/0x150 [zfs] [72742.173687] zfs_fsync+0x77/0xe0 [zfs] [72742.175044] zpl_fsync+0x80/0x110 [zfs] [72742.191690] vfs_fsync_range+0x51/0xb0 [72742.193876] do_fsync+0x3d/0x70 [72742.195126] SyS_fsync+0x10/0x20 [72742.211059] do_syscall_64+0x73/0x130 [72742.214078] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 It's possible to hit this issue due to a race between the ZFS evict and writeback threads. If the z_iput task is trying to evict a znode that's currently sitting in the writeback thread, both will "livelock" each other and stall the ZIO pipeline, causing other ZFS operations (such as zil_commit) to hang indefinitely. This has been documented and fixed upstream in PR#9583 [0]. We need to pull two fixes from upstream: the first one fixes the zfs_zget() issue in the writeback thread, while the second fixes a regression on O_TMPFILE descriptors caused by the first one. Upstream patches: - Break out of zfs_zget early if unlinked znode (41e1aa2a06f8) - Check for unlinked znodes after igrab() (0c46813805f4) [Test Case] Being a race condition, this issue has been hard to reproduce consistently. The racing window between evict() and the ZFS writeback thread is quite strict, but users have reported this to show up after some hours of running LXD-containerized mySQL workloads. [Regression Potential] These patches have been tested both in the ZFS test suite and in production environments, so the potential for further regressions should be low. Additional regressions would likely cause issues with the ZFS writeback/commit and IO pipeline, so they should be spotted fairly quickly. [0] https://github.com/zfsonlinux/zfs/pull/9583 [1] https://github.com/zfsonlinux/zfs/commit/41e1aa2a06f8 [2] https://github.com/zfsonlinux/zfs/commit/0c46813805f4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/zfs-linux/+bug/1856084/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1727358] Re: cloud-init is slow to complete init on minimized images
In Openstack Newton (linux-kvm) with Centos 7 (latest cloud-image) with
cloud-init 19.3, the delay is observed. I think this is due to the
version that Centos ships with for python (2.7.5).
The problem is at the init-local stage. https://github.com/canonical
/cloud-init/pull/103
here is the attached cloud-init.log
** Attachment added: "cloud-init.log"
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1727358/+attachment/5312004/+files/cloud-init.log
--
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/1727358
Title:
cloud-init is slow to complete init on minimized images
Status in cloud-init:
Won't Fix
Status in cloud-init package in Ubuntu:
Won't Fix
Status in linux-kvm package in Ubuntu:
Confirmed
Status in python3.6 package in Ubuntu:
Triaged
Bug description:
http://paste.ubuntu.com/25816789/ for the full logs.
cloud-init is very slow to complete its initialization steps.
Specifically, the 'init' takes over 150 seconds.
Cloud-init v. 17.1 running 'init-local' at Wed, 25 Oct 2017 13:22:07 +.
Up 2.39 seconds.
2017-10-25 13:22:07,157 - util.py[WARNING]: did not find either path
/sys/class/dmi/id or dmidecode command
Cloud-init v. 17.1 running 'init' at Wed, 25 Oct 2017 13:22:16 +. Up
11.37 seconds.
ci-info: Net device
info+
ci-info:
++---+-+---+---+---+
ci-info: | Device | Up | Address | Mask | Scope |
Hw-Address|
ci-info:
++---+-+---+---+---+
ci-info: | ens3: | True | 192.168.100.161 | 255.255.255.0 | . |
52:54:00:bb:ad:fb |
ci-info: | ens3: | True |.| . | d |
52:54:00:bb:ad:fb |
ci-info: | lo: | True |127.0.0.1| 255.0.0.0 | . |
. |
ci-info: | lo: | True |.| . | d |
. |
ci-info: | sit0: | False |.| . | . |
. |
ci-info:
++---+-+---+---+---+
ci-info: Route IPv4
info
ci-info:
+---+---+---+-+---+---+
ci-info: | Route | Destination |Gateway| Genmask |
Interface | Flags |
ci-info:
+---+---+---+-+---+---+
ci-info: | 0 |0.0.0.0| 192.168.100.1 | 0.0.0.0 |ens3
| UG |
ci-info: | 1 | 192.168.100.0 |0.0.0.0| 255.255.255.0 |ens3
| U |
ci-info: | 2 | 192.168.100.1 |0.0.0.0| 255.255.255.255 |ens3
| UH |
ci-info:
+---+---+---+-+---+---+
2017-10-25 13:24:38,187 - util.py[WARNING]: Failed to resize filesystem
(cmd=('resize2fs', '/dev/root'))
2017-10-25 13:24:38,193 - util.py[WARNING]: Running module resizefs () failed
Generating public/private rsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
The key fingerprint is:
SHA256:LKNlCqqOgPB8KBKGfPhFO5Rs6fDMnAvVet/W9i4vLxY root@cloudimg
The key's randomart image is:
+---[RSA 2048]+
| |
|. + |
| . O . |
|o . % +. |
|++.o %=.S|
|+=ooo=+o. . .E |
|* +.+. . o o. |
|=. . . .=. |
|+. . B= |
+[SHA256]-+
Generating public/private dsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
The key fingerprint is:
SHA256:dNWNyBHqTUCl820/vL0dEhOVDFYJzqr1WeuqV1PAmjk root@cloudimg
The key's randomart image is:
+---[DSA 1024]+
| .oo=X==o|
| =* *+.|
|. = .B . |
| . o =E.. .|
|S .oo+o..|
| o ..*+.|
| . +.=o|
| .o *|
| .o..++|
+[SHA256]-+
Generating public/private ecdsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
The key fingerprint is:
SHA256:N3RTlPa7KU5ryq6kJAO8Tiq90ub4P1DGSofn6jFkM3k root@cloudimg
The key's randomart image is:
+---[ECDSA 256]---+
| .o. |
| .o |
| o . o. . |
| +.*. . . .|
| .*XE S o .|
| oo++. . . |
| oo= o . . . o|
|o.Oo. + o . .o.o |
|oB=+.. . .o++o. |
+[SHA256]-+
Generating public/private ed25519 key pair.
Your identification has been saved in /etc/ssh/ssh_host_ed25519_key.
Your
[Kernel-packages] [Bug 1850540] Re: multi-zone raid0 corruption
There is no plan to reapply the kernel side of these fixes ahead of 18.04.4. Introducing the mdadm side of that in 18.04.4 therefore would cause a regression in functionality: ubuntu@ip-172-30-0-208:~$ sudo mdadm --create /dev/md0 --run --metadata=default --level=0 --raid-devices=2 /dev/xvdb /dev/xvdc mdadm: /dev/xvdb appears to be part of a raid array: level=raid0 devices=2 ctime=Wed Dec 11 22:10:59 2019 mdadm: /dev/xvdc appears to be part of a raid array: level=raid0 devices=2 ctime=Wed Dec 11 22:10:59 2019 mdadm: ADD_NEW_DISK for /dev/xvdb failed: Invalid argument mdadm: Possibly your kernel doesn't support RAID0 layouts. mdadm: Either upgrade, or use --layout=dangerous Of course, at install time, upgrading the kernel isn't an option. So let's hold this SRU until after the point release. ** Description changed: Bug 1849682 tracks the temporarily revert of the fix for this issue, while this bug tracks the re-application of that fix once we have a full solution. [Impact] (cut & paste from https://marc.info/?l=linux-raid=157360088014027=2) An unintentional RAID0 layout change was introduced in the v3.14 kernel. This effectively means there are 2 different layouts Linux will use to write data to RAID0 arrays in the wild - the “pre-3.14” way and the “3.14 and later” way. Mixing these layouts by writing to an array while booted on these different kernel versions can lead to corruption. Note that this only impacts RAID0 arrays that include devices of different sizes. If your devices are all the same size, both layouts are equivalent, and your array is not at risk of corruption due to this issue. Unfortunately, the kernel cannot detect which layout was used for writes to pre-existing arrays, and therefore requires input from the administrator. This input can be provided via the kernel command line with the raid0.default_layout= parameter, or by setting the default_layout module parameter when loading the raid0 module. With a new enough version of mdadm (>= 4.2, or equivalent distro backports), you can set the layout version when assembling a stopped array. For example: mdadm --stop /dev/md0 mdadm --assemble -U layout-alternate /dev/md0 /dev/sda1 /dev/sda2 See the mdadm manpage for more details. Once set in this manner, the layout will be recorded in the array and will not need to be explicitly specified in the future. (The mdadm part of this SRU is for the above support ^) [Test Case] = mdadm = Confirm that a multi-zone raid0 created w/ older mdadm is able to be started on a fixed kernel by setting a layout. 1) Ex: w/ old kernel/mdadm: mdadm --create /dev/md0 --run --metadata=default \ --level=0 --raid-devices=2 /dev/vdb1 /dev/vdc1 2) Reboot onto fixed kernel & update mdadm 3) sudo mdadm --stop /dev/md0 && -sudo mdadm --assemble -U layout-alternate \ + sudo mdadm --assemble -U layout-alternate \ /dev/md0 /dev/vdb1 /dev/vdc1 4) Confirm that the array autostarts on reboot 5) Confirm that w/ new kernel & new mdadm, a user can create and start an array in a backwards-compatible fashion (i.e. w/o an explicit layout). 6) Verify that 'mdadm --detail /dev/md0' displays the layout = linux = Similar to above, but using kernel command line options. [Regression Risk] The kernel side of things will break starting pre-existing arrays. That's intentional. - Although I've done due-diligence to check for backwards compatibility - issues, the mdadm side may still present some. + The mdadm side will cause a regression in functionality where a user can + no longer create multi-zone raid0s on kernels that do not yet have the + raid0 layout patches. This is intentional, as such RAID arrays present a + corruption risk. ** Tags removed: verification-done verification-done-bionic verification-done-disco verification-done-eoan ** Tags added: verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1850540 Title: multi-zone raid0 corruption Status in Release Notes for Ubuntu: New Status in linux package in Ubuntu: Confirmed Status in mdadm package in Ubuntu: Fix Released Status in linux source package in Precise: New Status in mdadm source package in Precise: New Status in linux source package in Trusty: Confirmed Status in mdadm source package in Trusty: Confirmed Status in linux source package in Xenial: Confirmed Status in mdadm source package in Xenial: Confirmed Status in linux source package in Bionic: Confirmed Status in mdadm source package in Bionic: Fix Committed Status in linux source package in Disco: Confirmed Status in mdadm source package in Disco: Fix Committed Status in linux source package in Eoan: Confirmed Status in mdadm source package in
[Kernel-packages] [Bug 1856203] Re: xenial/linux-azure: -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + xenial/linux-azure: -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 + packages: + main: linux-azure + meta: linux-meta-azure + signed: linux-signed-azure + phase: Ready for Packaging + phase-changed: Thursday, 12. December 2019 15:53 UTC + reason: + prepare-package: Pending -- version not specified replaces: bug 1854813 + trackers: + trusty/linux-azure: bug 1856202 + xenial/linux-azure/azure-kernel: bug 1856199 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1856203 Title: xenial/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1854819 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Thursday, 12. December 2019 15:53 UTC reason: prepare-package: Pending -- version not specified replaces: bug 1854813 trackers: trusty/linux-azure: bug 1856202 xenial/linux-azure/azure-kernel: bug 1856199 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1856203/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855637] Re: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10
Current results... Eoan iso live boot: cores hang and recover Eoan install + all updates: cores hang and recover Eoan install + all updates + backport iwlwifi ppa: cannot associate Eoan install + all updates + backport iwlwifi from Eoan: Kernel panic Bionic + all updates: Everything works fine. Not sure where to go from here, but wanted to communicate the results of all the testing I did. Is there some special version of the linux-firmware package I should be using? Wayne -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855637 Title: Intel AC 9260 (iwlwifi) completely unstable and halts cores in 19.10 Status in linux package in Ubuntu: Confirmed Bug description: After updating from 18.04 to 19.10, the entire system will freeze and eventually recover with many dmesg errors with backtraces and all sorts of errors around the iwlwifi module. I eventually restored to an 18.04 backup, but not before logging a lot of information and also validating that it reproduces with the 19.10 "Try Ubuntu" from the iso, so it certainly isn't an artifact of the upgrade (although ubuntu-drivers does appear a bit confused about iwlwifi when I did an upgrade, but that appears to be unrelated). It is worth noting that I also use the bluetooth module in this card, but it is connected via a cable to an internal USB 2 header to the system board and I believe it uses another driver entirely. I have additional external drives I can install test bed systems on to test fixes if need be, but it is worth noting that this is rock solid on 18.04.3 and the issue will reproduce within 15 minutes of watching youtube videos on 19.10. DMESG output from start of issues is attached. Wayne --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-12-09 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Gigabyte Technology Co., Ltd. Z97-HD3 Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=24f8119c-dff3-46da-9242-15c3b9c76355 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 RelatedPackageVersions: linux-restricted-modules-5.3.0-24-generic N/A linux-backports-modules-5.3.0-24-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.3.0-24-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 07/31/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: F9 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: Z97-HD3 dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrF9:bd07/31/2015:svnGigabyteTechnologyCo.,Ltd.:pnZ97-HD3:pvrTobefilledbyO.E.M.:rvnGigabyteTechnologyCo.,Ltd.:rnZ97-HD3:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvrToBeFilledByO.E.M.: dmi.product.family: To be filled by O.E.M. dmi.product.name: Z97-HD3 dmi.product.sku: To be filled by O.E.M. dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856213] [NEW] Disco update: upstream stable patchset 2019-12-12
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 2019-12-12 Ported from the following upstream stable releases: v4.19.88, v5.3.15 from git://git.kernel.org/ clk: meson: gxbb: let sar_adc_clk_div set the parent clock rate clocksource/drivers/mediatek: Fix error handling ASoC: msm8916-wcd-analog: Fix RX1 selection in RDAC2 MUX ASoC: compress: fix unsigned integer overflow check reset: Fix memory leak in reset_control_array_put() clk: samsung: exynos5433: Fix error paths ASoC: kirkwood: fix external clock probe defer ASoC: kirkwood: fix device remove ordering clk: samsung: exynos5420: Preserve PLL configuration during suspend/resume pinctrl: cherryview: Allocate IRQ chip dynamic ARM: dts: imx6qdl-sabreauto: Fix storm of accelerometer interrupts reset: fix reset_control_ops kerneldoc comment clk: at91: avoid sleeping early clk: sunxi: Fix operator precedence in sunxi_divs_clk_setup clk: sunxi-ng: a80: fix the zero'ing of bits 16 and 18 ARM: dts: sun8i-a83t-tbs-a711: Fix WiFi resume from suspend samples/bpf: fix build by setting HAVE_ATTR_TEST to zero powerpc/bpf: Fix tail call implementation idr: Fix integer overflow in idr_for_each_entry idr: Fix idr_alloc_u32 on 32-bit systems x86/resctrl: Prevent NULL pointer dereference when reading mondata clk: ti: dra7-atl-clock: Remove ti_clk_add_alias call clk: ti: clkctrl: Fix failed to enable error with double udelay timeout net: fec: add missed clk_disable_unprepare in remove bridge: ebtables: don't crash when using dnat target in output chains can: peak_usb: report bus recovery as well can: c_can: D_CAN: c_can_chip_config(): perform a sofware reset on open can: rx-offload: can_rx_offload_queue_tail(): fix error handling, avoid skb mem leak can: rx-offload: can_rx_offload_offload_one(): do not increase the skb_queue beyond skb_queue_len_max can: rx-offload: can_rx_offload_offload_one(): increment rx_fifo_errors on queue overflow or OOM can: rx-offload: can_rx_offload_offload_one(): use ERR_PTR() to propagate error value in case of errors can: rx-offload: can_rx_offload_irq_offload_timestamp(): continue on error can: rx-offload: can_rx_offload_irq_offload_fifo(): continue on error can: flexcan: increase error counters if skb enqueueing via can_rx_offload_queue_sorted() fails can: mcp251x: mcp251x_restart_work_handler(): Fix potential force_quit race condition watchdog: meson: Fix the wrong value of left time ASoC: stm32: sai: add restriction on mmap support scripts/gdb: fix debugging modules compiled with hot/cold partitioning net: bcmgenet: use RGMII loopback for MAC reset net: bcmgenet: reapply manual settings to the PHY net: mscc: ocelot: fix __ocelot_rmw_ix prototype ceph: return -EINVAL if given fsc mount option on kernel w/o support net/fq_impl: Switch to kvmalloc() for memory allocation mac80211: fix station inactive_time shortly after boot block: drbd: remove a stray unlock in __drbd_send_protocol() pwm: bcm-iproc: Prevent unloading the driver module while in use clk: at91: fix update bit maps on CFG_MOR write usb: dwc2: use a longer core rest timeout in dwc2_core_reset() staging: rtl8192e: fix potential use after free staging: rtl8723bs: Drop ACPI device ids staging: rtl8723bs: Add 024c:0525 to the list of SDIO device-ids USB: serial: ftdi_sio: add device IDs for U-Blox C099-F9P mei: bus: prefix device names on bus with the bus name mei: me: add comet point V device id thunderbolt: Power cycle the router if NVM authentication fails media: v4l2-ctrl: fix flags for DO_WHITE_BALANCE pwm: Clear chip_data in pwm_put() media: atmel: atmel-isc: fix INIT_WORK misplacement macvlan: schedule bc_work even if error net: psample: fix skb_over_panic openvswitch: fix flow command message size sctp: Fix memory leak in sctp_sf_do_5_2_4_dupcook slip: Fix use-after-free Read in slip_open openvswitch: drop unneeded BUG_ON() in ovs_flow_cmd_build_info() openvswitch: remove another BUG_ON() selftests: bpf: test_sockmap: handle file creation failures gracefully tipc: fix link name length check sctp: cache netns in sctp_ep_common net: sched: fix `tc -s class show` no bstats on class with nolock subqueues net: macb: add missed tasklet_kill ext4: add more paranoia checking in ext4_expand_extra_isize handling watchdog: sama5d4: fix WDD value to be always set to max net: macb: Fix SUBNS increment and increase resolution net: macb driver, check for SKBTX_HW_TSTAMP mtd: rawnand: atmel: Fix spelling mistake in error message mtd: rawnand: atmel: fix possible object reference leak
[Kernel-packages] [Bug 1856213] Re: Disco update: upstream stable patchset 2019-12-12
** 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 2019-12-12 -upstream stable patchset 2019-12-12 -from git://git.kernel.org/ + Ported from the following upstream stable releases: + v4.19.88, v5.3.15 + + from git://git.kernel.org/ + + clk: meson: gxbb: let sar_adc_clk_div set the parent clock rate + clocksource/drivers/mediatek: Fix error handling + ASoC: msm8916-wcd-analog: Fix RX1 selection in RDAC2 MUX + ASoC: compress: fix unsigned integer overflow check + reset: Fix memory leak in reset_control_array_put() + clk: samsung: exynos5433: Fix error paths + ASoC: kirkwood: fix external clock probe defer + ASoC: kirkwood: fix device remove ordering + clk: samsung: exynos5420: Preserve PLL configuration during suspend/resume + pinctrl: cherryview: Allocate IRQ chip dynamic + ARM: dts: imx6qdl-sabreauto: Fix storm of accelerometer interrupts + reset: fix reset_control_ops kerneldoc comment + clk: at91: avoid sleeping early + clk: sunxi: Fix operator precedence in sunxi_divs_clk_setup + clk: sunxi-ng: a80: fix the zero'ing of bits 16 and 18 + ARM: dts: sun8i-a83t-tbs-a711: Fix WiFi resume from suspend + samples/bpf: fix build by setting HAVE_ATTR_TEST to zero + powerpc/bpf: Fix tail call implementation + idr: Fix integer overflow in idr_for_each_entry + idr: Fix idr_alloc_u32 on 32-bit systems + x86/resctrl: Prevent NULL pointer dereference when reading mondata + clk: ti: dra7-atl-clock: Remove ti_clk_add_alias call + clk: ti: clkctrl: Fix failed to enable error with double udelay timeout + net: fec: add missed clk_disable_unprepare in remove + bridge: ebtables: don't crash when using dnat target in output chains + can: peak_usb: report bus recovery as well + can: c_can: D_CAN: c_can_chip_config(): perform a sofware reset on open + can: rx-offload: can_rx_offload_queue_tail(): fix error handling, avoid skb mem leak + can: rx-offload: can_rx_offload_offload_one(): do not increase the skb_queue beyond skb_queue_len_max + can: rx-offload: can_rx_offload_offload_one(): increment rx_fifo_errors on queue overflow or OOM + can: rx-offload: can_rx_offload_offload_one(): use ERR_PTR() to propagate error value in case of errors + can: rx-offload: can_rx_offload_irq_offload_timestamp(): continue on error + can: rx-offload: can_rx_offload_irq_offload_fifo(): continue on error + can: flexcan: increase error counters if skb enqueueing via can_rx_offload_queue_sorted() fails + can: mcp251x: mcp251x_restart_work_handler(): Fix potential force_quit race condition + watchdog: meson: Fix the wrong value of left time + ASoC: stm32: sai: add restriction on mmap support + scripts/gdb: fix debugging modules compiled with hot/cold partitioning + net: bcmgenet: use RGMII loopback for MAC reset + net: bcmgenet: reapply manual settings to the PHY + net: mscc: ocelot: fix __ocelot_rmw_ix prototype + ceph: return -EINVAL if given fsc mount option on kernel w/o support + net/fq_impl: Switch to kvmalloc() for memory allocation + mac80211: fix station inactive_time shortly after boot + block: drbd: remove a stray unlock in __drbd_send_protocol() + pwm: bcm-iproc: Prevent unloading the driver module while in use + clk: at91: fix update bit maps on CFG_MOR write + usb: dwc2: use a longer core rest timeout in dwc2_core_reset() + staging: rtl8192e: fix potential use after free + staging: rtl8723bs: Drop ACPI device ids + staging: rtl8723bs: Add 024c:0525 to the list of SDIO device-ids + USB: serial: ftdi_sio: add device IDs for U-Blox C099-F9P + mei: bus: prefix device names on bus with the bus name + mei: me: add comet point V device id + thunderbolt: Power cycle the router if NVM authentication fails + media: v4l2-ctrl: fix flags for DO_WHITE_BALANCE + pwm: Clear chip_data in pwm_put() + media: atmel: atmel-isc: fix INIT_WORK misplacement + macvlan: schedule bc_work even if error + net: psample: fix skb_over_panic + openvswitch: fix flow command message size + sctp: Fix memory leak in sctp_sf_do_5_2_4_dupcook + slip: Fix use-after-free Read in
[Kernel-packages] [Bug 1855172] Re: Synaptics s3203 touchpad on Dell Inspiron 15 5547 has no working after recent upgrade
*** This bug is a duplicate of bug 1854798 *** https://bugs.launchpad.net/bugs/1854798 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** No longer affects: xserver-xorg-input-synaptics (Ubuntu) ** 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/1855172 Title: Synaptics s3203 touchpad on Dell Inspiron 15 5547 has no working after recent upgrade Status in linux package in Ubuntu: Confirmed Bug description: I upgraded my Ubuntu 18.04 with the `apt upgrade` command, and the kernel upgrade to 4.15.0-72. After a reboot, the touchpad stopped working. And the external USB mouse kept working fine. Looking for this issue, I found these reports about similar problems (https://sangams.com.np/fix-ubuntu-18-4-touchpad-not-working-properly/ and https://askubuntu.com/questions/1041820/touchpad-not-working-on- ubuntu-18-04), and I checked the package `xserver-xorg-input- synaptics` wasn't installed. Then I tried to install with the command: `apt install xserver-xorg-input-synaptics`. I rebooted the computer, but the problem continues. After I ran a diagnostic test with BIOS from Dell Notebook, and on interacting with the diagnostic system, I was able to use the touchpad without problems. Then I suppose this problem is from SO kernel upgraded. = Follow some info's system: $uname -a Linux myinspiron155547 4.15.0-72-generic #81-Ubuntu SMP Tue Nov 26 12:20:02 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux $ xinput ⎡ Virtual core pointerid=2[master pointer (3)] ⎜ ↳ Virtual core XTEST pointer id=4[slave pointer (2)] ⎜ ↳ Synaptics s3203 id=11 [slave pointer (2)] ⎣ Virtual core keyboard id=3[master keyboard (2)] ↳ Virtual core XTEST keyboard id=5[slave keyboard (3)] ↳ Power Buttonid=6[slave keyboard (3)] ↳ Video Bus id=7[slave keyboard (3)] ↳ Power Buttonid=8[slave keyboard (3)] ↳ Sleep Buttonid=9[slave keyboard (3)] ↳ Integrated_Webcam_HD: Integrate id=10 [slave keyboard (3)] ↳ Dell WMI hotkeysid=12 [slave keyboard (3)] ↳ AT Translated Set 2 keyboardid=13 [slave keyboard (3)] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1855172/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1563110] Re: No sound on Asus e200ha, intel sst with cx2072x codec
Hey all, got it working on my Asus E200HA @ Xubuntu 19.10. As already mentioned, the installed kernel (currently 5.3.0-24) already brings the driver. What I had to do was uninstalling libasound2 (currently 1.1.9-1), as the sound card is not supported in this version. After uninstalling, I installed the latest alsa-lib [1] (1.2.1.2). Note, that the default installation of the alsa-lib takes place in "/usr/lib", but it should be placed in "/usr/lib/x86_64-linux-gnu/". This can be done by running "./configure --libdir=/usr/lib/x86_64-linux-gnu/". After installing it, I downloaded the latest alsa-ucm-config [2] (1.2.1.2). The content of the ucm2 folder must be stored in "/usr/share/alsa/ucm2/". After a reboot, the sound works :) So, installing the latest libasound2 (= alsa-lib) on the right place and placing the UCM files in the right directory did the trick for me. [1] https://github.com/alsa-project/alsa-lib [2] https://github.com/alsa-project/alsa-ucm-conf/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1563110 Title: No sound on Asus e200ha, intel sst with cx2072x codec Status in ALSA driver: Confirmed Status in alsa-driver package in Ubuntu: Fix Released Status in linux package in Ubuntu: Fix Released Bug description: I've recently bought an Asus e200ha. Sound in this laptop doesn't work. The sound card is an intel sst with codec conexant cx2072x aplay -l: aplay: device_list:268: no soundcard found... in the sound setting there is a "Dummy output" --- ApportVersion: 2.14.1-0ubuntu3.19 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: XFCE DistroRelease: Ubuntu 14.04 HibernationDevice: RESUME=UUID=7b77dc46-7d5b-4869-83dd-739980736c3a InstallationDate: Installed on 2016-03-28 (0 days ago) InstallationMedia: Linux Mint 17.3 "Rosa" - Release amd64 20160105 Lsusb: Bus 002 Device 002: ID 0781:5583 SanDisk Corp. Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:3496 IMC Networks Bus 001 Device 002: ID 04f2:b54b Chicony Electronics Co., Ltd Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: ASUSTeK COMPUTER INC. E200HA Package: linux (not installed) ProcEnviron: TERM=xterm PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.19.0-32-generic root=UUID=50fb13c0-a8cd-441d-a38b-c0295c1b9a15 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 3.19.0-32.37~14.04.1-generic 3.19.8-ckt7 RelatedPackageVersions: linux-restricted-modules-3.19.0-32-generic N/A linux-backports-modules-3.19.0-32-generic N/A linux-firmware 1.127.16 Tags: rosa Uname: Linux 3.19.0-32-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 11/26/2015 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: E200HA.203 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: E200HA dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: ATN12345678901234567 dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrE200HA.203:bd11/26/2015:svnASUSTeKCOMPUTERINC.:pnE200HA:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnE200HA:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.name: E200HA dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. To manage notifications about this bug go to: https://bugs.launchpad.net/alsa-driver/+bug/1563110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1854762] Re: eoan/linux: 5.3.0-25.27 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: - bionic/linux-hwe: bug 1855309 + bionic/linux-hwe: bug 1855309, bug 1856210 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1854762 Title: eoan/linux: 5.3.0-25.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 05. December 2019 11:26 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-hwe: bug 1855309, bug 1856210 bionic/linux-hwe-edge: bug 1854761 eoan/linux-aws: bug 1854746 eoan/linux-azure: bug 1854749 eoan/linux-gcp: bug 1854751 eoan/linux-kvm: bug 1854752 eoan/linux-oracle: bug 1854755 eoan/linux-raspi2: bug 1854744 eoan/linux/pc-kernel: bug 1854741 eoan/linux/pc-lowlatency-kernel: bug 1854742 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1854762/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1646565] Re: GPF when removing lots of files from hfsplus partition
Is HFS+ support broken in Linux since 4.9? Can we have this officially acknowledged here? It's a high ranking result. For what it's worth, mounting large HFS+ volumes, like this Drobo I own, just hangs: uname -a Linux hiddenswitch-2 4.19.66-v7+ #1253 SMP Thu Aug 15 11:49:46 BST 2019 armv7l GNU/Linux Dec 7 03:14:24 hiddenswitch-2 kernel: [ 59.131448] usb 1-1.1.2: new high-speed USB device number 5 using dwc_otg Dec 7 03:14:24 hiddenswitch-2 kernel: [ 59.262082] usb 1-1.1.2: New USB device found, idVendor=19b9, idProduct=4d10 Dec 7 03:14:24 hiddenswitch-2 kernel: [ 59.262089] usb 1-1.1.2: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Dec 7 03:14:24 hiddenswitch-2 kernel: [ 59.262093] usb 1-1.1.2: Product: Drobo Dec 7 03:14:24 hiddenswitch-2 kernel: [ 59.262097] usb 1-1.1.2: Manufacturer: Data Robotics Inc. Dec 7 03:14:24 hiddenswitch-2 kernel: [ 59.262100] usb 1-1.1.2: SerialNumber: 0DB100221405 Dec 7 03:14:24 hiddenswitch-2 kernel: [ 59.337663] usb-storage 1-1.1.2:1.0: USB Mass Storage device detected Dec 7 03:14:24 hiddenswitch-2 kernel: [ 59.338383] scsi host0: usb-storage 1-1.1.2:1.0 Dec 7 03:14:25 hiddenswitch-2 kernel: [ 60.392032] scsi 0:0:0:0: Direct-Access TRUSTED Mass Storage 2.00 PQ: 0 ANSI: 5 Dec 7 03:14:25 hiddenswitch-2 kernel: [ 60.392751] sd 0:0:0:0: [sda] Very big device. Trying to use READ CAPACITY(16). Dec 7 03:14:25 hiddenswitch-2 kernel: [ 60.392996] sd 0:0:0:0: [sda] 34359738368 512-byte logical blocks: (17.6 TB/16.0 TiB) Dec 7 03:14:25 hiddenswitch-2 kernel: [ 60.393375] sd 0:0:0:0: [sda] Write Protect is off Dec 7 03:14:25 hiddenswitch-2 kernel: [ 60.393380] sd 0:0:0:0: [sda] Mode Sense: 03 00 00 00 Dec 7 03:14:25 hiddenswitch-2 kernel: [ 60.393827] sd 0:0:0:0: [sda] No Caching mode page found Dec 7 03:14:25 hiddenswitch-2 kernel: [ 60.393835] sd 0:0:0:0: [sda] Assuming drive cache: write through Dec 7 03:14:25 hiddenswitch-2 kernel: [ 60.403220] sd 0:0:0:0: Attached scsi generic sg0 type 0 Dec 7 03:14:53 hiddenswitch-2 kernel: [ 88.767530] sda: sda1 sda2 sda3 Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667794] INFO: task mount:2282 blocked for more than 120 seconds. Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667800] Tainted: G C 4.14.79-v7+ #1159 Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667802] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667806] mount D0 2282 2278 0x0001 Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667831] [<8079ef70>] (__schedule) from [<8079f5d8>] (schedule+0x50/0xa8) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667840] [<8079f5d8>] (schedule) from [<8079fa50>] (schedule_preempt_disabled+0x18/0x1c) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667848] [<8079fa50>] (schedule_preempt_disabled) from [<807a1358>] (__mutex_lock.constprop.3+0x190/0x58c) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667857] [<807a1358>] (__mutex_lock.constprop.3) from [<807a1870>] (__mutex_lock_slowpath+0x1c/0x20) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667865] [<807a1870>] (__mutex_lock_slowpath) from [<807a18d0>] (mutex_lock+0x5c/0x60) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667874] [<807a18d0>] (mutex_lock) from [<802cbc00>] (__blkdev_get+0x70/0x44c) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667882] [<802cbc00>] (__blkdev_get) from [<802cbd88>] (__blkdev_get+0x1f8/0x44c) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667889] [<802cbd88>] (__blkdev_get) from [<802cc1ec>] (blkdev_get+0x210/0x378) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667896] [<802cc1ec>] (blkdev_get) from [<802cc938>] (blkdev_get_by_path+0x60/0x98) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667904] [<802cc938>] (blkdev_get_by_path) from [<8028e2b4>] (mount_bdev+0x40/0x19c) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667930] [<8028e2b4>] (mount_bdev) from [<7f7080e4>] (hfsplus_mount+0x28/0x30 [hfsplus]) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667973] [<7f7080e4>] (hfsplus_mount [hfsplus]) from [<8028f320>] (mount_fs+0x24/0xb8) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667981] [<8028f320>] (mount_fs) from [<802acf08>] (vfs_kern_mount+0x58/0x110) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667989] [<802acf08>] (vfs_kern_mount) from [<802b0788>] (do_mount+0x174/0xbd4) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.667996] [<802b0788>] (do_mount) from [<802b1538>] (SyS_mount+0x84/0xac) Dec 7 03:17:28 hiddenswitch-2 kernel: [ 243.668005] [<802b1538>] (SyS_mount) from [<80108000>] (ret_fast_syscall+0x0/0x28) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1646565 Title: GPF when removing lots of files from hfsplus partition Status in linux package in Ubuntu: Confirmed Bug description: I get a general protection fault when removing a
