[Kernel-packages] [Bug 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 14. February 2020 08:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff + security-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-oem in Ubuntu. https://bugs.launchpad.net/bugs/1863072 Title: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 14. February 2020 08:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1859380] Re: Sleep doesn't work on my ThinkPad X1 Yoga with Kubuntu 20.04
Here's the output as requested ** Attachment added: "journalctl output" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859380/+attachment/5328672/+files/journalctl_output-021620 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859380 Title: Sleep doesn't work on my ThinkPad X1 Yoga with Kubuntu 20.04 Status in linux package in Ubuntu: Confirmed Bug description: Sleep button doesn't work at all, and when I close the lid, the screen goes black, but there's a cursor, and it doesn't respond. Had to force shut down. Operating System: Kubuntu 20.04 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.66.0 Qt Version: 5.12.5 Kernel Version: 5.4.0-9-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-10510U CPU @ 1.80GHz Memory: 15.3 GiB of RAM ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: kubuntu-desktop 1.392 ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3 Uname: Linux 5.4.0-9-generic x86_64 ApportVersion: 2.20.11-0ubuntu15 Architecture: amd64 CurrentDesktop: KDE Date: Sun Jan 12 19:24:55 2020 InstallationDate: Installed on 2020-01-03 (9 days ago) InstallationMedia: Kubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: kubuntu-meta UpgradeStatus: Upgraded to focal on 2020-01-12 (0 days ago) --- 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: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (9 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120) IwConfig: wlp0s20f3 no wireless extensions. lono wireless extensions. enp0s31f6 no wireless extensions. MachineType: LENOVO 20SA0002US Package: linux (not installed) ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-12-generic root=UUID=d3ea3aaf-4630-491b-8315-c7efa5381fdf ro quiet splash vt.handoff=7 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.186 Tags: focal Uname: Linux 5.4.0-12-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: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1859380/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863479] Re: package nvidia-compute-utils-435 (not installed) failed to install/upgrade: installed nvidia-compute-utils-435 package post-installation script subprocess returned
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1863479 Title: package nvidia-compute-utils-435 (not installed) failed to install/upgrade: installed nvidia-compute-utils-435 package post- installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: I tried to remove the package also ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-compute-utils-435 (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sun Feb 16 15:52:50 2020 ErrorMessage: installed nvidia-compute-utils-435 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: nvidia-graphics-drivers-435 Title: package nvidia-compute-utils-435 (not installed) failed to install/upgrade: installed nvidia-compute-utils-435 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-01-24 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1863479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862254] Re: focal/linux-oracle-5.4: 5.4.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862254 Title: focal/linux-oracle-5.4: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: lrm: linux-restricted-modules-oracle-5.4 main: linux-oracle-5.4 meta: linux-meta-oracle-5.4 signed: linux-signed-oracle-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:56 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862250] Re: focal/linux-azure-5.4: 5.4.0-1002.2 -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: 1862255 packages: lrm: linux-restricted-modules-azure-5.4 main: linux-azure-5.4 meta: linux-meta-azure-5.4 signed: linux-signed-azure-5.4 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 13. February 2020 08:48 UTC + phase: Promote to Proposed + phase-changed: Sunday, 16. February 2020 16:51 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862250 Title: focal/linux-azure-5.4: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: lrm: linux-restricted-modules-azure-5.4 main: linux-azure-5.4 meta: linux-meta-azure-5.4 signed: linux-signed-azure-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:51 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856370] Re: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend
same with 440, after adding the graphics repo -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1856370 Title: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Bug description: Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590 with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5 Description: Ubuntu 19.10 Release: 19.10 nvidia driver 435 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 16:31:58 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905] Subsystem: Dell Device [1028:0905] InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861218] Re: Mini DisplayPort port not recognized on i915 driver for Linux 5.3 (Ubuntu 19.10)
The regression appears to have been resolved as of: $ uname -sr Linux 5.4.18-1-MANJARO As seen in the `uname` output this isn't on Ubuntu, but it's solved on my end by installing a more recent Linux 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/1861218 Title: Mini DisplayPort port not recognized on i915 driver for Linux 5.3 (Ubuntu 19.10) Status in linux package in Ubuntu: Confirmed Bug description: Description: Ubuntu 19.10 Release: 19.10 What I expected to happen: The Mini DisplayPort connection should appear. What happened: There appears to be no Mini DisplayPort connection. On Ubuntu 19.04 (Linux 5.0.0-x) Mini DisplayPort worked, when upgrading to Ubuntu 19.10 (Linux 5.3.0-x) it stopped working after a reboot. The computer is a Lenovo T530 with Intel(R) Core(TM) i5-3210M integrated graphics. No DP connection shows up in /sys/class/drm $ ls /sys/class/drm/ card0 card0-LVDS-1 card0-VGA-1 renderD128 version Unsurprisingly no DP connection shows up when running xrandr either. $ xrandr Screen 0: minimum 8 x 8, current 1600 x 900, maximum 32767 x 32767 LVDS1 connected primary 1600x900+0+0 (normal left inverted right x axis y axis) 340mm x 190mm ... VGA1 disconnected (normal left inverted right x axis y axis) Module parameters: $ modinfo -p i915 modeset:Use kernel modesetting [KMS] (0=disable, 1=on, -1=force vga console preference [default]) (int) enable_dc:Enable power-saving display C-states. (-1=auto [default]; 0=disable; 1=up to DC5; 2=up to DC6) (int) enable_fbc:Enable frame buffer compression for power savings (default: -1 (use per-chip default)) (int) lvds_channel_mode:Specify LVDS channel mode (0=probe BIOS [default], 1=single-channel, 2=dual-channel) (int) panel_use_ssc:Use Spread Spectrum Clock with panels [LVDS/eDP] (default: auto from VBT) (int) vbt_sdvo_panel_type:Override/Ignore selection of SDVO panel mode in the VBT (-2=ignore, -1=auto [default], index in VBT BIOS table) (int) reset:Attempt GPU resets (0=disabled, 1=full gpu reset, 2=engine reset [default]) (int) vbt_firmware:Load VBT from specified file under /lib/firmware (charp) error_capture:Record the GPU state following a hang. This information in /sys/class/drm/card/error is vital for triaging and debugging hangs. (bool) enable_hangcheck:Periodically check GPU activity for detecting hangs. WARNING: Disabling this can cause system wide hangs. (default: true) (bool) enable_psr:Enable PSR (0=disabled, 1=enabled) Default: -1 (use per-chip default) (int) force_probe:Force probe the driver for specified devices. See CONFIG_DRM_I915_FORCE_PROBE for details. (charp) alpha_support:Deprecated. See i915.force_probe. (bool) disable_power_well:Disable display power wells when possible (-1=auto [default], 0=power wells always on, 1=power wells disabled when possible) (int) enable_ips:Enable IPS (default: true) (int) fastboot:Try to skip unnecessary mode sets at boot time (0=disabled, 1=enabled) Default: -1 (use per-chip default) (int) prefault_disable:Disable page prefaulting for pread/pwrite/reloc (default:false). For developers only. (bool) load_detect_test:Force-enable the VGA load detect code for testing (default:false). For developers only. (bool) force_reset_modeset_test:Force a modeset during gpu reset for testing (default:false). For developers only. (bool) invert_brightness:Invert backlight brightness (-1 force normal, 0 machine defaults, 1 force inversion), please report PCI device ID, subsystem vendor and subsystem device ID to dri-de...@lists.freedesktop.org, if your machine needs it. It will then be included in an upcoming module version. (int) disable_display:Disable display (default: false) (bool) mmio_debug:Enable the MMIO debug code for the first N failures (default: off). This may negatively affect performance. (int) verbose_state_checks:Enable verbose logs (ie. WARN_ON()) in case of unexpected hw state conditions. (bool) nuclear_pageflip:Force enable atomic functionality on platforms that don't have full support yet. (bool) edp_vswing:Ignore/Override vswing pre-emph table selection from VBT (0=use value from vbt [default], 1=low power swing(200mV),2=default swing(400mV)) (int) enable_guc:Enable GuC load for GuC submission and/or HuC load. Required functionality can be selected using bitmask values. (-1=auto, 0=disable [default], 1=GuC submission, 2=HuC load) (int) guc_log_level:GuC firmware logging level. Requires GuC to be loaded. (-1=auto [default], 0=disable, 1..4=enable with verbosity min..max) (int) guc_firmware_path:GuC firmware path to use instead of the default one (charp) huc_firmware_path:HuC firmware path to use instead of the default one (charp) dmc_firmware_path:DMC firmware path to use instead of the default one (charp) enable_dp_mst:Enable
[Kernel-packages] [Bug 1862252] Re: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862252 Title: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:56 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862253] Re: focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862253 Title: focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: main: linux-kvm-5.4 meta: linux-meta-kvm-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:56 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862249] Re: focal/linux-oem-5.4: 5.4.0-1003.5 -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: 1862255 packages: lrm: linux-restricted-modules-oem-5.4 main: linux-oem-5.4 meta: linux-meta-oem-5.4 signed: linux-signed-oem-5.4 - phase: Ready for Promote to Proposed - phase-changed: Tuesday, 11. February 2020 19:27 UTC + phase: Promote to Proposed + phase-changed: Sunday, 16. February 2020 16:51 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1862249 Title: focal/linux-oem-5.4: 5.4.0-1003.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oem-5.4 package in Ubuntu: Confirmed Status in linux-oem-5.4 source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-oem-5.4 main: linux-oem-5.4 meta: linux-meta-oem-5.4 signed: linux-signed-oem-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:51 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862816] Re: trusty/linux-azure: 4.15.0-1071.76~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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Proposed - phase-changed: Saturday, 15. February 2020 02:47 UTC + phase: Promote to Proposed + phase-changed: Sunday, 16. February 2020 11:31 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress 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/1862816 Title: trusty/linux-azure: 4.15.0-1071.76~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: In Progress 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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 11:31 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862816] Re: trusty/linux-azure: 4.15.0-1071.76~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed 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 -- boot-testing-requested: true kernel-stable-master-bug: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Sunday, 16. February 2020 11:31 UTC + phase: Ready for Promote to Proposed + phase-changed: Sunday, 16. February 2020 13:36 UTC reason: - promote-to-proposed: Ongoing -- package copied to Signing signed:depwait + promote-signing-to-proposed: Pending -- ready for review 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/1862816 Title: trusty/linux-azure: 4.15.0-1071.76~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: Confirmed 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: 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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Sunday, 16. February 2020 13:36 UTC reason: promote-signing-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862816] Re: trusty/linux-azure: 4.15.0-1071.76~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => 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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Promote to Proposed - phase-changed: Sunday, 16. February 2020 15:32 UTC + phase: Testing + phase-changed: Sunday, 16. February 2020 16:22 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- review in progress + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- 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/1862816 Title: trusty/linux-azure: 4.15.0-1071.76~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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Sunday, 16. February 2020 16:22 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1778087] Re: ELAN1200 touchpad jumps around and disconnects
Hello, I am still having the issue with the ELAN 1200 disconnections on my new zenbook UX533FD-A9030T. It happens every 10-40 minutes, randomly! This is my info : 5.3.0-28-generic #30~18.04.1-Ubuntu SMP Fri Jan 17 06:14:09 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux Any solution for that ? THANKS FOR THE HELP -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1778087 Title: ELAN1200 touchpad jumps around and disconnects Status in linux package in Ubuntu: Fix Released Bug description: This is on an ASUS GL503VD laptop and would probably affect other ASUS laptops equipped with the ELAN1200 touchpad. I am on Kernel 4.17.2 because older kernels did not enable the touchpad at all(It was just unrecognized or i2c-hid stopped the computer from booting) The touchpad works but it has erratic behaviour and disconnects randomly. After it disconnects the only way to bring it back is to `modprobe -r hid-multitouch && modprobe hid-multitouch` Libinput and synaptics can handle the touchpad though I found synaptics to be more stable. dmesg gets spammed with this whenever I move the touchpad: [timestamp] i2c_hid i2c-ELAN1200:00: i2c_hid_get_input: incomplete report (16/65535) I tried to compile: https://github.com/mishurov/linux_elan1200_touchpad Because from what I understand the "jumpy/disconnect" problem is associated to the incomplete reports and Mishurov managed to mitigate those. Unfortunately some symbols were deprecated in kernel 4.17.2 and it did not compile for my system. While I can use my touchpad as is right now, and "restart" it with modprobe when needed, it would be nice to have it function bug-free. (Right after I typed this my touchpad disconnected and I needed to modprobe again, I am considering making a cronjob for that) Let me know if anything else is needed. Will wait for an apport collection to add log files. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-06-10 (11 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcEnviron: TERM=screen PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash Tags: bionic Uname: Linux 4.17.2 x86_64 UnreportableReason: The running kernel is not an Ubuntu kernel UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1778087/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862250] Re: focal/linux-azure-5.4: 5.4.0-1002.2 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862250 Title: focal/linux-azure-5.4: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: lrm: linux-restricted-modules-azure-5.4 main: linux-azure-5.4 meta: linux-meta-azure-5.4 signed: linux-signed-azure-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:51 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862250/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863087] Re: i915 GPU HANG: ecode 9:1:0x00000000, hang on rcs0
I also have this bug on focal. This bug is discussed here: https://gitlab.freedesktop.org/drm/intel/issues/451 https://gitlab.freedesktop.org/drm/intel/issues/673 My `/sys/class/drm/card0/error`: GPU HANG: ecode 9:1:0x, hang on rcs0 Kernel: 5.4.0-14-generic x86_64 Driver: 20190822 Time: 1581840082 s 636802 us Boottime: 3404 s 969848 us Uptime: 3403 s 860416 us Epoch: 4295743496 jiffies (250 HZ) Capture: 4295743496 jiffies; 1198000 ms ago, 0 ms after epoch Reset count: 0 Suspend count: 0 Platform: KABYLAKE Subplatform: 0x0 PCI ID: 0x5917 PCI Revision: 0x07 PCI Subsystem: 17aa:506c IOMMU enabled?: 0 DMC loaded: yes DMC fw version: 1.4 GT awake: yes RPM wakelock: yes PM suspended: no EIR: 0x IER: 0x0808 GTIER[0]: 0x01010101 GTIER[1]: 0x01010101 GTIER[2]: 0x0070 GTIER[3]: 0x0101 PGTBL_ER: 0x FORCEWAKE: 0x00010001 DERRMR: 0x2077efef CCID: 0x fence[0] = 2fe803b0281 fence[1] = 102803b00840001 fence[2] = 47e803b0401 fence[3] = 142801f01029003 fence[4] = fence[5] = 3fe803b0381 fence[6] = 1fe803b0181 fence[7] = 4fe803b0481 fence[8] = 37e803b0301 fence[9] = fence[10] = 27e803b0201 fence[11] = fence[12] = fence[13] = fence[14] = fence[15] = fence[16] = fence[17] = fence[18] = fence[19] = fence[20] = fence[21] = fence[22] = fence[23] = fence[24] = fence[25] = fence[26] = fence[27] = fence[28] = fence[29] = fence[30] = fence[31] = ERROR: 0x0001 DONE_REG: 0x FAULT_TLB_DATA: 0x001f 0xffeec01e Num Pipes: 3 Pipe [0]: Power: on SRC: 077f0437 STAT: Plane [0]: CNTR: c4042400 STRIDE: 000f SURF: 0480 TILEOFF: Cursor [0]: CNTR: 0427 POS: 020a03ae BASE: 0080 Pipe [1]: Power: off SRC: STAT: Plane [1]: CNTR: STRIDE: SURF: TILEOFF: Cursor [1]: CNTR: POS: BASE: Pipe [2]: Power: off SRC: STAT: Plane [2]: CNTR: STRIDE: SURF: TILEOFF: Cursor [2]: CNTR: POS: BASE: CPU transcoder: A Power: off CONF: HTOTAL: HBLANK: HSYNC: VTOTAL: VBLANK: VSYNC: CPU transcoder: A Power: off CONF: HTOTAL: HBLANK: HSYNC: VTOTAL: VBLANK: VSYNC: CPU transcoder: A Power: off CONF: HTOTAL: HBLANK: HSYNC: VTOTAL: VBLANK: VSYNC: CPU transcoder: EDP Power: on CONF: c000 HTOTAL: 081f077f HBLANK: 081f077f HSYNC: 07cf07af VTOTAL: 04560437 VBLANK: 04560437 VSYNC: 043f043a is_mobile: no is_lp: no require_force_probe: no has_64bit_reloc: yes gpu_reset_clobbers_display: no has_reset_engine: yes has_fpga_dbg: yes has_global_mocs: no has_gt_uc: yes has_l3_dpf: no has_llc: yes has_logical_ring_contexts: yes has_logical_ring_elsq: no has_logical_ring_preemption: yes has_pooled_eu: no has_rc6: yes has_rc6p: no has_rps: yes has_runtime_pm: yes has_snoop: no has_coherent_ggtt: yes unfenced_needs_alignment: no hws_needs_physical: no cursor_needs_physical: no has_csr: yes has_ddi: yes has_dp_mst: yes has_fbc: yes has_gmch: no has_hotplug: yes has_ipc: yes has_modular_fia: no has_overlay: no has_psr: yes overlay_needs_physical: no supports_tv: no Has logical contexts? yes scheduler: 1f slice0: 3 subslice(s) (0x7): subslice0: 8 EUs (0xff) subslice1: 8 EUs (0xff) subslice2: 8 EUs (0xff) subslice3: 0 EUs (0x0) slice1: 0 subslice(s) (0x0): subslice0: 0 EUs (0x0) subslice1: 0 EUs (0x0) subslice2: 0 EUs (0x0) subslice3: 0 EUs (0x0) slice2: 0 subslice(s) (0x0): subslice0: 0 EUs (0x0) subslice1: 0 EUs (0x0) subslice2: 0 EUs (0x0) subslice3: 0 EUs (0x0) i915.vbt_firmware=(null) i915.modeset=-1 i915.lvds_channel_mode=0 i915.panel_use_ssc=-1 i915.vbt_sdvo_panel_type=-1 i915.enable_dc=-1 i915.enable_fbc=1 i915.enable_psr=-1 i915.disable_power_well=1 i915.enable_ips=1 i915.invert_brightness=0 i915.enable_guc=0 i915.guc_log_level=-1 i915.guc_firmware_path=(null) i915.huc_firmware_path=(null) i915.dmc_firmware_path=(null) i915.mmio_debug=1 i915.edp_vswing=0 i915.reset=2 i915.inject_load_failure=0 i915.fastboot=-1 i915.enable_dpcd_backlight=-1 i915.force_probe= i915.alpha_support=no i915.enable_hangcheck=yes i915.prefault_disable=no i915.load_detect_test=no i915.force_reset_modeset_test=no i915.error_capture=yes i915.disable_display=no i915.verbose_state_checks=yes i915.nuclear_pageflip=no i915.enable_dp_mst=yes i915.enable_gvt=yes GuC firmware:
[Kernel-packages] [Bug 1862253] Re: focal/linux-kvm-5.4: 5.4.0-1001.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: 1862255 packages: main: linux-kvm-5.4 meta: linux-meta-kvm-5.4 - phase: Ready for Promote to Proposed - phase-changed: Thursday, 13. February 2020 14:16 UTC + phase: Promote to Proposed + phase-changed: Sunday, 16. February 2020 16:56 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862253 Title: focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: main: linux-kvm-5.4 meta: linux-meta-kvm-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:56 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862252] Re: focal/linux-gcp-5.4: 5.4.0-1001.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: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 - phase: Ready for Promote to Proposed - phase-changed: Friday, 14. February 2020 10:46 UTC + phase: Promote to Proposed + phase-changed: Sunday, 16. February 2020 16:56 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862252 Title: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:56 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862254] Re: focal/linux-oracle-5.4: 5.4.0-1002.2 -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: 1862255 packages: lrm: linux-restricted-modules-oracle-5.4 main: linux-oracle-5.4 meta: linux-meta-oracle-5.4 signed: linux-signed-oracle-5.4 - phase: Ready for Promote to Proposed - phase-changed: Sunday, 16. February 2020 01:56 UTC + phase: Promote to Proposed + phase-changed: Sunday, 16. February 2020 16:56 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862254 Title: focal/linux-oracle-5.4: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: lrm: linux-restricted-modules-oracle-5.4 main: linux-oracle-5.4 meta: linux-meta-oracle-5.4 signed: linux-signed-oracle-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:56 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863087] Re: i915 GPU HANG: ecode 9:1:0x00000000, hang on rcs0
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: linux-signed-5.4 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-signed-5.4 in Ubuntu.
https://bugs.launchpad.net/bugs/1863087
Title:
i915 GPU HANG: ecode 9:1:0x, hang on rcs0
Status in linux-signed-5.4 package in Ubuntu:
Confirmed
Bug description:
During normal desktop use I noticed the whole desktop freeze and it
would not respond (even mouse was frozen and virtual consoles were
inaccessible) - so I rebooted using Alt-SysRq-RIESUB and the following
was in the logs:
Feb 13 16:15:19 slate kernel: i915 :00:02.0: GPU HANG: ecode
9:1:0x, hang on rcs0
Feb 13 16:15:19 slate kernel: GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
Feb 13 16:15:19 slate kernel: Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
Feb 13 16:15:19 slate kernel: drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
Feb 13 16:15:19 slate kernel: The GPU crash dump is required to analyze GPU
hangs, so please always attach it.
Feb 13 16:15:19 slate kernel: GPU crash dump saved to
/sys/class/drm/card0/error
Feb 13 16:15:19 slate kernel: i915 :00:02.0: Resetting rcs0 for hang on
rcs0
Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 13 16:15:19 slate kernel: i915 :00:02.0: Resetting chip for hang on
rcs0
Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 13 16:15:19 slate kernel: [drm:gen8_reset_engines [i915]] *ERROR* rcs0
reset request timed out: {request: 0001, RESET_CTL: 0001}
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
EDID vendor "DEL", prod id 53409
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Using hsync ranges from config file
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Using vrefresh ranges from config file
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Printing DDC gathered Modelines:
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080"x0.0 148.50 1920 2008 2052 2200 1080 1084 1089 1125
+hsync +vsync (67.5 kHz eP)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080"x0.0 174.50 1920 1968 2000 2080 1080 1083 1088 1119
+hsync -vsync (83.9 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080i"x0.0 74.25 1920 2008 2052 2200 1080 1084 1094 1125
interlace +hsync +vsync (33.8 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1280x720"x0.0 74.25 1280 1390 1430 1650 720 725 730 750 +hsync
+vsync (45.0 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "720x480"x0.0 27.00 720 736 798 858 480 489 495 525 -hsync -vsync
(31.5 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1440x480i"x0.0 27.00 1440 1478 1602 1716 480 488 494 525
interlace -hsync -vsync (15.7 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1440x576i"x0.0 27.00 1440 1464 1590 1728 576 580 586 625
interlace -hsync -vsync (15.6 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "640x480"x0.0 25.18 640 656 752 800 480 490 492 525 -hsync -vsync
(31.5 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080i"x0.0 74.25 1920 2448 2492 2640 1080 1084 1094 1125
interlace +hsync +vsync (28.1 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1920x1080"x0.0 148.50 1920 2448 2492 2640 1080 1084 1089 1125
+hsync +vsync (56.2 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "720x576"x0.0 27.00 720 732 796 864 576 581 586 625 -hsync -vsync
(31.2 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "1280x720"x0.0 74.25 1280 1720 1760 1980 720 725 730 750 +hsync
+vsync (37.5 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "800x600"x0.0 40.00 800 840 968 1056 600 601 605 628 +hsync +vsync
(37.9 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "640x480"x0.0 31.50 640 656 720 840 480 481 484 500 -hsync -vsync
(37.5 kHz e)
Feb 13 16:15:20 slate /usr/lib/gdm3/gdm-x-session[6923]: (II) modeset(0):
Modeline "720x400"x0.0 28.32 720 738
[Kernel-packages] [Bug 1825626] Re: nvLock: client timed out, taking the lock
No, but this event seems to happen most often when I go in/out of fullscreen mode in celluloid (gnome-mpv) while playing a video with subtitles: feb. 16 10:00:12 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer event7 debounce: scheduled expiry is in the past (-34ms), your system is too slow feb. 16 10:00:12 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer event7 debounce short: scheduled expiry is in the past (-48ms), your system is too slow feb. 16 10:03:44 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer event7 debounce: scheduled expiry is in the past (-32ms), your system is too slow feb. 16 10:03:44 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer event7 debounce short: scheduled expiry is in the past (-45ms), your system is too slow feb. 16 10:05:50 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer event7 debounce: scheduled expiry is in the past (-2ms), your system is too slow feb. 16 10:05:50 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer event7 debounce short: scheduled expiry is in the past (-15ms), your system is too slow I'm not sure if it's related to "nvLock: client timed out, taking the lock" or not, but here's how my last freeze looked in the journal: feb. 16 09:39:55 host dbus-daemon[1294]: [session uid=1000 pid=1294] Activating service name='io.github.celluloid_player.Celluloid' requested by ':1.100' (uid=1000 pi> feb. 16 09:39:55 host dbus-daemon[1294]: [session uid=1000 pid=1294] Successfully activated service 'io.github.celluloid_player.Celluloid' feb. 16 09:42:01 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer event7 debounce: scheduled expiry is in the past (-24ms), your system is too slow feb. 16 09:42:01 host /usr/lib/gdm3/gdm-x-session[1299]: (EE) client bug: timer event7 debounce short: scheduled expiry is in the past (-37ms), your system is too slow feb. 16 09:44:18 host kernel: NVRM: GPU at PCI::01:00: GPU-fd72a0ff-d55a-e23d-1169-227134e81d2b feb. 16 09:44:18 host kernel: NVRM: GPU Board Serial Number: feb. 16 09:44:18 host kernel: NVRM: Xid (PCI::01:00): 68, pid=906, CCMDs 0042 c2b0 feb. 16 09:44:20 host kernel: perf: interrupt took too long (3172 > 3140), lowering kernel.perf_event_max_sample_rate to 63000 feb. 16 09:44:29 host /usr/lib/gdm3/gdm-x-session[1299]: nvLock: client timed out, taking the lock feb. 16 09:44:34 host /usr/lib/gdm3/gdm-x-session[1299]: nvLock: client timed out, taking the lock feb. 16 09:44:39 host /usr/lib/gdm3/gdm-x-session[1299]: (WW) NVIDIA: Wait for channel idle timed out. feb. 16 09:44:39 host gnome-shell[1609]: Object .Gjs_AppSwitcherPopup (0x55b758a47860), has been already deallocated — impossible to access it. This might be caused b> feb. 16 09:44:39 host gnome-shell[1609]: == Stack trace for context 0x55b7580485e0 == feb. 16 09:44:39 host gnome-shell[1609]: #0 55b75de9ed20 i resource:///org/gnome/shell/ui/windowManager.js:2094 (7f1059e3ec10 @ 410) feb. 16 09:44:39 host gnome-shell[1609]: #1 7ffd012dc2b0 b self-hosted:981 (7f1059c35670 @ 474) feb. 16 09:44:39 host gnome-shell[1609]: clutter_actor_destroy: assertion 'CLUTTER_IS_ACTOR (self)' failed feb. 16 09:44:39 host gnome-shell[1609]: NOTE: Not using GLX TFP! feb. 16 09:45:11 host gnome-shell[1609]: Window manager warning: last_focus_time (7213510) is greater than comparison timestamp (7205655). This most likely represent> feb. 16 09:45:11 host gnome-shell[1609]: pushModal: invocation of begin_modal failed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-418 in Ubuntu. https://bugs.launchpad.net/bugs/1825626 Title: nvLock: client timed out, taking the lock Status in gnome-desktop: New Status in mutter package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-418 package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Confirmed Bug description: While launching an app or performing an operation, the screen has a certain chance to freeze for a few seconds and then recover. [ System Info ] Version : Ubuntu 19.04 Kernel : x86_64 Linux 5.0.0-13-generic GPU : NVIDIA GeForce GTX 1050 Xorg version : 1:7.7+19ubuntu12 Product Name : Aspire VX5-591G (Acer) [ Log File ] Uploaded as an attachment *Sorry for my not-good English. ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.0.0-13.14-generic 5.0.6 Uname: Linux 5.0.0-13-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] 是一个目录: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 418.56 Fri Mar 15 12:59:26 CDT 2019 GCC version: gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1) ApportVersion:
[Kernel-packages] [Bug 1862816] Re: trusty/linux-azure: 4.15.0-1071.76~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- 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/1862816 Title: trusty/linux-azure: 4.15.0-1071.76~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: In Progress 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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 11:31 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862254] Re: focal/linux-oracle-5.4: 5.4.0-1002.2 -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: 1862255 packages: lrm: linux-restricted-modules-oracle-5.4 main: linux-oracle-5.4 meta: linux-meta-oracle-5.4 signed: linux-signed-oracle-5.4 phase: Ready for Promote to Proposed phase-changed: Sunday, 16. February 2020 01:56 UTC reason: - promote-to-proposed: Pending -- ready for review + promote-to-proposed: Stalled -- ready for review 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/1862254 Title: focal/linux-oracle-5.4: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid 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: 1862255 packages: lrm: linux-restricted-modules-oracle-5.4 main: linux-oracle-5.4 meta: linux-meta-oracle-5.4 signed: linux-signed-oracle-5.4 phase: Ready for Promote to Proposed phase-changed: Sunday, 16. February 2020 01:56 UTC reason: promote-to-proposed: Stalled -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862254/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 916677] Re: 1106:0415 Boot problem with VIA VT6415 PATA IDE Host Controller
I can confirm this bug still persists on Ubuntu 20.04 64-bit, using an ASRock 990fx Extreme4 motherboard. The solution pointed out here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/916677/comments/39 seems to still fix the problem. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/916677 Title: 1106:0415 Boot problem with VIA VT6415 PATA IDE Host Controller Status in linux package in Ubuntu: Incomplete Bug description: kubuntu-32 11.10, Linux server 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10 UTC 2011 i686 athlon i386 GNU/Linux. After the motherboard and CPU uograde I started to experience intermittent system frezes during the system boot process with udevd[101]: timeout: killing '/sbin/modprobe -bv pci:v1B4Bd91A0sv1849sd91A0bc01sc01i8f' [145] message dispayed on screen (white on black, 'thick' system textmode font, not 'thin' ubuntu console font). If system boots successfully (3 out of 8 attempts so far) it functions without futher problems. WORKAROUND: I disabled IDE controller system booted normally. --- AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 ArecordDevices: List of CAPTURE Hardware Devices card 0: SB [HDA ATI SB], device 0: ALC892 Analog [ALC892 Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: lvm2342 F pulseaudio /dev/snd/controlC0: lvm2342 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'SB'/'HDA ATI SB at 0xfe60 irq 16' Mixer name : 'Realtek ALC892' Components : 'HDA:10ec0892,18497892,00100302' Controls : 35 Simple ctrls : 20 Card1.Amixer.info: Card hw:1 'NVidia'/'HDA NVidia at 0xfe08 irq 25' Mixer name : 'Nvidia GPU 0d HDMI/DP' Components : 'HDA:10de000d,10de0101,00100100' Controls : 17 Simple ctrls : 5 DistroRelease: Ubuntu 11.10 HibernationDevice: RESUME=UUID=d22ce633-8298-47af-bd3b-b2f2c011e08f InstallationMedia: Kubuntu 11.04 "Natty Narwhal" - Release i386 (20110427) IwConfig: lono wireless extensions. eth2 no wireless extensions. MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. NonfreeKernelModules: nvidia Package: linux (not installed) ProcEnviron: LANGUAGE= PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-3.0.0-14-generic-pae root=UUID=e5d4b20c-2274-4625-bff0-06fcc27e7755 ro recovery nomodeset ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9 RelatedPackageVersions: linux-restricted-modules-3.0.0-14-generic-pae N/A linux-backports-modules-3.0.0-14-generic-pae N/A linux-firmware1.60 RfKill: Tags: oneiric Uname: Linux 3.0.0-14-generic-pae i686 UpgradeStatus: Upgraded to oneiric on 2011-10-15 (95 days ago) UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare dmi.bios.date: 09/13/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.30 dmi.board.name: 990FX Extreme4 dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.30:bd09/13/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rn990FXExtreme4:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.: dmi.product.name: To Be Filled By O.E.M. dmi.product.version: To Be Filled By O.E.M. dmi.sys.vendor: To Be Filled By O.E.M. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/916677/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862249] Re: focal/linux-oem-5.4: 5.4.0-1003.5 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Canonical Kernel Team (canonical-kernel-team) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1862249 Title: focal/linux-oem-5.4: 5.4.0-1003.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-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 prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oem-5.4 package in Ubuntu: Confirmed Status in linux-oem-5.4 source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-oem-5.4 main: linux-oem-5.4 meta: linux-meta-oem-5.4 signed: linux-signed-oem-5.4 phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 16:51 UTC reason: promote-to-proposed: Stalled -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862249/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1856370] Re: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend
yes i used the 435 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1856370 Title: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Bug description: Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590 with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5 Description: Ubuntu 19.10 Release: 19.10 nvidia driver 435 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 16:31:58 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905] Subsystem: Dell Device [1028:0905] InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862816] Re: trusty/linux-azure: 4.15.0-1071.76~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed ** 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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 11:31 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- package copied to Signing 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/1862816 Title: trusty/linux-azure: 4.15.0-1071.76~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: Fix Committed 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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 11:31 UTC reason: promote-to-proposed: Ongoing -- package copied to Signing signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862816] Re: trusty/linux-azure: 4.15.0-1071.76~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/promote-signing-to-proposed Assignee: (unassigned) => Andy Whitcroft (apw) -- 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/1862816 Title: trusty/linux-azure: 4.15.0-1071.76~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: In Progress 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: 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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 15:32 UTC reason: promote-signing-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862505] Re: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology-conf to focal image by default
** Tags added: packaging -- 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/1862505 Title: alsa-lib-1.2.1.2: should install the alsa-ucm-conf and alsa-topology- conf to focal image by default Status in alsa-lib package in Ubuntu: New Bug description: Before the alsa-lib-1.2.1 the ucm and topology conf files are in the alsa-lib, when we install the alsa-lib/libasound2, they are installed together with alsa-lib. But from 1.2.1 they are separated from the alsa-lib, and in the focal, we choose the 1.2.1.2 version, we should install the ucm and topology too, otherwise those machines need ucm and topology will not work anymore, users have to install these two packages manually. Two packages we need to put into the focal image are: alsa-ucm-conf 1.2.1.2-2 alsa-topology-conf 1.2.1-2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-lib/+bug/1862505/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863489] Re: intel grafic i915 driver no power saving states rc6
** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863489 Title: intel grafic i915 driver no power saving states rc6 Status in linux package in Ubuntu: New Bug description: It seems that the i915 intel graphic driver in newer kernels (observed with 5.3) doesn't support energy saving. How do I know that? Using powertop shows in idle tab the GPU - and this shows only : GPU power on 100% - no rc6 or deeper states are used. For some strange reason also the packet (summery?) shows in all states 0%, although I can observe the individual CPU cores are in different power states. The previous parameter enable_rc6 is not existing anymore. The other possible energy saving parameter enable_dc (if set to 1 or 2) results in log with: setting dangerous option enable_dc - tainting kernel. Any idea what might go wrong there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861134] Re: bionic/linux-raspi2: 4.15.0-1055.59 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861134 Title: bionic/linux-raspi2: 4.15.0-1055.59 -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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: '1862824' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Sunday, 16. February 2020 19:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: bionic/linux-raspi2/pi-kernel: bug 1861133 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861113] Re: xenial/linux-raspi2: 4.4.0-1129.138 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861113 Title: xenial/linux-raspi2: 4.4.0-1129.138 -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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1861122 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Sunday, 16. February 2020 19:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: xenial/linux-raspi2/pi2-kernel: bug 186 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863489] 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 1863489 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/1863489 Title: intel grafic i915 driver no power saving states rc6 Status in linux package in Ubuntu: Incomplete Bug description: It seems that the i915 intel graphic driver in newer kernels (observed with 5.3) doesn't support energy saving. How do I know that? Using powertop shows in idle tab the GPU - and this shows only : GPU power on 100% - no rc6 or deeper states are used. For some strange reason also the packet (summery?) shows in all states 0%, although I can observe the individual CPU cores are in different power states. The previous parameter enable_rc6 is not existing anymore. The other possible energy saving parameter enable_dc (if set to 1 or 2) results in log with: setting dangerous option enable_dc - tainting kernel. Any idea what might go wrong there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838176] Re: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor
You can try the linux-firmware package from upcoming focal: https://packages.ubuntu.com/focal/linux-firmware Because of this bug I am currently running 19.10 with latest 5.5 kernel from mainline ppa: https://kernel.ubuntu.com/~kernel-ppa/mainline/ With 5.5 the number of my problems was significantly reduced and suspend seems to work, too. The 5.5 kernel works with VirtualBox 6.1.2 and zfsonlinux 0.8.3 For example, to try out 5.5.4 you may need the following packages: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.4/linux-headers-5.5.4-050504_5.5.4-050504.202002150446_all.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.4/linux-headers-5.5.4-050504-generic_5.5.4-050504.202002150446_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.4/linux-image-unsigned-5.5.4-050504-generic_5.5.4-050504.202002150446_amd64.deb https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.5.4/linux-modules-5.5.4-050504-generic_5.5.4-050504.202002150446_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838176 Title: Kernel 5.2.3 fails to fully boot on Lenovo 330s-15arr, black screen at login screen with cursor Status in linux package in Ubuntu: Confirmed Bug description: Was on 4.20, booted fine (with the boot option ivrs_ioapic[32]=00:14.0) Tried to boot 5.2.3 (but I believe this happened on 5.1.X too) It will boot to a certain extent, it does my disk password, i can see everything say "ok" when i do no quiet splash. But where it should go to the login screen I just see a single cursor Setting nomodeset lets me boot, looking at logs: Syslog Jul 27 21:28:58 kenji-mintop systemd[1]: Startup finished in 41.291s (kernel) + 8.383s (userspace) = 49.675s. Jul 27 21:28:59 kenji-mintop kernel: [ 50.535066] failed to write reg 1a6f4 wait reg 1a706 Jul 27 21:28:59 kenji-mintop NetworkManager[1082]: [1564288139.7335] manager: NetworkManager state is now CONNECTED_GLOBAL Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': new request (1 scripts) Jul 27 21:28:59 kenji-mintop nm-dispatcher: req:4 'connectivity-change': start running ordered scripts... Jul 27 21:29:09 kenji-mintop kernel: [ 60.615575] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615662] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:09 kenji-mintop kernel: [ 60.615665] [drm] GPU recovery disabled. Jul 27 21:29:11 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:19 kenji-mintop kernel: [ 70.855956] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856043] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:19 kenji-mintop kernel: [ 70.856047] [drm] GPU recovery disabled. Jul 27 21:29:20 kenji-mintop zerotier-one[1984]: message repeated 3 times: [ connect: Host is unreachable] Jul 27 21:29:22 kenji-mintop systemd-timesyncd[968]: Synchronized to time server 91.189.94.4:123 (ntp.ubuntu.com). Jul 27 21:29:23 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:29 kenji-mintop kernel: [ 81.095310] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095397] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:29 kenji-mintop kernel: [ 81.095401] [drm] GPU recovery disabled. Jul 27 21:29:40 kenji-mintop kernel: [ 91.335557] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335645] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:40 kenji-mintop kernel: [ 91.335648] [drm] GPU recovery disabled. Jul 27 21:29:41 kenji-mintop zerotier-one[1984]: message repeated 6 times: [ connect: Host is unreachable] Jul 27 21:29:43 kenji-mintop systemd[1]: Starting Stop ureadahead data collection... Jul 27 21:29:43 kenji-mintop systemd[1]: Started Stop ureadahead data collection. Jul 27 21:29:44 kenji-mintop zerotier-one[1984]: connect: Host is unreachable Jul 27 21:29:50 kenji-mintop kernel: [ 101.575935] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* ring gfx timeout, signaled seq=1, emitted seq=3 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576023] [drm:amdgpu_job_timedout [amdgpu]] *ERROR* Process information: process Xorg pid 1361 thread Xorg:cs0 pid 1736 Jul 27 21:29:50 kenji-mintop kernel: [ 101.576027] [drm] GPU recovery disabled.
[Kernel-packages] [Bug 1859979] Re: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing
Brian G also bisected and found another commit (d3b3c0a14615c495118acc4bdca23d53eea46ed2) to trigger the bug: https://lkml.org/lkml/2020/2/15/260. There's also a lot of additional information from ARAI Shun-ichi. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1859979 Title: nilfs2 segctord kthread dies after which write to nilfs2 fs freezes the process writing Status in linux package in Ubuntu: Incomplete Bug description: With linux-image-5.3.0-26-lowlatency, segctord kthread encounters a "BUG: kernel NULL pointer dereference, address: 00a8" some half a minute from boot. Before that, one can log in to the system (/home is on a nilfs2 filesystem), but after the kernel BUG report, any write to a nilfs2 filesystem freezes the process trying to write, or any new login attempt freezes. This bug can be reproduced with every boot. With linux-image-5.3.0-24-lowlatency and earlier, this doesn't happen. Relevant excerpt from syslog: ... Jan 16 10:56:59 lillukka kernel: [0.00] Linux version 5.3.0-26-lowlatency (buildd@lgw01-amd64-013) (gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2)) #28-Ubuntu SMP PREEMPT Wed Dec 18 06:21:38 UTC 2019 (Ubuntu 5.3.0-26.28-lowlatency 5.3.13) ... Jan 16 10:57:13 lillukka kernel: [ 28.727753] BUG: kernel NULL pointer dereference, address: 00a8 Jan 16 10:57:13 lillukka kernel: [ 28.727852] #PF: supervisor read access in kernel mode Jan 16 10:57:13 lillukka kernel: [ 28.727914] #PF: error_code(0x) - not-present page Jan 16 10:57:13 lillukka kernel: [ 28.727974] PGD 0 P4D 0 Jan 16 10:57:13 lillukka kernel: [ 28.728012] Oops: [#1] PREEMPT SMP PTI Jan 16 10:57:13 lillukka kernel: [ 28.728067] CPU: 3 PID: 838 Comm: segctord Not tainted 5.3.0-26-lowlatency #28-Ubuntu Jan 16 10:57:13 lillukka kernel: [ 28.728156] Hardware name: Sony Corporation SVP1321C5E/VAIO, BIOS R0280V7 07/11/2013 Jan 16 10:57:13 lillukka kernel: [ 28.728257] RIP: 0010:percpu_counter_add_batch+0x13/0x80 Jan 16 10:57:13 lillukka kernel: [ 28.728334] Code: e0 41 5c 41 5d 41 5e 5d c3 66 66 2e 0f 1f 84 00 00 00 00 00 0f 1f 00 55 48 89 e5 41 55 41 54 49 89 fc 53 65 ff 05 b5 5c ed 72 <48> 8b 47 20 48 63 ca 65 44 8b 28 49 63 dd 48 01 f3 48 39 d9 7e 0a Jan 16 10:57:13 lillukka kernel: [ 28.728536] RSP: 0018:b582c02afcb0 EFLAGS: 00010082 Jan 16 10:57:13 lillukka kernel: [ 28.728598] RAX: 0002 RBX: RCX: 0001 Jan 16 10:57:13 lillukka kernel: [ 28.728679] RDX: 0018 RSI: 0001 RDI: 0088 Jan 16 10:57:13 lillukka kernel: [ 28.728760] RBP: b582c02afcc8 R08: 8f519357ab40 R09: 0018 Jan 16 10:57:13 lillukka kernel: [ 28.728841] R10: 00030140 R11: 8f5193609eea R12: 0088 Jan 16 10:57:13 lillukka kernel: [ 28.728920] R13: 8f518a3ee498 R14: 8f518a3ee608 R15: e52b07e5a200 Jan 16 10:57:13 lillukka kernel: [ 28.729001] FS: () GS:8f519798() knlGS: Jan 16 10:57:13 lillukka kernel: [ 28.729091] CS: 0010 DS: ES: CR0: 80050033 Jan 16 10:57:13 lillukka kernel: [ 28.729157] CR2: 00a8 CR3: 8d60a002 CR4: 001606e0 Jan 16 10:57:13 lillukka kernel: [ 28.729237] Call Trace: Jan 16 10:57:13 lillukka kernel: [ 28.729280] __test_set_page_writeback+0x2f1/0x310 Jan 16 10:57:13 lillukka kernel: [ 28.729362] nilfs_segctor_do_construct+0xd13/0x1260 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729432] ? __switch_to_asm+0x40/0x70 Jan 16 10:57:13 lillukka kernel: [ 28.729496] nilfs_segctor_construct+0x1ff/0x2f0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729572] nilfs_segctor_thread+0x136/0x3a0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729640] kthread+0x104/0x140 Jan 16 10:57:13 lillukka kernel: [ 28.729690] ? nilfs_segctor_construct+0x2f0/0x2f0 [nilfs2] Jan 16 10:57:13 lillukka kernel: [ 28.729760] ? kthread_park+0x80/0x80 Jan 16 10:57:13 lillukka kernel: [ 28.729807] ret_from_fork+0x35/0x40 Jan 16 10:57:13 lillukka kernel: [ 28.729854] Modules linked in: ccm rfcomm aufs overlay cmac bnep nilfs2 snd_hda_codec_realtek snd_hda_codec_generic ledtrig_audio snd_hda_codec_hdmi snd_hda_intel pn544_mei mei_phy pn544 snd_hda_codec hci snd_hda_core snd_hwdep intel_rapl_msr mei_hdcp nfc snd_pcm snd_seq_midi snd_seq_midi_event intel_rapl_common x86_pkg_temp_thermal intel_powerclamp snd_rawmidi coretemp iwlmvm mac80211 snd_seq btusb btrtl libarc4 btbcm uvcvideo btintel kvm videobuf2_vmalloc iwlwifi videobuf2_memops bluetooth snd_seq_device videobuf2_v4l2 videobuf2_common irqbypass joydev input_leds intel_cstate videodev ecdh_generic snd_timer intel_rapl_perf ecc serio_raw mc mei_me cfg80211 mei snd
[Kernel-packages] [Bug 1861134] Re: bionic/linux-raspi2: 4.15.0-1055.59 -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: '1862824' packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Signoff - phase-changed: Saturday, 15. February 2020 01:50 UTC + phase: Holding before Promote to Updates + phase-changed: Sunday, 16. February 2020 19:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- security signoff not verified - security-signoff: Stalled -- waiting for signoff + promote-to-updates: Holding -- cycle not ready to release trackers: bionic/linux-raspi2/pi-kernel: bug 1861133 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861134 Title: bionic/linux-raspi2: 4.15.0-1055.59 -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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: '1862824' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Sunday, 16. February 2020 19:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: bionic/linux-raspi2/pi-kernel: bug 1861133 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861113] Re: xenial/linux-raspi2: 4.4.0-1129.138 -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: 1861122 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Signoff - phase-changed: Friday, 14. February 2020 21:41 UTC + phase: Holding before Promote to Updates + phase-changed: Sunday, 16. February 2020 19:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- security signoff not verified - security-signoff: Stalled -- waiting for signoff + promote-to-updates: Holding -- cycle not ready to release trackers: xenial/linux-raspi2/pi2-kernel: bug 186 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861113 Title: xenial/linux-raspi2: 4.4.0-1129.138 -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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1861122 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Sunday, 16. February 2020 19:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- cycle not ready to release trackers: xenial/linux-raspi2/pi2-kernel: bug 186 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860253] Re: After kernel upgrade, the screen has got stuck when in running programs on GUI.
Hi Kai-Heng, First of all, I'm sorry for the late response.. and.. I may need to tell you that I'm just a user, not a developer. It is hard to install new kernel for testing to me. Also, I have no skill for GRUB bootloader. I beg your pardon. Thank you -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860253 Title: After kernel upgrade, the screen has got stuck when in running programs on GUI. Status in linux package in Ubuntu: Confirmed Bug description: Hi, Ubuntu First of all, Ubuntu Version: 18.04.3 LTS Kernel Version: linux-image-5.0.0-37-generic H/W Info: Processor - AMD Phenom II X3 720 Chipset - NVIDIA GeForce 8200 Package Repository: JAIST (JP) Summary: A problem with Linux kernel linux-image-5.3.0-26-generic Today, I got a notice from update manager that there are some upgrade packages. So, I did press the button 'Upgrade'. After the upgrade, I reboot the machine and login as usual via gdm. To run web browser, I clicked Firefox icon but got stuck, also other apps like Settings. I did investigate what packages have updated and found out that the kernel package has upgraded to 5.3.0-26 from 5.0.0-37 So, I did boot up my machine with 5.0.0-37 instead 5.3.0-26 and the machine works very well. I hereby request you to investigate kernel package 5.3.0-26. Thank you To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863489] [NEW] intel grafic i915 driver no power saving states rc6
You have been subscribed to a public bug: It seems that the i915 intel graphic driver in newer kernels (observed with 5.3) doesn't support energy saving. How do I know that? Using powertop shows in idle tab the GPU - and this shows only : GPU power on 100% - no rc6 or deeper states are used. For some strange reason also the packet (summery?) shows in all states 0%, although I can observe the individual CPU cores are in different power states. The previous parameter enable_rc6 is not existing anymore. The other possible energy saving parameter enable_dc (if set to 1 or 2) results in log with: setting dangerous option enable_dc - tainting kernel. Any idea what might go wrong there? ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bot-comment -- intel grafic i915 driver no power saving states rc6 https://bugs.launchpad.net/bugs/1863489 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 1861152] Re: bionic/linux-fips: 4.15.0-1023.26 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: '1862824' packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Updates phase-changed: Thursday, 13. February 2020 18:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Holding -- master bug not ready for release 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/1861152 Title: bionic/linux-fips: 4.15.0-1023.26 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: '1862824' packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Holding before Promote to Updates phase-changed: Thursday, 13. February 2020 18:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861152/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862806] Re: bionic/linux-aws-fips: 4.15.0-2009.9 -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: 1862808 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Updates phase-changed: Friday, 14. February 2020 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Holding -- master bug not ready for release 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/1862806 Title: bionic/linux-aws-fips: 4.15.0-2009.9 -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-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-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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1862808 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Holding before Promote to Updates phase-changed: Friday, 14. February 2020 09:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker
4.15.0-1072.82 - oem Regression test CMPL, RTB. Issue to note in amd64: ubuntu_bpf - test_maps failed (bug 1837386) ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) apic-split timeouted (bug 1821390) vmx (bug 1821394) ubuntu_ltp - proc01 (bug 1829849) pty03 (bug 1862114) memcg_max_usage_in_bytes (bug 1829979) memcg_stat (bug 1829983) memcg_use_hierarchy (bug 1829989) memcg_usage_in_bytes (bug 1829984) cpuset_hotplug (bug 1834006) getaddrinfo_01 (bug 1829995) crypto_user02 (bug 1837543) cve-2017-1000380 cve-2017-17053 failures caused by pty03 ubuntu_xfstests_btrfs - timed out on generic/241 ubuntu_xfstests_ext4 - timed out on generic/430 test (bug 1755999) ubuntu_xfstests_xfs - timed out on generic/430 test (bug 1755999) ** 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) ** Tags added: regression-testing-passed -- 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/1863072 Title: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 14. February 2020 08:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855679] Comment bridged from LTC Bugzilla
--- Comment From mranw...@us.ibm.com 2020-02-17 01:53 EDT---
On the original (old) kernel on a tuleta (p8) I was able to create a hard
lockup. I haven't been able to recreate that on the -76 kernel on a tuleta. I
did, however, recreate a stall on the tuleta. I did not see either on some run
time on a boston.
I'm going to compare this with focal on the tuleta.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1855679
Title:
Rcu stalls and Soft-lockups observed on stressing Ubuntu 18 04 1
Status in The Ubuntu-power-systems project:
Incomplete
Status in linux package in Ubuntu:
Incomplete
Bug description:
== Comment: #0 - Harish Sriram - 2018-07-31 03:50:07 ==
--Problem Description--
Rcu stalls and Soft-lockups observed on stressing Ubuntu 18 04 1
Contact Information = hasri...@in.ibm.com
---Issue observed---
[ 1196.813220] INFO: rcu_sched detected stalls on CPUs/tasks:
[ 1196.813241]0-: (19 ticks this GP) idle=966/140/0
softirq=11580/11580 fqs=1552
[ 1196.813249](detected by 24, t=5252 jiffies, g=11722, c=11721,
q=1061088)
[ 1196.813282] Task dump for CPU 0:
[ 1196.813285] stress-ng-dev R running task0 46323 33635
0x00042004
[ 1196.813294] Call Trace:
[ 1196.813310] [c02c75ad7b10] [c18bd940] log_first_seq+0x0/0x8
(unreliable)
[ 1198.508930] kauditd_printk_skb: 3 callbacks suppressed
[ 1198.508938] audit: type=1400 audit(1533020002.449:312): apparmor="STATUS"
operation="profile_load" profile="unconfined" name="/usr/bin/pulseaudio-eg"
pid=12813 comm="stress-ng-appar"
[ 1198.508954] audit: type=1400 audit(1533020002.449:313): apparmor="STATUS"
operation="profile_load" profile="unconfined"
name="/usr/bin/pulseaudio-eg///usr/lib/pulseaudio/pulse/gconf-helper" pid=12813
comm="stress-ng-appar"
[ 1199.361719] INFO: rcu_sched detected expedited stalls on CPUs/tasks: {
0-... 145-... 159-... } 5489 jiffies s: 173 root: 0x201/.
[ 1199.361742] blocking rcu_node structures: l=1:0-15:0x1/.
l=1:144-159:0x8002/.
[ 1199.361749] Task dump for CPU 0:
[ 1199.361752] stress-ng-dev R running task0 46323 33635
0x00042004
[ 1199.361757] Call Trace:
[ 1199.361769] [c02c75ad7b10] [c18bd940] log_first_seq+0x0/0x8
(unreliable)
[ 1199.361777] Task dump for CPU 145:
[ 1199.361779] migration/145 R running task0 883 2
0x0804
[ 1199.361783] Call Trace:
[ 1199.361787] [c02ff0f5fa40] [c02ff0f5fb00] 0xc02ff0f5fb00
(unreliable)
[ 1199.361791] Task dump for CPU 159:
[ 1199.361792] migration/159 R running task0 967 2
0x0804
[ 1199.361796] Call Trace:
[ 1199.361799] [c02d78a47a40] [c02d78a47b00] 0xc02d78a47b00
(unreliable)
[ 1199.787698] audit: type=1400 audit(1533020003.985:314): apparmor="STATUS"
operation="profile_replace" profile="unconfined" name="/usr/bin/pulseaudio-eg"
pid=12813 comm="stress-ng-appar"
[ 1200.781159] watchdog: BUG: soft lockup - CPU#145 stuck for 23s!
[migration/145:883]
[ 1200.781163] Modules linked in: snd_seq snd_seq_device snd_timer snd
soundcore kvm_hv kvm_pr kvm camellia_generic cast6_generic cast_common
serpent_generic vhost_vsock vmw_vsock_virtio_transport_common vsock
twofish_generic twofish_common vhost_net vhost tap hci_vhci bluetooth
ecdh_generic lrw userio algif_skcipher binfmt_misc tgr192 wp512 rmd320
unix_diag sctp rmd256 rmd160 rmd128 md4 dccp_ipv4 algif_hash dccp af_alg
powernv_op_panel ipmi_powernv ipmi_devintf ipmi_msghandler uio_pdrv_genirq
leds_powernv uio ibmpowernv powernv_rng vmx_crypto sch_fq_codel ib_iser rdma_cm
iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi
ip_tables x_tables autofs4 ses enclosure scsi_transport_sas btrfs zstd_compress
raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor async_tx xor
[ 1200.781321] raid6_pq libcrc32c raid1 raid0 multipath linear uas
usb_storage crct10dif_vpmsum crc32c_vpmsum tg3 ipr
[ 1200.781353] CPU: 145 PID: 883 Comm: migration/145 Not tainted
4.15.0-29-generic #31-Ubuntu
[ 1200.781359] NIP: c0206594 LR: c020699c CTR:
c0206470
[ 1200.781364] REGS: c02ff0f5f9e0 TRAP: 0901 Not tainted
(4.15.0-29-generic)
[ 1200.781366] MSR: 90019033 CR:
2800 XER: 2000
[ 1200.781392] CFAR: c02065a4 SOFTE: 1
GPR00: c020699c c02ff0f5fc60 c16eaf00
GPR04: 0001 002ffbf9 009dde82957a
GPR08: cfae3b00 0001 c0d432f8
0bdf
GPR12: cfae3b00
[ 1200.781453] NIP [c0206594] multi_cpu_stop+0x124/0x1f0
[ 1200.781461] LR [c020699c] cpu_stopper_thread+0xfc/0x1f0
[ 1200.781462]
[Kernel-packages] [Bug 1861192] Re: disco/linux: 5.0.0-41.45 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-disco ** Tags removed: 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 bugs-spammed: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Updates - phase-changed: Saturday, 15. February 2020 02:46 UTC + phase: Ready for Promote to Updates + phase-changed: Monday, 17. February 2020 02:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 bionic/linux-gcp: bug 1862213 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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: 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: Invalid Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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: Fix Released 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: Ready for Promote to Updates phase-changed: Monday, 17. February 2020 02:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: bionic/linux-aws-5.0: bug 1861179 bionic/linux-azure: bug 1862405 bionic/linux-bluefield: bug 1861188 bionic/linux-gcp: bug 1862213 bionic/linux-gke-5.0: bug 1861187 bionic/linux-oem-osp1: bug 1863082 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 1863455] Re: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28
** Package changed: xorg (Ubuntu) => linux (Ubuntu) ** Tags added: regression-update -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863455 Title: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28 Status in linux package in Ubuntu: Confirmed Bug description: Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. Keyboard and mouse (both connected via USB) are not working. It looks like everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the new kernel version has problems with the USB system. If I choose in GRUB an older kernel version (e.g. 5.0.0-37) everything is fine. Same problem with kernel 5.3.0-28. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Feb 16 05:14:11 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2019-03-19 (333 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7817 ProcEnviron: LANGUAGE=de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1860806] Re: Ubuntu 18.04 and 19.04 new ethernet problem
I don't think that apport-collect will work while I am offline. Please let me know how I can run this command and send the data after I have done the restart. Remember, after restart the problem goes away. I can't run diagnostics on Internet access that requires Internet access to run. As it looks like I am talking to an automated script rather than a real person perhaps this is now a dead thread. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1860806 Title: Ubuntu 18.04 and 19.04 new ethernet problem Status in linux package in Ubuntu: Confirmed Status in network-manager package in Ubuntu: New Bug description: Ubuntu 19.04 (64 bit) on OptiPlex-7010 On every power on I have no wired Ethernet connection or even an icon to enable it. After a restart (soft boot) it comes back again. This appears to be different from another bug reported which states that the Ethernet cable has to be unplugged during power on. In my issue, I can leave the Ethernet cable plugged in and it works fine. It just doesn't work during first power on boot. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 18.04 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback InstallationDate: Installed on 2020-01-26 (2 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) IpRoute: default via 192.168.1.1 dev eno1 proto dhcp metric 100 169.254.0.0/16 dev eno1 scope link metric 1000 192.168.1.0/24 dev eno1 proto kernel scope link src 192.168.1.156 metric 100 IwConfig: lono wireless extensions. eno1 no wireless extensions. NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true Package: network-manager 1.10.6-2ubuntu1.2 PackageArchitecture: amd64 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 4.15.0-74.84-generic 4.15.18 RfKill: Tags: bionic Uname: Linux 4.15.0-74-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True nmcli-con: NAMEUUID TYPE TIMESTAMP TIMESTAMP-REAL AUTOCONNECT AUTOCONNECT-PRIORITY READONLY DBUS-PATH ACTIVE DEVICE STATE ACTIVE-PATH SLAVE Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 ethernet 1580229876 Tue 28 Jan 2020 08:44:36 AM PST yes 4294966297 no/org/freedesktop/NetworkManager/Settings/1 yes eno1activated /org/freedesktop/NetworkManager/ActiveConnection/1 -- nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH eno1ethernet connected /org/freedesktop/NetworkManager/Devices/2 Wired connection 1 bea41631-df6c-3de0-ac4c-7606d1313303 /org/freedesktop/NetworkManager/ActiveConnection/1 lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/1 -- ---- nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.10.6 connected started full enabled enabled enabled enabled enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1860806/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855668] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-02-16 22:34 EDT--- Hi, I'm going to ask you to hold this open for a little bit - we're investigating internally another ppcism that may need additional lockdown support. In the mean time I will test the kernel in -proposed. Kind regards, Daniel -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855668 Title: lockdown on power Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: == Comment: #0 - Michael Ranweiler - 2019-11-11 08:50:51 == For 20.04 testing/inclusion. The ubuntu kernel team has a ppa here for testing: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable Test results will follow... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1855668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862816] Re: trusty/linux-azure: 4.15.0-1071.76~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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Sunday, 16. February 2020 16: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/1862816 Title: trusty/linux-azure: 4.15.0-1071.76~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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Testing phase-changed: Sunday, 16. February 2020 16: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/1862816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms
Intel (Mengdong@Intel) told us it is too complicated to backport the fixing patches to 5.0-oem-osp1 kernel, and these 3 patches are not very important. we will not backport these 3 patches to osp1 kernel until Intel backport the fixing patches to osp1 kernel. Set it to Medium first. ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Importance: Critical => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1857409 Title: alsa/sof: load different firmware on different platforms Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: [Impact] In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware) on all platforms, but mainline kernel already supported the multi firmwares on differnt platforms, and OEM project needs us to support the mutli-firmware names in the ubuntu kernel [Fix] cherry-pick 3 upstream patches, then on cnl platforms, it will load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl platforms, it will load sof-cfl.ri [Test Case] Prepare the firmware from https://github.com/thesofproject/linux-firmware master branch, then boot the kernel with these patches. [Regression Risk] Low, just let different platforms load differnt firmware, and these patches are in the upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863562] [NEW] Restrict ppc64el xmon to read-only-mode if kernel is locked down
Public bug reported:
This is a spin off of LP 1855668 (see comment #11 there:)
Please could you pick up (in addition to the issue still pending) commit
69393cb03ccd ("powerpc/xmon: Restrict when kernel is locked down").
>From the pull-request that included it, the commit does the following:
- A change to xmon (our crash handler / pseudo-debugger) to restrict
it to read-only mode when the kernel is lockdown'ed, otherwise it's
trivial to drop into xmon and modify kernel data, such as the
lockdown state.
To exploit this you'd need to boot with command line including
'xmon=rw', as xmon isn't read-write by default on the Focal kernel, but
that's not exactly a challenge. I have used this to drop down from
lockdown=confidentiality to lockdown=none on 5.4.0-14-generic #17-Ubuntu
** Affects: ubuntu-power-systems
Importance: High
Assignee: Ubuntu on IBM Power Systems Bug Triage (ubuntu-power-triage)
Status: Triaged
** Affects: linux (Ubuntu)
Importance: High
Assignee: Frank Heimes (fheimes)
Status: Triaged
** Tags: ppc64el
** Also affects: ubuntu-power-systems
Importance: Undecided
Status: New
** Changed in: ubuntu-power-systems
Status: New => Triaged
** Changed in: ubuntu-power-systems
Importance: Undecided => High
** Changed in: ubuntu-power-systems
Assignee: (unassigned) => Ubuntu on IBM Power Systems Bug Triage
(ubuntu-power-triage)
** Changed in: linux (Ubuntu)
Status: New => Triaged
** Changed in: linux (Ubuntu)
Importance: Undecided => High
** Changed in: linux (Ubuntu)
Assignee: (unassigned) => Frank Heimes (fheimes)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863562
Title:
Restrict ppc64el xmon to read-only-mode if kernel is locked down
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
This is a spin off of LP 1855668 (see comment #11 there:)
Please could you pick up (in addition to the issue still pending) commit
69393cb03ccd ("powerpc/xmon: Restrict when kernel is locked down").
From the pull-request that included it, the commit does the following:
- A change to xmon (our crash handler / pseudo-debugger) to restrict
it to read-only mode when the kernel is lockdown'ed, otherwise it's
trivial to drop into xmon and modify kernel data, such as the
lockdown state.
To exploit this you'd need to boot with command line including
'xmon=rw', as xmon isn't read-write by default on the Focal kernel,
but that's not exactly a challenge. I have used this to drop down from
lockdown=confidentiality to lockdown=none on 5.4.0-14-generic
#17-Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1863562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863086] Re: unkillable process (kernel NULL pointer dereference)
Yes, you are absolutely correct. I can reproduce this now, when
kernel.core_pattern is set to "|".
I can also confirm that the first kernel that this is broken in is 5.3,
as it works fine in 5.2 and below.
I will look into this and hopefully get this fixed for you. Thanks for
reporting!
Engineering Notes:
RIP: 0010:do_coredump+0x536/0xb30
$ eu-addr2line do_coredump+0x536 -e vmlinux-5.3.0-29-generic
/build/linux-OZAq_R/linux-5.3.0/include/linux/fs.h:2841:7
This is the function file_start_write():
2839 static inline void file_start_write(struct file *file)
2840 {
2841 if (!S_ISREG(file_inode(file)->i_mode))
2842 return;
2843 __sb_start_write(file_inode(file)->i_sb, SB_FREEZE_WRITE, true);
2844 }
This is called from do_coredump():
565 void do_coredump(const kernel_siginfo_t *siginfo)
566 {
...
788 if (!dump_interrupted()) {
789 file_start_write(cprm.file);
790 core_dumped = binfmt->core_dump();
791 file_end_write(cprm.file);
792 }
...
810 }
On kernels 5.2 and before, kernel.core_pattern=| normally outputs:
[ 39.328638] Core dump to | pipe failed
This is output is from the pipe section of do_coredump():
565 void do_coredump(const kernel_siginfo_t *siginfo)
566 {
...
623 ispipe = format_corename(, , , );
624
625 if (ispipe) {
...
681 sub_info = call_usermodehelper_setup(helper_argv[0],
682 helper_argv, NULL, GFP_KERNEL,
683 umh_pipe_setup, NULL, );
684 if (sub_info)
685 retval = call_usermodehelper_exec(sub_info,
686 UMH_WAIT_EXEC);
687
688 kfree(helper_argv);
689 if (retval) {
690 printk(KERN_INFO "Core dump to |%s pipe failed\n",
691cn.corename);
692 goto close_fail;
693 }
...
810 }
With kernel.core_pattern=|, format_corename() still interprets this as
the pipe path with:
191 static int format_corename(struct core_name *cn, struct coredump_params
*cprm,
192size_t **argv, int *argc)
193 {
...
196 int ispipe = (*pat_ptr == '|');
...
335 return ispipe;
336 }
Which checks the first byte of the core_pattern string to see if it is a
"|".
This means we really want the call to call_usermodehelper_exec() in
do_coredump() to fail, so we take the if(retval) step and output "Core
dump to |%s pipe failed\n".
Note that cn.corename is NULL when kernel.core_pattern=|.
For some reason with 5.3 and later, this call to
call_usermodehelper_exec() is not failing, and execution continues on
and breaks at file_start_write(cprm.file); at the end of do_coredump().
call_usermodehelper_exec() calls umh_pipe_setup() and creates the pipe
used. Something has likely changed in the pipe subsystem.
I will update when I figure out what.
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Focal)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu Eoan)
Status: New => Confirmed
** Changed in: linux (Ubuntu Eoan)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Focal)
Importance: Undecided => Medium
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Changed in: linux (Ubuntu Focal)
Assignee: (unassigned) => Matthew Ruffell (mruffell)
** Description changed:
If process that listens socket on any port crashes (segmentation fault) it
becomes unkillable.
Kill command does not kill this process.
Port that listen crashed process never be freed.
journalctl shows error:
Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip
55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000]
Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30
30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72
ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18
Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address:
0020
Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode
Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page
Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0
Feb 13 13:28:09 vbun04 kernel: Oops: [#1] SMP NOPTI
Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G
OE 5.3.0-29-generic #31-Ubuntu
Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH
VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006
Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30
Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05
e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65
05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f
Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246
Feb 13 13:28:09 vbun04 kernel: RAX:
[Kernel-packages] [Bug 1856370] Re: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend
ohad, If you are referring to a PPA then please do not report bugs. PPAs are not officially supported here. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1856370 Title: [nvidia] Black screen with message "GPU has fallen off the bus" after resuming from suspend Status in linux package in Ubuntu: Incomplete Status in nvidia-graphics-drivers-435 package in Ubuntu: Incomplete Bug description: Every time I suspend my laptop, after I resume it, a black screen shows with the error message - GPU has fallen off the bus It's a plain vanilla Ubunbtu 19.10 installation on an Dell XPS 15 7590 with NVIDIA(R) GeForce(R) GTX 1650 4GB GDDR5 Description: Ubuntu 19.10 Release: 19.10 nvidia driver 435 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: xorg 1:7.7+19ubuntu12 ProcVersionSignature: Ubuntu 5.3.0-24.26-generic 5.3.10 Uname: Linux 5.3.0-24-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia .proc.driver.nvidia.gpus..01.00.0: Error: [Errno 21] Is a directory: '/proc/driver/nvidia/gpus/:01:00.0' .proc.driver.nvidia.registry: Binary: "" .proc.driver.nvidia.suspend: suspend hibernate resume .proc.driver.nvidia.suspend_depth: default modeset uvm .proc.driver.nvidia.version: NVRM version: NVIDIA UNIX x86_64 Kernel Module 435.21 Sun Aug 25 08:17:57 CDT 2019 GCC version: gcc version 9.2.1 20191008 (Ubuntu 9.2.1-9ubuntu2) ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Fri Dec 13 16:31:58 2019 DistUpgraded: Fresh install DistroCodename: eoan DistroVariant: ubuntu DkmsStatus: nvidia, 435.21, 5.3.0-18-generic, x86_64: installed nvidia, 435.21, 5.3.0-24-generic, x86_64: installed virtualbox, 6.0.14, 5.3.0-24-generic, x86_64: installed ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: Intel Corporation UHD Graphics 630 (Mobile) [8086:3e9b] (prog-if 00 [VGA controller]) Subsystem: Dell UHD Graphics 630 (Mobile) [1028:0905] Subsystem: Dell Device [1028:0905] InstallationDate: Installed on 2019-12-13 (0 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) MachineType: Dell Inc. XPS 15 7590 ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-24-generic root=UUID=0b1a4be3-b095-45fc-ae1b-4b6fb7845eb2 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/25/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.3.3 dmi.board.name: 0VYV0G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.3.3:bd09/25/2019:svnDellInc.:pnXPS157590:pvr:rvnDellInc.:rn0VYV0G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 7590 dmi.product.sku: 0905 dmi.sys.vendor: Dell Inc. version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.1-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.1-1ubuntu1 version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.5+git20191008-0ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.0.1-1ubuntu1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20190815-1 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.16-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1856370/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862812] Re: bionic/linux-ibm-gt: 4.15.0-1048.52 -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: 1862824 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Updates phase-changed: Thursday, 13. February 2020 18:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Holding -- master bug not ready for release 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/1862812 Title: bionic/linux-ibm-gt: 4.15.0-1048.52 -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 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: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Invalid 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: 1862824 packages: main: linux-ibm-gt meta: linux-meta-ibm-gt phase: Holding before Promote to Updates phase-changed: Thursday, 13. February 2020 18:44 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862812/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861113] Re: xenial/linux-raspi2: 4.4.0-1129.138 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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: 1861122 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Holding before Promote to Updates - phase-changed: Sunday, 16. February 2020 19:35 UTC + phase: Ready for Promote to Updates + phase-changed: Monday, 17. February 2020 01:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Pending -- ready to copy trackers: xenial/linux-raspi2/pi2-kernel: bug 186 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861113 Title: xenial/linux-raspi2: 4.4.0-1129.138 -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: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: 1861122 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Ready for Promote to Updates phase-changed: Monday, 17. February 2020 01:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-raspi2/pi2-kernel: bug 186 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861113/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861119] Re: trusty/linux-aws: 4.4.0-1062.66 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-trusty ** Tags removed: 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: 1861122 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Promote to Updates - phase-changed: Wednesday, 12. February 2020 03:10 UTC + phase: Ready for Promote to Updates + phase-changed: Monday, 17. February 2020 02:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Pending -- ready to copy 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/1861119 Title: trusty/linux-aws: 4.4.0-1062.66 -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 promote-signing-to-proposed series: Invalid 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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1861122 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Promote to Updates phase-changed: Monday, 17. February 2020 02:00 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861119/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861116] Re: xenial/linux-fips: 4.4.0-1029.34 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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: 1861122 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips - phase: Holding before Promote to Updates - phase-changed: Thursday, 13. February 2020 08:38 UTC + phase: Ready for Promote to Updates + phase-changed: Monday, 17. February 2020 01:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Pending -- ready to copy 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/1861116 Title: xenial/linux-fips: 4.4.0-1029.34 -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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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: 1861122 packages: main: linux-fips meta: linux-meta-fips signed: linux-signed-fips phase: Ready for Promote to Updates phase-changed: Monday, 17. February 2020 01:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861116/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861115] Re: xenial/linux-snapdragon: 4.4.0-1133.141 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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: 1861122 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Holding before Promote to Updates - phase-changed: Saturday, 15. February 2020 02:38 UTC + phase: Ready for Promote to Updates + phase-changed: Monday, 17. February 2020 01:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Pending -- ready to copy trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1861114 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/1861115 Title: xenial/linux-snapdragon: 4.4.0-1133.141 -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: New Status in Kernel SRU Workflow promote-to-updates series: Confirmed 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 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: 1861122 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Ready for Promote to Updates phase-changed: Monday, 17. February 2020 01:59 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1861114 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861115/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861110] Re: xenial/linux-kvm: 4.4.0-1066.73 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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: 1861122 packages: main: linux-kvm meta: linux-meta-kvm - phase: Holding before Promote to Updates - phase-changed: Thursday, 13. February 2020 08:38 UTC + phase: Ready for Promote to Updates + phase-changed: Monday, 17. February 2020 01:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Pending -- ready to copy 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/1861110 Title: xenial/linux-kvm: 4.4.0-1066.73 -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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm 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: 1861122 packages: main: linux-kvm meta: linux-meta-kvm phase: Ready for Promote to Updates phase-changed: Monday, 17. February 2020 01:58 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-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
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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 bugs-spammed: true packages: main: linux meta: linux-meta signed: linux-signed - phase: Holding before Promote to Updates - phase-changed: Saturday, 15. February 2020 04:45 UTC + phase: Ready for Promote to Updates + phase-changed: Monday, 17. February 2020 01:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Pending -- ready to copy 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: 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 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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in 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: Ready for Promote to Updates phase-changed: Monday, 17. February 2020 01:56 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy 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 1861107] Re: xenial/linux-aws: 4.4.0-1102.113 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-updates Status: New => Confirmed ** Tags removed: block-proposed-xenial ** Tags removed: 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: 1861122 packages: main: linux-aws meta: linux-meta-aws - phase: Holding before Promote to Updates - phase-changed: Wednesday, 12. February 2020 03:08 UTC + phase: Ready for Promote to Updates + phase-changed: Monday, 17. February 2020 01:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Pending -- ready to copy trackers: xenial/linux-aws/aws-kernel: bug 1861106 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/1861107 Title: xenial/linux-aws: 4.4.0-1102.113 -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: Confirmed Status in Kernel SRU Workflow regression-testing series: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-aws package in Ubuntu: Invalid Status in linux-aws 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: 1861122 packages: main: linux-aws meta: linux-meta-aws phase: Ready for Promote to Updates phase-changed: Monday, 17. February 2020 01:57 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Pending -- ready to copy trackers: xenial/linux-aws/aws-kernel: bug 1861106 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863455] [NEW] USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28
You have been subscribed to a public bug: Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. Keyboard and mouse (both connected via USB) are not working. It looks like everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the new kernel version has problems with the USB system. If I choose in GRUB an older kernel version (e.g. 5.0.0-37) everything is fine. Same problem with kernel 5.3.0-28. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Feb 16 05:14:11 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2019-03-19 (333 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7817 ProcEnviron: LANGUAGE=de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic fonts kubuntu ubuntu -- USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28 https://bugs.launchpad.net/bugs/1863455 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 1863086] Re: unkillable process (kernel NULL pointer dereference)
The regression was introduced by the following commit: commit 315c69261dd3fa12dbc830d4fa00d1fad98d3b03 Author: Paul Wise Date: Fri Aug 2 21:49:05 2019 -0700 Subject: coredump: split pipe command whitespace before expanding template You can read it here: https://github.com/torvalds/linux/commit/315c69261dd3fa12dbc830d4fa00d1fad98d3b03 This landed in 5.3-rc3, and is still in latest mainline. Reading through the commit message, the linux-fsdevel message and the debian bug found in the commit message, it just seems that the new changes omit the NULL case, and construct the helper_argv[] array slightly differently than it did before. I confirmed this commit is the root cause by reverting this commit on a v5.3 build and seeing the old correct behaviour return. I'll try write a patch to fix this, or I will contact the upstream maintainer for a fix in the coming days. ** Changed in: linux (Ubuntu Eoan) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu Focal) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863086 Title: unkillable process (kernel NULL pointer dereference) Status in linux package in Ubuntu: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: If process that listens socket on any port crashes (segmentation fault) it becomes unkillable. Kill command does not kill this process. Port that listen crashed process never be freed. journalctl shows error: Feb 13 13:28:09 vbun04 kernel: socktest[1359]: segfault at 21 ip 55ec3a6bf11e sp 7ffd88899fb0 error 6 in socktest[55ec3a6bf000+1000] Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: BUG: kernel NULL pointer dereference, address: 0020 Feb 13 13:28:09 vbun04 kernel: #PF: supervisor read access in kernel mode Feb 13 13:28:09 vbun04 kernel: #PF: error_code(0x) - not-present page Feb 13 13:28:09 vbun04 kernel: PGD 0 P4D 0 Feb 13 13:28:09 vbun04 kernel: Oops: [#1] SMP NOPTI Feb 13 13:28:09 vbun04 kernel: CPU: 1 PID: 1359 Comm: socktest Tainted: G OE 5.3.0-29-generic #31-Ubuntu Feb 13 13:28:09 vbun04 kernel: Hardware name: innotek GmbH VirtualBox/VirtualBox, BIOS VirtualBox 12/01/2006 Feb 13 13:28:09 vbun04 kernel: RIP: 0010:do_coredump+0x536/0xb30 Feb 13 13:28:09 vbun04 kernel: Code: 00 48 8b bd 18 ff ff ff 48 85 ff 74 05 e8 c2 47 fa ff 65 48 8b 04 25 c0 6b 01 00 48 8b 00 48 8b 7d a0 a8 04 0f 85 65 05 00 00 <48> 8b 57 20 0f b7 02 66 25 00 f0 66 3d 00 80 0f Feb 13 13:28:09 vbun04 kernel: RSP: :b464c2c5fca8 EFLAGS: 00010246 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: 9d4b76995100 RCX: 1afc Feb 13 13:28:09 vbun04 kernel: RDX: RSI: b464c2c5fc68 RDI: Feb 13 13:28:09 vbun04 kernel: RBP: b464c2c5fdd8 R08: 0400 R09: b464c2c5fbe0 Feb 13 13:28:09 vbun04 kernel: R10: 9d4b75d01170 R11: R12: 9d4b7b3df540 Feb 13 13:28:09 vbun04 kernel: R13: 0001 R14: R15: b9f15920 Feb 13 13:28:09 vbun04 kernel: FS: 7f6c91911540() GS:9d4b7db0() knlGS: Feb 13 13:28:09 vbun04 kernel: CS: 0010 DS: ES: CR0: 80050033 Feb 13 13:28:09 vbun04 kernel: CR2: 0020 CR3: 723ac003 CR4: 000606e0 Feb 13 13:28:09 vbun04 kernel: Call Trace: Feb 13 13:28:09 vbun04 kernel: ? wake_up_state+0x10/0x20 Feb 13 13:28:09 vbun04 kernel: ? __send_signal+0x1eb/0x3f0 Feb 13 13:28:09 vbun04 kernel: get_signal+0x159/0x880 Feb 13 13:28:09 vbun04 kernel: do_signal+0x34/0x280 Feb 13 13:28:09 vbun04 kernel: ? bad_area+0x47/0x50 Feb 13 13:28:09 vbun04 kernel: exit_to_usermode_loop+0xbf/0x160 Feb 13 13:28:09 vbun04 kernel: prepare_exit_to_usermode+0x77/0xa0 Feb 13 13:28:09 vbun04 kernel: retint_user+0x8/0x8 Feb 13 13:28:09 vbun04 kernel: RIP: 0033:0x55ec3a6bf11e Feb 13 13:28:09 vbun04 kernel: Code: 04 24 02 00 17 70 89 c5 48 b8 30 30 30 30 30 30 30 30 89 ef 48 89 44 24 08 e8 8e ff ff ff be 0a 00 00 00 89 ef e8 72 ff ff ff 04 25 21 00 00 00 21 00 00 00 48 8b 44 24 18 Feb 13 13:28:09 vbun04 kernel: RSP: 002b:7ffd88899fb0 EFLAGS: 00010217 Feb 13 13:28:09 vbun04 kernel: RAX: RBX: RCX: 7f6c918424eb Feb 13 13:28:09 vbun04 kernel: RDX: 0010 RSI: 000a RDI: 0003 Feb 13 13:28:09 vbun04 kernel: RBP: 0003 R08: R09: 7f6c919331f0 Feb 13 13:28:09 vbun04 kernel: R10: R11:
[Kernel-packages] [Bug 1861162] Re: xenial/linux-deeplens: 4.15.0-1016.16 -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: 1862823 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Updates phase-changed: Friday, 14. February 2020 22:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Holding -- master bug not ready for release 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/1861162 Title: xenial/linux-deeplens: 4.15.0-1016.16 -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: 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: 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: Fix Released Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: Invalid 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: 1862823 packages: main: linux-deeplens meta: linux-meta-deeplens phase: Holding before Promote to Updates phase-changed: Friday, 14. February 2020 22:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861162/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863455] 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/1863455 Title: USB system (mouse and keybord) are not working since kernel update to 5.3.0-26 and 5.3.0-28 Status in linux package in Ubuntu: Confirmed Bug description: Since the kernel update to 5.3.0-26 it is not possible to use Ubuntu. Keyboard and mouse (both connected via USB) are not working. It looks like everything is frozen, but also ALT+PRINT REISUB is not working, so I guess the new kernel version has problems with the USB system. If I choose in GRUB an older kernel version (e.g. 5.0.0-37) everything is fine. Same problem with kernel 5.3.0-28. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: xorg 1:7.7+19ubuntu7.1 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 Uname: Linux 5.0.0-37-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 BootLog: Error: [Errno 13] Keine Berechtigung: '/var/log/boot.log' CompositorRunning: None CurrentDesktop: KDE Date: Sun Feb 16 05:14:11 2020 DistUpgraded: Fresh install DistroCodename: bionic DistroVariant: ubuntu DkmsStatus: virtualbox, 5.2.34, 5.0.0-37-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-26-generic, x86_64: installed virtualbox, 5.2.34, 5.3.0-28-generic, x86_64: installed EcryptfsInUse: Yes ExtraDebuggingInterest: Yes GraphicsCard: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06) (prog-if 00 [VGA controller]) Subsystem: Micro-Star International Co., Ltd. [MSI] Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [1462:7817] InstallationDate: Installed on 2019-03-19 (333 days ago) InstallationMedia: Kubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64 (20190210) MachineType: MSI MS-7817 ProcEnviron: LANGUAGE=de PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=de_DE.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-37-generic root=UUID=bd7aadf3-2ec3-43b1-a590-407076e37c31 ro quiet splash vt.handoff=1 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/26/2013 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V4.1 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: B85M-P33 (MS-7817) dmi.board.vendor: MSI dmi.board.version: 1.0 dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: MSI dmi.chassis.version: 1.0 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV4.1:bd04/26/2013:svnMSI:pnMS-7817:pvr1.0:rvnMSI:rnB85M-P33(MS-7817):rvr1.0:cvnMSI:ct3:cvr1.0: dmi.product.family: To be filled by O.E.M. dmi.product.name: MS-7817 dmi.product.sku: To be filled by O.E.M. dmi.product.version: 1.0 dmi.sys.vendor: MSI version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.99-1ubuntu1~18.04.2 version.libgl1-mesa-dri: libgl1-mesa-dri 19.2.8-0ubuntu0~18.04.2 version.libgl1-mesa-glx: libgl1-mesa-glx 19.2.8-0ubuntu0~18.04.2 version.xserver-xorg-core: xserver-xorg-core N/A version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati N/A version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau N/A To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863455/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862723] Re: 18.04 can't auto load ib_uverbs (18.04.3 hwe can) for Mellanox PMD nics
** Summary changed: - 18.04 can't auto load ub_iverbs (18.04.3 hwe can) for Mellanox PMD nics + 18.04 can't auto load ib_uverbs (18.04.3 hwe can) for Mellanox PMD nics -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862723 Title: 18.04 can't auto load ib_uverbs (18.04.3 hwe can) for Mellanox PMD nics Status in linux package in Ubuntu: Incomplete Bug description: 18.04 ga-kernel to load ib_uverbs model which required by Mellanox PMD ( 18.04.3 hwe can auto load via model depends) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1862723/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863072] Re: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 14. February 2020 08:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff variant: debs -- 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/1863072 Title: bionic/linux-oem: 4.15.0-1072.82 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Fix Released Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-oem package in Ubuntu: Invalid Status in linux-oem 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: 1862824 packages: lrm: linux-restricted-modules-oem main: linux-oem meta: linux-meta-oem signed: linux-signed-oem phase: Testing phase-changed: Friday, 14. February 2020 08:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Stalled -- waiting for signoff variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863072/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855668] Comment bridged from LTC Bugzilla
--- Comment From daniel.axte...@ibm.com 2020-02-17 00:27 EDT---
Hi,
I'm sorry, I thought I had already mentioned this but it was a case of
me getting projects and teams mixed up.
Please could you pick up (in addition to the issue still pending) commit
69393cb03ccd ("powerpc/xmon: Restrict when kernel is locked down").
>From the pull-request that included it, the commit does the following:
- A change to xmon (our crash handler / pseudo-debugger) to restrict
it to read-only mode when the kernel is lockdown'ed, otherwise it's
trivial to drop into xmon and modify kernel data, such as the
lockdown state.
To exploit this you'd need to boot with command line including
'xmon=rw', as xmon isn't read-write by default on the Focal kernel, but
that's not exactly a challenge. I have used this to drop down from
lockdown=confidentiality to lockdown=none on 5.4.0-14-generic #17-Ubuntu
Regards,
Daniel
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1855668
Title:
lockdown on power
Status in The Ubuntu-power-systems project:
Fix Committed
Status in linux package in Ubuntu:
Fix Committed
Bug description:
== Comment: #0 - Michael Ranweiler - 2019-11-11
08:50:51 ==
For 20.04 testing/inclusion. The ubuntu kernel team has a ppa here for
testing:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable
Test results will follow...
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1855668/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863489] Re: intel grafic i915 driver no power saving states rc6
I am off from my testobject for a few days - will at this later. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863489 Title: intel grafic i915 driver no power saving states rc6 Status in linux package in Ubuntu: Incomplete Bug description: It seems that the i915 intel graphic driver in newer kernels (observed with 5.3) doesn't support energy saving. How do I know that? Using powertop shows in idle tab the GPU - and this shows only : GPU power on 100% - no rc6 or deeper states are used. For some strange reason also the packet (summery?) shows in all states 0%, although I can observe the individual CPU cores are in different power states. The previous parameter enable_rc6 is not existing anymore. The other possible energy saving parameter enable_dc (if set to 1 or 2) results in log with: setting dangerous option enable_dc - tainting kernel. Any idea what might go wrong there? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863489/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1855668] Re: lockdown on power
Hi Daniel, I found that that commit 69393cb03ccd "powerpc/xmon: Restrict when kernel is locked down" landed upstream with v5.5-rc1. I created a separate LP bug / ticket to get it into focal's kernel 5.4 (hoping that it's a simple cherry pick): LP 1863562 - "Restrict ppc64el xmon to read-only-mode if kernel is locked down" https://bugs.launchpad.net/ubuntu-power-systems/+bug/1863562 You may consider mirroring LP 1863562 to bugzilla for completeness reasons. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1855668 Title: lockdown on power Status in The Ubuntu-power-systems project: Fix Committed Status in linux package in Ubuntu: Fix Committed Bug description: == Comment: #0 - Michael Ranweiler - 2019-11-11 08:50:51 == For 20.04 testing/inclusion. The ubuntu kernel team has a ppa here for testing: https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/unstable Test results will follow... To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1855668/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861134] Re: bionic/linux-raspi2: 4.15.0-1055.59 -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: '1862824' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Sunday, 16. February 2020 19:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - promote-to-updates: Holding -- cycle not ready to release + promote-to-updates: Holding -- master bug not ready for release trackers: bionic/linux-raspi2/pi-kernel: bug 1861133 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1861134 Title: bionic/linux-raspi2: 4.15.0-1055.59 -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: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Fix Released Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 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: '1862824' packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Holding before Promote to Updates phase-changed: Sunday, 16. February 2020 19:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: promote-to-updates: Holding -- master bug not ready for release trackers: bionic/linux-raspi2/pi-kernel: bug 1861133 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1857409] Re: alsa/sof: load different firmware on different platforms
The patch has been reverted by https://bugs.launchpad.net/bugs/1860642 ** Changed in: linux-oem-osp1 (Ubuntu Bionic) Status: Fix Released => 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/1857409 Title: alsa/sof: load different firmware on different platforms Status in HWE Next: New Status in OEM Priority Project: New Status in linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Fix Released Status in linux-oem-osp1 source package in Bionic: Confirmed Status in linux source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Bug description: [Impact] In our ubuntu kernel, the sof driver will load the sof-cnl.ri (firmware) on all platforms, but mainline kernel already supported the multi firmwares on differnt platforms, and OEM project needs us to support the mutli-firmware names in the ubuntu kernel [Fix] cherry-pick 3 upstream patches, then on cnl platforms, it will load sof-cnl.ri, on cml platfomrs, it will load sof-cml.ri, on cfl platforms, it will load sof-cfl.ri [Test Case] Prepare the firmware from https://github.com/thesofproject/linux-firmware master branch, then boot the kernel with these patches. [Regression Risk] Low, just let different platforms load differnt firmware, and these patches are in the upstream kernel. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1857409/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863338] Re: xenial/linux: 4.4.0-175.205 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863338 Title: xenial/linux: 4.4.0-175.205 -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 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 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 packages: main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Saturday, 15. February 2020 05:06 UTC reason: promote-to-proposed: Stalled -- another kernel is currently pending in Proposed trackers: trusty/linux-aws: bug 1863334 trusty/linux-lts-xenial: bug 1863336 xenial/linux-aws: bug 1863311 xenial/linux-cascade: bug 1863314 xenial/linux-fips: bug 1863331 xenial/linux-kvm: bug 1863319 xenial/linux-raspi2: bug 1863324 xenial/linux-snapdragon: bug 1863329 xenial/linux/caracalla-kernel: bug 1863304 xenial/linux/pc-kernel: bug 1863306 xenial/linux/stlouis-kernel: bug 1863307 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863338/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863297] Re: disco/linux: 5.0.0-42.46 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863297 Title: disco/linux: 5.0.0-42.46 -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-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: 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 verification-testing series: New 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Saturday, 15. February 2020 01:37 UTC reason: promote-to-proposed: Stalled -- another kernel is currently pending in Proposed trackers: bionic/linux-aws-5.0: bug 1863281 bionic/linux-azure: bug 1863285 bionic/linux-bluefield: bug 1863295 bionic/linux-gcp: bug 1863289 bionic/linux-gke-5.0: bug 1863293 bionic/linux-hwe-5.0: bug 1863276 bionic/linux-oem-osp1: bug 1863279 bionic/linux-oracle-5.0: bug 1863296 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863297/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863294] Re: eoan/linux: 5.3.0-41.33 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863294 Title: eoan/linux: 5.3.0-41.33 -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-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 package in Ubuntu: Invalid Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Saturday, 15. February 2020 04:47 UTC reason: promote-to-proposed: Stalled -- another kernel is currently pending in Proposed trackers: bionic/linux-hwe: bug 1863292 eoan/linux-aws: bug 1863272 eoan/linux-azure: bug 1863274 eoan/linux-gcp: bug 1863280 eoan/linux-kvm: bug 1863283 eoan/linux-oracle: bug 1863290 eoan/linux-raspi2: bug 1863269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863294/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863350] Re: bionic/linux: 4.15.0-89.89 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Andy Whitcroft (apw) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863350 Title: bionic/linux: 4.15.0-89.89 -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-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 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 packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Holding before Promote to Proposed phase-changed: Saturday, 15. February 2020 04:06 UTC reason: promote-to-proposed: Stalled -- another kernel is currently pending in Proposed trackers: bionic/linux-aws: bug 1863325 bionic/linux-fips: bug 1863341 bionic/linux-gke-4.15: bug 1863330 bionic/linux-ibm-gt: bug 1863335 bionic/linux-kvm: bug 1863332 bionic/linux-oem: bug 1863312 bionic/linux-oracle: bug 1863339 bionic/linux-raspi2: bug 1863305 bionic/linux-snapdragon: bug 1863310 bionic/linux/pc-kernel: bug 1863301 bionic/linux/pc-lowlatency-kernel: bug 1863302 xenial/linux-azure: bug 1863344 xenial/linux-gcp: bug 1863347 xenial/linux-hwe: bug 1863349 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863350/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863479] [NEW] package nvidia-compute-utils-435 (not installed) failed to install/upgrade: installed nvidia-compute-utils-435 package post-installation script subprocess returne
Public bug reported: I tried to remove the package also ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-compute-utils-435 (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sun Feb 16 15:52:50 2020 ErrorMessage: installed nvidia-compute-utils-435 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: nvidia-graphics-drivers-435 Title: package nvidia-compute-utils-435 (not installed) failed to install/upgrade: installed nvidia-compute-utils-435 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-01-24 (23 days ago) ** Affects: nvidia-graphics-drivers-435 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-435 in Ubuntu. https://bugs.launchpad.net/bugs/1863479 Title: package nvidia-compute-utils-435 (not installed) failed to install/upgrade: installed nvidia-compute-utils-435 package post- installation script subprocess returned error exit status 1 Status in nvidia-graphics-drivers-435 package in Ubuntu: New Bug description: I tried to remove the package also ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-compute-utils-435 (not installed) ProcVersionSignature: Ubuntu 5.4.0-14.17-generic 5.4.18 Uname: Linux 5.4.0-14-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 Date: Sun Feb 16 15:52:50 2020 ErrorMessage: installed nvidia-compute-utils-435 package post-installation script subprocess returned error exit status 1 Python3Details: /usr/bin/python3.8, Python 3.8.2rc1, python3-minimal, 3.8.0-3 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.9 SourcePackage: nvidia-graphics-drivers-435 Title: package nvidia-compute-utils-435 (not installed) failed to install/upgrade: installed nvidia-compute-utils-435 package post-installation script subprocess returned error exit status 1 UpgradeStatus: Upgraded to focal on 2020-01-24 (23 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-435/+bug/1863479/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862816] Re: trusty/linux-azure: 4.15.0-1071.76~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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Promote to Proposed - phase-changed: Sunday, 16. February 2020 13:36 UTC + phase: Promote to Proposed + phase-changed: Sunday, 16. February 2020 15:32 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- review in progress 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/1862816 Title: trusty/linux-azure: 4.15.0-1071.76~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: In Progress 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: 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: 1862818 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Promote to Proposed phase-changed: Sunday, 16. February 2020 15:32 UTC reason: promote-signing-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1862816/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863562] Re: Restrict xmon to read-only-mode if kernel is locked down
** Summary changed:
- Restrict ppc64el xmon to read-only-mode if kernel is locked down
+ Restrict xmon to read-only-mode if kernel is locked down
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863562
Title:
Restrict xmon to read-only-mode if kernel is locked down
Status in The Ubuntu-power-systems project:
Triaged
Status in linux package in Ubuntu:
Triaged
Bug description:
This is a spin off of LP 1855668 (see comment #11 there:)
Please could you pick up (in addition to the issue still pending) commit
69393cb03ccd ("powerpc/xmon: Restrict when kernel is locked down").
From the pull-request that included it, the commit does the following:
- A change to xmon (our crash handler / pseudo-debugger) to restrict
it to read-only mode when the kernel is lockdown'ed, otherwise it's
trivial to drop into xmon and modify kernel data, such as the
lockdown state.
To exploit this you'd need to boot with command line including
'xmon=rw', as xmon isn't read-write by default on the Focal kernel,
but that's not exactly a challenge. I have used this to drop down from
lockdown=confidentiality to lockdown=none on 5.4.0-14-generic
#17-Ubuntu
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1863562/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848978] Re: CML: perf enabling for core
** Changed in: oem-priority
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1848978
Title:
CML: perf enabling for core
Status in intel:
Fix Committed
Status in OEM Priority Project:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux-oem-osp1 package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Won't Fix
Status in linux-oem-osp1 source package in Bionic:
Fix Released
Status in linux source package in Disco:
Won't Fix
Status in linux-oem-osp1 source package in Disco:
Fix Released
Status in linux source package in Eoan:
Fix Released
Status in linux-oem-osp1 source package in Eoan:
Fix Released
Status in linux source package in Focal:
Confirmed
Status in linux-oem-osp1 source package in Focal:
Confirmed
Bug description:
[SRU Justification]
[Impact]
There is no complete perf support for Comet Lake CPU. For Ice Lake, some
changes has been included in v5.3, but still misses CPU IDs.
[Fix]
perf support for Comet Lake is based on previous works for Ice Lake, so
changes for both have to be backported.
[Test Case]
On platforms with Comet Lake/Ice Lake CPUs, one should find new
cstate_pkg events c{8,9,10}-residency appear in output of `perf list`
for use.
[Regression Potential]
Low. This backports perf support for previously incompletedly supported
cpu models.
== original bug description ==
Description:
CML perf enabling for core
v5.4-rc3
1ffa6c04dae39776a3c222bdf88051e394386c01
9066288b2aab1804dc1eebec6ff88474363b89cb
9674b1cc0f94c34f76e58c102623a866836f269e
Target Kernel: 5.4
Target Release: 20.04
To manage notifications about this bug go to:
https://bugs.launchpad.net/intel/+bug/1848978/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
