[Kernel-packages] [Bug 1820530] Re: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit
** Patch added: "0002-UBUNTU-fix-missing-modules.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+attachment/5276122/+files/0002-UBUNTU-fix-missing-modules.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820530 Title: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit Status in linux package in Ubuntu: Expired Bug description: Hi, Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf counterpart ? This will follow the debian kernel config. Here is the list of config that should be enabled to have optimal platform support: CONFIG_ARCH_MESON=y CONFIG_MESON_SM=y CONFIG_DWMAC_MESON=m CONFIG_MESON_GXL_PHY=m CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPICC=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_PINCTRL_MESON_GXBB=y CONFIG_PINCTRL_MESON_GXL=y CONFIG_PINCTRL_MESON_AXG=y CONFIG_PINCTRL_MESON_AXG_PMX=y CONFIG_PINCTRL_MESON_G12A=y CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_IR_MESON=m CONFIG_VIDEO_MESON_AO_CEC=m CONFIG_DRM_MESON=m CONFIG_DRM_MESON_DW_HDMI=m CONFIG_MMC_MESON_GX=m CONFIG_MESON_CANVAS=m CONFIG_MESON_GX_SOCINFO=y CONFIG_MESON_GX_PM_DOMAINS=y CONFIG_MESON_SARADC=m CONFIG_PWM_MESON=m CONFIG_MESON_IRQ_GPIO=y CONFIG_RESET_MESON=m CONFIG_PHY_MESON_GXL_USB2=m CONFIG_PHY_MESON_GXL_USB3=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820530] Re: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit
** Patch added: "0001-UBUNTU-Config-enable-ARCH_MESON.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+attachment/5276121/+files/0001-UBUNTU-Config-enable-ARCH_MESON.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820530 Title: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit Status in linux package in Ubuntu: Expired Bug description: Hi, Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf counterpart ? This will follow the debian kernel config. Here is the list of config that should be enabled to have optimal platform support: CONFIG_ARCH_MESON=y CONFIG_MESON_SM=y CONFIG_DWMAC_MESON=m CONFIG_MESON_GXL_PHY=m CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPICC=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_PINCTRL_MESON_GXBB=y CONFIG_PINCTRL_MESON_GXL=y CONFIG_PINCTRL_MESON_AXG=y CONFIG_PINCTRL_MESON_AXG_PMX=y CONFIG_PINCTRL_MESON_G12A=y CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_IR_MESON=m CONFIG_VIDEO_MESON_AO_CEC=m CONFIG_DRM_MESON=m CONFIG_DRM_MESON_DW_HDMI=m CONFIG_MMC_MESON_GX=m CONFIG_MESON_CANVAS=m CONFIG_MESON_GX_SOCINFO=y CONFIG_MESON_GX_PM_DOMAINS=y CONFIG_MESON_SARADC=m CONFIG_PWM_MESON=m CONFIG_MESON_IRQ_GPIO=y CONFIG_RESET_MESON=m CONFIG_PHY_MESON_GXL_USB2=m CONFIG_PHY_MESON_GXL_USB3=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
Source package with fix in: https://people.canonical.com/~ppisati/lp1837073/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837073] Re: linux 5.2.0-8.9 disabled backlight on s390x.
** Attachment added: "dcci-driver-linux_0.3.2-2_0.3.2-2ubuntu1.diff.gz" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1837073/+attachment/5278043/+files/dcci-driver-linux_0.3.2-2_0.3.2-2ubuntu1.diff.gz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1837073 Title: linux 5.2.0-8.9 disabled backlight on s390x. Status in ddcci-driver-linux package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: Looks like ddcci-driver-linux started to fail on s390x with the switch from kernel 5.0.0-21-generic to 5.2.0-8-generic http://autopkgtest.ubuntu.com/packages/d/ddcci-driver-linux/eoan/s390x According to changelog and diff: - [Config] CONFIG_BACKLIGHT_CLASS_DEVICE=n on s390x from Seth Forshee. According to the build log of ddci backlight rm: cannot remove '.tmp_versions/ddcci-backlight.mod': No such file or directory Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == Makefile:227: = WARNING Makefile:228: 'SUBDIRS' will be removed after Linux 5.3 Makefile:229: Please use 'M=' or 'KBUILD_EXTMOD' instead Makefile:230: == ERROR: "devm_backlight_device_register" [/var/lib/dkms/ddcci/0.3.2/build/ddcci-backlight/ddcci-backlight.ko] undefined! make[3]: *** [scripts/Makefile.modpost:91: __modpost] Error 1 make[2]: *** [Makefile:1628: modules] Error 2 make[1]: *** [Makefile:37: ddcci-backlight.ko] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ddcci-driver-linux/+bug/1837073/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820530] Re: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit
** Description changed: + Impact: + + Enable ARCH_MESON for arm64 as we already do in armhf. + + Fix: + + Apply the attached patches. + + How to test: + + Boot the patched kernel on a support MESON board. + + Regression potential: + + Low - the patch is enabling an architecture alreay enabled in upstream + defconfig for a while. + + -- + + Hi, Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf counterpart ? This will follow the debian kernel config. Here is the list of config that should be enabled to have optimal platform support: CONFIG_ARCH_MESON=y CONFIG_MESON_SM=y CONFIG_DWMAC_MESON=m CONFIG_MESON_GXL_PHY=m CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPICC=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_PINCTRL_MESON_GXBB=y CONFIG_PINCTRL_MESON_GXL=y CONFIG_PINCTRL_MESON_AXG=y CONFIG_PINCTRL_MESON_AXG_PMX=y CONFIG_PINCTRL_MESON_G12A=y CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_IR_MESON=m CONFIG_VIDEO_MESON_AO_CEC=m CONFIG_DRM_MESON=m CONFIG_DRM_MESON_DW_HDMI=m CONFIG_MMC_MESON_GX=m CONFIG_MESON_CANVAS=m CONFIG_MESON_GX_SOCINFO=y CONFIG_MESON_GX_PM_DOMAINS=y CONFIG_MESON_SARADC=m CONFIG_PWM_MESON=m CONFIG_MESON_IRQ_GPIO=y CONFIG_RESET_MESON=m CONFIG_PHY_MESON_GXL_USB2=m CONFIG_PHY_MESON_GXL_USB3=m -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820530 Title: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit Status in linux package in Ubuntu: Expired Bug description: Impact: Enable ARCH_MESON for arm64 as we already do in armhf. Fix: Apply the attached patches. How to test: Boot the patched kernel on a support MESON board. Regression potential: Low - the patch is enabling an architecture alreay enabled in upstream defconfig for a while. -- Hi, Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf counterpart ? This will follow the debian kernel config. Here is the list of config that should be enabled to have optimal platform support: CONFIG_ARCH_MESON=y CONFIG_MESON_SM=y CONFIG_DWMAC_MESON=m CONFIG_MESON_GXL_PHY=m CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPICC=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_PINCTRL_MESON_GXBB=y CONFIG_PINCTRL_MESON_GXL=y CONFIG_PINCTRL_MESON_AXG=y CONFIG_PINCTRL_MESON_AXG_PMX=y CONFIG_PINCTRL_MESON_G12A=y CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_IR_MESON=m CONFIG_VIDEO_MESON_AO_CEC=m CONFIG_DRM_MESON=m CONFIG_DRM_MESON_DW_HDMI=m CONFIG_MMC_MESON_GX=m CONFIG_MESON_CANVAS=m CONFIG_MESON_GX_SOCINFO=y CONFIG_MESON_GX_PM_DOMAINS=y CONFIG_MESON_SARADC=m CONFIG_PWM_MESON=m CONFIG_MESON_IRQ_GPIO=y CONFIG_RESET_MESON=m CONFIG_PHY_MESON_GXL_USB2=m CONFIG_PHY_MESON_GXL_USB3=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837209] Re: Splash screen fails to display on recent pi core18 images
Last working image / kernel version? First broken image / kernel version? So we can compare the two. -- 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/1837209 Title: Splash screen fails to display on recent pi core18 images Status in Snappy: New Status in linux-raspi2 package in Ubuntu: New Bug description: The current core18 image [1] for the raspberry pi fails to display the "Core" splash screen on boot. This is because psplash fails to open the /dev/fb0 framebuffer device, because it doesn't exist. This appears to be due to a lack of supporting kernel modules in the initrd.img (fb_sys_fops, drm, vc4, etc.) which were formerly present but are missing from the version I'm testing (pi-kernel 4.15.0-1041.44, snap rev 42). Steps to reproduce: * Flash the image to a uSD card and boot the pi with it (preferably with a serial console attached). * Note screen remains black instead of displaying the familiar "Core" text under an Ubuntu logo. * If serial console is attached, note "Error opening /dev/fb0" in the output shortly after u-boot starts the kernel; this is output from psplash failing [1] http://cdimage.ubuntu.com/ubuntu-core/18/current/ubuntu- core-18-armhf+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1837209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837209] Re: Splash screen fails to display on recent pi core18 images
If you remove the dtoverlay line (just tested it) and it works fine during boot (before root is mounted), it means initrd has all necessary modules to make it work, so it's not like initrd is missing something. -- 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/1837209 Title: Splash screen fails to display on recent pi core18 images Status in Snappy: New Status in linux-raspi2 package in Ubuntu: New Bug description: The current core18 image [1] for the raspberry pi fails to display the "Core" splash screen on boot. This is because psplash fails to open the /dev/fb0 framebuffer device, because it doesn't exist. This appears to be due to a lack of supporting kernel modules in the initrd.img (fb_sys_fops, drm, vc4, etc.) which were formerly present but are missing from the version I'm testing (pi-kernel 4.15.0-1041.44, snap rev 42). Steps to reproduce: * Flash the image to a uSD card and boot the pi with it (preferably with a serial console attached). * Note screen remains black instead of displaying the familiar "Core" text under an Ubuntu logo. * If serial console is attached, note "Error opening /dev/fb0" in the output shortly after u-boot starts the kernel; this is output from psplash failing [1] http://cdimage.ubuntu.com/ubuntu-core/18/current/ubuntu- core-18-armhf+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1837209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1837209] Re: Splash screen fails to display on recent pi core18 images
Test kernel snap available here: https://people.canonical.com/~ppisati/lp1837209/pi- kernel_4.15.0-1041.44_armhf.snap and precooked image here: https://people.canonical.com/~ppisati/lp1837209/ubuntu- core-18-pi_lp1837209fix.img.xz -- 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/1837209 Title: Splash screen fails to display on recent pi core18 images Status in Snappy: New Status in linux-raspi2 package in Ubuntu: New Bug description: The current core18 image [1] for the raspberry pi fails to display the "Core" splash screen on boot. This is because psplash fails to open the /dev/fb0 framebuffer device, because it doesn't exist. This appears to be due to a lack of supporting kernel modules in the initrd.img (fb_sys_fops, drm, vc4, etc.) which were formerly present but are missing from the version I'm testing (pi-kernel 4.15.0-1041.44, snap rev 42). Steps to reproduce: * Flash the image to a uSD card and boot the pi with it (preferably with a serial console attached). * Note screen remains black instead of displaying the familiar "Core" text under an Ubuntu logo. * If serial console is attached, note "Error opening /dev/fb0" in the output shortly after u-boot starts the kernel; this is output from psplash failing [1] http://cdimage.ubuntu.com/ubuntu-core/18/current/ubuntu- core-18-armhf+raspi3.img.xz To manage notifications about this bug go to: https://bugs.launchpad.net/snappy/+bug/1837209/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841147] [NEW] linux: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841146 (bionic/linux-hwe-edge) -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.08.23-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.08.23-1 ** 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/kern
[Kernel-packages] [Bug 1841159] [NEW] eoan/linux: 5.2.0-14.15 -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1841158 (bionic/linux-hwe-edge) -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.08.23-2 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2019.08.23-2 ** 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.co
[Kernel-packages] [Bug 1841147] Re: linux: -proposed tracker
*** This bug is a duplicate of bug 1841159 *** https://bugs.launchpad.net/bugs/1841159 ** 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 - backports: bug 1841146 (bionic/linux-hwe-edge) - -- swm properties -- variant: debs ** This bug has been marked a duplicate of bug 1841159 linux: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1841147 Title: linux: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: New Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1841147/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841893] [NEW] Dragonboard fails to boot: hangs after SMMU init
Public bug reported: Impact: Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot: ... [1.856849] arm-smmu da.arm,smmu: probing hardware configuration... [1.859296] arm-smmu da.arm,smmu: SMMUv2 with: [1.865845] arm-smmu da.arm,smmu:stage 1 translation [1.870658] arm-smmu da.arm,smmu:address translation ops [1.876121] arm-smmu da.arm,smmu:non-coherent table walk [1.881936] arm-smmu da.arm,smmu:(IDR0.CTTW overridden by FW configuration) [1.887760] arm-smmu da.arm,smmu:stream matching with 4 register groups [1.895337] arm-smmu da.arm,smmu:2 context banks (0 stage-2 only) [1.902455] arm-smmu da.arm,smmu:Supported page sizes: 0x63315000 [1.908852] arm-smmu da.arm,smmu:Stage-1: 32-bit VA -> 36-bit IPA [hangs here] Fix: During the Ubuntu-snapdragon-4.15.0-1061.68, the qcom smmuv2 implementation was replaced with an upstream generic version that didn't explicit clocks, power requirements and early init via IOMMU_OF_DECLARE() - reverting the upstream patch, and reapplying the original qcom one fixes this hangs. How to test: Try to boot a patched kernel and see if it reaches userspace. Regression potential: None, since the current kernel version doesn't boot at all. ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New -- 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/1841893 Title: Dragonboard fails to boot: hangs after SMMU init Status in linux-snapdragon package in Ubuntu: New Bug description: Impact: Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot: ... [1.856849] arm-smmu da.arm,smmu: probing hardware configuration... [1.859296] arm-smmu da.arm,smmu: SMMUv2 with: [1.865845] arm-smmu da.arm,smmu:stage 1 translation [1.870658] arm-smmu da.arm,smmu:address translation ops [1.876121] arm-smmu da.arm,smmu:non-coherent table walk [1.881936] arm-smmu da.arm,smmu:(IDR0.CTTW overridden by FW configuration) [1.887760] arm-smmu da.arm,smmu:stream matching with 4 register groups [1.895337] arm-smmu da.arm,smmu:2 context banks (0 stage-2 only) [1.902455] arm-smmu da.arm,smmu:Supported page sizes: 0x63315000 [1.908852] arm-smmu da.arm,smmu:Stage-1: 32-bit VA -> 36-bit IPA [hangs here] Fix: During the Ubuntu-snapdragon-4.15.0-1061.68, the qcom smmuv2 implementation was replaced with an upstream generic version that didn't explicit clocks, power requirements and early init via IOMMU_OF_DECLARE() - reverting the upstream patch, and reapplying the original qcom one fixes this hangs. How to test: Try to boot a patched kernel and see if it reaches userspace. Regression potential: None, since the current kernel version doesn't boot at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1841893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1841893] Re: Dragonboard fails to boot: hangs after SMMU init
** Description changed: Impact: Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot: ... [1.856849] arm-smmu da.arm,smmu: probing hardware configuration... [1.859296] arm-smmu da.arm,smmu: SMMUv2 with: [1.865845] arm-smmu da.arm,smmu:stage 1 translation [1.870658] arm-smmu da.arm,smmu:address translation ops [1.876121] arm-smmu da.arm,smmu:non-coherent table walk [1.881936] arm-smmu da.arm,smmu:(IDR0.CTTW overridden by FW configuration) [1.887760] arm-smmu da.arm,smmu:stream matching with 4 register groups [1.895337] arm-smmu da.arm,smmu:2 context banks (0 stage-2 only) [1.902455] arm-smmu da.arm,smmu:Supported page sizes: 0x63315000 [1.908852] arm-smmu da.arm,smmu:Stage-1: 32-bit VA -> 36-bit IPA [hangs here] Fix: During the Ubuntu-snapdragon-4.15.0-1061.68, the qcom smmuv2 implementation was replaced with an upstream generic version that didn't - take into accout clocks and power requirements - reverting the upstream - patch, and reapplying the qcom one fixes this hangs. + explicit clocks, power requirements and early init via + IOMMU_OF_DECLARE() - reverting the upstream patch, and reapplying the + original qcom one fixes this hangs. How to test: Try to boot a patched kernel and see if it reaches userspace. Regression potential: None, since the current kernel version doesn't boot at all. ** Description changed: Impact: Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot: ... [1.856849] arm-smmu da.arm,smmu: probing hardware configuration... [1.859296] arm-smmu da.arm,smmu: SMMUv2 with: [1.865845] arm-smmu da.arm,smmu:stage 1 translation [1.870658] arm-smmu da.arm,smmu:address translation ops [1.876121] arm-smmu da.arm,smmu:non-coherent table walk [1.881936] arm-smmu da.arm,smmu:(IDR0.CTTW overridden by FW configuration) [1.887760] arm-smmu da.arm,smmu:stream matching with 4 register groups [1.895337] arm-smmu da.arm,smmu:2 context banks (0 stage-2 only) [1.902455] arm-smmu da.arm,smmu:Supported page sizes: 0x63315000 [1.908852] arm-smmu da.arm,smmu:Stage-1: 32-bit VA -> 36-bit IPA [hangs here] Fix: During the Ubuntu-snapdragon-4.15.0-1061.68, the qcom smmuv2 implementation was replaced with an upstream generic version that didn't explicit clocks, power requirements and early init via IOMMU_OF_DECLARE() - reverting the upstream patch, and reapplying the - original qcom one fixes this hangs. + original qcom patch that was dropped, fixes this hang. How to test: Try to boot a patched kernel and see if it reaches userspace. Regression potential: None, since the current kernel version doesn't boot at all. -- 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/1841893 Title: Dragonboard fails to boot: hangs after SMMU init Status in linux-snapdragon package in Ubuntu: New Bug description: Impact: Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot: ... [1.856849] arm-smmu da.arm,smmu: probing hardware configuration... [1.859296] arm-smmu da.arm,smmu: SMMUv2 with: [1.865845] arm-smmu da.arm,smmu:stage 1 translation [1.870658] arm-smmu da.arm,smmu:address translation ops [1.876121] arm-smmu da.arm,smmu:non-coherent table walk [1.881936] arm-smmu da.arm,smmu:(IDR0.CTTW overridden by FW configuration) [1.887760] arm-smmu da.arm,smmu:stream matching with 4 register groups [1.895337] arm-smmu da.arm,smmu:2 context banks (0 stage-2 only) [1.902455] arm-smmu da.arm,smmu:Supported page sizes: 0x63315000 [1.908852] arm-smmu da.arm,smmu:Stage-1: 32-bit VA -> 36-bit IPA [hangs here] Fix: During the Ubuntu-snapdragon-4.15.0-1061.68, the qcom smmuv2 implementation was replaced with an upstream generic version that didn't explicit clocks, power requirements and early init via IOMMU_OF_DECLARE() - reverting the upstream patch, and reapplying the original qcom patch that was dropped, fixes this hang. How to test: Try to boot a patched kernel and see if it reaches userspace. Regression potential: None, since the current kernel version doesn't boot at all. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1841893/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.ne
[Kernel-packages] [Bug 1841911] [NEW] Kernel crash during msm init (or during shutdown)
Public bug reported: Impact: Ubuntu-snapdragon-4.15.0-1061.68 stacktraces during boot around msm init: [8.113018] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 [8.131081] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops [msm]): -517 [8.138234] msm 1a0.mdss: master bind failed: -517 [8.145551] platform 1a01000.mdp: Dropping the link to 1ef.iommu [8.150545] iommu: Removing device 1a01000.mdp from group 1 [8.157051] [ cut here ] [8.162369] WARNING: CPU: 1 PID: 1316 at /build/linux-snapdragon-t5G9R3/linux-snapdragon-4.15.0/drivers/iommu/qcom_iommu.c:336 qcom_iommu_domain_free +0x74/0x88 [8.167166] Modules linked in: adv7511_drm cec rc_core msm(+) mdt_loader [8.181137] CPU: 1 PID: 1316 Comm: systemd-udevd Not tainted 4.15.0-1061-snapdragon #68-Ubuntu [8.188079] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) [8.196501] pstate: 6045 (nZCv daif +PAN -UAO) [8.203356] pc : qcom_iommu_domain_free+0x74/0x88 [8.207955] lr : qcom_iommu_domain_free+0x74/0x88 [8.212727] sp : 0cbeb680 [8.217412] x29: 0cbeb680 x28: 8000396d84b8 [8.220713] x27: 8000396d84b0 x26: 8000396d84c0 [8.226096] x25: 80003d057c10 x24: 8000396d8420 [8.231391] x23: 0003 x22: 80003ce40258 [8.236686] x21: 8203ad00 x20: 8203af30 [8.241981] x19: 8203af00 x18: [8.247275] x17: x16: 0004 [8.252570] x15: 09549c08 x14: 0720072007200720 [8.257866] x13: 0720072007200720 x12: 0720072007200720 [8.263161] x11: 09549e80 x10: 0871d340 [8.268456] x9 : 0720072007200720 x8 : 0005 [8.273751] x7 : 0720072d072d072d x6 : 014c [8.279046] x5 : 08610250 x4 : [8.284345] x3 : x2 : a59fa8ece8469a00 [8.289637] x1 : x0 : 0024 [8.294932] Call trace: [8.300227] qcom_iommu_domain_free+0x74/0x88 [8.302400] iommu_group_release+0x54/0x90 [8.306914] kobject_put+0x8c/0x1f0 [8.310905] kobject_del.part.0+0x3c/0x50 [8.314292] kobject_put+0x74/0x1f0 [8.318455] iommu_group_remove_device+0x10c/0x198 [8.321756] qcom_iommu_remove_device+0x58/0x70 [8.326617] iommu_bus_notifier+0xa8/0x120 [8.331045] notifier_call_chain+0x5c/0xa0 [8.335210] blocking_notifier_call_chain+0x64/0x88 [8.339294] device_del+0x234/0x368 [8.344066] platform_device_del.part.3+0x2c/0x98 [8.347539] platform_device_unregister+0x24/0x38 [8.352410] of_platform_device_destroy+0xb8/0xc0 [8.357087] device_for_each_child+0x58/0xb0 [8.361775] of_platform_depopulate+0x4c/0x68 [8.366350] msm_pdev_probe+0x2c4/0x388 [msm] [8.370369] platform_drv_probe+0x60/0xc0 [8.374707] driver_probe_device+0x2ec/0x458 [8.378701] __driver_attach+0xdc/0x128 [8.383042] bus_for_each_dev+0x78/0xd8 [8.386598] driver_attach+0x30/0x40 [8.390418] bus_add_driver+0x20c/0x2a8 [8.394237] driver_register+0x6c/0x110 [8.397797] __platform_driver_register+0x54/0x60 [8.401841] msm_drm_register+0x54/0x80 [msm] [8.406481] do_one_initcall+0x58/0x160 [8.410818] do_init_module+0x64/0x1d8 [8.414463] load_module+0x1378/0x15c8 [8.418282] SyS_finit_module+0x100/0x118 [8.422016] el0_svc_naked+0x30/0x34 [8.426095] ---[ end trace 800d0885aa276bfd ]--- Fix: During the Ubuntu-snapdragon-4.15.0-1061.68 cycle, we picked up one upstream patch that of_platform_depopulate() msm in case of probe deferral, but that patch triggers a WARN_ON() during the wind down of the IOMMU (and a kernel hang) - revert the ported stable patch that depopulates. How to test: Boot a patched kernel and check if that stracktrace shows up again. Regression: None, i'm reverting a patch that wasn't there before and clearly wasn't tested with our downstream BSP. ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New -- 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/1841911 Title: Kernel crash during msm init (or during shutdown) Status in linux-snapdragon package in Ubuntu: New Bug description: Impact: Ubuntu-snapdragon-4.15.0-1061.68 stacktraces during boot around msm init: [8.113018] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 [8.131081] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops [msm]): -517 [8.138234] msm 1a0.mdss: master bind failed: -517 [8.145551] platform 1a01000.mdp: Dropping the link to 1ef.iommu [8.150545] iommu: Removing device 1a01000.mdp from group 1 [8.157051] [ cut here ] [8.162369] WARNING: CPU: 1 PID: 1316 at
[Kernel-packages] [Bug 1841911] Re: Kernel crash during msm init (or during shutdown)
** Description changed: Impact: - Ubuntu-snapdragon-4.15.0-1061.68 stacktraces during boot around msm - init: + Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot around msm init. + Sometimes we get the following stack trace, or the boot completes and the board hangs during reboot: + ... [8.113018] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 [8.131081] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops [msm]): -517 [8.138234] msm 1a0.mdss: master bind failed: -517 [8.145551] platform 1a01000.mdp: Dropping the link to 1ef.iommu [8.150545] iommu: Removing device 1a01000.mdp from group 1 [8.157051] [ cut here ] [8.162369] WARNING: CPU: 1 PID: 1316 at /build/linux-snapdragon-t5G9R3/linux-snapdragon-4.15.0/drivers/iommu/qcom_iommu.c:336 qcom_iommu_domain_free +0x74/0x88 [8.167166] Modules linked in: adv7511_drm cec rc_core msm(+) mdt_loader [8.181137] CPU: 1 PID: 1316 Comm: systemd-udevd Not tainted 4.15.0-1061-snapdragon #68-Ubuntu [8.188079] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) [8.196501] pstate: 6045 (nZCv daif +PAN -UAO) [8.203356] pc : qcom_iommu_domain_free+0x74/0x88 [8.207955] lr : qcom_iommu_domain_free+0x74/0x88 [8.212727] sp : 0cbeb680 [8.217412] x29: 0cbeb680 x28: 8000396d84b8 [8.220713] x27: 8000396d84b0 x26: 8000396d84c0 [8.226096] x25: 80003d057c10 x24: 8000396d8420 - [8.231391] x23: 0003 x22: 80003ce40258 - [8.236686] x21: 8203ad00 x20: 8203af30 - [8.241981] x19: 8203af00 x18: - [8.247275] x17: x16: 0004 - [8.252570] x15: 09549c08 x14: 0720072007200720 - [8.257866] x13: 0720072007200720 x12: 0720072007200720 - [8.263161] x11: 09549e80 x10: 0871d340 - [8.268456] x9 : 0720072007200720 x8 : 0005 - [8.273751] x7 : 0720072d072d072d x6 : 014c - [8.279046] x5 : 08610250 x4 : - [8.284345] x3 : x2 : a59fa8ece8469a00 - [8.289637] x1 : x0 : 0024 + [8.231391] x23: 0003 x22: 80003ce40258 + [8.236686] x21: 8203ad00 x20: 8203af30 + [8.241981] x19: 8203af00 x18: + [8.247275] x17: x16: 0004 + [8.252570] x15: 09549c08 x14: 0720072007200720 + [8.257866] x13: 0720072007200720 x12: 0720072007200720 + [8.263161] x11: 09549e80 x10: 0871d340 + [8.268456] x9 : 0720072007200720 x8 : 0005 + [8.273751] x7 : 0720072d072d072d x6 : 014c + [8.279046] x5 : 08610250 x4 : + [8.284345] x3 : x2 : a59fa8ece8469a00 + [8.289637] x1 : x0 : 0024 [8.294932] Call trace: [8.300227] qcom_iommu_domain_free+0x74/0x88 [8.302400] iommu_group_release+0x54/0x90 [8.306914] kobject_put+0x8c/0x1f0 [8.310905] kobject_del.part.0+0x3c/0x50 [8.314292] kobject_put+0x74/0x1f0 [8.318455] iommu_group_remove_device+0x10c/0x198 [8.321756] qcom_iommu_remove_device+0x58/0x70 [8.326617] iommu_bus_notifier+0xa8/0x120 [8.331045] notifier_call_chain+0x5c/0xa0 [8.335210] blocking_notifier_call_chain+0x64/0x88 [8.339294] device_del+0x234/0x368 [8.344066] platform_device_del.part.3+0x2c/0x98 [8.347539] platform_device_unregister+0x24/0x38 [8.352410] of_platform_device_destroy+0xb8/0xc0 [8.357087] device_for_each_child+0x58/0xb0 [8.361775] of_platform_depopulate+0x4c/0x68 [8.366350] msm_pdev_probe+0x2c4/0x388 [msm] [8.370369] platform_drv_probe+0x60/0xc0 [8.374707] driver_probe_device+0x2ec/0x458 [8.378701] __driver_attach+0xdc/0x128 [8.383042] bus_for_each_dev+0x78/0xd8 [8.386598] driver_attach+0x30/0x40 [8.390418] bus_add_driver+0x20c/0x2a8 [8.394237] driver_register+0x6c/0x110 [8.397797] __platform_driver_register+0x54/0x60 [8.401841] msm_drm_register+0x54/0x80 [msm] [8.406481] do_one_initcall+0x58/0x160 [8.410818] do_init_module+0x64/0x1d8 [8.414463] load_module+0x1378/0x15c8 [8.418282] SyS_finit_module+0x100/0x118 [8.422016] el0_svc_naked+0x30/0x34 [8.426095] ---[ end trace 800d0885aa276bfd ]--- Fix: During the Ubuntu-snapdragon-4.15.0-1061.68 cycle, we picked up one upstream patch that of_platform_depopulate() msm in case of probe - deferral, but that patch triggers a WARN_ON() during the wind down of - the IOMMU (and a kernel hang) - revert the ported stable patch that - depopulates. + deferral (or during the removal), but that patch triggers a WARN_ON() + during the wind down
[Kernel-packages] [Bug 1841911] Re: Kernel hangs during msm init
** Summary changed: - Kernel crash during msm init (or during shutdown) + Kernel hangs during msm init -- 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/1841911 Title: Kernel hangs during msm init Status in linux-snapdragon package in Ubuntu: New Bug description: Impact: Ubuntu-snapdragon-4.15.0-1061.68 hangs during boot around msm init. Sometimes we get the following stack trace, or the boot completes and the board hangs during reboot: ... [8.113018] msm_dsi_manager_register: failed to register mipi dsi host for DSI 0 [8.131081] msm 1a0.mdss: failed to bind 1a98000.dsi (ops dsi_ops [msm]): -517 [8.138234] msm 1a0.mdss: master bind failed: -517 [8.145551] platform 1a01000.mdp: Dropping the link to 1ef.iommu [8.150545] iommu: Removing device 1a01000.mdp from group 1 [8.157051] [ cut here ] [8.162369] WARNING: CPU: 1 PID: 1316 at /build/linux-snapdragon-t5G9R3/linux-snapdragon-4.15.0/drivers/iommu/qcom_iommu.c:336 qcom_iommu_domain_free +0x74/0x88 [8.167166] Modules linked in: adv7511_drm cec rc_core msm(+) mdt_loader [8.181137] CPU: 1 PID: 1316 Comm: systemd-udevd Not tainted 4.15.0-1061-snapdragon #68-Ubuntu [8.188079] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT) [8.196501] pstate: 6045 (nZCv daif +PAN -UAO) [8.203356] pc : qcom_iommu_domain_free+0x74/0x88 [8.207955] lr : qcom_iommu_domain_free+0x74/0x88 [8.212727] sp : 0cbeb680 [8.217412] x29: 0cbeb680 x28: 8000396d84b8 [8.220713] x27: 8000396d84b0 x26: 8000396d84c0 [8.226096] x25: 80003d057c10 x24: 8000396d8420 [8.231391] x23: 0003 x22: 80003ce40258 [8.236686] x21: 8203ad00 x20: 8203af30 [8.241981] x19: 8203af00 x18: [8.247275] x17: x16: 0004 [8.252570] x15: 09549c08 x14: 0720072007200720 [8.257866] x13: 0720072007200720 x12: 0720072007200720 [8.263161] x11: 09549e80 x10: 0871d340 [8.268456] x9 : 0720072007200720 x8 : 0005 [8.273751] x7 : 0720072d072d072d x6 : 014c [8.279046] x5 : 08610250 x4 : [8.284345] x3 : x2 : a59fa8ece8469a00 [8.289637] x1 : x0 : 0024 [8.294932] Call trace: [8.300227] qcom_iommu_domain_free+0x74/0x88 [8.302400] iommu_group_release+0x54/0x90 [8.306914] kobject_put+0x8c/0x1f0 [8.310905] kobject_del.part.0+0x3c/0x50 [8.314292] kobject_put+0x74/0x1f0 [8.318455] iommu_group_remove_device+0x10c/0x198 [8.321756] qcom_iommu_remove_device+0x58/0x70 [8.326617] iommu_bus_notifier+0xa8/0x120 [8.331045] notifier_call_chain+0x5c/0xa0 [8.335210] blocking_notifier_call_chain+0x64/0x88 [8.339294] device_del+0x234/0x368 [8.344066] platform_device_del.part.3+0x2c/0x98 [8.347539] platform_device_unregister+0x24/0x38 [8.352410] of_platform_device_destroy+0xb8/0xc0 [8.357087] device_for_each_child+0x58/0xb0 [8.361775] of_platform_depopulate+0x4c/0x68 [8.366350] msm_pdev_probe+0x2c4/0x388 [msm] [8.370369] platform_drv_probe+0x60/0xc0 [8.374707] driver_probe_device+0x2ec/0x458 [8.378701] __driver_attach+0xdc/0x128 [8.383042] bus_for_each_dev+0x78/0xd8 [8.386598] driver_attach+0x30/0x40 [8.390418] bus_add_driver+0x20c/0x2a8 [8.394237] driver_register+0x6c/0x110 [8.397797] __platform_driver_register+0x54/0x60 [8.401841] msm_drm_register+0x54/0x80 [msm] [8.406481] do_one_initcall+0x58/0x160 [8.410818] do_init_module+0x64/0x1d8 [8.414463] load_module+0x1378/0x15c8 [8.418282] SyS_finit_module+0x100/0x118 [8.422016] el0_svc_naked+0x30/0x34 [8.426095] ---[ end trace 800d0885aa276bfd ]--- Fix: During the Ubuntu-snapdragon-4.15.0-1061.68 cycle, we picked up one upstream patch that of_platform_depopulate() msm in case of probe deferral (or during the removal), but that patch triggers a WARN_ON() during the wind down of the IOMMU (and the susequent kernel hang) - unless we want to backport the new msm dri driver (and all the relevant dependencies), revert the stable patch that calls of_platform_depopulate(). How to test: Boot a patched kernel and check if that stracktrace shows up again. Regression: None, i'm reverting a patch that wasn't there before and clearly wasn't tested with our downstream BSP. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1841911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : ke
[Kernel-packages] [Bug 1838619] Re: Turn off nvme driver on raspi2
** Description changed: + Impact: + We recently adjusted CONFIG_NVM to fix a build failure. The change causing this was actually a mis-merge and will be reverted. However the question came up whether it makes sense at all to build any raspberry kernel with NVME support at all. There currently is no way to attach any NVME to a raspberry pi, so lets turn off driver support for it for that kernel in total. + + Fix: + + Disable the relevant config options: + + # CONFIG_NVM is not set + ... + # CONFIG_NVME_FC is not set + # CONFIG_NVME_TARGET is not set + + + Regression potential: + + None, we are disabling support for a piece of hardware that doesn't + exist on the RaspberryPi boards. -- 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/1838619 Title: Turn off nvme driver on raspi2 Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 source package in Bionic: New Bug description: Impact: We recently adjusted CONFIG_NVM to fix a build failure. The change causing this was actually a mis-merge and will be reverted. However the question came up whether it makes sense at all to build any raspberry kernel with NVME support at all. There currently is no way to attach any NVME to a raspberry pi, so lets turn off driver support for it for that kernel in total. Fix: Disable the relevant config options: # CONFIG_NVM is not set ... # CONFIG_NVME_FC is not set # CONFIG_NVME_TARGET is not set Regression potential: None, we are disabling support for a piece of hardware that doesn't exist on the RaspberryPi boards. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1838619/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829193] Re: linux-aws: 4.4.0-1084.94 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.4.0-1084.94 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- 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/1829193 Title: linux-aws: 4.4.0-1084.94 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow 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 snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable 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 Xenial: New 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: 1829209 phase: Ready for Packaging phase-changed: Wednesday, 15. May 2019 14:03 UTC reason: prepare-package: Pending -- version not specified To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829193/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1829179] Re: linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker
** Summary changed: - linux-azure: -proposed tracker + linux-azure: 4.18.0-1019.19~18.04.1 -proposed tracker ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- 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/1829179 Title: linux-azure: 4.18.0-1019.19~18.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: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow snap-release-to-beta series: New Status in Kernel SRU Workflow snap-release-to-candidate series: New Status in Kernel SRU Workflow snap-release-to-edge series: New Status in Kernel SRU Workflow snap-release-to-stable 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 Bionic: New 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 derivatives: bug 1829178 (linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1829180 phase: Packaging phase-changed: Thursday, 16. May 2019 14:08 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 To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1829179/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1824474] Re: Is Vcs-Git line correct?
** Description changed: + Impact: + + apt-get source suggets the wrong instructions when inquiring for linux- + meta-raspi2: + + $ apt-get source linux-meta-raspi2 + ... + NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: + git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 + Please use: + git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 + to retrieve the latest (possibly unreleased) updates to the package. + + which, if executed, result in a checkout of the master branch in a + raspi2 subdirectory (instead of a checkout of the raspi2 branch). + + Fix: + + Fix the Vcs-Git line in linux-meta-raspi2/debian/control.common. + + How to test: + + Check the output of `apt-get source linux-meta-raspi2`, a fixed version + will suggest: + + ... + git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic -b raspi2 + ... + + Regression potential: + + Very low, trivial modification. + + -- + The control file for the latest version of this package contains: Vcs-Git: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux- meta/+git/disco raspi2 This cauases `apt-get source` to suggest: NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. ...which checks out the sources to the raspi2 subdirectory, instead of checking out the raspi2 branch. Is this supposed to be "-b raspi2" instead? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-meta-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1824474 Title: Is Vcs-Git line correct? Status in linux-meta-raspi2 package in Ubuntu: New Bug description: Impact: apt-get source suggets the wrong instructions when inquiring for linux-meta-raspi2: $ apt-get source linux-meta-raspi2 ... NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. which, if executed, result in a checkout of the master branch in a raspi2 subdirectory (instead of a checkout of the raspi2 branch). Fix: Fix the Vcs-Git line in linux-meta-raspi2/debian/control.common. How to test: Check the output of `apt-get source linux-meta-raspi2`, a fixed version will suggest: ... git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic -b raspi2 ... Regression potential: Very low, trivial modification. -- The control file for the latest version of this package contains: Vcs-Git: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux- meta/+git/disco raspi2 This cauases `apt-get source` to suggest: NOTICE: 'linux-meta-raspi2' packaging is maintained in the 'Git' version control system at: git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 Please use: git clone git://git.launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-meta/+git/cosmic raspi2 to retrieve the latest (possibly unreleased) updates to the package. ...which checks out the sources to the raspi2 subdirectory, instead of checking out the raspi2 branch. Is this supposed to be "-b raspi2" instead? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-meta-raspi2/+bug/1824474/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2
Armhf is already using zImage (and the kernel decompress itself once we jump to it), so this is an arm64-only issue and no, there's no reason to have vmlinuz uncompressed as long as the bootloader can handle it - i'll send a fix to switch to Image.gz in Eoan. -- 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/1808056 Title: vmlinuz is very large in arm64 -raspi2 Status in flash-kernel package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: The debs are close to the same size: mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb But the vmlinuz on arm64 is several times larger: $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw--- root/root 6633048 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw--- root/root 23914504 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 This forced us to make the boot partition larger for the raspi3 b+ arm64 image we made. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1808056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
I realize this is just a workaround (and the above 31M cma memory fragmentation is ugly), but we should definitely bump CMA allocation space: definitely 32M (since that's what upstream default to) but if 64M solves a problem you have at the moment (until we sort out the driver issue), i'm not opposing to such a change - after all, you are the main consumer of generic/arm64 (all other boards are either armhf or have their own topic kernel) so if there's a workaround we can apply to make your life easier, i don't see why we shouldn't do it. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2
** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- 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/1808056 Title: vmlinuz is very large in arm64 -raspi2 Status in flash-kernel package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: The debs are close to the same size: mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb But the vmlinuz on arm64 is several times larger: $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw--- root/root 6633048 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw--- root/root 23914504 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 This forced us to make the boot partition larger for the raspi3 b+ arm64 image we made. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1808056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2
Yes, arm64 kernels don't have any decompressor build-in (and they'll never get one) - i'm fine with your idea of compressing / decompressing kernels upon installation (to avoid regression in corner cases) but i would like (at some point in the future) to switch to compressed kernels though (next LTS? F?). -- 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/1808056 Title: vmlinuz is very large in arm64 -raspi2 Status in flash-kernel package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: The debs are close to the same size: mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb But the vmlinuz on arm64 is several times larger: $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw--- root/root 6633048 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw--- root/root 23914504 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 This forced us to make the boot partition larger for the raspi3 b+ arm64 image we made. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1808056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
Yes, i have all the hardware to do some testing, prepare some kernels and we can take it from there. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2
** Changed in: linux-raspi2 (Ubuntu) Assignee: Paolo Pisati (p-pisati) => (unassigned) -- 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/1808056 Title: vmlinuz is very large in arm64 -raspi2 Status in flash-kernel package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: The debs are close to the same size: mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb But the vmlinuz on arm64 is several times larger: $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw--- root/root 6633048 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw--- root/root 23914504 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 This forced us to make the boot partition larger for the raspi3 b+ arm64 image we made. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1808056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
Here are dmesg and meminfo for all 3 cases (generuic, cma3 and cma3=64M): https://people.canonical.com/~ppisati/lp1823753/ Other than the different memory alloaction, i didn't notice any evident regression. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Confirmed Bug description: On some arm64 systems[*] we are seeing a spew of messages on the console: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 This appears to be non-fatal - impacted systems all eventually boot. But, at least in the case of the HP m400, it slows down boot enough that MAAS' default timeout will expire before completing deployment. [*] Observed on a HiSilicon D06 w/ SMMU disabled in the BIOS, as well as an HP m400 (APM X-Gene) cartridge - although, not on another one that - in theory - should be identical. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823655] Re: Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work
Can you add all the relevant information here? How to reproduce the issue (kernel version pre & post regression), hardware used (cpu board, io board), an accurate description of the issue (what *exactly* was working before the regression, what didn't work after the breakage, etc), any other relevant information, etc. ** Changed in: linux-raspi2 (Ubuntu) Status: New => Incomplete ** Changed in: linux-raspi2 (Ubuntu) Importance: Undecided => Low -- 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/1823655 Title: Second SD card on RPi3 CM3 on Ubuntu Core 18 does not work Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: As suggested in following thread; https://forum.snapcraft.io/t/second-sd-card-on-rpi3-cm3-with-ubuntu- core-18/10465 a bug report. The configuration works for a Ubuntu Core 16 device. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1823655/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1675949] Re: perf report can't annotate kernel and dbgsym package has wrong addresses
** Also affects: linux (Ubuntu Disco) Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: Confirmed ** Also affects: linux (Ubuntu Cosmic) 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/1675949 Title: perf report can't annotate kernel and dbgsym package has wrong addresses Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Status in linux source package in Cosmic: New Status in linux source package in Disco: Confirmed Bug description: Impact: Under some condition, 'perf report' is unable to show the assembly code of a kernel function (perf report -> select a kernel function -> annotate). This is not an issue of the kernel itself or the perf tool, instead it's your environment that is missing the objdump binary (and perf, unfortunately, doesn't complain about it). Make sure binutils is not installed, or move away the objdump binary: # mv /usr/bin/objdump /usr/bin/objdump.foo Run a perf session and write down all events: # perf record -a -- sleep 10 # perf report selct a kernel function, press 'Annotate', a blank screen will appears (instead of the assembly code). Now put the objdump binary back (or install binutils): # mv /usr/bin/objdump.foo /usr/bin/objdump and run again perf report: # perf report select a kernel function, annotate, the disassembly will show up. Fix: Make binutils a Depends in SRCPKGNAME-tools-PKGVER-ABINUM - see the attached patch. How to test: Install a patched linux-tools-PKGVER-ABINUM.deb package: it will require binutils. Regression: We are adding a new dependency on a package, so code wise there's no regression potential - on the other hand, image creation, or development environment will experience a slight increase in size (1.8MB on x86-64 and 2.1M on arm64) if they didn't install binutils already. -- Running zesty 4.10.0-13-generic kernel and running: $ perf record followed by $ perf report results in output that can't be annotated (even when run as root). The following message appears: Couldn't annotate do_io_submit: No vmlinux file with build id 81ba79d482fa9e3ea58486de8f119b27fe6db55e was found in the path. Note that annotation using /proc/kcore requires CAP_SYS_RAWIO capability. Please use: perf buildid-cache -vu vmlinux Note this is being run as root and /proc/kcore is accessible with dd from the same shell: $ dd if=/proc/kcore bs=8 count=16 | hexdump 000 457f 464c 0102 0001 010 0004 00b7 0001 020 0040 030 0040 0038 0003 040 0004 00e8 Additionally, installing the linux-image-4.10.0-13-generic-dbgsym actually hurts the situation because the symbol addresses in the dbgsym don't match the kernel addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1675949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827750] Re: Not boot with EFI
** Description changed: + Impact: + + The linux-raspi2 kernel doesn't have the necessary UEFI hooks to boot on + a UEFI enabled system. + + Fix: + + Enable the relevant UEFI options (see the attached patch). + + How to test: + + On a patched kernel, UEFI presence will be check during boot: + + $ dmesg | grep -i eufi + ... + [0.00] efi: UEFI not found. + ... + + Regression potential: + + Very low, some config option changes that have been enabled in generic + for a long while. + + -- + Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. Please add support kernel option CONFIG_U(EFI)_STUB=y as default. Thanks. os: ubuntu 18.04 lts arm64 hw: raspberry pi 3b (+ tiano core uefi) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1827750 Title: Not boot with EFI Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: Impact: The linux-raspi2 kernel doesn't have the necessary UEFI hooks to boot on a UEFI enabled system. Fix: Enable the relevant UEFI options (see the attached patch). How to test: On a patched kernel, UEFI presence will be check during boot: $ dmesg | grep -i eufi ... [0.00] efi: UEFI not found. ... Regression potential: Very low, some config option changes that have been enabled in generic for a long while. -- Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. Please add support kernel option CONFIG_U(EFI)_STUB=y as default. Thanks. os: ubuntu 18.04 lts arm64 hw: raspberry pi 3b (+ tiano core uefi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1827750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831219] [NEW] Refresh RaspberryPi BSP
Public bug reported: BugLink: https://bugs.launchpad.net/bugs/1831219 BugLink: https://bugs.launchpad.net/bugs/1825235 Impact: Since the release of Ubuntu Disco, the upstream RaspberryPI BSP has received a lot of bug fixes and improvements over the release imported in disco/raspi2. Among the fixes, it corrects a patological 'fictious high load situation' we inherithed from upstream: https://github.com/raspberrypi/linux/issues/2881 BugLink: https://bugs.launchpad.net/bugs/1825235 Fix: As part of our SRU process, remove the imported RaspberryPI BSP (first patch in the series) and do a fresh import of the latest available revision Regression: Since it contains many changes, it comes with regression risks, but so does every stable update series we apply ** Affects: linux-raspi2 (Ubuntu) Importance: Undecided Status: New ** Affects: linux-raspi2 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-raspi2 (Ubuntu Disco) Importance: Undecided Status: New ** Description changed: + BugLink: https://bugs.launchpad.net/bugs/1831219 + BugLink: https://bugs.launchpad.net/bugs/1825235 + Impact: Since the release of Ubuntu Disco, the upstream RaspberryPI BSP has received a lot of bug fixes and improvements over the release imported in disco/raspi2. Among the fixes, it corrects a patological 'fictious high load situation' we inherithed from upstream: https://github.com/raspberrypi/linux/issues/2881 BugLink: https://bugs.launchpad.net/bugs/1825235 Fix: - As part of our SRU process, remove the original RaspberryPI BSP and do a - fresh import of the latest available revision + As part of our SRU process, remove the imported RaspberryPI BSP (first + patch in the series) and do a fresh import of the latest available + revision Regression: Since it contains many changes, it comes with regression risks, but so does every stable update series we apply -- 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/1831219 Title: Refresh RaspberryPi BSP Status in linux-raspi2 package in Ubuntu: New Status in linux-raspi2 source package in Disco: New Bug description: BugLink: https://bugs.launchpad.net/bugs/1831219 BugLink: https://bugs.launchpad.net/bugs/1825235 Impact: Since the release of Ubuntu Disco, the upstream RaspberryPI BSP has received a lot of bug fixes and improvements over the release imported in disco/raspi2. Among the fixes, it corrects a patological 'fictious high load situation' we inherithed from upstream: https://github.com/raspberrypi/linux/issues/2881 BugLink: https://bugs.launchpad.net/bugs/1825235 Fix: As part of our SRU process, remove the imported RaspberryPI BSP (first patch in the series) and do a fresh import of the latest available revision Regression: Since it contains many changes, it comes with regression risks, but so does every stable update series we apply To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1831219/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808056] Re: vmlinuz is very large in arm64 -raspi2
On the kernel side, the switch to a compressed kernel is a trivial change: diff --git a/debian.raspi2/rules.d/arm64.mk b/debian.raspi2/rules.d/arm64.mk index ada61b8..9f82433 100644 --- a/debian.raspi2/rules.d/arm64.mk +++ b/debian.raspi2/rules.d/arm64.mk @@ -3,7 +3,7 @@ build_arch = arm64 header_arch= arm64 defconfig = defconfig flavours = raspi2 -build_image= Image +build_image= Image.gz kernel_file= arch/$(build_arch)/boot/Image install_file = vmlinuz no_dumpfile= true Feel free to send such a change to the kernel ml once userspace issues (classic and core) are sorted out. -- 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/1808056 Title: vmlinuz is very large in arm64 -raspi2 Status in flash-kernel package in Ubuntu: Confirmed Status in linux-raspi2 package in Ubuntu: Triaged Bug description: The debs are close to the same size: mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw-rw-r-- 1 mwhudson mwhudson 5398652 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb mwhudson@ringil:~/Downloads$ ls -l linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw-rw-r-- 1 mwhudson mwhudson 6640960 Dec 12 10:42 linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb But the vmlinuz on arm64 is several times larger: $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_armhf.deb -rw--- root/root 6633048 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 $ dpkg-deb -c linux-image-4.15.0-1030-raspi2_4.15.0-1030.32_arm64.deb -rw--- root/root 23914504 2018-12-07 06:38 ./boot/vmlinuz-4.15.0-1030-raspi2 This forced us to make the boot partition larger for the raspi3 b+ arm64 image we made. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/flash-kernel/+bug/1808056/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832012] [NEW] Enable the Qualcomm DB820C board
Public bug reported: Impact: The bionic/snapdragon kernel should work on qcom410 and qcom820 chipsets, but due to some bugs, it never booted on any qcom820 board (e.g. Qualcomm DB820C APQ8096). Fix: Import all the necessary patches (see the pull request below). How to test: 1) put the board in fastboot mode (see [1]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 --ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output bionic-snapdragon-db820c-boot.img 3) fastboot the board using the freshly generated boot.img: $ fastboot boot bionic-snapdragon-db820c-boot.img Regression potential: With new code there's always a degree of regression potential, but all patches (but one) were cherry-picked from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree. 1: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation /board-recovery.md.html ** Affects: linux-snapdragon (Ubuntu) Importance: Undecided Status: New -- 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/1832012 Title: Enable the Qualcomm DB820C board Status in linux-snapdragon package in Ubuntu: New Bug description: Impact: The bionic/snapdragon kernel should work on qcom410 and qcom820 chipsets, but due to some bugs, it never booted on any qcom820 board (e.g. Qualcomm DB820C APQ8096). Fix: Import all the necessary patches (see the pull request below). How to test: 1) put the board in fastboot mode (see [1]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 --ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output bionic-snapdragon-db820c-boot.img 3) fastboot the board using the freshly generated boot.img: $ fastboot boot bionic-snapdragon-db820c-boot.img Regression potential: With new code there's always a degree of regression potential, but all patches (but one) were cherry-picked from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree. 1: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation /board-recovery.md.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1832012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832012] Re: Initial support for Qualcomm Snapdragon 820 chipset
** Summary changed: - Enable the Qualcomm DB820C board + Initial support for Qualcomm Snapdragon 820 chipset -- 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/1832012 Title: Initial support for Qualcomm Snapdragon 820 chipset Status in linux-snapdragon package in Ubuntu: New Bug description: Impact: The bionic/snapdragon kernel should work on qcom410 and qcom820 chipsets, but due to some bugs, it never booted on any qcom820 board (e.g. Qualcomm DB820C APQ8096). Fix: Import all the necessary patches (see the pull request below). How to test: 1) put the board in fastboot mode (see [1]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 --ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output bionic-snapdragon-db820c-boot.img 3) fastboot the board using the freshly generated boot.img: $ fastboot boot bionic-snapdragon-db820c-boot.img Regression potential: With new code there's always a degree of regression potential, but all patches (but one) were cherry-picked from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree. 1: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation /board-recovery.md.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-snapdragon/+bug/1832012/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832012] Re: Initial support for Qualcomm Snapdragon 820 chipset
** Description changed: Impact: - The bionic/snapdragon kernel should work on qcom410 and qcom820 - chipsets, but due to some bugs, it never booted on any qcom820 board - (e.g. Qualcomm DB820C APQ8096). + Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing + tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm + DB820C APQ8096). Fix: - Import all the necessary patches (see the pull request below). + Import the necessary patches to make it boot on such board (and clones). How to test: - 1) put the board in fastboot mode (see [1]) + 1) put the board in fastboot mode (see [2]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 --ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output bionic-snapdragon-db820c-boot.img - 3) fastboot the board using the freshly generated boot.img: + 3) boot the board using the generated boot.img: $ fastboot boot bionic-snapdragon-db820c-boot.img Regression potential: - With new code there's always a degree of regression potential, but all - patches (but one) were cherry-picked from Linus's upstream tree, and the - only external one, came direclty from the qcom-lt 4.14 tree. + With new code there's always a degree of regression potential, but all patches + (but one) came from Linus's upstream tree, and the only external one, came + direclty from the qcom-lt 4.14 tree. - 1: - https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation - /board-recovery.md.html + 1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14 + 2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html ** Description changed: Impact: - Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing - tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm - DB820C APQ8096). + Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm + landing tree kernel[1], it didn't work on Snapdragon 820 based board + (e.g. Qualcomm DB820C APQ8096). Fix: Import the necessary patches to make it boot on such board (and clones). How to test: 1) put the board in fastboot mode (see [2]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 --ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output bionic-snapdragon-db820c-boot.img 3) boot the board using the generated boot.img: $ fastboot boot bionic-snapdragon-db820c-boot.img Regression potential: - With new code there's always a degree of regression potential, but all patches - (but one) came from Linus's upstream tree, and the only external one, came - direclty from the qcom-lt 4.14 tree. + With new code there's always a degree of regression potential, but all + patches (but one) came from Linus's upstream tree, and the only external + one, came direclty from the qcom-lt 4.14 tree. 1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14 2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html -- 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/1832012 Title: Initial support for Qualcomm Snapdragon 820 chipset Status in linux-snapdragon package in Ubuntu: New Bug description: Impact: Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096). Fix: Import the necessary patches to make it boot on such a board (and clones). How to test: 1) put the board in fastboot mode (see [2]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Ima
[Kernel-packages] [Bug 1832012] Re: Initial support for Qualcomm Snapdragon 820 chipset
** Description changed: Impact: - Altough the Bionic/snapdragon kernel contains the BSP from the Qualcomm + Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096). Fix: Import the necessary patches to make it boot on such board (and clones). How to test: 1) put the board in fastboot mode (see [2]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 --ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output bionic-snapdragon-db820c-boot.img 3) boot the board using the generated boot.img: $ fastboot boot bionic-snapdragon-db820c-boot.img Regression potential: With new code there's always a degree of regression potential, but all patches (but one) came from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree. 1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14 2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html ** Description changed: Impact: Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096). Fix: - Import the necessary patches to make it boot on such board (and clones). + Import the necessary patches to make it boot on such a board (and + clones). How to test: 1) put the board in fastboot mode (see [2]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 --ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output bionic-snapdragon-db820c-boot.img 3) boot the board using the generated boot.img: $ fastboot boot bionic-snapdragon-db820c-boot.img Regression potential: With new code there's always a degree of regression potential, but all patches (but one) came from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree. 1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14 2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-recovery.md.html -- 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/1832012 Title: Initial support for Qualcomm Snapdragon 820 chipset Status in linux-snapdragon package in Ubuntu: New Bug description: Impact: Although the Bionic/snapdragon kernel contains the BSP from the Qualcomm landing tree kernel[1], it didn't work on Snapdragon 820 based board (e.g. Qualcomm DB820C APQ8096). Fix: Import the necessary patches to make it boot on such a board (and clones). How to test: 1) put the board in fastboot mode (see [2]) 2) generate a compatible boot.img: $ cat linux/arch/arm64/boot/Image.gz linux/arch/arm64/boot/dts/qcom/apq8096-db820c.dtb > Image.gz+dtb $ touch ramdisk $ python android/system/core/mkbootimg/mkbootimg.py --kernel Image.gz+dtb --ramdisk ramdisk --pagesize 4096 --base 0x8000 --kernel_offset 0x8000 --ramdisk_offset 0x100 --tags_offset 0x100 --cmdline 'console=ttyMSM0,115200n8 root=/dev/sda1 net.ifnames=0 init=/lib/systemd/systemd ro rootwait rng_core.default_quality=700 panic=-1 fixrtc earlyprintk earlycon=msm_serial_dm,0x75b' --output bionic-snapdragon-db820c-boot.img 3) boot the board using the generated boot.img: $ fastboot boot bionic-snapdragon-db820c-boot.img Regression potential: With new code there's always a degree of regression potential, but all patches (but one) came from Linus's upstream tree, and the only external one, came direclty from the qcom-lt 4.14 tree. 1: https://git.linaro.org/landing-teams/working/qualcomm/kernel.git/log/?h=release/qcomlt-4.14 2: https://www.96boards.org/documentation/consumer/dragonboard/dragonboard820c/installation/board-
[Kernel-packages] [Bug 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi
** Changed in: linux-raspi2 (Ubuntu) Status: New => Confirmed -- 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/1825235 Title: Load average inexplicably high with 5.0 kernel on rpi Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the disco release candidate. After booting, the load average stays quite high, typically over 4.0. This persists, even if I leave it idle for several hours: ubuntu@ubuntu:~$ w 19:44:05 up 2:22, 1 user, load average: 4.16, 4.03, 4.01 /proc/loadavg is consistent with these numbers. But when I check top, there are no obvious culprits hogging the cpu or anything. Typically everything looks to be <1% cpu usage, with top being the biggest cpu hog at about 2%. The system doesn't seem too slow (for a pi), but it's unusual to see such high numbers. Nothing seems to be swapping: ubuntu@ubuntu:~$ free -m totalusedfree shared buff/cache available Mem:908 173 422 6 312 707 Swap: 0 0 0 ubuntu@ubuntu:~$ iostat Linux 5.0.0-1006-raspi2 (ubuntu) 04/17/19_aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.640.151.572.060.00 94.57 Device tpskB_read/skB_wrtn/skB_readkB_wrtn loop0 0.08 0.50 0.00354 0 loop1 2.56 3.98 0.00 2805 0 loop2 0.01 0.01 0.00 4 0 mmcblk0 12.70 367.40 705.16 258830 496785 ubuntu@ubuntu:~$ vmstat 1 procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 0 0 514540 18004 2240720097 182 2564 76 2 2 94 2 0 0 0 0 514512 18004 22413600 0 2012 10136 142 0 0 94 5 0 0 0 0 514512 18004 22413600 0 0 10117 106 0 0 100 0 0 0 0 0 514512 18004 22413600 0 0 10121 98 0 0 100 0 0 0 0 0 514512 18012 22412800 0 2028 10129 141 0 0 93 7 0 0 0 0 514512 18012 22413600 0 0 10149 135 0 0 100 0 0 0 0 0 514512 18012 22413600 0 0 10108 97 0 0 100 0 0 0 0 0 514512 18012 22413600 0 2012 10125 126 0 0 95 5 0 0 0 0 514512 18012 22413600 0 0 10117 101 0 0 100 0 0 0 1 0 514512 18012 22413600 0 2012 10109 104 0 0 98 2 0 0 0 0 514512 18020 22412800 012 10139 150 0 0 96 4 0 0 0 0 514512 18020 22412800 0 0 10108 90 0 0 100 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1825235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1825235] Re: Load average inexplicably high with 5.0 kernel on rpi
I can reproduce the bug on a fresh installation of Disco/armhf rpi3. Moreover, the bug appears to be kernel in-kernel - by installing the Disco kernel on a Bionic image (that didn't show any abnormal load with its Bionic/armhf kernel), the bug appears there too. The bug is reproducible as early as Ubuntu-raspi2-5.0.0-1002.2, and before that there's the Broadcom BSP, and the initial config sync wrt bcm2709_defconfig - bisecting the Broadcom BSP is a bit problematic, because removing patches, often, breaks the build. -- 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/1825235 Title: Load average inexplicably high with 5.0 kernel on rpi Status in linux-raspi2 package in Ubuntu: Confirmed Bug description: Linux ubuntu 5.0.0-1006-raspi2 #6-Ubuntu SMP Thu Apr 11 18:04:26 UTC 2019 aarch64 aarch64 aarch64 GNU/Linux I've seen this on rpi2, as well as rpi3 with both armhf and arm64 using the disco release candidate. After booting, the load average stays quite high, typically over 4.0. This persists, even if I leave it idle for several hours: ubuntu@ubuntu:~$ w 19:44:05 up 2:22, 1 user, load average: 4.16, 4.03, 4.01 /proc/loadavg is consistent with these numbers. But when I check top, there are no obvious culprits hogging the cpu or anything. Typically everything looks to be <1% cpu usage, with top being the biggest cpu hog at about 2%. The system doesn't seem too slow (for a pi), but it's unusual to see such high numbers. Nothing seems to be swapping: ubuntu@ubuntu:~$ free -m totalusedfree shared buff/cache available Mem:908 173 422 6 312 707 Swap: 0 0 0 ubuntu@ubuntu:~$ iostat Linux 5.0.0-1006-raspi2 (ubuntu) 04/17/19_aarch64_ (4 CPU) avg-cpu: %user %nice %system %iowait %steal %idle 1.640.151.572.060.00 94.57 Device tpskB_read/skB_wrtn/skB_readkB_wrtn loop0 0.08 0.50 0.00354 0 loop1 2.56 3.98 0.00 2805 0 loop2 0.01 0.01 0.00 4 0 mmcblk0 12.70 367.40 705.16 258830 496785 ubuntu@ubuntu:~$ vmstat 1 procs ---memory-- ---swap-- -io -system-- --cpu- r b swpd free buff cache si sobibo in cs us sy id wa st 0 0 0 514540 18004 2240720097 182 2564 76 2 2 94 2 0 0 0 0 514512 18004 22413600 0 2012 10136 142 0 0 94 5 0 0 0 0 514512 18004 22413600 0 0 10117 106 0 0 100 0 0 0 0 0 514512 18004 22413600 0 0 10121 98 0 0 100 0 0 0 0 0 514512 18012 22412800 0 2028 10129 141 0 0 93 7 0 0 0 0 514512 18012 22413600 0 0 10149 135 0 0 100 0 0 0 0 0 514512 18012 22413600 0 0 10108 97 0 0 100 0 0 0 0 0 514512 18012 22413600 0 2012 10125 126 0 0 95 5 0 0 0 0 514512 18012 22413600 0 0 10117 101 0 0 100 0 0 0 1 0 514512 18012 22413600 0 2012 10109 104 0 0 98 2 0 0 0 0 514512 18020 22412800 012 10139 150 0 0 96 4 0 0 0 0 514512 18020 22412800 0 0 10108 90 0 0 100 0 0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1825235/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827750] Re: Not boot with EFI
Please test this kernel and tell us if it solves you problem: https://people.canonical.com/~ppisati/lp1827750/ This kernel has EFI support (and several other EFI features) enabled: https://git.launchpad.net/~p-pisati/ubuntu/+source/linux/commit/?h=b-raspi2-lp1827750&id=ce621b56138a15dd3c67d6b40429f5739a6b51ec Once positively verified, add a step by step test procedure to this bug so we can move forward with integrating the changes. ** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Paolo Pisati (p-pisati) -- 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/1827750 Title: Not boot with EFI Status in linux-raspi2 package in Ubuntu: New Bug description: Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. Please add support kernel option CONFIG_U(EFI)_STUB=y as default. Thanks. os: ubuntu 18.04 lts arm64 hw: raspberry pi 3b (+ tiano core uefi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1827750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827750] Re: Not boot with EFI
** Changed in: linux-raspi2 (Ubuntu) Status: New => Incomplete -- 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/1827750 Title: Not boot with EFI Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. Please add support kernel option CONFIG_U(EFI)_STUB=y as default. Thanks. os: ubuntu 18.04 lts arm64 hw: raspberry pi 3b (+ tiano core uefi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1827750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1827750] Re: Not boot with EFI
Copied out that package, try again. -- 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/1827750 Title: Not boot with EFI Status in linux-raspi2 package in Ubuntu: Incomplete Bug description: Hello. I can't boot with linux-raspi2 kernel, but linux-generic work fine. Please add support kernel option CONFIG_U(EFI)_STUB=y as default. Thanks. os: ubuntu 18.04 lts arm64 hw: raspberry pi 3b (+ tiano core uefi) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1827750/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1838429] Re: Kernel snap initrd is missing several fb related kmods
** Patch added: "0001-Enable-initramfs-tools-framebuffer-script.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1838429/+attachment/5280020/+files/0001-Enable-initramfs-tools-framebuffer-script.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1838429 Title: Kernel snap initrd is missing several fb related kmods Status in linux package in Ubuntu: New Status in linux-raspi2 package in Ubuntu: New Bug description: Impact: Around pi-kernel #23 (and pc-kernel #196), kernel snap's initrd went missing all fb kmods - that was workarounded for pi-kernel last week by manually adding the modules back in: commit edd1f8914fded36d4739fd24cdbdd05c5cf37611 Author: Paolo Pisati Date: Tue Jul 23 11:30:49 2019 +0200 Initrd modules: fbdev/hdmi out support for psplash BugLink: https://launchpad.net/bugs/1837209 After more debugging, it turned out that the regression was in fact the effect of fixing LP#1561643: initrmafs-tools kept installing fb modules even when framebuffer support was not enabled, and kernel snap never explicitly enabled framebuffer initramfs-tools script, but still came bundled with such kmods. Fix: In Ubuntu Classic, to bundle fb kmods in initrd, we normally install cryptsetup: $ cat /usr/share/initramfs-tools/conf-hooks.d/cryptsetup ... FRAMEBUFFER=y But cryptsetup, among other things, adds several initramfs-tools hooks and scripts to initrd: ... scripts scripts/local +scripts/local-block +scripts/local-block/ORDER +scripts/local-block/cryptroot scripts/ubuntu-core-rootfs scripts/functions +scripts/init-premount +scripts/init-premount/ORDER +scripts/init-premount/plymouth scripts/ubuntu-core-functions scripts/local-premount scripts/local-premount/ORDER @@ -247,6 +359,10 @@ scripts/local-premount/fixrtc scripts/local-premount/dragonmac scripts/local-premount/resume +scripts/local-top +scripts/local-top/ORDER +scripts/local-top/cryptroot +scripts/local-top/cryptopensc scripts/nfs scripts/panic scripts/panic/ORDER @@ -258,10 +374,13 @@ scripts/local-bottom scripts/local-bottom/ORDER scripts/local-bottom/fixrtc-mount +scripts/local-bottom/cryptopensc scripts/init-top ... so to avoid any possible regression in kernel snaps and keep the changes to a minimum, we avoid installing cryptsetup and just enable framebuffer in initramfs-tools/conf-hooks.d (see also the attached path): --- a/Makefile +++ b/Makefile @@ -106,6 +106,9 @@ all: fi $(ENV) chroot chroot apt-get -y update;\ $(ENV) chroot chroot apt-get -y install initramfs-tools-ubuntu-core linux-firmware xz-utils + # enable initramfs-tools framebuffer script (and includes the necessary + # kmods to initrd.img) + echo "FRAMEBUFFER=y" > chroot/usr/share/initramfs-tools/conf-hooks.d/ubuntu-core-fb $(ENV) chroot chroot apt-get -y install $(KERNELDEB) $(PKGS) umount chroot/sys umount chroot/proc How to test: A diff between the content of an 'empty initrd' and one that is generated after applying the above fix, shows that fb kmods are now back: lib/modules/4.15.0-1042-raspi2/modules.dep.bin lib/modules/4.15.0-1042-raspi2/modules.alias lib/modules/4.15.0-1042-raspi2/kernel +lib/modules/4.15.0-1042-raspi2/kernel/sound +lib/modules/4.15.0-1042-raspi2/kernel/sound/soc +lib/modules/4.15.0-1042-raspi2/kernel/sound/soc/snd-soc-core.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/ac97_bus.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd-timer.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd-pcm-dmaengine.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd-pcm.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd-compress.ko lib/modules/4.15.0-1042-raspi2/kernel/drivers +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media/rc +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media/rc/rc-core.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media/cec +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media/cec/cec.ko lib/modules/4.15.0-1042-raspi2/kernel/drivers/i2c lib/modules/4.15.0-1042-raspi2/kernel/drivers/i2c/busses lib/modules/4.15.0-1042-raspi2/kernel/drivers/i2c/busses/i2c-bcm2708.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/vc4 +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/vc4/vc4.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge +lib/modules/4.15.0-104
[Kernel-packages] [Bug 1838429] [NEW] Kernel snap initrd is missing several fb related kmods
Public bug reported: Impact: Around pi-kernel #23 (and pc-kernel #196), kernel snap's initrd went missing all fb kmods - that was workarounded for pi-kernel last week by manually adding the modules back in: commit edd1f8914fded36d4739fd24cdbdd05c5cf37611 Author: Paolo Pisati Date: Tue Jul 23 11:30:49 2019 +0200 Initrd modules: fbdev/hdmi out support for psplash BugLink: https://launchpad.net/bugs/1837209 After more debugging, it turned out that the regression was in fact the effect of fixing LP#1561643: initrmafs-tools kept installing fb modules even when framebuffer support was not enabled, and kernel snap never explicitly enabled framebuffer initramfs-tools script, but still came bundled with such kmods. Fix: In Ubuntu Classic, to bundle fb kmods in initrd, we normally install cryptsetup: $ cat /usr/share/initramfs-tools/conf-hooks.d/cryptsetup ... FRAMEBUFFER=y But cryptsetup, among other things, adds several initramfs-tools hooks and scripts to initrd: ... scripts scripts/local +scripts/local-block +scripts/local-block/ORDER +scripts/local-block/cryptroot scripts/ubuntu-core-rootfs scripts/functions +scripts/init-premount +scripts/init-premount/ORDER +scripts/init-premount/plymouth scripts/ubuntu-core-functions scripts/local-premount scripts/local-premount/ORDER @@ -247,6 +359,10 @@ scripts/local-premount/fixrtc scripts/local-premount/dragonmac scripts/local-premount/resume +scripts/local-top +scripts/local-top/ORDER +scripts/local-top/cryptroot +scripts/local-top/cryptopensc scripts/nfs scripts/panic scripts/panic/ORDER @@ -258,10 +374,13 @@ scripts/local-bottom scripts/local-bottom/ORDER scripts/local-bottom/fixrtc-mount +scripts/local-bottom/cryptopensc scripts/init-top ... so to avoid any possible regression in kernel snaps and keep the changes to a minimum, we avoid installing cryptsetup and just enable framebuffer in initramfs-tools/conf-hooks.d (see also the attached path): --- a/Makefile +++ b/Makefile @@ -106,6 +106,9 @@ all: fi $(ENV) chroot chroot apt-get -y update;\ $(ENV) chroot chroot apt-get -y install initramfs-tools-ubuntu-core linux-firmware xz-utils + # enable initramfs-tools framebuffer script (and includes the necessary + # kmods to initrd.img) + echo "FRAMEBUFFER=y" > chroot/usr/share/initramfs-tools/conf-hooks.d/ubuntu-core-fb $(ENV) chroot chroot apt-get -y install $(KERNELDEB) $(PKGS) umount chroot/sys umount chroot/proc How to test: A diff between the content of an 'empty initrd' and one that is generated after applying the above fix, shows that fb kmods are now back: lib/modules/4.15.0-1042-raspi2/modules.dep.bin lib/modules/4.15.0-1042-raspi2/modules.alias lib/modules/4.15.0-1042-raspi2/kernel +lib/modules/4.15.0-1042-raspi2/kernel/sound +lib/modules/4.15.0-1042-raspi2/kernel/sound/soc +lib/modules/4.15.0-1042-raspi2/kernel/sound/soc/snd-soc-core.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/ac97_bus.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd-timer.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd-pcm-dmaengine.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd-pcm.ko +lib/modules/4.15.0-1042-raspi2/kernel/sound/core/snd-compress.ko lib/modules/4.15.0-1042-raspi2/kernel/drivers +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media/rc +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media/rc/rc-core.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media/cec +lib/modules/4.15.0-1042-raspi2/kernel/drivers/media/cec/cec.ko lib/modules/4.15.0-1042-raspi2/kernel/drivers/i2c lib/modules/4.15.0-1042-raspi2/kernel/drivers/i2c/busses lib/modules/4.15.0-1042-raspi2/kernel/drivers/i2c/busses/i2c-bcm2708.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/vc4 +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/vc4/vc4.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/sii902x.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/tc358767.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/sil-sii8620.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/sii9234.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/dumb-vga-dac.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/parade-ps8622.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/adv7511 +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/adv7511/adv7511_drm.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/lvds-encoder.ko +lib/modules/4.15.0-1042-raspi2/kernel/drivers/gpu/drm/bridge/megachips-stdp-ge-b850
[Kernel-packages] [Bug 1838539] [NEW] Eoan update: v5.2.5 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.2.5 upstream stable release
from git://git.kernel.org/
Linux 5.2.5
io_uring: don't use iov_iter_advance() for fixed buffers
io_uring: fix counter inc/dec mismatch in async_list
io_uring: ensure ->list is initialized for poll commands
io_uring: add a memory barrier before atomic_read
access: avoid the RCU grace period for the temporary subjective credentials
drm/i915: Make the semaphore saturation mask global
structleak: disable STRUCTLEAK_BYREF in combination with KASAN_STACK
libnvdimm/bus: Stop holding nvdimm_bus_list_mutex over __nd_ioctl()
libnvdimm/region: Register badblocks before namespaces
libnvdimm/bus: Prevent duplicate device_unregister() calls
drivers/base: Introduce kill_device()
iommu/iova: Fix compilation error with !CONFIG_IOMMU_IOVA
iommu/iova: Remove stale cached32_node
iommu/vt-d: Don't queue_iova() if there is no flush queue
io_uring: fix the sequence comparison in io_sequence_defer
powerpc/pmu: Set pmcregs_in_use in paca when running as LPAR
powerpc/tm: Fix oops on sigreturn on systems without TM
powerpc/mm: Limit rma_size to 1TB when running without HV mode
powerpc/xive: Fix loop exit-condition in xive_find_target_in_mask()
powerpc/dma: Fix invalid DMA mmap behavior
ALSA: hda - Add a conexant codec entry to let mute led work
ALSA: hda - Fix intermittent CORB/RIRB stall on Intel chips
ALSA: pcm: Fix refcount_inc() on zero usage
ALSA: line6: Fix wrong altsetting for LINE6_PODHD500_1
ALSA: ac97: Fix double free of ac97_codec_device
drm/panel: Add support for Armadeus ST0700 Adapt
hpet: Fix division by zero in hpet_time_div()
eeprom: make older eeprom drivers select NVMEM_SYSFS
mei: me: add mule creek canyon (EHL) device ids
fpga-manager: altera-ps-spi: Fix build error
binder: prevent transactions to context manager from its own process.
binder: Set end of SG buffer area properly.
x86/stacktrace: Prevent access_ok() warnings in arch_stack_walk_user()
x86/speculation/mds: Apply more accurate check on hypervisor platform
x86/sysfb_efi: Add quirks for some devices with swapped width and height
selinux: check sidtab limit before adding a new entry
btrfs: inode: Don't compress if NODATASUM or NODATACOW set
media: videodev2.h: change V4L2_PIX_FMT_BGRA444 define: fourcc was already in
use
KVM: PPC: Book3S HV: XIVE: fix rollback when kvmppc_xive_create fails
KVM: PPC: Book3S HV: Save and restore guest visible PSSCR bits on pseries
KVM: PPC: Book3S HV: Always save guest pmu for guest capable of nesting
KVM: X86: Fix fpu state crash in kvm guest
usb: usb251xb: Reallow swap-dx-lanes to apply to the upstream port
Revert "usb: usb251xb: Add US port lanes inversion property"
Revert "usb: usb251xb: Add US lanes inversion dts-bindings"
usb: pci-quirks: Correct AMD PLL quirk detection
usb: wusbcore: fix unbalanced get/put cluster_id
usb-storage: Add a limitation for blk_queue_max_hw_sectors()
xhci: Fix crash if scatter gather is used with Immediate Data Transfer (IDT).
locking/lockdep: Hide unused 'class' variable
mm, swap: fix race between swapoff and some swap operations
mm: use down_read_killable for locking mmap_sem in access_remote_vm
locking/lockdep: Fix lock used or unused stats error
proc: use down_read_killable mmap_sem for /proc/pid/maps
cxgb4: reduce kernel stack usage in cudbg_collect_mem_region()
proc: use down_read_killable mmap_sem for /proc/pid/map_files
proc: use down_read_killable mmap_sem for /proc/pid/clear_refs
proc: use down_read_killable mmap_sem for /proc/pid/pagemap
proc: use down_read_killable mmap_sem for /proc/pid/smaps_rollup
mm/mmu_notifier: use hlist_add_head_rcu()
memcg, fsnotify: no oom-kill for remote memcg charging
mm/gup.c: remove some BUG_ONs from get_gate_page()
mm/gup.c: mark undo_dev_pagemap as __maybe_unused
mm/mincore.c: fix race between swapoff and mincore
9p: pass the correct prototype to read_cache_page
mm/kmemleak.c: fix check for softirq context
sh: prevent warnings when using iounmap
nvme: fix NULL deref for fabrics options
block/bio-integrity: fix a memory leak bug
platform/x86: Fix PCENGINES_APU2 Kconfig warning
powerpc/eeh: Handle hugepages in ioremap space
dlm: check if workqueues are NULL before flushing/destroying
mailbox: handle failed named mailbox channel request
f2fs: avoid out-of-range memory access
f2fs: fix to avoid long latency during umount
rds: Accept peer connection reject messages due to incompatible version
block: init flush rq ref count to 1
powerpc/boot: add {get, put}_unaligned_be32 to xz_config.h
powerpc/irq: Don't WARN continuously in arch
[Kernel-packages] [Bug 1839587] [NEW] Eoan update: v5.2.6 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.2.6 upstream stable release from git://git.kernel.org/ Linux 5.2.6 ceph: hold i_ceph_lock when removing caps for freeing inode Fix allyesconfig output. drivers/pps/pps.c: clear offset flags in PPS_SETPARAMS ioctl /proc//cmdline: add back the setproctitle() special case /proc//cmdline: remove all the special cases sched/fair: Use RCU accessors consistently for ->numa_group sched/fair: Don't free p->numa_faults with concurrent readers Bluetooth: hci_uart: check for missing tty operations nvme: fix multipath crash when ANA is deactivated xfrm: policy: fix bydst hlist corruption on hash rebuild media: radio-raremono: change devm_k*alloc to k*alloc NFS: Cleanup if nfs_match_client is interrupted media: pvrusb2: use a different format for warnings media: cpia2_usb: first wake up, then free in disconnect ath10k: Change the warning message string media: au0828: fix null dereference in error path bpf: fix NULL deref in btf_type_is_resolve_source_only ISDN: hfcsusb: checking idx of ep configuration vsock: correct removal of socket from the list ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: 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/1839587 Title: Eoan update: v5.2.6 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed 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: v5.2.6 upstream stable release from git://git.kernel.org/ Linux 5.2.6 ceph: hold i_ceph_lock when removing caps for freeing inode Fix allyesconfig output. drivers/pps/pps.c: clear offset flags in PPS_SETPARAMS ioctl /proc//cmdline: add back the setproctitle() special case /proc//cmdline: remove all the special cases sched/fair: Use RCU accessors consistently for ->numa_group sched/fair: Don't free p->numa_faults with concurrent readers Bluetooth: hci_uart: check for missing tty operations nvme: fix multipath crash when ANA is deactivated xfrm: policy: fix bydst hlist corruption on hash rebuild media: radio-raremono: change devm_k*alloc to k*alloc NFS: Cleanup if nfs_match_client is interrupted media: pvrusb2: use a different format for warnings media: cpia2_usb: first wake up, then free in disconnect ath10k: Change the warning message string media: au0828: fix null dereference in error path bpf: fix NULL deref in btf_type_is_resolve_source_only ISDN: hfcsusb: checking idx of ep configuration vsock: correct removal of socket from the list To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1839587/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1839588] [NEW] Eoan update: v5.2.7 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.2.7 upstream stable release
from git://git.kernel.org/
Linux 5.2.7
Documentation: Add swapgs description to the Spectre v1 documentation
x86/speculation/swapgs: Exclude ATOMs from speculation through SWAPGS
x86/entry/64: Use JMP instead of JMPQ
x86/speculation: Enable Spectre v1 swapgs mitigations
x86/speculation: Prepare entry code for Spectre v1 swapgs mitigations
x86/cpufeatures: Combine word 11 and 12 into a new scattered features word
x86/cpufeatures: Carve out CQM features retrieval
drm/i915/gvt: fix incorrect cache entry for guest page mapping
drm/i915/perf: fix ICL perf register offsets
IB/hfi1: Field not zero-ed when allocating TID flow memory
IB/hfi1: Drop all TID RDMA READ RESP packets after r_next_psn
IB/hfi1: Check for error on call to alloc_rsm_map_table
IB/mlx5: Fix RSS Toeplitz setup to be aligned with the HW specification
IB/mlx5: Fix clean_mr() to work in the expected order
IB/mlx5: Move MRs to a kernel PD when freeing them to the MR cache
IB/mlx5: Use direct mkey destroy command upon UMR unreg failure
IB/mlx5: Fix unreg_umr to ignore the mkey state
RDMA/devices: Do not deadlock during client removal
RDMA/bnxt_re: Honor vlan_id in GID entry comparison
xen/gntdev.c: Replace vm_map_pages() with vm_map_pages_zero()
xen/swiotlb: fix condition for calling xen_destroy_contiguous_region()
nbd: replace kill_bdev() with __invalidate_device() again
scsi: mpt3sas: Use 63-bit DMA addressing on SAS35 HBA
clk: mediatek: mt8183: Register 13MHz clock earlier for clocksource
io_uring: fix KASAN use after free in io_sq_wq_submit_work
arm64: cpufeature: Fix feature comparison for CTR_EL0.{CWG,ERG}
arm64: compat: Allow single-byte watchpoints on all addresses
drivers/perf: arm_pmu: Fix failure path in PM notifier
parisc: Fix build of compressed kernel even with debug enabled
parisc: Strip debug info from kernel before creating compressed vmlinuz
parisc: Add archclean Makefile target
cgroup: kselftest: relax fs_spec checks
s390/dasd: fix endless loop after read unit address configuration
loop: Fix mount(2) failure due to race with LOOP_SET_FD
mm/migrate.c: initialize pud_entry in migrate_vma()
ubsan: build ubsan.c more conservatively
mm: compaction: avoid 100% CPU usage during compaction when a task is killed
mm: migrate: fix reference check race between __find_get_block() and migration
mm: vmscan: check if mem cgroup is disabled or not before calling memcg slab
shrinker
ALSA: hda: Fix 1-minute detection delay when i915 module is not available
selinux: fix memory leak in policydb_init()
powerpc/kasan: fix early boot failure on PPC32
i2c: at91: fix clk_offset for sama5d2
i2c: at91: disable TXRDY interrupt after sending data
i2c: iproc: Fix i2c master read more than 63 bytes
eeprom: at24: make spd world-readable again
mtd: rawnand: micron: handle on-die "ECC-off" devices correctly
drm/nouveau: Only release VCPI slots on mode changes
IB/hfi1: Fix Spectre v1 vulnerability
gpiolib: fix incorrect IRQ requesting of an active-low lineevent
gpio: don't WARN() on NULL descs if gpiolib is disabled
gpiolib: Preserve desc->flags when setting state
mmc: mmc_spi: Enable stable writes
mmc: host: sdhci-sprd: Fix the missing pm_runtime_put_noidle()
mmc: meson-mx-sdio: Fix misuse of GENMASK macro
mmc: dw_mmc: Fix occasional hang after tuning on eMMC
fgraph: Remove redundant ftrace_graph_notrace_addr() test
dax: Fix missed wakeup in put_unlocked_entry()
Btrfs: fix race leading to fs corruption after transaction abort
Btrfs: fix incremental send failure after deduplication
tpm: Fix null pointer dereference on chip register error path
kbuild: modpost: include .*.cmd files only when targets exist
kbuild: initialize CLANG_FLAGS correctly in the top Makefile
kconfig: Clear "written" flag to avoid data loss
drm/nouveau/dmem: missing mutex_lock in error path
drm/nouveau: fix memory leak in nouveau_conn_reset()
bpf: Disable GCC -fgcse optimization for ___bpf_prog_run()
x86, boot: Remove multiple copy of static function sanitize_boot_params()
x86/paravirt: Fix callee-saved function ELF sizes
x86/kvm: Don't call kvm_spurious_fault() from .fixup
xen/pv: Fix a boot up hang revealed by int3 self test
crypto: ccp - Fix SEV_VERSION_GREATER_OR_EQUAL
stacktrace: Force USER_DS for stack_trace_save_user()
mm/hotplug: make remove_memory() interface usable
device-dax: fix memory and resource leak if hotplug fails
nds32: fix asm/syscall.h
ipc/mqueue.c: only perform resource calculation if user valid
drivers/rapidio/devices/rio_mport_cdev.c: NUL terminate
[Kernel-packages] [Bug 1839624] [NEW] eoan/linux: 5.2.0-12.13 -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1839623 (bionic/linux-hwe-edge) -- swm properties -- packages: lrm: linux-restricted-modules main: linux meta: linux-meta signed: linux-signed phase: Packaging phase-changed: Friday, 09. August 2019 13:55 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 trackers: bionic/linux-hwe-edge: bug 1839623 variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: In Progress ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Paolo Pisati (p-pisati) Status: In Progress ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Medium Status: Confirmed ** Tags: eoan kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2019.08.09-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: eoan kernel-release-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Eoan) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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
[Kernel-packages] [Bug 1862253] Re: focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker
** Summary changed: - focal/linux-kvm-5.4: -proposed tracker + focal/linux-kvm-5.4: 5.4.0-1001.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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862253 Title: focal/linux-kvm-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Confirmed Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862255 packages: main: linux-kvm-5.4 meta: linux-meta-kvm-5.4 phase: Ready for Promote to Proposed phase-changed: Thursday, 13. February 2020 14:16 UTC 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/1862253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1862252] Re: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker
** Summary changed: - focal/linux-gcp-5.4: -proposed tracker + focal/linux-gcp-5.4: 5.4.0-1001.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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1862252 Title: focal/linux-gcp-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1862255 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Packaging phase-changed: Thursday, 13. February 2020 14:45 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/1862252/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863589] [NEW] Focal update: v5.4.20 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.20 upstream stable release from git://git.kernel.org/ Linux 5.4.20 selinux: fall back to ref-walk if audit is required libertas: make lbs_ibss_join_existing() return error code on rates overflow libertas: don't exit from lbs_ibss_join_existing() with RCU read lock held mwifiex: Fix possible buffer overflows in mwifiex_cmd_append_vsie_tlv() mwifiex: Fix possible buffer overflows in mwifiex_ret_wmm_get_status() dmaengine: axi-dmac: add a check for devm_regmap_init_mmio clk: meson: g12a: fix missing uart2 in regmap table mfd: max77650: Select REGMAP_IRQ in Kconfig regmap: fix writes to non incrementing registers pinctrl: sh-pfc: r8a7778: Fix duplicate SDSELF_B and SD1_CLK_B pinctrl: sh-pfc: r8a77965: Fix DU_DOTCLKIN3 drive/bias control selinux: fix regression introduced by move_mount(2) syscall selinux: revert "stop passing MAY_NOT_BLOCK to the AVC upon follow_link" bcache: avoid unnecessary btree nodes flushing in btree_flush_write() dt-bindings: iio: adc: ad7606: Fix wrong maxItems value media: i2c: adv748x: Fix unsafe macros drivers: watchdog: stm32_iwdg: set WDOG_HW_RUNNING at probe crypto: caam/qi2 - fix typo in algorithm's driver name crypto: atmel-sha - fix error handling when setting hmac key crypto: artpec6 - return correct error code for failed setkey() crypto: testmgr - don't try to decrypt uninitialized buffers mtd: sharpslpart: Fix unsigned comparison to zero mtd: onenand_base: Adjust indentation in onenand_read_ops_nolock arm64: nofpsmid: Handle TIF_FOREIGN_FPSTATE flag cleanly KVM: arm64: Treat emulated TVAL TimerValue as a signed 32-bit integer KVM: arm64: pmu: Fix chained SW_INCR counters KVM: arm64: pmu: Don't increment SW_INCR if PMCR.E is unset KVM: arm: Make inject_abt32() inject an external abort instead KVM: arm: Fix DFSR setting for non-LPAE aarch32 guests KVM: arm/arm64: Fix young bit from mmu notifier arm64: ptrace: nofpsimd: Fail FP/SIMD regset operations arm64: cpufeature: Set the FP/SIMD compat HWCAP bits properly arm64: cpufeature: Fix the type of no FP/SIMD capability sched/uclamp: Fix a bug in propagating uclamp value in new cgroups ARM: 8949/1: mm: mark free_memmap as __init KVM: arm/arm64: vgic-its: Fix restoration of unmapped collections ARM: at91: pm: use of_device_id array to find the proper shdwc node ARM: at91: pm: use SAM9X60 PMC's compatible iommu/arm-smmu-v3: Populate VMID field for CMDQ_OP_TLBI_NH_VA powerpc/pseries: Allow not having ibm, hypertas-functions::hcall-multi-tce for DDW powerpc/pseries/vio: Fix iommu_table use-after-free refcount warning powerpc/papr_scm: Fix leaking 'bus_desc.provider_name' in some paths powerpc/ptdump: Only enable PPC_CHECK_WX with STRICT_KERNEL_RWX powerpc/ptdump: Fix W+X verification call in mark_rodata_ro() Revert "powerpc/pseries/iommu: Don't use dma_iommu_ops on secure guests" soc: qcom: rpmhpd: Set 'active_only' for active only power domains tools/power/acpi: fix compilation error ARM: dts: at91: sama5d3: define clock rate range for tcb1 ARM: dts: at91: sama5d3: fix maximum peripheral clock rates ARM: dts: meson8b: use the actual frequency for the GPU's 364MHz OPP ARM: dts: meson8: use the actual frequency for the GPU's 182.1MHz OPP arm64: dts: marvell: clearfog-gt-8k: fix switch cpu port node arm64: dts: renesas: r8a77990: ebisu: Remove clkout-lr-synchronous from sound ARM: dts: am43xx: add support for clkout1 clock ARM: dts: at91: Reenable UART TX pull-ups arm64: dts: uDPU: fix broken ethernet arm64: dts: qcom: msm8998: Fix tcsr syscon size platform/x86: intel_mid_powerbtn: Take a copy of ddata ARC: [plat-axs10x]: Add missing multicast filter number to GMAC node watchdog: qcom: Use platform_get_irq_optional() for bark irq rtc: cmos: Stop using shared IRQ rtc: hym8563: Return -EINVAL if the time is known to be invalid x86/boot: Handle malformed SRAT tables during early ACPI parsing NFSv4.0: nfs4_do_fsinfo() should not do implicit lease renewals NFSv4: try lease recovery on NFS4ERR_EXPIRED NFSv4: pnfs_roc() must use cred_fscmp() to compare creds NFS: Fix fix of show_nfs_errors NFS/pnfs: Fix pnfs_generic_prepare_to_resend_writes() NFS: Revalidate the file size on a fatal write error nfs: NFS_SWAP should depend on SWAP bpf, sockmap: Check update requirements after locking bpf: Improve bucket_log calculation logic selftests/bpf: Test freeing sockmap/sockhash with a socket in it bpf, sockhash: Synchronize_rcu before free'ing map bpf, sockmap: Don't sleep while holding RCU lock on tear-down bpftool: Don't crash on missing xlated program
[Kernel-packages] [Bug 1863588] [NEW] Focal update: v5.4.19 upstream stable release
Public bug reported:
SRU Justification
Impact:
The upstream process for stable tree updates is quite similar
in scope to the Ubuntu SRU process, e.g., each patch has to
demonstrably fix a bug, and each patch is vetted by upstream
by originating either directly from a mainline/stable Linux tree or
a minimally backported form of that patch. The following upstream
stable patches should be included in the Ubuntu kernel:
v5.4.19 upstream stable release
from git://git.kernel.org/
Linux 5.4.19
powerpc/kuap: Fix set direction in allow/prevent_user_access()
regulator fix for "regulator: core: Add regulator_is_equal() helper"
rxrpc: Fix service call disconnection
perf/core: Fix mlock accounting in perf_mmap()
clocksource: Prevent double add_timer_on() for watchdog_timer
x86/apic/msi: Plug non-maskable MSI affinity race
cifs: fail i/o on soft mounts if sessionsetup errors out
KVM: Play nice with read-only memslots when querying host page size
KVM: Use vcpu-specific gva->hva translation when querying host page size
KVM: nVMX: vmread should not set rflags to specify success in case of #PF
KVM: x86: fix overlap between SPTE_MMIO_MASK and generation
KVM: x86: Use gpa_t for cr2/gpa to fix TDP support on 32-bit KVM
KVM: x86: use CPUID to locate host page table reserved bits
KVM: x86/mmu: Apply max PA check for MMIO sptes to 32-bit KVM
drm/dp_mst: Remove VCPI while disabling topology mgr
btrfs: free block groups after free'ing fs trees
btrfs: use bool argument in free_root_pointers()
x86/timer: Don't skip PIT setup when APIC is disabled or in legacy mode
mfd: bd70528: Fix hour register mask
mfd: rn5t618: Mark ADC control register volatile
mfd: da9062: Fix watchdog compatible string
ASoC: Intel: skl_hda_dsp_common: Fix global-out-of-bounds bug
net/mlx5: Deprecate usage of generic TLS HW capability bit
net/mlx5: Fix deadlock in fs_core
drop_monitor: Do not cancel uninitialized work item
qed: Fix timestamping issue for L2 unicast ptp packets.
ipv6/addrconf: fix potential NULL deref in inet6_set_link_af()
taprio: Fix dropping packets when using taprio + ETF offloading
taprio: Use taprio_reset_tc() to reset Traffic Classes configuration
taprio: Add missing policy validation for flags
taprio: Fix still allowing changing the flags during runtime
taprio: Fix enabling offload with wrong number of traffic classes
net: macb: Limit maximum GEM TX length in TSO
net: macb: Remove unnecessary alignment check for TSO
net/mlx5: IPsec, fix memory leak at mlx5_fpga_ipsec_delete_sa_ctx
net/mlx5: IPsec, Fix esp modify function attribute
net: systemport: Avoid RBUF stuck in Wake-on-LAN mode
net: stmmac: fix a possible endless loop
net_sched: fix a resource leak in tcindex_set_parms()
net: mvneta: move rx_dropped and rx_errors in per-cpu stats
net: dsa: microchip: enable module autoprobe
net: dsa: bcm_sf2: Only 7278 supports 2Gb/sec IMP port
net: dsa: b53: Always use dev->vlan_enabled in b53_configure_vlan()
dpaa_eth: support all modes with rate adapting PHYs
devlink: report 0 after hitting end in region read
bonding/alb: properly access headers in bond_alb_xmit()
ASoC: sgtl5000: Fix VDDA and VDDIO comparison
regulator: core: Add regulator_is_equal() helper
ubifs: Fix memory leak from c->sup_node
ubi: Fix an error pointer dereference in error handling code
ubi: fastmap: Fix inverted logic in seen selfcheck
virtio_balloon: Fix memory leaks on errors in virtballoon_probe()
virtio-balloon: Fix memory leak when unloading while hinting is in progress
nfsd: Return the correct number of bytes written to the file
nfsd: fix jiffies/time_t mixup in LRU list
nfsd: fix delay timer on 32-bit architectures
IB/core: Fix ODP get user pages flow
IB/mlx5: Fix outstanding_pi index for GSI qps
net: tulip: Adjust indentation in {dmfe, uli526x}_init_module
net: smc911x: Adjust indentation in smc911x_phy_configure
ppp: Adjust indentation into ppp_async_input
NFC: pn544: Adjust indentation in pn544_hci_check_presence
drm: msm: mdp4: Adjust indentation in mdp4_dsi_encoder_enable
powerpc/44x: Adjust indentation in ibm4xx_denali_fixup_memsize
ext2: Adjust indentation in ext2_fill_super
phy: qualcomm: Adjust indentation in read_poll_timeout
mtd: spi-nor: Split mt25qu512a (n25q512a) entry into two
scsi: ufs: Recheck bkops level if bkops is disabled
scsi: qla4xxx: Adjust indentation in qla4xxx_mem_free
scsi: csiostor: Adjust indentation in csio_device_reset
scsi: qla2xxx: Fix the endianness of the qla82xx_get_fw_size() return type
ASoC: meson: axg-fifo: fix fifo threshold setup
percpu: Separate decrypted varaibles anytime encryption can be enabled
broken ping to ipv6 linklocal addresses on debian buster
fix up iter on short count in fuse_direct_io()
virtio-pci: check name when counting MSI-X vectors
virtio-balloon: initialize all vq callbacks
drm/amd/dm/mst: Ignore payload update failures
clk: tegra: Mark fuse clock as critical
mm/mmu_gather: invalidate TLB correctly on batch allocation failure
[Kernel-packages] [Bug 1861410] Re: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true - kernel-stable-master-bug: '1862255' + kernel-stable-master-bug: 1862255 packages: main: linux-raspi2-5.4 meta: linux-meta-raspi2-5.4 phase: Holding before Promote to Release phase-changed: Thursday, 30. January 2020 23:36 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs ** Tags removed: kernel-sru-derivative-of-1858880 ** Tags added: kernel-sru-derivative-of-1862255 ** Tags removed: kernel-sru-derivative-of-1862255 ** Tags added: kernel-sru-derivative-of-1862255 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1861410 Title: focal/linux-raspi2-5.4: 5.4.0-1001.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux package in Ubuntu: Invalid Status in linux source package in Focal: Invalid Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1862255 packages: main: linux-raspi2-5.4 meta: linux-meta-raspi2-5.4 phase: Holding before Promote to Release phase-changed: Thursday, 30. January 2020 23:36 UTC proposed-announcement-sent: true proposed-testing-requested: true variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1861410/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863657] [NEW] focal/linux-5.4: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-5.4 (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-5.4 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: focal kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2020.02.17-1 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: focal kernel-release-tracking-bug ** Also affects: linux-5.4 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-5.4 (Ubuntu Focal) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-5.4 (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2020.02.17-1 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided => Medium -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu.
[Kernel-packages] [Bug 1863656] [NEW] focal/linux-oracle-5.4: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863657 packages: lrm: linux-restricted-modules-oracle-5.4 main: linux-oracle-5.4 meta: linux-meta-oracle-5.4 signed: linux-signed-oracle-5.4 phase: Holding before Packaging phase-changed: Monday, 17. February 2020 17:30 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Status: Invalid ** Tags: focal kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2020.02.17-1 kernel-sru-derivative-of-1863657 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: focal kernel-release-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + var
[Kernel-packages] [Bug 1863653] [NEW] focal/linux-gcp-5.4: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863657 packages: lrm: linux-restricted-modules-gcp-5.4 main: linux-gcp-5.4 meta: linux-meta-gcp-5.4 signed: linux-signed-gcp-5.4 phase: Holding before Packaging phase-changed: Monday, 17. February 2020 17:30 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Status: Invalid ** Tags: focal kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2020.02.17-1 kernel-sru-derivative-of-1863657 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: focal kernel-release-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs
[Kernel-packages] [Bug 1863655] [NEW] focal/linux-kvm-5.4: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863657 packages: main: linux-kvm-5.4 meta: linux-meta-kvm-5.4 phase: Holding before Packaging phase-changed: Monday, 17. February 2020 17:30 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Status: Invalid ** Tags: focal kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2020.02.17-1 kernel-sru-derivative-of-1863657 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: focal kernel-release-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2020.02.17-1 ** 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: 1863657 variant: debs ** Tags added: kernel-sru-derivative-of-1863657 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-sru-workflow Importance: Undecided =>
[Kernel-packages] [Bug 1863651] [NEW] focal/linux-aws-5.4: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863657 packages: lrm: linux-restricted-modules-aws-5.4 main: linux-aws-5.4 meta: linux-meta-aws-5.4 phase: Holding before Packaging phase-changed: Monday, 17. February 2020 17:29 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Status: Invalid ** Tags: focal kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2020.02.17-1 kernel-sru-derivative-of-1863657 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: focal kernel-release-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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 -- + variant: debs ** Tags added: kernel-sru-cycle-d2020.02.17-1 ** 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: 1863657 variant: debs ** Tags added: kernel-sru-derivative-of-1863657 ** Changed in: kernel-sru-workflow Status: New => In Progress ** Changed in: kernel-
[Kernel-packages] [Bug 1863652] [NEW] focal/linux-azure-5.4: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863657 packages: lrm: linux-restricted-modules-azure-5.4 main: linux-azure-5.4 meta: linux-meta-azure-5.4 signed: linux-signed-azure-5.4 phase: Holding before Packaging phase-changed: Monday, 17. February 2020 17:30 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/stakeholder-signoff Importance: Medium Assignee: linux-azure stakeholder signoff (linux-azure-signoff) Status: New ** Affects: linux (Ubuntu) Importance: Medium Status: Invalid ** Affects: linux (Ubuntu Focal) Importance: Medium Status: Invalid ** Tags: focal kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2020.02.17-1 kernel-sru-derivative-of-1863657 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/stakeholder-signoff Importance: Undecided Status: New ** Tags added: focal kernel-release-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Focal) Status: New => Invalid ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/stakeholder-signoff Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/stakeholder-sign
[Kernel-packages] [Bug 1863650] [NEW] focal/linux-oem-5.4: -proposed tracker
Public bug reported: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1863657 packages: lrm: linux-restricted-modules-oem-5.4 main: linux-oem-5.4 meta: linux-meta-oem-5.4 signed: linux-signed-oem-5.4 phase: Holding before Packaging phase-changed: Monday, 17. February 2020 17:29 UTC reason: prepare-package: Holding -- waiting for master bug variant: debs ** Affects: kernel-sru-workflow Importance: Medium Status: In Progress ** Affects: kernel-sru-workflow/automated-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-meta Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/prepare-package-signed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-proposed Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: kernel-sru-workflow/promote-to-release Importance: Medium Assignee: Ubuntu Package Archive Administrators (ubuntu-archive) Status: New ** Affects: kernel-sru-workflow/regression-testing Importance: Medium Assignee: Canonical Kernel Team (canonical-kernel-team) Status: New ** Affects: linux-oem-5.4 (Ubuntu) Importance: Medium Status: Confirmed ** Affects: linux-oem-5.4 (Ubuntu Focal) Importance: Medium Status: Confirmed ** Tags: focal kernel-release-tracking-bug kernel-release-tracking-bug-live kernel-sru-cycle-d2020.02.17-1 kernel-sru-derivative-of-1863657 ** Also affects: kernel-sru-workflow/automated-testing Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-meta Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/prepare-package-signed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-proposed Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/promote-to-release Importance: Undecided Status: New ** Also affects: kernel-sru-workflow/regression-testing Importance: Undecided Status: New ** Tags added: focal kernel-release-tracking-bug ** Also affects: linux-oem-5.4 (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: linux-oem-5.4 (Ubuntu Focal) Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/automated-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-meta Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-meta Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/prepare-package-signed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/prepare-package-signed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-proposed Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-proposed Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: kernel-sru-workflow/promote-to-release Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/promote-to-release Assignee: (unassigned) => Ubuntu Package Archive Administrators (ubuntu-archive) ** Changed in: kernel-sru-workflow/regression-testing Importance: Undecided => Medium ** Changed in: kernel-sru-workflow/regression-testing Assignee: (unassigned) => Canonical Kernel Team (canonical-kernel-team) ** Changed in: linux-oem-5.4 (Ubuntu) Importance: Undecided => Medium ** Tags added: kernel-release-tracking-bug-live ** 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-workfl
[Kernel-packages] [Bug 1845860] Re: test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, but is missing or corrupted.)
FWIW, i'm having a similar problem on Focal 5.4: https://paste.ubuntu.com/p/CdFBr9QmHp/ ... libbpf: Error loading .BTF into kernel: -22. Failed to load SK_SKB verdict prog but i have clang-10: ii clang1:10.0-50~exp1 amd64 C, C++ and Objective-C compiler (LLVM based) ii clang-10 1:10.0.0-2ubuntu2 amd64 C, C++ and Objective-C compiler ii libclang-common-10-dev 1:10.0.0-2ubuntu2 amd64 Clang library - Common development package ii libclang-cpp10 1:10.0.0-2ubuntu2 amd64 C++ interface to the Clang library ii libclang1-10 1:10.0.0-2ubuntu2 amd64 C interface to the Clang library -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1845860 Title: test_maps in ubuntu_bpf failed to build on B-hwe-edge 5.3 (BTF is required, but is missing or corrupted.) Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Eoan: Incomplete Bug description: Issue found on 5.3 Bionic hwe: Running './test_maps' libbpf: BTF is required, but is missing or corrupted. Failed to load SK_SKB verdict prog To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1845860/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1871611] Re: multipath nvme, failed to install with multipath disabled install failed crashed with CalledProcessError
There were several nvme related commits in the last kernel upload
(Ubuntu-5.4.0-24.28), could you try it?
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1871611
Title:
multipath nvme, failed to install with multipath disabled install
failed crashed with CalledProcessError
Status in curtin:
Invalid
Status in subiquity:
New
Status in linux package in Ubuntu:
Confirmed
Bug description:
multipath nvme, failed to install with multipath disabled install
failed crashed with CalledProcessError
so trying to install with nvme_core.multipath=0 set on the cmdline, and that
fails.
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: subiquity (1641)
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
Uname: Linux 5.4.0-21-generic ppc64le
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu24
Architecture: ppc64el
CasperVersion: 1.443
CrashDB:
{
"impl": "launchpad",
"project": "subiquity",
"bug_pattern_url":
"http://people.canonical.com/~ubuntu-archive/bugpatterns/bugpatterns.xml";
}
Date: Wed Apr 8 11:35:20 2020
ExecutablePath: /snap/subiquity/1638/usr/bin/subiquity
InstallerLog: Error: [Errno 2] No such file or directory: 'logfile'
InterpreterPath: /snap/subiquity/1638/usr/bin/python3.6
LiveMediaBuild: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta ppc64el
(20200408)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 1d6b:0107 Linux Foundation USB Virtual Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
ProcAttrCurrent: snap.subiquity.subiquity (complain)
ProcCmdline: /snap/subiquity/1638/usr/bin/python3
/snap/subiquity/1638/usr/bin/subiquity
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=C.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: ip=dhcp
url=http://cdimage.ubuntu.com/hostname/daily-live/pending/focal-live-server-ppc64el.iso
subiquity-channel=latest/edge nvme_core.multipath=0
http_proxy=http://91.189.89.11:3128 --- quiet
ProcLoadAvg: 0.11 1.05 0.96 1/1380 14592
ProcLocks:
1: FLOCK ADVISORY WRITE 5503 00:18:751 0 EOF
2: POSIX ADVISORY WRITE 5198 00:18:647 0 EOF
3: POSIX ADVISORY WRITE 5520 00:18:760 0 EOF
ProcSwaps: Filename TypeSizeUsed
Priority
ProcVersion: Linux version 5.4.0-21-generic (buildd@bos02-ppc64el-028) (gcc
version 9.3.0 (Ubuntu 9.3.0-8ubuntu1)) #25-Ubuntu SMP Sat Mar 28 13:10:37 UTC
2020
Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal,
3.8.2-0ubuntu2
PythonDetails: N/A
SnapChannel:
SnapRevision: 1638
SnapUpdated: False
SnapVersion: 20.03.3+git132.a0dae13d
SourcePackage: subiquity
Title: install failed crashed with CalledProcessError
UpgradeStatus: No upgrade log present (probably fresh install)
UsingAnswers: False
VarLogDump_list: total 0
cpu_cores: Number of cores present = 32
cpu_coreson: Number of cores online = 32
cpu_smt: SMT=4
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1871611/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873315] Re: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does.
I've posted some test kernel with the RT_GROUP_SCHED option turned off here: https://people.canonical.com/~ppisati/lp1873315/ can you test it? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873315 Title: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. Status in linux package in Ubuntu: Confirmed Bug description: I'm using the xwax package on a Dell XPS 13 (9370) 20.04, which requires rtprio privileges: [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf @audio - rtprio 99 [daniel@reef ~ ]$ This worked fine for the past releases of Ubuntu up until the move from linux-image-5.4.0-21-generic to linux-image-5.4.0-24-generic. Today I'm seeing: Launching realtime thread to handle devices... sched_setscheduler: Operation not permitted Failed to get realtime priorities Booting the previous kernel makes it work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: daniel 2905 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 18:57:21 2020 InstallationDate: Installed on 2018-04-14 (733 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-24-generic N/A linux-backports-modules-5.4.0-24-generic N/A linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (39 days ago) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1873315] Re: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does.
** Description changed: + Impact: + + Software that requires RT priority is not working anymore since we + turned on RT_GROUP_SCHED: + + commit 9b039fc517876d312e7fa0955571101a299c91f5 + Author: Seth Forshee + Date: Mon Apr 6 07:11:44 2020 -0500 + + UBUNTU: [Config] CONFIG_RT_GROUP_SCHED=y + + This is wanted by docker, and the original reason for disabling + it no longer applied. Performance testing shows no noticible + impact when the option is enabled. + + + We already his this issue in the past (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731), but nowadays reverting RT_GROUP_SCHED back to off would regress Docker and since RT privileges are usually required by audio/multimedia software, it probably make sense to revert this change only for -lowlatency, and keep the rest as is. + + Fix: + + Apply the attached patch + + Regression potential: + + None, only -lowlatency is impacted, -generic doesn't change. + + -- + + I'm using the xwax package on a Dell XPS 13 (9370) 20.04, which requires rtprio privileges: - [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf + [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf @audio - rtprio 99 [daniel@reef ~ ]$ This worked fine for the past releases of Ubuntu up until the move from linux-image-5.4.0-21-generic to linux-image-5.4.0-24-generic. Today I'm seeing: Launching realtime thread to handle devices... sched_setscheduler: Operation not permitted Failed to get realtime priorities Booting the previous kernel makes it work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse: - USERPID ACCESS COMMAND - /dev/snd/controlC0: daniel 2905 F pulseaudio + Â USERPID ACCESS COMMAND + Â /dev/snd/controlC0: daniel 2905 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 18:57:21 2020 InstallationDate: Installed on 2018-04-14 (733 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Lsusb: - Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub - Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai - Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD - Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub + Â Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub + Â Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai + Â Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD + Â Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7 RelatedPackageVersions: - linux-restricted-modules-5.4.0-24-generic N/A - linux-backports-modules-5.4.0-24-generic N/A - linux-firmware1.187 + Â linux-restricted-modules-5.4.0-24-generic N/A + Â linux-backports-modules-5.4.0-24-generic N/A + Â linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (39 days ago) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. ** Patch added: "0001-UBUNTU-Config-lowlatency-turn-off-RT_GROUP_SCHED.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1873315/+attachment/5356084/+files/0001-UBUNTU-Config-lowlatency-turn-off-RT_GROUP_SCHED.patch ** Description changed: Impact: Software that requires RT priority is not working anymore since we turned on RT_GROUP_SCHED: commit 9b039fc517876d312e7fa0955571101a299c91f5 Author: Seth Forshee Date: Mon Apr 6 07:11:44 2020 -0500 UBUNTU: [Config] CONFIG_RT_GROUP_SCHED=y - + This is wanted by docker, and the original reason for disabling it no longer applied. Performance testing shows no noticible impact when the option is enabled. - - We already his this issue in the past (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731), but nowadays reverting RT_GROUP_SCHED back to off would regress Docker and since RT privileges are usually required by audio/multimedia software, it probably make sense to revert this change only for -lowlatency, and keep the rest as is. + We already had this issue in the p
[Kernel-packages] [Bug 1873315] Re: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does.
** Description changed: Impact: Software that requires RT priority is not working anymore since we turned on RT_GROUP_SCHED: commit 9b039fc517876d312e7fa0955571101a299c91f5 Author: Seth Forshee Date: Mon Apr 6 07:11:44 2020 -0500 UBUNTU: [Config] CONFIG_RT_GROUP_SCHED=y This is wanted by docker, and the original reason for disabling it no longer applied. Performance testing shows no noticible impact when the option is enabled. We already hit this issue in the past (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731), but nowadays reverting RT_GROUP_SCHED back to off would regress Docker and since RT privileges are usually required by audio/multimedia software, - it probably make sense to revert this change only for -lowlatency, and - keep the rest as is. + it probably make sense to revert this change only for -lowlatency (and + keep the rest as is) and encourage people to use -lowlatency if they hit + this problem. Fix: Apply the attached patch Regression potential: None, only -lowlatency is impacted, -generic doesn't change. -- I'm using the xwax package on a Dell XPS 13 (9370) 20.04, which requires rtprio privileges: [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf @audio - rtprio 99 [daniel@reef ~ ]$ This worked fine for the past releases of Ubuntu up until the move from linux-image-5.4.0-21-generic to linux-image-5.4.0-24-generic. Today I'm seeing: Launching realtime thread to handle devices... sched_setscheduler: Operation not permitted Failed to get realtime priorities Booting the previous kernel makes it work. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-image-5.4.0-24-generic 5.4.0-24.28 ProcVersionSignature: Ubuntu 5.4.0-24.28-generic 5.4.30 Uname: Linux 5.4.0-24-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 AudioDevicesInUse:  USERPID ACCESS COMMAND  /dev/snd/controlC0: daniel 2905 F pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Thu Apr 16 18:57:21 2020 InstallationDate: Installed on 2018-04-14 (733 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180409) Lsusb:  Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub  Bus 001 Device 003: ID 0489:e0a2 Foxconn / Hon Hai  Bus 001 Device 002: ID 0bda:58f4 Realtek Semiconductor Corp. Integrated_Webcam_HD  Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. XPS 13 9370 ProcFB: 0 i915drmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-24-generic root=UUID=0af0a12d-3b1e-4708-89c4-73f666ddc618 ro quiet splash vt.handoff=7 RelatedPackageVersions:  linux-restricted-modules-5.4.0-24-generic N/A  linux-backports-modules-5.4.0-24-generic N/A  linux-firmware1.187 SourcePackage: linux UpgradeStatus: Upgraded to focal on 2020-03-08 (39 days ago) dmi.bios.date: 02/21/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.2.1 dmi.board.name: 0F6P3V dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 9 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.2.1:bd02/21/2018:svnDellInc.:pnXPS139370:pvr:rvnDellInc.:rn0F6P3V:rvrA00:cvnDellInc.:ct9:cvr: dmi.product.family: XPS dmi.product.name: XPS 13 9370 dmi.product.sku: 07E6 dmi.sys.vendor: Dell Inc. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1873315 Title: 5.4.0-24.28 does not seem to apply rtprio, whereas -21 does. Status in linux package in Ubuntu: Confirmed Bug description: Impact: Software that requires RT priority is not working anymore since we turned on RT_GROUP_SCHED: commit 9b039fc517876d312e7fa0955571101a299c91f5 Author: Seth Forshee Date: Mon Apr 6 07:11:44 2020 -0500 UBUNTU: [Config] CONFIG_RT_GROUP_SCHED=y This is wanted by docker, and the original reason for disabling it no longer applied. Performance testing shows no noticible impact when the option is enabled. We already hit this issue in the past (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1284731), but nowadays reverting RT_GROUP_SCHED back to off would regress Docker and since RT privileges are usually required by audio/multimedia software, it probably make sense to revert this change only for -lowlatency (and keep the rest as is) and encourage people to use -lowlatency if they hit this problem. Fix: Apply the attached patch Regression potential: None, only -lowlatency is impacted, -generic doesn't change. -- I'm using the xwax package on a Dell XPS 13 (9370) 20.04, which requires rtprio privileges: [daniel@reef ~ ]$ sudo cat /etc/security/limits.d/audio.conf @audio - rtprio 99 [daniel@reef ~ ]$ This worked fine f
[Kernel-packages] [Bug 1871182] Re: [RTL810xE] No ethernet connection
Here is a test kernel, could you test it and tell us if it fixes your problem? https://people.canonical.com/~ppisati/lp1871182/ linux-image-unsigned-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb linux-modules-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb linux-modules-extra-5.4.0-25-generic_5.4.0-25.29~lp1871182_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1871182 Title: [RTL810xE] No ethernet connection Status in initramfs-tools package in Ubuntu: Confirmed Status in linux package in Ubuntu: Incomplete Bug description: ubuntu doesn't show cable plugged-in. Wifi is also intermittent. Errors in log with realtek. long boot up. No problems with live-USB or fresh install, only after update. sudo lspci -vnvn > lspci-vnvn.log pcilib: sysfs_read_vpd: read failed: Input/output error ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: linux-headers-5.4.0-22-generic 5.4.0-22.26 ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29 Uname: Linux 5.4.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu24 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: finisdiem 1332 F pulseaudio /dev/snd/controlC0: finisdiem 1332 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 6 10:49:03 2020 InstallationDate: Installed on 2020-04-01 (4 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200331) MachineType: Hewlett-Packard HP Pavilion g6 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.4.0-22-generic root=UUID=e2543a6c-bc86-40b3-a4dd-d9e29603fb52 ro quiet splash vt.handoff=7 RelatedPackageVersions: linux-restricted-modules-5.4.0-22-generic N/A linux-backports-modules-5.4.0-22-generic N/A linux-firmware1.187 RfKill: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 10/04/2012 dmi.bios.vendor: Insyde dmi.bios.version: F.15 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 1849 dmi.board.vendor: Hewlett-Packard dmi.board.version: 57.2F dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.15:bd10/04/2012:svnHewlett-Packard:pnHPPaviliong6NotebookPC:pvr088B1130591620100:rvnHewlett-Packard:rn1849:rvr57.2F:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=PAV dmi.product.name: HP Pavilion g6 Notebook PC dmi.product.sku: C2N51UA#ABA dmi.product.version: 088B1130591620100 dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/initramfs-tools/+bug/1871182/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1883553] [NEW] Groovy update: v5.7.2 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.7.2 upstream stable release from git://git.kernel.org/ Linux 5.7.2 uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned x86/speculation: Add Ivy Bridge to affected list x86/speculation: Add SRBDS vulnerability and mitigation documentation x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation x86/cpu: Add 'table' argument to cpu_matches() x86/cpu: Add a steppings field to struct x86_cpu_id nvmem: qfprom: remove incorrect write support CDC-ACM: heed quirk also in error handling staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK tty: hvc_console, fix crashes on parallel open/close vt: keyboard: avoid signed integer overflow in k_ascii serial: 8250: Enable 16550A variants by default on non-x86 usb: musb: jz4740: Prevent lockup when CONFIG_SMP is set usb: musb: Fix runtime PM imbalance on error usb: musb: start session in resume for host port iio: adc: stm32-adc: fix a wrong error message when probing interrupts iio:chemical:pms7003: Fix timestamp alignment and prevent data leak. iio: vcnl4000: Fix i2c swapped word reading. iio:chemical:sps30: Fix timestamp alignment USB: serial: ch341: fix lockup of devices with limited prescaler USB: serial: ch341: add basis for quirk detection USB: serial: option: add Telit LE910C1-EUX compositions USB: serial: usb_wwan: do not resubmit rx urb on fatal errors USB: serial: qcserial: add DW5816e QDL support ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Groovy) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Groovy) Importance: Undecided Status: 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/1883553 Title: Groovy update: v5.7.2 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Groovy: Confirmed 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: v5.7.2 upstream stable release from git://git.kernel.org/ Linux 5.7.2 uprobes: ensure that uprobe->offset and ->ref_ctr_offset are properly aligned x86/speculation: Add Ivy Bridge to affected list x86/speculation: Add SRBDS vulnerability and mitigation documentation x86/speculation: Add Special Register Buffer Data Sampling (SRBDS) mitigation x86/cpu: Add 'table' argument to cpu_matches() x86/cpu: Add a steppings field to struct x86_cpu_id nvmem: qfprom: remove incorrect write support CDC-ACM: heed quirk also in error handling staging: rtl8712: Fix IEEE80211_ADDBA_PARAM_BUF_SIZE_MASK tty: hvc_console, fix crashes on parallel open/close vt: keyboard: avoid signed integer overflow in k_ascii serial: 8250: Enable 16550A variants by default on non-x86 usb: musb: jz4740: Prevent lockup when CONFIG_SMP is set usb: musb: Fix runtime PM imbalance on error usb: musb: start session in resume for host port iio: adc: stm32-adc: fix a wrong error message when probing interrupts iio:chemical:pms7003: Fix timestamp alignment and prevent data leak. iio: vcnl4000: Fix i2c swapped word reading. iio:chemical:sps30: Fix timestamp alignment USB: serial: ch341: fix lockup of devices with limited prescaler USB: serial: ch341: add basis for quirk detection USB: serial: option: add Telit LE910C1-EUX compositions USB: serial: usb_wwan: do not resubmit rx urb on fatal errors USB: serial: qcserial: add DW5816e QDL support To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1883553/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1884730] [NEW] Groovy update: v5.7.5 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.7.5 upstream stable release from git://git.kernel.org/ Linux 5.7.5 perf symbols: Fix kernel maps for kcore and eBPF perf symbols: Fix debuginfo search for Ubuntu perf probe: Check address correctness by map instead of _etext perf probe: Fix to check blacklist address correctly perf probe: Do not show the skipped events f2fs: fix checkpoint=disable:%u%% f2fs: don't leak filename in f2fs_try_convert_inline_dir() w1: omap-hdq: fix interrupt handling which did show spurious timeouts w1: omap-hdq: fix return value to be -1 if there is a timeout w1: omap-hdq: cleanup to add missing newline for some dev_dbg mtd: rawnand: tmio: Fix the probe error path mtd: rawnand: mtk: Fix the probe error path mtd: rawnand: pasemi: Fix the probe error path mtd: rawnand: plat_nand: Fix the probe error path mtd: rawnand: sunxi: Fix the probe error path mtd: rawnand: oxnas: Fix the probe error path mtd: rawnand: socrates: Fix the probe error path mtd: rawnand: orion: Fix the probe error path mtd: rawnand: xway: Fix the probe error path mtd: rawnand: ingenic: Fix the probe error path mtd: rawnand: sharpsl: Fix the probe error path mtd: rawnand: diskonchip: Fix the probe error path mtd: rawnand: brcmnand: fix hamming oob layout mtd: rawnand: onfi: Fix redundancy detection check mtd: rawnand: Fix nand_gpio_waitrdy() pwm: jz4740: Enhance precision in calculation of duty cycle pwm: lpss: Fix get_state runtime-pm reference handling RISC-V: Don't mark init section as non-executable block: nr_sects_write(): Disable preemption on seqcount write sunrpc: clean up properly in gss_mech_unregister() sunrpc: svcauth_gss_register_pseudoflavor must reject duplicate registrations. virtio-balloon: Disable free page reporting if page poison reporting is not enabled kbuild: force to build vmlinux if CONFIG_MODVERSION=y powerpc/64s: Save FSCR to init_task.thread.fscr after feature init powerpc/64s: Don't let DT CPU features set FSCR_DSCR powerpc/32: Disable KASAN with pages bigger than 16k powerpc/kasan: Fix shadow pages allocation failure powerpc/kasan: Fix issues by lowering KASAN_SHADOW_END powerpc/32s: Fix another build failure with CONFIG_PPC_KUAP_DEBUG drivers/macintosh: Fix memleak in windfarm_pm112 driver ARM: dts: s5pv210: Set keep-power-in-suspend for SDHCI1 on Aries ARM: dts: at91: sama5d2_ptc_ek: fix vbus pin ARM: dts: exynos: Fix GPIO polarity for thr GalaxyS3 CM36651 sensor's bus jbd2: avoid leaking transaction credits when unreserving handle soc/tegra: pmc: Select GENERIC_PINCONF ARM: tegra: Correct PL310 Auxiliary Control Register initialization kernel/cpu_pm: Fix uninitted local in cpu_pm powerpc/fadump: Account for memory_limit while reserving memory powerpc/fadump: consider reserved ranges while reserving memory powerpc/fadump: use static allocation for reserved memory ranges memory: samsung: exynos5422-dmc: Fix tFAW timings alignment alpha: fix memory barriers so that they conform to the specification dm crypt: avoid truncating the logical block size software node: implement software_node_unregister() sparc64: fix misuses of access_process_vm() in genregs32_[sg]et() sparc32: fix register window handling in genregs32_[gs]et() gnss: sirf: fix error return code in sirf_probe() pinctrl: samsung: Save/restore eint_mask over suspend for EINT_TYPE GPIOs pinctrl: samsung: Correct setting of eint wakeup mask on s5pv210 power: supply: core: fix memory leak in HWMON error path power: supply: core: fix HWMON temperature labels power: vexpress: add suppress_bind_attrs to true iommu/vt-d: Allocate domain info for real DMA sub-devices iommu/vt-d: Only clear real DMA device's context entries EDAC/amd64: Add AMD family 17h model 60h PCI IDs hwmon: (k10temp) Add AMD family 17h model 60h PCI match igb: Report speed and duplex as unknown when device is runtime suspended clk: mediatek: assign the initial value to clk_init_data of mtk_mux usb: musb: mediatek: add reset FADDR to zero in reset interrupt handle media: ov5640: fix use of destroyed mutex b43_legacy: Fix connection problem with WPA3 b43: Fix connection problem with WPA3 b43legacy: Fix case where channel status is corrupted Bluetooth: hci_bcm: fix freeing not-requested IRQ Bluetooth: hci_bcm: respect IRQ polarity from DT serial: 8250: Avoid error message on reprobe media: cedrus: Program output format during each run clocksource/drivers/timer-microchip-pit64b: Select CONFIG_TIMER_OF clocksource: Remove obsolete ifdef carl9170: remove P2P_GO support irqchip/sifive-plic: Setup cpuhp once after boot CP
[Kernel-packages] [Bug 1882955] Re: LXD 4.2 broken on linux-kvm due to missing VLAN filtering
** Description changed: - This is another case of linux-kvm having unexplained differences - compared to linux-generic in areas that aren't related to hardware - drivers (see other bug we filed for missing nft). + [Description] + + Some VLAN options (BRIDGE_VLAN_FILTERING, and its dependencies + VLAN_8021Q*) were in a different state in Focal/kvm compared to + Focal/generic: LXD now depends on BRIDGE_VLAN_FILTERING and due to this + discrepancy it fails to work on the Focal/kvm kernel: fix it by aligning + the config with Focal/generic + + [Fix] + + Apply the attached config patch + + [Regression potential] + + Low, just some config changes already present in generic. + + --- + This is another case of linux-kvm having unexplained differences compared to linux-generic in areas that aren't related to hardware drivers (see other bug we filed for missing nft). This time, CPC is reporting that LXD no longer works on linux-kvm as we now set vlan filtering on our bridges to prevent containers from escaping firewalling through custom vlan tags. This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the generic kernel but is apparently missing on linux-kvm (I don't have any system running that kernel to confirm its config, but the behavior certainly matches that). We need this fixed in focal and groovy. ** Patch added: "0001-UBUNTU-Config-VLAN_8021Q-m-BRIDGE_VLAN_FILTERING-y.patch" https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1882955/+attachment/5386465/+files/0001-UBUNTU-Config-VLAN_8021Q-m-BRIDGE_VLAN_FILTERING-y.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1882955 Title: LXD 4.2 broken on linux-kvm due to missing VLAN filtering Status in linux-kvm package in Ubuntu: Triaged Bug description: [Description] Some VLAN options (BRIDGE_VLAN_FILTERING, and its dependencies VLAN_8021Q*) were in a different state in Focal/kvm compared to Focal/generic: LXD now depends on BRIDGE_VLAN_FILTERING and due to this discrepancy it fails to work on the Focal/kvm kernel: fix it by aligning the config with Focal/generic [Fix] Apply the attached config patch [Regression potential] Low, just some config changes already present in generic. --- This is another case of linux-kvm having unexplained differences compared to linux-generic in areas that aren't related to hardware drivers (see other bug we filed for missing nft). This time, CPC is reporting that LXD no longer works on linux-kvm as we now set vlan filtering on our bridges to prevent containers from escaping firewalling through custom vlan tags. This relies on CONFIG_BRIDGE_VLAN_FILTERING which is a built-in on the generic kernel but is apparently missing on linux-kvm (I don't have any system running that kernel to confirm its config, but the behavior certainly matches that). We need this fixed in focal and groovy. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-kvm/+bug/1882955/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1867903] [NEW] Focal update: v5.4.26 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.26 upstream stable release from git://git.kernel.org/ Linux 5.4.26 net/smc: cancel event worker during device removal net/smc: check for valid ib_client_data ipv6: restrict IPV6_ADDRFORM operation iommu/amd: Fix IOMMU AVIC not properly update the is_run bit in IRTE i2c: acpi: put device when verifying client fails iommu/vt-d: Ignore devices with out-of-spec domain number iommu/vt-d: Fix the wrong printing in RHSA parsing netfilter: nft_chain_nat: inet family is missing module ownership netfilter: nf_tables: dump NFTA_CHAIN_FLAGS attribute netfilter: nft_tunnel: add missing attribute validation for tunnels netfilter: nft_payload: add missing attribute validation for payload csum flags netfilter: cthelper: add missing attribute validation for cthelper perf bench futex-wake: Restore thread count default to online CPU count nl80211: add missing attribute validation for channel switch nl80211: add missing attribute validation for beacon report scanning nl80211: add missing attribute validation for critical protocol indication i2c: gpio: suppress error on probe defer iommu/vt-d: Fix RCU-list bugs in intel_iommu_init() driver code: clarify and fix platform device DMA mask allocation drm/i915/gvt: Fix unnecessary schedule timer when no vGPU exits pinctrl: core: Remove extra kref_get which blocks hogs being freed drm/i915/gvt: Fix dma-buf display blur issue on CFL virtio_ring: Fix mem leak with vring_new_virtqueue() pinctrl: imx: scu: Align imx sc msg structs to 4 pinctrl: meson-gxl: fix GPIOX sdio pins clk: imx8mn: Fix incorrect clock defines batman-adv: Don't schedule OGM for disabled interface iommu/vt-d: Fix a bug in intel_iommu_iova_to_phys() for huge page iommu/vt-d: Fix RCU list debugging warnings iommu/vt-d: dmar: replace WARN_TAINT with pr_warn + add_taint iommu/dma: Fix MSI reservation allocation x86/mce: Fix logic and comments around MSR_PPIN_CTL perf/amd/uncore: Replace manual sampling check with CAP_NO_INTERRUPT flag mt76: fix array overflow on receiving too many fragments for a packet i2c: designware-pci: Fix BUG_ON during device removal efi: Add a sanity check to efivar_store_raw() efi: Fix a race and a buffer overflow while reading efivars via sysfs x86/ioremap: Map EFI runtime services data as encrypted for SEV macintosh: windfarm: fix MODINFO regression fscrypt: don't evict dirty inodes after removing key blk-iocost: fix incorrect vtime comparison in iocg_is_idle() ipmi_si: Avoid spurious errors for optional IRQs s390/dasd: fix data corruption for thin provisioned devices fuse: fix stack use after return ARC: define __ALIGN_STR and __ALIGN symbols for ARC KVM: nVMX: avoid NULL pointer dereference with incorrect EVMCS GPAs KVM: x86: clear stale x86_emulate_ctxt->intercept value gfs2_atomic_open(): fix O_EXCL|O_CREAT handling on cold dcache cifs_atomic_open(): fix double-put on late allocation failure ktest: Add timeout for ssh sync testing pinctrl: falcon: fix syntax error mmc: sdhci-pci-gli: Enable MSI interrupt for GL975x drm/i915: Defer semaphore priority bumping to a workqueue drm/i915: be more solid in checking the alignment drm/amd/display: remove duplicated assignment to grph_obj_type workqueue: don't use wq_select_unbound_cpu() for bound works netfilter: x_tables: xt_mttg_seq_next should increase position index netfilter: xt_recent: recent_seq_next should increase position index netfilter: synproxy: synproxy_cpu_seq_next should increase position index netfilter: nf_conntrack: ct_cpu_seq_next should increase position index iommu/vt-d: quirk_ioat_snb_local_iommu: replace WARN_TAINT with pr_warn + add_taint virtio-blk: fix hw_queue stopped on arbitrary error iwlwifi: mvm: Do not require PHY_SKU NVM section for 3168 devices netfilter: nf_tables: fix infinite loop when expr is not available cgroup: Iterate tasks that did not finish do_exit() cgroup: cgroup_procs_next should increase position index net: phy: Avoid multiple suspends net: dsa: Don't instantiate phylink for CPU/DSA ports unless needed selftests/net/fib_tests: update addr_metric_test for peer route testing net/ipv6: remove the old peer route if change it to a new one net/ipv6: need update peer route when modify metric net: phy: fix MDIO bus PM PHY resuming net: phy: avoid clearing PHY interrupts twice in irq handler nfc: add missing attribute validation for vendor subcommand nfc: add missing attribute validation for deactivate target nfc: add missing attribute validation for SE API tipc: add missing attribute validation for MTU propert
[Kernel-packages] [Bug 1868538] [NEW] Focal update: v5.4.27 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.27 upstream stable release from git://git.kernel.org/ Linux 5.4.27 ipv4: ensure rcu_read_lock() in cipso_v4_error() ARM: 8961/2: Fix Kbuild issue caused by per-task stack protector GCC plugin HID: add ALWAYS_POLL quirk to lenovo pixart mouse HID: google: add moonball USB id mm: slub: add missing TID bump in kmem_cache_alloc_bulk() ARM: 8958/1: rename missed uaccess .fixup section ARM: 8957/1: VDSO: Match ARMv8 timer in cntvct_functional() net: qrtr: fix len of skb_put_padto in qrtr_node_enqueue blk-mq: insert flush request to the front of dispatch queue jbd2: fix data races at struct journal_head sfc: fix timestamp reconstruction at 16-bit rollover points net: rmnet: fix packet forwarding in rmnet bridge mode net: rmnet: fix bridge mode bugs net: rmnet: use upper/lower device infrastructure net: rmnet: do not allow to change mux id if mux id is duplicated net: rmnet: remove rcu_read_lock in rmnet_force_unassociate_device() net: rmnet: fix suspicious RCU usage net: rmnet: fix NULL pointer dereference in rmnet_changelink() net: rmnet: fix NULL pointer dereference in rmnet_newlink() hinic: fix a bug of rss configuration hinic: fix a bug of setting hw_ioctxt hinic: fix a irq affinity bug net: phy: mscc: fix firmware paths slip: not call free_netdev before rtnl_unlock in slip_open signal: avoid double atomic counter increments for user accounting kbuild: add dt_binding_check to PHONY in a correct place kbuild: add dtbs_check to PHONY drm/amdgpu: fix memory leak during TDR test(v2) blk-mq: insert passthrough request into hctx->dispatch directly net: ll_temac: Handle DMA halt condition caused by buffer underrun net: ll_temac: Fix RX buffer descriptor handling on GFP_ATOMIC pressure net: ll_temac: Add more error handling of dma_map_single() calls net: ll_temac: Fix race condition causing TX hang mac80211: rx: avoid RCU list traversal under mutex net: ks8851-ml: Fix IRQ handling and locking net: usb: qmi_wwan: restore mtu min/max values after raw_ip switch scsi: libfc: free response frame from GPN_ID cfg80211: check reg_rule for NULL in handle_channel_custom() tracing: Fix number printing bug in print_synth_event() selftests/rseq: Fix out-of-tree compilation HID: hid-bigbenff: fix race condition for scheduled work during removal HID: hid-bigbenff: call hid_hw_stop() in case of error HID: hid-bigbenff: fix general protection fault caused by double kfree HID: i2c-hid: add Trekstor Surfbook E11B to descriptor override ACPI: watchdog: Set default timeout in probe HID: apple: Add support for recent firmware on Magic Keyboards ACPI: watchdog: Allow disabling WDAT at boot drm/amdgpu: Fix TLB invalidation request when using semaphore netfilter: xt_hashlimit: unregister proc file before releasing mutex netfilter: hashlimit: do not use indirect calls during gc ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Focal) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Focal) Importance: Undecided Status: 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/1868538 Title: Focal update: v5.4.27 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Focal: Confirmed 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: v5.4.27 upstream stable release from git://git.kernel.org/ Linux 5.4.27 ipv4: ensure rcu_read_lock() in cipso_v4_error() ARM: 8961/2: Fix Kbuild issue caused by per-task stack protector GCC plugin HID: add ALWAYS_POLL quirk to lenovo pixart mouse HID: google: add moonball USB id mm: slub: add missing TID bump in kmem_cache_alloc_bulk() ARM: 8958/1: rename missed uaccess .fixup section ARM: 8957/1: VDSO: Match ARMv8 timer in cntvct_fu
[Kernel-packages] [Bug 1863657] Re: focal/linux-5.4: 5.4.0-15.18 -proposed tracker
** Summary changed: - focal/linux-5.4: -proposed tracker + focal/linux-5.4: 5.4.0-15.18 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-5.4 in Ubuntu. https://bugs.launchpad.net/bugs/1863657 Title: focal/linux-5.4: 5.4.0-15.18 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-5.4 package in Ubuntu: Confirmed Status in linux-5.4 source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- packages: lrm: linux-restricted-modules-5.4 main: linux-5.4 meta: linux-meta-5.4 signed: linux-signed-5.4 phase: Packaging phase-changed: Tuesday, 18. February 2020 11:21 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 trackers: focal/linux-5.4/pc-kernel: bug 1863646 focal/linux-5.4/pc-lowlatency-kernel: bug 1863647 focal/linux-aws-5.4: bug 1863651 focal/linux-azure-5.4: bug 1863652 focal/linux-gcp-5.4: bug 1863653 focal/linux-kvm-5.4: bug 1863655 focal/linux-oem-5.4: bug 1863650 focal/linux-oracle-5.4: bug 1863656 focal/linux-raspi2-5.4: bug 1863649 variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1863657/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863627] Re: Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem id [8086:0034] kernel oops in __iwl_mvm_mac_stop
You are running an old Eoan kernel: ... Package: linux-image-generic 5.3.0.29.33 ... can you update to the latest Eoan kernel and report if such a bug still exist? linux-image-generic | 5.3.0.40.34| eoan-updates | amd64, arm64, armhf, ppc64el, s390x -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863627 Title: Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem id [8086:0034] kernel oops in __iwl_mvm_mac_stop Status in linux package in Ubuntu: Confirmed Bug description: When booting, i always get this oops: [ 31.477399] iwlwifi :00:14.3: RF_KILL bit toggled to disable radio. [ 31.477400] iwlwifi :00:14.3: reporting RF_KILL (radio disabled) [ 31.490515] [ cut here ] [ 31.490516] UMAC scan UID 0 status was not cleaned [ 31.490540] WARNING: CPU: 3 PID: 954 at drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:1434 __iwl_mvm_mac_stop+0x129/0x130 [iwlmvm] [ 31.490540] Modules linked in: cmac nvidia_modeset(PO) snd_usb_audio snd_usbmidi_lib bnep aufs uvcvideo videobuf2_vmalloc videobuf2_memops overlay videobuf2_v4l2 videobuf2_common videodev mc btusb btrtl btbcm btintel bluetooth ecdh_generic ecc bbswitch(OE) binfmt_misc nls_iso8859_1 sof_pci_dev snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof x86_pkg_temp_thermal snd_sof_xtensa_dsp intel_powerclamp snd_soc_skl snd_soc_hdac_hda snd_hda_codec_hdmi snd_hda_ext_core coretemp snd_soc_skl_ipc snd_soc_sst_ipc iwlmvm snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match snd_soc_acpi mac80211 kvm snd_soc_core snd_hda_codec_realtek snd_compress irqbypass ac97_bus snd_hda_codec_generic libarc4 nvidia(PO) snd_pcm_dmaengine intel_cstate mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_pcm iwlwifi intel_rapl_perf thinkpad_acpi joydev input_leds processor_thermal_device idma64 nvram [ 31.490556] intel_rapl_common ucsi_acpi mei_me serio_raw ledtrig_audio typec_ucsi ipmi_devintf intel_wmi_thunderbolt wmi_bmof snd_seq_device ipmi_msghandler cfg80211 mei virt_dma intel_soc_dts_iosf intel_pch_thermal typec snd_timer snd int3403_thermal soundcore int340x_thermal_zone int3400_thermal mac_hid acpi_thermal_rel acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops aes_x86_64 crypto_simd drm cryptd glue_helper nvme psmouse e1000e i2c_i801 sdhci_pci nvme_core thunderbolt cqhci intel_lpss_pci sdhci intel_lpss wmi pinctrl_cannonlake video pinctrl_intel [last unloaded: nvidia_modeset] [ 31.490571] CPU: 3 PID: 954 Comm: kworker/3:3 Tainted: P OE 5.3.0-29-generic #31-Ubuntu [ 31.490572] Hardware name: LENOVO 20N3S1HU00/20N3S1HU00, BIOS N2IET77W (1.55 ) 10/17/2019 [ 31.490587] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [ 31.490591] RIP: 0010:__iwl_mvm_mac_stop+0x129/0x130 [iwlmvm] [ 31.490592] Code: 9b 04 00 00 74 0e 42 c7 84 a3 ec 1d 00 00 00 00 00 00 eb c0 44 89 e6 48 c7 c7 20 65 24 c2 c6 05 41 9b 04 00 01 e8 02 7d c9 e0 <0f> 0b eb d8 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 [ 31.490592] RSP: 0018:b8e0c0febc48 EFLAGS: 00010286 [ 31.490593] RAX: RBX: 937ac5bf1e28 RCX: 0006 [ 31.490594] RDX: 0007 RSI: 0082 RDI: 937acc2d7440 [ 31.490594] RBP: b8e0c0febc58 R08: 0498 R09: 0004 [ 31.490594] R10: R11: 0001 R12: [ 31.490595] R13: 937ac5bf1e90 R14: 937ac5bf1e28 R15: 937ac5bf3290 [ 31.490595] FS: () GS:937acc2c() knlGS: [ 31.490596] CS: 0010 DS: ES: CR0: 80050033 [ 31.490596] CR2: 5597e8a3b4e8 CR3: 00038d00a001 CR4: 003606e0 [ 31.490597] Call Trace: [ 31.490601] iwl_mvm_mac_stop+0xed/0x110 [iwlmvm] [ 31.490616] drv_stop+0x39/0x100 [mac80211] [ 31.490625] ieee80211_stop_device+0x46/0x50 [mac80211] [ 31.490632] ieee80211_do_stop+0x583/0x810 [mac80211] [ 31.490639] ieee80211_stop+0x1a/0x20 [mac80211] [ 31.490641] __dev_close_many+0xa5/0x120 [ 31.490641] dev_close_many+0x91/0x150 [ 31.490642] dev_close.part.0+0x4a/0x70 [ 31.490643] dev_close+0x18/0x20 [ 31.490649] cfg80211_shutdown_all_interfaces+0x77/0xd0 [cfg80211] [ 31.490653] cfg80211_rfkill_sync_work+0x2b/0x40 [cfg80211] [ 31.490655] process_one_work+0x1db/0x380 [ 31.490656] worker_thread+0x4d/0x400 [ 31.490657] kthread+0x104/0x140 [ 31.490658] ? process_one_work+0x380/0x380 [ 31.490659] ? kthread_park+0
[Kernel-packages] [Bug 1863675] Re: ASUS Zenbook 15 UX534FTC no sound
*** This bug is a duplicate of bug 1850439 ***
https://bugs.launchpad.net/bugs/1850439
** This bug has been marked a duplicate of bug 1850439
No sound on ASUS UX534FT
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1863675
Title:
ASUS Zenbook 15 UX534FTC no sound
Status in linux package in Ubuntu:
Confirmed
Bug description:
Hello everyone.
Recently I've bought a new laptop ASUS Zenbook 15 UX534FTC. I
installed Ubuntu 18.04 on it and everything works fine except sound.
When music plays - pavucontrol indicates that there is sound, but my
speakers are silent. No sound at all.
I googled that problem and found this topic:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1826645
I tried Petr Nosek's solution, but unfortunately sound not appeared.
What did I do:
1. Cloned kernel repo from git://kernel.ubuntu.com/ubuntu/ubuntu-bionic.git
2. Switched to branch Ubuntu-hwe-5.3.0-40.32_18.04.1
3. Added one line to the patch_realtek.c:
$ git diff
diff --git a/sound/pci/hda/patch_realtek.c b/sound/pci/hda/patch_realtek.c
index 1fc4cc89d62b..ba04bbe75ba0 100644
--- a/sound/pci/hda/patch_realtek.c
+++ b/sound/pci/hda/patch_realtek.c
@@ -7145,6 +7145,7 @@ static const struct snd_pci_quirk alc269_fixup_tbl[] = {
SND_PCI_QUIRK(0x1043, 0x18b1, "Asus MJ401TA",
ALC256_FIXUP_ASUS_HEADSET_MIC),
SND_PCI_QUIRK(0x1043, 0x1a13, "Asus G73Jw", ALC269_FIXUP_ASUS_G73JW),
SND_PCI_QUIRK(0x1043, 0x1a30, "ASUS X705UD", ALC256_FIXUP_ASUS_MIC),
+ SND_PCI_QUIRK(0x1043, 0x1a61, "Asus Zenbook UX534FTC",
ALC294_FIXUP_ASUS_SPK),
SND_PCI_QUIRK(0x1043, 0x1b13, "Asus U41SV", ALC269_FIXUP_INV_DMIC),
SND_PCI_QUIRK(0x1043, 0x1bbd, "ASUS Z550MA",
ALC255_FIXUP_ASUS_MIC_NO_PRESENCE),
SND_PCI_QUIRK(0x1043, 0x1c23, "Asus X55U",
ALC269_FIXUP_LIMIT_INT_MIC_BOOST),
4. Typed 2 commands:
fakeroot debian/rules clean
fakeroot debian/rules binary-headers binary-generic binary-perarch
5. Kernel build was successful and then I've installed it
6. Rebooted my laptop and booted into the new kernel
Sound not appeared after these steps. Pavucontrol indicates that
everything is OK, but speakers not producing any sound. Screenshot in
attachment.
My hwinfo:
$ hwinfo --sound
18: PCI 1f.3: 0403 Audio device
[Created at pci.378]
Unique ID: nS1_.9G5mT1GK4nF
SysFS ID: /devices/pci:00/:00:1f.3
SysFS BusID: :00:1f.3
Hardware Class: sound
Model: "Intel Audio device"
Vendor: pci 0x8086 "Intel Corporation"
Device: pci 0x02c8
SubVendor: pci 0x1043 "ASUSTeK Computer Inc."
SubDevice: pci 0x1a61
Driver: "snd_hda_intel"
Driver Modules: "snd_hda_intel"
Memory Range: 0xc4318000-0xc431bfff (rw,non-prefetchable)
Memory Range: 0xc410-0xc41f (rw,non-prefetchable)
IRQ: 148 (635 events)
Module Alias: "pci:v8086d02C8sv1043sd1A61bc04sc03i80"
Driver Info #0:
Driver Status: snd_hda_intel is active
Driver Activation Cmd: "modprobe snd_hda_intel"
Driver Info #1:
Driver Status: snd_soc_skl is active
Driver Activation Cmd: "modprobe snd_soc_skl"
Driver Info #2:
Driver Status: sof_pci_dev is active
Driver Activation Cmd: "modprobe sof_pci_dev"
Config Status: cfg=new, avail=yes, need=no, active=unknown
Seems like a bug. Need solution.
P.S. Sorry for my English.
---
ProblemType: Bug
ApportVersion: 2.20.9-0ubuntu7.9
Architecture: amd64
AudioDevicesInUse:
USERPID ACCESS COMMAND
/dev/snd/controlC0: polina29075 F pulseaudio
DistroRelease: Ubuntu 18.04
InstallationDate: Installed on 2020-02-15 (2 days ago)
InstallationMedia: Ubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64
(20200203.1)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 13d3:56cb IMC Networks
Bus 001 Device 002: ID 248a:8367
Bus 001 Device 004: ID 8087:0026 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: ASUSTeK COMPUTER INC. ZenBook UX534FTC_UX534FT
NonfreeKernelModules: nvidia_modeset nvidia
Package: linux (not installed)
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.3.0-40-generic
root=UUID=08d45cb1-9899-4e9a-86c9-3e23964cf2ec ro quiet splash vt.handoff=1
ProcVersionSignature: Ubuntu 5.3.0-40.32~18.04.1-generic 5.3.18
RelatedPackageVersions:
linux-restricted-modules-5.3.0-40-generic N/A
linux-backports-modules-5.3.0-40-generic N/A
linux-firmware1.173.14
Tags: bionic
Uname: Linux 5.3.0-40-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
_MarkForUpload: True
dmi.bios.date: 12/16/2019
[Kernel-packages] [Bug 1863627] Re: Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem id [8086:0034] kernel oops in __iwl_mvm_mac_stop
** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863627 Title: Intel Dual Band Wireless AC 9560 [8086:9df0] subsystem id [8086:0034] kernel oops in __iwl_mvm_mac_stop Status in linux package in Ubuntu: Incomplete Bug description: When booting, i always get this oops: [ 31.477399] iwlwifi :00:14.3: RF_KILL bit toggled to disable radio. [ 31.477400] iwlwifi :00:14.3: reporting RF_KILL (radio disabled) [ 31.490515] [ cut here ] [ 31.490516] UMAC scan UID 0 status was not cleaned [ 31.490540] WARNING: CPU: 3 PID: 954 at drivers/net/wireless/intel/iwlwifi/mvm/mac80211.c:1434 __iwl_mvm_mac_stop+0x129/0x130 [iwlmvm] [ 31.490540] Modules linked in: cmac nvidia_modeset(PO) snd_usb_audio snd_usbmidi_lib bnep aufs uvcvideo videobuf2_vmalloc videobuf2_memops overlay videobuf2_v4l2 videobuf2_common videodev mc btusb btrtl btbcm btintel bluetooth ecdh_generic ecc bbswitch(OE) binfmt_misc nls_iso8859_1 sof_pci_dev snd_sof_intel_hda_common snd_sof_intel_hda snd_sof_intel_byt snd_sof_intel_ipc snd_sof x86_pkg_temp_thermal snd_sof_xtensa_dsp intel_powerclamp snd_soc_skl snd_soc_hdac_hda snd_hda_codec_hdmi snd_hda_ext_core coretemp snd_soc_skl_ipc snd_soc_sst_ipc iwlmvm snd_soc_sst_dsp kvm_intel snd_soc_acpi_intel_match snd_soc_acpi mac80211 kvm snd_soc_core snd_hda_codec_realtek snd_compress irqbypass ac97_bus snd_hda_codec_generic libarc4 nvidia(PO) snd_pcm_dmaengine intel_cstate mei_hdcp intel_rapl_msr snd_seq_midi snd_seq_midi_event snd_rawmidi snd_hda_intel snd_hda_codec snd_hda_core snd_hwdep snd_seq snd_pcm iwlwifi intel_rapl_perf thinkpad_acpi joydev input_leds processor_thermal_device idma64 nvram [ 31.490556] intel_rapl_common ucsi_acpi mei_me serio_raw ledtrig_audio typec_ucsi ipmi_devintf intel_wmi_thunderbolt wmi_bmof snd_seq_device ipmi_msghandler cfg80211 mei virt_dma intel_soc_dts_iosf intel_pch_thermal typec snd_timer snd int3403_thermal soundcore int340x_thermal_zone int3400_thermal mac_hid acpi_thermal_rel acpi_pad sch_fq_codel parport_pc ppdev lp parport ip_tables x_tables autofs4 dm_crypt hid_generic usbhid hid i915 crct10dif_pclmul crc32_pclmul ghash_clmulni_intel i2c_algo_bit drm_kms_helper syscopyarea aesni_intel sysfillrect sysimgblt fb_sys_fops aes_x86_64 crypto_simd drm cryptd glue_helper nvme psmouse e1000e i2c_i801 sdhci_pci nvme_core thunderbolt cqhci intel_lpss_pci sdhci intel_lpss wmi pinctrl_cannonlake video pinctrl_intel [last unloaded: nvidia_modeset] [ 31.490571] CPU: 3 PID: 954 Comm: kworker/3:3 Tainted: P OE 5.3.0-29-generic #31-Ubuntu [ 31.490572] Hardware name: LENOVO 20N3S1HU00/20N3S1HU00, BIOS N2IET77W (1.55 ) 10/17/2019 [ 31.490587] Workqueue: events cfg80211_rfkill_sync_work [cfg80211] [ 31.490591] RIP: 0010:__iwl_mvm_mac_stop+0x129/0x130 [iwlmvm] [ 31.490592] Code: 9b 04 00 00 74 0e 42 c7 84 a3 ec 1d 00 00 00 00 00 00 eb c0 44 89 e6 48 c7 c7 20 65 24 c2 c6 05 41 9b 04 00 01 e8 02 7d c9 e0 <0f> 0b eb d8 0f 1f 00 0f 1f 44 00 00 55 48 89 e5 41 57 41 56 41 55 [ 31.490592] RSP: 0018:b8e0c0febc48 EFLAGS: 00010286 [ 31.490593] RAX: RBX: 937ac5bf1e28 RCX: 0006 [ 31.490594] RDX: 0007 RSI: 0082 RDI: 937acc2d7440 [ 31.490594] RBP: b8e0c0febc58 R08: 0498 R09: 0004 [ 31.490594] R10: R11: 0001 R12: [ 31.490595] R13: 937ac5bf1e90 R14: 937ac5bf1e28 R15: 937ac5bf3290 [ 31.490595] FS: () GS:937acc2c() knlGS: [ 31.490596] CS: 0010 DS: ES: CR0: 80050033 [ 31.490596] CR2: 5597e8a3b4e8 CR3: 00038d00a001 CR4: 003606e0 [ 31.490597] Call Trace: [ 31.490601] iwl_mvm_mac_stop+0xed/0x110 [iwlmvm] [ 31.490616] drv_stop+0x39/0x100 [mac80211] [ 31.490625] ieee80211_stop_device+0x46/0x50 [mac80211] [ 31.490632] ieee80211_do_stop+0x583/0x810 [mac80211] [ 31.490639] ieee80211_stop+0x1a/0x20 [mac80211] [ 31.490641] __dev_close_many+0xa5/0x120 [ 31.490641] dev_close_many+0x91/0x150 [ 31.490642] dev_close.part.0+0x4a/0x70 [ 31.490643] dev_close+0x18/0x20 [ 31.490649] cfg80211_shutdown_all_interfaces+0x77/0xd0 [cfg80211] [ 31.490653] cfg80211_rfkill_sync_work+0x2b/0x40 [cfg80211] [ 31.490655] process_one_work+0x1db/0x380 [ 31.490656] worker_thread+0x4d/0x400 [ 31.490657] kthread+0x104/0x140 [ 31.490658] ? process_one_work+0x380/0x380 [ 31.490659] ? kthread_park+0x80/0x80 [ 31.490660] ret_from_fork+0x1f/0x40 [ 31.490661] ---[ end trace 78f4dd0c5ace42be ]--- [ 34.559852] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control:
[Kernel-packages] [Bug 1863752] Re: Removal of linux-image-5.3.0-29-generic fails
Looks like a grub config syntax error, definitely not a kernel issue: ... Found Debian GNU/Linux 10 (buster) on /dev/sdc2 error: syntax error. error: Incorrect command. error: syntax error. Syntax error at line 178 Syntax errors are detected in generated GRUB config file. Ensure that there are no errors in /etc/default/grub and /etc/grub.d/* files or please file a bug report with /boot/grub/grub.cfg.new file attached. ... ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863752 Title: Removal of linux-image-5.3.0-29-generic fails Status in linux package in Ubuntu: Incomplete Bug description: Attempting to update the kernel from linux-image-5.3.0-29-generic to 5.3.0-40-generic on a 19.10 system with default ZFS root and boot keeps failing. The latter has installed (for some value of install) but the former can't be removed and the system is left running that older kernel. Possibly due to some issue with setting up the next boot image under ZFS? root@foo:~# apt-get upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done The following packages will be REMOVED linux-image-5.3.0-29-generic 0 to upgrade, 0 to newly install, 1 to remove and 0 not to upgrade. 2 not fully installed or removed. After this operation, 11.4 MB disk space will be freed. Do you want to continue? [Y/n] Y (Reading database ... 228252 files and directories currently installed.) Removing linux-image-5.3.0-29-generic (5.3.0-29.31) ... /etc/kernel/postrm.d/initramfs-tools: update-initramfs: Deleting /boot/initrd.img-5.3.0-29-generic /etc/kernel/postrm.d/zz-update-grub: Sourcing file `/etc/default/grub' Sourcing file `/etc/default/grub.d/init-select.cfg' Generating grub configuration file ... Found linux image: vmlinuz-5.3.0-18-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-18-generic in rpool/ROOT/ubuntu_hgbr1h Found linux image: vmlinuz-5.3.0-26-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-26-generic in rpool/ROOT/ubuntu_hgbr1h Found linux image: vmlinuz-5.3.0-40-generic in rpool/ROOT/ubuntu_hgbr1h Found initrd image: initrd.img-5.3.0-40-generic in rpool/ROOT/ubuntu_hgbr1h Found memtest86+ image: /BOOT/ubuntu_hgbr1h@/memtest86+.elf Found memtest86+ image: /BOOT/ubuntu_hgbr1h@/memtest86+.bin device-mapper: reload ioctl on osprober-linux-sda7 failed: Device or resource busy Command failed. device-mapper: reload ioctl on osprober-linux-sdb7 failed: Device or resource busy Command failed. Found Debian GNU/Linux 10 (buster) on /dev/sdc2 error: syntax error. error: Incorrect command. error: syntax error. Syntax error at line 178 Syntax errors are detected in generated GRUB config file. Ensure that there are no errors in /etc/default/grub and /etc/grub.d/* files or please file a bug report with /boot/grub/grub.cfg.new file attached. run-parts: /etc/kernel/postrm.d/zz-update-grub exited with return code 1 dpkg: error processing package linux-image-5.3.0-29-generic (--remove): installed linux-image-5.3.0-29-generic package post-removal script subprocess returned error exit status 1 dpkg: too many errors, stopping Errors were encountered while processing: linux-image-5.3.0-29-generic Processing was halted because there were too many errors. E: Sub-process /usr/bin/dpkg returned an error code (1) root@foo:~# lsb_release -rd Description: Ubuntu 19.10 Release: 19.10 root@foo:~# apt-cache policy linux-image-5.3.0-29-generic linux-image-5.3.0-29-generic: Installed: 5.3.0-29.31 Candidate: 5.3.0-29.31 Version table: *** 5.3.0-29.31 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status root@foo:~# apt-cache policy linux-image-5.3.0-40-generic linux-image-5.3.0-40-generic: Installed: 5.3.0-40.32 Candidate: 5.3.0-40.32 Version table: *** 5.3.0-40.32 500 500 http://gb.archive.ubuntu.com/ubuntu eoan-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu eoan-security/main amd64 Packages 100 /var/lib/dpkg/status root@foo:~# uname -a Linux foo 5.3.0-26-generic #28-Ubuntu SMP Wed Dec 18 05:37:46 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux ProblemType: Bug DistroRelease: Ubuntu 19.10 Package: linux-image-5.3.0-29-generic 5.3.0-29.31 ProcVersionSignature: Ubuntu 5.3.0-26.28-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 NonfreeKernelModules: nvidia zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu8.4 Architecture: amd64 AudioDevicesInUse: Error: command ['fuse
[Kernel-packages] [Bug 1863761] Re: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel
Which kernel version are you using? Please run "apport-collect 1863761" on your laptop. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863761 Title: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel Status in linux package in Ubuntu: Incomplete Bug description: CONFIG_HID_SENSOR_HUB=m makes keyboard unusable on Lenovo Yoga C630 WOS with -snapdragon kernel. More details is here: https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000163.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000164.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000165.html https://lists.linaro.org/pipermail/aarch64-laptops/2020-February/000166.html To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863761/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863810] Re: Focal Fossa (20.04) feature request - Enable CONFIG_X86_UV
Michael, could you check if this kernel fixes your issue? https://people.canonical.com/~ppisati/lp1863810/ linux-buildinfo-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb linux-cloud-tools-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb linux-headers-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb linux-image-unsigned-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb linux-modules-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb linux-modules-extra-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb linux-tools-5.4.0-15-generic_5.4.0-15.18~lp1863810_amd64.deb -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863810 Title: Focal Fossa (20.04) feature request - Enable CONFIG_X86_UV Status in linux package in Ubuntu: Incomplete Bug description: Superdome Flex depends on CONFIG_X86_UV config option to enable platform support and currently it is not enabled on Ubuntu. The ask is to formally request to enable this option in Ubuntu to allow Superdome Flex to work properly. Specifically, this small change "CONFIG_X86_UV=y" is needed in the default config file. linux:/images # grep CONFIG_X86_UV x86_64-ubuntu-19.04/boot/config* # CONFIG_X86_UV is not set To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863810/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1861237] Re: Audio not detected on X1 Yoga 4th
Could you test if latest Focal kernel and firmware fix this issue? linux-image-generic | 5.4.0.14.17 linux-firmware | 1.186 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1861237 Title: Audio not detected on X1 Yoga 4th Status in linux package in Ubuntu: Confirmed Status in linux-firmware package in Ubuntu: New Bug description: I'm testing out Kubuntu 20.04 on my 4th gen ThinkPad X1 Yoga, and Ubuntu's not detecting audio from it at all. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (9 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120) Package: pulseaudio 1:13.0-3ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu16 Architecture: amd64 AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CurrentDesktop: KDE DistroRelease: Ubuntu 20.04 InstallationDate: Installed on 2020-01-25 (9 days ago) InstallationMedia: Kubuntu 20.04 LTS "Focal Fossa" - Alpha amd64 (20200120) Package: pulseaudio 1:13.0-3ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.4.0-12.15-generic 5.4.8 Tags: focal Uname: Linux 5.4.0-12-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/15/2020 dmi.bios.vendor: LENOVO dmi.bios.version: N2QET19W (1.13 ) dmi.board.asset.tag: Not Available dmi.board.name: 20SA0002US dmi.board.vendor: LENOVO dmi.board.version: SDK0J40697 WIN dmi.chassis.asset.tag: No Asset Information dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: None dmi.modalias: dmi:bvnLENOVO:bvrN2QET19W(1.13):bd01/15/2020:svnLENOVO:pn20SA0002US:pvrThinkPadX1Yoga4th:rvnLENOVO:rn20SA0002US:rvrSDK0J40697WIN:cvnLENOVO:ct31:cvrNone: dmi.product.family: ThinkPad X1 Yoga 4th dmi.product.name: 20SA0002US dmi.product.sku: LENOVO_MT_20SA_BU_Think_FM_ThinkPad X1 Yoga 4th dmi.product.version: ThinkPad X1 Yoga 4th dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1861237/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1863864] Re: Lenovo e590 laptop hangs when connect to dock station with kernel 5.3.0+
Disconnect the laptop from the docking station, boot into the problematic kernel, and run `apport-collect 1863864` again. ** Changed in: linux (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1863864 Title: Lenovo e590 laptop hangs when connect to dock station with kernel 5.3.0+ Status in linux package in Ubuntu: Incomplete Bug description: I have Lenovo ThinkPad e590, which connected via USB Type-C to Lenovo Dock station. To doc station connected network cable, USB mouse, keyboard, power, and two monitors. On previous kernel versions (include 5.0.0-37) it works ok. But after update to any version on 5.3.0 I can't use it with doc station: 1) If I boot with connected Dock station then 2 external monitors are black and laptop monitor the same black 2) If I boot without connected Dock station then Laptop works ok. At the moment when I connect USB Type-C cable to laptop screen become black, and 2 external monitors show the image, but it hangs: Â I can move the mouse cursor but all other UI hangs, even the clock does not work, only REISUB helps. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: andrii 1548 F pulseaudio /dev/snd/controlC1: andrii 1548 F pulseaudio /dev/snd/controlC0: andrii 1548 F pulseaudio CurrentDesktop: X-Cinnamon DistroRelease: Linux Mint 19.1 InstallationDate: Installed on 2019-07-26 (207 days ago) InstallationMedia: Linux Mint 19.1 "Tessa" - Release amd64 20181217 MachineType: LENOVO 20NB000YRT Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-37-generic root=/dev/mapper/vg0-root ro cryptops=target=vg0-root,source=/dev/disk/by-uuid/737a3cbd-a798-45e6-88e3-602d767eae77,lvm=vg0 ProcVersionSignature: Ubuntu 5.0.0-37.40~18.04.1-generic 5.0.21 RelatedPackageVersions: linux-restricted-modules-5.0.0-37-generic N/A linux-backports-modules-5.0.0-37-generic N/A linux-firmware1.173.14 Tags: tessa Uname: Linux 5.0.0-37-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip kvm lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 01/22/2019 dmi.bios.vendor: LENOVO dmi.bios.version: R0YET27W (1.10 ) dmi.board.asset.tag: Not Available dmi.board.name: 20NB000YRT 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:bvrR0YET27W(1.10):bd01/22/2019:svnLENOVO:pn20NB000YRT:pvrThinkPadE590:rvnLENOVO:rn20NB000YRT:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone: dmi.product.family: ThinkPad E590 dmi.product.name: 20NB000YRT dmi.product.sku: LENOVO_MT_20NB_BU_SMB_FM_ThinkPad E590 dmi.product.version: ThinkPad E590 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1863864/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864083] Re: focal/linux-kvm: 5.4.0-1002.2 -proposed tracker
** Summary changed: - focal/linux-kvm: -proposed tracker + focal/linux-kvm: 5.4.0-1002.2 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1864083 Title: focal/linux-kvm: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Friday, 21. February 2020 10:52 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1864083/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864082] Re: focal/linux-gcp: 5.4.0-1002.2 -proposed tracker
** Summary changed: - focal/linux-gcp: -proposed tracker + focal/linux-gcp: 5.4.0-1002.2 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1864082 Title: focal/linux-gcp: 5.4.0-1002.2 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1864085 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Friday, 21. February 2020 16:51 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/1864082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1864488] [NEW] Focal update: 5.4.22 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: 5.4.22 upstream stable release from git://git.kernel.org/ Linux 5.4.22 rtc: Kconfig: select REGMAP_I2C when necessary bcache: properly initialize 'path' and 'err' in register_bcache() drm/amdgpu/display: handle multiple numbers of fclks in dcn_calcs.c (v2) s390/pci: Recover handle in clp_set_pci_fn() mlxsw: spectrum_dpipe: Add missing error path fuse: don't overflow LLONG_MAX with end offset virtio_balloon: prevent pfn array overflow cifs: log warning message (once) if out of disk space i40e: Relax i40e_xsk_wakeup's return value when PF is busy help_next should increase position index NFS: Fix memory leaks drm/amdgpu/smu10: fix smu10_get_clock_by_type_with_voltage drm/amdgpu/smu10: fix smu10_get_clock_by_type_with_latency brd: check and limit max_part par microblaze: Prevent the overflow of the start asm-generic/tlb: add missing CONFIG symbol iwlwifi: mvm: Check the sta is not NULL in iwl_mvm_cfg_he_sta() iwlwifi: mvm: Fix thermal zone registration nvme-pci: remove nvmeq->tags nvmet: Pass lockdep expression to RCU lists irqchip/gic-v3-its: Reference to its_invall_cmd descriptor when building INVALL bcache: fix incorrect data type usage in btree_flush_write() bcache: explicity type cast in bset_bkey_last() bcache: fix memory corruption in bch_cache_accounting_clear() reiserfs: prevent NULL pointer dereference in reiserfs_insert_item() lib/scatterlist.c: adjust indentation in __sg_alloc_table ocfs2: fix a NULL pointer dereference when call ocfs2_update_inode_fsync_trans() ocfs2: make local header paths relative to C files btrfs: do not do delalloc reservation under page lock powerpc: Do not consider weak unresolved symbol relocations as bad radeon: insert 10ms sleep in dce5_crtc_load_lut trigger_next should increase position index ftrace: fpid_next() should increase position index char: hpet: Fix out-of-bounds read bug drm/nouveau/disp/nv50-: prevent oops when no channel method map provided irqchip/gic-v3: Only provision redistributors that are enabled in ACPI drm/amd/display: do not allocate display_mode_lib unnecessarily rbd: work around -Wuninitialized warning ceph: check availability of mds cluster on mount after wait timeout powerpc/mm: Don't log user reads to 0x bpf: map_seq_next should always increase position index cifs: fix NULL dereference in match_prepath cifs: Fix mount options set in automount cifs: fix unitialized variable poential problem with network I/O cache lock patch iwlegacy: ensure loop counter addr does not wrap and cause an infinite loop rtw88: fix potential NULL skb access in TX ISR hostap: Adjust indentation in prism2_hostapd_add_sta ALSA: usb-audio: add quirks for Line6 Helix devices fw>=2.82 ARM: 8951/1: Fix Kexec compilation issue. selftests/eeh: Bump EEH wait time to 60s powerpc/pseries/lparcfg: Fix display of Maximum Memory jbd2: make sure ESHUTDOWN to be recorded in the journal superblock jbd2: switch to use jbd2_journal_abort() when failed to submit the commit record selftests: bpf: Reset global state between reuseport test runs alarmtimer: Make alarmtimer platform device child of RTC device iommu/vt-d: Remove unnecessary WARN_ON_ONCE() bcache: fix use-after-free in register_bcache() bcache: rework error unwinding in register_bcache bcache: cached_dev_free needs to put the sb page btrfs: Fix split-brain handling when changing FSID to metadata uuid btrfs: separate definition of assertion failure handlers media: uvcvideo: Add a quirk to force GEO GC6500 Camera bits-per-pixel value powerpc/sriov: Remove VF eeh_dev state when disabling SR-IOV drm/nouveau/mmu: fix comptag memory leak sunrpc: Fix potential leaks in sunrpc_cache_unhash() ALSA: hda - Add docking station support for Lenovo Thinkpad T420s bpf, btf: Always output invariant hit in pahole DWARF to BTF transform driver core: platform: fix u32 greater or equal to zero comparison s390/ftrace: generate traced function stack frame s390: adjust -mpacked-stack support check for clang 10 x86/decoder: Add TEST opcode to Group3-2 objtool: Fix ARCH=x86_64 build error kbuild: use -S instead of -E for precise cc-option test in Kconfig spi: spi-fsl-qspi: Ensure width is respected in spi-mem operations ALSA: hda/hdmi - add retry logic to parse_intel_hdmi() irqchip/mbigen: Set driver .suppress_bind_attrs to avoid remove problems regulator: core: Fix exported symbols to the exported GPL version remoteproc: Initialize rproc_class before use module: avoid setting info->name early in case we can fall back to info->mod->name btrfs: device s
[Kernel-packages] [Bug 1865023] Re: focal/linux-kvm: 5.4.0-1003.3 -proposed tracker
** Summary changed: - focal/linux-kvm: -proposed tracker + focal/linux-kvm: 5.4.0-1003.3 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1865023 Title: focal/linux-kvm: 5.4.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865025 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Friday, 28. February 2020 10:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1865023/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865022] Re: focal/linux-gcp: 5.4.0-1004.4 -proposed tracker
** Summary changed: - focal/linux-gcp: -proposed tracker + focal/linux-gcp: 5.4.0-1004.4 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1865022 Title: focal/linux-gcp: 5.4.0-1004.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865025 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Friday, 28. February 2020 15:04 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/1865022/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1865024] Re: focal/linux-oracle: 5.4.0-1004.4 -proposed tracker
** Summary changed: - focal/linux-oracle: -proposed tracker + focal/linux-oracle: 5.4.0-1004.4 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- 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/1865024 Title: focal/linux-oracle: 5.4.0-1004.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1865025 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Monday, 02. March 2020 10:36 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/1865024/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866165] [NEW] Focal update: v5.4.23 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.23 upstream stable release from git://git.kernel.org/ Linux 5.4.23 ASoC: SOF: Intel: hda: Add iDisp4 DAI bpf: Selftests build error in sockmap_basic.c s390/mm: Explicitly compare PAGE_DEFAULT_KEY against zero in storage_key_init_range s390/kaslr: Fix casts in get_random net/mlx5e: Fix crash in recovery flow without devlink reporter net/mlx5: Fix sleep while atomic in mlx5_eswitch_get_vepa net/mlx5e: Reset RQ doorbell counter before moving RQ state from RST to RDY xen: Enable interrupts when calling _cond_resched() ata: ahci: Add shutdown to freeze hardware resources of ahci io_uring: prevent sq_thread from spinning when it should stop rxrpc: Fix call RCU cleanup using non-bh-safe locks netfilter: xt_hashlimit: limit the max size of hashtable ALSA: seq: Fix concurrent access to queue current tick/time ALSA: seq: Avoid concurrent access to queue flags ALSA: rawmidi: Avoid bit fields for state flags io_uring: fix __io_iopoll_check deadlock in io_sq_thread arm64: lse: Fix LSE atomics with LLVM bpf, offload: Replace bitwise AND by logical AND in bpf_prog_offload_info_fill genirq/proc: Reject invalid affinity masks (again) crypto: rename sm3-256 to sm3 in hash_algo_name iommu/vt-d: Fix compile warning from intel-svm.h ecryptfs: replace BUG_ON with error handling code ASoC: fsl_sai: Fix exiting path on probing failure ASoC: atmel: fix atmel_ssc_set_audio link failure staging: greybus: use after free in gb_audio_manager_remove_all() staging: rtl8723bs: fix copy of overlapping memory usb: dwc2: Fix in ISOC request length checking usb: gadget: composite: Fix bMaxPower for SuperSpeedPlus scsi: Revert "target: iscsi: Wait for all commands to finish before freeing a session" scsi: Revert "RDMA/isert: Fix a recently introduced regression related to logout" drm/msm/dpu: fix BGR565 vs RGB565 confusion drm/i915/gt: Protect defer_request() from new waiters drm/bridge: tc358767: fix poll timeouts drm/i915/gvt: more locking for ppgtt mm LRU list drm/i915/execlists: Always force a context reload when rewinding RING_TAIL drm/i915/gt: Detect if we miss WaIdleLiteRestore Revert "dmaengine: imx-sdma: Fix memory leak" Btrfs: fix deadlock during fast fsync when logging prealloc extents beyond eof btrfs: don't set path->leave_spinning for truncate Btrfs: fix race between shrinking truncate and fiemap Btrfs: fix btrfs_wait_ordered_range() so that it waits for all ordered extents btrfs: do not check delayed items are empty for single transaction cleanup btrfs: reset fs_root to NULL on error in open_ctree btrfs: fix bytes_may_use underflow in prealloc error condtition btrfs: destroy qgroup extent records on transaction abort KVM: apic: avoid calculating pending eoi from an uninitialized val KVM: nVMX: handle nested posted interrupts when apicv is disabled for L1 KVM: nVMX: clear PIN_BASED_POSTED_INTR from nested pinbased_ctls only when apicv is globally disabled KVM: nVMX: Check IO instruction VM-exit conditions KVM: nVMX: Refactor IO bitmap checks into helper function ext4: fix race between writepages and enabling EXT4_EXTENTS_FL ext4: rename s_journal_flag_rwsem to s_writepages_rwsem ext4: fix mount failure with quota configured as module ext4: fix potential race between s_flex_groups online resizing and access ext4: fix potential race between s_group_info online resizing and access ext4: fix potential race between online resizing and write operations ext4: add cond_resched() to __ext4_find_entry() ext4: fix a data race in EXT4_I(inode)->i_disksize KVM: x86: don't notify userspace IOAPIC on edge-triggered interrupt EOI KVM: nVMX: Don't emulate instructions in guest mode sched/psi: Fix OOB write when writing 0 bytes to PSI files drm/i915: Update drm/i915 bug filing URL drm/i915: Wean off drm_pci_alloc/drm_pci_free drm/nouveau/kms/gv100-: Re-set LUT after clearing for modesets drm/amdgpu/gfx10: disable gfxoff when reading rlc clock drm/amdgpu/gfx9: disable gfxoff when reading rlc clock drm/amdgpu/soc15: fix xclk for raven mm: Avoid creating virtual address aliases in brk()/mmap()/mremap() lib/stackdepot.c: fix global out-of-bounds in stack_slabs mm/sparsemem: pfn_to_page is not valid yet on SPARSEMEM mm/vmscan.c: don't round up scan size for online memory cgroup genirq/irqdomain: Make sure all irq domain flags are distinct nvme-multipath: Fix memory leak with ana_log_buf mm/memcontrol.c: lost css_put in memcg_expand_shrinker_maps() Revert "ipc,sem: remove uneeded sem_undo_list lock usage in exit_sem()" ACPI: PM: s2idle: Check fixed wak
[Kernel-packages] [Bug 1866333] [NEW] Focal update: v5.4.24 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.4.24 upstream stable release from git://git.kernel.org/ Linux 5.4.24 blktrace: Protect q->blk_trace with RCU kvm: nVMX: VMWRITE checks unsupported field before read-only field kvm: nVMX: VMWRITE checks VMCS-link pointer before VMCS field mm, thp: fix defrag setting if newline is not used mm/huge_memory.c: use head to check huge zero page mm/gup: allow FOLL_FORCE for get_user_pages_fast() mm/debug.c: always print flags in dump_page() locking/lockdep: Fix lockdep_stats indentation problem xfs: clear kernel only flags in XFS_IOC_ATTRMULTI_BY_HANDLE bus: tegra-aconnect: Remove PM_CLK dependency netfilter: nf_flowtable: fix documentation netfilter: nft_tunnel: no need to call htons() when dumping ports thermal: brcmstb_thermal: Do not use DT coefficients thermal: db8500: Depromote debug print ubifs: Fix ino_t format warnings in orphan_delete() rcu: Allow only one expedited GP to run concurrently with wakeups KVM: x86: Remove spurious clearing of async #PF MSR KVM: x86: Remove spurious kvm_mmu_unload() from vcpu destruction path x86/resctrl: Check monitoring static key in the MBM overflow handler perf ui gtk: Add missing zalloc object perf hists browser: Restore ESC as "Zoom out" of DSO/thread/etc pwm: omap-dmtimer: put_device() after of_find_device_by_node() lib/vdso: Update coarse timekeeper unconditionally lib/vdso: Make __arch_update_vdso_data() logic understandable kprobes: Set unoptimized flag after unoptimizing code ima: ima/lsm policy rule loading logic bug fixes drivers: net: xgene: Fix the order of the arguments of 'alloc_etherdev_mqs()' RDMA/hns: Bugfix for posting a wqe with sge RDMA/hns: Simplify the calculation and usage of wqe idx for post verbs f2fs: fix to add swap extent correctly sched/fair: Optimize select_idle_cpu KVM: Check for a bad hva before dropping into the ghc slow path KVM: SVM: Override default MMIO mask if memory encryption is enabled mwifiex: delete unused mwifiex_get_intf_num() mwifiex: drop most magic numbers from mwifiex_process_tdls_action_frame() namei: only return -ECHILD from follow_dotdot_rcu() kbuild: make single target builds even faster kbuild: remove unneeded variable, single-all kbuild: move headers_check rule to usr/include/Makefile kbuild: remove header compile test selftests: Install settings files to fix TIMEOUT failures net: ena: make ena rxfh support ETH_RSS_HASH_NO_CHANGE net/smc: no peer ID in CLC decline for SMCD net: atlantic: fix out of range usage of active_vlans array net: atlantic: fix potential error handling net: atlantic: fix use after free kasan warn net: netlink: cap max groups which will be considered in netlink_bind() s390/qeth: vnicc Fix EOPNOTSUPP precedence nvme-pci: Hold cq_poll_lock while completing CQEs usb: charger: assign specific number for enum value hv_netvsc: Fix unwanted wakeup in netvsc_attach() kbuild: fix DT binding schema rule to detect command line changes mac80211: Remove a redundant mutex unlock nl80211: fix potential leak in AP start drm/i915/gvt: Separate display reset from ALL_ENGINES reset drm/i915/gvt: Fix orphan vgpu dmabuf_objs' lifetime i2c: jz4780: silence log flood on txabrt i2c: altera: Fix potential integer overflow MIPS: VPE: Fix a double free and a memory leak in 'release_vpe()' HID: hiddev: Fix race in in hiddev_disconnect() HID: alps: Fix an error handling path in 'alps_input_configured()' netfilter: xt_hashlimit: reduce hashlimit_mutex scope for htable_put() netfilter: ipset: Fix forceadd evaluation path vhost: Check docket sk_family instead of call getname net/smc: transfer fasync_list in case of fallback netfilter: ipset: Fix "INFO: rcu detected stall in hash_xxx" reports io_uring: fix 32-bit compatability with sendmsg/recvmsg cpufreq: Fix policy initialization for internal governor drivers amdgpu/gmc_v9: save/restore sdpif regs during S3 Revert "PM / devfreq: Modify the device name as devfreq(X) for sysfs" tracing: Disable trace_printk() on post poned tests macintosh: therm_windtunnel: fix regression when instantiating devices drm/radeon: Inline drm_get_pci_dev drm/amdgpu: Drop DRIVER_USE_AGP HID: core: increase HID report buffer size to 8KiB HID: core: fix off-by-one memset in hid_report_raw_event() HID: ite: Only bind to keyboard USB interface on Acer SW5-012 keyboard dock KVM: VMX: check descriptor table exits on instruction emulation ACPI: watchdog: Fix gas->access_width usage ACPICA: Introduce ACPI_ACCESS_BYTE_WIDTH() macro audit: always check the netlink payload length in audit_receive_msg() audit: fix erro
[Kernel-packages] [Bug 1866486] Re: focal/linux-kvm: 5.4.0-1004.4 -proposed tracker
** Summary changed: - focal/linux-kvm: -proposed tracker + focal/linux-kvm: 5.4.0-1004.4 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1866486 Title: focal/linux-kvm: 5.4.0-1004.4 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-kvm package in Ubuntu: Confirmed Status in linux-kvm source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1866488 packages: main: linux-kvm meta: linux-meta-kvm phase: Packaging phase-changed: Monday, 09. March 2020 09:31 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1866486/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866487] Re: focal/linux-oracle: 5.4.0-1005.5 -proposed tracker
** Summary changed: - focal/linux-oracle: -proposed tracker + focal/linux-oracle: 5.4.0-1005.5 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- 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/1866487 Title: focal/linux-oracle: 5.4.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-oracle package in Ubuntu: Confirmed Status in linux-oracle source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1866488 packages: lrm: linux-restricted-modules-oracle main: linux-oracle meta: linux-meta-oracle signed: linux-signed-oracle phase: Packaging phase-changed: Monday, 09. March 2020 11:21 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/1866487/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1866485] Re: focal/linux-gcp: 5.4.0-1005.5 -proposed tracker
** Summary changed: - focal/linux-gcp: -proposed tracker + focal/linux-gcp: 5.4.0-1005.5 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1866485 Title: focal/linux-gcp: 5.4.0-1005.5 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in linux-gcp package in Ubuntu: Confirmed Status in linux-gcp source package in Focal: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-stable-master-bug: 1866488 packages: lrm: linux-restricted-modules-gcp main: linux-gcp meta: linux-meta-gcp signed: linux-signed-gcp phase: Packaging phase-changed: Monday, 09. March 2020 12:17 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/1866485/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846704] [NEW] Enable the Dragonboards out of eoan/generic
Public bug reported: [Impact] Upstream has good support for qcom410 and 820 chipsets, so enable the Dragonboard410c and db820c out of generic [Fix] Apply the packaging and config changes in the below pull request [How to test] Boot the resulting kernel on the db410c / db820c boards [Regression potential] No code changes are involved, it's all config work and everything has been isolated into its own 'snapdragon' flavour ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Tags: eoan -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846704 Title: Enable the Dragonboards out of eoan/generic Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Upstream has good support for qcom410 and 820 chipsets, so enable the Dragonboard410c and db820c out of generic [Fix] Apply the packaging and config changes in the below pull request [How to test] Boot the resulting kernel on the db410c / db820c boards [Regression potential] No code changes are involved, it's all config work and everything has been isolated into its own 'snapdragon' flavour To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846704] Re: Enable the Dragonboards out of eoan/generic
** Description changed: [Impact] - Upstream has good support for qcom410 and 820 chipsets, so enable the - Dragonboard410c and db820c out of generic + Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820 + SOCs, so enable the Dragonboard410c and Dragonboard820c out of it, + isolating all the changes in a 'snapdragon' generic flavour. [Fix] - Apply the packaging and config changes in the below pull request + Apply the packaging and config changes in the pull request. [How to test] - Boot the resulting kernel on the db410c / db820c boards + Boot the resulting kernel on the db410c / db820c boards. [Regression potential] - No code changes are involved, it's all config work and everything has - been isolated into its own 'snapdragon' flavour + No code changes are involved: it's all config work and everything has + been isolated into its own 'snapdragon' flavour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846704 Title: Enable the Dragonboards out of eoan/generic Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820 SOCs, so enable the Dragonboard410c and Dragonboard820c out of it, isolating all the changes in a 'snapdragon' generic flavour. [Fix] Apply the packaging and config changes in the pull request. [How to test] Boot the resulting kernel on the db410c / db820c boards. [Regression potential] No code changes are involved: it's all config work and everything has been isolated into its own 'snapdragon' flavour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846704] Re: Enable the Dragonboards out of Eoan/generic arm64 kernel
** Summary changed: - Enable the Dragonboards out of eoan/generic + Enable the Dragonboards out of Eoan/generic arm64 kernel ** Summary changed: - Enable the Dragonboards out of Eoan/generic arm64 kernel + Enable the Dragonboards out of Eoan/master arm64 kernel ** Description changed: [Impact] Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820 SOCs, so enable the Dragonboard410c and Dragonboard820c out of it, - isolating all the changes in a 'snapdragon' generic flavour. + isolating all the changes in a 'snapdragon' flavour. [Fix] Apply the packaging and config changes in the pull request. [How to test] Boot the resulting kernel on the db410c / db820c boards. [Regression potential] No code changes are involved: it's all config work and everything has been isolated into its own 'snapdragon' flavour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846704 Title: Enable the Dragonboards out of Eoan/master arm64 kernel Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820 SOCs, so enable the Dragonboard410c and Dragonboard820c out of it, isolating all the changes in a 'snapdragon' flavour. [Fix] Apply the packaging and config changes in the pull request. [How to test] Boot the resulting kernel on the db410c / db820c boards. [Regression potential] No code changes are involved: it's all config work and everything has been isolated into its own 'snapdragon' flavour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1846704] Re: Enable the Dragonboards out of Eoan/master arm64 kernel
** Description changed: [Impact] - Upstream / Linux 5.3 has good support for Qcom Snapdragon 410 and 820 - SOCs, so enable the Dragonboard410c and Dragonboard820c out of it, - isolating all the changes in a 'snapdragon' flavour. + Upstream has good support for Qcom Snapdragon SOCs, so enable the + Dragonboards out of it, isolating all the changes in a 'snapdragon' + flavour. [Fix] Apply the packaging and config changes in the pull request. [How to test] Boot the resulting kernel on the db410c / db820c boards. [Regression potential] No code changes are involved: it's all config work and everything has been isolated into its own 'snapdragon' flavour. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1846704 Title: Enable the Dragonboards out of Eoan/master arm64 kernel Status in linux package in Ubuntu: Incomplete Bug description: [Impact] Upstream has good support for Qcom Snapdragon SOCs, so enable the Dragonboards out of it, isolating all the changes in a 'snapdragon' flavour. [Fix] Apply the packaging and config changes in the pull request. [How to test] Boot the resulting kernel on the db410c / db820c boards. [Regression potential] No code changes are involved: it's all config work and everything has been isolated into its own 'snapdragon' flavour. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1846704/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847290] Re: eoan/linux-raspi2: 5.3.0-1007.8 -proposed tracker
** Summary changed: - eoan/linux-raspi2: -proposed tracker + eoan/linux-raspi2: 5.3.0-1007.8 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- 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/1847290 Title: eoan/linux-raspi2: 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 prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in linux-raspi2 package in Ubuntu: Confirmed Status in linux-raspi2 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 -- kernel-stable-master-bug: 1847298 packages: main: linux-raspi2 meta: linux-meta-raspi2 phase: Packaging phase-changed: Wednesday, 09. October 2019 14:01 UTC reason: prepare-package: Pending -- package not yet uploaded prepare-package-meta: Pending -- package not yet uploaded variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1847290/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847292] Re: eoan/linux-azure: 5.3.0-1003.3 -proposed tracker
** Summary changed: - eoan/linux-azure: -proposed tracker + eoan/linux-azure: 5.3.0-1003.3 -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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) ** 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) => Paolo Pisati (p-pisati) -- 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/1847292 Title: eoan/linux-azure: 5.3.0-1003.3 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow prepare-package series: In Progress Status in Kernel SRU Workflow prepare-package-meta series: In Progress Status in Kernel SRU Workflow prepare-package-signed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-release series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in linux-azure package in Ubuntu: Confirmed Status in linux-azure 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 -- kernel-stable-master-bug: 1847298 packages: lrm: linux-restricted-modules-azure main: linux-azure meta: linux-meta-azure signed: linux-signed-azure phase: Ready for Packaging phase-changed: Tuesday, 08. October 2019 19:02 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/1847292/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1847596] Re: rpi3b+: corrupted screen on hdmi
** Changed in: linux-raspi2 (Ubuntu) Assignee: (unassigned) => Hui Wang (hui.wang) -- 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/1847596 Title: rpi3b+: corrupted screen on hdmi Status in linux-raspi2 package in Ubuntu: New Bug description: Eoan daily: 20191010 Ubuntu Server arm64+raspi3 HW: Raspberrypi 3 B+ Initial boot ok but as soon as changing to the high resolution framebuffer, the whole screen consists mostly of bright yellow and darker yellow vertical stipes. Further boot messages are visible but barely readable. Device is accessible via ssh. The dmesg there shows some kernel warnings: [1.450650] bcm2708_fb soc:fb: FB found 1 display(s) [1.452916] WARNING: CPU: 2 PID: 1 at mm/page_alloc.c:4696 __alloc_pages_nodemask+0x284/0x2c8 [1.460096] Modules linked in: [1.467227] CPU: 2 PID: 1 Comm: swapper/0 Not tainted 5.3.0-1005-raspi2 #6-Ubuntu [1.474549] Hardware name: Raspberry Pi 3 Model B Plus Rev 1.3 (DT) [1.481908] pstate: 2045 (nzCv daif +PAN -UAO) [1.489237] pc : __alloc_pages_nodemask+0x284/0x2c8 [1.496499] lr : __dma_direct_alloc_pages+0x100/0x1e8 ... [1.761649] bcm2708_fb soc:fb: Registered framebuffer for display 0, size 1824x984 [1.850950] Serial: 8250/16550 driver, 1 ports, IRQ sharing enabled [1.859009] bcm2835-rng 3f104000.rng: hwrng registered [1.865102] vc-mem: phys_addr:0x mem_base=0x3ec0 mem_size:0x4000(1024 MiB) ... [2.909823] WARN::dwc_otg_hcd_init:1043: FIQ DMA bounce buffers: virt = 10616000 dma = 0xfad1 len=9024 ... [2.946722] WARN::hcd_init_fiq:496: MPHI regs_base at 10075000 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+bug/1847596/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1848042] [NEW] Eoan update: v5.3.2 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.3.2 upstream stable release from git://git.kernel.org/ Linux 5.3.2 objtool: Clobber user CFLAGS variable platform/x86: i2c-multi-instantiate: Derive the device name from parent ALSA: hda - Apply AMD controller workaround for Raven platform ALSA: hda - Add laptop imic fixup for ASUS M9V laptop ALSA: dice: fix wrong packet parameter for Alesis iO26 ALSA: usb-audio: Add DSD support for EVGA NU Audio ALSA: usb-audio: Add Hiby device family to quirks for native DSD support Revert "mm/z3fold.c: fix race between migration and destruction" clk: imx: imx8mm: fix audio pll setting crypto: talitos - fix missing break in switch statement mtd: cfi_cmdset_0002: Use chip_good() to retry in do_write_oneword() HID: Add quirk for HP X500 PIXART OEM mouse HID: hidraw: Fix invalid read in hidraw_ioctl HID: logitech-dj: Fix crash when initial logi_dj_recv_query_paired_devices fails HID: logitech: Fix general protection fault caused by Logitech driver HID: sony: Fix memory corruption issue on cleanup. HID: prodikeys: Fix general protection fault during probe powerpc/xive: Fix bogus error code returned by OPAL drm/amd/display: readd -msse2 to prevent Clang from emitting libcalls to undefined SW FP routines drm/amd/display: Don't replace the dc_state for fast updates drm/amd/display: Skip determining update type for async updates drm/amd/display: Allow cursor async updates for framebuffer swaps clocksource/drivers: Do not warn on probe defer clocksource/drivers/timer-of: Do not warn on deferred probe netfilter: add missing IS_ENABLED(CONFIG_NF_TABLES) check to header-file. ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: 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/1848042 Title: Eoan update: v5.3.2 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed 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: v5.3.2 upstream stable release from git://git.kernel.org/ Linux 5.3.2 objtool: Clobber user CFLAGS variable platform/x86: i2c-multi-instantiate: Derive the device name from parent ALSA: hda - Apply AMD controller workaround for Raven platform ALSA: hda - Add laptop imic fixup for ASUS M9V laptop ALSA: dice: fix wrong packet parameter for Alesis iO26 ALSA: usb-audio: Add DSD support for EVGA NU Audio ALSA: usb-audio: Add Hiby device family to quirks for native DSD support Revert "mm/z3fold.c: fix race between migration and destruction" clk: imx: imx8mm: fix audio pll setting crypto: talitos - fix missing break in switch statement mtd: cfi_cmdset_0002: Use chip_good() to retry in do_write_oneword() HID: Add quirk for HP X500 PIXART OEM mouse HID: hidraw: Fix invalid read in hidraw_ioctl HID: logitech-dj: Fix crash when initial logi_dj_recv_query_paired_devices fails HID: logitech: Fix general protection fault caused by Logitech driver HID: sony: Fix memory corruption issue on cleanup. HID: prodikeys: Fix general protection fault during probe powerpc/xive: Fix bogus error code returned by OPAL drm/amd/display: readd -msse2 to prevent Clang from emitting libcalls to undefined SW FP routines drm/amd/display: Don't replace the dc_state for fast updates drm/amd/display: Skip determining update type for async updates drm/amd/display: Allow cursor async updates for framebuffer swaps clocksource/drivers: Do not warn on probe defer clocksource/drivers/timer-of: Do not warn on deferred probe netfilter: add missing IS_ENABLED(CONFIG_NF_TABLES) check to header-file. To manage notifications about this bug go
[Kernel-packages] [Bug 1848039] [NEW] Eoan update: v5.3.6 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.3.6 upstream stable release from git://git.kernel.org/ Linux 5.3.6 libnvdimm: prevent nvdimm from requesting key when security is disabled staging: erofs: detect potential multiref due to corrupted images staging: erofs: avoid endless loop of invalid lookback distance 0 staging: erofs: add two missing erofs_workgroup_put for corrupted images staging: erofs: some compressed cluster should be submitted for corrupted images staging: erofs: fix an error handling in erofs_readdir() coresight: etm4x: Use explicit barriers on enable/disable vfs: Fix EOVERFLOW testing in put_compat_statfs64 riscv: Avoid interrupts being erroneously enabled in handle_exception() perf stat: Reset previous counts on repeat with interval tick: broadcast-hrtimer: Fix a race in bc_set_next KVM: nVMX: Fix consistency check on injected exception error code Btrfs: fix selftests failure due to uninitialized i_mode in test inodes drm/radeon: Bail earlier when radeon.cik_/si_support=0 is passed nfp: abm: fix memory leak in nfp_abm_u32_knode_replace mlxsw: spectrum_flower: Fail in case user specifies multiple mirror actions perf unwind: Fix libunwind build failure on i386 systems i2c: qcom-geni: Disable DMA processing on the Lenovo Yoga C630 net: dsa: microchip: Always set regmap stride to 1 bpf: Fix bpf_event_output re-entry issue blk-mq: move lockdep_assert_held() into elevator_exit libbpf: fix false uninitialized variable warning kernel/elfcore.c: include proper prototypes selftests/bpf: adjust strobemeta loop to satisfy latest clang include/trace/events/writeback.h: fix -Wstringop-truncation warnings perf build: Add detection of java-11-openjdk-devel package sched/core: Fix migration to invalid CPU in __set_cpus_allowed_ptr() sched/membarrier: Fix private expedited registration check sched/membarrier: Call sync_core only before usermode for same mm libnvdimm/nfit_test: Fix acpi_handle redefinition fuse: fix memleak in cuse_channel_open libnvdimm: Fix endian conversion issues libnvdimm/region: Initialize bad block for volatile namespaces iommu/amd: Fix downgrading default page-sizes in alloc_pte() thermal_hwmon: Sanitize thermal_zone type thermal: Fix use-after-free when unregistering thermal zone device ntb: point to right memory window index x86/purgatory: Disable the stackleak GCC plugin for the purgatory selftests/seccomp: fix build on older kernels pwm: stm32-lp: Add check in case requested period cannot be achieved SUNRPC: Don't try to parse incomplete RPC messages pNFS: Ensure we do clear the return-on-close layout stateid on fatal errors perf probe: Fix to clear tev->nargs in clear_probe_trace_event() drm/amdgpu: Check for valid number of registers to read drm/amdgpu: Fix KFD-related kernel oops on Hawaii netfilter: nf_tables: allow lookups in dynamic sets watchdog: aspeed: Add support for AST2600 SUNRPC: RPC level errors should always set task->tk_rpc_status ceph: reconnect connection if session hang in opening state ceph: fetch cap_gen under spinlock in ceph_add_cap ceph: fix directories inode i_blkbits initialization fuse: fix request limit xen/pci: reserve MCFG areas earlier 9p: avoid attaching writeback_fid on mmap with type PRIVATE 9p: Transport error uninitialized xprtrdma: Send Queue size grows after a reconnect xprtrdma: Toggle XPRT_CONGESTED in xprtrdma's slot methods fs: nfs: Fix possible null-pointer dereferences in encode_attrs() ima: fix freeing ongoing ahash_request ima: always return negative code for error drivers: thermal: qcom: tsens: Fix memory leak from qfprom read cfg80211: initialize on-stack chandefs cfg80211: validate SSID/MBSSID element ordering assumption nl80211: validate beacon head ieee802154: atusb: fix use-after-free at disconnect xen/xenbus: fix self-deadlock after killing user process xen/balloon: Set pages PageOffline() in balloon_add_region() DTS: ARM: gta04: introduce legacy spi-cs-high to make display work again sched: Add __ASSEMBLY__ guards around struct clone_args libnvdimm/altmap: Track namespace boundaries in altmap Revert "locking/pvqspinlock: Don't wait if vCPU is preempted" mmc: sdhci: Let drivers define their DMA mask mmc: sdhci-of-esdhc: set DMA snooping based on DMA coherence mmc: sdhci: improve ADMA error reporting mmc: tegra: Implement ->set_dma_mask() mac80211: keep BHs disabled while calling drv_tx_wake_queue() drm/i915: to make vgpu ppgtt notificaiton as atomic operation drm/i915/gvt: update vgpu workload head pointer correctly drm/amd/powerplay: change metrics update period from 1ms
[Kernel-packages] [Bug 1848045] [NEW] Eoan update: v5.3.3 upstream stable release
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: v5.3.3 upstream stable release from git://git.kernel.org/ Linux 5.3.3 Revert "Linux 5.3.2" Linux 5.3.2 ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Eoan) Importance: Undecided Status: 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/1848045 Title: Eoan update: v5.3.3 upstream stable release Status in linux package in Ubuntu: Confirmed Status in linux source package in Eoan: Confirmed 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: v5.3.3 upstream stable release from git://git.kernel.org/ Linux 5.3.3 Revert "Linux 5.3.2" Linux 5.3.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1848045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
