[Kernel-packages] [Bug 1861184] Re: bionic/linux-gcp: 5.0.0-1030.31 -proposed tracker
*** This bug is a duplicate of bug 1862213 *** https://bugs.launchpad.net/bugs/1862213 ** This bug has been marked a duplicate of bug 1862213 bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1861184 Title: bionic/linux-gcp: 5.0.0-1030.31 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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-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-gcp package in Ubuntu: Invalid Status in linux-gcp 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 kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Monday, 03. February 2020 22:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-gcp/gcp-kernel: bug 1861183 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861184/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** 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: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 11. February 2020 04:07 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 11. February 2020 07:47 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building - replaces: bug 1861184 + promote-to-proposed: Pending -- ready for review trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862213 Title: bionic/linux-gcp: 5.0.0-1031.32 -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-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: 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Tuesday, 11. February 2020 07:47 UTC reason: promote-to-proposed: Pending -- ready for review trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
We have narrowed it down to a flaw in a specific configuration setting on this NIC, so we're comparing the good and bad configurations now. Primary port: enp94s0f0 Secondary port: enp94s0f1d1 A] Good config for fault-tolerance (active-backup) bonding mode: -- Primary port = active interface; Secondary port = backup B] Bad config for fault-tolerance (active-backup) bonding mode: -- Primary port = backup interface; Secondary port = active We are consistently able to reproduce a drop rate difference with UDP pkts, for the above good/bad cases: Good Case UDP MTR Test Result - mtr --no-dns --report --report-cycles 60 --udp -s 1428 $DEST Start: 2020-02-10T10:14:01+ HOST: hostname Loss% Snt Last Avg Best Wrst StDev 1.|-- nn.nn.nnn.nnn 0.0%600.3 0.2 0.2 0.3 0.0 Bad Case UDP MTR Test Result --- mtr --no-dns --report --report-cycles 60 --udp -s 1428 $DEST Start: 2020-02-10T14:10:52+ HOST: hostname Loss% Snt Last Avg Best Wrst StDev 1.|-- nn.nn.nnn.nnn 8.3%600.3 0.3 0.2 0.4 0.0 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209]
[Kernel-packages] [Bug 1862734] Re: Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16
** Description changed: - TBD + Similar to bug 1858776 and bug 1850738, Intel(R) Wireless-AC 9560 + 160MHz, REV=0x354 [8086:02f0] subsystem [8086:4034] btusb may fail + system suspend with following error messages in dmesg: + [4.880979] Bluetooth: hci0: Bootloader revision 0.1 build 0 week 30 2018 + [4.881987] Bluetooth: hci0: Device revision is 2 + [4.881988] Bluetooth: hci0: Secure boot is enabled + [4.881989] Bluetooth: hci0: OTP lock is enabled + [4.881990] Bluetooth: hci0: API lock is enabled + [4.881991] Bluetooth: hci0: Debug lock is disabled + [4.881992] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 + [4.883480] Bluetooth: hci0: Found device firmware: intel/ibt-19-0-1.sfi + ... + [ 71.387652] PM: suspend entry (s2idle) + [ 71.387655] PM: Syncing filesystems ... done. + [ 71.395449] Freezing user space processes ... + [ 71.770699] Bluetooth: hci0: advertising data len corrected + [ 72.330683] (elapsed 0.920 seconds) done. + [ 72.330689] OOM killer disabled. + [ 72.330690] Freezing remaining freezable tasks ... (elapsed 0.014 seconds) done. + [ 72.345132] printk: Suspending console(s) (use no_console_suspend to debug) + [ 72.399557] pci_pm_suspend(): hcd_pci_suspend+0x0/0x30 returns -16 + [ 72.399566] dpm_run_callback(): pci_pm_suspend+0x0/0x150 returns -16 + [ 72.399730] PM: Device :00:14.0 failed to suspend async: error -16 + [ 72.425583] PM: Some devices failed to suspend, or early wake event detected + [ 72.486631] Bluetooth: hci0: advertising data len corrected + [ 72.611800] OOM killer enabled. + [ 72.611802] Restarting tasks ... done. + [ 72.629308] thermal thermal_zone5: failed to read out thermal zone (-61) + [ 72.663376] PM: suspend exit + [ 72.663413] PM: suspend entry (s2idle) + + This can be fixed by upgrading intel/ibt-19-0-1.sfi to REL0318 from + upstream commit c0ca980cee32. + + --- ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21 Uname: Linux 5.0.0-1037-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: u 1583 F pulseaudio + USERPID ACCESS COMMAND + /dev/snd/controlC0: u 1583 F pulseaudio Date: Tue Feb 11 02:05:47 2020 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-arya+X37 + # 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-arya+X37 InstallationDate: Installed on 2020-01-06 (35 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Latitude 7410 PackageArchitecture: all ProcEnviron: - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 root=UUID=fd4c84f6-205f-4fb2-9225-bb232ba08e38 ro quiet splash vt.handoff=1 PulseList: - Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied - No PulseAudio daemon running, or not running as session daemon. + Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied + No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: - linux-restricted-modules-5.0.0-1037-oem-osp1 N/A - linux-backports-modules-5.0.0-1037-oem-osp1 N/A - linux-firmware 1.173.14 + linux-restricted-modules-5.0.0-1037-oem-osp1 N/A + linux-backports-modules-5.0.0-1037-oem-osp1 N/A + linux-firmware 1.173.14 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.7:bd12/30/2019:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09BE dmi.sys.vendor: Dell Inc. ** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux-firmware (Ubuntu Disco) Status: New => Won't Fix ** Changed in: linux-firmware
[Kernel-packages] [Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -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: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Tuesday, 11. February 2020 04:07 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862213 Title: bionic/linux-gcp: 5.0.0-1031.32 -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-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: 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Tuesday, 11. February 2020 04:07 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:building replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862224] Re: xenial/linux-gcp: 4.15.0-1054.58 -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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 11. February 2020 03:42 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 11. February 2020 07:32 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait - replaces: bug 1861160 + promote-to-proposed: Pending -- ready for review trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862224 Title: xenial/linux-gcp: 4.15.0-1054.58 -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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Ready for Promote to Proposed phase-changed: Tuesday, 11. February 2020 07:32 UTC reason: promote-to-proposed: Pending -- ready for review trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861160] Re: xenial/linux-gcp: 4.15.0-1053.57 -proposed tracker
*** This bug is a duplicate of bug 1862224 *** https://bugs.launchpad.net/bugs/1862224 ** This bug has been marked a duplicate of bug 1862224 xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1861160 Title: xenial/linux-gcp: 4.15.0-1053.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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 verification-testing series: In Progress Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Testing phase-changed: Wednesday, 05. February 2020 16:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-gcp/gcp-kernel: bug 1861158 xenial/linux-gcp/gke-kernel: bug 1861159 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861160/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862736] [NEW] sof driver fails and print lots of errors in the dmesg (focal)
Public bug reported: Because we introduced this commit from stable patches, but only backporting this commit is not enough. Author: Ranjani Sridharan Date: Mon Nov 4 14:48:12 2019 -0800 ASoC: SOF: topology: set trigger order for FE DAI link BugLink: https://bugs.launchpad.net/bugs/1858428 [ Upstream commit 5eee2b3f60065a2530d13f28e771be48b989eb4c ] Set trigger order for FE DAI links to SND_SOC_DPCM_TRIGGER_POST to trigger the BE DAI's before the FE DAI's. This prevents the xruns seen on playback pipelines using the link DMA. Signed-off-by: Ranjani Sridharan Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191104224812.3393-3-ranjani.sridha...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Seth Forshee ** Affects: linux (Ubuntu) Importance: Undecided Assignee: Hui Wang (hui.wang) 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/1862736 Title: sof driver fails and print lots of errors in the dmesg (focal) Status in linux package in Ubuntu: New Bug description: Because we introduced this commit from stable patches, but only backporting this commit is not enough. Author: Ranjani Sridharan Date: Mon Nov 4 14:48:12 2019 -0800 ASoC: SOF: topology: set trigger order for FE DAI link BugLink: https://bugs.launchpad.net/bugs/1858428 [ Upstream commit 5eee2b3f60065a2530d13f28e771be48b989eb4c ] Set trigger order for FE DAI links to SND_SOC_DPCM_TRIGGER_POST to trigger the BE DAI's before the FE DAI's. This prevents the xruns seen on playback pipelines using the link DMA. Signed-off-by: Ranjani Sridharan Signed-off-by: Pierre-Louis Bossart Link: https://lore.kernel.org/r/20191104224812.3393-3-ranjani.sridha...@linux.intel.com Signed-off-by: Mark Brown Signed-off-by: Sasha Levin Signed-off-by: Seth Forshee To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862736/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831940] Re: hibernation support for linux-aws
** Description changed: Additional AWS-specific and mainline patches are required to support hibernation across the various types of AWS instances. The following patch sets for linux-aws-xenial and linux-aws-bionic provide the necessary functionality, and should only impact the hibernation and resume paths. [linux-aws-xenial] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. radix-tree: delete radix_tree_locate_item() mm: rid swapoff of quadratic complexity sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to wake_up() sched/wait: Avoid abort_exclusive_wait() in ___wait_event() sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock() sched/wait: Introduce init_wait_entry() sched/wait: Standardize wait_bit_queue naming sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled NVMe: Allow request merges PM / hibernate: Do not free preallocated safe pages during image restore PM / hibernate: Recycle safe pages after image restoration PM / hibernate: Simplify mark_unsafe_pages() UBUNTU: [Config] aws: disable CONFIG_TRANSPARENT_HUGEPAGE_ALWAYS UBUNTU SAUCE [aws] PM / hibernate: set image_size to total RAM size by default UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing UBUNTU SAUCE [aws] mm, page_alloc: disable fair zone allocation policy on hibernate - [linux-aws-bionic] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. mm: rid swapoff of quadratic complexity sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff netlink: Don't shift on 64 for ngroups + + [linux-aws-edge-bionic] + + UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. + UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. + UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore + UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake + UBUNTU SAUCE [aws]: PM / hibernate: set image_size to 0 by default + UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled + UBUNTU SAUCE [aws]: mm: swap: improve swap readahead heuristic + UBUNTU SAUCE [aws] PM / hibernate: reduce memory pressure during image writing + PM / hibernate: memory_bm_find_bit(): Tighten node optimisation + mm: rid swapoff of quadratic complexity + mm: refactor swap-in logic out of shmem_getpage_gfp -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1831940 Title: hibernation support for linux-aws Status in linux-aws package in Ubuntu: Fix Committed Status in linux-aws source package in Xenial: Fix Released Status in linux-aws source package in Bionic: Fix Released Status in linux-aws source package in Disco: New Bug description: Additional AWS-specific and mainline patches are required to support hibernation across the various types of AWS instances. The following patch sets for linux-aws-xenial and linux-aws-bionic provide the necessary functionality, and should only impact the hibernation and resume paths. [linux-aws-xenial] UBUNTU SAUCE [aws]: block: xen-blkfront: consider new dom0 features on restore UBUNTU SAUCE [aws]: ACPICA: Enable sleep button on ACPI legacy wake UBUNTU SAUCE [aws]: xen: restore pirqs on resume from hibernation. UBUNTU SAUCE [aws]: xen: Only restore the ACPI SCI interrupt in xen_restore_pirqs. radix-tree: delete radix_tree_locate_item() mm: rid swapoff of quadratic complexity sched/wait: Fix abort_exclusive_wait(), it should pass TASK_NORMAL to wake_up() sched/wait: Avoid abort_exclusive_wait() in ___wait_event() sched/wait: Avoid abort_exclusive_wait() in __wait_on_bit_lock() sched/wait: Introduce init_wait_entry() sched/wait: Standardize wait_bit_queue naming sched/wait: Introduce wait_var_event() mm: swapoff: shmem_unuse() stop eviction without igrab() UBUNTU SAUCE [aws]: mm: aggressive swapoff UBUNTU SAUCE [aws]: PM / hibernate: make sure pm_async is always disabled NVMe: Allow request merges PM / hibernate: Do not free preallocated safe pages during image restore PM / hibernate: Recycle safe pages after image
[Kernel-packages] [Bug 1862734] Re: Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16
** Tags added: oem-priority originate-from-1858770 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/1862734 Title: Failed to suspend once ever paired with BLE devices: PM: Device :00:14.0 failed to suspend async: error -16 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: TBD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21 Uname: Linux 5.0.0-1037-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1583 F pulseaudio Date: Tue Feb 11 02:05:47 2020 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-arya+X37 InstallationDate: Installed on 2020-01-06 (35 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Latitude 7410 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 root=UUID=fd4c84f6-205f-4fb2-9225-bb232ba08e38 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1037-oem-osp1 N/A linux-backports-modules-5.0.0-1037-oem-osp1 N/A linux-firmware 1.173.14 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.7:bd12/30/2019:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862734] [NEW] Failed to suspend once ever paired with BLE devices: PM: Device 0000:00:14.0 failed to suspend async: error -16
Public bug reported: TBD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21 Uname: Linux 5.0.0-1037-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1583 F pulseaudio Date: Tue Feb 11 02:05:47 2020 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-arya+X37 InstallationDate: Installed on 2020-01-06 (35 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Latitude 7410 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 root=UUID=fd4c84f6-205f-4fb2-9225-bb232ba08e38 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1037-oem-osp1 N/A linux-backports-modules-5.0.0-1037-oem-osp1 N/A linux-firmware 1.173.14 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.7:bd12/30/2019:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09BE dmi.sys.vendor: Dell Inc. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux-firmware (Ubuntu) Importance: Undecided Assignee: You-Sheng Yang (vicamo) Status: New ** Tags: amd64 apport-bug bionic oem-priority originate-from-1858770 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/1862734 Title: Failed to suspend once ever paired with BLE devices: PM: Device :00:14.0 failed to suspend async: error -16 Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Bug description: TBD ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.173.14 ProcVersionSignature: Ubuntu 5.0.0-1037.42-oem-osp1 5.0.21 Uname: Linux 5.0.0-1037-oem-osp1 x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: u 1583 F pulseaudio Date: Tue Feb 11 02:05:47 2020 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-arya+X37 InstallationDate: Installed on 2020-01-06 (35 days ago) InstallationMedia: Ubuntu 18.04 "Bionic" - Build amd64 LIVE Binary 20190418-12:10 MachineType: Dell Inc. Latitude 7410 PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-1037-oem-osp1 root=UUID=fd4c84f6-205f-4fb2-9225-bb232ba08e38 ro quiet splash vt.handoff=1 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-5.0.0-1037-oem-osp1 N/A linux-backports-modules-5.0.0-1037-oem-osp1 N/A linux-firmware 1.173.14 SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 0.4.7 dmi.board.vendor: Dell Inc. dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr0.4.7:bd12/30/2019:svnDellInc.:pnLatitude7410:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct10:cvr: dmi.product.family: Latitude dmi.product.name: Latitude 7410 dmi.product.sku: 09BE dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1862734/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861122] Re: xenial/linux: 4.4.0-174.204 -proposed tracker
** Tags added: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861122 Title: xenial/linux: 4.4.0-174.204 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 30. January 2020 14:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1861119 trusty/linux-lts-xenial: bug 1861121 xenial/linux-aws: bug 1861107 xenial/linux-cascade: bug 1861109 xenial/linux-fips: bug 1861116 xenial/linux-kvm: bug 1861110 xenial/linux-raspi2: bug 1861113 xenial/linux-snapdragon: bug 1861115 xenial/linux/caracalla-kernel: bug 1861103 xenial/linux/pc-kernel: bug 1861104 xenial/linux/stlouis-kernel: bug 1861105 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861063] Re: Dualshock4 controller doesn't stay connected
Thank you for the info Bastian. Now all we can do is wait for the bugfix. -- 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/1861063 Title: Dualshock4 controller doesn't stay connected Status in bluez package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Pairing the Dualshock4 controller works somehow, after several attempts. I expected this to work out of the box but it does not work well at all. Once the pairing is completed, if I try to connect it it doesn't stay connected. I have checked the dmesg and apparently there is a buffer overflow somewhere. I can pair a bluetooth headset to my laptop and the Dualshock4 pairs with my samsung tablet without problems but when I try to pair the dualshock4 to the laptop, running Ubuntu 19.10, it does not work. Dmesg output: [4.099796] Bluetooth: Core ver 2.22 [4.099833] Bluetooth: HCI device and connection manager initialized [4.099837] Bluetooth: HCI socket layer initialized [4.099839] Bluetooth: L2CAP socket layer initialized [4.099842] Bluetooth: SCO socket layer initialized [4.128978] Bluetooth: hci0: Firmware revision 0.0 build 10 week 41 2018 [6.855412] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [6.855413] Bluetooth: BNEP filters: protocol multicast [6.855416] Bluetooth: BNEP socket layer initialized [ 14.234706] Bluetooth: RFCOMM TTY layer initialized [ 14.234711] Bluetooth: RFCOMM socket layer initialized [ 14.234715] Bluetooth: RFCOMM ver 1.11 [ 117.427931] Bluetooth: Dropping L2CAP data: receive buffer overflow Release: Description: Ubuntu 19.10 Release: 19.10 Package Info: bluez: Installed: 5.50-0ubuntu4 Candidate: 5.50-0ubuntu4 Version table: *** 5.50-0ubuntu4 500 500 http://jp.archive.ubuntu.com/ubuntu eoan/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: bluez 5.50-0ubuntu4 ProcVersionSignature: Ubuntu 5.3.0-29.31-generic 5.3.13 Uname: Linux 5.3.0-29-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Jan 28 14:11:19 2020 InstallationDate: Installed on 2019-11-26 (62 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) InterestingModules: rfcomm bnep btusb bluetooth MachineType: LENOVO 20FCS33A00 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-29-generic root=/dev/mapper/linux--vg-root ro quiet splash vt.handoff=7 SourcePackage: bluez UpgradeStatus: Upgraded to eoan on 2020-01-16 (11 days ago) dmi.bios.date: 03/13/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N1FET68W (1.42 ) dmi.board.asset.tag: Not Available dmi.board.name: 20FCS33A00 dmi.board.vendor: LENOVO dmi.board.version: Not Defined dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN1FET68W(1.42):bd03/13/2019:svnLENOVO:pn20FCS33A00:pvrThinkPadX1Carbon4th:rvnLENOVO:rn20FCS33A00:rvrNotDefined:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 4th dmi.product.name: 20FCS33A00 dmi.product.sku: LENOVO_MT_20FC_BU_Think_FM_ThinkPad X1 Carbon 4th dmi.product.version: ThinkPad X1 Carbon 4th dmi.sys.vendor: LENOVO hciconfig: hci0:Type: Primary Bus: USB BD Address: E4:A7:A0:C6:7F:AE ACL MTU: 1021:4 SCO MTU: 96:6 UP RUNNING PSCAN RX bytes:8289 acl:41 sco:0 events:268 errors:0 TX bytes:9494 acl:44 sco:0 commands:163 errors:0 syslog: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1861063/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861192] Re: disco/linux: 5.0.0-41.45 -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, 30. January 2020 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 - bionic/linux-gcp: bug 1861184, bug 1862213 + bionic/linux-gcp: bug 1862213, bug 1861184 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1861178 bionic/linux-oracle-5.0: bug 1861190 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/1861192 Title: disco/linux: 5.0.0-41.45 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: 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, 30. January 2020 14:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 bionic/linux-gcp: bug 1862213, bug 1861184 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1861178 bionic/linux-oracle-5.0: bug 1861190 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861122] Re: xenial/linux: 4.4.0-174.204 -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: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 30. January 2020 14:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1861119 trusty/linux-lts-xenial: bug 1861121 xenial/linux-aws: bug 1861107 xenial/linux-cascade: bug 1861109 xenial/linux-fips: bug 1861116 xenial/linux-kvm: bug 1861110 xenial/linux-raspi2: bug 1861113 xenial/linux-snapdragon: bug 1861115 xenial/linux/caracalla-kernel: bug 1861103 xenial/linux/pc-kernel: bug 1861104 xenial/linux/stlouis-kernel: bug 1861105 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/1861122 Title: xenial/linux: 4.4.0-174.204 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux package in Ubuntu: Invalid Status in linux 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed phase: Testing phase-changed: Thursday, 30. January 2020 14:52 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress trackers: trusty/linux-aws: bug 1861119 trusty/linux-lts-xenial: bug 1861121 xenial/linux-aws: bug 1861107 xenial/linux-cascade: bug 1861109 xenial/linux-fips: bug 1861116 xenial/linux-kvm: bug 1861110 xenial/linux-raspi2: bug 1861113 xenial/linux-snapdragon: bug 1861115 xenial/linux/caracalla-kernel: bug 1861103 xenial/linux/pc-kernel: bug 1861104 xenial/linux/stlouis-kernel: bug 1861105 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861122/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861122] Re: xenial/linux: 4.4.0-174.204 -proposed tracker
4.4.0-174.204 - generic Regression test CMPL, RTB. 56 / 59 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in amd64: ubuntu_kernel_selftests - script permission issue in net (bug 1861973) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) vmx (bug 1821394) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 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_ecryptfs - proxy issue (RT#123768) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) script permission issue in net (bug 1861973) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - gicv2-mmio on X-ARM64 (bug 1828165) gicv2-mmio-3p (bug 1828027) gicv2-mmio-up (bug 1828026) pmu on ms10-34-mcdivittB0-kernel (bug 1751000) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_lxc - failed to fetch GPG key, probably FW issue ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 50 / 54 tests were run, missing: ubuntu_kvm_unit_tests, ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in i386: ubuntu_kernel_selftests - script permission issue in net (bug 1861973) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) 52 / 55 tests were run, missing: ubuntu_xfstests_btrfs, ubuntu_xfstests_ext4, ubuntu_xfstests_xfs Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ecryptfs - faild to fork child for file-concurrent.sh and directory-concurrent.sh.ext3 ubuntu_fan_smoke_test - failed to fetch file from ports.ubuntu.com, probably FW issue ubuntu_kernel_selftests - script permission issue in net (bug 1861973) ubuntu_ltp_syscalls - fallocate04, fallocate05, fsetxattr01, fdatasync03, fgetxattr01, fremovexattr01, fremovexattr02, fsync01, fsync04, fanotify13, fanotify14, fanotify15, lremovexattr01, msync04, preadv03, preadv03_64, preadv203, preadv203_64, pwritev03, pwritev03_64, setxattr01, sync03, syncfs01, sync_file_range02, copy_file_range01 (bug 1842270) fanotify06 (bug 1833028) fanotify10 (bug 1802454) move_pages12 (bug 1831043) ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Issue to note in s390x (Ubuntu on LPAR): libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) killed by signal 1 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) script permission issue in net (bug 1861973) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Issue to note in s390x (zVM): libhugetlbfs - failed 5 (Address is not hugepage, Heap not on hugepages) killed by signal 1 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) script permission issue in net (bug 1861973) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705) ubuntu_ltp_syscalls - fanotify06 (bug 1833028) fanotify10 (bug 1802454) ubuntu_seccomp - failed on s390x / PowerPC (bug 1850904) ubuntu_unionmount_ovlfs - failed with the latest code in upstream (bug 1854298) Note: * Missing s390x KVM because of bug 1859656 ** Changed in: kernel-sru-workflow/regression-testing Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin (cypressyew) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861122 Title: xenial/linux: 4.4.0-174.204 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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
[Kernel-packages] [Bug 1861136] Re: bionic/linux-snapdragon: 4.15.0-1072.79 -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 kernel-stable-master-bug: 1861165 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Promote to Proposed phase-changed: Monday, 10. February 2020 17:41 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1861135 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1861136 Title: bionic/linux-snapdragon: 4.15.0-1072.79 -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: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon 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 kernel-stable-master-bug: 1861165 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Promote to Proposed phase-changed: Monday, 10. February 2020 17:41 UTC reason: promote-to-proposed: Stalled -- ready for review trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1861135 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -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: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Tuesday, 11. February 2020 04:07 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,signed:depwait replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862213 Title: bionic/linux-gcp: 5.0.0-1031.32 -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-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: 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Tuesday, 11. February 2020 04:07 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,signed:depwait replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859561] Re: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45
** Tags removed: verification-needed-bionic verification-needed-eoan ** Tags added: verification-done-bionic verification-done-eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1859561 Title: [SRU][B/OEM-B/OEM-OSP1/D/E/Unstable] UBUNTU: SAUCE: Use native backlight on Lenovo E41-25/45 Status in HWE Next: New Status in linux package in Ubuntu: Fix Committed Status in linux-oem package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: New Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: In Progress Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Disco: Won't Fix Status in linux-oem source package in Disco: Invalid Status in linux-oem-osp1 source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in linux-oem source package in Eoan: Invalid Status in linux-oem-osp1 source package in Eoan: Invalid Bug description: SRU justification: [Impact] ACPI backlight control doesn't work on 2 Lenovo E41 laptops. [Fix] Use native backlight control instead. [Test] Verified on hardware with a positive result. [Regression Potential] Low. Add new DMI strings with positive verification. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1859561/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862725] 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 1862725 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Bionic) Status: New => Incomplete ** Tags added: bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862725 Title: Flip bionic/linux-oracle from 4.15 to 5.0 Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: Incomplete Bug description: https://canonical.my.salesforce.com/5003z23pO6v To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862224] Re: xenial/linux-gcp: 4.15.0-1054.58 -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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Tuesday, 11. February 2020 03:42 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 1861160 trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862224 Title: xenial/linux-gcp: 4.15.0-1054.58 -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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Tuesday, 11. February 2020 03:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait replaces: bug 1861160 trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862725] [NEW] Flip bionic/linux-oracle from 4.15 to 5.0
Public bug reported: https://canonical.my.salesforce.com/5003z23pO6v ** Affects: kernel-sru-workflow Importance: Undecided Assignee: Khaled El Mously (kmously) Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) 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/1862725 Title: Flip bionic/linux-oracle from 4.15 to 5.0 Status in Kernel SRU Workflow: New Status in linux package in Ubuntu: New Status in linux source package in Bionic: New Bug description: https://canonical.my.salesforce.com/5003z23pO6v To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862725/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861165] Re: bionic/linux: 4.15.0-87.87 -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: Monday, 03. February 2020 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress 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-aws: bug 1861141 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1861145 bionic/linux-ibm-gt: bug 1861149 bionic/linux-kvm: bug 1861146 bionic/linux-oem: bug 1862013 bionic/linux-oracle: bug 1861151 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1861130 bionic/linux/pc-lowlatency-kernel: bug 1861132 xenial/linux-azure: bug 1862408 - xenial/linux-gcp: bug 1862224, bug 1861160 + xenial/linux-gcp: bug 1861160, bug 1862224 xenial/linux-hwe: bug 1861164 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/1861165 Title: bionic/linux: 4.15.0-87.87 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: In Progress 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: Monday, 03. February 2020 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress 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-aws: bug 1861141 bionic/linux-fips: bug 1861152 bionic/linux-gke-4.15: bug 1861145 bionic/linux-ibm-gt: bug 1861149 bionic/linux-kvm: bug 1861146 bionic/linux-oem: bug 1862013 bionic/linux-oracle: bug 1861151 bionic/linux-raspi2: bug 1861134 bionic/linux-snapdragon: bug 1861136 bionic/linux/pc-kernel: bug 1861130 bionic/linux/pc-lowlatency-kernel: bug 1861132 xenial/linux-azure: bug 1862408 xenial/linux-gcp: bug 1861160, bug 1862224 xenial/linux-hwe: bug 1861164 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861165/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862720] Re: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel
"I/O error, dev sdb, sector 82830936 flags 0" would seem to suggest this is a hardware error (physically defective storage media sdb), have you ruled this out, yet? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862720 Title: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel Status in linux package in Ubuntu: Incomplete Bug description: coping data get io error [ OK ] Reached target Remote File Systems (Pre). [ OK ] Started Availability of block devices. [ 185.379378] kdump-tools[1695]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete Copying data :[ 421.979156] print_req_error: I/O error, dev sdb, sector 82830936 flags 0 [ 54.8 %] |[ 422.081318] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862720] 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 1862720 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862720 Title: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel Status in linux package in Ubuntu: Incomplete Bug description: coping data get io error [ OK ] Reached target Remote File Systems (Pre). [ OK ] Started Availability of block devices. [ 185.379378] kdump-tools[1695]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete Copying data :[ 421.979156] print_req_error: I/O error, dev sdb, sector 82830936 flags 0 [ 54.8 %] |[ 422.081318] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862720] Re: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel
ubuntu@infra1:~$ sudo lsblk NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINT loop0 7:00 93.1G 0 loop /var/lib/lxd/storage-pools/default sda 8:00 1.1T 0 disk ├─sda1 8:10 512M 0 part /boot/efi └─sda2 8:20 1.1T 0 part ├─infra1--vg-root 253:00 1.1T 0 lvm / └─infra1--vg-swap_1 253:10 976M 0 lvm [SWAP] sdb 8:16 0 557.9G 0 disk sdc 8:32 0 557.9G 0 disk ubuntu@infra1:~$ df -h Filesystem Size Used Avail Use% Mounted on udev 126G 0 126G 0% /dev tmpfs 26G 2.4M 26G 1% /run /dev/mapper/infra1--vg-root 1.1T 313G 729G 31% / tmpfs126G 54M 126G 1% /dev/shm tmpfs5.0M 0 5.0M 0% /run/lock tmpfs126G 0 126G 0% /sys/fs/cgroup /dev/sda1511M 6.1M 505M 2% /boot/efi tmpfs100K 0 100K 0% /var/lib/lxd/shmounts tmpfs100K 0 100K 0% /var/lib/lxd/devlxd /dev/loop094G 6.2G 86G 7% /var/lib/lxd/storage-pools/default tmpfs 26G 0 26G 0% /run/user/1000 ubuntu@infra1:~$ cd /var/crash/ ubuntu@infra1:/var/crash$ ls -lhs total 8.7M 8.7M -rw-r- 1 bind bind 8.7M Dec 24 05:39 _usr_sbin_named.115.crash ubuntu@infra1:/var/crash$ root@node1:~# kdump-config show DUMP_MODE:kdump USE_KDUMP:1 KDUMP_SYSCTL: kernel.panic_on_oops=1 KDUMP_COREDIR:/var/crash crashkernel addr: 0x400 /var/lib/kdump/vmlinuz: symbolic link to /boot/vmlinuz-5.0.0-37-generic kdump initrd: /var/lib/kdump/initrd.img: symbolic link to /var/lib/kdump/initrd.img-5.0.0-37-generic current state:ready to kdump kexec command: /sbin/kexec -p --command-line="BOOT_IMAGE=/vmlinuz-5.0.0-37-generic root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB transparent_hugepage=never solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 systemd.unit=kdump-tools-dump.service nr_cpus=1 irqpoll nousb ata_piix.prefer_ms_hyperv=0" --initrd=/var/lib/kdump/initrd.img /var/lib/kdump/vmlinuz root@node1:~# dmesg |grep -i crash [0.00] Command line: BOOT_IMAGE=/vmlinuz-5.0.0-37-generic root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB hugepagesz=1GB hugepages=192 transparent_hugepage=never solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 crashkernel=2G-:512M [0.02] Reserving 512MB of memory at 64MB for crashkernel (System RAM: 261726MB) [1.921643] Kernel command line: BOOT_IMAGE=/vmlinuz-5.0.0-37-generic root=UUID=d9281738-de5a-4564-852e-f07c29ea4817 ro default_hugepagesz=1GB hugepagesz=1GB hugepages=192 transparent_hugepage=never solcpus=4-13,32-41,18-27,46-55 console=tty0 console=ttyS0 crashkernel=2G-:512M [ 73.044719] pstore: Using crash dump compression: deflate [ 79.287259] megaraid_sas :1c:00.0: firmware crash dump : no root@node1:~# [ OK ] Reached target Remote File Systems (Pre). [ OK ] Started Availability of block devices. [ 185.379378] kdump-tools[1695]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete Copying data :[ 421.979156] print_req_error: I/O error, dev sdb, sector 82830936 flags 0 [ 54.8 %] |[ 422.081318] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. C[ 422.203707] Read-error on swap-device (8:0:4709320) opying data [ 422.284891] print_req_error: I/O error, dev sdb, sector 61463240 flags 0 [ 422.386425] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. [ 422.508953] Read-error on swap-device (8:0:2743136) : [ 55.2 %] \ [ 422.589689] print_req_error: I/O error, dev sdb, sector 4070592 flags 80700 eta: 19s[ 422.695501] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. Copying data [ 422.818144] print_req_error: I/O error, dev sdb, sector 4070744 flags 80700 [ 422.924145] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. [ 423.047007] print_req_error: I/O error, dev sda, sector 23649960 flags 80700 : [ 55.6 %] -[ 423.154494] print_req_error: I/O error, dev sda, sector 23650112 flags 80700 eta: 1[ 423.263750] print_req_error: I/O error, dev sdb, sector 65443209 flags 1001 Copying data [ 423.367832] bcache: bch_count_io_errors() sdb1: IO error on writing btree. [ 423.473080] print_req_error: I/O error, dev sdb, sector 4070712 flags 0 [ 423.575254] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. : [ 56.0 %][ 423.698447] print_req_error: I/O error, dev sda,
[Kernel-packages] [Bug 1862720] [NEW] kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel
Public bug reported: coping data get io error [ OK ] Reached target Remote File Systems (Pre). [ OK ] Started Availability of block devices. [ 185.379378] kdump-tools[1695]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete Copying data :[ 421.979156] print_req_error: I/O error, dev sdb, sector 82830936 flags 0 [ 54.8 %] |[ 422.081318] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: 18.04.3 hwe-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/1862720 Title: kernel crash dump create error on Huawei server for 18.04.3 hwe-kernel Status in linux package in Ubuntu: Incomplete Bug description: coping data get io error [ OK ] Reached target Remote File Systems (Pre). [ OK ] Started Availability of block devices. [ 185.379378] kdump-tools[1695]: Starting kdump-tools: * running makedumpfile -c -d 31 /proc/vmcore /var/crash/201912310519/dump-incomplete Copying data :[ 421.979156] print_req_error: I/O error, dev sdb, sector 82830936 flags 0 [ 54.8 %] |[ 422.081318] bcache: bch_count_io_errors() sdb1: IO error on reading from cache, recovering. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862720/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** 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: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Tuesday, 11. February 2020 03:22 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 11. February 2020 04:07 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-lrm: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862213 Title: bionic/linux-gcp: 5.0.0-1031.32 -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-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: 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Tuesday, 11. February 2020 04:07 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,main:building,signed:depwait replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862312] Re: Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel
Issue NOT spotted on 4.15 GKE (4.15.0-1051.54), X-4.15 GCP (4.15.0-1053.57) Spotted on B-4.15 AWS (4.15.0-1059.61) with instance r5.large -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862312 Title: Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: It looks like memory-hotplug test in ubuntu_kernel_selftests will trigger this issue. This issue cannot be reproduced with the kernel in -updates, but can be reproduced quite easily with the proposed kernel (X-4.15 Oracle 4.15.0-1032.35~16.04.1). This was spotted on the following kernels (for now): * X-oracle-4.15 * B * B-oracle-4.15 It's not very easy to spot this as the jenkins job will just hang and you won't see the test result on the report page, for example the jenkins job "sru-misc__B_ppc64el-generic__using_baltar__for_kernel" hung at the same spot (the beginning of the KVM unit test) for two out of two attempts: 05:06:37 INFO | GOODubuntu_kvm_unit_tests.setup ubuntu_kvm_unit_tests.setup timestamp=1580792797localtime=Feb 04 05:06:37 completed successfully 05:06:37 INFO | END GOODubuntu_kvm_unit_tests.setup ubuntu_kvm_unit_tests.setup timestamp=1580792797localtime=Feb 04 05:06:37 05:06:37 DEBUG| Persistent state client._record_indent now set to 1 05:06:37 DEBUG| Persistent state client.unexpected_reboot deleted 05:06:37 INFO | START ubuntu_kvm_unit_tests.emulator ubuntu_kvm_unit_tests.emulator timestamp=1580792797localtime=Feb 04 05:06:37 05:06:37 DEBUG| Persistent state client._record_indent now set to 2 05:06:37 DEBUG| Persistent state client.unexpected_reboot now set to ('ubuntu_kvm_unit_tests.emulator', 'ubuntu_kvm_unit_tests.emulator') 05:06:37 DEBUG| Running 'kvm-ok' 05:06:37 DEBUG| [stdout] INFO: /dev/kvm exists 05:06:37 DEBUG| [stdout] KVM acceleration can be used 05:06:37 DEBUG| Running 'ppc64_cpu --smt=off' Build was aborted Check the syslog, there is a call trace before the test_bpf and after page offline: [ 1195.321441] Offlined Pages 4096 [ 1195.335056] Offlined Pages 4096 [ 1195.354614] Offlined Pages 4096 [ 1198.491967] Offlined Pages 4096 [ 1199.457587] Injecting error (-12) to MEM_GOING_ONLINE [ 1200.473838] [ cut here ] [ 1200.473841] kernel BUG at /build/linux-CWyQTi/linux-4.15.0/kernel/rcu/sync.c:128! [ 1200.473909] Oops: Exception in kernel mode, sig: 5 [#1] [ 1200.473953] LE SMP NR_CPUS=2048 NUMA PowerNV [ 1200.473999] Modules linked in: memory_notifier_error_inject notifier_error_inject overlay veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter binfmt_misc joydev input_leds mac_hid idt_89hpesx opal_prd ofpart at24 cmdlinepart powernv_flash ipmi_powernv uio_pdrv_genirq uio mtd ipmi_devintf ibmpowernv ipmi_msghandler sch_fq_codel vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas ast i2c_algo_bit hid_generic ttm drm_kms_helper [ 1200.474641] syscopyarea usbhid sysfillrect sysimgblt hid fb_sys_fops crct10dif_vpmsum crc32c_vpmsum drm i40e aacraid [last unloaded: test_bpf] [ 1200.474792] CPU: 12 PID: 139071 Comm: mem-on-off-test Not tainted 4.15.0-87-generic #87-Ubuntu [ 1200.474894] NIP: c01a8490 LR: c01a8478 CTR: c026c5e0 [ 1200.474981] REGS: c00c830ff7c0 TRAP: 0700 Not tainted (4.15.0-87-generic) [ 1200.475084] MSR: 9282b033 CR: 28222888 XER: 2004 [ 1200.475219] CFAR: c001940c SOFTE: 1 [ 1200.475219] GPR00: c01a8434 c00c830ffa40 c172c900 0001 [ 1200.475219] GPR04: 01f0 c00c7a4d2480 28228882 c001e730 [ 1200.475219] GPR08: 000ff9a1 0001 c00c61bab790 [ 1200.475219] GPR12: 2000 cfa88400 058d97936070 [ 1200.475219] GPR16: 058d6b6e9690 058d6b776ab0 058d6b7a8204 058d6b776ae8 [ 1200.475219] GPR20: 058d6b7ad5d8 0001 7fffd1cb80e4 [ 1200.475219] GPR24: 7fffd1cb80e0 c1763428 c15f6ba8 [ 1200.475219] GPR28: 0020 c15f6bb0 c15f6ba8 [ 1200.476036] NIP [c01a8490]
[Kernel-packages] [Bug 1861141] Re: bionic/linux-aws: 4.15.0-1059.61 -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 kernel-stable-master-bug: 1861165 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 03. February 2020 23:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: + regression-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1861139 bionic/linux-aws/aws-kernel: bug 1861138 xenial/linux-aws-hwe: bug 1861140 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1861141 Title: bionic/linux-aws: 4.15.0-1059.61 -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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 kernel-stable-master-bug: 1861165 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 03. February 2020 23:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1861139 bionic/linux-aws/aws-kernel: bug 1861138 xenial/linux-aws-hwe: bug 1861140 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861141] Re: bionic/linux-aws: 4.15.0-1059.61 -proposed tracker
Marked as Incomplete for possible regression (bug 1862312) ** Changed in: kernel-sru-workflow/regression-testing Status: Fix Released => Incomplete ** Tags removed: regression-testing-passed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1861141 Title: bionic/linux-aws: 4.15.0-1059.61 -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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Incomplete Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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 kernel-stable-master-bug: 1861165 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Monday, 03. February 2020 23:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1861139 bionic/linux-aws/aws-kernel: bug 1861138 xenial/linux-aws-hwe: bug 1861140 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861141/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860387] Re: [Asus ZenBook UX534FTC, Realtek ALC294, Mic, Internal] No sound at all
Hi, please follow instructions here: https://wiki.ubuntu.com/Kernel/KernelBootParameters https://askubuntu.com/questions/19486/how-do-i-add-a-kernel-boot-parameter -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860387 Title: [Asus ZenBook UX534FTC, Realtek ALC294, Mic, Internal] No sound at all Status in linux package in Ubuntu: Confirmed Bug description: There is no sound, although everything is displayed ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.0.0-23-generic 5.0.0-23.24~18.04.1 ProcVersionSignature: Ubuntu 5.0.0-23.24~18.04.1-generic 5.0.15 Uname: Linux 5.0.0-23-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: XFCE Date: Tue Jan 21 00:32:46 2020 InstallationDate: Installed on 2020-01-20 (0 days ago) InstallationMedia: Xubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860387/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862224] Re: xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** 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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Packaging - phase-changed: Tuesday, 11. February 2020 02:56 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 11. February 2020 03:42 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait replaces: bug 1861160 trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862224 Title: xenial/linux-gcp: 4.15.0-1054.58 -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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Holding before Promote to Proposed phase-changed: Tuesday, 11. February 2020 03:42 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait replaces: bug 1861160 trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862407] Re: trusty/linux-azure: 4.15.0-1070.75~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 -- + boot-testing-requested: true kernel-stable-master-bug: 1862408 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 10. February 2020 23:28 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait + promote-to-proposed: Holding -- master bug not ready for proposed 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/1862407 Title: trusty/linux-azure: 4.15.0-1070.75~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 -- boot-testing-requested: true kernel-stable-master-bug: 1862408 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 10. February 2020 23:28 UTC reason: promote-to-proposed: Holding -- master bug not ready for proposed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal
** 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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Confirmed Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534817] Could not create tracefs 'print-parent' entry [0.534817]
[Kernel-packages] [Bug 1859754] Re: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines)
For 18.04 and 19.10, the alsa-lib only supports ucm, Intel audio team write the ucm confs and this is sth I plan to SRU to Eoan and Bionic in this bug. For 20.04, we choose alsa-lib-1.2.1.2, it supports ucm2, and upstream writes the ucm2 confs based on the Intel audio team's work, we use #1862505 to track it. So the ucm for bionic and eoan is not backported from ucm2 of 1.2.1.2, it is maintained by Intel: https://github.com/thesofproject/alsa-ucm- conf.git the ucm2 for focal is maintained by upstream: https://github.com/alsa- project/alsa-ucm-conf.git, it is written based on the Intel's work. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-lib in Ubuntu. https://bugs.launchpad.net/bugs/1859754 Title: add ucm to make alsa/sof driver work under PA (variants of Lenovo X1 Carbon 7th, Dell cnl and cml machines) Status in alsa-lib package in Ubuntu: Fix Committed Status in alsa-lib source package in Bionic: Fix Committed Status in alsa-lib source package in Eoan: Fix Committed Bug description: This ucm is only for Eoan and Bionic, for focal and future versions, we plan to integrate the ucm2 instead of this ucm, and the ucm2 depends on the alsa-lib-1.2.1 and pluseaudio-v14, the ucm2 is under developing by the community, is not ready yet. [Impact] In the oem project, we have a couple of Lenovo and Dell machines which connect the digital mic to PCH directly, this design needs the new sound driver soc/sof, and this driver can't work under pulseaudio automatically, we need to integrate the ucm for the driver, then the sof dirver could work under pulseaudio and gnome. This ucm is maintained by intel audio team, and it is not upstreamed and will not be upstreamed, since the community is developing the ucm2 which is based on at least alsa-lib-1.2.1 and pulseaudio-v14.0 (still under developing), for bionic and eoan, we have to integrate this ucm since the alsa-lib version is too low. For focal and future version, we are going to integrate the ucm2 after the ucm2 is ready. This ucm is already verified in the oem project, now it is time to put it into the stock ubuntu. [Fix] These ucm files are backported from sof_ucm1 branch of https://github.com/thesofproject/alsa-ucm-conf.git [Test Case] Boot the eoan kernel or oem-osp1-bionic kernel, then check the log of pulseaudio, the ucm files are loaded successfully, then check the gnome-sound-setting, both output and input devices work well. [Regression Risk] Low, just add some new ucm files, and this will not affect other machines, and those new added ucm files are only used by specific machines which enable the sof driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1859754/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker
** Summary changed: - bionic/linux-gcp: -proposed tracker + bionic/linux-gcp: 5.0.0-1031.32 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-lrm Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-lrm Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862213 Title: bionic/linux-gcp: 5.0.0-1031.32 -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: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 11. February 2020 03:22 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862213] Re: bionic/linux-gcp: 5.0.0-1031.32 -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: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Packaging - phase-changed: Thursday, 06. February 2020 17:12 UTC + phase: Packaging + phase-changed: Tuesday, 11. February 2020 03:22 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-lrm: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862213 Title: bionic/linux-gcp: 5.0.0-1031.32 -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: In Progress Status in Kernel SRU Workflow prepare-package-lrm series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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 -- kernel-stable-master-bug: 1861192 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 11. February 2020 03:22 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-lrm: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1861184 trackers: bionic/linux-gcp/gcp-kernel: bug 1862212 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862213/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862708] Lsusb.txt
apport information ** Attachment added: "Lsusb.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327189/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1862708] ProcInterrupts.txt
apport information ** Attachment added: "ProcInterrupts.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327194/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327199/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1862708] ProcModules.txt
apport information ** Attachment added: "ProcModules.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327195/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7
[Kernel-packages] [Bug 1862708] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327193/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] PciMultimedia.txt
apport information ** Attachment added: "PciMultimedia.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327192/+files/PciMultimedia.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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327197/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1862708] Card0.Amixer.values.txt
apport information ** Attachment added: "Card0.Amixer.values.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327183/+files/Card0.Amixer.values.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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] Card0.Codecs.codec.2.txt
apport information ** Attachment added: "Card0.Codecs.codec.2.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327185/+files/Card0.Codecs.codec.2.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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] Lsusb-v.txt
apport information ** Attachment added: "Lsusb-v.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327191/+files/Lsusb-v.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1862708] PulseList.txt
apport information ** Attachment added: "PulseList.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327196/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1862708] Card1.Amixer.values.txt
apport information ** Attachment added: "Card1.Amixer.values.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327186/+files/Card1.Amixer.values.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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] CurrentDmesg.txt
apport information ** Attachment added: "CurrentDmesg.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327187/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7
[Kernel-packages] [Bug 1862708] Lspci.txt
apport information ** Attachment added: "Lspci.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327188/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1862708] Lsusb-t.txt
apport information ** Attachment added: "Lsusb-t.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327190/+files/Lsusb-t.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1862708] UdevDb.txt
apport information ** Attachment added: "UdevDb.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327198/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [
[Kernel-packages] [Bug 1862708] Card0.Codecs.codec.0.txt
apport information ** Attachment added: "Card0.Codecs.codec.0.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327184/+files/Card0.Codecs.codec.0.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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] CRDA.txt
apport information ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327182/+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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534817]
[Kernel-packages] [Bug 1862712] Re: change the ASoC card name and card longname to meet the requirement of alsa-lib-1.2.1 (Focal)
** Description changed: - In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and the ucm for - this version is alsa-ucm-conf-1.2.1.2, in this package, the ucm2 folder - is named by changed card name and longname (patches are in the - v5.5-rc1). + In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and from the + alsa-lib-1.2.1, the ucm is put into a standalone package alsa-ucm-conf, + and from the 1.2.1, the alsa-lib supports the ucm2. - To make the focal kernel work with alsa-lib-1.2.1.2, we need to backport - those patches. + In the alsa-ucm-conf-1.2.1.2, the ucm2 folders are named by new + card name or longname, kernel-v5.5-rc1 has patches to change those + names to new names. now we backport them to focal kernel. + + [Impact] + booting with the focal kernel, the audio driver can't find the ucm2 + confs, that is becuase alsa-lib-1.2.1 requires new cardname and long + name, but focal kernel provides the old card names. + + [Fix] + backport 3 patches from v5.5-rc1. + + + [Test Case] + install the 20.04 daily build image, install the linux-firmware and + alsa-ucm-conf, booting with the kernel which have those 3 patches, + the alsa-lib could find the correct ucm2 confs. + + [Regression Risk] + It is low risk to focal. + If users install focal kernel to bionic or disco, it will break + the audio since the ucm in the bionic and disco still follow the old + card name and longname, we need to link a new copy ucm named by new + cardname or longname in the bionic and disco. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862712 Title: change the ASoC card name and card longname to meet the requirement of alsa-lib-1.2.1 (Focal) Status in linux package in Ubuntu: Incomplete Bug description: In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and from the alsa-lib-1.2.1, the ucm is put into a standalone package alsa-ucm-conf, and from the 1.2.1, the alsa-lib supports the ucm2. In the alsa-ucm-conf-1.2.1.2, the ucm2 folders are named by new card name or longname, kernel-v5.5-rc1 has patches to change those names to new names. now we backport them to focal kernel. [Impact] booting with the focal kernel, the audio driver can't find the ucm2 confs, that is becuase alsa-lib-1.2.1 requires new cardname and long name, but focal kernel provides the old card names. [Fix] backport 3 patches from v5.5-rc1. [Test Case] install the 20.04 daily build image, install the linux-firmware and alsa-ucm-conf, booting with the kernel which have those 3 patches, the alsa-lib could find the correct ucm2 confs. [Regression Risk] It is low risk to focal. If users install focal kernel to bionic or disco, it will break the audio since the ucm in the bionic and disco still follow the old card name and longname, we need to link a new copy ucm named by new cardname or longname in the bionic and disco. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862708] AplayDevices.txt
apport information ** Attachment added: "AplayDevices.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327180/+files/AplayDevices.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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7
[Kernel-packages] [Bug 1862708] ArecordDevices.txt
apport information ** Attachment added: "ArecordDevices.txt" https://bugs.launchpad.net/bugs/1862708/+attachment/5327181/+files/ArecordDevices.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/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man
[Kernel-packages] [Bug 1862708] Re: tracing doesn't work on focal
apport information ** Tags added: apport-collected ** Description changed: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534817] Could not create tracefs 'print-parent' entry [0.534817] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534818] Could not create tracefs 'sym-offset' entry [0.534819] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534819] Could not create tracefs 'sym-addr' entry [0.534820]
[Kernel-packages] [Bug 1862715] Re: mac mini late 2009 usb 2.0 devices detected as 1.0, run slow
this apparently affects only a few devices, let me collect more info and reopen ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862715 Title: mac mini late 2009 usb 2.0 devices detected as 1.0, run slow Status in linux package in Ubuntu: Invalid Bug description: I've got ubuntu 18.04 LTS installed on an old 2009 mac mini. Any USB 2.0 device I plug into the mac is detected, but runs at usb 1.0 speeds. I see ehci hubs in lsusb, but the ohci hubs seem to "grab" whatever device I plug in. lspci --tree /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M |__ Port 1: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=, 12M |__ Port 1: Dev 3, If 3, Class=Application Specific Interface, Driver=, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/7p, 12M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 5: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/7p, 480M ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-76-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: armalota 8462 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Feb 11 02:38:53 2020 InstallationDate: Installed on 2020-01-17 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Apple Inc. Macmini3,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=9e36d5d6-24fd-4483-830d-9ee79b7e32eb ro RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM31.88Z.00AD.B00.0907171535 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C86C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C86C8 dmi.modalias: dmi:bvnAppleInc.:bvrMM31.88Z.00AD.B00.0907171535:bd07/17/09:svnAppleInc.:pnMacmini3,1:pvr1.0:rvnAppleInc.:rnMac-F22C86C8:rvr:cvnAppleInc.:ct16:cvrMac-F22C86C8: dmi.product.family: Macmini dmi.product.name: Macmini3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862312] Re: Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel
Thanks! I will try, but this issue was not spotted in our general kernel testing with the node we use (node rizzo). Thus it might take some time to find out an affected node first. You can run this with the source tree: $ make -C tools/testing/selftests TARGETS=memory-hotplug run_tests Ref: https://www.kernel.org/doc/html/v4.15/dev-tools/kselftest.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/1862312 Title: Segmentation fault (kernel oops) with memory-hotplug in ubuntu_kernel_selftests on Bionic kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Bug description: It looks like memory-hotplug test in ubuntu_kernel_selftests will trigger this issue. This issue cannot be reproduced with the kernel in -updates, but can be reproduced quite easily with the proposed kernel (X-4.15 Oracle 4.15.0-1032.35~16.04.1). This was spotted on the following kernels (for now): * X-oracle-4.15 * B * B-oracle-4.15 It's not very easy to spot this as the jenkins job will just hang and you won't see the test result on the report page, for example the jenkins job "sru-misc__B_ppc64el-generic__using_baltar__for_kernel" hung at the same spot (the beginning of the KVM unit test) for two out of two attempts: 05:06:37 INFO | GOODubuntu_kvm_unit_tests.setup ubuntu_kvm_unit_tests.setup timestamp=1580792797localtime=Feb 04 05:06:37 completed successfully 05:06:37 INFO | END GOODubuntu_kvm_unit_tests.setup ubuntu_kvm_unit_tests.setup timestamp=1580792797localtime=Feb 04 05:06:37 05:06:37 DEBUG| Persistent state client._record_indent now set to 1 05:06:37 DEBUG| Persistent state client.unexpected_reboot deleted 05:06:37 INFO | START ubuntu_kvm_unit_tests.emulator ubuntu_kvm_unit_tests.emulator timestamp=1580792797localtime=Feb 04 05:06:37 05:06:37 DEBUG| Persistent state client._record_indent now set to 2 05:06:37 DEBUG| Persistent state client.unexpected_reboot now set to ('ubuntu_kvm_unit_tests.emulator', 'ubuntu_kvm_unit_tests.emulator') 05:06:37 DEBUG| Running 'kvm-ok' 05:06:37 DEBUG| [stdout] INFO: /dev/kvm exists 05:06:37 DEBUG| [stdout] KVM acceleration can be used 05:06:37 DEBUG| Running 'ppc64_cpu --smt=off' Build was aborted Check the syslog, there is a call trace before the test_bpf and after page offline: [ 1195.321441] Offlined Pages 4096 [ 1195.335056] Offlined Pages 4096 [ 1195.354614] Offlined Pages 4096 [ 1198.491967] Offlined Pages 4096 [ 1199.457587] Injecting error (-12) to MEM_GOING_ONLINE [ 1200.473838] [ cut here ] [ 1200.473841] kernel BUG at /build/linux-CWyQTi/linux-4.15.0/kernel/rcu/sync.c:128! [ 1200.473909] Oops: Exception in kernel mode, sig: 5 [#1] [ 1200.473953] LE SMP NR_CPUS=2048 NUMA PowerNV [ 1200.473999] Modules linked in: memory_notifier_error_inject notifier_error_inject overlay veth xt_CHECKSUM iptable_mangle ipt_MASQUERADE nf_nat_masquerade_ipv4 iptable_nat nf_conntrack_ipv4 nf_defrag_ipv4 nf_nat_ipv4 nf_nat nf_conntrack xt_tcpudp bridge stp llc iptable_filter binfmt_misc joydev input_leds mac_hid idt_89hpesx opal_prd ofpart at24 cmdlinepart powernv_flash ipmi_powernv uio_pdrv_genirq uio mtd ipmi_devintf ibmpowernv ipmi_msghandler sch_fq_codel vmx_crypto ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi ip_tables x_tables autofs4 btrfs zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor raid6_pq libcrc32c raid1 raid0 multipath linear ses enclosure scsi_transport_sas ast i2c_algo_bit hid_generic ttm drm_kms_helper [ 1200.474641] syscopyarea usbhid sysfillrect sysimgblt hid fb_sys_fops crct10dif_vpmsum crc32c_vpmsum drm i40e aacraid [last unloaded: test_bpf] [ 1200.474792] CPU: 12 PID: 139071 Comm: mem-on-off-test Not tainted 4.15.0-87-generic #87-Ubuntu [ 1200.474894] NIP: c01a8490 LR: c01a8478 CTR: c026c5e0 [ 1200.474981] REGS: c00c830ff7c0 TRAP: 0700 Not tainted (4.15.0-87-generic) [ 1200.475084] MSR: 9282b033 CR: 28222888 XER: 2004 [ 1200.475219] CFAR: c001940c SOFTE: 1 [ 1200.475219] GPR00: c01a8434 c00c830ffa40 c172c900 0001 [ 1200.475219] GPR04: 01f0 c00c7a4d2480 28228882 c001e730 [ 1200.475219] GPR08: 000ff9a1 0001 c00c61bab790 [ 1200.475219] GPR12: 2000 cfa88400 058d97936070 [ 1200.475219] GPR16: 058d6b6e9690 058d6b776ab0 058d6b7a8204 058d6b776ae8 [ 1200.475219] GPR20: 058d6b7ad5d8 0001 7fffd1cb80e4 [ 1200.475219] GPR24:
[Kernel-packages] [Bug 1855992] Re: Enable GVE network driver for GCP kernels
** Changed in: linux-gcp (Ubuntu Xenial) Status: Confirmed => Fix Committed ** Changed in: linux-gcp (Ubuntu Bionic) Status: New => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855992 Title: Enable GVE network driver for GCP kernels Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Xenial: Fix Committed Status in linux-gcp source package in Bionic: Fix Committed Status in linux-gcp source package in Disco: Fix Released Status in linux-gcp source package in Eoan: Fix Released Bug description: Need to enable that driver for the gcp cloud kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1855992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862715] Re: mac mini late 2009 usb 2.0 devices detected as 1.0, run slow
** Attachment added: "dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862715/+attachment/5327176/+files/dmesg.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/1862715 Title: mac mini late 2009 usb 2.0 devices detected as 1.0, run slow Status in linux package in Ubuntu: Invalid Bug description: I've got ubuntu 18.04 LTS installed on an old 2009 mac mini. Any USB 2.0 device I plug into the mac is detected, but runs at usb 1.0 speeds. I see ehci hubs in lsusb, but the ohci hubs seem to "grab" whatever device I plug in. lspci --tree /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M |__ Port 1: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=, 12M |__ Port 1: Dev 3, If 3, Class=Application Specific Interface, Driver=, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/7p, 12M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 5: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/7p, 480M ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-76-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: armalota 8462 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Feb 11 02:38:53 2020 InstallationDate: Installed on 2020-01-17 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Apple Inc. Macmini3,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=9e36d5d6-24fd-4483-830d-9ee79b7e32eb ro RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM31.88Z.00AD.B00.0907171535 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C86C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C86C8 dmi.modalias: dmi:bvnAppleInc.:bvrMM31.88Z.00AD.B00.0907171535:bd07/17/09:svnAppleInc.:pnMacmini3,1:pvr1.0:rvnAppleInc.:rnMac-F22C86C8:rvr:cvnAppleInc.:ct16:cvrMac-F22C86C8: dmi.product.family: Macmini dmi.product.name: Macmini3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862224] Re: xenial/linux-gcp: 4.15.0-1054.58 -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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp - phase: Ready for Packaging - phase-changed: Thursday, 06. February 2020 18:57 UTC + phase: Packaging + phase-changed: Tuesday, 11. February 2020 02:56 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1861160 trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862224 Title: xenial/linux-gcp: 4.15.0-1054.58 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 11. February 2020 02:56 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1861160 trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862671] 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 1862671 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862671 Title: Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20 Status in linux package in Ubuntu: Incomplete Bug description: Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to version 4.20 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1454 F pulseaudio /dev/snd/pcmC0D0c: scott 1454 F...m pulseaudio Date: Mon Feb 10 12:10:52 2020 InstallationDate: Installed on 2020-01-30 (11 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LD_LIBRARY_PATH= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD 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/1862671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862715] 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/1862715 Title: mac mini late 2009 usb 2.0 devices detected as 1.0, run slow Status in linux package in Ubuntu: Confirmed Bug description: I've got ubuntu 18.04 LTS installed on an old 2009 mac mini. Any USB 2.0 device I plug into the mac is detected, but runs at usb 1.0 speeds. I see ehci hubs in lsusb, but the ohci hubs seem to "grab" whatever device I plug in. lspci --tree /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M |__ Port 1: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=, 12M |__ Port 1: Dev 3, If 3, Class=Application Specific Interface, Driver=, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/7p, 12M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 5: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/7p, 480M ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-76-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: armalota 8462 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Feb 11 02:38:53 2020 InstallationDate: Installed on 2020-01-17 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Apple Inc. Macmini3,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=9e36d5d6-24fd-4483-830d-9ee79b7e32eb ro RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM31.88Z.00AD.B00.0907171535 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C86C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C86C8 dmi.modalias: dmi:bvnAppleInc.:bvrMM31.88Z.00AD.B00.0907171535:bd07/17/09:svnAppleInc.:pnMacmini3,1:pvr1.0:rvnAppleInc.:rnMac-F22C86C8:rvr:cvnAppleInc.:ct16:cvrMac-F22C86C8: dmi.product.family: Macmini dmi.product.name: Macmini3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862715/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862224] Re: xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker
** Summary changed: - xenial/linux-gcp: -proposed tracker + xenial/linux-gcp: 4.15.0-1054.58 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1862224 Title: xenial/linux-gcp: 4.15.0-1054.58 -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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress 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 verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp 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: 1861165 packages: main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Tuesday, 11. February 2020 02:56 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded replaces: bug 1861160 trackers: xenial/linux-gcp/gcp-kernel: bug 186 xenial/linux-gcp/gke-kernel: bug 1862223 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862224/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862715] [NEW] mac mini late 2009 usb 2.0 devices detected as 1.0, run slow
Public bug reported: I've got ubuntu 18.04 LTS installed on an old 2009 mac mini. Any USB 2.0 device I plug into the mac is detected, but runs at usb 1.0 speeds. I see ehci hubs in lsusb, but the ohci hubs seem to "grab" whatever device I plug in. lspci --tree /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M |__ Port 1: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=, 12M |__ Port 1: Dev 3, If 3, Class=Application Specific Interface, Driver=, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/7p, 12M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 5: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/7p, 480M ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-76-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: armalota 8462 F pulseaudio Card0.Amixer.info: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Card0.Amixer.values: Error: [Errno 2] No such file or directory: 'amixer': 'amixer' Date: Tue Feb 11 02:38:53 2020 InstallationDate: Installed on 2020-01-17 (24 days ago) InstallationMedia: Ubuntu-Server 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) MachineType: Apple Inc. Macmini3,1 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-76-generic root=UUID=9e36d5d6-24fd-4483-830d-9ee79b7e32eb ro RelatedPackageVersions: linux-restricted-modules-4.15.0-76-generic N/A linux-backports-modules-4.15.0-76-generic N/A linux-firmware 1.173.14 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/17/09 dmi.bios.vendor: Apple Inc. dmi.bios.version: MM31.88Z.00AD.B00.0907171535 dmi.board.asset.tag: Base Board Asset Tag# dmi.board.name: Mac-F22C86C8 dmi.board.vendor: Apple Inc. dmi.chassis.asset.tag: Asset Tag# dmi.chassis.type: 16 dmi.chassis.vendor: Apple Inc. dmi.chassis.version: Mac-F22C86C8 dmi.modalias: dmi:bvnAppleInc.:bvrMM31.88Z.00AD.B00.0907171535:bd07/17/09:svnAppleInc.:pnMacmini3,1:pvr1.0:rvnAppleInc.:rnMac-F22C86C8:rvr:cvnAppleInc.:ct16:cvrMac-F22C86C8: dmi.product.family: Macmini dmi.product.name: Macmini3,1 dmi.product.version: 1.0 dmi.sys.vendor: Apple Inc. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic uec-images -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862715 Title: mac mini late 2009 usb 2.0 devices detected as 1.0, run slow Status in linux package in Ubuntu: New Bug description: I've got ubuntu 18.04 LTS installed on an old 2009 mac mini. Any USB 2.0 device I plug into the mac is detected, but runs at usb 1.0 speeds. I see ehci hubs in lsusb, but the ohci hubs seem to "grab" whatever device I plug in. lspci --tree /: Bus 04.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/5p, 12M |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/3p, 12M |__ Port 1: Dev 3, If 0, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 1, Class=Wireless, Driver=btusb, 12M |__ Port 1: Dev 3, If 2, Class=Vendor Specific Class, Driver=, 12M |__ Port 1: Dev 3, If 3, Class=Application Specific Interface, Driver=, 12M /: Bus 03.Port 1: Dev 1, Class=root_hub, Driver=ohci-pci/7p, 12M |__ Port 1: Dev 7, If 0, Class=Vendor Specific Class, Driver=, 12M |__ Port 5: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/5p, 480M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/7p, 480M ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-76-generic 4.15.0-76.86 ProcVersionSignature: Ubuntu 4.15.0-76.86-generic 4.15.18 Uname: Linux 4.15.0-76-generic x86_64 AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-76-generic. AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64
[Kernel-packages] [Bug 1860793] Re: [amdgpu] Severe freezes that begin with minor stutters
Thanks. Unfortunately I can't yet see anything going wrong at the end there. It's interesting you say that 18.04 is unaffected. I wonder are you able to try some other kernel versions to see if that's the important factor here? https://kernel.ubuntu.com/~kernel-ppa/mainline/ ** Package changed: gnome-shell (Ubuntu) => linux (Ubuntu) ** Also affects: xserver-xorg-video-amdgpu (Ubuntu) Importance: Undecided Status: New ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: Incomplete => New ** Changed in: xserver-xorg-video-amdgpu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860793 Title: [amdgpu] Severe freezes that begin with minor stutters Status in linux package in Ubuntu: Incomplete Status in xserver-xorg-video-amdgpu package in Ubuntu: Incomplete Bug description: It starts with very subtle stuttering that you notice when moving windows around, then keeps getting worse and worse until it starts freezing the UI for many seconds. I could only reproduce it twice in a couple of days. The applications open at the time are usually Atom, Firefox, Hexchat, GNOME Files and occasionally Eye of GNOME. I checked resource consumption at the time of the stutters. Memory consumption was about 50% of 8GB, while the swap partition was nearly full (after a long gaming session). Storage device is a SATA SSD. During the stutters and freezes, CPU usage is normal. Through the process list of System Monitor I cannot see any application overusing resources. Temperatures are also normal. One potentially problematic hardware device is the GPU: AMD RX 560 4GB (open source AMDGPU). Its temperature and fan speed were also normal at the time. I know my system is capable of handling this workload. Also, this is only reproducible on Ubuntu 19.10 Eoan with GNOME. The LTS version of Ubuntu (18.04.3) is unaffected. I have used it for months before switching to the latest non-LTS version. What I've tried to stop the freezes: - Closed all running applications and waited. It didn't improve the situation, so I restarted my user session. The freezes continued, so I performed a system reboot, which finally helped normalize things. I did not try to reproduce this on the Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 11:13:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-27 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
These are just the zfs bookmark and zfs send commands from the sender. ** Attachment added: "zfs bookmark, zfs send commands" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861235/+attachment/5327157/+files/sender_limited_history -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ? syscall_trace_enter+0x1da/0x2d0 [ 967.637927] SyS_ioctl+0x79/0x90 [ 967.637930] do_syscall_64+0x73/0x130 [ 967.637935] entry_SYSCALL_64_after_hwframe+0x3d/0xa2 [ 967.637938] RIP: 0033:0x7fc305a905d7 [ 967.637940] RSP: 002b:7ffc45e39618 EFLAGS:
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
The two machines involved are: Receiver, bionic, probably running 4.15.0-76-generic and zfsutils-linux 0.7.5-1ubuntu16.7 Sender, focal, probably running 5.4.0-12-generic and zfsutils-linux 0.8.3-1ubuntu3 I'm using sanoid and syncoid to automate snapshot management and sending and receiving. The combination worked well for about a week before I got this failure. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ? syscall_trace_enter+0x1da/0x2d0 [ 967.637927] SyS_ioctl+0x79/0x90 [ 967.637930] do_syscall_64+0x73/0x130 [ 967.637935]
[Kernel-packages] [Bug 1861235] Re: zfs recv PANIC at range_tree.c:304:range_tree_find_impl()
These are all the zpool and zfs commands on the receiver except snapshots, renames, and destroys, associated with my Ubuntu archive mirror rsync. (7000-ish lines of juggling 30-snapshots. I should do something better here.) ** Attachment added: "receiver_limited_history" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861235/+attachment/5327158/+files/receiver_limited_history -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861235 Title: zfs recv PANIC at range_tree.c:304:range_tree_find_impl() Status in Linux: Unknown Status in linux package in Ubuntu: Confirmed Bug description: Same as bug 1861228 but with a newer kernel installed. [ 790.702566] VERIFY(size != 0) failed [ 790.702590] PANIC at range_tree.c:304:range_tree_find_impl() [ 790.702611] Showing stack for process 28685 [ 790.702614] CPU: 17 PID: 28685 Comm: receive_writer Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 790.702615] Hardware name: Supermicro SSG-6038R-E1CR16L/X10DRH-iT, BIOS 2.0 12/17/2015 [ 790.702616] Call Trace: [ 790.702626] dump_stack+0x6d/0x8e [ 790.702637] spl_dumpstack+0x42/0x50 [spl] [ 790.702640] spl_panic+0xc8/0x110 [spl] [ 790.702645] ? __switch_to_asm+0x41/0x70 [ 790.702714] ? arc_prune_task+0x1a/0x40 [zfs] [ 790.702740] ? dbuf_dirty+0x43d/0x850 [zfs] [ 790.702745] ? getrawmonotonic64+0x43/0xd0 [ 790.702746] ? getrawmonotonic64+0x43/0xd0 [ 790.702775] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702778] ? getrawmonotonic64+0x43/0xd0 [ 790.702805] ? dmu_zfetch+0x49a/0x500 [zfs] [ 790.702807] ? mutex_lock+0x12/0x40 [ 790.702833] ? dbuf_rele_and_unlock+0x1a8/0x4b0 [zfs] [ 790.702866] range_tree_find_impl+0x88/0x90 [zfs] [ 790.702870] ? spl_kmem_zalloc+0xdc/0x1a0 [spl] [ 790.702902] range_tree_clear+0x4f/0x60 [zfs] [ 790.702930] dnode_free_range+0x11f/0x5a0 [zfs] [ 790.702957] dmu_object_free+0x53/0x90 [zfs] [ 790.702983] dmu_free_long_object+0x9f/0xc0 [zfs] [ 790.703010] receive_freeobjects.isra.12+0x7a/0x100 [zfs] [ 790.703036] receive_writer_thread+0x6d2/0xa60 [zfs] [ 790.703040] ? set_curr_task_fair+0x2b/0x60 [ 790.703043] ? spl_kmem_free+0x33/0x40 [spl] [ 790.703048] ? kfree+0x165/0x180 [ 790.703073] ? receive_free.isra.13+0xc0/0xc0 [zfs] [ 790.703078] thread_generic_wrapper+0x74/0x90 [spl] [ 790.703081] kthread+0x121/0x140 [ 790.703084] ? __thread_exit+0x20/0x20 [spl] [ 790.703085] ? kthread_create_worker_on_cpu+0x70/0x70 [ 790.703088] ret_from_fork+0x35/0x40 [ 967.636923] INFO: task txg_quiesce:14810 blocked for more than 120 seconds. [ 967.636979] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637024] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637076] txg_quiesce D0 14810 2 0x8000 [ 967.637080] Call Trace: [ 967.637089] __schedule+0x24e/0x880 [ 967.637092] schedule+0x2c/0x80 [ 967.637106] cv_wait_common+0x11e/0x140 [spl] [ 967.637114] ? wait_woken+0x80/0x80 [ 967.637122] __cv_wait+0x15/0x20 [spl] [ 967.637210] txg_quiesce_thread+0x2cb/0x3d0 [zfs] [ 967.637278] ? txg_delay+0x1b0/0x1b0 [zfs] [ 967.637286] thread_generic_wrapper+0x74/0x90 [spl] [ 967.637291] kthread+0x121/0x140 [ 967.637297] ? __thread_exit+0x20/0x20 [spl] [ 967.637299] ? kthread_create_worker_on_cpu+0x70/0x70 [ 967.637304] ret_from_fork+0x35/0x40 [ 967.637326] INFO: task zfs:28590 blocked for more than 120 seconds. [ 967.637371] Tainted: P O 4.15.0-76-generic #86-Ubuntu [ 967.637416] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 967.637467] zfs D0 28590 28587 0x8080 [ 967.637470] Call Trace: [ 967.637474] __schedule+0x24e/0x880 [ 967.637477] schedule+0x2c/0x80 [ 967.637486] cv_wait_common+0x11e/0x140 [spl] [ 967.637491] ? wait_woken+0x80/0x80 [ 967.637498] __cv_wait+0x15/0x20 [spl] [ 967.637554] dmu_recv_stream+0xa51/0xef0 [zfs] [ 967.637630] zfs_ioc_recv_impl+0x306/0x1100 [zfs] [ 967.637679] ? dbuf_read+0x34a/0x920 [zfs] [ 967.637725] ? dbuf_rele+0x36/0x40 [zfs] [ 967.637728] ? _cond_resched+0x19/0x40 [ 967.637798] zfs_ioc_recv_new+0x33d/0x410 [zfs] [ 967.637809] ? spl_kmem_alloc_impl+0xe5/0x1a0 [spl] [ 967.637816] ? spl_vmem_alloc+0x19/0x20 [spl] [ 967.637828] ? nv_alloc_sleep_spl+0x1f/0x30 [znvpair] [ 967.637834] ? nv_mem_zalloc.isra.0+0x2e/0x40 [znvpair] [ 967.637840] ? nvlist_xalloc.part.2+0x50/0xb0 [znvpair] [ 967.637905] zfsdev_ioctl+0x451/0x610 [zfs] [ 967.637913] do_vfs_ioctl+0xa8/0x630 [ 967.637917] ? __audit_syscall_entry+0xbc/0x110 [ 967.637924] ? syscall_trace_enter+0x1da/0x2d0 [ 967.637927] SyS_ioctl+0x79/0x90 [ 967.637930] do_syscall_64+0x73/0x130 [
[Kernel-packages] [Bug 1862671] Re: Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20
** Summary changed: - Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to kernel version 4.20 + Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20 ** Package changed: pulseaudio (Ubuntu) => linux (Ubuntu) ** Tags added: regression-release -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862671 Title: Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20 Status in linux package in Ubuntu: New Bug description: Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to version 4.20 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1454 F pulseaudio /dev/snd/pcmC0D0c: scott 1454 F...m pulseaudio Date: Mon Feb 10 12:10:52 2020 InstallationDate: Installed on 2020-01-30 (11 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LD_LIBRARY_PATH= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD 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/1862671/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853638] Re: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data
The second port on the NIC definitely works as the active interface in an active-backup bonding configuration on the other NICs. At the moment, it's only this particular NIC that is seeing this problem that we know of. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853638 Title: BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: Confirmed Bug description: The issue appears to be with the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device seems to be dropping data Basically, we are dropping data, as you can see from the benchmark tool as follows: tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ ./benchmark_rate --rx_rate 10e6 --tx_rate 10e6 --duration 300 [INFO] [UHD] linux; GNU C++ version 5.4.0 20160609; Boost_105800; UHD_3.14.1.1-0-g98c7c986 [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:00.07] Creating the usrp device with: ... [INFO] [X300] X300 initialization sequence... [INFO] [X300] Maximum frame size: 1472 bytes. [INFO] [X300] Radio 1x clock: 200 MHz [INFO] [GPS] Found an internal GPSDO: LC_XO, Firmware Rev 0.929a [INFO] [0/DmaFIFO_0] Initializing block control (NOC ID: 0xF1F0D000) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1308 MB/s) [INFO] [0/DmaFIFO_0] BIST passed (Throughput: 1316 MB/s) [INFO] [0/Radio_0] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/Radio_1] Initializing block control (NOC ID: 0x12AD1001) [INFO] [0/DDC_0] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DDC_1] Initializing block control (NOC ID: 0xDDC0) [INFO] [0/DUC_0] Initializing block control (NOC ID: 0xD0C0) [INFO] [0/DUC_1] Initializing block control (NOC ID: 0xD0C0) Using Device: Single USRP: Device: X-Series Device Mboard 0: X310 RX Channel: 0 RX DSP: 0 RX Dboard: A RX Subdev: SBX-120 RX RX Channel: 1 RX DSP: 0 RX Dboard: B RX Subdev: SBX-120 RX TX Channel: 0 TX DSP: 0 TX Dboard: A TX Subdev: SBX-120 TX TX Channel: 1 TX DSP: 0 TX Dboard: B TX Subdev: SBX-120 TX [00:00:04.305374] Setting device timestamp to 0... [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.310990] Testing receive rate 10.00 Msps on 1 channels [WARNING] [UHD] Unable to set the thread priority. Performance may be negatively affected. Please see the general application notes in the manual for instructions. EnvironmentError: OSError: error in pthread_setschedparam [00:00:04.318356] Testing transmit rate 10.00 Msps on 1 channels [00:00:06.693119] Detected Rx sequence error. D[00:00:09.402843] Detected Rx sequence error. DD[00:00:40.927978] Detected Rx sequence error. D[00:01:44.982243] Detected Rx sequence error. D[00:02:11.400692] Detected Rx sequence error. D[00:02:14.805292] Detected Rx sequence error. D[00:02:41.875596] Detected Rx sequence error. D[00:03:06.927743] Detected Rx sequence error. D[00:03:47.967891] Detected Rx sequence error. D[00:03:58.233659] Detected Rx sequence error. D[00:03:58.876588] Detected Rx sequence error. D[00:04:03.139770] Detected Rx sequence error. D[00:04:45.287465] Detected Rx sequence error. D[00:04:56.425845] Detected Rx sequence error. D[00:04:57.929209] Detected Rx sequence error. [00:05:04.529548] Benchmark complete. Benchmark rate summary: Num received samples: 2995435936 Num dropped samples: 4622800 Num overruns detected:0 Num transmitted samples: 3008276544 Num sequence errors (Tx): 0 Num sequence errors (Rx): 15 Num underruns detected: 0 Num late commands:0 Num timeouts (Tx):0 Num timeouts (Rx):0 Done! tcdforge@x310a:/usr/local/lib/lib/uhd/examples$ In this particular case description, the nodes are USRP x310s. However, we have the same issue with N210 nodes dropping samples connected to the BCM57416 NetXtreme-E Dual-Media 10G RDMA Ethernet device. There is no problem with the USRPs themselves, as we have tested them with normal 1G network cards and have no dropped samples. Personally I think its something to do with the 10G network card, possibly on a ubuntu driver??? Note, Dell have said there is no hardware problem with the 10G interfaces I have followed the troubleshooting information on
[Kernel-packages] [Bug 1862671] [NEW] Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20
You have been subscribed to a public bug: Internel mic/audio doesn't work in Asus with Ubuntu 18.04. It works only when downgrading the kernel to version 4.20 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: pulseaudio 1:11.1-1ubuntu7.4 ProcVersionSignature: Ubuntu 5.3.0-28.30~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-28-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: scott 1454 F pulseaudio /dev/snd/pcmC0D0c: scott 1454 F...m pulseaudio Date: Mon Feb 10 12:10:52 2020 InstallationDate: Installed on 2020-01-30 (11 days ago) InstallationMedia: Ubuntu 18.04.3 LTS "Bionic Beaver" - Release amd64 (20190805) ProcEnviron: LD_LIBRARY_PATH= TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: Home directory not accessible: Permission denied No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/03/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: GL703VD.304 dmi.board.asset.tag: ATN12345678901234567 dmi.board.name: GL703VD dmi.board.vendor: ASUSTeK COMPUTER INC. dmi.board.version: 1.0 dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: ASUSTeK COMPUTER INC. dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrGL703VD.304:bd10/03/2017:svnASUSTeKCOMPUTERINC.:pnGL703VD:pvr1.0:rvnASUSTeKCOMPUTERINC.:rnGL703VD:rvr1.0:cvnASUSTeKCOMPUTERINC.:ct10:cvr1.0: dmi.product.family: GL dmi.product.name: GL703VD dmi.product.version: 1.0 dmi.sys.vendor: ASUSTeK COMPUTER INC. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic -- Internal mic/audio doesn't work in Asus with Ubuntu 18.04 kernel 5.3. It works only when downgrading the kernel to kernel version 4.20 https://bugs.launchpad.net/bugs/1862671 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855992] Re: Enable GVE network driver for GCP kernels
Re-opening this bug for Xenial and Bionic, to apply one additional GVE patch to both kernels. ** Changed in: linux-gcp (Ubuntu Xenial) Status: Fix Released => Confirmed ** Also affects: linux-gcp (Ubuntu Bionic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1855992 Title: Enable GVE network driver for GCP kernels Status in linux-gcp package in Ubuntu: Fix Released Status in linux-gcp source package in Xenial: Confirmed Status in linux-gcp source package in Bionic: New Status in linux-gcp source package in Disco: Fix Released Status in linux-gcp source package in Eoan: Fix Released Bug description: Need to enable that driver for the gcp cloud kernels. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-gcp/+bug/1855992/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860793] [NEW] [amdgpu] Severe freezes that begin with minor stutters
You have been subscribed to a public bug: It starts with very subtle stuttering that you notice when moving windows around, then keeps getting worse and worse until it starts freezing the UI for many seconds. I could only reproduce it twice in a couple of days. The applications open at the time are usually Atom, Firefox, Hexchat, GNOME Files and occasionally Eye of GNOME. I checked resource consumption at the time of the stutters. Memory consumption was about 50% of 8GB, while the swap partition was nearly full (after a long gaming session). Storage device is a SATA SSD. During the stutters and freezes, CPU usage is normal. Through the process list of System Monitor I cannot see any application overusing resources. Temperatures are also normal. One potentially problematic hardware device is the GPU: AMD RX 560 4GB (open source AMDGPU). Its temperature and fan speed were also normal at the time. I know my system is capable of handling this workload. Also, this is only reproducible on Ubuntu 19.10 Eoan with GNOME. The LTS version of Ubuntu (18.04.3) is unaffected. I have used it for months before switching to the latest non-LTS version. What I've tried to stop the freezes: - Closed all running applications and waited. It didn't improve the situation, so I restarted my user session. The freezes continued, so I performed a system reboot, which finally helped normalize things. I did not try to reproduce this on the Wayland session. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: gnome-shell 3.34.1+git20191024-1ubuntu1~19.10.1 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Fri Jan 24 11:13:56 2020 DisplayManager: gdm3 InstallationDate: Installed on 2019-12-27 (28 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) RelatedPackageVersions: mutter-common 3.34.3-1ubuntu1~19.10.1 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: amd64 amdgpu apport-bug eoan regression-release -- [amdgpu] Severe freezes that begin with minor stutters https://bugs.launchpad.net/bugs/1860793 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862712] 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 1862712 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862712 Title: change the ASoC card name and card longname to meet the requirement of alsa-lib-1.2.1 (Focal) Status in linux package in Ubuntu: Incomplete Bug description: In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and the ucm for this version is alsa-ucm-conf-1.2.1.2, in this package, the ucm2 folder is named by changed card name and longname (patches are in the v5.5-rc1). To make the focal kernel work with alsa-lib-1.2.1.2, we need to backport those patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862712] [NEW] change the ASoC card name and card longname to meet the requirement of alsa-lib-1.2.1 (Focal)
Public bug reported: In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and the ucm for this version is alsa-ucm-conf-1.2.1.2, in this package, the ucm2 folder is named by changed card name and longname (patches are in the v5.5-rc1). To make the focal kernel work with alsa-lib-1.2.1.2, we need to backport those patches. ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: Incomplete ** Tags: focal ** Changed in: linux (Ubuntu) Importance: Undecided => Critical ** Changed in: linux (Ubuntu) Importance: Critical => High -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862712 Title: change the ASoC card name and card longname to meet the requirement of alsa-lib-1.2.1 (Focal) Status in linux package in Ubuntu: Incomplete Bug description: In the ubuntu-20.04, we integrate the alsa-lib-1.2.1.2, and the ucm for this version is alsa-ucm-conf-1.2.1.2, in this package, the ucm2 folder is named by changed card name and longname (patches are in the v5.5-rc1). To make the focal kernel work with alsa-lib-1.2.1.2, we need to backport those patches. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862712/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1856908] Re: Sometimes my Lenovo v310 freezes completely while playing music
ok, tomorrow С уважением, Валерий Фролов ООО "АСУ-Проект", г. Челябинск www.asu-proekt.com i...@asu-proekt.com вт, 11 февр. 2020 г., 07:25 Daniel van Vugt : > Then please try 4.16-4.19 etc to further narrow down the problem. > > ** Changed in: linux (Ubuntu) >Status: Confirmed => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1856908 > > Title: > Sometimes my Lenovo v310 freezes completely while playing music > > Status in linux package in Ubuntu: > Incomplete > > Bug description: > $lsb_release -rd > Description: Ubuntu 16.04.6 LTS > Release: 16.04 > > $uname -a > Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 > UTC 2019 x86_64 x86_64 x86_64 GNU/Linux > > audacious: 3.6.2-2 > > What happened: > Sometimes my Lenovo v310 freezes completely while playing music > (Audacious). > This is something i found in syslog. > > > Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here > ] > Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active) > Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: > 14771 at > /build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 > intel_fbc_enable+0x3ed/0x570 [i915] > Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm > rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick > intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp > snd_hda_codec_hdmi kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul > ghash_clmulni_intel pcbc snd_hda_codec_realtek snd_hda_codec_generic arc4 > aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_soc_skl > intel_cstate intel_rapl_perf snd_soc_skl_ipc snd_hda_ext_core > snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress > ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core > snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo videobuf2_vmalloc > videobuf2_memops videobuf2_v4l2 snd_seq_midi snd_seq_midi_event > videobuf2_core joydev snd_rawmidi input_leds videodev serio_raw snd_seq > media wmi_bmof snd_seq_device > Dec 19 03:01:53 localhost kernel: [12615.594456] intel_wmi_thunderbolt > snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me > mei btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop > sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic > rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper > syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci > libahci wmi video > Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: > kworker/u8:0 Tainted: G OE4.15.0-73-generic #82~16.04.1-Ubuntu > Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO > 80SY/, BIOS 0ZCN30WW 12/08/2016 > Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: > events_unbound intel_atomic_commit_work [i915] > Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: > 0010:intel_fbc_enable+0x3ed/0x570 [i915] > Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: > 0018:c23fc1367cb0 EFLAGS: 00010286 > Dec 19 03:01:53 localhost kernel: [12615.594969] RAX: > RBX: a06e2a00 RCX: 97e63a28 > Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 > RSI: 0082 RDI: 0202 > Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 > R08: fffa734938d0 R09: > Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 > R11: 0367 R12: a06c56299000 > Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 > R14: a06c5629f000 R15: a06e2a00 > Dec 19 03:01:53 localhost kernel: [12615.594997] FS: > () GS:a06e3ec0() knlGS: > Dec 19 03:01:53 localhost kernel: [12615.595003] CS: 0010 DS: ES: > CR0: 80050033 > Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 > CR3: 000210a0a001 CR4: 003626f0 > Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace: > Dec 19 03:01:53 localhost kernel: [12615.595197] ? > intel_pre_plane_update+0x12f/0x190 [i915] > Dec 19 03:01:53 localhost kernel: [12615.595371] > intel_update_crtc+0x75/0xa0 [i915] > Dec 19 03:01:53 localhost kernel: [12615.595526] > skl_update_crtcs+0x1a9/0x1f0 [i915] > Dec 19 03:01:53 localhost kernel: [12615.595663] > intel_atomic_commit_tail+0x3c8/0xe00 [i915] > Dec 19 03:01:53 localhost kernel: [12615.595676] ? > __switch_to+0x9b/0x4e0 > Dec 19 03:01:53 localhost kernel: [12615.595687] ? > __switch_to_asm+0x35/0x70 > Dec 19 03:01:53 localhost kernel: [12615.595819] > intel_atomic_commit_work+0x12/0x20 [i915] > Dec 19 03:01:53 localhost kernel: [12615.595830] >
[Kernel-packages] [Bug 1856908] Re: Sometimes my Lenovo v310 freezes completely while playing music
Then please try 4.16-4.19 etc to further narrow down the problem. ** 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/1856908 Title: Sometimes my Lenovo v310 freezes completely while playing music Status in linux package in Ubuntu: Incomplete Bug description: $lsb_release -rd Description: Ubuntu 16.04.6 LTS Release: 16.04 $uname -a Linux fvg 4.15.0-73-generic #82~16.04.1-Ubuntu SMP Tue Dec 3 17:36:08 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux audacious: 3.6.2-2 What happened: Sometimes my Lenovo v310 freezes completely while playing music (Audacious). This is something i found in syslog. Dec 19 03:01:53 localhost kernel: [12615.593931] [ cut here ] Dec 19 03:01:53 localhost kernel: [12615.593947] WARN_ON(fbc->active) Dec 19 03:01:53 localhost kernel: [12615.594285] WARNING: CPU: 0 PID: 14771 at /build/linux-hwe-BQMZOc/linux-hwe-4.15.0/drivers/gpu/drm/i915/intel_fbc.c:1136 intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594289] Modules linked in: ccm rfcomm vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) bnep rtsx_usb_ms memstick intel_rapl x86_pkg_temp_thermal intel_powerclamp coretemp snd_hda_codec_hdmi kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel pcbc snd_hda_codec_realtek snd_hda_codec_generic arc4 aesni_intel aes_x86_64 crypto_simd glue_helper cryptd snd_soc_skl intel_cstate intel_rapl_perf snd_soc_skl_ipc snd_hda_ext_core snd_soc_sst_dsp snd_soc_sst_ipc snd_soc_acpi snd_soc_core snd_compress ac97_bus snd_pcm_dmaengine snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep iwlmvm mac80211 snd_pcm uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 snd_seq_midi snd_seq_midi_event videobuf2_core joydev snd_rawmidi input_leds videodev serio_raw snd_seq media wmi_bmof snd_seq_device Dec 19 03:01:53 localhost kernel: [12615.594456] intel_wmi_thunderbolt snd_timer iwlwifi snd soundcore cfg80211 shpchp intel_pch_thermal mei_me mei btusb btrtl btbcm btintel bluetooth ecdh_generic mac_hid ideapad_laptop sparse_keymap acpi_pad parport_pc ppdev lp parport autofs4 hid_generic rtsx_usb_sdmmc usbhid hid rtsx_usb i915 i2c_algo_bit drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops psmouse r8169 drm mii ahci libahci wmi video Dec 19 03:01:53 localhost kernel: [12615.594572] CPU: 0 PID: 14771 Comm: kworker/u8:0 Tainted: G OE4.15.0-73-generic #82~16.04.1-Ubuntu Dec 19 03:01:53 localhost kernel: [12615.594576] Hardware name: LENOVO 80SY/, BIOS 0ZCN30WW 12/08/2016 Dec 19 03:01:53 localhost kernel: [12615.594768] Workqueue: events_unbound intel_atomic_commit_work [i915] Dec 19 03:01:53 localhost kernel: [12615.594953] RIP: 0010:intel_fbc_enable+0x3ed/0x570 [i915] Dec 19 03:01:53 localhost kernel: [12615.594960] RSP: 0018:c23fc1367cb0 EFLAGS: 00010286 Dec 19 03:01:53 localhost kernel: [12615.594969] RAX: RBX: a06e2a00 RCX: 97e63a28 Dec 19 03:01:53 localhost kernel: [12615.594974] RDX: 0001 RSI: 0082 RDI: 0202 Dec 19 03:01:53 localhost kernel: [12615.594979] RBP: c23fc1367d00 R08: fffa734938d0 R09: Dec 19 03:01:53 localhost kernel: [12615.594984] R10: c23fc30e38e8 R11: 0367 R12: a06c56299000 Dec 19 03:01:53 localhost kernel: [12615.594989] R13: a06d4cbd6b00 R14: a06c5629f000 R15: a06e2a00 Dec 19 03:01:53 localhost kernel: [12615.594997] FS: () GS:a06e3ec0() knlGS: Dec 19 03:01:53 localhost kernel: [12615.595003] CS: 0010 DS: ES: CR0: 80050033 Dec 19 03:01:53 localhost kernel: [12615.595008] CR2: e1ad9000 CR3: 000210a0a001 CR4: 003626f0 Dec 19 03:01:53 localhost kernel: [12615.595012] Call Trace: Dec 19 03:01:53 localhost kernel: [12615.595197] ? intel_pre_plane_update+0x12f/0x190 [i915] Dec 19 03:01:53 localhost kernel: [12615.595371] intel_update_crtc+0x75/0xa0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595526] skl_update_crtcs+0x1a9/0x1f0 [i915] Dec 19 03:01:53 localhost kernel: [12615.595663] intel_atomic_commit_tail+0x3c8/0xe00 [i915] Dec 19 03:01:53 localhost kernel: [12615.595676] ? __switch_to+0x9b/0x4e0 Dec 19 03:01:53 localhost kernel: [12615.595687] ? __switch_to_asm+0x35/0x70 Dec 19 03:01:53 localhost kernel: [12615.595819] intel_atomic_commit_work+0x12/0x20 [i915] Dec 19 03:01:53 localhost kernel: [12615.595830] process_one_work+0x14d/0x410 Dec 19 03:01:53 localhost kernel: [12615.595839] worker_thread+0x4b/0x460 Dec 19 03:01:53 localhost kernel: [12615.595853] kthread+0x105/0x140 Dec 19 03:01:53 localhost kernel: [12615.595861] ? process_one_work+0x410/0x410 Dec 19
[Kernel-packages] [Bug 1861837] Re: machine doesn't come up after suspend and re-opening the lid
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: linux-oem (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1861837 Title: machine doesn't come up after suspend and re-opening the lid Status in linux package in Ubuntu: Confirmed Status in linux-oem package in Ubuntu: Confirmed Bug description: A Carbon X1 running current focal (fresh focal installation), and the linux-oem kernel doesn't come up after suspend and re-opening the lid. I have to force a power-off (holding the power button for a few seconds), and restart the machine. What information can I provide? --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-17 (17 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200117) MachineType: LENOVO 20QDCTO1WW Package: linux-oem (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-13-generic root=/dev/mapper/vgubuntu-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.4.0-13.16-generic 5.4.16 RelatedPackageVersions: linux-restricted-modules-5.4.0-13-generic N/A linux-backports-modules-5.4.0-13-generic N/A linux-firmware1.186 Tags: focal Uname: Linux 5.4.0-13-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: 11/26/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2HET42W (1.25 ) dmi.board.asset.tag: Not Available dmi.board.name: 20QDCTO1WW 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:bvrN2HET42W(1.25):bd11/26/2019:svnLENOVO:pn20QDCTO1WW:pvrThinkPadX1Carbon7th:rvnLENOVO:rn20QDCTO1WW:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 7th dmi.product.name: 20QDCTO1WW dmi.product.sku: LENOVO_MT_20QD_BU_Think_FM_ThinkPad X1 Carbon 7th dmi.product.version: ThinkPad X1 Carbon 7th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861837/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862706] Re: segfaults, dpkg script failures
I didn't know that two of my datasets were not mounted: $ zfs list -oname,canmount,mounted,mountpoint | grep 'on no' rpool/var/cache on no /var/cache rpool/var/lib/AccountsServiceon no /var/lib/AccountsService Thanks -- 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/1862706 Title: segfaults, dpkg script failures Status in zfs-linux package in Ubuntu: New Bug description: Hello, I had some apt install failures due to zfs segfaults during zfs postinst scripts: sarnold@millbarge:/var/lib$ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: ebtables libbrlapi0.6 libenchant1c2a libgspell-1-1 libxen-4.9 libxenstore3.0 linux-headers-5.3.0-29 linux-headers-5.3.0-29-generic linux-image-5.3.0-29-generic linux-modules-5.3.0-29-generic linux-modules-extra-5.3.0-29-generic linux-tools-5.3.0-29 linux-tools-5.3.0-29-generic python3-asn1crypto Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up zfsutils-linux (0.8.3-1ubuntu3) ... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-02-11 00:46:19 UTC; 5ms ago Docs: man:zfs(8) Process: 2770075 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2770075 (code=exited, status=1/FAILURE) Feb 11 00:46:19 millbarge systemd[1]: Starting Mount ZFS filesystems... Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount '/var/lib/AccountsService': Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount '/var/lib/AccountsService': mount failed Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Feb 11 00:46:19 millbarge systemd[1]: Failed to start Mount ZFS filesystems. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of zfs-initramfs: zfs-initramfs depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-initramfs (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: zfsutils-linux zfs-initramfs zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) sarnold@millbarge:/var/lib$ sudo dmesg | tail -30 [345819.461404] pci_bus :06: Allocating resources [345819.461422] pcieport :06:01.0: bridge window [mem 0x0010-0x000f] to [bus 08-3a] add_size 40 add_align 10 [345819.461424] pcieport :06:04.0: bridge window [mem 0x0010-0x000f] to [bus 3c-6f] add_size 40 add_align 10 [345819.461428] pcieport :06:01.0: BAR 14: no space for [mem size 0x0040] [345819.461428] pcieport :06:01.0: BAR 14: failed to assign [mem size 0x0040] [345819.461429] pcieport :06:04.0: BAR 14: no space for [mem size 0x0040] [345819.461430] pcieport :06:04.0: BAR 14: failed to assign [mem size 0x0040] [345819.461431] pcieport :06:04.0: BAR 14: no space for [mem size 0x0040] [345819.461432] pcieport :06:04.0: BAR 14: failed to assign [mem size 0x0040] [345819.461432] pcieport
[Kernel-packages] [Bug 1862708] 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 1862708 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862708 Title: tracing doesn't work on focal Status in linux package in Ubuntu: Incomplete Status in perf-tools-unstable package in Ubuntu: New Bug description: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785]
[Kernel-packages] [Bug 1849844] Re: seccomp test in ubuntu_kernel_selftests failed to build on D amd64
** Tags added: sru-20200127 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1849844 Title: seccomp test in ubuntu_kernel_selftests failed to build on D amd64 Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Disco: Incomplete Bug description: Test failed to build with the proposed Disco kernel with: undefined reference to `BIT' ubuntu@moe:~/ubuntu-disco/tools/testing/selftests$ sudo make run_tests make[1]: Entering directory '/home/ubuntu/ubuntu-disco/tools/testing/selftests/seccomp' gcc -Wl,-no-as-needed -Wall seccomp_bpf.c -lpthread -o seccomp_bpf seccomp_bpf.c: In function ‘user_notification_continue’: seccomp_bpf.c:3074:26: warning: overflow in conversion from ‘long int’ to ‘__s32’ {aka ‘int’} changes value from ‘116983961184613’ to ‘1936943461’ [-Woverflow] #define USER_NOTIF_MAGIC 116983961184613L ^~~~ seccomp_bpf.c:3535:15: note: in expansion of macro ‘USER_NOTIF_MAGIC’ resp.error = USER_NOTIF_MAGIC; ^~~~ /usr/bin/ld: /tmp/cc5Df3dg.o: in function `user_notification_continue': seccomp_bpf.c:(.text+0x2e226): undefined reference to `BIT' collect2: error: ld returned 1 exit status make[1]: *** [Makefile:12: seccomp_bpf] Error 1 make[1]: Leaving directory '/home/ubuntu/ubuntu-disco/tools/testing/selftests/seccomp' make: *** [Makefile:91: all] Error 2 Note that bug 1849281 looks like a different issue. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: linux-image-5.0.0-33-generic 5.0.0-33.35 ProcVersionSignature: User Name 5.0.0-33.35-generic 5.0.21 Uname: Linux 5.0.0-33-generic x86_64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Oct 25 13:38 seq crw-rw 1 root audio 116, 33 Oct 25 13:38 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay': 'aplay' ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord': 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDmesg: [ 484.024237] systemd-journald[391]: /dev/kmsg buffer overrun, some messages lost. Date: Fri Oct 25 13:50:36 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' Lsusb: Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: QEMU Standard PC (i440FX + PIIX, 1996) PciMultimedia: ProcFB: 0 cirrusdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-33-generic root=UUID=36e162f3-41b5-4487-a6dc-09ba4e37d3bf ro console=tty1 console=ttyS0 RelatedPackageVersions: linux-restricted-modules-5.0.0-33-generic N/A linux-backports-modules-5.0.0-33-generic N/A linux-firmware1.178.5 RfKill: Error: [Errno 2] No such file or directory: 'rfkill': 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/01/2014 dmi.bios.vendor: SeaBIOS dmi.bios.version: 1.10.2-1ubuntu1 dmi.chassis.type: 1 dmi.chassis.vendor: QEMU dmi.chassis.version: pc-i440fx-bionic dmi.modalias: dmi:bvnSeaBIOS:bvr1.10.2-1ubuntu1:bd04/01/2014:svnQEMU:pnStandardPC(i440FX+PIIX,1996):pvrpc-i440fx-bionic:cvnQEMU:ct1:cvrpc-i440fx-bionic: dmi.product.name: Standard PC (i440FX + PIIX, 1996) dmi.product.version: pc-i440fx-bionic dmi.sys.vendor: QEMU To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1849844/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783881] Re: ltp-syscalls: msgstress03 fails because systemd limits number of processes
** Tags added: gke -- 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/1783881 Title: ltp-syscalls: msgstress03 fails because systemd limits number of processes Status in ubuntu-kernel-tests: Triaged Status in linux package in Ubuntu: Incomplete Status in linux-azure package in Ubuntu: New Status in systemd package in Ubuntu: Incomplete Status in linux source package in Xenial: New Status in linux-azure source package in Xenial: New Status in systemd source package in Xenial: New Status in linux source package in Bionic: New Status in linux-azure source package in Bionic: New Status in systemd source package in Bionic: New Bug description: As systemd limits the number of processes, this test will fail because it can't fork enough processes. That is limited to when the test is run after logging as user 1000, then running sudo. I guess that logging as root may not cause this to happen. # ./testcases/bin/msgstress03 Fork failed (may be OK if under stress) Fork failed (may be OK if under stress) msgstress031 TFAIL : msgstress03.c:157: Fork failed (may be OK if under stress) # To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1783881/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859793] Re: bionic/linux-snapdragon: 4.15.0-1071.78 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security 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 -- boot-testing-requested: true kernel-stable-master-bug: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Promote to Security - phase-changed: Monday, 10. February 2020 17:36 UTC + phase: Ready for Promote to Security + phase-changed: Tuesday, 11. February 2020 01:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-security: Holding -- not ready for security (replication dwell) + promote-to-security: Pending -- ready to copy trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1859791 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1859793 Title: bionic/linux-snapdragon: 4.15.0-1071.78 -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-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Confirmed Status in Kernel SRU Workflow promote-to-updates series: Fix Released Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: Fix Released 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: '1860123' packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Promote to Security phase-changed: Tuesday, 11. February 2020 01:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-security: Pending -- ready to copy trackers: bionic/linux-snapdragon/dragonboard-kernel: bug 1859791 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1859793/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862407] Re: trusty/linux-azure: 4.15.0-1070.75~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: 1862408 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 10. February 2020 23:28 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 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/1862407 Title: trusty/linux-azure: 4.15.0-1070.75~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: 1862408 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 10. February 2020 23:28 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862407/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861206] Re: eoan/linux-kvm: 5.3.0-1010.11 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** 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: 1861214 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Monday, 03. February 2020 19:33 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 variant: debs -- 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/1861206 Title: eoan/linux-kvm: 5.3.0-1010.11 -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 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-kvm package in Ubuntu: Invalid Status in linux-kvm 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 kernel-stable-master-bug: 1861214 packages: main: linux-kvm meta: linux-meta-kvm phase: Testing phase-changed: Monday, 03. February 2020 19:33 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 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861206/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861199] Re: eoan/linux-aws: 5.3.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** 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: 1861214 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 04. February 2020 14:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1861198 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1861199 Title: eoan/linux-aws: 5.3.0-1011.12 -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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-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-aws package in Ubuntu: Invalid Status in linux-aws 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 04. February 2020 14:53 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-5.3: bug 1861198 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861199/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
Re: [Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use
> What do you have in /proc/sys/vm/swappiness? Could you try to set that > to 0 (kernel prefers to drop file-backed pages instead of swapping out > anonymous pages) and see if the swap out activity is still happening? Unfortunately, this did not solve the problem. Setting swappiness to 0 and re-enabling my swap nearly immediately caused the whole computer to lag whenever firefox had focus -- and swap use jumped to 380M, despite having roughly five gigs free space. Turning swap back off again helped immensely. Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861359 Title: swap storms kills interactive use Status in linux package in Ubuntu: Confirmed Bug description: Hello, several times since upgrading to focal from 19.04 I've found my computer entirely unresponsive for periods of twenty or thirty seconds. No mouse movement, no keyboard input, the screen output does not change. My computer was using swap space and despite very slow writeout speeds well below what the NVME drive can handle, the computer was unusable. I've captured some vmstat 1 output and top output that I started collecting during the event. (Normally one very long painful period is followed by several shorter periods of uselessness.) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Wed Jan 29 23:44:05 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) UserGroups: adm cdrom libvirt lpadmin plugdev sambashare sbuild sudo _MarkForUpload: True dmi.bios.date: 11/25/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET69W (1.44 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KHCTO1WW dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN23ET69W(1.44):bd11/25/2019:svnLENOVO:pn20KHCTO1WW:pvrThinkPadX1Carbon6th:rvnLENOVO:rn20KHCTO1WW:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Carbon 6th dmi.product.name: 20KHCTO1WW dmi.product.sku: LENOVO_MT_20KH_BU_Think_FM_ThinkPad X1 Carbon 6th dmi.product.version: ThinkPad X1 Carbon 6th dmi.sys.vendor: LENOVO --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285'
[Kernel-packages] [Bug 1861208] Re: eoan/linux-oracle: 5.3.0-1009.10 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: Incomplete => Fix Released ** 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: 1861214 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Tuesday, 04. February 2020 16:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Stalled -- testing FAILED security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1861207 variant: debs -- 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/1861208 Title: eoan/linux-oracle: 5.3.0-1009.10 -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-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: Invalid Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle 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 kernel-stable-master-bug: 1861214 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Testing phase-changed: Tuesday, 04. February 2020 16:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: security-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-oracle-5.3: bug 1861207 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861208/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862708] [NEW] tracing doesn't work on focal
Public bug reported: Hello, while investigating bug 1861359 I tried to use kprobe-perf to troubleshoot and found that tracing doesn't work on focal: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options I'm guessing this is due to lockdown: # dmesg | grep -C2 -i lockdown [0.00] efi: TPMFinalLog=0x9ff92000 SMBIOS=0x9f05d000 SMBIOS 3.0=0x9f05a000 ACPI=0x9fffe000 ACPI 2.0=0x9fffe014 ESRT=0x9eee7000 MEMATTR=0x99c76018 TPMEventLog=0x931f7018 [0.00] secureboot: Secure boot enabled [0.00] Kernel is locked down from EFI Secure Boot mode; see man kernel_lockdown.7 [0.00] SMBIOS 3.0.0 present. [0.00] DMI: LENOVO 20KHCTO1WW/20KHCTO1WW, BIOS N23ET69W (1.44 ) 11/25/2019 -- [0.532664] hpet0: 8 comparators, 64-bit 24.00 MHz counter [0.534731] clocksource: Switched to clocksource tsc-early [0.534737] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534737] Could not create tracefs 'available_events' entry [0.534741] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534741] Could not create tracefs 'set_event' entry [0.534742] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534743] Could not create tracefs 'available_tracers' entry [0.534744] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534745] Could not create tracefs 'current_tracer' entry [0.534745] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534746] Could not create tracefs 'tracing_cpumask' entry [0.534747] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534747] Could not create tracefs 'trace_options' entry [0.534748] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534748] Could not create tracefs 'trace' entry [0.534749] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534750] Could not create tracefs 'trace_pipe' entry [0.534750] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534751] Could not create tracefs 'buffer_size_kb' entry [0.534752] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534752] Could not create tracefs 'buffer_total_size_kb' entry [0.534753] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534754] Could not create tracefs 'free_buffer' entry [0.534754] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534755] Could not create tracefs 'trace_marker' entry [0.534782] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534783] Could not create tracefs 'trace_marker_raw' entry [0.534783] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534784] Could not create tracefs 'trace_clock' entry [0.534785] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534785] Could not create tracefs 'tracing_on' entry [0.534786] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534786] Could not create tracefs 'timestamp_mode' entry [0.534787] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534788] Could not create tracefs 'buffer_percent' entry [0.534816] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534817] Could not create tracefs 'print-parent' entry [0.534817] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534818] Could not create tracefs 'sym-offset' entry [0.534819] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534819] Could not create tracefs 'sym-addr' entry [0.534820] Lockdown: swapper/0: use of tracefs is restricted; see man kernel_lockdown.7 [0.534820] Could not create tracefs 'verbose' entry [0.534821] Lockdown: swapper/0: use of tracefs is restricted; see man
Re: [Kernel-packages] [Bug 1861359] Re: swap storms kills interactive use
On Mon, Feb 10, 2020 at 07:53:20AM -, Andrea Righi wrote: > OK, so we know that it's not related to the memory cgroup subsystem. But this is a good instinct. It does seem to happen when eg firefox or git is in heavy memory use, not the system as a whole. > Another reason of such unexpected swapping activity could be due to > memory compaction code that is triggering some direct memory reclaim and > forcing to swap out pages. > > What do you have in /proc/sys/vm/swappiness? Could you try to set that > to 0 (kernel prefers to drop file-backed pages instead of swapping out > anonymous pages) and see if the swap out activity is still happening? $ cat /proc/sys/vm/swappiness 60 I'll try 0. > Moreover, we can do some more advanced tracing of the direct memory reclaim > code, for example: > $ sudo kprobe-perf -s 'p:shrink_node' > This doesn't work: # kprobe-perf -s 'p:shrink_node' ERROR: func shrink_node not in /sys/kernel/debug/tracing/available_filter_functions. Either it doesn't exist, or, it might be unsafe to kprobe. Exiting. Use -F to override. # ls -l /sys/kernel/debug/tracing/available_filter_functions ls: cannot access '/sys/kernel/debug/tracing/available_filter_functions': No such file or directory # find /sys/kernel/debug/tracing /sys/kernel/debug/tracing /sys/kernel/debug/tracing/instances /sys/kernel/debug/tracing/trace_stat /sys/kernel/debug/tracing/per_cpu /sys/kernel/debug/tracing/per_cpu/cpu7 /sys/kernel/debug/tracing/per_cpu/cpu6 /sys/kernel/debug/tracing/per_cpu/cpu5 /sys/kernel/debug/tracing/per_cpu/cpu4 /sys/kernel/debug/tracing/per_cpu/cpu3 /sys/kernel/debug/tracing/per_cpu/cpu2 /sys/kernel/debug/tracing/per_cpu/cpu1 /sys/kernel/debug/tracing/per_cpu/cpu0 /sys/kernel/debug/tracing/options # Thanks -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861359 Title: swap storms kills interactive use Status in linux package in Ubuntu: Confirmed Bug description: Hello, several times since upgrading to focal from 19.04 I've found my computer entirely unresponsive for periods of twenty or thirty seconds. No mouse movement, no keyboard input, the screen output does not change. My computer was using swap space and despite very slow writeout speeds well below what the NVME drive can handle, the computer was unusable. I've captured some vmstat 1 output and top output that I started collecting during the event. (Normally one very long painful period is followed by several shorter periods of uselessness.) Thanks ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-12-generic 5.4.0-12.15 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Uname: Linux 5.4.0-12-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 Date: Wed Jan 29 23:44:05 2020 ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: linux-signed-5.4 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) --- ProblemType: Bug AlsaVersion: Advanced Linux Sound Architecture Driver Version k5.4.0-12-generic. ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: sarnold2734 F pulseaudio /dev/snd/controlC1: sarnold2734 F pulseaudio Card0.Amixer.info: Card hw:0 'PCH'/'HDA Intel PCH at 0x2fe1028000 irq 145' Mixer name : 'Realtek ALC285' Components : 'HDA:10ec0285,17aa225c,0012 HDA:8086280b,80860101,0010' Controls : 53 Simple ctrls : 15 Card1.Amixer.info: Card hw:1 'Audio'/'Generic ThinkPad Dock USB Audio at usb-:00:14.0-4.2.4, high speed' Mixer name : 'USB Mixer' Components : 'USB17ef:306f' Controls : 9 Simple ctrls : 4 DistroRelease: Ubuntu 20.04 HibernationDevice: RESUME=none IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig': 'iwconfig' MachineType: LENOVO 20KHCTO1WW NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair Package: linux (not installed) ProcEnviron: TERM=rxvt-unicode-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/BOOT/ubuntu@/vmlinuz-5.4.0-12-generic root=ZFS=rpool/ROOT/ubuntu ro root=ZFS=rpool/ROOT/ubuntu quiet splash acpi_osi=! "acpi_osi=Windows 2015" vt.handoff=1 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 RelatedPackageVersions: linux-restricted-modules-5.4.0-12-generic N/A linux-backports-modules-5.4.0-12-generic N/A linux-firmware1.185 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: Upgraded to focal on 2020-01-24 (5 days ago) UserGroups: adm cdrom libvirt lpadmin
[Kernel-packages] [Bug 1862706] [NEW] segfaults, dpkg script failures
Public bug reported: Hello, I had some apt install failures due to zfs segfaults during zfs postinst scripts: sarnold@millbarge:/var/lib$ sudo apt install -f Reading package lists... Done Building dependency tree Reading state information... Done The following packages were automatically installed and are no longer required: ebtables libbrlapi0.6 libenchant1c2a libgspell-1-1 libxen-4.9 libxenstore3.0 linux-headers-5.3.0-29 linux-headers-5.3.0-29-generic linux-image-5.3.0-29-generic linux-modules-5.3.0-29-generic linux-modules-extra-5.3.0-29-generic linux-tools-5.3.0-29 linux-tools-5.3.0-29-generic python3-asn1crypto Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 3 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Setting up zfsutils-linux (0.8.3-1ubuntu3) ... zfs-import-scan.service is a disabled or a static unit, not starting it. zfs-import-scan.service is a disabled or a static unit, not starting it. Job for zfs-mount.service failed because the control process exited with error code. See "systemctl status zfs-mount.service" and "journalctl -xe" for details. invoke-rc.d: initscript zfs-mount, action "start" failed. ● zfs-mount.service - Mount ZFS filesystems Loaded: loaded (/lib/systemd/system/zfs-mount.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Tue 2020-02-11 00:46:19 UTC; 5ms ago Docs: man:zfs(8) Process: 2770075 ExecStart=/sbin/zfs mount -a (code=exited, status=1/FAILURE) Main PID: 2770075 (code=exited, status=1/FAILURE) Feb 11 00:46:19 millbarge systemd[1]: Starting Mount ZFS filesystems... Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount '/var/lib/AccountsService': Feb 11 00:46:19 millbarge zfs[2770075]: cannot mount '/var/lib/AccountsService': mount failed Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Main process exited, code=exited, status=1/FAILURE Feb 11 00:46:19 millbarge systemd[1]: zfs-mount.service: Failed with result 'exit-code'. Feb 11 00:46:19 millbarge systemd[1]: Failed to start Mount ZFS filesystems. dpkg: error processing package zfsutils-linux (--configure): installed zfsutils-linux package post-installation script subprocess returned error exit status 1 No apport report written because the error message indicates its a followup error from a previous failure. dpkg: dependency problems prevent configuration of zfs-initramfs: zfs-initramfs depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-initramfs (--configure): dependency problems - leaving unconfigured dpkg: dependency problems prevent configuration of zfs-zed: zfs-zed depends on zfsutils-linux (>= 0.8.3-1ubuntu3); however: Package zfsutils-linux is not configured yet. dpkg: error processing package zfs-zed (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: zfsutils-linux zfs-initramfs zfs-zed E: Sub-process /usr/bin/dpkg returned an error code (1) sarnold@millbarge:/var/lib$ sudo dmesg | tail -30 [345819.461404] pci_bus :06: Allocating resources [345819.461422] pcieport :06:01.0: bridge window [mem 0x0010-0x000f] to [bus 08-3a] add_size 40 add_align 10 [345819.461424] pcieport :06:04.0: bridge window [mem 0x0010-0x000f] to [bus 3c-6f] add_size 40 add_align 10 [345819.461428] pcieport :06:01.0: BAR 14: no space for [mem size 0x0040] [345819.461428] pcieport :06:01.0: BAR 14: failed to assign [mem size 0x0040] [345819.461429] pcieport :06:04.0: BAR 14: no space for [mem size 0x0040] [345819.461430] pcieport :06:04.0: BAR 14: failed to assign [mem size 0x0040] [345819.461431] pcieport :06:04.0: BAR 14: no space for [mem size 0x0040] [345819.461432] pcieport :06:04.0: BAR 14: failed to assign [mem size 0x0040] [345819.461432] pcieport :06:01.0: BAR 14: no space for [mem size 0x0040] [345819.461433] pcieport :06:01.0: BAR 14: failed to assign [mem size 0x0040] [345833.001361] show_signal_msg: 34 callbacks suppressed [345833.001363] zfs[2653666]: segfault at 0 ip 7f2ff09bbd63 sp 7f2fec900430 error 4 in libc-2.30.so[7f2ff094d000+178000] [345833.001369] Code: 48 29 f2 ff 55 70 48 85 c0 7e 4c 48 8b 93 90 00 00 00 48 01 43 10 48 83 fa ff 74 0a 48 01 d0 48 89 83 90 00 00 00 48 8b 43 08 <0f> b6 00 48 83 c4 18 5b 5d 41 5c 41 5d 41 5e 41 5f c3 0f 1f 00 0f [345833.001370] zfs[2653667]: segfault at 0 ip 7f2ff0aafa20 sp 7f2fcfff7498 error 4
[Kernel-packages] [Bug 1861156] Re: xenial/linux-azure: 4.15.0-1068.73 -proposed tracker
*** This bug is a duplicate of bug 1862408 *** https://bugs.launchpad.net/bugs/1862408 ** This bug is no longer a duplicate of bug 1862355 xenial/linux-azure: 4.15.0-1069.74 -proposed tracker ** This bug has been marked a duplicate of bug 1862408 xenial/linux-azure: 4.15.0-1070.75 -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/1861156 Title: xenial/linux-azure: 4.15.0-1068.73 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress 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: 1861165 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Wednesday, 05. February 2020 16:02 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Stalled -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: trusty/linux-azure: bug 1861155 xenial/linux-azure/azure-kernel: bug 1861154 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861156/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862408] Re: xenial/linux-azure: 4.15.0-1070.75 -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 kernel-stable-master-bug: 1861165 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 10. February 2020 22:25 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait - replaces: bug 1861156 + promote-to-proposed: Stalled -- another kernel is currently pending in Proposed trackers: trusty/linux-azure: bug 1862407 xenial/linux-azure/azure-kernel: bug 1862406 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/1862408 Title: xenial/linux-azure: 4.15.0-1070.75 -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 -- boot-testing-requested: true kernel-stable-master-bug: 1861165 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Monday, 10. February 2020 22:25 UTC reason: promote-to-proposed: Stalled -- another kernel is currently pending in Proposed trackers: trusty/linux-azure: bug 1862407 xenial/linux-azure/azure-kernel: bug 1862406 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862408/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862354] Re: trusty/linux-azure: 4.15.0-1069.74~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 -- boot-testing-requested: true kernel-stable-master-bug: 1862355 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 10. February 2020 12:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - stakeholder-signoff: Pending -- waiting for signoff + stakeholder-signoff: Stalled -- waiting for signoff 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/1862354 Title: trusty/linux-azure: 4.15.0-1069.74~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: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released 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: In Progress Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in 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: 1862355 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Monday, 10. February 2020 12:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862354/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
= linux/eoan verification = I created a multi-zone array on current eoan, then upgraded to the -proposed kernel: [4.021562] md/raid0:md0: !!! DEFAULTING TO ALTERNATE LAYOUT !!! [4.021563] md/raid0: Please set raid0.default_layout to 1 or 2 [4.021564] md/raid0: Read the following page for more information: [4.021564] md/raid0: https://wiki.ubuntu.com/Kernel/Raid0LayoutMigration I verified that the array is active. = linux/bionic verification = Similarly: [1.830003] md/raid0:md0: !!! DEFAULTING TO ALTERNATE LAYOUT !!! [1.835050] md/raid0: Please set raid0.default_layout to 1 or 2 [1.839513] md/raid0: Read the following page for more information: [1.844259] md/raid0: https://wiki.ubuntu.com/Kernel/Raid0LayoutMigration = linux/xenial verification = Similarly: [3.157653] md: raid0 personality registered for level 0 [3.170468] md/raid0:md0: !!! DEFAULTING TO ALTERNATE LAYOUT !!! [3.176180] md/raid0: Please set raid0.default_layout to 1 or 2 [3.181684] md/raid0: Read the following page for more information: [3.187394] md/raid0: https://wiki.ubuntu.com/Kernel/Raid0LayoutMigration ** Tags removed: verification-needed verification-needed-bionic verification-needed-disco verification-needed-eoan ** Tags added: verification-done verification-done-bionic verification-done-disco verification-done-eoan ** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/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: Fix Committed Status in mdadm source package in Trusty: Confirmed Status in linux source package in Xenial: Fix Committed Status in mdadm source package in Xenial: Confirmed Status in linux source package in Bionic: Fix Committed Status in mdadm source package in Bionic: Fix Released Status in linux source package in Disco: Fix Committed Status in mdadm source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed 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 =