[Kernel-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
I started a kernel bisect between v4.14 final and v4.15-rc1. The kernel bisect will require testing of about 7-10 test kernels. I built the first test kernel, up to the following commit: 1be2172e96e33bfa22a5c7a651f768ef30ce3984 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1777674 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797143] Re: arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016 gic_irq_domain_translate
** Tags added: 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/1797143
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-
gic.c:1016 gic_irq_domain_translate
Status in linux package in Ubuntu:
Confirmed
Bug description:
Impact:
During boot on a Dragonboard410c using a recent Cosmic kernel:
...
[0.071535] WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016
gic_irq_domain_translate+0xe4/0xf0
[0.071541] Modules linked in:
[0.071552] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
4.18.0-8-snapdragon #9
[0.071558] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.071566] pstate: 6045 (nZCv daif +PAN -UAO)
[0.071575] pc : gic_irq_domain_translate+0xe4/0xf0
[0.071582] lr : gic_irq_domain_alloc+0x58/0xc0
[0.071588] sp : 080337d0
[0.071594] x29: 080337d0 x28:
[0.071604] x27: 08033938 x26: 0001
[0.071615] x25: 006080c0 x24: 09a6ef70
[0.071625] x23: 09a48708 x22: 0025
[0.071636] x21: 0803384c x20: 08033850
[0.071647] x19: 08033938 x18: 0001
[0.071658] x17: x16:
[0.071668] x15: x14: 09a48708
[0.071679] x13: 80003a4c2703 x12: 0038
[0.071690] x11: 0101010101010101 x10: 0040
[0.071700] x9 : 09a6e9d8 x8 : 80003b0016f8
[0.071710] x7 : x6 : 80003b0016d0
[0.071721] x5 : 80003b001820 x4 : 0857b4f8
[0.071731] x3 : 0803384c x2 :
[0.071741] x1 : 0057 x0 :
[0.071751] Call trace:
[0.071759] gic_irq_domain_translate+0xe4/0xf0
[0.071767] gic_irq_domain_alloc+0x58/0xc0
[0.071777] __irq_domain_alloc_irqs+0x150/0x338
[0.071786] irq_create_fwspec_mapping+0x118/0x318
[0.071794] irq_create_of_mapping+0x7c/0xa8
[0.071803] of_irq_get+0x88/0xe0
[0.071812] of_irq_to_resource+0x48/0x108
[0.071821] of_irq_to_resource_table+0x54/0x70
[0.071829] of_device_alloc+0x110/0x1e0
[0.071837] of_platform_device_create_pdata+0x60/0xe0
[0.071846] of_platform_bus_create+0x2bc/0x4b0
[0.071854] of_platform_bus_create+0x31c/0x4b0
[0.071862] of_platform_populate+0x8c/0x140
[0.071872] of_platform_default_populate_init+0xb4/0xd0
[0.071880] do_one_initcall+0x54/0x1e0
[0.071890] kernel_init_freeable+0x254/0x2f8
[0.071898] kernel_init+0x18/0x110
[0.071907] ret_from_fork+0x10/0x18
[0.071913] ---[ end trace dc768b294fafe4b4 ]---
...
remove the usage of IRQ_TYPE_NONE to fix loud warnings from
patch (83a86fbb5b56b "irqchip/gic: Loudly complain about
the use of IRQ_TYPE_NONE").
The same was done in commit 242579dd0829 ("arm64: dts: msm8996: fix
gic_irq_domain_translate warnings") and commit c16e78b8e862("arm64:
dts: msm8916: fix gic_irq_domain_translate warnings") upstream, so fix
the same issue in our forward-ported Qualcomm BSP code.
Fix:
Apply the attached patch and recompile
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
None, it's mechanical modification to silence a WARNING
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797143/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797139] Re: arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
** Tags added: 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/1797139
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1
arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
Status in linux package in Ubuntu:
Confirmed
Bug description:
Impact:
Upon boot on a dragonboard410c using a recent Bionic or Cosmic kernel:
...
[0.049776] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xe0/0x148
[0.049783] Modules linked in:
[0.049797] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-8-snapdragon
#9
[0.049803] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.049813] pstate: 8045 (Nzcv daif +PAN -UAO)
[0.049821] pc : reserve_memblock_reserved_regions+0xe0/0x148
[0.049829] lr : reserve_memblock_reserved_regions+0xd8/0x148
[0.049836] sp : 08033d40
[0.049841] x29: 08033d40 x28:
[0.049852] x27: 09410584 x26: 09577018
[0.049863] x25: x24: 00488020
[0.049874] x23: bfff x22: 090e8928
[0.049885] x21: 08ffb578 x20: 09a48708
[0.049896] x19: 80003a409280 x18:
[0.049906] x17: x16:
[0.049917] x15: x14: 09a48708
[0.049927] x13: x12: 0028
[0.049938] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[0.049949] x9 : x8 : 80003a409300
[0.049959] x7 : x6 : 003f
[0.049969] x5 : 0040 x4 : 80003d9ffc70
[0.049980] x3 : bd9f x2 : 09c241b0
[0.049990] x1 : x0 :
[0.050001] Call trace:
[0.050010] reserve_memblock_reserved_regions+0xe0/0x148
[0.050021] do_one_initcall+0x54/0x1e0
[0.050031] kernel_init_freeable+0x254/0x2f8
[0.050043] kernel_init+0x18/0x110
[0.050052] ret_from_fork+0x10/0x18
[0.050063] ---[ end trace dc768b294fafe4aa ]---
...
commit 50d7ba36b916 upstream ("arm64: export memblock_reserve()d regions via
/proc/iomem") backported in commit 62289841 in bionic/master, wrongly assumed
that memblock_reserve() would not be used to reserve regions that aren't
memory. It turns out, this is exactly what early_init_dt_reserve_memory_arch()
will do if it finds a reservation
that was also carved out of the memory node.
Fix:
Apply the attached patch and recompile
The fix wad discussed here: https://www.spinics.net/lists/arm-
kernel/msg675580.html
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
The patch didn't make it upstream yet, but the fix is very small and
was tested on the lkml.
Proposing for Bionic and Cosmic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797139/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
Thanks for the feedback. The kernel posted in comment #41 was the first of a series needed for the reverse bisect. There will be about 7 in total. I built the next test kernel, up to the following commit: e002434e2d8f8205619b5b8f1d8e373a2724 The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1788997 Can you test that kernel and report back if it has the bug or not? I will build the next test kernel based on your test results. Thanks in advance -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797176] [NEW] PC is unbearably slow
Public bug reported: Everything on my machine is running abnormally, unbearably slow - From opening an application from either my GUI (GNOME) to BASH. Simple tasks like checking for an update to opening a web browser is just god-aweful slow, yet it behaves just fine booting up from the HDD and running benchmarks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeb1786 F pulseaudio /dev/snd/controlC0: jeb1786 F pulseaudio /dev/snd/controlC2: jeb1786 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 12:09:11 2018 InstallationDate: Installed on 2018-08-17 (54 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: BIOSTAR Group A880G+ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.sys.vendor: BIOSTAR Group ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug bionic hdd lagspeed latency -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797176 Title: PC is unbearably slow Status in linux package in Ubuntu: Confirmed Bug description: Everything on my machine is running abnormally, unbearably slow - From opening an application from either my GUI (GNOME) to BASH. Simple tasks like checking for an update to opening a web browser is just god-aweful slow, yet it behaves just fine booting up from the HDD and running benchmarks. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-34-generic 4.15.0-34.37 ProcVersionSignature: Ubuntu 4.15.0-34.37-generic 4.15.18 Uname: Linux 4.15.0-34-generic x86_64 NonfreeKernelModules: lkp_Ubuntu_4_15_0_34_37_generic_44 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: jeb1786 F pulseaudio /dev/snd/controlC0: jeb1786 F pulseaudio /dev/snd/controlC2: jeb1786 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Wed Oct 10 12:09:11 2018 InstallationDate: Installed on 2018-08-17 (54 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: BIOSTAR Group A880G+ ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcFB: 0 nouveaufb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-34-generic root=UUID=a967adb1-1600-455b-8704-e2bf5de5081d ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-34-generic N/A linux-backports-modules-4.15.0-34-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/21/2011 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 080016 dmi.board.asset.tag: To Be Filled By O.E.M. dmi.board.name: A880G+ dmi.board.vendor: BIOSTAR Group dmi.chassis.asset.tag: None dmi.chassis.type: 3 dmi.chassis.vendor: BIOSTAR Group dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr080016:bd09/21/2011:svnBIOSTARGroup:pnA880G+:pvr:rvnBIOSTARGroup:rnA880G+:rvr:cvnBIOSTARGroup:ct3:cvr: dmi.product.family: To Be Filled By O.E.M. dmi.product.name: A880G+ dmi.sys.vendor: BIOSTAR Group To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797176/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released -- 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/1797062 Title: linux-gcp: 4.15.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797066] Re: linux-aws: 4.15.0-1025.25 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 10. October 2018 16:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - phase: Packaging - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Wednesday, 10. October 2018 16:02 UTC + phase: Uploaded -- 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/1797066 Title: linux-aws: 4.15.0-1025.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796918] Re: [Bionic] additional support for CPPC (V3) and documentation.
** Summary changed: - [Bionic] add support for CPPC V3 + [Bionic] additional support for CPPC (V3) and documentation. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796918 Title: [Bionic] additional support for CPPC (V3) and documentation. Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: [IMPACT] Add support for CPPC V3 [FIX] 33477d84c26b cpufreq / CPPC: Add cpuinfo_cur_freq support for CPPC b382bf885269 ACPI / CPPC: Document CPPC sysfs interface 256f19d212f2 cpufreq / CPPC: Support for CPPC v3 4773e77cdc9b ACPI / CPPC: Add support for CPPC v3 [Test] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797154] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1797154 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797154 Title: arm64: snapdragon: reduce boot noise Status in linux package in Ubuntu: Incomplete Bug description: Impact: During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel, there's some noise like: ... [3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517 [3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to init regulator, ret=-517 [3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to init regulator ... or ... [4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get supply 'vdd-cdc-io': -517 [4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get regulator supplies -517 ... and similar. This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in, and tries to initialize before the voltage regulators are ready to work, resulting in a noisy bootlog. These patches factor out some code as modules, so when the kmods are loaded and initialized, regulators are already present and ready to attach - all these config changes shave around ~3K bytes from dmesg, making the bootlog easir to parse. Fix: Apply the attached patches and recompile How to test: Boot a patched kernel and check for the above noise in dmesg Regression potential: None, we are just turning some code into kmods, and turning off a couple of not used feature for this flavour - all the other flavours are untouched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1762385] Re: dell_wmi: Unknown key codes
Hello Dmitriy, or anyone else affected, Accepted systemd into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/systemd/229-4ubuntu21.5 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-xenial to verification-done-xenial. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-xenial. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: systemd (Ubuntu Xenial) Status: In Progress => Fix Committed ** Tags removed: verification-done ** Tags added: verification-needed verification-needed-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1762385 Title: dell_wmi: Unknown key codes Status in OEM Priority Project: Triaged Status in linux package in Ubuntu: Fix Committed Status in systemd package in Ubuntu: Fix Released Status in systemd source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Released Status in systemd source package in Bionic: Fix Released Status in linux source package in Cosmic: Fix Committed Status in systemd source package in Cosmic: Fix Released Bug description: [Impact] * Bogus keycode messages produced by the kernel / user annoyance * rfkill keyboard shortcuts not working as intended on some Dell machines [Test Case] * check that there are no spurious kernel messages about unknown keys in journalctl upon RFKill key presses * check that RFKill key presses work correctly and kill/restore RF capabilities [Regression Potential] * The change is scoped to particular SKUs and thus should only affect them * It is related to matching gsd support, which is in-place on xenial and up [Solution] Cherrypick upstream commit https://github.com/systemd/systemd/commit/cab01e9ecf1c69656785e64f5fc94cd4ed09e57f [Original Bug report] RFKill key produces these messages in kernel log: dell_wmi: Unknown key with type 0x0010 and code 0xe008 pressed This key code is a notification and should be added as KEY_IGNORE here: https://github.com/torvalds/linux/blob/master/drivers/platform/x86 /dell-wmi.c#L263 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-15-generic 4.15.0-15.16 ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15 Uname: Linux 4.15.0-15-generic x86_64 ApportVersion: 2.20.9-0ubuntu4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: dmig 2737 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Apr 9 18:09:03 2018 InstallationDate: Installed on 2018-03-27 (12 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180327) MachineType: Dell Inc. Inspiron 5379 ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/@/boot/vmlinuz-4.15.0-15-generic root=UUID=9745e22b-0b19-4a7d-98a0-1a4bc5b19d99 ro rootflags=subvol=@ quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-15-generic N/A linux-backports-modules-4.15.0-15-generic N/A linux-firmware 1.173 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 01/31/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.6.0 dmi.board.name: 0C6J64 dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.6.0:bd01/31/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn0C6J64:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1762385/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796918] Re: [Bionic] add support for CPPC V3
In the list above 6799982c25e9 (HEAD -> cppc) cpufreq / CPPC: Add cpuinfo_cur_freq support for CPPC This patch is missing in Cosmic, so this patch applies to both Bionic and Cosmic. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796918 Title: [Bionic] additional support for CPPC (V3) and documentation. Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: [IMPACT] Add support for CPPC V3 [FIX] 33477d84c26b cpufreq / CPPC: Add cpuinfo_cur_freq support for CPPC b382bf885269 ACPI / CPPC: Document CPPC sysfs interface 256f19d212f2 cpufreq / CPPC: Support for CPPC v3 4773e77cdc9b ACPI / CPPC: Add support for CPPC v3 [Test] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796918] Re: [Bionic] add support for CPPC V3
** Description changed: [IMPACT] Add support for CPPC V3 [FIX] - + 33477d84c26b cpufreq / CPPC: Add cpuinfo_cur_freq support for CPPC + b382bf885269 ACPI / CPPC: Document CPPC sysfs interface + 256f19d212f2 cpufreq / CPPC: Support for CPPC v3 + 4773e77cdc9b ACPI / CPPC: Add support for CPPC v3 + [Test] [Regression Potential] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796918 Title: [Bionic] add support for CPPC V3 Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: [IMPACT] Add support for CPPC V3 [FIX] 33477d84c26b cpufreq / CPPC: Add cpuinfo_cur_freq support for CPPC b382bf885269 ACPI / CPPC: Document CPPC sysfs interface 256f19d212f2 cpufreq / CPPC: Support for CPPC v3 4773e77cdc9b ACPI / CPPC: Add support for CPPC v3 [Test] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796949] Re: [Bionic] CPPC bug fixes
** Description changed: [Impact] + A number of CPPC related fixes from upstream needed for Cavium ThunderX2 systems. [Fix] - [Test] + 58e1c03536c9 ACPI / CPPC: Fix invalid PCC channel status errors + 6fa12d584dcb ACPI / CPPC: Check for valid PCC subspace only if PCC is used + b8b10bc2015c cpufreq: CPPC: Don't set transition_latency + d29abc836843 ACPI / CPPC: Update all pr_(debug/err) messages to log the susbspace id [Regression Potential] ** Description changed: [Impact] A number of CPPC related fixes from upstream needed for Cavium ThunderX2 systems. [Fix] 58e1c03536c9 ACPI / CPPC: Fix invalid PCC channel status errors 6fa12d584dcb ACPI / CPPC: Check for valid PCC subspace only if PCC is used b8b10bc2015c cpufreq: CPPC: Don't set transition_latency d29abc836843 ACPI / CPPC: Update all pr_(debug/err) messages to log the susbspace id + [Test] + [Regression Potential] -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796949 Title: [Bionic] CPPC bug fixes Status in linux package in Ubuntu: Incomplete Bug description: [Impact] A number of CPPC related fixes from upstream needed for Cavium ThunderX2 systems. [Fix] 58e1c03536c9 ACPI / CPPC: Fix invalid PCC channel status errors 6fa12d584dcb ACPI / CPPC: Check for valid PCC subspace only if PCC is used b8b10bc2015c cpufreq: CPPC: Don't set transition_latency d29abc836843 ACPI / CPPC: Update all pr_(debug/err) messages to log the susbspace id [Test] [Regression Potential] To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796949/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797086] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1797086 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797086 Title: Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted Status in linux package in Ubuntu: Incomplete Bug description: I am using Ubuntu 18.04.1 LTS, and have set up hard disk encryption during installation. With new automatic software update that installed linux-image-4.15.0-36-generic kernel my password for disk encryption was rejected. The only way I could log in was through choosing the old kernel (linux-image-4.15.0-29-generic) advanced options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797086] Re: Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted
** Tags added: bionic regression-update ** Package changed: ubuntu => linux (Ubuntu) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797086 Title: Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted Status in linux package in Ubuntu: Incomplete Bug description: I am using Ubuntu 18.04.1 LTS, and have set up hard disk encryption during installation. With new automatic software update that installed linux-image-4.15.0-36-generic kernel my password for disk encryption was rejected. The only way I could log in was through choosing the old kernel (linux-image-4.15.0-29-generic) advanced options. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797086/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797154] Re: arm64: snapdragon: reduce boot noise
** Description changed: Impact: - During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel: + During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel, + there's some noise like: ... [3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517 [3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to init regulator, ret=-517 [3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to init regulator ... or ... [4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get supply 'vdd-cdc-io': -517 [4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get regulator supplies -517 ... - this is mainly because the DRM_MSM* and the SND_QCOM_MSM* were built-in, - and tries to initialize before the voltage regulators are ready, - spamming the boot log with useless noise. + and similar. + + This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in, and + tries to initialize before the voltage regulators are ready to work, + resulting in a noisy bootlog. These patches factor out some code as modules, so when the kmods are loaded and initialized, regulators are already present and ready to attach - all these config changes shave around ~3K bytes from dmesg, - making the bootlog more clear. + making the bootlog easir to parse. Fix: Apply the attached patches and recompile How to test: Boot a patched kernel and check for the above noise in dmesg Regression potential: None, we are just turning some code into kmods, and turning off a couple - of not used feature for this flavour. + of not used feature for this flavour - all the other flavours are + untouched. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797154 Title: arm64: snapdragon: reduce boot noise Status in linux package in Ubuntu: New Bug description: Impact: During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel, there's some noise like: ... [3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517 [3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to init regulator, ret=-517 [3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to init regulator ... or ... [4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get supply 'vdd-cdc-io': -517 [4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get regulator supplies -517 ... and similar. This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in, and tries to initialize before the voltage regulators are ready to work, resulting in a noisy bootlog. These patches factor out some code as modules, so when the kmods are loaded and initialized, regulators are already present and ready to attach - all these config changes shave around ~3K bytes from dmesg, making the bootlog easir to parse. Fix: Apply the attached patches and recompile How to test: Boot a patched kernel and check for the above noise in dmesg Regression potential: None, we are just turning some code into kmods, and turning off a couple of not used feature for this flavour - all the other flavours are untouched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797086] [NEW] Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted
You have been subscribed to a public bug: I am using Ubuntu 18.04.1 LTS, and have set up hard disk encryption during installation. With new automatic software update that installed linux-image-4.15.0-36-generic kernel my password for disk encryption was rejected. The only way I could log in was through choosing the old kernel (linux-image-4.15.0-29-generic) advanced options. ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: bionic bot-comment regression-update -- Updating kernel from 4.15.0-29 to 4.15.0-36 hard disk encryption key not accpeted https://bugs.launchpad.net/bugs/1797086 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792044] Re: update ENA driver to latest mainline version
Fix verified in bionic generic (4.15.0-37.40). Fix verified in xenial generic (4.4.0-138.164). ** Tags removed: verification-needed-bionic verification-needed-xenial ** Tags added: verification-done-bionic verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792044 Title: update ENA driver to latest mainline version Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Bug description: Update ENA driver to latest mainline version as of this commit: https://git.kernel.org/pub/scm/linux/kernel/git/davem/net.git/commit/?id=0e1f4c76be241377d282e34ebea6d16ff7829747 For Bionic, the following commits: net: ena: fix incorrect usage of memory barriers net: ena: fix missing calls to READ_ONCE net: ena: fix missing lock during device destruction net: ena: fix potential double ena_destroy_device() net: ena: fix device destruction to gracefully free resources net: ena: fix driver when PAGE_SIZE == 64kB net: ena: fix surprise unplug NULL dereference kernel crash net: ena: Fix use of uninitialized DMA address bits field UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() net: ena: Eliminate duplicate barriers on weakly-ordered archs net: ena: increase ena driver version to 1.5.0 net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X For Xenial, the following commits: net: ena: fix incorrect usage of memory barriers net: ena: fix missing calls to READ_ONCE net: ena: fix missing lock during device destruction net: ena: fix potential double ena_destroy_device() net: ena: fix device destruction to gracefully free resources net: ena: fix driver when PAGE_SIZE == 64kB net: ena: fix surprise unplug NULL dereference kernel crash net: ena: Fix use of uninitialized DMA address bits field UBUNTU: SAUCE: ena: devm_kzalloc() -> devm_kcalloc() net: ena: Eliminate duplicate barriers on weakly-ordered archs net: ena: fix error handling in ena_down() sequence net: ena: increase ena driver version to 1.5.0 net: ena: add detection and recovery mechanism for handling missed/misrouted MSI-X net: ena: fix race condition between device reset and link up setup net: ena: increase ena driver version to 1.3.0 net: ena: add new admin define for future support of IPv6 RSS net: ena: add statistics for missed tx packets net: ena: add power management ops to the ENA driver net: ena: remove legacy suspend suspend/resume support net: ena: improve ENA driver boot time. net: ena: fix wrong max Tx/Rx queues on ethtool net: ena: fix rare kernel crash when bar memory remap fails net: ena: reduce the severity of some printouts net: ena: Remove redundant unlikely() *Note that some of these were already present in the linux-aws variants (the remainder will be picked up on their next rebase cycles). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1792044/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797154] [NEW] arm64: snapdragon: reduce boot noise
Public bug reported: Impact: During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel, there's some noise like: ... [3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517 [3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to init regulator, ret=-517 [3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to init regulator ... or ... [4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get supply 'vdd-cdc-io': -517 [4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get regulator supplies -517 ... and similar. This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in, and tries to initialize before the voltage regulators are ready to work, resulting in a noisy bootlog. These patches factor out some code as modules, so when the kmods are loaded and initialized, regulators are already present and ready to attach - all these config changes shave around ~3K bytes from dmesg, making the bootlog easir to parse. Fix: Apply the attached patches and recompile How to test: Boot a patched kernel and check for the above noise in dmesg Regression potential: None, we are just turning some code into kmods, and turning off a couple of not used feature for this flavour - all the other flavours are untouched. ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797154 Title: arm64: snapdragon: reduce boot noise Status in linux package in Ubuntu: New Bug description: Impact: During boot on a Dragonboard410c using a recent Bionic or Cosmic kernel, there's some noise like: ... [3.665431] msm_dsi_phy 1a98300.dsi-phy: Failed to get supply 'vddio': -517 [3.669243] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_regulator_init: failed to init regulator, ret=-517 [3.676180] msm_dsi_phy 1a98300.dsi-phy: dsi_phy_driver_probe: failed to init regulator ... or ... [4.192280] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get supply 'vdd-cdc-io': -517 [4.195660] qcom,pm8916-wcd-spmi-codec 200f000.spmi:pm8916@1:codec@f000: Failed to get regulator supplies -517 ... and similar. This is mainly due to DRM_MSM* and SND_QCOM_MSM* that were built-in, and tries to initialize before the voltage regulators are ready to work, resulting in a noisy bootlog. These patches factor out some code as modules, so when the kmods are loaded and initialized, regulators are already present and ready to attach - all these config changes shave around ~3K bytes from dmesg, making the bootlog easir to parse. Fix: Apply the attached patches and recompile How to test: Boot a patched kernel and check for the above noise in dmesg Regression potential: None, we are just turning some code into kmods, and turning off a couple of not used feature for this flavour - all the other flavours are untouched. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797154/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795453] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1795453 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: Incomplete Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797143] Re: arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016 gic_irq_domain_translate
Ignore the above patch, this is the patch with the correct buglink.
** Patch added:
"0001-UBUNTU-SAUCE-arm64-dts-msm8916-camms-fix-gic_irq_dom.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797143/+attachment/5199522/+files/0001-UBUNTU-SAUCE-arm64-dts-msm8916-camms-fix-gic_irq_dom.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/1797143
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-
gic.c:1016 gic_irq_domain_translate
Status in linux package in Ubuntu:
Confirmed
Bug description:
Impact:
During boot on a Dragonboard410c using a recent Cosmic kernel:
...
[0.071535] WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016
gic_irq_domain_translate+0xe4/0xf0
[0.071541] Modules linked in:
[0.071552] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
4.18.0-8-snapdragon #9
[0.071558] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.071566] pstate: 6045 (nZCv daif +PAN -UAO)
[0.071575] pc : gic_irq_domain_translate+0xe4/0xf0
[0.071582] lr : gic_irq_domain_alloc+0x58/0xc0
[0.071588] sp : 080337d0
[0.071594] x29: 080337d0 x28:
[0.071604] x27: 08033938 x26: 0001
[0.071615] x25: 006080c0 x24: 09a6ef70
[0.071625] x23: 09a48708 x22: 0025
[0.071636] x21: 0803384c x20: 08033850
[0.071647] x19: 08033938 x18: 0001
[0.071658] x17: x16:
[0.071668] x15: x14: 09a48708
[0.071679] x13: 80003a4c2703 x12: 0038
[0.071690] x11: 0101010101010101 x10: 0040
[0.071700] x9 : 09a6e9d8 x8 : 80003b0016f8
[0.071710] x7 : x6 : 80003b0016d0
[0.071721] x5 : 80003b001820 x4 : 0857b4f8
[0.071731] x3 : 0803384c x2 :
[0.071741] x1 : 0057 x0 :
[0.071751] Call trace:
[0.071759] gic_irq_domain_translate+0xe4/0xf0
[0.071767] gic_irq_domain_alloc+0x58/0xc0
[0.071777] __irq_domain_alloc_irqs+0x150/0x338
[0.071786] irq_create_fwspec_mapping+0x118/0x318
[0.071794] irq_create_of_mapping+0x7c/0xa8
[0.071803] of_irq_get+0x88/0xe0
[0.071812] of_irq_to_resource+0x48/0x108
[0.071821] of_irq_to_resource_table+0x54/0x70
[0.071829] of_device_alloc+0x110/0x1e0
[0.071837] of_platform_device_create_pdata+0x60/0xe0
[0.071846] of_platform_bus_create+0x2bc/0x4b0
[0.071854] of_platform_bus_create+0x31c/0x4b0
[0.071862] of_platform_populate+0x8c/0x140
[0.071872] of_platform_default_populate_init+0xb4/0xd0
[0.071880] do_one_initcall+0x54/0x1e0
[0.071890] kernel_init_freeable+0x254/0x2f8
[0.071898] kernel_init+0x18/0x110
[0.071907] ret_from_fork+0x10/0x18
[0.071913] ---[ end trace dc768b294fafe4b4 ]---
...
remove the usage of IRQ_TYPE_NONE to fix loud warnings from
patch (83a86fbb5b56b "irqchip/gic: Loudly complain about
the use of IRQ_TYPE_NONE").
The same was done in commit 242579dd0829 ("arm64: dts: msm8996: fix
gic_irq_domain_translate warnings") and commit c16e78b8e862("arm64:
dts: msm8916: fix gic_irq_domain_translate warnings") upstream, so fix
the same issue in our forward-ported Qualcomm BSP code.
Fix:
Apply the attached patch and recompile
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
None, it's mechanical modification to silence a WARNING
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797143/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
@Joseph I think I have bandwidth, please provide specific links and instructions:) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797143] Re: arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016 gic_irq_domain_translate
** Patch added:
"0001-UBUNTU-SAUCE-arm64-dts-msm8916-camms-fix-gic_irq_dom.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797143/+attachment/5199517/+files/0001-UBUNTU-SAUCE-arm64-dts-msm8916-camms-fix-gic_irq_dom.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/1797143
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-
gic.c:1016 gic_irq_domain_translate
Status in linux package in Ubuntu:
Confirmed
Bug description:
Impact:
During boot on a Dragonboard410c using a recent Cosmic kernel:
...
[0.071535] WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016
gic_irq_domain_translate+0xe4/0xf0
[0.071541] Modules linked in:
[0.071552] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
4.18.0-8-snapdragon #9
[0.071558] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.071566] pstate: 6045 (nZCv daif +PAN -UAO)
[0.071575] pc : gic_irq_domain_translate+0xe4/0xf0
[0.071582] lr : gic_irq_domain_alloc+0x58/0xc0
[0.071588] sp : 080337d0
[0.071594] x29: 080337d0 x28:
[0.071604] x27: 08033938 x26: 0001
[0.071615] x25: 006080c0 x24: 09a6ef70
[0.071625] x23: 09a48708 x22: 0025
[0.071636] x21: 0803384c x20: 08033850
[0.071647] x19: 08033938 x18: 0001
[0.071658] x17: x16:
[0.071668] x15: x14: 09a48708
[0.071679] x13: 80003a4c2703 x12: 0038
[0.071690] x11: 0101010101010101 x10: 0040
[0.071700] x9 : 09a6e9d8 x8 : 80003b0016f8
[0.071710] x7 : x6 : 80003b0016d0
[0.071721] x5 : 80003b001820 x4 : 0857b4f8
[0.071731] x3 : 0803384c x2 :
[0.071741] x1 : 0057 x0 :
[0.071751] Call trace:
[0.071759] gic_irq_domain_translate+0xe4/0xf0
[0.071767] gic_irq_domain_alloc+0x58/0xc0
[0.071777] __irq_domain_alloc_irqs+0x150/0x338
[0.071786] irq_create_fwspec_mapping+0x118/0x318
[0.071794] irq_create_of_mapping+0x7c/0xa8
[0.071803] of_irq_get+0x88/0xe0
[0.071812] of_irq_to_resource+0x48/0x108
[0.071821] of_irq_to_resource_table+0x54/0x70
[0.071829] of_device_alloc+0x110/0x1e0
[0.071837] of_platform_device_create_pdata+0x60/0xe0
[0.071846] of_platform_bus_create+0x2bc/0x4b0
[0.071854] of_platform_bus_create+0x31c/0x4b0
[0.071862] of_platform_populate+0x8c/0x140
[0.071872] of_platform_default_populate_init+0xb4/0xd0
[0.071880] do_one_initcall+0x54/0x1e0
[0.071890] kernel_init_freeable+0x254/0x2f8
[0.071898] kernel_init+0x18/0x110
[0.071907] ret_from_fork+0x10/0x18
[0.071913] ---[ end trace dc768b294fafe4b4 ]---
...
remove the usage of IRQ_TYPE_NONE to fix loud warnings from
patch (83a86fbb5b56b "irqchip/gic: Loudly complain about
the use of IRQ_TYPE_NONE").
The same was done in commit 242579dd0829 ("arm64: dts: msm8996: fix
gic_irq_domain_translate warnings") and commit c16e78b8e862("arm64:
dts: msm8916: fix gic_irq_domain_translate warnings") upstream, so fix
the same issue in our forward-ported Qualcomm BSP code.
Fix:
Apply the attached patch and recompile
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
None, it's mechanical modification to silence a WARNING
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797143/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797143] [NEW] arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016 gic_irq_domain_translate
Public bug reported:
Impact:
During boot on a Dragonboard410c using a recent Cosmic kernel:
...
[0.071535] WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016
gic_irq_domain_translate+0xe4/0xf0
[0.071541] Modules linked in:
[0.071552] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
4.18.0-8-snapdragon #9
[0.071558] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.071566] pstate: 6045 (nZCv daif +PAN -UAO)
[0.071575] pc : gic_irq_domain_translate+0xe4/0xf0
[0.071582] lr : gic_irq_domain_alloc+0x58/0xc0
[0.071588] sp : 080337d0
[0.071594] x29: 080337d0 x28:
[0.071604] x27: 08033938 x26: 0001
[0.071615] x25: 006080c0 x24: 09a6ef70
[0.071625] x23: 09a48708 x22: 0025
[0.071636] x21: 0803384c x20: 08033850
[0.071647] x19: 08033938 x18: 0001
[0.071658] x17: x16:
[0.071668] x15: x14: 09a48708
[0.071679] x13: 80003a4c2703 x12: 0038
[0.071690] x11: 0101010101010101 x10: 0040
[0.071700] x9 : 09a6e9d8 x8 : 80003b0016f8
[0.071710] x7 : x6 : 80003b0016d0
[0.071721] x5 : 80003b001820 x4 : 0857b4f8
[0.071731] x3 : 0803384c x2 :
[0.071741] x1 : 0057 x0 :
[0.071751] Call trace:
[0.071759] gic_irq_domain_translate+0xe4/0xf0
[0.071767] gic_irq_domain_alloc+0x58/0xc0
[0.071777] __irq_domain_alloc_irqs+0x150/0x338
[0.071786] irq_create_fwspec_mapping+0x118/0x318
[0.071794] irq_create_of_mapping+0x7c/0xa8
[0.071803] of_irq_get+0x88/0xe0
[0.071812] of_irq_to_resource+0x48/0x108
[0.071821] of_irq_to_resource_table+0x54/0x70
[0.071829] of_device_alloc+0x110/0x1e0
[0.071837] of_platform_device_create_pdata+0x60/0xe0
[0.071846] of_platform_bus_create+0x2bc/0x4b0
[0.071854] of_platform_bus_create+0x31c/0x4b0
[0.071862] of_platform_populate+0x8c/0x140
[0.071872] of_platform_default_populate_init+0xb4/0xd0
[0.071880] do_one_initcall+0x54/0x1e0
[0.071890] kernel_init_freeable+0x254/0x2f8
[0.071898] kernel_init+0x18/0x110
[0.071907] ret_from_fork+0x10/0x18
[0.071913] ---[ end trace dc768b294fafe4b4 ]---
...
remove the usage of IRQ_TYPE_NONE to fix loud warnings from
patch (83a86fbb5b56b "irqchip/gic: Loudly complain about
the use of IRQ_TYPE_NONE").
The same was done in commit 242579dd0829 ("arm64: dts: msm8996: fix
gic_irq_domain_translate warnings") and commit c16e78b8e862("arm64: dts:
msm8916: fix gic_irq_domain_translate warnings") upstream, so fix the
same issue in our forward-ported Qualcomm BSP code.
Fix:
Apply the attached patch and recompile
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
None, it's mechanical modification to silence a WARNING
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Confirmed
** Changed in: linux (Ubuntu)
Status: New => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => 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/1797143
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-
gic.c:1016 gic_irq_domain_translate
Status in linux package in Ubuntu:
Confirmed
Bug description:
Impact:
During boot on a Dragonboard410c using a recent Cosmic kernel:
...
[0.071535] WARNING: CPU: 0 PID: 1 at drivers/irqchip/irq-gic.c:1016
gic_irq_domain_translate+0xe4/0xf0
[0.071541] Modules linked in:
[0.071552] CPU: 0 PID: 1 Comm: swapper/0 Tainted: GW
4.18.0-8-snapdragon #9
[0.071558] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.071566] pstate: 6045 (nZCv daif +PAN -UAO)
[0.071575] pc : gic_irq_domain_translate+0xe4/0xf0
[0.071582] lr : gic_irq_domain_alloc+0x58/0xc0
[0.071588] sp : 080337d0
[0.071594] x29: 080337d0 x28:
[0.071604] x27: 08033938 x26: 0001
[0.071615] x25: 006080c0 x24: 09a6ef70
[0.071625] x23: 09a48708 x22: 0025
[0.071636] x21: 0803384c x20: 08033850
[0.071647] x19: 08033938 x18: 0001
[0.071658] x17: x16:
[0.071668] x15: x14: 09a48708
[0.071679] x13: 80003a4c2703 x12: 0038
[0.071690] x11: 0101010101010101 x10: 0040
[0.071700] x9 : 09a6e9d8 x8 : 80003b0016f8
[0.071710] x7 : x6 : 80003b0016d0
[0.071721] x5 : 80003b00182
[Kernel-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
** Changed in: linux (Ubuntu) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu Bionic) Status: Incomplete => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Joseph Salisbury (jsalisbury) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: In Progress Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: In Progress Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797139] Re: arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
** Changed in: linux (Ubuntu)
Status: Incomplete => Invalid
** Changed in: linux (Ubuntu)
Status: Invalid => 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/1797139
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1
arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
Status in linux package in Ubuntu:
Confirmed
Bug description:
Impact:
Upon boot on a dragonboard410c using a recent Bionic or Cosmic kernel:
...
[0.049776] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xe0/0x148
[0.049783] Modules linked in:
[0.049797] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-8-snapdragon
#9
[0.049803] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.049813] pstate: 8045 (Nzcv daif +PAN -UAO)
[0.049821] pc : reserve_memblock_reserved_regions+0xe0/0x148
[0.049829] lr : reserve_memblock_reserved_regions+0xd8/0x148
[0.049836] sp : 08033d40
[0.049841] x29: 08033d40 x28:
[0.049852] x27: 09410584 x26: 09577018
[0.049863] x25: x24: 00488020
[0.049874] x23: bfff x22: 090e8928
[0.049885] x21: 08ffb578 x20: 09a48708
[0.049896] x19: 80003a409280 x18:
[0.049906] x17: x16:
[0.049917] x15: x14: 09a48708
[0.049927] x13: x12: 0028
[0.049938] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[0.049949] x9 : x8 : 80003a409300
[0.049959] x7 : x6 : 003f
[0.049969] x5 : 0040 x4 : 80003d9ffc70
[0.049980] x3 : bd9f x2 : 09c241b0
[0.049990] x1 : x0 :
[0.050001] Call trace:
[0.050010] reserve_memblock_reserved_regions+0xe0/0x148
[0.050021] do_one_initcall+0x54/0x1e0
[0.050031] kernel_init_freeable+0x254/0x2f8
[0.050043] kernel_init+0x18/0x110
[0.050052] ret_from_fork+0x10/0x18
[0.050063] ---[ end trace dc768b294fafe4aa ]---
...
commit 50d7ba36b916 upstream ("arm64: export memblock_reserve()d regions via
/proc/iomem") backported in commit 62289841 in bionic/master, wrongly assumed
that memblock_reserve() would not be used to reserve regions that aren't
memory. It turns out, this is exactly what early_init_dt_reserve_memory_arch()
will do if it finds a reservation
that was also carved out of the memory node.
Fix:
Apply the attached patch and recompile
The fix wad discussed here: https://www.spinics.net/lists/arm-
kernel/msg675580.html
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
The patch didn't make it upstream yet, but the fix is very small and
was tested on the lkml.
Proposing for Bionic and Cosmic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797139/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795453] Re: IO's are issued with incorrect Scatter Gather Buffer
moving to kernel itself rather than the hwe package ** Package changed: linux-signed-hwe (Ubuntu) => linux (Ubuntu) ** Changed in: linux (Ubuntu) Status: Confirmed => 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/1795453 Title: IO's are issued with incorrect Scatter Gather Buffer Status in linux package in Ubuntu: New Bug description: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1795453/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1776155] Re: Touchpad detected as SYNA3602, does not work at all.
Does anyone know when the patch in the official Ubuntu 18.04 kernel comes? Thanks Olaf -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1776155 Title: Touchpad detected as SYNA3602, does not work at all. Status in linux package in Ubuntu: Confirmed Bug description: On my cheaper-end slimline laptop/netbook the touchpad is (I think wrongly) detected by Linux to be the SYNA 3602. Anyway it does not work at all, neither touchpad nor buttons. Freshly installed Ubuntu 18.04 system. External mouse works fine. It seems that there is a bug reported on a similar issue, although I can not confirm that my touchpad hardware is exactly the same: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1688625 If so, there may be a whole new generation of slimline Windows 10 netbooks that have this problem. martin@alanah:~$ cat /proc/bus/input/devices I: Bus=0011 Vendor=0001 Product=0001 Version=ab83 N: Name="AT Translated Set 2 keyboard" P: Phys=isa0060/serio0/input0 S: Sysfs=/devices/platform/i8042/serio0/input/input2 U: Uniq= H: Handlers=sysrq kbd event2 leds B: PROP=0 B: EV=120013 B: KEY=40200 3803078f800d001 fedfffef fffe B: MSC=10 B: LED=7 I: Bus=0018 Vendor=0911 Product=5288 Version=0100 N: Name="SYNA3602:00 0911:5288 Touchpad" P: Phys=i2c-SYNA3602:00 S: Sysfs=/devices/pci:00/:00:16.1/i2c_designware.1/i2c-5/i2c-SYNA3602:00/0018:0911:5288.0001/input/input15 U: Uniq= H: Handlers=mouse0 event14 B: PROP=5 B: EV=1b B: KEY=e420 3 0 0 0 0 B: ABS=2608003 B: MSC=20 I: Bus=0003 Vendor=045e Product=00b9 Version=0111 N: Name="Microsoft Microsoft USB Wireless Mouse" P: Phys=usb-:00:15.0-1/input0 S: Sysfs=/devices/pci:00/:00:15.0/usb1/1-1/1-1:1.0/0003:045E:00B9.0002/input/input16 U: Uniq= H: Handlers=mouse1 event15 B: PROP=0 B: EV=17 B: KEY=1f 0 0 0 0 B: REL=1c3 B: MSC=10 ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-20-generic 4.15.0-20.21 ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 Uname: Linux 4.15.0-20-generic x86_64 ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 CurrentDesktop: MATE Date: Mon Jun 11 07:57:56 2018 InstallationDate: Installed on 2018-04-25 (46 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) SourcePackage: linux-signed UpgradeStatus: No upgrade log present (probably fresh install) --- ApportVersion: 2.20.9-0ubuntu7 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: martin 1536 F pulseaudio CurrentDesktop: MATE DistroRelease: Ubuntu 18.04 InstallationDate: Installed on 2018-04-25 (48 days ago) InstallationMedia: Ubuntu-MATE 18.04 LTS "Bionic Beaver" - Beta amd64 (20180404) MachineType: Multicom Multicom U230 Package: linux (not installed) ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-20-generic root=UUID=c7a82fee-6e9d-491d-a38d-f5d6bdb4a930 ro ProcVersionSignature: Ubuntu 4.15.0-20.21-generic 4.15.17 RelatedPackageVersions: linux-restricted-modules-4.15.0-20-generic N/A linux-backports-modules-4.15.0-20-generic N/A linux-firmware 1.173 Tags: bionic Uname: Linux 4.15.0-20-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 09/15/2017 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: ORO10x.WP313P.NHNAUHL01 dmi.board.asset.tag: Default string dmi.board.name: Default string dmi.board.vendor: Default string dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrORO10x.WP313P.NHNAUHL01:bd09/15/2017:svnMulticom:pnMulticomU230:pvrDefaultstring:rvnDefaultstring:rnDefaultstring:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring: dmi.product.family: U-series dmi.product.name: Multicom U230 dmi.product.version: Default string dmi.sys.vendor: Multicom To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1776155/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging + kernel-stable-phase-changed:Wednesday, 10. October 2018 13:33 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - phase: Packaging - kernel-stable-phase-changed:Wednesday, 10. October 2018 13:33 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- 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/1797062 Title: linux-gcp: 4.15.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
** Changed in: linux (Ubuntu Bionic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) ** Changed in: linux (Ubuntu Cosmic) Assignee: Joseph Salisbury (jsalisbury) => (unassigned) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
** Changed in: ubuntu-power-systems Importance: High => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1783957] Re: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence
** Tags removed: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1783957 Title: Nouveau crashes at login with Kernel 4.15.0-29 on MacBook Air, so no login screen in a normal sequence Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Status in linux source package in Cosmic: Triaged Bug description: I have a MacBook Air laptop which is running Linux (Kubuntu 16.04.5 LTS) with NVidia Graphics Card, KDE, Xorg, SDDM, and so on... Clean and natural install, no funky custom kernel or drivers or anything... Everything worked fine (with the 4.13.* kernel) until I've upgraded all my packages (which included the "wonderful" 4.15.0-29 kernel, which broke my system). Now, everytime I try to boot normally, it asks me for my disk password (I have an encrypted LVM) and after that, guess what ?: blank screen. The login screen does not appear. I can switch the Terminals with Ctrl+Alt+Fx, however. However, the same kernel, if I boot it in recovery mode and then I select "Resume", the login screen appears, but it lags a little bit... Needless to say, if I boot the older kernel (4.13), everything works perfectly. I dug up some logs and found something like "sddm-greeter" segmentation fault in nouveau_dri.so or something like this. So, it looks like the new kernel doesn't quite seem to look eye-to-eye with nouveau drivers... And no, I don't want the NVidia proprietary drivers because I get along just perfectly with Nouveau on other machines, and I don't want to reinstall nvidia drivers everytime I'm upgrading the kernel. And yes, I already have "haveged" installed, to provide sufficient entropy (I saw that the possible lack of entropy might be a problem in some cases)... If I boot in recovery mode and then select "resume", everything works. So, what is going on ? Any help would be appreciated... ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: xorg 1:7.7+13ubuntu3 ProcVersionSignature: Ubuntu 4.15.0-29.31~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-29-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: KDE Date: Fri Jul 27 10:40:31 2018 InstallationDate: Installed on 2018-07-04 (22 days ago) InstallationMedia: Kubuntu 16.04.4 LTS "Xenial Xerus" - Release amd64 (20180228) SourcePackage: xorg UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1783957/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794110] Re: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD
Thanks for the feedback. If you can get a list of additional commits that are needed in Bionic, that would be great. An alternative would be for us to perform a reverse bisect, but that would require a lot of testing and be time consuming. ** Changed in: linux (Ubuntu Cosmic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1794110 Title: MPS (Max Payload Size) is not correctly programmed upon Hot Insertion NVMe PCIe SSD Status in The Dell-poweredge project: New Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: In Progress Status in linux source package in Cosmic: Fix Committed Bug description: Max Payload Size for the NVMe device is not getting programmed correctly. The OS is trying to set the device MPS to match Root Port which is greater than Capability of Device, instead of looking for lowest common denominator. This is fixed in upstream kernel version 4.19. Below are the commits that fix the issue. Please help include them in Ubuntu releases. PCI: Skip MPS logic for Virtual Functions (VFs) https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=3dbe97efe8bf450b183d6dee2305cbc032e6b8a4 PCI: Match Root Port's MPS to endpoint's MPSS as necessary https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/pci/probe.c?h=v4.19-rc2&id=9f0e89359775ee21fe1ea732e34edb52aef5addf To manage notifications about this bug go to: https://bugs.launchpad.net/dell-poweredge/+bug/1794110/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1777674] Re: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD
Ideally, we'd want to bisect and fix the kernel itself to reliably shutdown. yanking ahci sounds like a large hammer. Invalidating systemd task, and pinging kernely people. ** Changed in: systemd (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1777674 Title: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers with DVD Status in dellserver: New Status in linux package in Ubuntu: Incomplete Status in systemd package in Ubuntu: Invalid Status in linux source package in Bionic: Incomplete Bug description: Ubuntu 18.04 hangs at "kvm: exiting hardware virtualization" on AMD servers when under graceful reboot stress for 12hrs. * This hand is observed only when Onboard SATA DVD Drive is connected. * Not seen with Ubuntu 16.04.4 (HWE kernel v4.13) * Seen with Ubuntu 18.04 (4.15.0-23-generic, 4.15.0-20-generic) Steps: Setup a DellEMC AMD server with Onboard DVD Drive, install Ubuntu 18.04 and start reboot stress After a few reboots, observe that the machine hangs at "kvm: exiting hardware virtualization" and does not proceed with reboot cycles. Only physical reset helps in continuing the reboot test. To manage notifications about this bug go to: https://bugs.launchpad.net/dellserver/+bug/1777674/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Would be nice having it on mainline. 😅 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795453] [NEW] IO's are issued with incorrect Scatter Gather Buffer
You have been subscribed to a public bug: We have observed that OS is sending the IO's (SCSI Read/Write) with incorrect Scatter Gather Buffer address . i.e OS is sending the IO with 64 bit Scatter Gather Buffer address , such that if we add the length with buffer address then it causes the roll over . Here is the data we captured in our driver (Printed the SGE details which was sent by OS) sgl_ptr->Address = f000 [14547.313240] sgl_ptr->Length = 1000 [14547.313241] sge_count = 18 [14547.313242] cmd->index = 9d9 Note : This issue is observed only when virtualization is enabled Product : Broadcom (LSI) Megaraid H840 controller ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed -- IO's are issued with incorrect Scatter Gather Buffer https://bugs.launchpad.net/bugs/1795453 You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797139] Re: arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
** Patch added:
"0001-arm64-Fix-proc-iomem-for-reserved-but-not-memory-reg.patch"
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797139/+attachment/5199511/+files/0001-arm64-Fix-proc-iomem-for-reserved-but-not-memory-reg.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/1797139
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1
arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
Status in linux package in Ubuntu:
Incomplete
Bug description:
Impact:
Upon boot on a dragonboard410c using a recent Bionic or Cosmic kernel:
...
[0.049776] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xe0/0x148
[0.049783] Modules linked in:
[0.049797] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-8-snapdragon
#9
[0.049803] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.049813] pstate: 8045 (Nzcv daif +PAN -UAO)
[0.049821] pc : reserve_memblock_reserved_regions+0xe0/0x148
[0.049829] lr : reserve_memblock_reserved_regions+0xd8/0x148
[0.049836] sp : 08033d40
[0.049841] x29: 08033d40 x28:
[0.049852] x27: 09410584 x26: 09577018
[0.049863] x25: x24: 00488020
[0.049874] x23: bfff x22: 090e8928
[0.049885] x21: 08ffb578 x20: 09a48708
[0.049896] x19: 80003a409280 x18:
[0.049906] x17: x16:
[0.049917] x15: x14: 09a48708
[0.049927] x13: x12: 0028
[0.049938] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[0.049949] x9 : x8 : 80003a409300
[0.049959] x7 : x6 : 003f
[0.049969] x5 : 0040 x4 : 80003d9ffc70
[0.049980] x3 : bd9f x2 : 09c241b0
[0.049990] x1 : x0 :
[0.050001] Call trace:
[0.050010] reserve_memblock_reserved_regions+0xe0/0x148
[0.050021] do_one_initcall+0x54/0x1e0
[0.050031] kernel_init_freeable+0x254/0x2f8
[0.050043] kernel_init+0x18/0x110
[0.050052] ret_from_fork+0x10/0x18
[0.050063] ---[ end trace dc768b294fafe4aa ]---
...
commit 50d7ba36b916 upstream ("arm64: export memblock_reserve()d regions via
/proc/iomem") backported in commit 62289841 in bionic/master, wrongly assumed
that memblock_reserve() would not be used to reserve regions that aren't
memory. It turns out, this is exactly what early_init_dt_reserve_memory_arch()
will do if it finds a reservation
that was also carved out of the memory node.
Fix:
Apply the attached patch and recompile
The fix wad discussed here: https://www.spinics.net/lists/arm-
kernel/msg675580.html
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
The patch didn't make it upstream yet, but the fix is very small and
was tested on the lkml.
Proposing for Bionic and Cosmic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797139/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797139] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem.
While running an Ubuntu kernel (not a mainline or third-party kernel)
please enter the following command in a terminal window:
apport-collect 1797139
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable
to run this command, please add a comment stating that fact and change
the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the
Ubuntu Kernel Team.
** Changed in: linux (Ubuntu)
Status: New => Incomplete
** Tags added: cosmic
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1797139
Title:
arm64: snapdragon: WARNING: CPU: 0 PID: 1
arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
Status in linux package in Ubuntu:
Incomplete
Bug description:
Impact:
Upon boot on a dragonboard410c using a recent Bionic or Cosmic kernel:
...
[0.049776] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xe0/0x148
[0.049783] Modules linked in:
[0.049797] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-8-snapdragon
#9
[0.049803] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.049813] pstate: 8045 (Nzcv daif +PAN -UAO)
[0.049821] pc : reserve_memblock_reserved_regions+0xe0/0x148
[0.049829] lr : reserve_memblock_reserved_regions+0xd8/0x148
[0.049836] sp : 08033d40
[0.049841] x29: 08033d40 x28:
[0.049852] x27: 09410584 x26: 09577018
[0.049863] x25: x24: 00488020
[0.049874] x23: bfff x22: 090e8928
[0.049885] x21: 08ffb578 x20: 09a48708
[0.049896] x19: 80003a409280 x18:
[0.049906] x17: x16:
[0.049917] x15: x14: 09a48708
[0.049927] x13: x12: 0028
[0.049938] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[0.049949] x9 : x8 : 80003a409300
[0.049959] x7 : x6 : 003f
[0.049969] x5 : 0040 x4 : 80003d9ffc70
[0.049980] x3 : bd9f x2 : 09c241b0
[0.049990] x1 : x0 :
[0.050001] Call trace:
[0.050010] reserve_memblock_reserved_regions+0xe0/0x148
[0.050021] do_one_initcall+0x54/0x1e0
[0.050031] kernel_init_freeable+0x254/0x2f8
[0.050043] kernel_init+0x18/0x110
[0.050052] ret_from_fork+0x10/0x18
[0.050063] ---[ end trace dc768b294fafe4aa ]---
...
commit 50d7ba36b916 upstream ("arm64: export memblock_reserve()d regions via
/proc/iomem") backported in commit 62289841 in bionic/master, wrongly assumed
that memblock_reserve() would not be used to reserve regions that aren't
memory. It turns out, this is exactly what early_init_dt_reserve_memory_arch()
will do if it finds a reservation
that was also carved out of the memory node.
Fix:
Apply the attached patch and recompile
The fix wad discussed here: https://www.spinics.net/lists/arm-
kernel/msg675580.html
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
The patch didn't make it upstream yet, but the fix is very small and
was tested on the lkml.
Proposing for Bionic and Cosmic.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797139/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797139] [NEW] arm64: snapdragon: WARNING: CPU: 0 PID: 1 arch/arm64/kernel/setup.c:271 reserve_memblock_reserved_regions
Public bug reported:
Impact:
Upon boot on a dragonboard410c using a recent Bionic or Cosmic kernel:
...
[0.049776] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xe0/0x148
[0.049783] Modules linked in:
[0.049797] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-8-snapdragon #9
[0.049803] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.049813] pstate: 8045 (Nzcv daif +PAN -UAO)
[0.049821] pc : reserve_memblock_reserved_regions+0xe0/0x148
[0.049829] lr : reserve_memblock_reserved_regions+0xd8/0x148
[0.049836] sp : 08033d40
[0.049841] x29: 08033d40 x28:
[0.049852] x27: 09410584 x26: 09577018
[0.049863] x25: x24: 00488020
[0.049874] x23: bfff x22: 090e8928
[0.049885] x21: 08ffb578 x20: 09a48708
[0.049896] x19: 80003a409280 x18:
[0.049906] x17: x16:
[0.049917] x15: x14: 09a48708
[0.049927] x13: x12: 0028
[0.049938] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
[0.049949] x9 : x8 : 80003a409300
[0.049959] x7 : x6 : 003f
[0.049969] x5 : 0040 x4 : 80003d9ffc70
[0.049980] x3 : bd9f x2 : 09c241b0
[0.049990] x1 : x0 :
[0.050001] Call trace:
[0.050010] reserve_memblock_reserved_regions+0xe0/0x148
[0.050021] do_one_initcall+0x54/0x1e0
[0.050031] kernel_init_freeable+0x254/0x2f8
[0.050043] kernel_init+0x18/0x110
[0.050052] ret_from_fork+0x10/0x18
[0.050063] ---[ end trace dc768b294fafe4aa ]---
...
commit 50d7ba36b916 upstream ("arm64: export memblock_reserve()d regions via
/proc/iomem") backported in commit 62289841 in bionic/master, wrongly assumed
that memblock_reserve() would not be used to reserve regions that aren't
memory. It turns out, this is exactly what early_init_dt_reserve_memory_arch()
will do if it finds a reservation
that was also carved out of the memory node.
Fix:
Apply the attached patch and recompile
The fix wad discussed here: https://www.spinics.net/lists/arm-
kernel/msg675580.html
How to test:
Boot the patched kernel and check for the above WARNING in dmesg
Regression potential:
The patch didn't make it upstream yet, but the fix is very small and was
tested on the lkml.
Proposing for Bionic and Cosmic.
** Affects: linux (Ubuntu)
Importance: Undecided
Status: Incomplete
** Tags: cosmic
** Description changed:
Impact:
- Upon boot on a recent bionic or cosmic kernel:
+ Upon boot on a dragonboard410c using a recent bionic or cosmic kernel:
...
[0.049776] WARNING: CPU: 0 PID: 1 at arch/arm64/kernel/setup.c:271
reserve_memblock_reserved_regions+0xe0/0x148
[0.049783] Modules linked in:
[0.049797] CPU: 0 PID: 1 Comm: swapper/0 Not tainted 4.18.0-8-snapdragon
#9
[0.049803] Hardware name: Qualcomm Technologies, Inc. APQ 8016 SBC (DT)
[0.049813] pstate: 8045 (Nzcv daif +PAN -UAO)
[0.049821] pc : reserve_memblock_reserved_regions+0xe0/0x148
[0.049829] lr : reserve_memblock_reserved_regions+0xd8/0x148
[0.049836] sp : 08033d40
- [0.049841] x29: 08033d40 x28:
- [0.049852] x27: 09410584 x26: 09577018
- [0.049863] x25: x24: 00488020
- [0.049874] x23: bfff x22: 090e8928
- [0.049885] x21: 08ffb578 x20: 09a48708
- [0.049896] x19: 80003a409280 x18:
- [0.049906] x17: x16:
- [0.049917] x15: x14: 09a48708
- [0.049927] x13: x12: 0028
- [0.049938] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
- [0.049949] x9 : x8 : 80003a409300
- [0.049959] x7 : x6 : 003f
- [0.049969] x5 : 0040 x4 : 80003d9ffc70
- [0.049980] x3 : bd9f x2 : 09c241b0
- [0.049990] x1 : x0 :
+ [0.049841] x29: 08033d40 x28:
+ [0.049852] x27: 09410584 x26: 09577018
+ [0.049863] x25: x24: 00488020
+ [0.049874] x23: bfff x22: 090e8928
+ [0.049885] x21: 08ffb578 x20: 09a48708
+ [0.049896] x19: 80003a409280 x18:
+ [0.049906] x17: x16:
+ [0.049917] x15: x14: 09a48708
+ [0.049927] x13: x12: 0028
+ [0.049938] x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
+ [0.049949] x9 : x8 : 80003a4
[Kernel-packages] [Bug 1792102] Re: Ubuntu18.04: GPU total memory is reduced
** Changed in: ubuntu-power-systems
Importance: High => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792102
Title:
Ubuntu18.04: GPU total memory is reduced
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
Due to a recent change for powernv, now the total GPU memory is no longer
available. This impacts performance for any application/benchmark has a
large GPU memory utilization.
IBM is requesting mainlien commit 7acf50e4efa6 in Bionic, which reverts
mainline commit 4b5d62ca17a1.
== Fix ==
7acf50e4efa6 ("Revert "powerpc/powernv: Increase memory block size to 1GB on
radix"")
== Regression Potential ==
Low. This is a revert that was also done upstream due to a regression.
Limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Michael Ranweiler - 2018-09-10
19:26:14 ==
Due to a recent change for powernv, now the total GPU memory is no
longer available. This impacts performance for any
application/benchmark has a large GPU memory utilization.
Previous amount of memory : 16128MiB
Current amount of available memory : 15360MiB
From Anton, describing the recent change.:
powerpc/powernv: Increase memory block size to 1GB on radix
Memory hot unplug on PowerNV radix hosts is broken. Our memory block
size is 256MB but since we map the linear region with very large
pages, each pte we tear down maps 1GB.
A hot unplug of one 256MB memory block results in 768MB of memory
getting unintentionally unmapped. At this point we are likely to oops.
Fix this by increasing our memory block size to 1GB on PowerNV radix
hosts.
Fixes: 4b5d62ca17a1 ("powerpc/mm: add
radix__remove_section_mapping()")
This is fixed with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7acf50e4efa6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792102/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules
** Description changed: + SRU Justification + + Impact: Vagrant environments are no longer able to use virtualbox + feartures like shared folders. This is due to Ubuntu Cosmic kernels + currently shipping the upstream vboxguest module and not importing + modules from the virtualbox-guest-dkms package. + + Fix: One solution would be to use the dkms modules for Vagrant, but this + is not ideal. At this late stage the simplest solution is to go back to + importing the out-of-tree modules. + + Regression Potential: Minimal. Will have no impact outside of virtualbox + environments, and the drivers being imported come from the virtualbox- + guest-dkms package in cosmic and are thus expected to work well. + + --- + In bionic, the vboxsf module was included in linux-modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). - [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Changed in: linux (Ubuntu) Status: Confirmed => In Progress ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) ** Also affects: linux (Ubuntu Cosmic) Importance: High Assignee: Seth Forshee (sforshee) Status: In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: In Progress Status in linux source package in Cosmic: In Progress Bug description: SRU Justification Impact: Vagrant environments are no longer able to use virtualbox feartures like shared folders. This is due to Ubuntu Cosmic kernels currently shipping the upstream vboxguest module and not importing modules from the virtualbox-guest-dkms package. Fix: One solution would be to use the dkms modules for Vagrant, but this is not ideal. At this late stage the simplest solution is to go back to importing the out-of-tree modules. Regression Potential: Minimal. Will have no impact outside of virtualbox environments, and the drivers being imported come from the virtualbox-guest-dkms package in cosmic and are thus expected to work well. --- In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mou
[Kernel-packages] [Bug 1797066] Re: linux-aws: 4.15.0-1025.25 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- 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/1797066 Title: linux-aws: 4.15.0-1025.25 -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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797065] Re: linux-kvm: 4.15.0-1025.25 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging + kernel-stable-phase-changed:Wednesday, 10. October 2018 13:32 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - phase: Packaging - kernel-stable-phase-changed:Wednesday, 10. October 2018 13:32 UTC - kernel-stable-phase:Uploaded + phase: Uploaded -- 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/1797065 Title: linux-kvm: 4.15.0-1025.25 -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: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
** Changed in: linux (Ubuntu) Importance: Medium => Critical ** Changed in: linux (Ubuntu Bionic) Importance: Medium => Critical -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792102] Re: Ubuntu18.04: GPU total memory is reduced
** Changed in: linux (Ubuntu)
Importance: High => Critical
** Changed in: linux (Ubuntu Bionic)
Importance: High => Critical
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1792102
Title:
Ubuntu18.04: GPU total memory is reduced
Status in The Ubuntu-power-systems project:
In Progress
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
== SRU Justification ==
Due to a recent change for powernv, now the total GPU memory is no longer
available. This impacts performance for any application/benchmark has a
large GPU memory utilization.
IBM is requesting mainlien commit 7acf50e4efa6 in Bionic, which reverts
mainline commit 4b5d62ca17a1.
== Fix ==
7acf50e4efa6 ("Revert "powerpc/powernv: Increase memory block size to 1GB on
radix"")
== Regression Potential ==
Low. This is a revert that was also done upstream due to a regression.
Limited to powerpc.
== Test Case ==
A test kernel was built with this patch and tested by the original bug
reporter.
The bug reporter states the test kernel resolved the bug.
== Comment: #0 - Michael Ranweiler - 2018-09-10
19:26:14 ==
Due to a recent change for powernv, now the total GPU memory is no
longer available. This impacts performance for any
application/benchmark has a large GPU memory utilization.
Previous amount of memory : 16128MiB
Current amount of available memory : 15360MiB
From Anton, describing the recent change.:
powerpc/powernv: Increase memory block size to 1GB on radix
Memory hot unplug on PowerNV radix hosts is broken. Our memory block
size is 256MB but since we map the linear region with very large
pages, each pte we tear down maps 1GB.
A hot unplug of one 256MB memory block results in 768MB of memory
getting unintentionally unmapped. At this point we are likely to oops.
Fix this by increasing our memory block size to 1GB on PowerNV radix
hosts.
Fixes: 4b5d62ca17a1 ("powerpc/mm: add
radix__remove_section_mapping()")
This is fixed with:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=7acf50e4efa6
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792102/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
Thanks for the backport! I built a test kernel with commits f08d08f3db5545 and your backport of 2bf1071a8d50928. The test kernel can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1792195 Can you test this kernel and see if it resolves this bug? Note about installing test kernels: • If the test kernel is prior to 4.15(Bionic) you need to install the linux-image and linux-image-extra .deb packages. • If the test kernel is 4.15(Bionic) or newer, you need to install the linux-modules, linux-modules-extra and linux-image-unsigned .deb packages. Thanks in advance! -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released -- 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/1797062 Title: linux-gcp: 4.15.0-1023.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package-meta Status: In Progress => Fix Released ** Changed in: kernel-sru-workflow/prepare-package-signed Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797061 Title: linux: 4.15.0-38.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) kernel-stable-phase-changed:Wednesday, 10. October 2018 11:02 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797002] Re: all my bluetooth headsets skips terribly after todays update
I'm experiencing this as well. After rebooting today for the first time since September 25, I noticed somewhat choppy audio over bluetooth, first with mp3s on disk, then tried Youtube and it was significantly worse. Same audio content over laptop speakers seems to play without problems. Attaching a pulseaudio verbose log in case that helps. ** Attachment added: "pulseverbose.log" https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+attachment/5199509/+files/pulseverbose.log -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to bluez in Ubuntu. https://bugs.launchpad.net/bugs/1797002 Title: all my bluetooth headsets skips terribly after todays update Status in bluez package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Bug description: all my bluetooth headsets skips terribly after today's system update. it is heavy noticeable even on audio setting test form. it work just fine today before i applied updates. even reinstall ubuntu from scratch - didn't help. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: bluetooth (not installed) ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 18:40:44 2018 EcryptfsInUse: Yes InstallationDate: Installed on 2018-10-09 (0 days ago) InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725) InterestingModules: rfcomm bnep btusb bluetooth MachineType: Hewlett-Packard HP ENVY 17 Notebook PC ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-36-generic root=UUID=fc44a9dc-e173-43fb-ac3a-fdeadb1066e0 ro quiet splash vt.handoff=1 SourcePackage: bluez UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 09/22/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.66 dmi.board.asset.tag: Type2 - Board Asset Tag dmi.board.name: 1968 dmi.board.vendor: Hewlett-Packard dmi.board.version: KBC Version 93.52 dmi.chassis.asset.tag: 5CG32907G7 dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.66:bd09/22/2015:svnHewlett-Packard:pnHPENVY17NotebookPC:pvr088510305B0610100:rvnHewlett-Packard:rn1968:rvrKBCVersion93.52:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP S=ENV dmi.product.name: HP ENVY 17 Notebook PC dmi.product.version: 088510305B0610100 dmi.sys.vendor: Hewlett-Packard hciconfig: hci0:Type: Primary Bus: USB BD Address: 68:17:29:62:BE:6A ACL MTU: 310:10 SCO MTU: 64:8 UP RUNNING PSCAN ISCAN INQUIRY RX bytes:16831 acl:64 sco:0 events:1798 errors:0 TX bytes:688571 acl:2399 sco:0 commands:125 errors:0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/1797002/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
Would it be possible for you to test out some test kernels? That would allow us to reverse bisect and identify any missing commits from the 4.4 kernel. ** Tags added: performing-bisect -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797080] Re: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- 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/1797080 Title: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797065] Re: linux-kvm: 4.15.0-1025.25 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Uploaded + kernel-stable-phase:Uploaded + kernel-stable-phase-changed:Wednesday, 10. October 2018 14:02 UTC ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Uploaded - kernel-stable-phase:Uploaded - kernel-stable-phase-changed:Wednesday, 10. October 2018 14:02 UTC -- 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/1797065 Title: linux-kvm: 4.15.0-1025.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795585] Re: linux-aws: 4.4.0-1070.80 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-beta Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/snap-release-to-candidate Status: New => Confirmed ** Changed in: kernel-sru-workflow/snap-release-to-edge Status: Confirmed => Fix Released -- 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/1795585 Title: linux-aws: 4.4.0-1070.80 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795582 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795585/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797080] Re: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker ** Changed in: kernel-sru-workflow/prepare-package Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/prepare-package Assignee: Canonical Kernel Team (canonical-kernel-team) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1797080 Title: linux-gcp: 4.15.0-1023.24~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797031] Re: Touchscreen/stylus always reports 1% battery [patch]
Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem? Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.19 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.19-rc7 ** Changed in: linux (Ubuntu) Importance: Undecided => Medium ** 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/1797031 Title: Touchscreen/stylus always reports 1% battery [patch] Status in linux package in Ubuntu: Incomplete Bug description: I have a Dell 5379 with a touchscreen that always reports 1% battery with the stylus. This pops up a low battery notification the first time I use the stylus after booting. The attached patch tells the kernel to ignore the battery on this particular device, since it appears to not report information correctly anyway. ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-4.15.0-36-generic 4.15.0-36.39 ProcVersionSignature: Ubuntu 4.15.0-36.39-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.4 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: trent 1734 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Tue Oct 9 22:42:47 2018 HibernationDevice: RESUME=UUID=aef6a948-4599-4581-99a2-44b7944d2d58 InstallationDate: Installed on 2018-05-10 (153 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 004: ID 04f3:2361 Elan Microelectronics Corp. Bus 001 Device 003: ID 8087:0025 Intel Corp. Bus 001 Device 002: ID 0bda:5696 Realtek Semiconductor Corp. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub MachineType: Dell Inc. Inspiron 5379 ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcFB: 0 inteldrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-4.15.0-36-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.15.0-36-generic N/A linux-backports-modules-4.15.0-36-generic N/A linux-firmware 1.173.1 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 07/19/2018 dmi.bios.vendor: Dell Inc. dmi.bios.version: 1.10.0 dmi.board.name: 05G60G dmi.board.vendor: Dell Inc. dmi.board.version: A00 dmi.chassis.type: 10 dmi.chassis.vendor: Dell Inc. dmi.modalias: dmi:bvnDellInc.:bvr1.10.0:bd07/19/2018:svnDellInc.:pnInspiron5379:pvr:rvnDellInc.:rn05G60G:rvrA00:cvnDellInc.:ct10:cvr: dmi.product.family: Inspiron dmi.product.name: Inspiron 5379 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797031/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797092] Re: xenial guest on arm64 drops to busybux under openstack bionic-rocky
** Changed in: linux (Ubuntu) Importance: Undecided => High ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => High ** Changed in: linux (Ubuntu Bionic) Status: New => Triaged ** Changed in: linux (Ubuntu) Status: Incomplete => Triaged ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Triaged Status in linux source package in Bionic: Triaged Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1794067] Re: Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34
Can you test the following kernels and report back? We are looking for
the first kernel version that exhibits this bug:
For 4.14 and earlier kernels, install the linux-image and linux-image-extra
.deb packages:
4.14.0-11:
https://launchpad.net/~canonical-kernel-team/+archive/ubuntu/bootstrap/+build/13813977
4.14.0-16: https://launchpad.net/~canonical-kernel-security-
team/+archive/ubuntu/ppa2/+build/14223014
4.15.0-9: https://launchpad.net/ubuntu/+source/linux/4.15.0-9.10/+build/14326410
4.15.0-20:
https://launchpad.net/ubuntu/+source/linux/4.15.0-20.21/+build/14791489
You don't have to test every kernel, just up until the kernel that first
has this bug.
Thanks in advance!
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1794067
Title:
Bug in selinux on ubuntu 16.04 with kernel 4.15.0-34
Status in linux package in Ubuntu:
In Progress
Status in linux source package in Bionic:
In Progress
Bug description:
Hello, just found a bug in selinux.
Whats going wrong:
Copy a link with "-a" option while selinux is on.
steps to reproduce:
~$ mkdir -p a/b
~$ ln -s b a/c
~$ cp -a a b
cp: failed to restore the default file creation context: Invalid argument
Results of my investigation:
The "cp" of coreutils is calling "setfscreatecon (NULL)" to restore
the default file creation context (coreutils-8.30/src/copy.c:1771) as
it is stated in the selinux api
(/libselinux/include/selinux/selinux.h:71).
As we see in the result of strace below, the kernel returns an -1 on
try to restore the default file creation context. So in my opinion is
the bug has to be in the selinux_setprocattr method in the
security/selinux/hooks.c file.
Part of "strace cp -a a b"
lgetxattr("a/c", "security.selinux", "system_u:object_r:user_home_dir_t:s0",
255) = 37
readlink("a/c", "b", 2) = 1
symlink("b", "b/a/c") = 0
open("/proc/self/task/2136/attr/fscreate", O_RDWR|O_CLOEXEC) = 3
write(3, NULL, 0) = -1 EINVAL (Invalid argument)
close(3) = 0
open("/usr/share/locale/locale.alias", O_RDONLY|O_CLOEXEC) = 3
fstat(3, {st_mode=S_IFREG|0644, st_size=2995, ...}) = 0
read(3, "# Locale name alias data base.\n#"..., 4096) = 2995
read(3, "", 4096) = 0
close(3)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1794067/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1752772] Re: r8169 ethernet card don't work after returning from suspension
The system is not detecting ethernet connection when the ethernet cable is connected after boot. The system detects ethernet connection when the ethernet cable is already plugged into the system and system is rebooted. The system stops detecting ethernet connection after waking up from suspend. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1752772 Title: r8169 ethernet card don't work after returning from suspension Status in linux package in Ubuntu: Fix Released Status in linux source package in Bionic: Fix Released Bug description: ===SRU Justification=== [Impact] Ethernet r8169 stops working after system resumed from suspend. [Test] User confirmed these patches fix the issue. r8169 continues to work after resume from suspend. [Regression Potential] Medium. The fix is limited to one device, all patches are in mainline. The WOL default change might cause regression for users that depend on BIOS settings. We can advice them to use userspace tool (systemd, ethtool, etc.) instead. ===Original Bug Report=== I have noticed that the network stopped working on my desktop after I've suspended the system and woke it up. On dmesg there are messages like: [ 150.877998] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready [ 150.944101] do_IRQ: 3.37 No irq handler for vector [ 150.944105] r8169 :01:00.0 enp1s0: link down [ 150.944180] IPv6: ADDRCONF(NETDEV_UP): enp1s0: link is not ready When using Xenial (from a different install), this problem is not happening. This is happening on Bionic. There are only two ways to restore connectivity: 1) Reboot the system; 2) Remove the r8169 module and reinsert it with modprobe. The motherboard is a AsRock H55M-LE and the Ethernet controller is: 01:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-firmware 1.172 ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 Uname: Linux 4.15.0-10-generic x86_64 ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 CurrentDesktop: LXDE Date: Fri Mar 2 00:21:57 2018 Dependencies: InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) PackageArchitecture: all SourcePackage: linux-firmware UpgradeStatus: No upgrade log present (probably fresh install) --- AlsaVersion: Advanced Linux Sound Architecture Driver Version k4.15.0-10-generic. ApportVersion: 2.20.8-0ubuntu10 Architecture: amd64 ArecordDevices: List of CAPTURE Hardware Devices card 0: MID [HDA Intel MID], device 0: VT1818S Analog [VT1818S Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: usuario1153 F pulseaudio /dev/snd/controlC1: usuario1153 F pulseaudio Card0.Amixer.info: Card hw:0 'MID'/'HDA Intel MID at 0xfbdf8000 irq 26' Mixer name : 'VIA VT1818S' Components : 'HDA:11060440,18492818,0010' Controls : 40 Simple ctrls : 17 Card1.Amixer.info: Card hw:1 'HDMI'/'HDA ATI HDMI at 0xfbffc000 irq 27' Mixer name : 'ATI R6xx HDMI' Components : 'HDA:1002aa01,00aa0100,00100200' Controls : 7 Simple ctrls : 1 Card1.Amixer.values: Simple mixer control 'IEC958',0 Capabilities: pswitch pswitch-joined Playback channels: Mono Mono: Playback [on] CurrentDesktop: LXDE Dependencies: DistroRelease: Ubuntu 18.04 HibernationDevice: RESUME=UUID=edd83175-c707-4b31-90d2-ce2f5cebc73f InstallationDate: Installed on 2018-02-26 (3 days ago) InstallationMedia: Lubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180226) MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M. Package: linux-firmware 1.172 PackageArchitecture: all ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz root=UUID=0c4fc517-b7a0-49b0-bfcb-0485dfe6413b ro quiet ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3 RelatedPackageVersions: linux-restricted-modules-4.15.0-10-generic N/A linux-backports-modules-4.15.0-10-generic N/A linux-firmware 1.172 RfKill: Tags: bionic Uname: Linux 4.15.0-10-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip libvirt lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 10/20/2010 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: P1.80 dmi.board.name: H55M-LE dmi.board.vendor: ASRock dmi.chassis.asset.tag: To Be Filled By O.E.M. dmi.chassis.type: 3 dmi.chassis.vendor: To Be Filled By O.E.M. dmi.chassis.version: To Be Filled By O.E.M. dmi.modalias: dmi:bvnAmericanMegatrends
[Kernel-packages] [Bug 1797066] Re: linux-aws: 4.15.0-1025.25 -proposed tracker
** Summary changed: - linux-aws: -proposed tracker + linux-aws: 4.15.0-1025.25 -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) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1797066 Title: linux-aws: 4.15.0-1025.25 -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: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker
** Summary changed: - linux-gcp: -proposed tracker + linux-gcp: 4.15.0-1023.24 -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) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1797062 Title: linux-gcp: 4.15.0-1023.24 -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: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796253] Re: With one flash drive connected other flash drive doesn't connect anymore
Can you please write step by step how to do that. As I understand usbcore.dyndbg=+p I should add to boot options. But how to get dmesg? Just writing dmesg in bash terminal? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796253 Title: With one flash drive connected other flash drive doesn't connect anymore Status in linux package in Ubuntu: Incomplete Bug description: I have a Toshiba L855 laptop at home. When I connect any usb device to a USB3 port before boot then no other USB device doesn't work and even detected after boot. This concern even USB mouse and keyboard. But when I reconnect all USB devices to laptop then they started to work. I see this behaviour on every ubuntu 16.04.5 linux kernel i.e. version 4.15, so I suspect that it is due to some linux-extra-module. I have also windows 7 OS on the same laptop and I have never struck such a problem there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-36-generic 4.15.0-36.39~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Oct 5 12:17:20 2018 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2018-05-25 (132 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796253] Re: With one flash drive connected other flash drive doesn't connect anymore
Can you boot v4.19-rc7 with kernel parameter "usbcore.dyndbg=+p"? After the issue is reproduced, attach dmesg to this bug. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796253 Title: With one flash drive connected other flash drive doesn't connect anymore Status in linux package in Ubuntu: Incomplete Bug description: I have a Toshiba L855 laptop at home. When I connect any usb device to a USB3 port before boot then no other USB device doesn't work and even detected after boot. This concern even USB mouse and keyboard. But when I reconnect all USB devices to laptop then they started to work. I see this behaviour on every ubuntu 16.04.5 linux kernel i.e. version 4.15, so I suspect that it is due to some linux-extra-module. I have also windows 7 OS on the same laptop and I have never struck such a problem there. ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-modules-extra-4.15.0-36-generic 4.15.0-36.39~16.04.1 ProcVersionSignature: Ubuntu 4.15.0-36.39~16.04.1-generic 4.15.18 Uname: Linux 4.15.0-36-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.18 Architecture: amd64 CurrentDesktop: GNOME-Flashback:Unity Date: Fri Oct 5 12:17:20 2018 SourcePackage: linux-hwe UpgradeStatus: Upgraded to xenial on 2018-05-25 (132 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796253/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797062] Re: linux-gcp: 4.15.0-1023.24 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- 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/1797062 Title: linux-gcp: 4.15.0-1023.24 -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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Boris, Can you attach dmesg? Or even better, file a new bug since it may be a different issue. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796647] Re: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules
** Tags added: id-5bbcaca75adf6a4fe571e8ad -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796647 Title: Shared folders cannot be mounted in ubuntu/cosmic64 due to missing vbox modules Status in cloud-images: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: In bionic, the vboxsf module was included in linux- modules-...-generic: $ dpkg -c linux-modules-4.15.0-36-generic_4.15.0-36.39_amd64.deb | grep vboxsf.ko -rw-r--r-- root/root 63238 2018-09-24 10:08 ./lib/modules/4.15.0-36-generic/kernel/ubuntu/vbox/vboxsf/vboxsf.ko In cosmic, it isn't: $ dpkg -c ~/Downloads/linux- modules-4.18.0-9-generic_4.18.0-9.10_amd64.deb | grep vboxsf.ko This results in shared folders no longer being mountable in Ubuntu Vagrant boxes (and, as the other vbox modules are also missing, probably has other effects that haven't yet been reported). [Original Report] Just tried to test out the new cosmic64 vagrant box and get the following error; ``` Vagrant was unable to mount VirtualBox shared folders. This is usually because the filesystem "vboxsf" is not available. This filesystem is made available via the VirtualBox Guest Additions and kernel module. Please verify that these guest additions are properly installed in the guest. This is not a bug in Vagrant and is usually caused by a faulty Vagrant box. For context, the command attempted was: mount -t vboxsf -o uid=1000,gid=1000 vagrant /vagrant The error output from the command was: /sbin/mount.vboxsf: mounting failed with the error: No such device ``` I tried with ubuntu/bionic64 and it worked fine. I've got; $ vagrant version Installed Version: 2.1.5 Latest Version: 2.1.5 You're running an up-to-date version of Vagrant! $ VBoxManage --version 5.2.18r124319 $ To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-images/+bug/1796647/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1793430] Re: Page leaking in cachefiles_read_backing_file while vmscan is active
** Tags removed: verification-needed-xenial ** Tags added: verification-done-xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1793430 Title: Page leaking in cachefiles_read_backing_file while vmscan is active Status in linux package in Ubuntu: Fix Committed Status in linux source package in Xenial: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Bug description: SRU Justification - [Description] In a heavily loaded system where the system pagecache is nearing memory limits and fscache is enabled, pages can be leaked by fscache while trying read pages from cachefiles backend. This can happen because two applications can be reading same page from a single mount, two threads can be trying to read the backing page at same time. This results in one of the thread finding that a page for the backing file or netfs file is already in the radix tree. During the error handling cachefiles does not cleanup the reference on backing page, leading to page leak. [Fix] The fix is straightforward, to decrement the reference when error is encounterd. [Testing] A user has tested the fix using following method for 12+ hrs. 1) mkdir -p /mnt/nfs ; mount -o vers=3,fsc :/export /mnt/nfs 2) create 1 files of 2.8MB in a NFS mount. 3) start a thread to simulate heavy VM presssure (while true ; do echo 3 > /proc/sys/vm/drop_caches ; sleep 1 ; done)& 4) start multiple parallel reader for data set at same time find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & .. .. find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & find /mnt/nfs -type f | xargs -P 80 cat > /dev/null & 5) finally check using cat /proc/fs/fscache/stats | grep -i pages ; free -h , cat /proc/meminfo and page-types -r -b lru to ensure all pages are freed. [Regression Potential] Limited to cachefiles. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1793430/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797065] Re: linux-kvm: 4.15.0-1025.25 -proposed tracker
** Summary changed: - linux-kvm: -proposed tracker + linux-kvm: 4.15.0-1025.25 -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) => Kleber Sacilotto de Souza (kleber-souza) ** 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) => Kleber Sacilotto de Souza (kleber-souza) -- 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/1797065 Title: linux-kvm: 4.15.0-1025.25 -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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
@jsalisbury: ant_sel=1 with 4.15.0-36 kernel gives no improvement, both ant_sel 1 & 2 yield a poor signal. So, I believe http://kernel.ubuntu.com/~jsalisbury/lp1788997 has the problem fixed, but only with ant_sel=1. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797067] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:30 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - kernel-stable-phase-changed:Wednesday, 10. October 2018 11:30 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1797067 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa 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: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797067/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797066] Re: linux-aws: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:31 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - kernel-stable-phase-changed:Wednesday, 10. October 2018 11:31 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1797066 Title: linux-aws: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797066/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797082] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:33 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - kernel-stable-phase-changed:Wednesday, 10. October 2018 11:33 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1797082 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797082/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797080] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:32 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - kernel-stable-phase-changed:Wednesday, 10. October 2018 11:32 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1797080 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797080/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796720] Re: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460
Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.18.13 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'. Once testing of the upstream kernel is complete, please mark this bug as "Confirmed". Thanks in advance. [0]http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.18.13/ ** Changed in: linux (Ubuntu) Status: Triaged => 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/1796720 Title: High GPU temperature after kernel 4.18.0.9.10 on AMD RX460 Status in Linux: Unknown Status in linux package in Ubuntu: Incomplete Bug description: Hello, Today I have received an update for Linux kernel which upgraded the kernel on my Ubuntu 18.10 installation to 4.18.0.9.10! Immediately after restart I noticed that the GPU temperature is abnormally High... Before Update: - GPU fan set to off on idle - GPU idle temperature: 29-32 C After Update: - GPU fan set to off on idle - GPU idle temperature: 47-50 C (which I have to put the fans on 50% to keep it on 33 C) I have also tried to boot from the older kernel (4.18.0.8) and everything is normal there! System spec: - MB: ASUS Prime x299-deluxe - CPU: Intel Corei7 7820x skylake-x - GPU: AMD RX460 glxinfo | grep OpenGL: OpenGL vendor string: X.Org OpenGL renderer string: AMD Radeon (TM) RX 460 Graphics (POLARIS11, DRM 3.26.0, 4.18.0-9-generic, LLVM 7.0.0) OpenGL core profile version string: 4.5 (Core Profile) Mesa 18.2.1 OpenGL core profile shading language version string: 4.50 OpenGL core profile context flags: (none) OpenGL core profile profile mask: core profile OpenGL core profile extensions: OpenGL version string: 4.4 (Compatibility Profile) Mesa 18.2.1 OpenGL shading language version string: 4.40 OpenGL context flags: (none) OpenGL profile mask: compatibility profile OpenGL extensions: OpenGL ES profile version string: OpenGL ES 3.2 Mesa 18.2.1 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.20 OpenGL ES profile extensions: sudo cat /sys/kernel/debug/dri/0/amdgpu_pm_info: Clock Gating Flags Mask: 0x37bcf Graphics Medium Grain Clock Gating: On Graphics Medium Grain memory Light Sleep: On Graphics Coarse Grain Clock Gating: On Graphics Coarse Grain memory Light Sleep: On Graphics Coarse Grain Tree Shader Clock Gating: Off Graphics Coarse Grain Tree Shader Light Sleep: Off Graphics Command Processor Light Sleep: On Graphics Run List Controller Light Sleep: On Graphics 3D Coarse Grain Clock Gating: Off Graphics 3D Coarse Grain memory Light Sleep: Off Memory Controller Light Sleep: On Memory Controller Medium Grain Clock Gating: On System Direct Memory Access Light Sleep: Off System Direct Memory Access Medium Grain Clock Gating: On Bus Interface Medium Grain Clock Gating: Off Bus Interface Light Sleep: On Unified Video Decoder Medium Grain Clock Gating: On Video Compression Engine Medium Grain Clock Gating: On Host Data Path Light Sleep: Off Host Data Path Medium Grain Clock Gating: On Digital Right Management Medium Grain Clock Gating: Off Digital Right Management Light Sleep: Off Rom Medium Grain Clock Gating: On Data Fabric Medium Grain Clock Gating: Off GFX Clocks and Power: 1750 MHz (MCLK) 1212 MHz (SCLK) 214 MHz (PSTATE_SCLK) 300 MHz (PSTATE_MCLK) 1081 mV (VDDGFX) 18.65 W (average GPU) GPU Temperature: 39 C GPU Load: 0 % UVD: Disabled VCE: Disabled ProblemType: Bug DistroRelease: Ubuntu 18.10 Package: linux-image-4.18.0-9-generic 4.18.0-9.10 ProcVersionSignature: Ubuntu 4.18.0-9.10-generic 4.18.12 Uname: Linux 4.18.0-9-generic x86_64 ApportVersion: 2.20.10-0ubuntu11 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: shadowfax 3078 F pulseaudio /dev/snd/controlC0: shadowfax 3078 F pulseaudio CurrentDesktop: ubuntu:GNOME Date: Mon Oct 8 20:27:13 2018 InstallationDate: Installed on 2018-09-26 (11 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Beta amd64 (20180925.1) MachineType: System manufacturer System Product Name ProcFB: 0 amdgpudrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.18.0-9-generic root=UUID=a58662c7-39e2-4f05-9da6-d63173c94d53 ro quiet splash vt.handoff=1 RelatedPackageVersions: linux-restricted-modules-4.18.0-9-generic N/A linux-backports-modules-4.18.0-9-generic N/A linux-firmware1.175 SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/03/2018 dmi.bios.vendor: Ame
[Kernel-packages] [Bug 1797069] Re: linux-oem: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:31 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - kernel-stable-phase-changed:Wednesday, 10. October 2018 11:31 UTC - kernel-stable-phase:Packaging + phase: Packaging -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1797069 Title: linux-oem: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797069/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797065] Re: linux-kvm: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:32 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - kernel-stable-phase-changed:Wednesday, 10. October 2018 11:32 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1797065 Title: linux-kvm: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797065/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1788997] Re: rtl8723be wifi does not work under linux-modules-extra-4.15.0-33-generic
I have never seen kernel 4.15.0-36 ... was this ever released ? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1788997 Title: rtl8723be wifi does not work under linux-modules- extra-4.15.0-33-generic Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: When starting Xubuntu 18.04.1 LTS on a laptop HP 1S-af023ng with kernel 4.15.0-32.35 amd64, wifi via rtl8723be works OK. Using actual 4.15.0-33.36 amd64 instead, rtl8723be doesn't find any wifi networks and thus there is no connection. Changing the antenna setup in /etc/modprobe.d/rtl8723be_options.conf doesn't help either; as a workaround an external wifi device (Gigaset USB Adapter 108) works. The expectation is that wifi through rtl8723be will still work under 4.15.0-33.36 as it did previously. --- ProblemType: Bug ApportVersion: 2.20.9-0ubuntu7.2 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC1: al 1234 F pulseaudio /dev/snd/controlC0: al 1234 F pulseaudio CurrentDesktop: XFCE DistroRelease: Ubuntu 18.04 EcryptfsInUse: Yes InstallationDate: Installed on 2018-05-27 (89 days ago) InstallationMedia: Xubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) MachineType: Hewlett-Packard HP Notebook Package: linux (not installed) ProcFB: 0 radeondrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.15.0-33-generic root=UUID=32ea87b7-f595-4137-a54b-55838586f720 ro quiet splash vt.handoff=1 ProcVersionSignature: Ubuntu 4.15.0-33.36-generic 4.15.18 RelatedPackageVersions: linux-restricted-modules-4.15.0-33-generic N/A linux-backports-modules-4.15.0-33-generic N/A linux-firmware 1.173.1 Tags: bionic Uname: Linux 4.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo _MarkForUpload: True dmi.bios.date: 04/01/2015 dmi.bios.vendor: Insyde dmi.bios.version: F.02 dmi.board.asset.tag: Base Board Asset Tag dmi.board.name: 8137 dmi.board.vendor: Hewlett-Packard dmi.board.version: 99.02 dmi.chassis.asset.tag: Chassis Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: Hewlett-Packard dmi.chassis.version: Chassis Version dmi.modalias: dmi:bvnInsyde:bvrF.02:bd04/01/2015:svnHewlett-Packard:pnHPNotebook:pvrType1ProductConfigId:rvnHewlett-Packard:rn8137:rvr99.02:cvnHewlett-Packard:ct10:cvrChassisVersion: dmi.product.family: 103C_5335KV G=N L=CON B=HP dmi.product.name: HP Notebook dmi.product.version: Type1ProductConfigId dmi.sys.vendor: Hewlett-Packard To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1788997/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797074] Re: linux-azure: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:03 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - kernel-stable-phase-changed:Wednesday, 10. October 2018 11:03 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1797074 Title: linux-azure: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797074/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797062] Re: linux-gcp: -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: New => Confirmed ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:03 UTC + kernel-stable-phase:Packaging ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 - kernel-stable-phase-changed:Wednesday, 10. October 2018 11:03 UTC - kernel-stable-phase:Packaging + phase: Packaging -- 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/1797062 Title: linux-gcp: -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Confirmed Status in Kernel SRU Workflow prepare-package-meta series: New Status in Kernel SRU Workflow prepare-package-signed series: New Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1797061 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797062/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker
** Changed in: kernel-sru-workflow/prepare-package Status: In Progress => Fix Released ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) + kernel-stable-phase-changed:Wednesday, 10. October 2018 11:02 UTC + kernel-stable-phase:Uploaded ** Description changed: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) kernel-stable-phase-changed:Wednesday, 10. October 2018 11:02 UTC kernel-stable-phase:Uploaded + + -- swm properties -- + phase: Uploaded -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797061 Title: linux: 4.15.0-38.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) kernel-stable-phase-changed:Wednesday, 10. October 2018 11:02 UTC kernel-stable-phase:Uploaded -- swm properties -- phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1728244] Re: Touchpad stops working after reboot on Apollo Lake
Hi, Hans/Kai-Heng Feng I tried kernel from comment #187 on Chuwi Lapbook Air 14.1 with touchpad HID\ALPS0001. It doesn't work for me completely - neither trackpad nor buttons. Is there anyhow I can help troubleshoot this issue? BTW. Hans, thank you for your support and answers in my previous question. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1728244 Title: Touchpad stops working after reboot on Apollo Lake Status in Linux: Unknown Status in linux package in Ubuntu: Triaged Bug description: On the Jumper EZBook 3 Pro (V4) laptop, using an Apollo Lake N3450 processor, if you install Ubuntu 17.10 (or less) with isorespin and use rEFInd as bootloader (this is the only way to get linux booting on this laptop) everything works out of the box, but after a reboot or two the touchpad stops working. Both in Ubuntu and Windows 10. The only way to restore functionality is to boot from usb key ubuntu 17.10 respined, or disassemble laptop and detach-reattach battery cable. This is mesg | grep i2c_hid: [ 2056.460636] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) [ 3077.604699] i2c_hid i2c-SYNA3602:00: failed to reset device. [ 3077.605473] dpm_run_callback(): i2c_hid_resume+0x0/0xe0 [i2c_hid] returns -61 [ 3080.468156] i2c_hid i2c-SYNA3602:00: i2c_hid_get_input: incomplete report (27/34) uname -rvps Linux 4.10.0-32-generic #36~16.04.1-Ubuntu SMP Wed Aug 9 09:19:02 UTC 2017 x86_64 There has to be a bug in the kernel. Any way to avoid this? To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1728244/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797092] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window: apport-collect 1797092 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Tags added: xenial -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: Incomplete Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker
** Changed in: kernel-sru-workflow/snap-release-to-stable Status: New => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797061 Title: linux: 4.15.0-38.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: 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 upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796542] Re: Silent data corruption in Linux kernel 4.15
** Changed in: linux (Ubuntu Bionic)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796542
Title:
Silent data corruption in Linux kernel 4.15
Status in linux package in Ubuntu:
Fix Released
Status in linux source package in Bionic:
Fix Committed
Bug description:
== SRU Justification [BIONIC] ==
A silent data corruption was introduced in v4.10-rc1 with commit
72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects
users of O_DIRECT, in our case a KVM virtual machine with drives
which use qemu's "cache=none" option.
== Fix ==
Upstream commits:
0aa69fd32a5f766e997ca8ab4723c5a1146efa8b
block: add a lower-level bio_add_page interface
b403ea2404889e1227812fa9657667a1deb9c694
block: bio_iov_iter_get_pages: fix size of last iovec
9362dd1109f87a9d0a798fbc890cb339c171ed35
blkdev: __blkdev_direct_IO_simple: fix leak in error case
17d51b10d7773e4618bcac64648f30f12d4078fb
block: bio_iov_iter_get_pages: pin more pages for multi-segment IOs
The first 3 patches are required for a clean application of the final
patch that actually addresses the problem with a fix to this known
issue.
== Regression Potential ==
This touches the block layer, so there is risk potential in data
corruption. The fixes have several weeks in the upstream kernel and
so far, I see no subsequent fixes required.
== Test Case ==
Build the program listed below [1]
kudos to Jan Kara, and run with:
dd if=/dev/zero if=loop.img bs=1M count=2048
sudo losetup /dev/loop0 loop.img
./blkdev-dio-test /dev/loop0 0 &
./blkdev-dio-test /dev/loop0 2048 &
Without the fix, ones lost writes fairly soon. Without the fix, this
runs without any losy write messages.
blkdev-dio-test.c:
#define _GNU_SOURCE
#include
#include
#include
#include
#include
#include
#define PAGE_SIZE 4096
#define SECT_SIZE 512
#define BUF_OFF (2*SECT_SIZE)
int main(int argc, char **argv)
{
int fd = open(argv[1], O_RDWR | O_DIRECT);
int ret;
char *buf;
loff_t off;
struct iovec iov[2];
unsigned int seq;
if (fd < 0) {
perror("open");
return 1;
}
off = strtol(argv[2], NULL, 10);
buf = aligned_alloc(PAGE_SIZE, PAGE_SIZE);
iov[0].iov_base = buf;
iov[0].iov_len = SECT_SIZE;
iov[1].iov_base = buf + BUF_OFF;
iov[1].iov_len = SECT_SIZE;
seq = 0;
memset(buf, 0, PAGE_SIZE);
while (1) {
*(unsigned int *)buf = seq;
*(unsigned int *)(buf + BUF_OFF) = seq;
ret = pwritev(fd, iov, 2, off);
if (ret < 0) {
perror("pwritev");
return 1;
}
if (ret != 2*SECT_SIZE) {
fprintf(stderr, "Short pwritev: %d\n", ret);
return 1;
}
ret = pread(fd, buf, PAGE_SIZE, off);
if (ret < 0) {
perror("pread");
return 1;
}
if (ret != PAGE_SIZE) {
fprintf(stderr, "Short read: %d\n", ret);
return 1;
}
if (*(unsigned int *)buf != seq ||
*(unsigned int *)(buf + SECT_SIZE) != seq) {
printf("Lost write %u: %u %u\n", seq, *(unsigned int *)buf, *(unsigned int
*)(buf + SECT_SIZE));
return 1;
}
seq++;
}
return 0;
}
References:
[1] https://www.spinics.net/lists/linux-block/msg28507.html
TLDR: commit 72ecad22d9f198aafee64218512e02ffa7818671 (in v4.10)
introduced silent data corruption for O_DIRECT uses, it's fixed in
17d51b10d7773e4618bcac64648f30f12d4078fb (in v4.18)
A silent data corruption was introduced in v4.10-rc1 with commit
72ecad22d9f198aafee64218512e02ffa7818671 and was fixed in v4.18-rc7
with commit 17d51b10d7773e4618bcac64648f30f12d4078fb. It affects users
of O_DIRECT, in our case a KVM virtual machine with drives which use
qemu's "cache=none" option.
This is the commit which fixes the issue:
-
commit 17d51b10d7773e4618bcac64648f30f12d4078fb
Author: Martin Wilck
Date: Wed Jul 25 23:15:09 2018 +0200
block: bio_iov_iter_get_pages: pin more pages for multi-segment
IOs
bio_iov_iter_get_pages() currently only adds pages for the next non-zero
segment from the iov_iter to the bio. That's suboptimal for callers,
which typically try to pin as many pages as fit into the bio. This patch
converts the current bio_iov_iter_get_pages() into a static helper, and
introduces a new helper that allocates as many pages as
1) fit into the bio,
2) are present in the iov_iter,
3) and can be pinned by MM.
Error is returned only if zero pages could be pinned. Because of 3), a
zero return value doesn't necessarily mean all pages have been pinned.
Callers that have to pin every page in the iov_iter must still call this
function in a loop (this is currently the
[Kernel-packages] [Bug 1751994] Re: ppc64el: Support firmware disable of RFI flush
** Tags removed: targetmilestone-inin--- ** Tags added: targetmilestone-inin16045 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1751994 Title: ppc64el: Support firmware disable of RFI flush Status in The Ubuntu-power-systems project: Fix Released Status in linux package in Ubuntu: Fix Released Status in linux source package in Trusty: Fix Released Status in linux source package in Xenial: Fix Released Status in linux source package in Artful: Invalid Status in linux source package in Bionic: Fix Released Bug description: == Comment: #0 - Breno Leitao - 2018-02-26 13:59:55 == Hi Canonical, We still need some changes regarding spectre and meltdown. We need to backport the following commit to all supported kernel. I undertand that the backport for kernel 4.XX should be trivial. Not sure about kernel 3.13 yet. https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=582605a429e20ae68fd0b041b2e840af296edd08 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=eb0a2d2620ae431c543963c8c7f08f597366fc60 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1751994/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797061] Re: linux: 4.15.0-38.41 -proposed tracker
** Summary changed: - linux: -proposed tracker + linux: 4.15.0-38.41 -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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) ** 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) => Stefan Bader (smb) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797061 Title: linux: 4.15.0-38.41 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: 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: New Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: New Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1797074 (linux-azure), bug 1797076 (linux-hwe), bug 1797078 (linux-azure-edge), bug 1797080 (linux-gcp), bug 1797081 (linux-hwe-edge), bug 1797082 (linux-azure) derivatives: bug 1797062 (linux-gcp), bug 1797065 (linux-kvm), bug 1797066 (linux-aws), bug 1797067 (linux-azure), bug 1797069 (linux-oem), bug 1797073 (linux-raspi2) To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1797061/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1792195] Re: Signal 7 error when running GPFS tracing in cluster
** Changed in: ubuntu-power-systems Status: Incomplete => In Progress -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1792195 Title: Signal 7 error when running GPFS tracing in cluster Status in The Ubuntu-power-systems project: In Progress Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: In Progress Bug description: -- Problem Description -- GPFS mmfsd daemon is mapping shared tracing buffer(allocated from kernel driver using vmalloc) and then writing trace records from user space threads in parallel. While the SIGBUS happened, the access virtual memory address is in the mapped range, no overflow on access. Worked with Benjamin Herrenschmidt on GPFS tracing kernel driver code and he made a suggestion as workaround on the driver code to bypass the problem, and it works the workaround code change as below: - rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, PAGE_SHARED); + rc = remap_pfn_range(vma, start, pfn, PAGE_SIZE, __pgprot(pgprot_val(PAGE_SHARED)|_PAGE_DIRTY); As Benjamin mentioned, this is a Linux kernel bug and this is just a workaround. He will give the details about the kernel bug and why this workaround works The root cause is that for PTEs created by a driver at mmap time (ie, that aren't created dynamically at fault time), it's not legit for ptep_set_access_flags() to make them invalid even temporarily. A concurrent access while they are invalid will be unable to service the page fault and will cause as SIGBUS. Thankfully such PTEs shouldn't normally be the subject of a RO->RW privilege escalation. What happens is that the GPFS driver creates the PTEs using remap_pfn_range(...,PAGE_SHARED). PAGE_SHARED has _PAGE_ACCESSED (R) but not _PAGE_DIRTY (C) set. Thus on the first write, we try set C and while doing so, hit the above workaround, which causes the problem described earlier. The proposed patch will ensure we only do the Nest MMU hack when changing _PAGE_RW and not for normal R/C updates. The workaround tested by the GPFS team consists of adding _PAGE_DIRTY to the mapping created by remap_pfn_range() to avoid the RC update fault completely. This is fixed by these: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=bd0dbb73e01306a1060e56f81e5fe287be936477 https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=f08d08f3db55452d31ba4a37c702da6245876b96 Since DD1 support is still in (ie, 2bf1071a8d50928a4ae366bb3108833166c2b70c is not applied) the second doesn't apply cleanly. Did you want that attached? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-systems/+bug/1792195/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1797092] [NEW] xenial guest on arm64 drops to busybux under openstack bionic-rocky
Public bug reported: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ ** Affects: linux (Ubuntu) Importance: Undecided Status: New ** Tags: libvirt ** Attachment added: "xenial_console_log.txt" https://bugs.launchpad.net/bugs/1797092/+attachment/5199436/+files/xenial_console_log.txt -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1797092 Title: xenial guest on arm64 drops to busybux under openstack bionic-rocky Status in linux package in Ubuntu: New Bug description: on openstack rocky-bionic (with patch, see 1771662), xenial guests will fail to launch as they drop to the busybox prompt after booting. However, bionic guests will build and launch successfully. Dann F believes this may be related to the xenial image not containing appropriate acpi modifications. xenial guest console log: https://pastebin.canonical.com/p/ntRxFJTvjV/ xenial virshxml: https://pastebin.canonical.com/p/cCY4ZVynP7/ bionic virshxml for comparison: https://pastebin.canonical.com/p/MSV3xG7t7g/ validation: https://pastebin.canonical.com/p/nC9pfSkXVs/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1797092/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796944] Re: linux-aws: 4.18.0-1002.3 -proposed tracker
** Tags added: kernel-sru-derivative-of-1796346 -- 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/1796944 Title: linux-aws: 4.18.0-1002.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-aws package in Ubuntu: Confirmed Status in linux-aws source package in Cosmic: Confirmed Bug description: This bug is for tracking the 4.18.0-1002.3 upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- kernel-master-bug: 1796346 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796944/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795572] Re: linux-kvm: 4.15.0-1024.24 -proposed tracker
*** This bug is a duplicate of bug 1797065 *** https://bugs.launchpad.net/bugs/1797065 ** This bug has been marked a duplicate of bug 1797065 linux-kvm: -proposed tracker -- 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/1795572 Title: linux-kvm: 4.15.0-1024.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795572/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795574] Re: linux-azure: 4.15.0-1024.25~14.04.1 -proposed tracker
*** This bug is a duplicate of bug 1797074 *** https://bugs.launchpad.net/bugs/1797074 ** This bug has been marked a duplicate of bug 1797074 linux-azure: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1795574 Title: linux-azure: 4.15.0-1024.25~14.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 stakeholder-signoff series: New Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Packaging To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795574/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795575] Re: linux-azure: 4.15.0-1026.27~16.04.1 -proposed tracker
*** This bug is a duplicate of bug 1797082 *** https://bugs.launchpad.net/bugs/1797082 ** This bug has been marked a duplicate of bug 1797082 linux-azure: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1795575 Title: linux-azure: 4.15.0-1026.27~16.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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 upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795575/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795567] Re: linux-aws: 4.15.0-1024.24 -proposed tracker
*** This bug is a duplicate of bug 1797066 *** https://bugs.launchpad.net/bugs/1797066 ** This bug has been marked a duplicate of bug 1797066 linux-aws: -proposed tracker -- 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/1795567 Title: linux-aws: 4.15.0-1024.24 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795567/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795571] Re: linux-gcp: 4.15.0-1022.23 -proposed tracker
*** This bug is a duplicate of bug 1797062 *** https://bugs.launchpad.net/bugs/1797062 ** This bug has been marked a duplicate of bug 1797062 linux-gcp: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1795571 Title: linux-gcp: 4.15.0-1022.23 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795571/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795568] Re: linux-azure: 4.15.0-1026.27 -proposed tracker
*** This bug is a duplicate of bug 1797067 *** https://bugs.launchpad.net/bugs/1797067 ** This bug has been marked a duplicate of bug 1797067 linux-azure: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1795568 Title: linux-azure: 4.15.0-1026.27 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: New Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow 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 upload-to-ppa 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: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Uploaded To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795568/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795566] Re: linux-oem: 4.15.0-1022.25 -proposed tracker
*** This bug is a duplicate of bug 1797069 *** https://bugs.launchpad.net/bugs/1797069 ** This bug is no longer a duplicate of bug 1796641 linux-oem: 4.15.0-1023.26 -proposed tracker ** This bug has been marked a duplicate of bug 1797069 linux-oem: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1795566 Title: linux-oem: 4.15.0-1022.25 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795566/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795578] Re: linux-gcp: 4.15.0-1022.23~16.04.1 -proposed tracker
*** This bug is a duplicate of bug 1797080 *** https://bugs.launchpad.net/bugs/1797080 ** This bug has been marked a duplicate of bug 1797080 linux-gcp: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1795578 Title: linux-gcp: 4.15.0-1022.23~16.04.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 certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Xenial: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795578/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@Eric : Logs in attachment. Thanks a lot for your help. ** Attachment added: "apt and unattended-upgrades logs" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+attachment/5199435/+files/bug-1796376.tgz -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796376] Re: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode
@David, of course : - Start from an up-to-date Ubuntu Bionic : [root@uzimysut01 ~]# lsb_release -a No LSB modules are available. Distributor ID: Ubuntu Description:Ubuntu 18.04.1 LTS Release:18.04 Codename: bionic - Downgrade linux-cloud-tools-common to version 4.15.0-34.37 : [root@uzimysut01 ~]# apt install linux-cloud-tools-common=4.15.0-34.37 Reading package lists... Done Building dependency tree Reading state information... Done The following packages will be DOWNGRADED: linux-cloud-tools-common 0 upgraded, 0 newly installed, 1 downgraded, 0 to remove and 0 not upgraded. Need to get 58.3 kB of archives. After this operation, 7,168 B disk space will be freed. Do you want to continue? [Y/n] Get:1 https://repos.it.sncf.fr/ubuntu-security bionic-security/main amd64 linux-cloud-tools-common all 4.15.0-34.37 [58.3 kB] Fetched 58.3 kB in 0s (268 kB/s) dpkg: warning: downgrading linux-cloud-tools-common from 4.15.0-36.39 to 4.15.0-34.37 (Reading database ... 37537 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-34.37_all.deb ... Unpacking linux-cloud-tools-common (4.15.0-34.37) over (4.15.0-36.39) ... Setting up linux-cloud-tools-common (4.15.0-34.37) ... Processing triggers for ureadahead (0.100.0-20) ... Processing triggers for man-db (2.8.3-2) ... - Install unattended-upgrades : [root@uzimysut01 ~]# apt install unattended-upgrades - Ensure unattended-upgrades is active, and that it works in "shutdown mode" : [root@uzimysut01 ~]# grep Unattended-Upgrade /etc/apt/apt.conf.d/20auto-upgrades APT::Periodic::Unattended-Upgrade "1"; [root@uzimysut01 ~]# grep InstallOnShutdown /etc/apt/apt.conf.d/50unattended-upgrades Unattended-Upgrade::InstallOnShutdown "true"; - [optional] If you do not want to wait 30 minutes, modify the TimeoutStopSec : [root@uzimysut01 ~]# systemctl edit unattended-upgrades [Service] TimeoutStopSec=300 - Reboot : [root@uzimysut01 ~]# systemctl reboot - After reboot, dpkg is in a broken state : [root@uzimysut01 ~]# apt dist-upgrade E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem. - State of the linux-cloud-tools-common package : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 Thanks a lot for your help. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1796376 Title: Bug #1739107 fix causes linux-cloud-tools-common not to be upgradable with unattended-upgrades on shutdown mode Status in linux package in Ubuntu: Confirmed Bug description: Since the following linux-cloud-tools-common package versions : Xenial : 4.4.0-135.161 Bionic : 4.15.0-34.37 the Systemd service unit file for hv-kvp-daemon has been modified with new dependencies that make the package unable to be upgraded with unattended-upgrades on shutdown mode. Unattended-upgrades hangs with the linux-cloud-tools-common package during "Preparing to unpack". The server restarts after the unattended-upgrades service timeout expires. - Package state after reboot : iFR linux-cloud-tools-common 4.15.0-34.37 all Linux kernel version specific cloud tools for version 4.15.0 - Unattended-upgrades dpkg logs : Log started: 2018-10-05 17:59:04 (Reading database ... 52043 files and directories currently installed.) Preparing to unpack .../linux-cloud-tools-common_4.15.0-36.39_all.deb ... Log ended: 2018-10-05 18:00:54 - Impact : The current impact is very important as all security updates are blocked until you manually fix each server with : dpkg --configure -a apt install --only-upgrade linux-cloud-tools-common - Workaround/Fix : As a simple straightforward fix, replacing : Before=shutdown.target cloud-init-local.service walinuxagent.service with : Before=shutdown.target walinuxagent.service makes the package upgradable during shutdown. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1796376/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796641] Re: linux-oem: 4.15.0-1023.26 -proposed tracker
*** This bug is a duplicate of bug 1797069 *** https://bugs.launchpad.net/bugs/1797069 ** This bug has been marked a duplicate of bug 1797069 linux-oem: -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1796641 Title: linux-oem: 4.15.0-1023.26 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Confirmed Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow upload-to-ppa series: New Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. 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: 1795564 phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1796641/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1795564] Re: linux: 4.15.0-37.40 -proposed tracker
*** This bug is a duplicate of bug 1797061 *** https://bugs.launchpad.net/bugs/1797061 ** This bug has been marked a duplicate of bug 1797061 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/1795564 Title: linux: 4.15.0-37.40 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Incomplete Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow snap-release-to-beta series: Fix Released Status in Kernel SRU Workflow snap-release-to-candidate series: Confirmed Status in Kernel SRU Workflow snap-release-to-edge series: Fix Released Status in Kernel SRU Workflow snap-release-to-stable series: Invalid Status in Kernel SRU Workflow upload-to-ppa series: Invalid Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: Confirmed Bug description: This bug is for tracking the upload package. This bug will contain status and testing results related to that upload. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1795574 (linux-azure), bug 1795575 (linux-azure), bug 1795576 (linux-azure-edge), bug 1795578 (linux-gcp), bug 1795579 (linux-hwe), bug 1795581 (linux-hwe-edge) derivatives: bug 1795565 (linux-raspi2), bug 1795566 (linux-oem), bug 1795567 (linux-aws), bug 1795568 (linux-azure), bug 1795571 (linux-gcp), bug 1795572 (linux-kvm) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Promoted to proposed proposed-announcement-sent: true proposed-testing-requested: true To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1795564/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
