[Kernel-packages] [Bug 1848978] Re: CML: perf enabling for core
Fixed that for two more patches for IceLake, but the resulting tree fails to enter deeper state than PC3. -- You 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 linux package in Ubuntu: Confirmed Status in linux-oem-osp1 package in Ubuntu: Confirmed Status in linux source package in Bionic: Confirmed Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux source package in Disco: New Status in linux-oem-osp1 source package in Disco: Confirmed Status in linux source package in Eoan: New Status in linux-oem-osp1 source package in Eoan: Confirmed Status in linux source package in Focal: Confirmed Status in linux-oem-osp1 source package in Focal: Confirmed 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
[Kernel-packages] [Bug 1853246] Re: [SRU][B/OEM-B/OEM-OSP1/D] Enable new touchpads which are not in current whitelist
** Tags added: oem-priority originate-from-1851774 sutton -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853246 Title: [SRU][B/OEM-B/OEM-OSP1/D] Enable new touchpads which are not in current whitelist Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: SRU justification: [Impact] New touchpads are ignored by hid driver because of IDs are missed in the whitelist. [Fix] Only 2 Elan touchpad IDs are allowed to be loaded in hid driver. Change to the blacklist of elan touchpads supported by elan_i2c, so others can be enabled by hid. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. keep current IDs of elan_i2c, loads those touchpads ID those weren't supported. Those patches are already in 5.3+ kernel, only bionic and disco kernel need them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Promote to Proposed - phase-changed: Wednesday, 20. November 2019 05:46 UTC + phase: Testing + phase-changed: Wednesday, 20. November 2019 07:21 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 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/1852302 Title: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Testing phase-changed: Wednesday, 20. November 2019 07:21 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853246] 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 1853246 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/1853246 Title: [SRU][B/OEM-B/OEM-OSP1/D] Enable new touchpads which are not in current whitelist Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: SRU justification: [Impact] New touchpads are ignored by hid driver because of IDs are missed in the whitelist. [Fix] Only 2 Elan touchpad IDs are allowed to be loaded in hid driver. Change to the blacklist of elan touchpads supported by elan_i2c, so others can be enabled by hid. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. keep current IDs of elan_i2c, loads those touchpads ID those weren't supported. Those patches are already in 5.3+ kernel, only bionic and disco kernel need them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853246] [NEW] [SRU][B/OEM-B/OEM-OSP1/D] Enable new touchpads which are not in current whitelist
Public bug reported: SRU justification: [Impact] New touchpads are ignored by hid driver because of IDs are missed in the whitelist. [Fix] Only 2 Elan touchpad IDs are allowed to be loaded in hid driver. Change to the blacklist of elan touchpads supported by elan_i2c, so others can be enabled by hid. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. keep current IDs of elan_i2c, loads those touchpads ID those weren't supported. Those patches are already in 5.3+ kernel, only bionic and disco kernel need them. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: oem-priority originate-from-1851774 sutton ** Description changed: SRU justification: [Impact] New touchpads are ignored by hid driver because of IDs are missed in the whitelist. [Fix] Only 2 Elan touchpad IDs are allowed to be loaded in hid driver. Change to the blacklist of elan touchpads supported by elan_i2c, so others can be enabled by hid. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. keep current IDs of elan_i2c, loads those touchpads ID those weren't supported. + + Those patches are already in 5.3+ kernel, + only bionic and disco kernel need them. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853246 Title: [SRU][B/OEM-B/OEM-OSP1/D] Enable new touchpads which are not in current whitelist Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: SRU justification: [Impact] New touchpads are ignored by hid driver because of IDs are missed in the whitelist. [Fix] Only 2 Elan touchpad IDs are allowed to be loaded in hid driver. Change to the blacklist of elan touchpads supported by elan_i2c, so others can be enabled by hid. [Test] Verified on hardware. Tests results are good. [Regression Potential] Low. keep current IDs of elan_i2c, loads those touchpads ID those weren't supported. Those patches are already in 5.3+ kernel, only bionic and disco kernel need them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1853246/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853075] Re: 19.10 Boots into a black screen
Should I build this from source? Or is there a .deb package that I can install with dpkg? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen Status in linux package in Ubuntu: Invalid Bug description: After upgrading to 19.10 and rebooting. My machine goes into a frozen black screen. The default kernel after the update (5.3.0-23-generic) does not succeed in booting. If I select the older kernel, 5.0.0-36-generic, grub does go through and succeeds booting up. System is a Dell XPS 15 9550 with Ubuntu Dual Boot. GRUB version 2.04-1ubuntu12. The Windows partition does work properly, and I am able to boot into it. Please advice on how to proceed with a fix, or if an update pushed to grub will fix this issue. Thanks. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pipemon2417 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c26ef9c3-b999-4441-b750-cf80d00fc68e InstallationDate: Installed on 2017-11-02 (746 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic root=UUID=6b1a4315-6bdf-471f-90b5-6fb32c3bfc2b ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-36-generic N/A linux-backports-modules-5.0.0-36-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.0.0-36-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-18 (0 days ago) UserGroups: adm audio cdrom dialout dip kvm lpadmin plugdev pulse sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd07/30/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853192] Re: Please add patch fixing RK818 ID detection
** Also affects: linux (Ubuntu Focal) Importance: Undecided Assignee: Po-Hsu Lin (cypressyew) Status: In Progress ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: linux (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Tags added: bionic disco eoan focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853192 Title: Please add patch fixing RK818 ID detection Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: Hi, Please add this upstream patch to ubuntu kernel: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=37ef8c2c15bdc1322b160e38986c187de2b877b2 It fixes detection of RK818 pmic. Without it ubuntu hangs at boot. Cheers Paweł Jarosz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1851347] Re: libmbim-proxy using 100% CPU on a Dell Edge Gateway 3002
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851347 Title: libmbim-proxy using 100% CPU on a Dell Edge Gateway 3002 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Impact == A Dell Edge Gateway 3002 user reported that `top` reports around 100% CPU usage for the libmbim-proxy process. Seen in at least 40% of their devices at some point during the last 6 months. The CPU keeps high at ~100% days or weeks, but does return back to normal without a reboot. The LTE connectivity is seemingly still working as usual. The issue starts after an EPIPE error in the syslogs: 'cdc_mbim 1-3:1.12: nonzero urb status received: -EPIPE'. == Fix == 8fec9355a968 USB: cdc-wdm: ignore -EPIPE from GetEncapsulatedResponse This has been in mainline kernel since 4.14. == Testcase == Connect to the LTE network and see if libmbim-proxy uses 100% after some point. == Risk of Regression == Low, since 1. Already tested by original reporter and no issue found after more than a week (usually it fails twice in a week). 2. Ignoring -EPIPE is the default behavior after 4.14. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1851347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852268] Re: bionic/linux-aws-fips: 4.15.0-2005.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: 1852270 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:21 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/1852268 Title: bionic/linux-aws-fips: 4.15.0-2005.5 -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: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New 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: 1852270 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:21 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/1852268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825222] Re: CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64, arm64
https://lists.ubuntu.com/archives/kernel-team/2019-November/105575.html ** Description changed: - Would it be possible to enable rockchip support in Ubuntu 18.04 kernel - for arch aarch64(arm64)? + == SRU Justification == + We already have this ROCKCHIP support enabled for armhf (bug 1566283), + let's enable it for arm64 as well. + + The only difference is arm64=m for CONFIG_CRYPTO_DEV_ROCKCHIP as + requested, it was set to 'n' for armhf. + + == Fix == + Enable the corresponding kernel configs for B/D/E/F. + + == Test == + Test kernels could be found here: + https://people.canonical.com/~phlin/kernel/lp-1825222-rockchip-arm64/ + + Kernel tested by Paweł, the bug reporter, with positive test results. + The kernel will need another RK818 ID detection patch, which will be + handled in bug 1853192. + + == Regression Potential == + Low, this patch just add the ARM64 support for ROCKCHIP, this should + not have impact to normal users. + + + == Original Bug Report == + Would it be possible to enable rockchip support in Ubuntu 18.04 kernel for arch aarch64(arm64)? Related kernel config options: CONFIG_ARCH_ROCKCHIP CONFIG_PCIE_ROCKCHIP CONFIG_PCIE_ROCKCHIP_HOST CONFIG_EMAC_ROCKCHIP CONFIG_DWMAC_ROCKCHIP CONFIG_ROCKCHIP_PHY CONFIG_SPI_ROCKCHIP CONFIG_PINCTRL_ROCKCHIP CONFIG_ROCKCHIP_IODOMAIN CONFIG_ROCKCHIP_THERMAL CONFIG_VIDEO_ROCKCHIP_RGA CONFIG_DRM_ROCKCHIP CONFIG_ROCKCHIP_ANALOGIX_DP CONFIG_ROCKCHIP_CDN_DP CONFIG_ROCKCHIP_DW_HDMI CONFIG_ROCKCHIP_DW_MIPI_DSI CONFIG_ROCKCHIP_INNO_HDMI CONFIG_ROCKCHIP_LVDS CONFIG_ROCKCHIP_RGB CONFIG_SND_SOC_ROCKCHIP CONFIG_SND_SOC_ROCKCHIP_I2S CONFIG_SND_SOC_ROCKCHIP_PDM CONFIG_SND_SOC_ROCKCHIP_SPDIF CONFIG_SND_SOC_ROCKCHIP_MAX98090 CONFIG_SND_SOC_ROCKCHIP_RT5645 CONFIG_MMC_DW_ROCKCHIP CONFIG_ROCKCHIP_TIMER CONFIG_ROCKCHIP_MBOX CONFIG_ROCKCHIP_IOMMU CONFIG_ROCKCHIP_GRF CONFIG_ROCKCHIP_PM_DOMAINS CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI CONFIG_ROCKCHIP_SARADC CONFIG_PWM_ROCKCHIP CONFIG_PHY_ROCKCHIP_DP CONFIG_PHY_ROCKCHIP_EMMC CONFIG_PHY_ROCKCHIP_INNO_HDMI CONFIG_PHY_ROCKCHIP_INNO_USB2 CONFIG_PHY_ROCKCHIP_PCIE CONFIG_PHY_ROCKCHIP_TYPEC CONFIG_PHY_ROCKCHIP_USB CONFIG_ROCKCHIP_EFUSE CONFIG_CRYPTO_DEV_ROCKCHIP Cheers, Paweł Jarosz ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: Incomplete ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Disco) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Eoan) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Focal) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Disco) Status: New => In Progress ** Changed in: linux (Ubuntu Eoan) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Focal) Status: Incomplete => 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/1825222 Title: CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64,arm64 Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in linux source package in Focal: In Progress Bug description: == SRU Justification == We already have this ROCKCHIP support enabled for armhf (bug 1566283), let's enable it for arm64 as well. The only difference is arm64=m for CONFIG_CRYPTO_DEV_ROCKCHIP as requested, it was set to 'n' for armhf. == Fix == Enable the corresponding kernel configs for B/D/E/F. == Test == Test kernels could be found here: https://people.canonical.com/~phlin/kernel/lp-1825222-rockchip-arm64/ Kernel tested by Paweł, the bug reporter, with positive test results. The kernel will need another RK818 ID detection patch, which will be handled in bug 1853192. == Regression Potential == Low, this patch just add the ARM64 support for ROCKCHIP, this should not have impact to normal users. == Original Bug Report == Would it be possible to enable rockchip support in Ubuntu 18.04 kernel for arch aarch64(arm64)? Related kernel config options: CONFIG_ARCH_ROCKCHIP CONFIG_PCIE_ROCKCHIP CONFIG_PCIE_ROCKCHIP_HOST CONFIG_EMAC_ROCKCHIP CONFIG_DWMAC_ROCKCHIP CONFIG_ROCKCHIP_PHY CONFIG_SPI_ROCKCHIP CONFIG_PINCTRL_ROCKCHIP CONFIG_ROCKCHIP_IODOMAIN CONFIG_ROCKCHIP_THERMAL CONFIG_VIDEO_ROCKCHIP_RGA CONFIG_DRM_ROCKCHIP CONFIG_ROCKCHIP_ANALOGIX_DP CONFIG_ROCKCHIP_CDN_DP CONFIG_ROCKCHIP_DW_HDMI CONFIG_ROCKCHIP_DW_MIPI_DSI CONFIG_ROCKCHIP_INNO_HDMI CONFIG_ROCKCHIP_LVDS CONFIG_ROCKCHIP_RGB CONFIG_SND_SOC_ROCKCHIP
[Kernel-packages] [Bug 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 20. November 2019 05:32 UTC reason: - promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,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/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 20. November 2019 05:32 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.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: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon - phase: Ready for Promote to Proposed - phase-changed: Monday, 18. November 2019 07:26 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 20. November 2019 05:46 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 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/1852302 Title: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in 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: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Wednesday, 20. November 2019 05:46 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852302] Re: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve Langasek (vorlon) -- 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/1852302 Title: xenial/linux-snapdragon: 4.4.0-1130.138 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in 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: 1852306 packages: main: linux-snapdragon meta: linux-meta-snapdragon phase: Promote to Proposed phase-changed: Wednesday, 20. November 2019 05:46 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-snapdragon/dragonboard-kernel: bug 1852301 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852302/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Wednesday, 20. November 2019 04:25 UTC + phase: Holding before Promote to Proposed + phase-changed: Wednesday, 20. November 2019 05:32 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,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/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Wednesday, 20. November 2019 05:32 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:building,meta:queued,signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1157681] Re: Some drm/radeon *ERROR* messages unnecessarily alarm the user
** Changed in: linux Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #293 https://gitlab.freedesktop.org/drm/amd/issues/293 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1157681 Title: Some drm/radeon *ERROR* messages unnecessarily alarm the user Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Message in monitor in start Ubuntu: [ 21.313079] [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-13-generic 3.8.0-13.23 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2100 F pulseaudio Date: Wed Mar 20 08:58:51 2013 HibernationDevice: RESUME=UUID=935761c6-0879-49ed-b5a5-c5218c97b843 InstallationDate: Installed on 2013-02-06 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) Lsusb: Bus 001 Device 002: ID 046d:0896 Logitech, Inc. OrbiCam Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Ferrari 1000 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=d1524094-f99b-4050-8e1b-40b1526ca8f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-13-generic N/A linux-backports-modules-3.8.0-13-generic N/A linux-firmware1.104 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/07 dmi.bios.vendor: Acer dmi.bios.version: v1.3204 dmi.board.name: Ferrari6 dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3204:bd09/11/07:svnAcer,inc.:pnFerrari1000:pvrNotApplicable:rvnAcer,Inc.:rnFerrari6:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Ferrari 1000 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1157681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276958] Re: Discrete Radeon videocard is missing with kernel 3.13
** Changed in: linux Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #433 https://gitlab.freedesktop.org/drm/amd/issues/433 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276958 Title: Discrete Radeon videocard is missing with kernel 3.13 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Discrete videocard is missing linux 3.13. There no /sys/kernel/debug/vgaswitcheroo and xrandr --listproviders shows me only Intel videocard. Videocard also missing in lspci output. There are some traces in dmesg which can be related to this bug. The last working kernel version for me is 3.12.9. My configuration: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks [Radeon HD 7650A/7670A] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-7-generic 3.13.0-7.25 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 1964 F pulseaudio CurrentDesktop: GNOME Date: Thu Feb 6 10:48:42 2014 HibernationDevice: RESUME=UUID=af09981e-c60b-4d4e-9bbe-8326111d555f InstallationDate: Installed on 2013-12-27 (40 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MachineType: Dell Inc. Inspiron One 2330 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-7-generic N/A linux-backports-modules-3.13.0-7-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-06 (0 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1276958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1157681]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/293. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1157681 Title: Some drm/radeon *ERROR* messages unnecessarily alarm the user Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Message in monitor in start Ubuntu: [ 21.313079] [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-13-generic 3.8.0-13.23 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2100 F pulseaudio Date: Wed Mar 20 08:58:51 2013 HibernationDevice: RESUME=UUID=935761c6-0879-49ed-b5a5-c5218c97b843 InstallationDate: Installed on 2013-02-06 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) Lsusb: Bus 001 Device 002: ID 046d:0896 Logitech, Inc. OrbiCam Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Ferrari 1000 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=d1524094-f99b-4050-8e1b-40b1526ca8f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-13-generic N/A linux-backports-modules-3.8.0-13-generic N/A linux-firmware1.104 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/07 dmi.bios.vendor: Acer dmi.bios.version: v1.3204 dmi.board.name: Ferrari6 dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3204:bd09/11/07:svnAcer,inc.:pnFerrari1000:pvrNotApplicable:rvnAcer,Inc.:rnFerrari6:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Ferrari 1000 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1157681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1157681]
Still present with kernel-4.0.5-200.fc21.x86_64: [drm:radeon_get_legacy_connector_info_from_bios [radeon]] *ERROR* Unknown connector type: 8 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1157681 Title: Some drm/radeon *ERROR* messages unnecessarily alarm the user Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Message in monitor in start Ubuntu: [ 21.313079] [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-13-generic 3.8.0-13.23 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2100 F pulseaudio Date: Wed Mar 20 08:58:51 2013 HibernationDevice: RESUME=UUID=935761c6-0879-49ed-b5a5-c5218c97b843 InstallationDate: Installed on 2013-02-06 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) Lsusb: Bus 001 Device 002: ID 046d:0896 Logitech, Inc. OrbiCam Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Ferrari 1000 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=d1524094-f99b-4050-8e1b-40b1526ca8f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-13-generic N/A linux-backports-modules-3.8.0-13-generic N/A linux-firmware1.104 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/07 dmi.bios.vendor: Acer dmi.bios.version: v1.3204 dmi.board.name: Ferrari6 dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3204:bd09/11/07:svnAcer,inc.:pnFerrari1000:pvrNotApplicable:rvnAcer,Inc.:rnFerrari6:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Ferrari 1000 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1157681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1276958]
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/433. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1276958 Title: Discrete Radeon videocard is missing with kernel 3.13 Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Discrete videocard is missing linux 3.13. There no /sys/kernel/debug/vgaswitcheroo and xrandr --listproviders shows me only Intel videocard. Videocard also missing in lspci output. There are some traces in dmesg which can be related to this bug. The last working kernel version for me is 3.12.9. My configuration: 00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09) 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks [Radeon HD 7650A/7670A] ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: linux-image-3.13.0-7-generic 3.13.0-7.25 ProcVersionSignature: Ubuntu 3.13.0-7.25-generic 3.13.1 Uname: Linux 3.13.0-7-generic x86_64 ApportVersion: 2.13.2-0ubuntu2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: asudak 1964 F pulseaudio CurrentDesktop: GNOME Date: Thu Feb 6 10:48:42 2014 HibernationDevice: RESUME=UUID=af09981e-c60b-4d4e-9bbe-8326111d555f InstallationDate: Installed on 2013-12-27 (40 days ago) InstallationMedia: Ubuntu-GNOME 13.10 "Saucy Salamander" - Release amd64 (20131017) MachineType: Dell Inc. Inspiron One 2330 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-7-generic.efi.signed root=UUID=13b39ae0-892a-4b5a-ab81-62dba9463c1a ro quiet splash radeon.dpm=1 radeon.runpm=1 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.13.0-7-generic N/A linux-backports-modules-3.13.0-7-generic N/A linux-firmware1.123 SourcePackage: linux UpgradeStatus: Upgraded to trusty on 2014-02-06 (0 days ago) dmi.bios.date: 05/13/2013 dmi.bios.vendor: Dell Inc. dmi.bios.version: A13 dmi.board.name: 09JR1D dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 13 dmi.chassis.vendor: Dell Inc. dmi.chassis.version: 27147636_1 dmi.modalias: dmi:bvnDellInc.:bvrA13:bd05/13/2013:svnDellInc.:pnInspironOne2330:pvr00:rvnDellInc.:rn09JR1D:rvrA00:cvnDellInc.:ct13:cvr27147636_1: dmi.product.name: Inspiron One 2330 dmi.product.version: 00 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1276958/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1157681]
Probably a bios bug. What physical connectors are actually on the board? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1157681 Title: Some drm/radeon *ERROR* messages unnecessarily alarm the user Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: Message in monitor in start Ubuntu: [ 21.313079] [drm:radeon_get_legacy_connector_info_from_bios] *ERROR* Unknown connector type: 8 ProblemType: Bug DistroRelease: Ubuntu 13.04 Package: linux-image-3.8.0-13-generic 3.8.0-13.23 ProcVersionSignature: Ubuntu 3.8.0-13.23-generic 3.8.3 Uname: Linux 3.8.0-13-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.9.2-0ubuntu1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: caravena 2100 F pulseaudio Date: Wed Mar 20 08:58:51 2013 HibernationDevice: RESUME=UUID=935761c6-0879-49ed-b5a5-c5218c97b843 InstallationDate: Installed on 2013-02-06 (41 days ago) InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20121126) Lsusb: Bus 001 Device 002: ID 046d:0896 Logitech, Inc. OrbiCam Bus 003 Device 002: ID 0a5c:2101 Broadcom Corp. BCM2045 Bluetooth Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub MachineType: Acer, inc. Ferrari 1000 MarkForUpload: True PccardctlIdent: Socket 0: no product info available PccardctlStatus: Socket 0: no card ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-13-generic root=UUID=d1524094-f99b-4050-8e1b-40b1526ca8f7 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.8.0-13-generic N/A linux-backports-modules-3.8.0-13-generic N/A linux-firmware1.104 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/11/07 dmi.bios.vendor: Acer dmi.bios.version: v1.3204 dmi.board.name: Ferrari6 dmi.board.vendor: Acer, Inc. dmi.board.version: Not Applicable dmi.chassis.type: 1 dmi.chassis.vendor: Acer, Inc. dmi.chassis.version: N/A dmi.modalias: dmi:bvnAcer:bvrv1.3204:bd09/11/07:svnAcer,inc.:pnFerrari1000:pvrNotApplicable:rvnAcer,Inc.:rnFerrari6:rvrNotApplicable:cvnAcer,Inc.:ct1:cvrN/A: dmi.product.name: Ferrari 1000 dmi.product.version: Not Applicable dmi.sys.vendor: Acer, inc. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1157681/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853061] Re: Connection to USB-C hub frequently drops when charging over it
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc8/ Under v5.4-rc8, run # echo "file drivers/pci/* +p" > /sys/kernel/debug/dynamic_debug/control And attach dmesg when this issue happens again. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853061 Title: Connection to USB-C hub frequently drops when charging over it Status in linux package in Ubuntu: Confirmed Bug description: I am running Ubuntu 19.10 on a Lenovo Thinkpad X1 Extreme. I have a CalDigit TS3 Plus USB-C hub connected to one of the laptop's USB-C/Thunderbolt ports. The laptop supports charging over USB-C. When I try to charge from the hub over USB-C, Ubuntu seems to frequently "drop" the connection to the hub and loses connection to the stuff attached to the hub (e.g., an external monitor connected to the hub by USB-C to displayport, an ethernet connection, and USB devices). After a few seconds, the computer reconnects to these devices. I disabled TLP but the problem persists. When I have the laptop's power adapter attached in addition to the USB-C hub, the problem does not appear and the computer does not lose connection to the peripherals. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: matt 2211 F pulseaudio /dev/snd/controlC1: matt 2211 F pulseaudio /dev/snd/controlC0: matt 2211 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:44:33 2019 InstallationDate: Installed on 2019-09-04 (75 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20MGS1YW00 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=3a5c73f9-5be3-4590-88a9-e362d949931c ro quiet splash resume=UUID=d464672d-224c-4149-a105-3a0cad515692 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-21 (28 days ago) dmi.bios.date: 08/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET42W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MGS1YW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET42W(1.24):bd08/06/2019:svnLENOVO:pn20MGS1YW00:pvrThinkPadX1Extreme:rvnLENOVO:rn20MGS1YW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MGS1YW00 dmi.product.sku: LENOVO_MT_20MG_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1799235] Re: kworker process starts at 85% of cpu and stays there
Daniel, can you please attach output of `grep . /sys/class/dmi/id/*`? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799235 Title: kworker process starts at 85% of cpu and stays there Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu starts, w/ /sbin/init, a kworker process that never stops running below 85%: pb@pb-tower:~/Downloads$ ps -elf F S UIDPID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 S root 1 0 0 80 0 - 56471 - 18:30 ?00:00:01 /sbin/init splash 1 S root 2 0 0 80 0 - 0 - 18:30 ?00:00:00 [kthreadd] 1 R root85 2 63 80 0 - 0 - 18:30 ? 00:03:03 [kworker/0:1+kac] After a few hours, grep . -r /sys/firmware/acpi/interrupts/ shows tens of millions of interrupts. The following command line stops the kworker process: echo "disable" > /sys/firmware/acpi/interrupts/gpe6F On the other hand, I haven't been able to properly shut down my system after this command (power never goes off except manually). I believe the bug is related to the one discussed here: https://superuser.com/questions/1117992/acpi-exception-ae-not-found- while-evaluating-gpe-method-floods-syslog The dmesg w/ this report may be somewhat confusing because there is an unsigned module. But w/ the module removed, dmesg gives the following: [0.097480] ACPI: Dynamic OEM Table Load: [0.097480] ACPI: SSDT 0xA07F57173000 000317 (v02 PmRef ApHwp 3000 INTL 20160527) [0.097480] ACPI: Executed 1 blocks of module-level executable AML code [0.100180] ACPI: Dynamic OEM Table Load: [0.100186] ACPI: SSDT 0xA07F577EF400 00030A (v02 PmRef ApCst 3000 INTL 20160527) [0.100473] ACPI: Executed 1 blocks of module-level executable AML code [0.102187] ACPI: Interpreter enabled [0.10] ACPI: (supports S0 S3 S4 S5) [0.102223] ACPI: Using IOAPIC for interrupt routing [0.102275] HEST: Table parsing has been initialized. [0.102277] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.103580] ACPI: GPE 0x20 active on init [0.104031] ACPI Error: No handler for Region [WST1] ((ptrval)) [GenericSerialBus] (20170831/evregion-166) [0.104035] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20170831/exfldio-299) [0.104040] Initialized Local Variables for Method [PAS1]: [0.104041] Local0: (ptrval)Integer 0001 [0.104045] No Arguments are initialized for method [PAS1] [0.104046] ACPI Error: Method parse/execution failed \_SB.PCI0.I2C0.PAS1, AE_NOT_EXIST (20170831/psparse-550) [0.104052] ACPI Error: Method parse/execution failed \_GPE._L20, AE_NOT_EXIST (20170831/psparse-550) [0.104058] ACPI Exception: AE_NOT_EXIST, while evaluating GPE method [_L20] (20170831/evgpe-646) [0.104005] ACPI: GPE 0x6F active on init [0.104005] ACPI: Enabled 10 GPEs in block 00 to 7F [0.212126] ACPI: Power Resource [USBC] (on) [0.444270] pci :06:00.0: PME# supported from D0 D1 D2 D3hot [0.444270] pci :06:00.1: [1033:00e0] type 00 class 0x0c0320 [0.444270] pci :06:00.1: reg 0x10: [mem 0xa200-0xa2ff] [0.444278] pci :06:00.1: supports D1 D2 [0.444278] pci :06:00.1: PME# supported from D0 D1 D2 D3hot [0.444278] pci :05:00.0: PCI bridge to [bus 06] [0.444278] pci :05:00.0: bridge window [mem 0xa200-0xa20f] [0.456183] ACPI: PCI Interrupt Link [LNKA] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKB] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKC] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKD] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKE] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKF] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKG] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKH] (IRQs) *1 [0.464184] SCSI subsystem initialized [0.464186] libata version 3.00 loaded. [0.464186] pci :00:02.0: vgaarb: setting as boot VGA device [1.225495] Scanning for low memory corruption every 60 seconds [1.226265] Initialise system trusted keyrings [1.226271] Key type blacklist registered [1.226399] workingset: timestamp_bits=36 max_order=23 bucket_order=0 [1.227127] zbud: loaded [1.227482] squashfs: version 4.0 (2009/01/31) Phillip Lougher [1.227769] fuse init (API version 7.26) [1.233972] Key type asymmetric registered [1.233973] Asymmetric key parser 'x509' registered [1.233991] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 246) [1.234105] io
[Kernel-packages] [Bug 1853197] Re: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection
commit 86c6739eda7d2a03f2db30cbee67a5fb81afa8ba
Author: Steffen Klassert
Date: Wed Nov 6 08:13:49 2019 +0100
xfrm: Fix memleak on xfrm state destroy
We leak the page that we use to create skb page fragments
when destroying the xfrm_state. Fix this by dropping a
page reference if a page was assigned to the xfrm_state.
Fixes: cac2661c53f3 ("esp4: Avoid skb_cow_data whenever possible")
Reported-by: JD
Reported-by: Paul Wouters
Signed-off-by: Steffen Klassert
This commit will be automatically picked by later kernel update since it
has "Fixes" tag.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853197
Title:
Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection
Status in linux package in Ubuntu:
Confirmed
Bug description:
Ubuntu linux distro, 4.15.0-62 kernel, server platform.
This OS is used as an IPSec VPN gateway. It serves up to several hundred
concurrent connections
In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed
that VPN gateway VMs were running out of physical memory after 12-48
hours, depending on load.
Attachments from a server machine in this state in attached leakinfo.txt
output of free -t
output of /proc/meminfo in out of memory condition
output of /slabtop -o -sc
/sys/kernel/debug/page_owner sorted and aggregated after server ran for 12
hrs and ran out of memory
Patches for 4.15 and 5.4
Highlight from page_owner, we can see the leak is a buffer associated
with the ipsec impelementation. Each connection leaks 32k of memory
via alloc_page with order=3
100960 times:
Page allocated via order 3, mask
0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP)
get_page_from_freelist+0xd64/0x1250
__alloc_pages_nodemask+0x11c/0x2e0
alloc_pages_current+0x6a/0xe0
skb_page_frag_refill+0x71/0x100
esp_output_head+0x265/0x3e0 [esp4]
esp_output+0xbc/0x180 [esp4]
xfrm_output_resume+0x179/0x530
xfrm_output+0x8e/0x230
xfrm4_output_finish+0x2b/0x30
__xfrm4_output+0x3a/0x50
xfrm4_output+0x43/0xc0
ip_forward_finish+0x51/0x80
ip_forward+0x38a/0x480
ip_rcv_finish+0x122/0x410
ip_rcv+0x292/0x360
__netif_receive_skb_core+0x815/0xbd0
Patch to fix this issue in 4.15 (tested and verified on same server
exhibiting above leak):
diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
index 728272f..7842f83 100644
--- a/net/xfrm/xfrm_state.c
+++ b/net/xfrm/xfrm_state.c
@@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x)
}
xfrm_dev_state_free(x);
security_xfrm_state_free(x);
+
+ if(x->xfrag.page)
+ put_page(x->xfrag.page);
+
kfree(x);
}
Patch for master branch (5.4 I believe) from Paul Wouters
(p...@nohats.ca)
diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c
index c6f3c4a1bd99..f3423562d933 100644
--- a/net/xfrm/xfrm_state.c
+++ b/net/xfrm/xfrm_state.c
@@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x)
x->type->destructor(x);
xfrm_put_type(x->type);
}
+ if (x->xfrag.page)
+ put_page(x->xfrag.page);
xfrm_dev_state_free(x);
security_xfrm_state_free(x);
xfrm_state_free(x);
Severity: Critical - we are unable to use any kernel later than 4.11,
and are sticking with 4.4 in production.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853197/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853075] Re: 19.10 Boots into a black screen
Please test latest mainline kernel: https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc8/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853075 Title: 19.10 Boots into a black screen Status in linux package in Ubuntu: Invalid Bug description: After upgrading to 19.10 and rebooting. My machine goes into a frozen black screen. The default kernel after the update (5.3.0-23-generic) does not succeed in booting. If I select the older kernel, 5.0.0-36-generic, grub does go through and succeeds booting up. System is a Dell XPS 15 9550 with Ubuntu Dual Boot. GRUB version 2.04-1ubuntu12. The Windows partition does work properly, and I am able to boot into it. Please advice on how to proceed with a fix, or if an update pushed to grub will fix this issue. Thanks. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pipemon2417 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c26ef9c3-b999-4441-b750-cf80d00fc68e InstallationDate: Installed on 2017-11-02 (746 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic root=UUID=6b1a4315-6bdf-471f-90b5-6fb32c3bfc2b ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-36-generic N/A linux-backports-modules-5.0.0-36-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.0.0-36-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-18 (0 days ago) UserGroups: adm audio cdrom dialout dip kvm lpadmin plugdev pulse sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd07/30/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-security Status: New => Invalid ** Changed in: kernel-sru-workflow/security-signoff Status: New => Invalid ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Ready for Packaging - phase-changed: Tuesday, 19. November 2019 17:05 UTC + phase: Packaging + phase-changed: Wednesday, 20. November 2019 04:25 UTC reason: - prepare-package: Pending -- version not specified + prepare-package: Pending -- package not yet uploaded + prepare-package-meta: Pending -- package not yet uploaded + prepare-package-signed: Pending -- package not yet uploaded 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/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 20. November 2019 04:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852281] Re: trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker
** Summary changed: - trusty/linux-azure: -proposed tracker + trusty/linux-azure: 4.15.0-1064.69~14.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-meta Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) ** Changed in: kernel-sru-workflow/prepare-package-signed Status: New => In Progress ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: Canonical Kernel Team (canonical-kernel-team) => Khaled El Mously (kmously) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1852281 Title: trusty/linux-azure: 4.15.0-1064.69~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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Packaging phase-changed: Wednesday, 20. November 2019 04:25 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded prepare-package-signed: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820967] Re: MAAS failing to commission HP ProLiant DL385 G7 (AMD Opteron 6172)
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820967 Title: MAAS failing to commission HP ProLiant DL385 G7 (AMD Opteron 6172) Status in MAAS: Invalid Status in linux package in Ubuntu: Expired Bug description: Hello, We have some HP ProLiant DL385 G7 (AMD Opteron 6172) servers which MAAS is failing to commission. We have also tried other servers on the same MAAS deployment that work with any issue. We try to commission a "New" machine, it boots from PXE and we get the following messages: [ 90.598545] x86/PAT: impi-locate:2905 map pfn expected mapping type uncached-minus for [mem 0xbde1c000-0xbde1cfff], got write-back [ 90.599073] x86/PAT: impi-locate:2905 map pfn expected mapping type uncached-minus for [mem 0xbde1d000-0xbde1dfff], got write-back [ 90.599278] x86/PAT: impi-locate:2905 map pfn expected mapping type uncached-minus for [mem 0xbde1c000-0xbde1cfff], got write-back [ 90.599814] x86/PAT: impi-locate:2905 map pfn expected mapping type uncached-minus for [mem 0xbde1d000-0xbde1dfff], got write-back Starting STop ureadahead data collection... Stopping Read required files in advance... [ OK ] Started Stop ureadahead data collection. [ 150.880073] INFO: rcu_sched detected stalls on CPUs/tasks: [ 150.880197] 0-...!: (0 ticks this GP) idle=ee4/0/0 softirq=2489/2489 fqs=0 [ 150.880303] 12-...!: (0 ticks this GP) idle=0d8/0/0 softirq=2429/2429 fqs=0 [ 150.880408] 21-...!: (51 GPs behind) idle=f10/0/0 softirq=1692/1694 fqs=0 [ 150.880510] 23-...!: (19 GPs behind) idle=28c/0/0 softirq=1761/1761 fqs=0 [ 150.880610] (detected by 2, t=15002 jiffies, g=2532, c=2531, q=2143) [ 150.884754] rcu_sched kthread starved for 15003 jiffies! g2532 c2531 f0x0 RCU_GP_WAIT_FQS(3) ->state=0x402 ->cpu=0 [ OK ] Stopped Read required files in advance. [ OK ] Stopped Flush Journal to Persistent Storage. Stopping Flush Journal to Persistent Storage... [ OK ] Stopped Journal Service. Starting Journal Service [ OK ] Started Journal Service. Starting Flush Journal to Persistent Storage... [ OK ] Started Flush Journal to Persistent Storage. [ 363.217837] INFO: task kworker/7:1:185 blocked for more than 120 seconds. [ 363.217950]Not tainted 4.15.0-46-generic #49-Ubuntu [ 363.218046] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 363.218375] INFO: task ipmi-config:2937 blocked for more than 120 seconds. [ 363.218476]Not tainted 4.15.0-46-generic #49-Ubuntu [ 363.218571] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 484.217837] INFO: task kworker/7:1:185 blocked for more than 120 seconds. [ 484.217950]Not tainted 4.15.0-46-generic #49-Ubuntu [ 484.218046] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 484.218375] INFO: task ipmi-config:2937 blocked for more than 120 seconds. [ 484.218476]Not tainted 4.15.0-46-generic #49-Ubuntu [ 484.218571] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. These 2 INFO messages continue to show until commissioning fails at 30min timeout. In approximately 1 out of 10 tries the server will be commissioned successfully but then the same behavior will occur in the deployment process. One thing I tried was in Settings -> General -> Global Kernel Parameters, I placed the "nosmp" boot parameter which makes Commissioning succeed every time but the Machine then has only 1 CPU. Thank you in advance, Yanos To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1820967/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1743595] Re: modprobing mlx5_core doesn't bring the interface up
[Expired for linux (Ubuntu) because there has been no activity for 60 days.] ** Changed in: linux (Ubuntu) Status: Incomplete => Expired -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1743595 Title: modprobing mlx5_core doesn't bring the interface up Status in MAAS: Invalid Status in linux package in Ubuntu: Expired Bug description: ubuntu@wrlsrvr321:~$ sudo -i root@wrlsrvr321:~# lsmod Module Size Used by ipmi_devintf 20480 0 iscsi_tcp 20480 0 libiscsi_tcp 24576 1 iscsi_tcp libiscsi 53248 2 libiscsi_tcp,iscsi_tcp scsi_transport_iscsi98304 3 iscsi_tcp,libiscsi overlay49152 1 btrfs 991232 0 raid10 49152 0 raid456 110592 0 async_raid6_recov 20480 1 raid456 async_memcpy 16384 2 raid456,async_raid6_recov async_pq 16384 2 raid456,async_raid6_recov async_xor 16384 3 async_pq,raid456,async_raid6_recov async_tx 16384 5 async_pq,raid456,async_xor,async_memcpy,async_raid6_recov xor24576 2 btrfs,async_xor raid6_pq 102400 4 async_pq,raid456,btrfs,async_raid6_recov libcrc32c 16384 1 raid456 raid1 36864 0 raid0 20480 0 multipath 16384 0 linear 16384 0 ipmi_ssif 24576 0 ses20480 0 enclosure 16384 1 ses scsi_transport_sas 45056 1 ses hid_generic16384 0 mxm_wmi16384 0 crct10dif_pclmul 16384 0 crc32_pclmul 16384 0 ghash_clmulni_intel16384 0 aesni_intel 167936 0 aes_x86_64 20480 1 aesni_intel lrw16384 1 aesni_intel gf128mul 16384 1 lrw glue_helper16384 1 aesni_intel ablk_helper16384 1 aesni_intel cryptd 20480 3 ghash_clmulni_intel,aesni_intel,ablk_helper i2c_algo_bit 16384 0 ttm98304 0 drm_kms_helper155648 0 ixgbe 290816 0 syscopyarea16384 1 drm_kms_helper sysfillrect16384 1 drm_kms_helper dca16384 1 ixgbe sysimgblt 16384 1 drm_kms_helper vxlan 49152 1 ixgbe fb_sys_fops16384 1 drm_kms_helper ip6_udp_tunnel 16384 1 vxlan drm 364544 2 ttm,drm_kms_helper udp_tunnel 16384 1 vxlan usbhid 49152 0 ptp20480 1 ixgbe ahci 36864 0 hid 118784 2 hid_generic,usbhid libahci32768 1 ahci pps_core 20480 1 ptp megaraid_sas 135168 0 mdio 16384 1 ixgbe ipmi_si57344 0 fjes 28672 0 ipmi_msghandler49152 3 ipmi_ssif,ipmi_devintf,ipmi_si wmi20480 1 mxm_wmi root@wrlsrvr321:~# root@wrlsrvr321:~# lspci | grep Mell 81:00.0 Ethernet controller: Mellanox Technologies MT28800 Family [ConnectX-5] root@wrlsrvr321:~# root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:130767 errors:0 dropped:30 overruns:0 frame:0 TX packets:20809 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:196717409 (196.7 MB) TX bytes:1575915 (1.5 MB) enp3s0f1 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:81 BROADCAST MULTICAST MTU:1500 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) loLink encap:Local Loopback inet addr:127.0.0.1 Mask:255.0.0.0 inet6 addr: ::1/128 Scope:Host UP LOOPBACK RUNNING MTU:65536 Metric:1 RX packets:0 errors:0 dropped:0 overruns:0 frame:0 TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1 RX bytes:0 (0.0 B) TX bytes:0 (0.0 B) root@wrlsrvr321:~# modprobe mlx5_core root@wrlsrvr321:~# ifconfig -a enp3s0f0 Link encap:Ethernet HWaddr 0c:c4:7a:df:23:80 inet addr:12.12.1.143 Bcast:12.12.1.255 Mask:255.255.255.0 inet6 addr: fe80::ec4:7aff:fedf:2380/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
[Kernel-packages] [Bug 1853192] Re: Please add patch fixing RK818 ID detection
** Changed in: linux (Ubuntu) Assignee: (unassigned) => Po-Hsu Lin (cypressyew) ** Changed in: linux (Ubuntu) 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/1853192 Title: Please add patch fixing RK818 ID detection Status in linux package in Ubuntu: In Progress Bug description: Hi, Please add this upstream patch to ubuntu kernel: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=37ef8c2c15bdc1322b160e38986c187de2b877b2 It fixes detection of RK818 pmic. Without it ubuntu hangs at boot. Cheers Paweł Jarosz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846539] Re: [broadwell-rt286, playback] Since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140
** Description changed: + [Impact] + With the current default kernel config, the SND_SOC_SOF_BROADWELL_SUPPORT + is set to Y, then it will make the legacy intel soc driver fail, and + moreover the current sof driver can't support broadwell well, as a + result, many broadwell computers with I2S codec can't support sound anymore. + + [Fix] + Intel submitted a patch, it will make those two kconfig options exclusive, + and the legacy soc's option has higher priority, if both of them are + enabled, sof's option will be disabled. + + [Test Case] + Build the kernel and check the debian/build/$buidling_dir/.config, the + SND_SOC_SOF_BROADWELL_SUPPORT is disabled. + + [Regression Risk] + Low, so far, the sof driver can't support broadwell machine well, so + there is no machine use this driver yet. + + Hello! I noticed that since Linux 5.2rc2 audio playback no longer works on Dell Venue 11 Pro 7140 (Intel Core M-5Y71; rt286). Turns out that happened because SND_SOC_SOF_BROADWELL_SUPPORT was enabled in kernel binary builds since 5.2rc2: https://kernel.ubuntu.com/~kernel- ppa/mainline/v5.2-rc2/ To verify this assumption I tested two builds of Linux 5.3.1. 1. Build with enabled SND_SOC_SOF_BROADWELL_SUPPORT from https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.3.1/ Audio playback doesn't work, dmesg: [4.072800] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.212606] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.238009] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.294920] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.407351] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.428922] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.458926] broadwell-audio broadwell-audio: ASoC: failed to init link System PCM: -517 [4.472113] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.472118] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.472735] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.474607] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.474676] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.474741] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.474807] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.476377] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.480344] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 [7.892659] haswell-pcm-audio haswell-pcm-audio: error: message type 7 header 0x8700 [ 13.015379] haswell-pcm-audio haswell-pcm-audio: error: reset stream 2 still running [ 13.127262] haswell-pcm-audio haswell-pcm-audio: error: reset stream 0 still running [ 19.623436] haswell-pcm-audio haswell-pcm-audio: ipc: --message timeout-- ipcx 0x8612 isr 0x ipcd 0x4700 imrx 0x7fff [ 19.623446] haswell-pcm-audio haswell-pcm-audio: ipc: error set dx state 3 faile 2. Build with disabled SND_SOC_SOF_BROADWELL_SUPPORT. Audio playback works, dmesg: [4.839028] haswell-pcm-audio haswell-pcm-audio: Direct firmware load for intel/IntcPP01.bin failed with error -2 [4.839034] haswell-pcm-audio haswell-pcm-audio: fw image intel/IntcPP01.bin not available(-2) [4.839644] haswell-pcm-audio haswell-pcm-audio: FW loaded, mailbox readback FW info: type 01, - version: 00.00, build 77, source commit id: 876ac6906f31a43b6772b23c7c983ce9dcb18a19 [4.851204] snd_hda_intel :00:03.0: bound :00:02.0 (ops i915_audio_component_bind_ops [i915]) [4.907386] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> System Pin mapping ok [4.907475] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload0 Pin mapping ok [4.909831] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Offload1 Pin mapping ok [4.909931] broadwell-audio broadwell-audio: snd-soc-dummy-dai <-> Loopback Pin mapping ok [4.912149] broadwell-audio broadwell-audio: rt286-aif1 <-> snd-soc-dummy-dai mapping ok [4.929629] input: broadwell-rt286 Headset as /devices/pci:00/INT3438:00/broadwell-audio/sound/card1/input14 ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 Uname: Linux 5.3.0-13-generic x86_64 ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64
[Kernel-packages] [Bug 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Promote to Proposed - phase-changed: Wednesday, 20. November 2019 00:51 UTC + phase: Testing + phase-changed: Wednesday, 20. November 2019 02:31 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 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/1852300 Title: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed 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: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress 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: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Testing phase-changed: Wednesday, 20. November 2019 02:31 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853219] 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 1853219 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: focal -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853219 Title: [CML-H] Add intel_thermal_pch driver support Comet Lake -H Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description Add intel_thermal_pch driver support Comet Lake -H Target Release: 20.04 Target Kernel: 5.5 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1853219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853219] [NEW] [CML-H] Add intel_thermal_pch driver support Comet Lake -H
Public bug reported: Description Add intel_thermal_pch driver support Comet Lake -H Target Release: 20.04 Target Kernel: 5.5 ** Affects: intel Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: focal intel-kernel-20.04 ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853219 Title: [CML-H] Add intel_thermal_pch driver support Comet Lake -H Status in intel: New Status in linux package in Ubuntu: Incomplete Bug description: Description Add intel_thermal_pch driver support Comet Lake -H Target Release: 20.04 Target Kernel: 5.5 To manage notifications about this bug go to: https://bugs.launchpad.net/intel/+bug/1853219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853075] Re: 19.10 Boots into a black screen
That didn't 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/1853075 Title: 19.10 Boots into a black screen Status in linux package in Ubuntu: Invalid Bug description: After upgrading to 19.10 and rebooting. My machine goes into a frozen black screen. The default kernel after the update (5.3.0-23-generic) does not succeed in booting. If I select the older kernel, 5.0.0-36-generic, grub does go through and succeeds booting up. System is a Dell XPS 15 9550 with Ubuntu Dual Boot. GRUB version 2.04-1ubuntu12. The Windows partition does work properly, and I am able to boot into it. Please advice on how to proceed with a fix, or if an update pushed to grub will fix this issue. Thanks. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: pipemon2417 F pulseaudio CurrentDesktop: KDE DistroRelease: Ubuntu 19.10 HibernationDevice: RESUME=UUID=c26ef9c3-b999-4441-b750-cf80d00fc68e InstallationDate: Installed on 2017-11-02 (746 days ago) InstallationMedia: Ubuntu 16.04.3 LTS "Xenial Xerus" - Release amd64 (20170801) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 04f3:21d5 Elan Microelectronics Corp. Touchscreen Bus 001 Device 002: ID 0cf3:e301 Qualcomm Atheros Communications Bus 001 Device 004: ID 1bcf:2b95 Sunplus Innovation Technology Inc. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 15 9550 NonfreeKernelModules: nvidia_modeset nvidia Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.0.0-36-generic root=UUID=6b1a4315-6bdf-471f-90b5-6fb32c3bfc2b ro quiet splash ProcVersionSignature: Ubuntu 5.0.0-36.39-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-36-generic N/A linux-backports-modules-5.0.0-36-generic N/A linux-firmware1.183.2 Tags: eoan Uname: Linux 5.0.0-36-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-11-18 (0 days ago) UserGroups: adm audio cdrom dialout dip kvm lpadmin plugdev pulse sambashare sudo video _MarkForUpload: True dmi.bios.date: 07/30/2019 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.11.2 dmi.board.name: 0N7TVV dmi.board.vendor: Dell Inc. dmi.board.version: A01 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.11.2:bd07/30/2019:svnDellInc.:pnXPS159550:pvr:rvnDellInc.:rn0N7TVV:rvrA01:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 15 9550 dmi.product.sku: 06E4 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853075/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852275] Re: xenial/linux-oracle: 4.15.0-1030.33~16.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: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 23:47 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait + promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852275 Title: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 23:47 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -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: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Wednesday, 20. November 2019 00:51 UTC reason: - promote-to-proposed: Pending -- package copies requested to Proposed main:missing,meta:missing + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 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/1852300 Title: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-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: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Wednesday, 20. November 2019 00:51 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -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: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 - phase: Ready for Promote to Proposed - phase-changed: Monday, 18. November 2019 04:51 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 20. November 2019 00:51 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Pending -- package copies requested to Proposed main:missing,meta:missing trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 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/1852300 Title: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-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: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Wednesday, 20. November 2019 00:51 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852300] Re: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve Langasek (vorlon) -- 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/1852300 Title: xenial/linux-raspi2: 4.4.0-1126.135 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-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: 1852306 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Promote to Proposed phase-changed: Wednesday, 20. November 2019 00:51 UTC reason: promote-to-proposed: Pending -- package copies requested to Proposed main:missing,meta:missing trackers: xenial/linux-raspi2/pi2-kernel: bug 1852299 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852300/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848481] Re: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud
** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => gerald.yang (gerald-yang-tw) ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848481 Title: cloudimg: no iavf/i40evf module so no network available with SR-IOV enabled cloud Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: Fix Committed Status in livecd-rootfs source package in Bionic: Invalid Status in linux source package in Disco: Fix Committed Status in livecd-rootfs source package in Disco: Invalid Status in linux source package in Eoan: Fix Committed Status in livecd-rootfs source package in Eoan: Invalid Status in linux source package in Focal: Fix Committed Status in livecd-rootfs source package in Focal: Invalid Bug description: === SRU Justification === [Impact] Intel's VF drivers such as igbvf and ixgbevf are already available in generic. It makes sense to add i40evf especially for SR-IOV enabled clouds with Intel X710/XXV710/XL710. [Fix] Add i40evf to linux-modules package [Test] Extract linux-modules to check if i40evf is there [Regression Potential] Low = original bug description = For example with bionic, i40evf module is in linux-modules-extra-4.15*-generic. However, cloudimg doesn't have linux-modules-extra seeded: $ curl -s http://cloud-images.ubuntu.com/releases/bionic/release/ubuntu-18.04-server-cloudimg-amd64.manifest | grep linux- linux-base 4.5ubuntu1 linux-headers-4.15.0-65 4.15.0-65.74 linux-headers-4.15.0-65-generic 4.15.0-65.74 linux-headers-generic 4.15.0.65.67 linux-headers-virtual 4.15.0.65.67 linux-image-4.15.0-65-generic 4.15.0-65.74 linux-image-virtual 4.15.0.65.67 linux-modules-4.15.0-65-generic 4.15.0-65.74 linux-virtual 4.15.0.65.67 We don't need the whole linux-modules-extra because the size is not small, but we need some VF drivers in cloud guest image embedded for SR-IOV enabled cloud including OpenStack. Otherwise, the guest is unusable with no network device. $ apt show linux-modules-extra-4.15.0-58-generic |& grep Installed-Size Installed-Size: 171 MB $ du -h /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko 148K /lib/modules/4.15.0-58-generic/kernel/drivers/net/ethernet/intel/i40evf/i40evf.ko ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: livecd-rootfs (not installed) ProcVersionSignature: User Name 4.15.0-58.64-generic 4.15.18 Uname: Linux 4.15.0-58-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 Date: Thu Oct 17 10:48:41 2019 ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=C.UTF-8 SHELL=/bin/bash SourcePackage: livecd-rootfs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848481/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1813018] Re: Kernel Oops - unable to handle kernel paging request; RIP is at wait_migrate_huge_page+0x51/0x70
This bug has been fixed on Ubuntu 14.04 ESM,
linux kernel package version 3.13.0-175.226.
Marking the LP bug as Fix Released / Trusty.
** Changed in: linux (Ubuntu Trusty)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1813018
Title:
Kernel Oops - unable to handle kernel paging request; RIP is at
wait_migrate_huge_page+0x51/0x70
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Trusty:
Fix Released
Bug description:
[Impact]
* Users on NUMA systems (mostly servers) with
NUMA balancing enabled (which is by default)
might hit a crash/BUG() on a race condition
if two simultaneous page faults of the same
transparent hugepage go into the path for
migration to another NUMA node.
* The symptom is BUG() for 0xeac0,
which happens if the PMD is set to zero/NULL.
BUG: unable to handle kernel paging request at eac0
IP: [] wait_migrate_huge_page+0x51/0x70
* NUMA balancing periodically unmaps pages so to
force page faults to occur, and later find out
using page faults where the NUMA memory access
is coming from - if it's often from other NUMA
node, it attempts to migrate the page contents
to the other NUMA node (for more local access.)
* The race condition is related to these 3 functions
in the pagefault handling of transparent hugepages:
do_huge_pmd_numa_page() -> migrate_misplaced_transhuge_page()
do_huge_pmd_numa_page() -> wait_migrate_huge_page()
The first task to hit the pagefault / migration path
calls migrate_misplaced_transhuge_page(), which does:
- ptl = pmd_lock(mm, pmd) // calls spin_lock(ptl)
- pmdp_clear_flush(..., pmd); // set PMD to zero
- set_pmd_at(..., pmd, ...); // set PMD to non-zero
- spin_unlock(ptl);
The second task to hit that path finds that the page
is already being migrated (page is locked) and waits
for that finish (ie, until page is unlocked), doing:
- spin_unlock(ptl)
- page = pmd_page(*pmd)
- wait_on_page_locked(page)
*BUT* it reads the PMD value *after* unlocking stuff.
So, if the tasks/CPUs manage to run in the sequence
below the PMD can be set to zero/NULL by first task
and read by second task before it's set to non-NULL.
Thus the second task miscalculates the page pointer,
from PMD and hit BUG for address 0xeac0.
https://pastebin.ubuntu.com/p/pjMNxkJfJy/
* The fix just moves pmd_page() before spin_unlock(),
and now the change perfomed in the other function
(done within the spin_lock()/spin_unlock() region)
can no longer run concurrently with this PMD read.
* So, when the other function releases the spin lock,
the PMD has already been set to non-NULL/valid PMD,
and wait_on_page_locked() receives a valid address.
* Fix commit 5d833062139d ("mm: numa: do not dereference
pmd outside of the lock during NUMA hinting fault") [1]
* Applied in v4.0 upstream; only Trusty/3.13 needs it.
$ git describe --contains 5d833062139d
v4.0-rc1~98^2~103
[Test Case]
* A synthetic reproducer is available for this bug.
It consists of two parts:
1) userspace program to allocate one transparent
huge page and spawn two threads that write to
it periodically - based on the period used by
numa balancing to unmap pages - so it trigger
page faults simultaneously on the two threads.
2) kernel module that inserts kprobes on several
points in the involved functions, in order to
synchronize the two threads's timing/progress
in the way that reproduces the problem.
Then the user forces the NUMA migration to occur
by changing the affinity of userspace program to
another NUMA node, and the kernel module/kprobes
force the problem to occur.
* Steps done with kprobes:
1) Task 1 and Task 2 join at do_huge_pmd_numa_page().
2) Task 1 moves on to migrate_misplaced_transhuge_page(),
signals Task 2 to move on, and waits for Task 2 signal.
3) Task 2 moves on to point in 'if pmd_trans_migrating()'
just after spin_unlock() [before pmd_page() originally],
signals Task 1 to move on, and waits for Task 1 signal.
4) Task 1 moves on until it sets the PMD to zero/NULL,
signals Task 2 to move on, and waits for Task 2 signal.
5) Task 2 moves on to read the PMD and calculate its page,
and attempt to wait on it to be unlocked.
5.1) BUG() on the original kernel / without the patch.
5.2) Go-on on the modified kernel / with the patch.
[Regression Potential]
* Low. The fix is both really targeted at this particular
problem/race condition (see last
[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash
The attachment "0001-dmidecode-Only-scan-dev-mem-for-entry-point-
on-x86.patch" seems to be a patch. If it isn't, please remove the
"patch" flag from the attachment, remove the "patch" tag, and if you are
a member of the ~ubuntu-reviewers, unsubscribe the team.
[This is an automated message performed by a Launchpad user owned by
~brian-murray, for any issues please contact him.]
** Tags added: patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
Status in dmidecode package in Ubuntu:
Confirmed
Bug description:
Please let me know what other information I can provide. Some basic
info I've captured below.
root@jetson-0423318029481:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@jetson-0423318029481:~# uname -a
Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
root@jetson-0423318029481:~# apt-cache madison dmidecode
dmidecode | 3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main
arm64 Packages
root@jetson-0423318029481:~# dmidecode -V
3.1
root@jetson-0423318029481:~# strace dmidecode
execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
brk(NULL) = 0x559651a000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
close(3)= 0
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0
\10\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f8050a000
mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f80369000
mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
close(3)= 0
mprotect(0x7f804b8000, 16384, PROT_READ) = 0
mprotect(0x55932d9000, 12288, PROT_READ) = 0
mprotect(0x7f8050e000, 4096, PROT_READ) = 0
munmap(0x7f804c2000, 130516)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
brk(NULL) = 0x559651a000
brk(0x559653b000) = 0x559653b000
write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
) = 16
openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or
directory)
write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry
point.
) = 35
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3,
# System hangs and reboots here.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dmidecode 3.1-1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 12:15:53 2019
Dependencies:
gcc-8-base 8.2.0-1ubuntu2~18.04
libc6 2.27-3ubuntu1
libgcc1 1:8.2.0-1ubuntu2~18.04
InstallationDate: Installed on 2019-02-28 (24 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dmidecode
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1850572] Re: AMD Prairie Falcon platform failed to boot up
** Tags removed: verification-needed-bionic ** Tags added: verification-done-bionic -- 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/1850572 Title: AMD Prairie Falcon platform failed to boot up Status in HWE Next: New Status in linux package in Ubuntu: Invalid Status in linux-oem package in Ubuntu: Invalid Status in linux source package in Bionic: Fix Committed Status in linux-oem source package in Bionic: Fix Released Bug description: [Impact] AMD Prairie Falcon is the AME Embedded variant of Stoney. It fails to boot up without disable its CGCG feature. Set 'amdgpu.cg_mask=0xfffb' kernel parameter to disable CGCG [Fix] Suggestion from AMD that we have to cherry pick this commit which is included in v4.16 fb4bbba27753 drm/amdgpu: re-enable CGCG on CZ and disable on ST [Test] Verified on AMD Prairie Falcon platform, system boots up normally. [Regression Potential] Low, this commit has been included for more than one and a half year in the upstream, should be pretty safe to include it. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1850572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852275] Re: xenial/linux-oracle: 4.15.0-1030.33~16.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: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Promote to Proposed - phase-changed: Saturday, 16. November 2019 06:34 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 19. November 2019 23:47 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852275 Title: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 23:47 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852275] Re: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: Confirmed => Fix Committed ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: Ubuntu Stable Release Updates Team (ubuntu-sru) => Steve Langasek (vorlon) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852275 Title: xenial/linux-oracle: 4.15.0-1030.33~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-oracle package in Ubuntu: Invalid Status in linux-oracle 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: 1852277 packages: main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 23:47 UTC reason: promote-to-proposed: Ongoing -- package copied to Proposed signed:depwait variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852275/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1651910] Re: radeon: black screen after upgrade from 14.04 to 16.04 on RS780
Launchpad has imported 6 comments from the remote bug at https://bugs.freedesktop.org/show_bug.cgi?id=99181. If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. On 2016-12-22T11:25:28+00:00 Chi-Thanh Christopher Nguyen wrote: Hardware: BIOSTAR A780L When booting with 3.15 or newer kernels, a monitor connected to the DVI port of the BIOSTAR A780L will stay blank. Kernel 3.14 and older work fine. I tried forcing the output to on with video=HDMI-A-1:e but this made no difference. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/comments/23 On 2016-12-22T11:26:57+00:00 Chi-Thanh Christopher Nguyen wrote: Created attachment 128629 dmesg from kernel 3.14 with drm.debug=15 (working) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/comments/24 On 2016-12-22T11:27:30+00:00 Chi-Thanh Christopher Nguyen wrote: Created attachment 128630 dmesg from kernel 4.9 with drm.debug=15 (not working) Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/comments/25 On 2016-12-22T19:11:02+00:00 Chi-Thanh Christopher Nguyen wrote: https://bugzilla.kernel.org/show_bug.cgi?id=91861 seems to be related, however this issue still happens with kernel 4.9 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/comments/26 On 2016-12-25T17:00:23+00:00 Christopher M. Penalver wrote: Commit bisect requested in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/comments/25 . Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/comments/30 On 2019-11-19T09:21:00+00:00 Martin-peres-n wrote: -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/766. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1651910/comments/31 ** Changed in: linux Importance: Unknown => Medium ** Bug watch added: Linux Kernel Bug Tracker #91861 https://bugzilla.kernel.org/show_bug.cgi?id=91861 ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #766 https://gitlab.freedesktop.org/drm/amd/issues/766 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1651910 Title: radeon: black screen after upgrade from 14.04 to 16.04 on RS780 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: After upgrading from Ubuntu 14.04 to 16.04, the screen will stay black after GRUB (backlight is on) when booting with the new 4.4 kernel (linux-image-4.4.0-57-generic). Monitor connected via DVI. WORKAROUND: Boot with the old 3.14 kernel. --- ApportVersion: 2.20.1-0ubuntu2.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D2c', '/dev/snd/pcmC0D1p', '/dev/snd/pcmC0D0c', '/dev/snd/pcmC0D0p', '/dev/snd/controlC0', '/dev/snd/hwC1D0', '/dev/snd/pcmC1D3p', '/dev/snd/controlC1', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: DistroRelease: Ubuntu 16.04 HibernationDevice: RESUME=UUID=dbcee44e-5c4b-4630-a837-f819f42e91eb IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: BIOSTAR Group A780L Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.8.0-32-generic root=UUID=da4d032c-4aef-42d0-bcf6-1cf98904be02 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.8.0-32.34~16.04.1-generic 4.8.11 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.8.0-32-generic N/A linux-backports-modules-4.8.0-32-generic N/A linux-firmware1.157.6 RfKill: Tags: xenial Uname: Linux 4.8.0-32-generic x86_64 UpgradeStatus: Upgraded to xenial on 2016-09-24 (89 days ago) UserGroups: adm admin cdrom dialout lpadmin nopasswdlogin plugdev sambashare _MarkForUpload: True dmi.bios.date: 07/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080014 dmi.board.asset.tag: To
[Kernel-packages] [Bug 1853208] [NEW] Bionic update: upstream stable patchset 2019-11-19
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-11-19 Ported from the following upstream stable releases: v4.14.153, v4.19.83 from git://git.kernel.org/ arm64: dts: Fix gpio to pinmux mapping regulator: ti-abb: Fix timeout in ti_abb_wait_txdone/ti_abb_clear_all_txdone regulator: pfuze100-regulator: Variable "val" in pfuze100_regulator_probe() could be uninitialized ASoC: wm_adsp: Don't generate kcontrols without READ flags ASoc: rockchip: i2s: Fix RPM imbalance ARM: dts: logicpd-torpedo-som: Remove twl_keypad pinctrl: ns2: Fix off by one bugs in ns2_pinmux_enable() ARM: mm: fix alignment handler faults under memory pressure scsi: scsi_dh_alua: handle RTPG sense code correctly during state transitions scsi: sni_53c710: fix compilation error scsi: fix kconfig dependency warning related to 53C700_LE_ON_BE ARM: dts: imx7s: Correct GPT's ipg clock source perf c2c: Fix memory leak in build_cl_output() perf kmem: Fix memory leak in compact_gfp_flags() ARM: davinci: dm365: Fix McBSP dma_slave_map entry scsi: target: core: Do not overwrite CDB byte 1 ARM: 8926/1: v7m: remove register save to stack before svc of: unittest: fix memory leak in unittest_data_add MIPS: bmips: mark exception vectors as char arrays i2c: stm32f7: remove warning when compiling with W=1 cifs: Fix cifsInodeInfo lock_sem deadlock when reconnect occurs nbd: handle racing with error'ed out commands cxgb4: fix panic when attaching to ULD fail dccp: do not leak jiffies on the wire net: annotate accesses to sk->sk_incoming_cpu net: annotate lockless accesses to sk->sk_napi_id net: dsa: bcm_sf2: Fix IMP setup for port different than 8 net: ethernet: ftgmac100: Fix DMA coherency issue with SW checksum net: fix sk_page_frag() recursion from memory reclaim net: hisilicon: Fix ping latency when deal with high throughput net/mlx4_core: Dynamically set guaranteed amount of counters per VF selftests: net: reuseport_dualstack: fix uninitalized parameter udp: fix data-race in udp_set_dev_scratch() net: add READ_ONCE() annotation in __skb_wait_for_more_packets() net/mlx5e: Fix handling of compressed CQEs in case of low NAPI budget net: dsa: b53: Do not clear existing mirrored port mask net: usb: lan78xx: Connect PHY before registering MAC r8152: add device id for Lenovo ThinkPad USB-C Dock Gen 2 net: dsa: fix switch tree list net: bcmgenet: reset 40nm EPHY on energy detect net: add skb_queue_empty_lockless() udp: use skb_queue_empty_lockless() net: use skb_queue_empty_lockless() in poll() handlers net: use skb_queue_empty_lockless() in busy poll contexts vxlan: check tun_info options_len properly erspan: fix the tun_info options_len check for erspan inet: stop leaking jiffies on the wire net/flow_dissector: switch to siphash kbuild: use -fmacro-prefix-map to make __FILE__ a relative path kbuild: add -fcf-protection=none when using retpoline flags platform/x86: pmc_atom: Add Siemens SIMATIC IPC227E to critclk_systems DMI table iio: adc: stm32-adc: move registers definitions powerpc/book3s64/mm: Don't do tlbie fixup for some hardware revisions powerpc/book3s64/radix: Rename CPU_FTR_P9_TLBIE_BUG feature flag selftests/powerpc: Add test case for tlbie vs mtpidr ordering issue selftests/powerpc: Fix compile error on tlbie_test due to newer gcc arm64: dts: allwinner: a64: pine64-plus: Add PHY regulator delay arm64: dts: allwinner: a64: sopine-baseboard: Add PHY regulator delay scsi: qla2xxx: fix a potential NULL pointer dereference irqchip/gic-v3-its: Use the exact ITSList for VMOVP netns: fix GFP flags in rtnl_net_notifyid() net: usb: lan78xx: Disable interrupts before calling generic_handle_irq() wireless: Skip directory when generating certificates ASoC: pcm3168a: The codec does not support S32_LE usb: gadget: udc: core: Fix segfault if udc_bind_to_driver() for pending driver fails UBUNTU: upstream stable to v4.14.153, v4.19.83 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Assignee: Kamal Mostafa (kamalmostafa) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) ** Description changed: +
[Kernel-packages] [Bug 1851347] Re: libmbim-proxy using 100% CPU on a Dell Edge Gateway 3002
Jesse, could you please verify that this is fixed in -proposed? Thanks. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1851347 Title: libmbim-proxy using 100% CPU on a Dell Edge Gateway 3002 Status in HWE Next: Fix Released Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Bug description: == Impact == A Dell Edge Gateway 3002 user reported that `top` reports around 100% CPU usage for the libmbim-proxy process. Seen in at least 40% of their devices at some point during the last 6 months. The CPU keeps high at ~100% days or weeks, but does return back to normal without a reboot. The LTE connectivity is seemingly still working as usual. The issue starts after an EPIPE error in the syslogs: 'cdc_mbim 1-3:1.12: nonzero urb status received: -EPIPE'. == Fix == 8fec9355a968 USB: cdc-wdm: ignore -EPIPE from GetEncapsulatedResponse This has been in mainline kernel since 4.14. == Testcase == Connect to the LTE network and see if libmbim-proxy uses 100% after some point. == Risk of Regression == Low, since 1. Already tested by original reporter and no issue found after more than a week (usually it fails twice in a week). 2. Ignoring -EPIPE is the default behavior after 4.14. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1851347/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1845797]
Same issue on Lenovo Yoga C940, Ubuntu 19.10, kernel 5.3.0-23-generic x86_64. Mic not working, audio not working properly with missing speakers. Alsa info -> http://alsa- project.org/db/?f=863a8059dba17f148fb2d3b5b1705d29bc900218 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845797 Title: Microphone not detected Lenovo Yoga S940 Status in Linux: Confirmed Status in alsa-driver package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu 19.10 as well as 19.04 do not detect the microphone in Lenovo Yoga S940 Attached the screen of gnome sound control panel. Inxi output: System:Host: Kernel: 5.3.0-13-generic x86_64 bits: 64 Desktop: Gnome 3.34.0 Distro: Ubuntu 19.10 (Eoan Ermine) Machine: Type: Laptop System: LENOVO product: 81Q7 v: Lenovo Yoga S940-14IWL serial: Mobo: LENOVO model: LNVNB161216 v: SDK0J40709 WIN serial: UEFI: LENOVO v: AKCN34WW date: 06/12/2019 CPU: Topology: Quad Core model: Intel Core i7-8565U bits: 64 type: MT MCP L2 cache: 8192 KiB Speed: 1161 MHz min/max: 400/4600 MHz Core speeds (MHz): 1: 1161 2: 1195 3: 1848 4: 976 5: 1041 6: 1209 7: 1061 8: 2229 Audio: Device-1: Intel Cannon Point-LP High Definition Audio driver: snd_hda_intel Sound Server: ALSA v: k5.3.0-13-generic --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniele2239 F pulseaudio CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-12 (17 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 81Q7 Package: pulseaudio 1:13.0-1ubuntu1 PackageArchitecture: amd64 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-13-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 5.3.0-13.14-generic 5.3.0 RelatedPackageVersions: linux-restricted-modules-5.3.0-13-generic N/A linux-backports-modules-5.3.0-13-generic N/A linux-firmware1.182 Tags: eoan Uname: Linux 5.3.0-13-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-09-21 (8 days ago) UserGroups: adm cdrom dip docker lpadmin microk8s plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 06/12/2019 dmi.bios.vendor: LENOVO dmi.bios.version: AKCN34WW dmi.board.asset.tag: No Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40709 WIN dmi.chassis.asset.tag: No Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Lenovo Yoga S940-14IWL dmi.modalias: dmi:bvnLENOVO:bvrAKCN34WW:bd06/12/2019:svnLENOVO:pn81Q7:pvrLenovoYogaS940-14IWL:rvnLENOVO:rnLNVNB161216:rvrSDK0J40709WIN:cvnLENOVO:ct10:cvrLenovoYogaS940-14IWL: dmi.product.family: Yoga S940-14IWL dmi.product.name: 81Q7 dmi.product.sku: LENOVO_MT_81Q7_BU_idea_FM_Yoga S940-14IWL dmi.product.version: Lenovo Yoga S940-14IWL dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1845797/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853177] Re: Xenial update: 4.4.202 upstream stable release
Please note that the following commits from this upstream Linux stable update were dropped in favor of the UBUNTU SAUCE equivalents: * KVM: Introduce kvm_get_arch_capabilities() * KVM: x86: Emulate MSR_IA32_ARCH_CAPABILITIES on AMD hosts * kvm: x86: IA32_ARCH_CAPABILITIES is always supported * KVM: x86: use Intel speculation bugs and features as derived in generic x86 code * x86/msr: Add the IA32_TSX_CTRL MSR * x86/cpu: Add a helper function x86_read_arch_cap_msr() * x86/cpu: Add a "tsx=" cmdline option with TSX disabled by default * x86/speculation/taa: Add mitigation for TSX Async Abort * x86/speculation/taa: Add sysfs reporting for TSX Async Abort * kvm/x86: Export MDS_NO=0 to guests when TSX is enabled * x86/tsx: Add "auto" option to the tsx= cmdline parameter * x86/speculation/taa: Add documentation for TSX Async Abort * x86/tsx: Add config options to set tsx=on|off|auto * x86/bugs: Add ITLB_MULTIHIT bug infrastructure -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853177 Title: Xenial update: 4.4.202 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: * kvm: mmu: Don't read PDPTEs when paging is not enabled * MIPS: BCM63XX: fix switch core reset on BCM6368 * powerpc/Makefile: Use cflags-y/aflags-y for setting endian options * powerpc: Fix compiling a BE kernel with a powerpc64le toolchain * powerpc/boot: Request no dynamic linker for boot wrapper * x86/speculation/taa: Fix printing of TAA_MSG_SMT on IBRS_ALL CPUs * Linux 4.4.202 * UBUNTU: upstream stable to v4.4.202 4.4.202 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853177] Re: Xenial update: 4.4.202 upstream stable release
** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + * kvm: mmu: Don't read PDPTEs when paging is not enabled + * MIPS: BCM63XX: fix switch core reset on BCM6368 + * powerpc/Makefile: Use cflags-y/aflags-y for setting endian options + * powerpc: Fix compiling a BE kernel with a powerpc64le toolchain + * powerpc/boot: Request no dynamic linker for boot wrapper + * x86/speculation/taa: Fix printing of TAA_MSG_SMT on IBRS_ALL CPUs + * Linux 4.4.202 + * UBUNTU: upstream stable to v4.4.202 -4.4.202 upstream stable release -from git://git.kernel.org/ + 4.4.202 upstream stable release + from git://git.kernel.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853177 Title: Xenial update: 4.4.202 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: * kvm: mmu: Don't read PDPTEs when paging is not enabled * MIPS: BCM63XX: fix switch core reset on BCM6368 * powerpc/Makefile: Use cflags-y/aflags-y for setting endian options * powerpc: Fix compiling a BE kernel with a powerpc64le toolchain * powerpc/boot: Request no dynamic linker for boot wrapper * x86/speculation/taa: Fix printing of TAA_MSG_SMT on IBRS_ALL CPUs * Linux 4.4.202 * UBUNTU: upstream stable to v4.4.202 4.4.202 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853197] Re: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection
** Description changed: Ubuntu linux distro, 4.15.0-62 kernel, server platform. This OS is used as an IPSec VPN gateway. It serves up to several hundred concurrent connections In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed that VPN gateway VMs were running out of physical memory after 12-48 hours, depending on load. Attachments from a server machine in this state in attached leakinfo.txt output of free -t output of /proc/meminfo in out of memory condition - output of /slabtop -o -sc + output of /slabtop -o -sc /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 hrs and ran out of memory Patches for 4.15 and 5.4 Highlight from page_owner, we can see the leak is a buffer associated with the ipsec impelementation. Each connection leaks 32k of memory via alloc_page with order=3 + 100960 times: Page allocated via order 3, mask 0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP) - get_page_from_freelist+0xd64/0x1250 - __alloc_pages_nodemask+0x11c/0x2e0 - alloc_pages_current+0x6a/0xe0 - skb_page_frag_refill+0x71/0x100 - esp_output_head+0x265/0x3e0 [esp4] - esp_output+0xbc/0x180 [esp4] - xfrm_output_resume+0x179/0x530 - xfrm_output+0x8e/0x230 - xfrm4_output_finish+0x2b/0x30 - __xfrm4_output+0x3a/0x50 - xfrm4_output+0x43/0xc0 - ip_forward_finish+0x51/0x80 - ip_forward+0x38a/0x480 - ip_rcv_finish+0x122/0x410 - ip_rcv+0x292/0x360 - __netif_receive_skb_core+0x815/0xbd0 + get_page_from_freelist+0xd64/0x1250 + __alloc_pages_nodemask+0x11c/0x2e0 + alloc_pages_current+0x6a/0xe0 + skb_page_frag_refill+0x71/0x100 + esp_output_head+0x265/0x3e0 [esp4] + esp_output+0xbc/0x180 [esp4] + xfrm_output_resume+0x179/0x530 + xfrm_output+0x8e/0x230 + xfrm4_output_finish+0x2b/0x30 + __xfrm4_output+0x3a/0x50 + xfrm4_output+0x43/0xc0 + ip_forward_finish+0x51/0x80 + ip_forward+0x38a/0x480 + ip_rcv_finish+0x122/0x410 + ip_rcv+0x292/0x360 + __netif_receive_skb_core+0x815/0xbd0 Patch to fix this issue in 4.15 (tested and verified on same server exhibiting above leak): diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index 728272f..7842f83 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x) - } - xfrm_dev_state_free(x); - security_xfrm_state_free(x); + } + xfrm_dev_state_free(x); + security_xfrm_state_free(x); + + if(x->xfrag.page) + put_page(x->xfrag.page); + - kfree(x); + kfree(x); } - - - Patch for master branch (5.4 I believe) from Paul Wouters (p...@nohats.ca) + Patch for master branch (5.4 I believe) from Paul Wouters + (p...@nohats.ca) diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index c6f3c4a1bd99..f3423562d933 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x) - x->type->destructor(x); - xfrm_put_type(x->type); - } + x->type->destructor(x); + xfrm_put_type(x->type); + } + if (x->xfrag.page) + put_page(x->xfrag.page); - xfrm_dev_state_free(x); - security_xfrm_state_free(x); - xfrm_state_free(x); - + xfrm_dev_state_free(x); + security_xfrm_state_free(x); + xfrm_state_free(x); Severity: Critical - we are unable to use any kernel later than 4.11, and are sticking with 4.4 in production. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853197 Title: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu linux distro, 4.15.0-62 kernel, server platform. This OS is used as an IPSec VPN gateway. It serves up to several hundred concurrent connections In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed that VPN gateway VMs were running out of physical memory after 12-48 hours, depending on load. Attachments from a server machine in this state in attached leakinfo.txt output of free -t output of /proc/meminfo in out of memory condition output of /slabtop -o -sc /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 hrs and ran out of memory Patches for 4.15 and 5.4 Highlight from page_owner, we can see the leak is a buffer associated with the ipsec impelementation. Each connection leaks 32k of memory via alloc_page with order=3 100960 times: Page allocated via order 3, mask
[Kernel-packages] [Bug 1848741] Re: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge)
This could be fix: https://www.phoronix.com/scan.php?page=news_item=Ubuntu-19.10-Radeon-RX-5700 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1848741 Title: [amdgpu] Ubuntu 19.10 horizontal graphics corruption on AMD Ryzen 2500u (Raven Ridge) Status in linux package in Ubuntu: Confirmed Status in xserver-xorg-video-amdgpu package in Ubuntu: Confirmed Bug description: I have graphics artefacts: screan tearing, pieces of the previous window appear in the newly opened window. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu8 Architecture: amd64 CurrentDesktop: ubuntu:GNOME DisplayManager: gdm3 DistroRelease: Ubuntu 19.10 InstallationDate: Installed on 2019-09-08 (42 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) Package: gnome-shell 3.34.1-1ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1 RelatedPackageVersions: mutter-common 3.34.1-1ubuntu1 Tags: eoan Uname: Linux 5.3.0-18-generic x86_64 UpgradeStatus: Upgraded to eoan on 2019-10-17 (3 days ago) UserGroups: adm cdrom dip docker input lpadmin plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848741/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash
Oops. Ubuntu 18.04 has dmidecode 3.0 not 3.1; this patch should work
with that version (at least, it applies against unpatched upstream 3.0
anyway).
** Patch added: "0001-dmidecode-Only-scan-dev-mem-for-entry-point-on-x86.patch"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+attachment/5306519/+files/0001-dmidecode-Only-scan-dev-mem-for-entry-point-on-x86.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
Status in dmidecode package in Ubuntu:
Confirmed
Bug description:
Please let me know what other information I can provide. Some basic
info I've captured below.
root@jetson-0423318029481:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@jetson-0423318029481:~# uname -a
Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
root@jetson-0423318029481:~# apt-cache madison dmidecode
dmidecode | 3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main
arm64 Packages
root@jetson-0423318029481:~# dmidecode -V
3.1
root@jetson-0423318029481:~# strace dmidecode
execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
brk(NULL) = 0x559651a000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
close(3)= 0
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0
\10\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f8050a000
mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f80369000
mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
close(3)= 0
mprotect(0x7f804b8000, 16384, PROT_READ) = 0
mprotect(0x55932d9000, 12288, PROT_READ) = 0
mprotect(0x7f8050e000, 4096, PROT_READ) = 0
munmap(0x7f804c2000, 130516)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
brk(NULL) = 0x559651a000
brk(0x559653b000) = 0x559653b000
write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
) = 16
openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or
directory)
write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry
point.
) = 35
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3,
# System hangs and reboots here.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dmidecode 3.1-1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 12:15:53 2019
Dependencies:
gcc-8-base 8.2.0-1ubuntu2~18.04
libc6 2.27-3ubuntu1
libgcc1 1:8.2.0-1ubuntu2~18.04
InstallationDate: Installed on 2019-02-28 (24 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dmidecode
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash
The upstream patch (which was made after upstream release 3.2) back-
ported to upstream 3.1 release (Ubuntu 18.04 contains dmidecode 3.1); it
should presumably apply cleanly to Ubuntu's dmidecode-3.1 source.
** Patch added: "0001-dmidecode-Only-scan-dev-mem-for-entry-point-on-x86.patch"
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+attachment/5306518/+files/0001-dmidecode-Only-scan-dev-mem-for-entry-point-on-x86.patch
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
Status in dmidecode package in Ubuntu:
Confirmed
Bug description:
Please let me know what other information I can provide. Some basic
info I've captured below.
root@jetson-0423318029481:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@jetson-0423318029481:~# uname -a
Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
root@jetson-0423318029481:~# apt-cache madison dmidecode
dmidecode | 3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main
arm64 Packages
root@jetson-0423318029481:~# dmidecode -V
3.1
root@jetson-0423318029481:~# strace dmidecode
execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
brk(NULL) = 0x559651a000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
close(3)= 0
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0
\10\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f8050a000
mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f80369000
mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
close(3)= 0
mprotect(0x7f804b8000, 16384, PROT_READ) = 0
mprotect(0x55932d9000, 12288, PROT_READ) = 0
mprotect(0x7f8050e000, 4096, PROT_READ) = 0
munmap(0x7f804c2000, 130516)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
brk(NULL) = 0x559651a000
brk(0x559653b000) = 0x559653b000
write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
) = 16
openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or
directory)
write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry
point.
) = 35
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3,
# System hangs and reboots here.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dmidecode 3.1-1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 12:15:53 2019
Dependencies:
gcc-8-base 8.2.0-1ubuntu2~18.04
libc6 2.27-3ubuntu1
libgcc1 1:8.2.0-1ubuntu2~18.04
InstallationDate: Installed on 2019-02-28 (24 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dmidecode
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-xenial ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Promote to Proposed - phase-changed: Tuesday, 19. November 2019 17:02 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 19. November 2019 21:21 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait + promote-to-proposed: Pending -- ready for review trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Promote to Proposed phase-changed: Tuesday, 19. November 2019 21:21 UTC reason: promote-to-proposed: Pending -- ready for review trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852270] Re: bionic/linux-aws: 4.15.0-1055.57 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: Confirmed => In Progress ** 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: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Promote to Proposed - phase-changed: Tuesday, 19. November 2019 18:56 UTC + phase: Testing + phase-changed: Tuesday, 19. November 2019 21:16 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 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/1852270 Title: bionic/linux-aws: 4.15.0-1055.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: In Progress Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow verification-testing series: In Progress Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Testing phase-changed: Tuesday, 19. November 2019 21:16 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash
This bug is actually fixed in the dmidecode source code:
(links removed in case that's why launchpad won't let me save this comment).
Can we please back-port this fix into Ubuntu 18.04 AArch64? Thanks.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
Status in dmidecode package in Ubuntu:
Confirmed
Bug description:
Please let me know what other information I can provide. Some basic
info I've captured below.
root@jetson-0423318029481:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@jetson-0423318029481:~# uname -a
Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
root@jetson-0423318029481:~# apt-cache madison dmidecode
dmidecode | 3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main
arm64 Packages
root@jetson-0423318029481:~# dmidecode -V
3.1
root@jetson-0423318029481:~# strace dmidecode
execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
brk(NULL) = 0x559651a000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
close(3)= 0
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0
\10\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f8050a000
mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f80369000
mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
close(3)= 0
mprotect(0x7f804b8000, 16384, PROT_READ) = 0
mprotect(0x55932d9000, 12288, PROT_READ) = 0
mprotect(0x7f8050e000, 4096, PROT_READ) = 0
munmap(0x7f804c2000, 130516)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
brk(NULL) = 0x559651a000
brk(0x559653b000) = 0x559653b000
write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
) = 16
openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or
directory)
write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry
point.
) = 35
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3,
# System hangs and reboots here.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dmidecode 3.1-1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 12:15:53 2019
Dependencies:
gcc-8-base 8.2.0-1ubuntu2~18.04
libc6 2.27-3ubuntu1
libgcc1 1:8.2.0-1ubuntu2~18.04
InstallationDate: Installed on 2019-02-28 (24 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dmidecode
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash
The upstream bug report is:
savannah.nongnu.org dmidecode bug 109697
(launchpad won't let me paste the whole link)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
Status in dmidecode package in Ubuntu:
Confirmed
Bug description:
Please let me know what other information I can provide. Some basic
info I've captured below.
root@jetson-0423318029481:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@jetson-0423318029481:~# uname -a
Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
root@jetson-0423318029481:~# apt-cache madison dmidecode
dmidecode | 3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main
arm64 Packages
root@jetson-0423318029481:~# dmidecode -V
3.1
root@jetson-0423318029481:~# strace dmidecode
execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
brk(NULL) = 0x559651a000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
close(3)= 0
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0
\10\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f8050a000
mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f80369000
mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
close(3)= 0
mprotect(0x7f804b8000, 16384, PROT_READ) = 0
mprotect(0x55932d9000, 12288, PROT_READ) = 0
mprotect(0x7f8050e000, 4096, PROT_READ) = 0
munmap(0x7f804c2000, 130516)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
brk(NULL) = 0x559651a000
brk(0x559653b000) = 0x559653b000
write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
) = 16
openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or
directory)
write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry
point.
) = 35
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3,
# System hangs and reboots here.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dmidecode 3.1-1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 12:15:53 2019
Dependencies:
gcc-8-base 8.2.0-1ubuntu2~18.04
libc6 2.27-3ubuntu1
libgcc1 1:8.2.0-1ubuntu2~18.04
InstallationDate: Installed on 2019-02-28 (24 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dmidecode
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash
The upstream commit is:
http://git.savannah.nongnu.org/cgit/dmidecode.git/commit/?id=e12ec26e19e02281d3e7258c3aabb88a5cf5ec1d
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
Status in dmidecode package in Ubuntu:
Confirmed
Bug description:
Please let me know what other information I can provide. Some basic
info I've captured below.
root@jetson-0423318029481:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@jetson-0423318029481:~# uname -a
Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
root@jetson-0423318029481:~# apt-cache madison dmidecode
dmidecode | 3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main
arm64 Packages
root@jetson-0423318029481:~# dmidecode -V
3.1
root@jetson-0423318029481:~# strace dmidecode
execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
brk(NULL) = 0x559651a000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
close(3)= 0
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0
\10\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f8050a000
mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f80369000
mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
close(3)= 0
mprotect(0x7f804b8000, 16384, PROT_READ) = 0
mprotect(0x55932d9000, 12288, PROT_READ) = 0
mprotect(0x7f8050e000, 4096, PROT_READ) = 0
munmap(0x7f804c2000, 130516)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
brk(NULL) = 0x559651a000
brk(0x559653b000) = 0x559653b000
write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
) = 16
openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or
directory)
write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry
point.
) = 35
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3,
# System hangs and reboots here.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dmidecode 3.1-1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 12:15:53 2019
Dependencies:
gcc-8-base 8.2.0-1ubuntu2~18.04
libc6 2.27-3ubuntu1
libgcc1 1:8.2.0-1ubuntu2~18.04
InstallationDate: Installed on 2019-02-28 (24 days ago)
InstallationMedia: Ubuntu 18.04.2 LTS "Bionic Beaver" - Release amd64
(20190210)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: dmidecode
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dmidecode/+bug/1821632/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853197] Re: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection
All VPN servers have been rolled back to 4.4 Additional log collection is not possible. Setting status to confirmed. ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853197 Title: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu linux distro, 4.15.0-62 kernel, server platform. This OS is used as an IPSec VPN gateway. It serves up to several hundred concurrent connections In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed that VPN gateway VMs were running out of physical memory after 12-48 hours, depending on load. Attachments from a server machine in this state in attached leakinfo.txt output of free -t output of /proc/meminfo in out of memory condition output of /slabtop -o -sc /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 hrs and ran out of memory Patches for 4.15 and 5.4 Highlight from page_owner, we can see the leak is a buffer associated with the ipsec impelementation. Each connection leaks 32k of memory via alloc_page with order=3 Page allocated via order 3, mask 0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP) get_page_from_freelist+0xd64/0x1250 __alloc_pages_nodemask+0x11c/0x2e0 alloc_pages_current+0x6a/0xe0 skb_page_frag_refill+0x71/0x100 esp_output_head+0x265/0x3e0 [esp4] esp_output+0xbc/0x180 [esp4] xfrm_output_resume+0x179/0x530 xfrm_output+0x8e/0x230 xfrm4_output_finish+0x2b/0x30 __xfrm4_output+0x3a/0x50 xfrm4_output+0x43/0xc0 ip_forward_finish+0x51/0x80 ip_forward+0x38a/0x480 ip_rcv_finish+0x122/0x410 ip_rcv+0x292/0x360 __netif_receive_skb_core+0x815/0xbd0 Patch to fix this issue in 4.15 (tested and verified on same server exhibiting above leak): diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index 728272f..7842f83 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x) } xfrm_dev_state_free(x); security_xfrm_state_free(x); + + if(x->xfrag.page) + put_page(x->xfrag.page); + kfree(x); } Patch for master branch (5.4 I believe) from Paul Wouters (p...@nohats.ca) diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index c6f3c4a1bd99..f3423562d933 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x) x->type->destructor(x); xfrm_put_type(x->type); } + if (x->xfrag.page) + put_page(x->xfrag.page); xfrm_dev_state_free(x); security_xfrm_state_free(x); xfrm_state_free(x); Severity: Critical - we are unable to use any kernel later than 4.11, and are sticking with 4.4 in production. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853197] 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 1853197 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/1853197 Title: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection Status in linux package in Ubuntu: Incomplete Bug description: Ubuntu linux distro, 4.15.0-62 kernel, server platform. This OS is used as an IPSec VPN gateway. It serves up to several hundred concurrent connections In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed that VPN gateway VMs were running out of physical memory after 12-48 hours, depending on load. Attachments from a server machine in this state in attached leakinfo.txt output of free -t output of /proc/meminfo in out of memory condition output of /slabtop -o -sc /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 hrs and ran out of memory Patches for 4.15 and 5.4 Highlight from page_owner, we can see the leak is a buffer associated with the ipsec impelementation. Each connection leaks 32k of memory via alloc_page with order=3 Page allocated via order 3, mask 0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP) get_page_from_freelist+0xd64/0x1250 __alloc_pages_nodemask+0x11c/0x2e0 alloc_pages_current+0x6a/0xe0 skb_page_frag_refill+0x71/0x100 esp_output_head+0x265/0x3e0 [esp4] esp_output+0xbc/0x180 [esp4] xfrm_output_resume+0x179/0x530 xfrm_output+0x8e/0x230 xfrm4_output_finish+0x2b/0x30 __xfrm4_output+0x3a/0x50 xfrm4_output+0x43/0xc0 ip_forward_finish+0x51/0x80 ip_forward+0x38a/0x480 ip_rcv_finish+0x122/0x410 ip_rcv+0x292/0x360 __netif_receive_skb_core+0x815/0xbd0 Patch to fix this issue in 4.15 (tested and verified on same server exhibiting above leak): diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index 728272f..7842f83 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x) } xfrm_dev_state_free(x); security_xfrm_state_free(x); + + if(x->xfrag.page) + put_page(x->xfrag.page); + kfree(x); } Patch for master branch (5.4 I believe) from Paul Wouters (p...@nohats.ca) diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index c6f3c4a1bd99..f3423562d933 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x) x->type->destructor(x); xfrm_put_type(x->type); } + if (x->xfrag.page) + put_page(x->xfrag.page); xfrm_dev_state_free(x); security_xfrm_state_free(x); xfrm_state_free(x); Severity: Critical - we are unable to use any kernel later than 4.11, and are sticking with 4.4 in production. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853197/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
(In reply to Michaël Colignon from comment #660) > (In reply to eric.c.morgan from comment #659) > > I applied the latest asrock BIOS with new options "amd cbs global c-state > > control" to disable voltage lowering when idle. > > > > Even with all BIOS settings, custom kernels and params, disabling C states, > > power supplies and so forth I'm done. 2 years of this BS. > > > > I picked up a 65 watt Intel i9 9900. > > > > Good luck to you all and thanks for all the ideas and help. I hope to > > revisit AMD Ryzen based linux servers in a few years. > > I think you had a faulty hardware. With just the typical idle current it fix > the trouble. > That happens. > > On the other side, Windows kernel has no problem with default parameters, so > i think something in Linux is not good. Agree, see https://bugzilla.kernel.org/show_bug.cgi?id=205017 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's
[Kernel-packages] [Bug 1690085]
Folks, this bugzilla entry, with the amount of different issues reported and the amount of FUD all collected in one place, is prohibitively hard for a debugger to handle. So, I'd suggest if you still would like your issue looked at, to open a separate bug. And please refrain from commenting on a bug with your own issue - it is much easier to open a separate one first and then when it turns out that it is a known issue, to merge the two bugzilla entries than to keep them apart in a single report. Thx. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color
[Kernel-packages] [Bug 1853197] [NEW] Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection
Public bug reported: Ubuntu linux distro, 4.15.0-62 kernel, server platform. This OS is used as an IPSec VPN gateway. It serves up to several hundred concurrent connections In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed that VPN gateway VMs were running out of physical memory after 12-48 hours, depending on load. Attachments from a server machine in this state in attached leakinfo.txt output of free -t output of /proc/meminfo in out of memory condition output of /slabtop -o -sc /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 hrs and ran out of memory Patches for 4.15 and 5.4 Highlight from page_owner, we can see the leak is a buffer associated with the ipsec impelementation. Each connection leaks 32k of memory via alloc_page with order=3 Page allocated via order 3, mask 0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP) get_page_from_freelist+0xd64/0x1250 __alloc_pages_nodemask+0x11c/0x2e0 alloc_pages_current+0x6a/0xe0 skb_page_frag_refill+0x71/0x100 esp_output_head+0x265/0x3e0 [esp4] esp_output+0xbc/0x180 [esp4] xfrm_output_resume+0x179/0x530 xfrm_output+0x8e/0x230 xfrm4_output_finish+0x2b/0x30 __xfrm4_output+0x3a/0x50 xfrm4_output+0x43/0xc0 ip_forward_finish+0x51/0x80 ip_forward+0x38a/0x480 ip_rcv_finish+0x122/0x410 ip_rcv+0x292/0x360 __netif_receive_skb_core+0x815/0xbd0 Patch to fix this issue in 4.15 (tested and verified on same server exhibiting above leak): diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index 728272f..7842f83 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x) } xfrm_dev_state_free(x); security_xfrm_state_free(x); + + if(x->xfrag.page) + put_page(x->xfrag.page); + kfree(x); } Patch for master branch (5.4 I believe) from Paul Wouters (p...@nohats.ca) diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index c6f3c4a1bd99..f3423562d933 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -495,6 +495,8 @@ static void ___xfrm_state_destroy(struct xfrm_state *x) x->type->destructor(x); xfrm_put_type(x->type); } + if (x->xfrag.page) + put_page(x->xfrag.page); xfrm_dev_state_free(x); security_xfrm_state_free(x); xfrm_state_free(x); Severity: Critical - we are unable to use any kernel later than 4.11, and are sticking with 4.4 in production. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: ipsec kernel kernel-bug leak linux memory vpn ** Attachment added: "additional data and patches" https://bugs.launchpad.net/bugs/1853197/+attachment/5306500/+files/leakinfo.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853197 Title: Memory leak in net/xfrm/xfrm_state.c - 8 pages per ipsec connection Status in linux package in Ubuntu: New Bug description: Ubuntu linux distro, 4.15.0-62 kernel, server platform. This OS is used as an IPSec VPN gateway. It serves up to several hundred concurrent connections In an attempt to upgrade from the 4.4 kernel to 4.15, the team noticed that VPN gateway VMs were running out of physical memory after 12-48 hours, depending on load. Attachments from a server machine in this state in attached leakinfo.txt output of free -t output of /proc/meminfo in out of memory condition output of /slabtop -o -sc /sys/kernel/debug/page_owner sorted and aggregated after server ran for 12 hrs and ran out of memory Patches for 4.15 and 5.4 Highlight from page_owner, we can see the leak is a buffer associated with the ipsec impelementation. Each connection leaks 32k of memory via alloc_page with order=3 Page allocated via order 3, mask 0x1085220(GFP_ATOMIC|__GFP_NOWARN|__GFP_NORETRY|__GFP_COMP) get_page_from_freelist+0xd64/0x1250 __alloc_pages_nodemask+0x11c/0x2e0 alloc_pages_current+0x6a/0xe0 skb_page_frag_refill+0x71/0x100 esp_output_head+0x265/0x3e0 [esp4] esp_output+0xbc/0x180 [esp4] xfrm_output_resume+0x179/0x530 xfrm_output+0x8e/0x230 xfrm4_output_finish+0x2b/0x30 __xfrm4_output+0x3a/0x50 xfrm4_output+0x43/0xc0 ip_forward_finish+0x51/0x80 ip_forward+0x38a/0x480 ip_rcv_finish+0x122/0x410 ip_rcv+0x292/0x360 __netif_receive_skb_core+0x815/0xbd0 Patch to fix this issue in 4.15 (tested and verified on same server exhibiting above leak): diff --git a/net/xfrm/xfrm_state.c b/net/xfrm/xfrm_state.c index 728272f..7842f83 100644 --- a/net/xfrm/xfrm_state.c +++ b/net/xfrm/xfrm_state.c @@ -451,6 +451,10 @@ static void xfrm_state_gc_destroy(struct xfrm_state *x) } xfrm_dev_state_free(x);
[Kernel-packages] [Bug 1853196] [NEW] nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build
Public bug reported: i tried to install nvidia drivers from this link https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-19-10-eoan-ermine-linux . My video card is nvdia Gforce GT610. Sometimes on boot there is pixel "scratches" (on the pink screen). ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-kernel-source-390 390.129-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DKMSKernelVersion: 5.3.0-23-generic Date: Tue Nov 19 22:29:16 2019 Dependencies: PackageVersion: 390.129-0ubuntu2 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-390 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to nvidia-graphics-drivers-390 in Ubuntu. https://bugs.launchpad.net/bugs/1853196 Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build Status in nvidia-graphics-drivers-390 package in Ubuntu: New Bug description: i tried to install nvidia drivers from this link https://linuxconfig.org/how-to-install-the-nvidia-drivers-on-ubuntu-19-10-eoan-ermine-linux . My video card is nvdia Gforce GT610. Sometimes on boot there is pixel "scratches" (on the pink screen). ProblemType: Package DistroRelease: Ubuntu 19.10 Package: nvidia-kernel-source-390 390.129-0ubuntu2 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 DKMSKernelVersion: 5.3.0-23-generic Date: Tue Nov 19 22:29:16 2019 Dependencies: PackageVersion: 390.129-0ubuntu2 Python3Details: /usr/bin/python3.7, Python 3.7.5rc1, python3-minimal, 3.7.5-1 PythonDetails: /usr/bin/python2.7, Python 2.7.17rc1, python-minimal, 2.7.17-1 RelatedPackageVersions: dpkg 1.19.7ubuntu2 apt 1.9.4 SourcePackage: nvidia-graphics-drivers-390 Title: nvidia-kernel-source-390 390.129-0ubuntu2: nvidia kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-390/+bug/1853196/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1690085]
> Likely not bad hardware. My 1700 was RMAd for the segfault issue (another > pain point), and has passed all testing. Memory has been tested as well, > many times over, with different profiles and settings. > I also had my 1600 RMAd, but still I experience hangs now and then. I have the impression that the hangs are worse lately. But I have no hard statistics. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic x86_64
[Kernel-packages] [Bug 1821632] Re: dmidecode causing system crash
> Reading illegal memory should not crash the system
I think this depends on what the memory is.
I agree 100% for any application-level memory (stuff from regular APIs
like sbrk() or mmap() etc.).
In this case, the application opens /dev/mem, which allows it to access
arbitrary physical memory without restriction. It assumes that a certain
physical memory region can be accessed (the DMI region) and does so. The
HW triggers an SError in this case since no device exists at that
location in memory, since this platform doesn't support DMI. This is
correct HW response to the request. The solution is to prevent SW from
accessing this location.
This issue happens identically if you were to use an upstream kernel
(which does support the HW), or the Ubuntu kernel (assuming it supports
this HW model).
Whether this SW access prevention is implemented in the kernel or the
application may be open for debate. I believe the definition of the
/dev/mem device is such that it does not intend to filter addresses to
prevent applications from accessing invalid HW. As such, I believe it's
up to the application to fix the issue; it should determine whether the
platform supports DMI before explicitly using low-level primitives
(/dev/mem) to attempt to access it.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to dmidecode in Ubuntu.
https://bugs.launchpad.net/bugs/1821632
Title:
dmidecode causing system crash
Status in dmidecode package in Ubuntu:
Confirmed
Bug description:
Please let me know what other information I can provide. Some basic
info I've captured below.
root@jetson-0423318029481:~# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 18.04.1 LTS
Release: 18.04
Codename: bionic
root@jetson-0423318029481:~# uname -a
Linux jetson-0423318029481 4.9.108-tegra #1 SMP PREEMPT Wed Oct 31 15:17:21
PDT 2018 aarch64 aarch64 aarch64 GNU/Linux
root@jetson-0423318029481:~# apt-cache madison dmidecode
dmidecode | 3.1-1 | http://ports.ubuntu.com/ubuntu-ports bionic/main
arm64 Packages
root@jetson-0423318029481:~# dmidecode -V
3.1
root@jetson-0423318029481:~# strace dmidecode
execve("/usr/sbin/dmidecode", ["dmidecode"], 0x7fdc753060 /* 15 vars */) = 0
brk(NULL) = 0x559651a000
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
faccessat(AT_FDCWD, "/etc/ld.so.preload", R_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/etc/ld.so.cache", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=130516, ...}) = 0
mmap(NULL, 130516, PROT_READ, MAP_PRIVATE, 3, 0) = 0x7f804c2000
close(3)= 0
faccessat(AT_FDCWD, "/etc/ld.so.nohwcap", F_OK) = -1 ENOENT (No such file or
directory)
openat(AT_FDCWD, "/lib/aarch64-linux-gnu/libc.so.6", O_RDONLY|O_CLOEXEC) = 3
read(3, "\177ELF\2\1\1\3\0\0\0\0\0\0\0\0\3\0\267\0\1\0\0\0
\10\2\0\0\0\0\0"..., 832) = 832
fstat(3, {st_mode=S_IFREG|0755, st_size=1341080, ...}) = 0
mmap(NULL, 8192, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
0x7f8050a000
mmap(NULL, 1409880, PROT_READ|PROT_EXEC, MAP_PRIVATE|MAP_DENYWRITE, 3, 0) =
0x7f80369000
mprotect(0x7f804a9000, 61440, PROT_NONE) = 0
mmap(0x7f804b8000, 24576, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_DENYWRITE, 3, 0x13f000) = 0x7f804b8000
mmap(0x7f804be000, 13144, PROT_READ|PROT_WRITE,
MAP_PRIVATE|MAP_FIXED|MAP_ANONYMOUS, -1, 0) = 0x7f804be000
close(3)= 0
mprotect(0x7f804b8000, 16384, PROT_READ) = 0
mprotect(0x55932d9000, 12288, PROT_READ) = 0
mprotect(0x7f8050e000, 4096, PROT_READ) = 0
munmap(0x7f804c2000, 130516)= 0
fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 0), ...}) = 0
brk(NULL) = 0x559651a000
brk(0x559653b000) = 0x559653b000
write(1, "# dmidecode 3.1\n", 16# dmidecode 3.1
) = 16
openat(AT_FDCWD, "/sys/firmware/dmi/tables/smbios_entry_point", O_RDONLY) =
-1 ENOENT (No such file or directory)
openat(AT_FDCWD, "/sys/firmware/efi/systab", O_RDONLY) = -1 ENOENT (No such
file or directory)
openat(AT_FDCWD, "/proc/efi/systab", O_RDONLY) = -1 ENOENT (No such file or
directory)
write(1, "Scanning /dev/mem for entry poin"..., 35Scanning /dev/mem for entry
point.
) = 35
openat(AT_FDCWD, "/dev/mem", O_RDONLY) = 3
fstat(3,
# System hangs and reboots here.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: dmidecode 3.1-1
ProcVersionSignature: Ubuntu 4.18.0-16.17~18.04.1-generic 4.18.20
Uname: Linux 4.18.0-16-generic x86_64
ApportVersion: 2.20.9-0ubuntu7.6
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Mar 25 12:15:53 2019
Dependencies:
gcc-8-base 8.2.0-1ubuntu2~18.04
libc6 2.27-3ubuntu1
libgcc1 1:8.2.0-1ubuntu2~18.04
InstallationDate: Installed
[Kernel-packages] [Bug 1690085]
(In reply to Michaël Colignon from comment #660) > (In reply to eric.c.morgan from comment #659) > > I applied the latest asrock BIOS with new options "amd cbs global c-state > > control" to disable voltage lowering when idle. > > > > Even with all BIOS settings, custom kernels and params, disabling C states, > > power supplies and so forth I'm done. 2 years of this BS. > > > > I picked up a 65 watt Intel i9 9900. > > > > Good luck to you all and thanks for all the ideas and help. I hope to > > revisit AMD Ryzen based linux servers in a few years. > > I think you had a faulty hardware. With just the typical idle current it fix > the trouble. > That happens. > > On the other side, Windows kernel has no problem with default parameters, so > i think something in Linux is not good. Likely not bad hardware. My 1700 was RMAd for the segfault issue (another pain point), and has passed all testing. Memory has been tested as well, many times over, with different profiles and settings. Tiny i9-9900 itx ready for transplant. I feel dirty. https://i.imgur.com/fTvWrWd.png -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random).
[Kernel-packages] [Bug 1690085]
(In reply to eric.c.morgan from comment #659) > I applied the latest asrock BIOS with new options "amd cbs global c-state > control" to disable voltage lowering when idle. > > Even with all BIOS settings, custom kernels and params, disabling C states, > power supplies and so forth I'm done. 2 years of this BS. > > I picked up a 65 watt Intel i9 9900. > > Good luck to you all and thanks for all the ideas and help. I hope to > revisit AMD Ryzen based linux servers in a few years. I think you had a faulty hardware. With just the typical idle current it fix the trouble. That happens. On the other side, Windows kernel has no problem with default parameters, so i think something in Linux is not good. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate:
[Kernel-packages] [Bug 1690085] Re: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks
** Bug watch added: Linux Kernel Bug Tracker #205017 https://bugzilla.kernel.org/show_bug.cgi?id=205017 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1690085 Title: Ryzen 1800X freeze - rcu_sched detected stalls on CPUs/tasks Status in Linux: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Hi, We aregetting various kernel crash on a pretty new config. We're using Ryzen 1800X CPU with X370 Gaming Pro Carbon MB (7A32V1) using latest BIOS available (1.52) We are running Ubuntu 17.04 (amd64), we've tried different kernel version, native one and releases from http://kernel.ubuntu.com/~kernel-ppa/mainline/ too. Tested kernel version: native 17.04 kernel 4.10.15 Issues are the same, we're getting random freeze on the machine. Here is kern.log entry when happening : May 10 22:41:56 dev2 kernel: [24366.186246] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:41:56 dev2 kernel: [24366.187618] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=913449 May 10 22:41:56 dev2 kernel: [24366.188977] (detected by 12, t=1860207 jiffies, g=10001, c=1, q=4656) May 10 22:41:56 dev2 kernel: [24366.190344] Task dump for CPU 0: May 10 22:41:56 dev2 kernel: [24366.190345] swapper/0 R running task 0 0 0 0x0008 May 10 22:41:56 dev2 kernel: [24366.190348] Call Trace: May 10 22:41:56 dev2 kernel: [24366.190354] ? native_safe_halt+0x6/0x10 May 10 22:41:56 dev2 kernel: [24366.190355] ? default_idle+0x20/0xd0 May 10 22:41:56 dev2 kernel: [24366.190358] ? arch_cpu_idle+0xf/0x20 May 10 22:41:56 dev2 kernel: [24366.190360] ? default_idle_call+0x23/0x30 May 10 22:41:56 dev2 kernel: [24366.190362] ? do_idle+0x16f/0x200 May 10 22:41:56 dev2 kernel: [24366.190364] ? cpu_startup_entry+0x71/0x80 May 10 22:41:56 dev2 kernel: [24366.190366] ? rest_init+0x77/0x80 May 10 22:41:56 dev2 kernel: [24366.190368] ? start_kernel+0x464/0x485 May 10 22:41:56 dev2 kernel: [24366.190369] ? early_idt_handler_array+0x120/0x120 May 10 22:41:56 dev2 kernel: [24366.190371] ? x86_64_start_reservations+0x24/0x26 May 10 22:41:56 dev2 kernel: [24366.190372] ? x86_64_start_kernel+0x14d/0x170 May 10 22:41:56 dev2 kernel: [24366.190373] ? start_cpu+0x14/0x14 May 10 22:44:56 dev2 kernel: [24546.188093] INFO: rcu_sched detected stalls on CPUs/tasks: May 10 22:44:56 dev2 kernel: [24546.189461] 0-...: (1 GPs behind) idle=49b/1/0 softirq=28561/28563 fqs=935027 May 10 22:44:56 dev2 kernel: [24546.190823] (detected by 14, t=1905212 jiffies, g=10001, c=1, q=4740) May 10 22:44:56 dev2 kernel: [24546.192191] Task dump for CPU 0: May 10 22:44:56 dev2 kernel: [24546.192192] swapper/0 R running task 0 0 0 0x0008 May 10 22:44:56 dev2 kernel: [24546.192195] Call Trace: May 10 22:44:56 dev2 kernel: [24546.192199] ? native_safe_halt+0x6/0x10 May 10 22:44:56 dev2 kernel: [24546.192201] ? default_idle+0x20/0xd0 May 10 22:44:56 dev2 kernel: [24546.192203] ? arch_cpu_idle+0xf/0x20 May 10 22:44:56 dev2 kernel: [24546.192204] ? default_idle_call+0x23/0x30 May 10 22:44:56 dev2 kernel: [24546.192206] ? do_idle+0x16f/0x200 May 10 22:44:56 dev2 kernel: [24546.192208] ? cpu_startup_entry+0x71/0x80 May 10 22:44:56 dev2 kernel: [24546.192210] ? rest_init+0x77/0x80 May 10 22:44:56 dev2 kernel: [24546.192211] ? start_kernel+0x464/0x485 May 10 22:44:56 dev2 kernel: [24546.192213] ? early_idt_handler_array+0x120/0x120 May 10 22:44:56 dev2 kernel: [24546.192214] ? x86_64_start_reservations+0x24/0x26 May 10 22:44:56 dev2 kernel: [24546.192215] ? x86_64_start_kernel+0x14d/0x170 May 10 22:44:56 dev2 kernel: [24546.192217] ? start_cpu+0x14/0x14 Depending on the kernel version, we've got NMI watchdog errors related to CPU stuck (mentioning the CPU core id, which is random). Crash is happening randomly, but in general after some hours (3-4h). Now, we've installed kernel 4.11.0-041100-generic #201705041534 this morning and waiting for crash... For now, the machine is not "used", at least, it's not CPU stressed... Thanks --- ApportVersion: 2.20.4-0ubuntu4 Architecture: amd64 DistroRelease: Ubuntu 17.04 InstallationDate: Installed on 2017-05-09 (1 days ago) InstallationMedia: Ubuntu-Server 17.04 "Zesty Zapus" - Release amd64 (20170412) Package: linux (not installed) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash Tags: zesty Uname: Linux 4.11.0-041100-generic 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:
[Kernel-packages] [Bug 1799235] Re: kworker process starts at 85% of cpu and stays there
PID USER PRI NI VIRT RES SHR S CPU% MEM% TIME+ Command 20684 root 20 0 0 0 0 I 59.9 0.0 2:52.66 kworker/0:0-kacpi_notify I'm also having this on a Dell G7 laptop ( Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz ) with kernel 4.19.80. I have also tried kernel's 5.2.0 with the same result. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1799235 Title: kworker process starts at 85% of cpu and stays there Status in Dell Sputnik: New Status in linux package in Ubuntu: Confirmed Bug description: Ubuntu starts, w/ /sbin/init, a kworker process that never stops running below 85%: pb@pb-tower:~/Downloads$ ps -elf F S UIDPID PPID C PRI NI ADDR SZ WCHAN STIME TTY TIME CMD 4 S root 1 0 0 80 0 - 56471 - 18:30 ?00:00:01 /sbin/init splash 1 S root 2 0 0 80 0 - 0 - 18:30 ?00:00:00 [kthreadd] 1 R root85 2 63 80 0 - 0 - 18:30 ? 00:03:03 [kworker/0:1+kac] After a few hours, grep . -r /sys/firmware/acpi/interrupts/ shows tens of millions of interrupts. The following command line stops the kworker process: echo "disable" > /sys/firmware/acpi/interrupts/gpe6F On the other hand, I haven't been able to properly shut down my system after this command (power never goes off except manually). I believe the bug is related to the one discussed here: https://superuser.com/questions/1117992/acpi-exception-ae-not-found- while-evaluating-gpe-method-floods-syslog The dmesg w/ this report may be somewhat confusing because there is an unsigned module. But w/ the module removed, dmesg gives the following: [0.097480] ACPI: Dynamic OEM Table Load: [0.097480] ACPI: SSDT 0xA07F57173000 000317 (v02 PmRef ApHwp 3000 INTL 20160527) [0.097480] ACPI: Executed 1 blocks of module-level executable AML code [0.100180] ACPI: Dynamic OEM Table Load: [0.100186] ACPI: SSDT 0xA07F577EF400 00030A (v02 PmRef ApCst 3000 INTL 20160527) [0.100473] ACPI: Executed 1 blocks of module-level executable AML code [0.102187] ACPI: Interpreter enabled [0.10] ACPI: (supports S0 S3 S4 S5) [0.102223] ACPI: Using IOAPIC for interrupt routing [0.102275] HEST: Table parsing has been initialized. [0.102277] PCI: Using host bridge windows from ACPI; if necessary, use "pci=nocrs" and report a bug [0.103580] ACPI: GPE 0x20 active on init [0.104031] ACPI Error: No handler for Region [WST1] ((ptrval)) [GenericSerialBus] (20170831/evregion-166) [0.104035] ACPI Error: Region GenericSerialBus (ID=9) has no handler (20170831/exfldio-299) [0.104040] Initialized Local Variables for Method [PAS1]: [0.104041] Local0: (ptrval)Integer 0001 [0.104045] No Arguments are initialized for method [PAS1] [0.104046] ACPI Error: Method parse/execution failed \_SB.PCI0.I2C0.PAS1, AE_NOT_EXIST (20170831/psparse-550) [0.104052] ACPI Error: Method parse/execution failed \_GPE._L20, AE_NOT_EXIST (20170831/psparse-550) [0.104058] ACPI Exception: AE_NOT_EXIST, while evaluating GPE method [_L20] (20170831/evgpe-646) [0.104005] ACPI: GPE 0x6F active on init [0.104005] ACPI: Enabled 10 GPEs in block 00 to 7F [0.212126] ACPI: Power Resource [USBC] (on) [0.444270] pci :06:00.0: PME# supported from D0 D1 D2 D3hot [0.444270] pci :06:00.1: [1033:00e0] type 00 class 0x0c0320 [0.444270] pci :06:00.1: reg 0x10: [mem 0xa200-0xa2ff] [0.444278] pci :06:00.1: supports D1 D2 [0.444278] pci :06:00.1: PME# supported from D0 D1 D2 D3hot [0.444278] pci :05:00.0: PCI bridge to [bus 06] [0.444278] pci :05:00.0: bridge window [mem 0xa200-0xa20f] [0.456183] ACPI: PCI Interrupt Link [LNKA] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKB] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKC] (IRQs) *0 [0.456183] ACPI: PCI Interrupt Link [LNKD] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKE] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKF] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKG] (IRQs) *1 [0.456183] ACPI: PCI Interrupt Link [LNKH] (IRQs) *1 [0.464184] SCSI subsystem initialized [0.464186] libata version 3.00 loaded. [0.464186] pci :00:02.0: vgaarb: setting as boot VGA device [1.225495] Scanning for low memory corruption every 60 seconds [1.226265] Initialise system trusted keyrings [1.226271] Key type blacklist registered [1.226399] workingset: timestamp_bits=36 max_order=23 bucket_order=0 [1.227127] zbud: loaded [1.227482] squashfs: version 4.0
[Kernel-packages] [Bug 1853192] Re: Please add patch fixing RK818 ID detection
** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853192 Title: Please add patch fixing RK818 ID detection Status in linux package in Ubuntu: Confirmed Bug description: Hi, Please add this upstream patch to ubuntu kernel: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=37ef8c2c15bdc1322b160e38986c187de2b877b2 It fixes detection of RK818 pmic. Without it ubuntu hangs at boot. Cheers Paweł Jarosz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853192] 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 1853192 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/1853192 Title: Please add patch fixing RK818 ID detection Status in linux package in Ubuntu: Incomplete Bug description: Hi, Please add this upstream patch to ubuntu kernel: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=37ef8c2c15bdc1322b160e38986c187de2b877b2 It fixes detection of RK818 pmic. Without it ubuntu hangs at boot. Cheers Paweł Jarosz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853192] [NEW] Please add patch fixing RK818 ID detection
Public bug reported: Hi, Please add this upstream patch to ubuntu kernel: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=37ef8c2c15bdc1322b160e38986c187de2b877b2 It fixes detection of RK818 pmic. Without it ubuntu hangs at boot. Cheers Paweł Jarosz ** Affects: linux (Ubuntu) Importance: Undecided Status: 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/1853192 Title: Please add patch fixing RK818 ID detection Status in linux package in Ubuntu: Incomplete Bug description: Hi, Please add this upstream patch to ubuntu kernel: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux- next.git/commit/?id=37ef8c2c15bdc1322b160e38986c187de2b877b2 It fixes detection of RK818 pmic. Without it ubuntu hangs at boot. Cheers Paweł Jarosz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853192/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825222] Re: CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64, arm64
Hi, I've tested 5.3.0-24-generic kernel with eoan. It boots ok after adding few modules (pl330, dw_mmc-rockchip, dw_mmc, sdhci-of-arasan, rk808, rk808-regulator, pwm-rockchip) to initramfs. Thanks! Ubuntu team is awesome! :) Also I'll open new bug about adding RK818 ID patch. About CONFIG_CRYPTO_DEV_ROCKCHIP=m please leave it as module :) Cheers Paweł -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1825222 Title: CONFIG_ARCH_ROCKCHIP is not set in ubuntu 18.04 aarch64,arm64 Status in linux package in Ubuntu: Incomplete Status in linux source package in Bionic: New Status in linux source package in Disco: New Status in linux source package in Eoan: Incomplete Bug description: Would it be possible to enable rockchip support in Ubuntu 18.04 kernel for arch aarch64(arm64)? Related kernel config options: CONFIG_ARCH_ROCKCHIP CONFIG_PCIE_ROCKCHIP CONFIG_PCIE_ROCKCHIP_HOST CONFIG_EMAC_ROCKCHIP CONFIG_DWMAC_ROCKCHIP CONFIG_ROCKCHIP_PHY CONFIG_SPI_ROCKCHIP CONFIG_PINCTRL_ROCKCHIP CONFIG_ROCKCHIP_IODOMAIN CONFIG_ROCKCHIP_THERMAL CONFIG_VIDEO_ROCKCHIP_RGA CONFIG_DRM_ROCKCHIP CONFIG_ROCKCHIP_ANALOGIX_DP CONFIG_ROCKCHIP_CDN_DP CONFIG_ROCKCHIP_DW_HDMI CONFIG_ROCKCHIP_DW_MIPI_DSI CONFIG_ROCKCHIP_INNO_HDMI CONFIG_ROCKCHIP_LVDS CONFIG_ROCKCHIP_RGB CONFIG_SND_SOC_ROCKCHIP CONFIG_SND_SOC_ROCKCHIP_I2S CONFIG_SND_SOC_ROCKCHIP_PDM CONFIG_SND_SOC_ROCKCHIP_SPDIF CONFIG_SND_SOC_ROCKCHIP_MAX98090 CONFIG_SND_SOC_ROCKCHIP_RT5645 CONFIG_MMC_DW_ROCKCHIP CONFIG_ROCKCHIP_TIMER CONFIG_ROCKCHIP_MBOX CONFIG_ROCKCHIP_IOMMU CONFIG_ROCKCHIP_GRF CONFIG_ROCKCHIP_PM_DOMAINS CONFIG_DEVFREQ_EVENT_ROCKCHIP_DFI CONFIG_ROCKCHIP_SARADC CONFIG_PWM_ROCKCHIP CONFIG_PHY_ROCKCHIP_DP CONFIG_PHY_ROCKCHIP_EMMC CONFIG_PHY_ROCKCHIP_INNO_HDMI CONFIG_PHY_ROCKCHIP_INNO_USB2 CONFIG_PHY_ROCKCHIP_PCIE CONFIG_PHY_ROCKCHIP_TYPEC CONFIG_PHY_ROCKCHIP_USB CONFIG_ROCKCHIP_EFUSE CONFIG_CRYPTO_DEV_ROCKCHIP Cheers, Paweł Jarosz To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1825222/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853061] Re: Connection to USB-C hub frequently drops when charging over it
I guess the manufacturer calls it a dock even though the computer does not actually dock into it, it attaches via a Thunderbolt 3 cable which I guess is different than USB-C . Sorry for the mistake. This entry in the lspci: 40:00.0 Ethernet controller [0200]: Intel Corporation I210 Gigabit Network Connection [8086:1533] (rev 03) is indeed over the dock (it disappears when the dock is unplugged; the other Ethernet controller remains so I guess it is the one in the laptop itself). When I ran the info reporting program the only connections I had to the dock were an ethernet cable to the dock's ethernet port and an external monitor from a USB-C port on the dock to the displayport out on the monitor. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853061 Title: Connection to USB-C hub frequently drops when charging over it Status in linux package in Ubuntu: Confirmed Bug description: I am running Ubuntu 19.10 on a Lenovo Thinkpad X1 Extreme. I have a CalDigit TS3 Plus USB-C hub connected to one of the laptop's USB-C/Thunderbolt ports. The laptop supports charging over USB-C. When I try to charge from the hub over USB-C, Ubuntu seems to frequently "drop" the connection to the hub and loses connection to the stuff attached to the hub (e.g., an external monitor connected to the hub by USB-C to displayport, an ethernet connection, and USB devices). After a few seconds, the computer reconnects to these devices. I disabled TLP but the problem persists. When I have the laptop's power adapter attached in addition to the USB-C hub, the problem does not appear and the computer does not lose connection to the peripherals. ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-23-generic 5.3.0-23.25 ProcVersionSignature: Ubuntu 5.3.0-23.25-generic 5.3.7 Uname: Linux 5.3.0-23-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu8.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: matt 2211 F pulseaudio /dev/snd/controlC1: matt 2211 F pulseaudio /dev/snd/controlC0: matt 2211 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Nov 18 13:44:33 2019 InstallationDate: Installed on 2019-09-04 (75 days ago) InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416) MachineType: LENOVO 20MGS1YW00 ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.3.0-23-generic root=UUID=3a5c73f9-5be3-4590-88a9-e362d949931c ro quiet splash resume=UUID=d464672d-224c-4149-a105-3a0cad515692 vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.3.0-23-generic N/A linux-backports-modules-5.3.0-23-generic N/A linux-firmware1.183.2 SourcePackage: linux UpgradeStatus: Upgraded to eoan on 2019-10-21 (28 days ago) dmi.bios.date: 08/06/2019 dmi.bios.vendor: LENOVO dmi.bios.version: N2EET42W (1.24 ) dmi.board.asset.tag: Not Available dmi.board.name: 20MGS1YW00 dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2EET42W(1.24):bd08/06/2019:svnLENOVO:pn20MGS1YW00:pvrThinkPadX1Extreme:rvnLENOVO:rn20MGS1YW00:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad X1 Extreme dmi.product.name: 20MGS1YW00 dmi.product.sku: LENOVO_MT_20MG_BU_Think_FM_ThinkPad X1 Extreme dmi.product.version: ThinkPad X1 Extreme dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852270] Re: bionic/linux-aws: 4.15.0-1055.57 -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: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:56 UTC reason: - promote-to-proposed: Pending -- package copies requested to Proposed lrm:missing,main:missing,meta:missing + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 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/1852270 Title: bionic/linux-aws: 4.15.0-1055.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:56 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Tuesday, 19. November 2019 17:02 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait + promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Tuesday, 19. November 2019 17:02 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa meta:depwait,signed:depwait trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852270] Re: bionic/linux-aws: 4.15.0-1055.57 -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: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:56 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Pending -- package copies requested to Proposed lrm:missing,main:missing,meta:missing trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 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/1852270 Title: bionic/linux-aws: 4.15.0-1055.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:56 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1609750]
In downstream bug report http://pad.lv/1609750 it was noted that this patch would be needed: https://github.com/torvalds/linux/commit/d5e120422db8808e1c8b1507900ca393a877c58f However I've tested 5.4rc7 and it does not seem to help. Do people know of other non-upstreamed patches required for the audio to work? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1609750]
if you can recompile a kernel, using Mark Brown's for-next should have have all the latest changes from Google for Cyan. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1609750 Title: Audio not working on Acer Chromebook R11 Status in linux: Confirmed Status in linux package in Ubuntu: In Progress Status in pulseaudio package in Ubuntu: Invalid Bug description: Audio is not working at all on Acer Chromebook R11 (codename CYAN). It's a Intel Braswell platform. snd_hda_intel messages seem normal, but Pulseaudio does not detect sound hardware. ProblemType: Bug DistroRelease: Ubuntu 16.10 Package: pulseaudio 1:9.0-1.1ubuntu1 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 Uname: Linux 4.4.0-33-generic x86_64 ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity Date: Thu Aug 4 14:12:03 2016 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE --- ApportVersion: 2.20.3-0ubuntu2 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/by-path', '/dev/snd/hwC0D2', '/dev/snd/pcmC0D8p', '/dev/snd/pcmC0D7p', '/dev/snd/pcmC0D3p', '/dev/snd/controlC0', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: Unity DistroRelease: Ubuntu 16.10 HibernationDevice: RESUME=UUID=53fe7902-c347-4ff8-945d-a3e3de773a08 InstallationDate: Installed on 2016-07-22 (13 days ago) InstallationMedia: Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 8087:0a2a Intel Corp. Bus 001 Device 002: ID 0bda:57cf Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: GOOGLE Cyan Package: linux-image-4.4.0-33-generic 4.4.0-33.52 PackageArchitecture: amd64 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-33-generic root=UUID=742e4082-264a-4459-93df-9ec07b41d5e8 ro quiet splash vt.handoff=7 ProcVersionSignature: Ubuntu 4.4.0-33.52-generic 4.4.15 PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. RelatedPackageVersions: linux-restricted-modules-4.4.0-33-generic N/A linux-backports-modules-4.4.0-33-generic N/A linux-firmware1.159 Tags: yakkety Uname: Linux 4.4.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 05/20/2016 dmi.bios.vendor: coreboot dmi.chassis.type: 3 dmi.chassis.vendor: GOOGLE dmi.modalias: dmi:bvncoreboot:bvr:bd05/20/2016:svnGOOGLE:pnCyan:pvr1.0:cvnGOOGLE:ct3:cvr: dmi.product.name: Cyan dmi.product.version: 1.0 dmi.sys.vendor: GOOGLE To manage notifications about this bug go to: https://bugs.launchpad.net/kernel/+bug/1609750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852270] Re: bionic/linux-aws: 4.15.0-1055.57 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- 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/1852270 Title: bionic/linux-aws: 4.15.0-1055.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:56 UTC reason: promote-to-proposed: Pending -- package copies requested to Proposed lrm:missing,main:missing,meta:missing trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852270] Re: bionic/linux-aws: 4.15.0-1055.57 -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: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws - phase: Ready for Promote to Proposed - phase-changed: Monday, 18. November 2019 07:37 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 19. November 2019 18:56 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 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/1852270 Title: bionic/linux-aws: 4.15.0-1055.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:56 UTC reason: promote-to-proposed: Pending -- package copies requested to Proposed lrm:missing,main:missing,meta:missing trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853180] Re: update ENA driver for DIMLIB dynamic interrupt moderation
https://lists.ubuntu.com/archives/kernel-team/2019-November/105559.html
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853180
Title:
update ENA driver for DIMLIB dynamic interrupt moderation
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Update the Amazon ENA driver to latest mainline version with dynamic
interrupt moderation supplied by DIMLIB, plus a couple of pending
fixes from the netdev mailing list.
Note: For {Xenial,Bionic,Disco}, this needs bug 1852637 ("backport
DIMLIB (lib/dim/) to pre-5.2 kernels") as a prerequisite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853180/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852270] Re: bionic/linux-aws: 4.15.0-1055.57 -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) => Łukasz Zemczak (sil2100) -- 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/1852270 Title: bionic/linux-aws: 4.15.0-1055.57 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852289 packages: lrm: linux-restricted-modules-aws main: linux-aws meta: linux-meta-aws phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:56 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-aws-fips: bug 1852268 bionic/linux-aws/aws-kernel: bug 1852267 xenial/linux-aws-hwe: bug 1852269 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852230] Re: eoan/linux-oracle: 5.3.0-1007.8 -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: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:11 UTC reason: - promote-to-proposed: Stalled -- review in progress + promote-to-proposed: Ongoing -- package copied to Proposed signed:building trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs ** 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: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:11 UTC reason: - promote-to-proposed: Ongoing -- package copied to Proposed signed:building + promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852230 Title: eoan/linux-oracle: 5.3.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:11 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852230] Re: eoan/linux-oracle: 5.3.0-1007.8 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852230 Title: eoan/linux-oracle: 5.3.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed 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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:11 UTC reason: promote-to-proposed: Pending -- package copied to Proposed signed:queued trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852268] Re: bionic/linux-aws-fips: 4.15.0-2005.5 -proposed tracker
** Changed in: kernel-sru-workflow/promote-to-proposed Status: New => Confirmed ** Tags added: block-proposed-bionic ** Tags added: block-proposed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- + boot-testing-requested: true kernel-stable-master-bug: 1852270 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 Proposed - phase-changed: Tuesday, 19. November 2019 16:50 UTC + phase: Ready for Promote to Proposed + phase-changed: Tuesday, 19. November 2019 18:21 UTC reason: - promote-to-proposed: Ongoing -- builds not complete in ppa lrm:depwait,meta:depwait,signed:depwait + promote-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 in Ubuntu. https://bugs.launchpad.net/bugs/1852268 Title: bionic/linux-aws-fips: 4.15.0-2005.5 -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: New Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: Invalid Status in Kernel SRU Workflow verification-testing series: New 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: 1852270 packages: lrm: linux-restricted-modules-aws-fips main: linux-aws-fips meta: linux-meta-aws-fips signed: linux-signed-aws-fips phase: Ready for Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:21 UTC reason: promote-to-proposed: Pending -- ready for review variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852268/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852230] Re: eoan/linux-oracle: 5.3.0-1007.8 -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) => Łukasz Zemczak (sil2100) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852230 Title: eoan/linux-oracle: 5.3.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:11 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853085] Re: Problem during installing anything
Thanks for taking the time to report this bug and helping to make Ubuntu better. We appreciate the difficulties you are facing, but this appears to be a "regular" (non-security) bug. I have unmarked it as a security issue since this bug does not show evidence of allowing attackers to cross privilege boundaries nor directly cause loss of data/privacy. Please feel free to report any other bugs you may find. ** Information type changed from Private Security to Public -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-signed in Ubuntu. https://bugs.launchpad.net/bugs/1853085 Title: Problem during installing anything Status in linux-signed package in Ubuntu: New Bug description: dpkg: error processing package linux-image-4.15.0-70-generic (--configure): installed linux-image-4.15.0-70-generic package post-installation script subprocess returned error exit status 1 Errors were encountered while processing: linux-image-4.15.0-70-generic E: Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed/+bug/1853085/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852230] Re: eoan/linux-oracle: 5.3.0-1007.8 -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: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle - phase: Ready for Promote to Proposed - phase-changed: Monday, 18. November 2019 05:31 UTC + phase: Promote to Proposed + phase-changed: Tuesday, 19. November 2019 18:11 UTC reason: - promote-to-proposed: Stalled -- ready for review + promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1852230 Title: eoan/linux-oracle: 5.3.0-1007.8 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: In Progress 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-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1852232 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Promote to Proposed phase-changed: Tuesday, 19. November 2019 18:11 UTC reason: promote-to-proposed: Stalled -- review in progress trackers: bionic/linux-oracle-5.3: bug 1852229 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852230/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1791427] Re: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th
Yes, but now your battery will die in like 4 hours in sleep mode, because you're not getting S3 mode. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1791427 Title: Touchpad and/or trackpoint stop working after S3 suspend on Lenovo X1 Carbon 6th Status in linux package in Ubuntu: Triaged Bug description: Ubuntu 18.04.1 Terminology in case we use different terms: touchpad - just the rectangular touch-sensitive surface below the keyboard (xinput lists it as Synaptics TM3288-011) trackpoint - the red thingy built into the keyboard + 3 physical buttons below the keyboard (trackpoint and buttons are integrated together; listed in xinput as TPPS/2 Elan TrackPoint) On September 7th, 2018, Lenovo has issued a BIOS update (v1.30), which enables proper S3 deep sleep state - users no longer have to patch DSDT tables to get it. It can be enabled in the BIOS settings. In X1 carbon 6th generation models that have NFC, when laptop wakes from suspend by opening the lid, in most cases both touchpad and trackpoint stop working completely. They are also no longer listed when running xinput command. Sometimes just one of them stops working, usually the trackpoint. In some rare cases it is possible to bring them back by using these commands: echo -n none > /sys/devices/platform/i8042/serio1/drvctl echo -n reconnect > /sys/devices/platform/i8042/serio1/drvctl rmmod psmouse modprobe psmouse These worked properly when waking up from S2Idle sleep state (had these in a script that runs after waking the machine from suspend), but with S3 deep sleep these rarely work and the only way to bring back touchpad and/or trackpoint is turning off the machine and turning it on (restart does not help). I could not find any pattern that would show when the input devices stop working or start working again using the commands mentioned above. It's completely random from my perspective. This is happening on the standard issue 4.15.0-33-generic kernel that shipped with my Ubuntu 18.04 (with updates), as well as with newer mainline kernels, such as the newest point versions of 4.17, 4.18 and 4.19 RC2. This happens regardless of whether "blacklist i2c_i801" is commented out in /etc/modprobe.d/blacklist.conf or not. It happens regardless of whether "psmouse.synaptics_intertouch=1" is passed as grub parameter. Presence of TLP does not make it better, nor worse. It appears that non-NFC models are not affected. I know at least one Arch Linux user who has the exact same model, but without this issue. I'm using synaptics driver (no libinput installed), he uses libinput and doesn't have synaptics, if that information is of any use. Libinput does not seem to help. This forum thread also has more details from users who updated their BIOS to get S3 suspend: https://forums.lenovo.com/t5/Linux- Discussion/X1-Carbon-Gen-6-cannot-enter-deep-sleep-S3-state-aka- Suspend-to/td-p/3998182/page/27 Another related thread: https://bbs.archlinux.org/viewtopic.php?id=236367 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-33-generic 4.15.0-33.36 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 Uname: Linux 4.15.0-33-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.3 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/pcmC0D0p: maciej 2651 F...m pulseaudio /dev/snd/controlC0: maciej 2651 F pulseaudio CurrentDesktop: i3 Date: Sat Sep 8 13:45:43 2018 HibernationDevice: RESUME=UUID=3116dcb0-d91e-4b2a-8166-43b7a9a9d36e InstallationDate: Installed on 2018-07-21 (49 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 13d3:56b2 IMC Networks Bus 001 Device 002: ID 04b4:0060 Cypress Semiconductor Corp. Wireless optical mouse Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: LENOVO 20KH006KPB ProcFB: 0 EFI VGA 1 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-33-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash psmouse.synaptics_intertouch=1 vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/31/2018 dmi.bios.vendor: LENOVO dmi.bios.version: N23ET55W (1.30 ) dmi.board.asset.tag: Not Available dmi.board.name: 20KH006KPB dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO
[Kernel-packages] [Bug 1852637] Re: backport DIMLIB (lib/dim/) to pre-5.2 kernels
** Description changed: The mellanox and broadcom drivers contained a "dynamic interrupt moderation" feature (as early as v5.0) which was broken out into a common kernel library 'DIMLIB' in lib/dim/ circa mainline v5.2. Backported drivers may now need DIMLIB to be available in pre-5.2 kernels (specifically, the latest upstream version of - net/ethernet/amazon/ena does). + net/ethernet/amazon/ena does: see bug 1853180). For Disco: - Apply all the mainline commits from v5.2 which extract DIMLIB from mellanox/broadcom and wire those drivers to use DIMLIB (plus a few later DIMLIB fixes). I.e. make Disco work the same as > 5.2 kernels; no significant functional change to those drivers. + Apply all the mainline commits from v5.2 which extract DIMLIB from mellanox/broadcom and wire those drivers to use DIMLIB (plus a few later DIMLIB fixes). I.e. make Disco work the same as > 5.2 kernels; no significant functional change to those drivers. For Bionic and Xenial: - Import the lib/dim/ directory from mainline (plus a couple porting prerequisites), but do *not* make mellanox/broadcom use it. I.e. no functional change at all. + Import the lib/dim/ directory from mainline (plus a couple porting prerequisites), but do *not* make mellanox/broadcom use it. I.e. no functional change at all. --- The mainline commits for Disco: (newest first) f8be17b81d44 lib/dim: Fix -Wunused-const-variable warnings f06d0ca45827 linux/dim: Fix overflow in dim calculation f4915455dcf0 linux/dim: Implement RDMA adaptive moderation (DIM) 398c2b05bbee linux/dim: Add completions count to dim_sample 4f75da3666c0 linux/dim: Move implementation to .c files 8960b38932be linux/dim: Rename externally used net_dim members e5b6ab02d7aa linux/dim: Rename net_dim_sample() to net_dim_update_sample() c002bd529d71 linux/dim: Rename externally exposed macros 449986ea9241 linux/dim: Remove "net" prefix from internal DIM members 0e58983de0d8 linux/dim: Move logic to dim.h -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1852637 Title: backport DIMLIB (lib/dim/) to pre-5.2 kernels Status in linux package in Ubuntu: In Progress Status in linux source package in Xenial: In Progress Status in linux source package in Bionic: In Progress Status in linux source package in Disco: In Progress Bug description: The mellanox and broadcom drivers contained a "dynamic interrupt moderation" feature (as early as v5.0) which was broken out into a common kernel library 'DIMLIB' in lib/dim/ circa mainline v5.2. Backported drivers may now need DIMLIB to be available in pre-5.2 kernels (specifically, the latest upstream version of net/ethernet/amazon/ena does: see bug 1853180). For Disco: Apply all the mainline commits from v5.2 which extract DIMLIB from mellanox/broadcom and wire those drivers to use DIMLIB (plus a few later DIMLIB fixes). I.e. make Disco work the same as > 5.2 kernels; no significant functional change to those drivers. For Bionic and Xenial: Import the lib/dim/ directory from mainline (plus a couple porting prerequisites), but do *not* make mellanox/broadcom use it. I.e. no functional change at all. --- The mainline commits for Disco: (newest first) f8be17b81d44 lib/dim: Fix -Wunused-const-variable warnings f06d0ca45827 linux/dim: Fix overflow in dim calculation f4915455dcf0 linux/dim: Implement RDMA adaptive moderation (DIM) 398c2b05bbee linux/dim: Add completions count to dim_sample 4f75da3666c0 linux/dim: Move implementation to .c files 8960b38932be linux/dim: Rename externally used net_dim members e5b6ab02d7aa linux/dim: Rename net_dim_sample() to net_dim_update_sample() c002bd529d71 linux/dim: Rename externally exposed macros 449986ea9241 linux/dim: Remove "net" prefix from internal DIM members 0e58983de0d8 linux/dim: Move logic to dim.h To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852637/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853180] [NEW] update ENA driver for DIMLIB dynamic interrupt moderation
Public bug reported:
Update the Amazon ENA driver to latest mainline version with dynamic
interrupt moderation supplied by DIMLIB, plus a couple of pending fixes
from the netdev mailing list.
Note: For {Xenial,Bionic,Disco}, this needs bug 1852637 ("backport
DIMLIB (lib/dim/) to pre-5.2 kernels") as a prerequisite.
** Affects: linux (Ubuntu)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Affects: linux (Ubuntu Xenial)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Affects: linux (Ubuntu Bionic)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Affects: linux (Ubuntu Disco)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Affects: linux (Ubuntu Eoan)
Importance: Undecided
Assignee: Kamal Mostafa (kamalmostafa)
Status: In Progress
** Also affects: linux (Ubuntu Bionic)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Eoan)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Xenial)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Disco)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Xenial)
Status: New => In Progress
** Changed in: linux (Ubuntu Bionic)
Status: New => In Progress
** Changed in: linux (Ubuntu Disco)
Status: New => In Progress
** Changed in: linux (Ubuntu Eoan)
Status: New => In Progress
** Changed in: linux (Ubuntu Xenial)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu Bionic)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu Disco)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
** Changed in: linux (Ubuntu Eoan)
Assignee: (unassigned) => Kamal Mostafa (kamalmostafa)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1853180
Title:
update ENA driver for DIMLIB dynamic interrupt moderation
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Xenial:
In Progress
Status in linux source package in Bionic:
In Progress
Status in linux source package in Disco:
In Progress
Status in linux source package in Eoan:
In Progress
Bug description:
Update the Amazon ENA driver to latest mainline version with dynamic
interrupt moderation supplied by DIMLIB, plus a couple of pending
fixes from the netdev mailing list.
Note: For {Xenial,Bionic,Disco}, this needs bug 1852637 ("backport
DIMLIB (lib/dim/) to pre-5.2 kernels") as a prerequisite.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853180/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852335] Re: Xenial update: 4.4.201 upstream stable release
Also of note:
* ("perf/x86/amd/ibs: Fix reading of the IBS OpData register and thus
precise RIP validity") modified a routine that was expected to be in
"arch/x86/kernel/cpu/perf_event_amd_ibs.c" but was found in
"arch/x86/events/amd/ibs.c"
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1852335
Title:
Xenial update: 4.4.201 upstream stable release
Status in linux package in Ubuntu:
Invalid
Status in linux source package in Xenial:
In Progress
Bug description:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
* CDC-NCM: handle incomplete transfer of MTU
* net: fix data-race in neigh_event_send()
* NFC: fdp: fix incorrect free object
* NFC: st21nfca: fix double free
* qede: fix NULL pointer deref in __qede_remove()
* nfc: netlink: fix double device reference drop
* ALSA: bebob: fix to detect configured source of sampling clock for
Focusrite Saffire Pro i/o series
* ALSA: hda/ca0132 - Fix possible workqueue stall
* mm, vmstat: hide /proc/pagetypeinfo from normal users
* dump_stack: avoid the livelock of the dump_lock
* perf tools: Fix time sorting
* drm/radeon: fix si_enable_smc_cac() failed issue
* ceph: fix use-after-free in __ceph_remove_cap()
* iio: imu: adis16480: make sure provided frequency is positive
* netfilter: nf_tables: Align nft_expr private data to 64-bit
* netfilter: ipset: Fix an error code in ip_set_sockfn_get()
* can: usb_8dev: fix use-after-free on disconnect
* can: c_can: c_can_poll(): only read status register after status IRQ
* can: peak_usb: fix a potential out-of-sync while decoding packets
* can: gs_usb: gs_can_open(): prevent memory leak
* can: peak_usb: fix slab info leak
* drivers: usb: usbip: Add missing break statement to switch
* configfs: fix a deadlock in configfs_symlink()
* PCI: tegra: Enable Relaxed Ordering only for Tegra20 & Tegra30
* scsi: qla2xxx: fixup incorrect usage of host_byte
* scsi: lpfc: Honor module parameter lpfc_use_adisc
* ipvs: move old_secure_tcp into struct netns_ipvs
* bonding: fix unexpected IFF_BONDING bit unset
* usb: fsl: Check memory resource before releasing it
* usb: gadget: udc: atmel: Fix interrupt storm in FIFO mode.
* usb: gadget: composite: Fix possible double free memory bug
* usb: gadget: configfs: fix concurrent issue between composite APIs
* perf/x86/amd/ibs: Fix reading of the IBS OpData register and thus precise
RIP validity
* USB: Skip endpoints with 0 maxpacket length
* scsi: qla2xxx: stop timer in shutdown path
* net: hisilicon: Fix "Trying to free already-free IRQ"
* NFSv4: Don't allow a cached open with a revoked delegation
* igb: Fix constant media auto sense switching when no cable is connected
* e1000: fix memory leaks
* can: flexcan: disable completely the ECC mechanism
* mm/filemap.c: don't initiate writeback if mapping has no dirty pages
* cgroup,writeback: don't switch wbs immediately on dead wbs if the memcg is
dead
* net: prevent load/store tearing on sk->sk_stamp
* Linux 4.4.201
* UBUNTU: upstream stable to v4.4.201
4.4.201 upstream stable release
from git://git.kernel.org/
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1852335/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1853177] [NEW] Xenial update: 4.4.202 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.202 upstream stable release from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux (Ubuntu Xenial) Importance: Medium Assignee: Connor Kuehl (connork) Status: In Progress ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid ** Changed in: linux (Ubuntu Xenial) Status: New => In Progress ** Changed in: linux (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Xenial) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1853177 Title: Xenial update: 4.4.202 upstream stable release Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: 4.4.202 upstream stable release from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1853177/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1806437]
For the stats i have it as well - came accross it, while troubleshooting freeze when shutting down opensuse : uname -a Linux linux-xnik.site 5.3.7-1-default #1 SMP Mon Oct 21 06:03:17 UTC 2019 (3eea5a9) x86_64 x86_64 x86_64 GNU/Linux But has had it for since some versions back (OMG i see further down i have some cleaning up to do ...: Not sure it is related, but if this content can help resolve this bug, then here goes : [0.262034] MDS CPU bug present and SMT on, data leak possible. See https://www.kernel.org/doc/html/latest/admin-guide/hw-vuln/mds.html for more details. [0.262034] #2 [0.264714] #3 [0.323178] ENERGY_PERF_BIAS: Set to 'normal', was 'performance' [2.118397] ata1.00: NCQ Send/Recv Log not supported [2.120828] ata1.00: NCQ Send/Recv Log not supported [3.643730] acpi PNP0C14:01: duplicate WMI GUID 05901221-D566-11D1-B2F0-00A0C9062910 (first instance was on PNP0C14:00) [5.938526] printk: systemd: 24 output lines suppressed due to ratelimiting [6.955571] ACPI: Deprecated procfs I/F for AC is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared [7.021378] battery: ACPI: Deprecated procfs I/F for battery is loaded, please retry with CONFIG_ACPI_PROCFS_POWER cleared [7.058723] ACPI Warning: SystemIO range 0x0428-0x042F conflicts with OpRegion 0x0400-0x047F (\_SB.PCI0.LPC.PMIO) (20190703/utaddress-204) [7.058733] ACPI Warning: SystemIO range 0x0540-0x054F conflicts with OpRegion 0x0500-0x057F (\_SB.PCI0.LPC.LPIO) (20190703/utaddress-204) [7.058738] ACPI Warning: SystemIO range 0x0530-0x053F conflicts with OpRegion 0x0500-0x057F (\_SB.PCI0.LPC.LPIO) (20190703/utaddress-204) [7.058742] ACPI Warning: SystemIO range 0x0500-0x052F conflicts with OpRegion 0x0500-0x057F (\_SB.PCI0.LPC.LPIO) (20190703/utaddress-204) [7.058745] lpc_ich: Resource conflict(s) found affecting gpio_ich [9.382663] uvcvideo 1-1.6:1.0: Entity type for entity Extension 3 was not initialized! [9.382667] uvcvideo 1-1.6:1.0: Entity type for entity Processing 2 was not initialized! [9.382669] uvcvideo 1-1.6:1.0: Entity type for entity Camera 1 was not initialized! [9.538736] Bluetooth: hci0: unexpected event for opcode 0xfc2f [ 881.086257] WARNING: CPU: 2 PID: 162 at fs/ext4/inode.c:3941 ext4_set_page_dirty+0x3e/0x50 [ 881.086261] Modules linked in: binfmt_misc fuse ccm rfcomm af_packet bnep uvcvideo videobuf2_vmalloc videobuf2_memops videobuf2_v4l2 videobuf2_common videodev btusb btrtl mc btbcm btintel bluetooth ecdh_generic ecc scsi_transport_iscsi snd_seq snd_seq_device dmi_sysfs intel_rapl_msr intel_rapl_common x86_pkg_temp_thermal intel_powerclamp coretemp kvm_intel kvm iwlmvm mac80211 irqbypass msr crct10dif_pclmul snd_hda_codec_hdmi crc32_pclmul libarc4 snd_hda_codec_conexant snd_hda_codec_generic iwlwifi mei_wdt mei_hdcp ghash_clmulni_intel iTCO_wdt iTCO_vendor_support snd_hda_intel snd_hda_codec aesni_intel snd_hda_core cfg80211 aes_x86_64 crypto_simd snd_hwdep cryptd snd_pcm glue_helper thinkpad_acpi joydev pcspkr ledtrig_audio mei_me wmi_bmof i2c_i801 snd_timer e1000e lpc_ich rfkill mei snd battery soundcore ac thermal button i915 sdhci_pci cqhci i2c_algo_bit sdhci ehci_pci drm_kms_helper ehci_hcd usbcore mmc_core syscopyarea sysfillrect sysimgblt fb_sys_fops crc32c_intel drm serio_raw wmi [ 881.086338] video sg dm_multipath dm_mod scsi_dh_rdac scsi_dh_emc scsi_dh_alua [ 881.086352] CPU: 2 PID: 162 Comm: kworker/u16:4 Not tainted 5.3.7-1-default #1 openSUSE Tumbleweed (unreleased) [ 881.086354] Hardware name: LENOVO 4291CF7/4291CF7, BIOS 8DET73WW (1.43 ) 10/12/2016 [ 881.086489] Workqueue: i915 __i915_gem_free_work [i915] [ 881.086501] RIP: 0010:ext4_set_page_dirty+0x3e/0x50 [ 881.086507] Code: 48 8b 00 a8 01 75 16 48 8b 57 08 48 8d 42 ff 83 e2 01 48 0f 44 c7 48 8b 00 a8 08 74 0d 48 8b 07 f6 c4 20 74 0f e9 d2 4b f8 ff <0f> 0b 48 8b 07 f6 c4 20 75 f1 0f 0b e9 c1 4b f8 ff 90 66 66 66 66 [ 881.086510] RSP: 0018:b5fec02a3d98 EFLAGS: 00010246 [ 881.086513] RAX: 00282036 RBX: 96fe89c01000 RCX: [ 881.086516] RDX: RSI: 0003d7b1 RDI: fca3cf0d7380 [ 881.086518] RBP: fca3cf0d7380 R08: 0003d7b1 R09: c06ef801 [ 881.086520] R10: 96fe85a3d680 R11: R12: 003c35ce [ 881.086522] R13: 96fe62601800 R14: 96fe8b3909e0 R15: [ 881.086526] FS: () GS:96fe8e28() knlGS: [ 881.086529] CS: 0010 DS: ES: CR0: 80050033 [ 881.086531] CR2: 7efd3cd9dff0 CR3: 38e0a001 CR4: 000606e0 [ 881.086534] Call Trace: [ 881.086645] i915_gem_userptr_put_pages+0x13f/0x1c0 [i915] [ 881.086749]
[Kernel-packages] [Bug 943263] Re: PC display will not turn on with Llano APUs connected to the VGA port
** Changed in: linux Status: Confirmed => Unknown ** Bug watch added: gitlab.freedesktop.org/drm/amd/issues #231 https://gitlab.freedesktop.org/drm/amd/issues/231 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/943263 Title: PC display will not turn on with Llano APUs connected to the VGA port Status in Linux: Unknown Status in linux package in Ubuntu: Fix Released Bug description: The PC has a Llano A6-3650 APU with a display connected to the VGA port, but the display turns off when plymouth should appear, thus making installation from liveCD/USB impossible. Ubuntu starts up, as I can hear the login sound, but nothing is visible. Filed separately, as requested in bug #825777, as this one is about a PC, and the other one is about laptops. --- Ubuntu Bug Squad volunteer triager http://wiki.ubuntu.com/BugSquad ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: linux-image-3.0.0-16-generic-pae 3.0.0-16.28 ProcVersionSignature: Ubuntu 3.0.0-16.28-generic-pae 3.0.17 Uname: Linux 3.0.0-16-generic-pae i686 NonfreeKernelModules: fglrx AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24. ApportVersion: 1.23-0ubuntu4 Architecture: i386 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: evfool 1592 F pulseaudio CRDA: Error: [Errno 2] No such file or directory Card0.Amixer.info: Card hw:0 'Generic'/'HD-Audio Generic at 0xfe01c000 irq 52' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 4 Simple ctrls : 1 Card0.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined penum Playback channels: Mono Mono: Playback [on] Card1.Amixer.info: Card hw:1 'Generic_1'/'HD-Audio Generic at 0xfe02 irq 16' Mixer name : 'Realtek ALC889' Components : 'HDA:10ec0889,1458a132,0014' Controls : 37 Simple ctrls : 22 CheckboxSubmission: 589b7562703a9b18f8c7bdabc7186c59 CheckboxSystem: 4ed15c40009aa6f7770f606350a390a2 Date: Wed Feb 29 15:48:11 2012 HibernationDevice: RESUME=UUID=1b7f7f1a-53b1-4d7a-95df-6862c754e92e InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1) IwConfig: lono wireless extensions. eth0 no wireless extensions. MachineType: Gigabyte Technology Co., Ltd. GA-A75M-UD2H ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.0.0-16-generic-pae root=UUID=9cafb3fa-9832-4949-bf09-039fbc4a9df6 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-3.0.0-16-generic-pae N/A linux-backports-modules-3.0.0-16-generic-pae N/A linux-firmware1.60 RfKill: SourcePackage: linux UpgradeStatus: Upgraded to oneiric on 2011-11-21 (100 days ago) WifiSyslog: dmi.bios.date: 11/03/2011 dmi.bios.vendor: Award Software International, Inc. dmi.bios.version: F5 dmi.board.name: GA-A75M-UD2H dmi.board.vendor: Gigabyte Technology Co., Ltd. dmi.board.version: x.x dmi.chassis.type: 3 dmi.chassis.vendor: Gigabyte Technology Co., Ltd. dmi.modalias: dmi:bvnAwardSoftwareInternational,Inc.:bvrF5:bd11/03/2011:svnGigabyteTechnologyCo.,Ltd.:pnGA-A75M-UD2H:pvr:rvnGigabyteTechnologyCo.,Ltd.:rnGA-A75M-UD2H:rvrx.x:cvnGigabyteTechnologyCo.,Ltd.:ct3:cvr: dmi.product.name: GA-A75M-UD2H dmi.sys.vendor: Gigabyte Technology Co., Ltd. To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/943263/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852281] Re: trusty/linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Holding before Packaging - phase-changed: Tuesday, 12. November 2019 14:47 UTC + phase: Ready for Packaging + phase-changed: Tuesday, 19. November 2019 17:05 UTC reason: - prepare-package: Holding -- waiting for master bug + prepare-package: Pending -- version not specified 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/1852281 Title: trusty/linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-signing-to-proposed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852282 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Tuesday, 19. November 2019 17:05 UTC reason: prepare-package: Pending -- version not specified variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852281/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1852282] Re: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-meta Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Committed ** Changed in: kernel-sru-workflow/prepare-package-signed Status: Fix Committed => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure - phase: Packaging - phase-changed: Tuesday, 19. November 2019 16:08 UTC + phase: Holding before Promote to Proposed + phase-changed: Tuesday, 19. November 2019 17:02 UTC reason: - prepare-package: Pending -- package not yet uploaded - prepare-package-meta: Pending -- package not yet uploaded - prepare-package-signed: Pending -- package not yet uploaded + promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 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/1852282 Title: xenial/linux-azure: 4.15.0-1064.69 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1852289 packages: main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Holding before Promote to Proposed phase-changed: Tuesday, 19. November 2019 17:02 UTC reason: promote-to-proposed: Ongoing -- builds not complete in ppa main:building,meta:depwait,signed:depwait trackers: trusty/linux-azure: bug 1852281 xenial/linux-azure-edge: bug 1852280 xenial/linux-azure/azure-kernel: bug 1852279 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1852282/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
