[Kernel-packages] [Bug 1828495] Re: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM.
The series was merged in 3a1acf5d47295d22ffdae0982a2fd808b802a7da as a prep to qemu 4.1. But the changes are rather invasive and after a review I think for the SRU we will not add them. For example the changes around: "model runnability guarantees won't apply to unversioned CPU models anymore" seems non backportable to me. I agree it is the right path going forward to keep the proliferation of CPU models under control and provide something like a "moving head" weakening the runability guarantees that can be regained by fetching the exact versions via alias-of. But none of the old systems management stacks will be able to do so. Yes there is [2] but I'm still scared in an SRU context to add that when it is a valid (more effort but working) option to add model+flags for the time being. And in addition the code for making the models versionable will be another great set of backports with potential backport flaws added. Hence at least for now my decision would be: - make the features available at least to the last LTS (Bionic) which will reach LTS-1 for many (to admit not all) users via Ubuntu cloud archive - do not backport the versioned CPU model changes (too much risk / incompatibilities) - pro: no changes to the higher virt stack needed - pro: less regression risk for the SRUs - pro: the new security features will be available - con: security features must be enabled individually via feature flags @Rafael that should match what you had prepared in your MPs already. I'll create a PPA with your any my changes for general regression tests. @Quaxlan - for the versioned CPUs an all that belongs to that context I'd ask you to file a new bug. I expect that will be in qemu 4.1 (just entered rc0) and a later (yet to be defined) libvirt version. Once all of that has properly landed we can consider if we will pull it back into Eoan (as long as it isn't released and under the SRU policy) OR if we wait for these new features to properly arrive in the next Ubuntu release being 20.04. Once you happen to know which libvirt version will have the appropriate changes to properly tolerate and exploit what was added to qemu via [1] (version and commits if you have both) let us know there. [1]: https://www.mail-archive.com/qemu-devel@nongnu.org/msg627282.html [2]: https://www.mail-archive.com/qemu-devel@nongnu.org/msg628326.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1828495 Title: [KVM][CLX] CPUID_7_0_EDX_ARCH_CAPABILITIES is not enabled in VM. Status in intel: New Status in linux package in Ubuntu: In Progress Status in qemu package in Ubuntu: In Progress Status in linux source package in Bionic: Confirmed Status in qemu source package in Bionic: In Progress Status in linux source package in Cosmic: Confirmed Status in qemu source package in Cosmic: In Progress Status in linux source package in Disco: Confirmed Status in qemu source package in Disco: In Progress Status in linux source package in Eoan: In Progress Status in qemu source package in Eoan: In Progress Bug description: [Impact] * QEMU does not support IceLake and CascadeLake CPUs specific features. * Most important feature to be supported is: IA32_ARCH_CAPABILITIES MSR. * With IA32_ARCH_CAPABILITIES, QEMU is able to advertise HW mitigations: - Rogue Data Cache Load - Enhanced IBRS - RSB Alternate - L1D flush need on VMENTRY - speculative Store Bypass to guests, as described in document: Intel 336996-Speculative-Execution-Side-Channel-Mitigations.pdf [Test Case] * From Original Description: """ 1. Boot up guest using: -cpu Cascadelake-Server [root@clx-2s2 yexin]# qemu-system-x86_64 -accel kvm -drive if=virtio,id=hd,file=/home/x/x,format=qcow2 -m 4096 -smp 4 -cpu Cascadelake-Server -serial stdio char device redirected to /dev/pts/3 (label serial0) qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] qemu-system-x86_64: warning: host doesn't support requested feature: CPUID.07H:ECX [bit 4] 2. To check CPU ID related to features[FEAT_7_0_EDX] ：CPUID_7_0_EDX_ARCH_CAPABILITIES Expected Result: Both host and guest's CPUID.07H EDX bit 29 should be 1. Actual Result: Host's cpuid: 0x0007 0x00: eax=0x ebx=0xd39b ecx=0x0818 edx=0xbc00 (EDX bit 29=1) Guest's cpuid : 0x0007 0x00: eax=0x ebx=0xd19f0fb9 ecx=0x0818 edx=0x8400 (EDX bit 29=0) Commit:2bdb76c015df7125783d8394d6339d181cb5bc30 Target Kerned: 5.1 Target Release: 19.10 """ [Regression Potential] * Most changes are related to CPU type definitions and its supported
[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834924 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1834954 phase: Holding before Promote to Proposed phase-changed: Wednesday, 10. July 2019 09:41 UTC - reason: - promote-to-proposed: Pending -- builds not complete in ppa main:failed variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834925 Title: linux-snapdragon: 4.15.0-1058.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834924 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1834954 phase: Holding before Promote to Proposed phase-changed: Wednesday, 10. July 2019 09:41 UTC variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834925] Re: linux-snapdragon: 4.15.0-1058.64 -proposed tracker
** Summary changed: - linux-snapdragon: 4.15.0-1058.63 -proposed tracker + linux-snapdragon: 4.15.0-1058.64 -proposed tracker -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834925 Title: linux-snapdragon: 4.15.0-1058.64 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: New Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: 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: Invalid Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834924 (dragonboard-kernel) -- swm properties -- kernel-stable-master-bug: 1834954 phase: Holding before Promote to Proposed phase-changed: Wednesday, 10. July 2019 09:41 UTC reason: promote-to-proposed: Pending -- builds not complete in ppa main:failed variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834925/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1808107] Re: fanotify11 in ubuntu_ltp_syscalls failed
** No longer affects: ubuntu-kernel-tests ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Xenial) Status: New => Invalid ** Also affects: ubuntu-kernel-tests 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/1808107 Title: fanotify11 in ubuntu_ltp_syscalls failed Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Trusty: New Status in linux source package in Xenial: Invalid Bug description: Timeouted on Trusty: startup='Tue Dec 11 11:58:36 2018' tst_test.c:1085: INFO: Timeout per run is 0h 05m 00s fanotify11.c:85: INFO: without FAN_REPORT_TID: tgid=5447, tid=5448, event.pid=5447 fanotify11.c:89: PASS: event.pid == tgid Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... tag=fanotify11 stime=1544529516 dur=350 exit=exited stat=1 core=no cu=0 cs=0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1808107/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836134] Re: 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node
** Description changed: - This test will take about 2 hours to run on node wright (ThunderX ARM64): + This test will take about 2 hours to run on node wright (ThunderX ARM64) with Xenial kernel. Test history: 4.4.0-155.182 - 1h45m 4.4.0-152.179 - 1h57m 4.4.0-150.176 - 2h00m 4.4.0-149.175 - 2h03m 4.4.0-147.173 - 1h55m 4.4.0-146.172 - 1h57m 4.4.0-145.171 - 1h59m - However it took about 25min to run on Moonshot ARM64 (node ms10-35-mcdivittB0-kernel), + However it took about 25min to run on a Moonshot ARM64 (ms10-35-mcdivittB0-kernel) with Xenial kernel. Test history: 4.4.0-155.182 - 23m 4.4.0-152.179 - 24m 4.4.0-150.176 - 23m 4.4.0-149.175 - 23m 4.4.0-147.173 - 23m 4.4.0-146.172 - 23m 4.4.0-145.171 - 24m Not sure why there is such a huge difference, but it might needs to be investigated. + This is node wright performance with this test against different kernels: + 5.0.0-21.22 - 1h20m + 4.18.0-26.27 - 1h18m + 5.0.0-21.22~18.04.1 - 1h17m + 4.15.0-55.60 - 1h23m + 4.15.0-55.60~16.04.2 - 1h23m + + And node ms10-35-mcdivittB0-kernel against different kernels: + 5.0.0-21.22 - 17m + 4.18.0-26.27 - 17m + 5.0.0-21.22~18.04.1 - 17m + 4.15.0-55.60 - 17m + 4.15.0-55.60~16.04.2 - 17m + + Step to run the test: - sudo apt-get install git python-minimal python-yaml gdb -y - git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests - git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest - rm -fr autotest/client/tests - ln -sf ~/autotest-client-tests autotest/client/tests - mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp - mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp - mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/ - AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control + sudo apt-get install git python-minimal python-yaml gdb -y + git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests + git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest + rm -fr autotest/client/tests + ln -sf ~/autotest-client-tests autotest/client/tests + mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp + mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp + mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/ + AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control + ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-154-generic 4.4.0-154.181 ProcVersionSignature: User Name 4.4.0-154.181-generic 4.4.179 Uname: Linux 4.4.0-154-generic aarch64 AlsaDevices: - total 0 - crw-rw 1 root audio 116, 1 Jul 10 08:25 seq - crw-rw 1 root audio 116, 33 Jul 10 08:25 timer + total 0 + crw-rw 1 root audio 116, 1 Jul 10 08:25 seq + crw-rw 1 root audio 116, 33 Jul 10 08:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CurrentDmesg: - + Date: Thu Jul 11 02:56:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: - + ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro RelatedPackageVersions: - linux-restricted-modules-4.4.0-154-generic N/A - linux-backports-modules-4.4.0-154-generic N/A - linux-firmware 1.157.21 + linux-restricted-modules-4.4.0-154-generic N/A + linux-backports-modules-4.4.0-154-generic N/A + linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 0 dmi.chassis.vendor: Cavium dmi.chassis.version: To be filled by O.E.M. dmi.modalias:
[Kernel-packages] [Bug 1836132] 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 1836132 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/1836132 Title: headphone-mic doesn't work on a couple of dell machines (alsa/realtek) Status in HWE Next: New Status in linux package in Ubuntu: Incomplete Bug description: We need to add support for a pure Mic device plugged into the audio jack. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836134] Re: 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node
** Tags added: sru-20190701 ubuntu-btrfs-kernel-fixes -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836134 Title: 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: This test will take about 2 hours to run on node wright (ThunderX ARM64): Test history: 4.4.0-155.182 - 1h45m 4.4.0-152.179 - 1h57m 4.4.0-150.176 - 2h00m 4.4.0-149.175 - 2h03m 4.4.0-147.173 - 1h55m 4.4.0-146.172 - 1h57m 4.4.0-145.171 - 1h59m However it took about 25min to run on Moonshot ARM64 (node ms10-35-mcdivittB0-kernel), Test history: 4.4.0-155.182 - 23m 4.4.0-152.179 - 24m 4.4.0-150.176 - 23m 4.4.0-149.175 - 23m 4.4.0-147.173 - 23m 4.4.0-146.172 - 23m 4.4.0-145.171 - 24m Not sure why there is such a huge difference, but it might needs to be investigated. Step to run the test: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-154-generic 4.4.0-154.181 ProcVersionSignature: User Name 4.4.0-154.181-generic 4.4.179 Uname: Linux 4.4.0-154-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 08:25 seq crw-rw 1 root audio 116, 33 Jul 10 08:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CurrentDmesg: Date: Thu Jul 11 02:56:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-154-generic N/A linux-backports-modules-4.4.0-154-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 0 dmi.chassis.vendor: Cavium dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.: dmi.product.name: ThunderX CRB dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Cavium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836134] [NEW] 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node
Public bug reported: This test will take about 2 hours to run on node wright (ThunderX ARM64): Test history: 4.4.0-155.182 - 1h45m 4.4.0-152.179 - 1h57m 4.4.0-150.176 - 2h00m 4.4.0-149.175 - 2h03m 4.4.0-147.173 - 1h55m 4.4.0-146.172 - 1h57m 4.4.0-145.171 - 1h59m However it took about 25min to run on Moonshot ARM64 (node ms10-35-mcdivittB0-kernel), Test history: 4.4.0-155.182 - 23m 4.4.0-152.179 - 24m 4.4.0-150.176 - 23m 4.4.0-149.175 - 23m 4.4.0-147.173 - 23m 4.4.0-146.172 - 23m 4.4.0-145.171 - 24m Not sure why there is such a huge difference, but it might needs to be investigated. Step to run the test: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-154-generic 4.4.0-154.181 ProcVersionSignature: User Name 4.4.0-154.181-generic 4.4.179 Uname: Linux 4.4.0-154-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 08:25 seq crw-rw 1 root audio 116, 33 Jul 10 08:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CurrentDmesg: Date: Thu Jul 11 02:56:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-154-generic N/A linux-backports-modules-4.4.0-154-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 0 dmi.chassis.vendor: Cavium dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.: dmi.product.name: ThunderX CRB dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Cavium ** Affects: ubuntu-kernel-tests Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: Undecided Status: Incomplete ** Affects: linux (Ubuntu Xenial) Importance: Undecided Status: Incomplete ** Tags: apport-bug arm64 sru-20190701 ubuntu-btrfs-kernel-fixes uec-images xenial ** Also affects: linux (Ubuntu Xenial) Importance: Undecided Status: New ** Also affects: ubuntu-kernel-tests 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/1836134 Title: 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: This test will take about 2 hours to run on node wright (ThunderX ARM64): Test history: 4.4.0-155.182 - 1h45m 4.4.0-152.179 - 1h57m 4.4.0-150.176 - 2h00m 4.4.0-149.175 - 2h03m 4.4.0-147.173 - 1h55m 4.4.0-146.172 - 1h57m 4.4.0-145.171 - 1h59m However it took about 25min to run on Moonshot ARM64 (node ms10-35-mcdivittB0-kernel), Test history: 4.4.0-155.182 - 23m 4.4.0-152.179 - 24m 4.4.0-150.176 - 23m 4.4.0-149.175 - 23m 4.4.0-147.173 - 23m 4.4.0-146.172 - 23m 4.4.0-145.171 - 24m Not sure why there is such a huge difference, but it might needs to be investigated. Step to run the test: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1
[Kernel-packages] [Bug 1836134] 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 1836134 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New => Incomplete ** Changed in: linux (Ubuntu Xenial) 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/1836134 Title: 361c093d test from ubuntu_btrfs_kernel_fixes will take about 2 hours to run on a ThunderX ARM64 node Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Incomplete Status in linux source package in Xenial: Incomplete Bug description: This test will take about 2 hours to run on node wright (ThunderX ARM64): Test history: 4.4.0-155.182 - 1h45m 4.4.0-152.179 - 1h57m 4.4.0-150.176 - 2h00m 4.4.0-149.175 - 2h03m 4.4.0-147.173 - 1h55m 4.4.0-146.172 - 1h57m 4.4.0-145.171 - 1h59m However it took about 25min to run on Moonshot ARM64 (node ms10-35-mcdivittB0-kernel), Test history: 4.4.0-155.182 - 23m 4.4.0-152.179 - 24m 4.4.0-150.176 - 23m 4.4.0-149.175 - 23m 4.4.0-147.173 - 23m 4.4.0-146.172 - 23m 4.4.0-145.171 - 24m Not sure why there is such a huge difference, but it might needs to be investigated. Step to run the test: sudo apt-get install git python-minimal python-yaml gdb -y git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest-client-tests git clone --depth=1 git://kernel.ubuntu.com/ubuntu/autotest rm -fr autotest/client/tests ln -sf ~/autotest-client-tests autotest/client/tests mkdir autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/* autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp mv autotest/client/tests/ubuntu_btrfs_kernel_fixes/tmp/361c093d7f99c3f6cbb07d5c580ce778ab418c42.sh autotest/client/tests/ubuntu_btrfs_kernel_fixes/fixes/ AUTOTEST_PATH=/home/ubuntu/autotest sudo -E autotest/client/autotest-local --verbose autotest/client/tests/ubuntu_btrfs_kernel_fixes/control ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: linux-image-4.4.0-154-generic 4.4.0-154.181 ProcVersionSignature: User Name 4.4.0-154.181-generic 4.4.179 Uname: Linux 4.4.0-154-generic aarch64 AlsaDevices: total 0 crw-rw 1 root audio 116, 1 Jul 10 08:25 seq crw-rw 1 root audio 116, 33 Jul 10 08:25 timer AplayDevices: Error: [Errno 2] No such file or directory: 'aplay' ApportVersion: 2.20.1-0ubuntu2.18 Architecture: arm64 ArecordDevices: Error: [Errno 2] No such file or directory: 'arecord' AudioDevicesInUse: Error: command ['fuser', '-v', '/dev/snd/seq', '/dev/snd/timer'] failed with exit code 1: CRDA: N/A CurrentDmesg: Date: Thu Jul 11 02:56:23 2019 IwConfig: Error: [Errno 2] No such file or directory: 'iwconfig' MachineType: Cavium ThunderX CRB PciMultimedia: ProcFB: 0 astdrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-154-generic root=UUID=d4e5f461-24ef-47d8-a67f-42c82ff1efe8 ro RelatedPackageVersions: linux-restricted-modules-4.4.0-154-generic N/A linux-backports-modules-4.4.0-154-generic N/A linux-firmware 1.157.21 RfKill: Error: [Errno 2] No such file or directory: 'rfkill' SourcePackage: linux UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 12/12/2012 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: 5.11 dmi.board.asset.tag: To be filled by O.E.M. dmi.board.name: To be filled by O.E.M. dmi.board.vendor: To be filled by O.E.M. dmi.board.version: To be filled by O.E.M. dmi.chassis.asset.tag: To be filled by O.E.M. dmi.chassis.type: 0 dmi.chassis.vendor: Cavium dmi.chassis.version: To be filled by O.E.M. dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.11:bd12/12/2012:svnCavium:pnThunderXCRB:pvrTobefilledbyO.E.M.:rvnTobefilledbyO.E.M.:rnTobefilledbyO.E.M.:rvrTobefilledbyO.E.M.:cvnCavium:ct0:cvrTobefilledbyO.E.M.: dmi.product.name: ThunderX CRB dmi.product.version: To be filled by O.E.M. dmi.sys.vendor: Cavium To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-kernel-tests/+bug/1836134/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836132] [NEW] headphone-mic doesn't work on a couple of dell machines (alsa/realtek)
Public bug reported: We need to add support for a pure Mic device plugged into the audio jack. ** Affects: hwe-next Importance: Undecided Status: New ** Affects: linux (Ubuntu) Importance: High Assignee: Hui Wang (hui.wang) Status: New ** Tags: originate-from-1835862 somerville ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: originate-from-1835862 somerville -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836132 Title: headphone-mic doesn't work on a couple of dell machines (alsa/realtek) Status in HWE Next: New Status in linux package in Ubuntu: New Bug description: We need to add support for a pure Mic device plugged into the audio jack. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1836132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834918] Re: linux: 4.4.0-155.182 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834917 (trusty/linux-lts-xenial) derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 1834915 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress - regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834918 Title: linux: 4.4.0-155.182 -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: Fix Released Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834917 (trusty/linux-lts-xenial) derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 1834915 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832048] Re: hinic: fix oops due to race in set_rx_mode
Verification: I ran 100 iterations 'modprobe -r hinic; modprobe hinic' on each kernel without a issue. ** Tags removed: verification-needed-bionic verification-needed-cosmic verification-needed-disco ** Tags added: verification-done-bionic verification-done-cosmic verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1832048 Title: hinic: fix oops due to race in set_rx_mode Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] It is possible for the hinic driver to oops after the module is removed and reinserted. [Test Case] while :; do sudo modprobe -r hinic; modprobe hinic; done [Fix] From linux-next: 66350023d5756 hinic: fix a bug in set rx mode [Regression Risk] Patch is local to the hinic driver. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832048/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
** Also affects: linux-firmware (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Disco) Importance: Undecided Status: New ** Also affects: linux-firmware (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: linux-oem-osp1 (Ubuntu Cosmic) Importance: Undecided Status: New ** Changed in: linux-oem-osp1 (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: linux-oem-osp1 (Ubuntu Disco) Status: New => Won't Fix -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux-firmware source package in Cosmic: New Status in linux-oem-osp1 source package in Cosmic: Won't Fix Status in linux-firmware source package in Disco: New Status in linux-oem-osp1 source package in Disco: Won't Fix Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835879] Re: Intel Wireless-AC 9462/9560 not supported on ICL
** Also affects: linux-firmware (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835879 Title: Intel Wireless-AC 9462/9560 not supported on ICL Status in HWE Next: New Status in linux-firmware package in Ubuntu: New Status in linux-oem-osp1 package in Ubuntu: In Progress Status in linux-firmware source package in Bionic: New Status in linux-oem-osp1 source package in Bionic: In Progress Status in linux-firmware source package in Cosmic: New Status in linux-oem-osp1 source package in Cosmic: New Status in linux-firmware source package in Disco: New Status in linux-oem-osp1 source package in Disco: New Bug description: [Impact] Intel Wireless-AC 9560/9462 is not correctly enabled on IceLake platforms. [Fix] Two changes from Intel maintained backport-iwlwifi repository are necessary to add device ID/configs to iwlwifi driver. [Test] Verified on hardware 9462/9560 on IceLake/CometLake platforms. [Regression Potential] Low. These changes are part of the series to enable 9462/9560 on CometLake/IceLake platforms that don't have the support originally. = Original Bug Description = Intel Wireless-AC 9462/9560 on CML was previously enabled via bug 1833065, bug 1834415 and bug 1834464. However on ICL, it fails to startup with following error messages with kernel v5.2-rc7: iwlwifi :00:14.3: loaded firmware version 48.13675109.0 op_mode iwlmvm iwlwifi :00:14.3: Detected Intel(R) Wireless-AC 9560, REV=0x338 iwlwifi :00:14.3: Loaded firmware version: 48.13675109.0 iwlwifi :00:14.3: SecBoot CPU1 Status: 0x5c97, CPU2 Status: 0x3 iwlwifi :00:14.3: Failed to start RT ucode: -5 iwlwifi :00:14.3: Collecting data: trigger 16 fired. iwlwifi :00:14.3: Firmware not running - cannot dump error iwlwifi :00:14.3: Failed to run INIT ucode: -5 Also tried backport-iwlwifi out-of-tree driver revision 7858 (HEAD at the moment) with no luck. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835879/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834918] Re: linux: 4.4.0-155.182 -proposed tracker
4.4.0-155.182 - generic Regression test CMPL, RTB. 55 / 56 tests were run, missing: xfstests Issue to note in amd64: ubuntu_kvm_unit_tests - apic timeouted (bug 1748103) debug (bug 1821906) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 (bug 1819116) 51 / 52 tests were run, missing: xfstests Issue to note in arm64: hwclock - issue for HP m400 (bug 1716603) ubuntu_kernel_selftests - cpu-hotplug failed on moonshot (bug 1809701) ubuntu_kvm_smoke_test - unable to create KVM with uvtool (bug 1749427) ubuntu_kvm_unit_tests - gicv2-mmio on X-ARM64 (bug 1828165) pmu on ms10-34-mcdivittB0-kernel (bug 1751000) gicv2 related test failed on ThunderX (bug 1828153) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 (bug 1819116) Issue to note in i386: ubuntu_kvm_smoke_test - timed out waiting for dnsmasq lease (bug 1802056) ubuntu_kvm_unit_tests - unable to build on X/T i386 (bug 1798007) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 (bug 1819116) xfstests - xfs generic/308 timed out (bug 1738152) 51 / 52 tests were run, missing: ubuntu_boot Issue to note in ppc64le (P8): ubuntu_btrfs_kernel_fixes - Unable to mount a btrfs filesystem smaller than 320M on Xenial P8 (bug 1813863) ubuntu_ltp_syscalls - fallocate05, fsetxattr01, fgetxattr01, fsync01, preadv03, preadv03_64, pwritev03, pwritev03_64, setxattr01 (bug 1785198) inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) xfstests - btrfs generic/176 timed out Issue to note in s390x (KVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - test should be skipped for X s390x KVM ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 (bug 1819116) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) 50 / 51 tests were run, missing: ubuntu_boot Issue to note in s390x (Ubuntu on LPAR): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 (bug 1819116) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) 50 / 51 tests were run, missing: ubuntu_boot Issue to note in s390x (zVM): libhugetlbfs - failed 11 killed by signal 7 bad config 1 ubuntu_bpf_jit - 4 failures reported for X s390x (bug 1768452) ubuntu_kernel_selftests - test_bpf in net (bug 1768452) ubuntu_kvm_smoke_test - uvtool issue (bug 1729854) ubuntu_kvm_unit_tests - skey failed on zVM (bug 1778705) ubuntu_ltp_syscalls - inotify07 (bug 1774387) inotify08 (bug 1775784) fanotify06 (bug 1833028) fanotify07 causing timeout on fanotify08, fanotify09, fanotify10, fanotify11, fanotify12, fanotify13, fanotify14, fanotify15 (bug 1775165) fanotify09-2 (bug 1804594) fanotify10 (bug 1802454) sync_file_range02 (bug 1819116) ubuntu_qrt_kernel_security - SECURITY_SELINUX_DISABLE option should be enable on X s390x (bug 1813721) ** Changed in: kernel-sru-workflow/regression-testing Status: Confirmed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Assignee: Canonical Kernel Team (canonical-kernel-team) => Po-Hsu Lin
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
Assigned to Seth per comment #16. ** Changed in: linux (Ubuntu) Assignee: (unassigned) => Seth Forshee (sforshee) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Confirmed Status in xtables-addons package in Ubuntu: New Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834935] Re: linux-gcp: 4.15.0-1037.39~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834932 (gcp-kernel), bug 1834934 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834936 - phase: Signoff - phase-changed: Friday, 05. July 2019 13:13 UTC + phase: Ready for Testing + phase-changed: Thursday, 11. July 2019 00:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834935 Title: linux-gcp: 4.15.0-1037.39~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: Fix Released 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834932 (gcp-kernel), bug 1834934 (gke-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834936 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:15 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834935/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834930] Re: linux-aws: 4.15.0-1044.46 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Signoff - phase-changed: Friday, 05. July 2019 20:09 UTC + phase: Ready for Testing + phase-changed: Thursday, 11. July 2019 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834930 Title: linux-aws: 4.15.0-1044.46 -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: Fix Released 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834929 (xenial/linux-aws-hwe) derivatives: bug 1834927 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:11 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834930/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834936] Re: linux-gcp: 4.15.0-1037.39 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834935 (xenial/linux-gcp) derivatives: bug 1834931 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 03. July 2019 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834936 Title: linux-gcp: 4.15.0-1037.39 -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: Fix Released 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834935 (xenial/linux-gcp) derivatives: bug 1834931 (gcp-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 03. July 2019 22:37 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834936/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834926] Re: linux-oem: 4.15.0-1046.51 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 10. July 2019 15:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1834926 Title: linux-oem: 4.15.0-1046.51 -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: Fix Released 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 10. July 2019 15:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834940] Re: linux-kvm: 4.15.0-1039.39 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Signoff - phase-changed: Thursday, 04. July 2019 08:08 UTC + phase: Ready for Testing + phase-changed: Thursday, 11. July 2019 00:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1834940 Title: linux-kvm: 4.15.0-1039.39 -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: Fix Released 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834940/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834941] Re: linux-ibm-gt: 4.15.0-1027.29 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Signoff - phase-changed: Tuesday, 09. July 2019 23:12 UTC + phase: Ready for Testing + phase-changed: Thursday, 11. July 2019 00:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834941 Title: linux-ibm-gt: 4.15.0-1027.29 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: Invalid Status in Kernel SRU Workflow promote-to-updates series: Invalid Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released 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 will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:12 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834941/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834923] Re: linux-raspi2: 4.15.0-1041.44 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834922 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Signoff - phase-changed: Wednesday, 10. July 2019 10:10 UTC + phase: Ready for Testing + phase-changed: Thursday, 11. July 2019 00:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1834923 Title: linux-raspi2: 4.15.0-1041.44 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834922 (pi-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Thursday, 11. July 2019 00:10 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834923/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
The newer kernel went about 16 runs and then popped this:
[ 2137.810559] md: md0: resync done.
[ 2296.795633] INFO: task python3:11639 blocked for more than 120 seconds.
[ 2296.800320] Tainted: P O 4.15.0-55-generic
#60+lp1796292+1
[ 2296.805097] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
[ 2296.810071] python3 D0 11639 8301 0x
[ 2296.810075] Call Trace:
[ 2296.810100] __schedule+0x291/0x8a0
[ 2296.810102] ? __switch_to_asm+0x34/0x70
[ 2296.810103] ? __switch_to_asm+0x40/0x70
[ 2296.810105] schedule+0x2c/0x80
[ 2296.810118] bch_bucket_alloc+0xe5/0x370 [bcache]
[ 2296.810128] ? wait_woken+0x80/0x80
[ 2296.810132] __bch_bucket_alloc_set+0x10d/0x160 [bcache]
[ 2296.810137] bch_bucket_alloc_set+0x4e/0x70 [bcache]
[ 2296.810143] __uuid_write+0x59/0x170 [bcache]
[ 2296.810148] ? __write_super+0x137/0x170 [bcache]
[ 2296.810153] bch_uuid_write+0x16/0x40 [bcache]
[ 2296.810159] __cached_dev_store+0x1e5/0x8b0 [bcache]
[ 2296.810160] ? __switch_to_asm+0x34/0x70
[ 2296.810161] ? __switch_to_asm+0x40/0x70
[ 2296.810163] ? __switch_to_asm+0x34/0x70
[ 2296.810167] bch_cached_dev_store+0x46/0x110 [bcache]
[ 2296.810181] sysfs_kf_write+0x3c/0x50
[ 2296.810182] kernfs_fop_write+0x125/0x1a0
[ 2296.810185] __vfs_write+0x1b/0x40
[ 2296.810187] vfs_write+0xb1/0x1a0
[ 2296.810189] SyS_write+0x55/0xc0
[ 2296.810193] do_syscall_64+0x73/0x130
[ 2296.810194] entry_SYSCALL_64_after_hwframe+0x3d/0xa2
[ 2296.810196] RIP: 0033:0x7f8e80077154
[ 2296.810197] RSP: 002b:7fffc23855e8 EFLAGS: 0246 ORIG_RAX:
0001
[ 2296.810199] RAX: ffda RBX: 0008 RCX: 7f8e80077154
[ 2296.810200] RDX: 0008 RSI: 00d734b0 RDI: 0003
[ 2296.810201] RBP: 7f8e805726c0 R08: R09:
[ 2296.810202] R10: 0100 R11: 0246 R12: 0003
[ 2296.810203] R13: R14: 00d734b0 R15: 00aa4db0
[ 2417.627259] INFO: task python3:11639 blocked for more than 120 seconds.
[ 2417.632687] Tainted: P O 4.15.0-55-generic
#60+lp1796292+1
[ 2417.638276] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this
message.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834918] Re: linux: 4.4.0-155.182 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834917 (trusty/linux-lts-xenial) derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 1834915 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834918 Title: linux: 4.4.0-155.182 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834917 (trusty/linux-lts-xenial) derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 1834915 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe) derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 (linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 1834943 (linux-oracle), bug 1834944 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 13:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834954 Title: linux: 4.15.0-55.60 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe) derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 (linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 1834943 (linux-oracle), bug 1834944 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 13:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 - phase: Signoff - phase-changed: Wednesday, 10. July 2019 16:46 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834908] Re: linux-aws: 4.4.0-1088.99 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834907 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 - phase: Signoff - phase-changed: Friday, 05. July 2019 11:36 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834908 Title: linux-aws: 4.4.0-1088.99 -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: Fix Released 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: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834907 (aws-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834908/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834911] Re: linux-raspi2: 4.4.0-1115.124 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834910 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 - phase: Signoff - phase-changed: Friday, 05. July 2019 00:36 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1834911 Title: linux-raspi2: 4.4.0-1115.124 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834910 (pi2-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834911/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834913] Re: linux-snapdragon: 4.4.0-1119.125 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834912 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 - phase: Signoff - phase-changed: Friday, 05. July 2019 00:36 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834913 Title: linux-snapdragon: 4.4.0-1119.125 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834912 (dragonboard-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:39 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834913/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834909] Re: linux-kvm: 4.4.0-1052.59 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 - phase: Signoff - phase-changed: Friday, 05. July 2019 00:36 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1834909 Title: linux-kvm: 4.4.0-1052.59 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834918 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:38 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834942] Re: linux-oracle: 4.15.0-1018.20~16.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834943 - phase: Signoff - phase-changed: Thursday, 04. July 2019 19:42 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834942 Title: linux-oracle: 4.15.0-1018.20~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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834943 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:45 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835434] Re: linux-azure: 5.0.0-1012.12 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835882 (bionic/linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1834902 - phase: Signoff - phase-changed: Wednesday, 10. July 2019 09:37 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835434 Title: linux-azure: 5.0.0-1012.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Disco: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835882 (bionic/linux-azure-edge) -- swm properties -- kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:36 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835434/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834954] Re: linux: 4.15.0-55.60 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834954 Title: linux: 4.15.0-55.60 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834950 (xenial/linux-azure), bug 1834953 (xenial/linux-hwe) derivatives: bug 1834919 (pc-kernel), bug 1834921 (pc-lowlatency-kernel), bug 1834923 (linux-raspi2), bug 1834925 (linux-snapdragon), bug 1834926 (linux-oem), bug 1834930 (linux-aws), bug 1834936 (linux-gcp), bug 1834939 (linux-gke-4.15), bug 1834940 (linux-kvm), bug 1834941 (linux-ibm-gt), bug 1834943 (linux-oracle), bug 1834944 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 13:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834954/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834943] Re: linux-oracle: 4.15.0-1018.20 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Signoff - phase-changed: Wednesday, 10. July 2019 11:41 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oracle in Ubuntu. https://bugs.launchpad.net/bugs/1834943 Title: linux-oracle: 4.15.0-1018.20 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-oracle package in Ubuntu: Invalid Status in linux-oracle source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834942 (xenial/linux-oracle) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834943/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834950] Re: linux-azure: 4.15.0-1051.56 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834948 (trusty/linux-azure) derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Signoff - phase-changed: Wednesday, 10. July 2019 20:43 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834950 Title: linux-azure: 4.15.0-1051.56 -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: Fix Released Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834948 (trusty/linux-azure) derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:42 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834894] Re: linux-snapdragon: 5.0.0-1017.18 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Signoff - phase-changed: Wednesday, 10. July 2019 10:06 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834894 Title: linux-snapdragon: 5.0.0-1017.18 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834892] Re: linux-kvm: 5.0.0-1011.12 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Signoff - phase-changed: Thursday, 04. July 2019 12:34 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1834892 Title: linux-kvm: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:35 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834918] Re: linux: 4.4.0-155.182 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834918 Title: linux: 4.4.0-155.182 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834917 (trusty/linux-lts-xenial) derivatives: bug 1834906 (pc-kernel), bug 1834908 (linux-aws), bug 1834909 (linux-kvm), bug 1834911 (linux-raspi2), bug 1834913 (linux-snapdragon), bug 1834915 (linux-fips) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 11:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834918/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836117] Re: Bionic update: upstream stable patchset 2019-07-10
** Description changed: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-10 -Ported from the following upstream stable releases: -v4.14.71, v4.18.9, -v4.14.72, v4.18.10 + Ported from the following upstream stable releases: + v4.14.71, v4.18.9, + v4.14.72, v4.18.10 from git://git.kernel.org/ + + i2c: xiic: Make the start and the byte count write atomic + i2c: i801: fix DNV's SMBCTRL register offset + scsi: lpfc: Correct MDS diag and nvmet configuration + nbd: don't allow invalid blocksize settings + block: bfq: swap puts in bfqg_and_blkg_put + android: binder: fix the race mmap and alloc_new_buf_locked + MIPS: VDSO: Match data page cache colouring when D$ aliases + SMB3: Backup intent flag missing for directory opens with backupuid mounts + smb3: check for and properly advertise directory lease support + Btrfs: fix data corruption when deduplicating between different files + KVM: s390: vsie: copy wrapping keys to right place + KVM: VMX: Do not allow reexecute_instruction() when skipping MMIO instr + ALSA: hda - Fix cancel_work_sync() stall from jackpoll work + cpu/hotplug: Adjust misplaced smb() in cpuhp_thread_fun() + cpu/hotplug: Prevent state corruption on error rollback + x86/microcode: Make sure boot_cpu_data.microcode is up-to-date + x86/microcode: Update the new microcode revision unconditionally + crypto: aes-generic - fix aes-generic regression on powerpc + tpm: separate cmd_ready/go_idle from runtime_pm + ARC: [plat-axs*]: Enable SWAP + misc: mic: SCIF Fix scif_get_new_port() error handling + ethtool: Remove trailing semicolon for static inline + i2c: aspeed: Add an explicit type casting for *get_clk_reg_val + Bluetooth: h5: Fix missing dependency on BT_HCIUART_SERDEV + gpio: tegra: Move driver registration to subsys_init level + selftests/bpf: fix a typo in map in map test + media: davinci: vpif_display: Mix memory leak on probe error path + media: dw2102: Fix memleak on sequence of probes + net: phy: Fix the register offsets in Broadcom iProc mdio mux driver + blk-mq: fix updating tags depth + scsi: target: fix __transport_register_session locking + md/raid5: fix data corruption of replacements after originals dropped + timers: Clear timer_base::must_forward_clk with timer_base::lock held + media: camss: csid: Configure data type and decode format properly + gpu: ipu-v3: default to id 0 on missing OF alias + misc: ti-st: Fix memory leak in the error path of probe() + uio: potential double frees if __uio_register_device() fails + firmware: vpd: Fix section enabled flag on vpd_section_destroy + Drivers: hv: vmbus: Cleanup synic memory free path + tty: rocket: Fix possible buffer overwrite on register_PCI + f2fs: fix to active page in lru list for read path + f2fs: do not set free of current section + f2fs: fix defined but not used build warnings + perf tools: Allow overriding MAX_NR_CPUS at compile time + NFSv4.0 fix client reference leak in callback + perf c2c report: Fix crash for empty browser + perf evlist: Fix error out while applying initial delay and LBR + macintosh/via-pmu: Add missing mmio accessors + ath9k: report tx status on EOSP + ath9k_hw: fix channel maximum power level test + ath10k: prevent active scans on potential unusable channels + wlcore: Set rx_status boottime_ns field on rx + MIPS: Fix ISA virt/bus conversion for non-zero PHYS_OFFSET + scsi: 3ware: fix return 0 on the error path of probe + tools/testing/nvdimm: kaddr and pfn can be NULL to ->direct_access() + ath10k: disable bundle mgmt tx completion event support + Bluetooth: hidp: Fix handling of strncpy for hid->name information + pinctrl: imx: off by one in imx_pinconf_group_dbg_show() + gpio: ml-ioh: Fix buffer underwrite on probe error path + pinctrl/amd: only handle irq if it is pending and unmasked + net: mvneta: fix mtu change on port without link + f2fs: try grabbing node page lock aggressively in sync scenario + f2fs: fix to skip GC if type in SSA and SIT is inconsistent + tpm_tis_spi: Pass the SPI IRQ down to the driver + tpm/tpm_i2c_infineon: switch to i2c_lock_bus(..., I2C_LOCK_SEGMENT) + f2fs: fix to do sanity check with reserved blkaddr of inline inode + MIPS: Octeon: add missing of_node_put() + MIPS: generic: fix missing of_node_put() + net: dcb: For wild-card lookups, use priority -1, not 0 + dm cache: only allow a single io_mode cache feature to be requested + Input: atmel_mxt_ts - only use first T9 instance + media: s5p-mfc: Fix buffer look up in
[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834900 (bionic/linux-oem-osp1), bug 1835388 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834902 Title: linux: 5.0.0-21.22 -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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834900 (bionic/linux-oem-osp1), bug 1835388 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834892] Re: linux-kvm: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-kvm in Ubuntu. https://bugs.launchpad.net/bugs/1834892 Title: linux-kvm: 5.0.0-1011.12 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-kvm package in Ubuntu: Invalid Status in linux-kvm source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Signoff phase-changed: Thursday, 04. July 2019 12:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834892/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834894] Re: linux-snapdragon: 5.0.0-1017.18 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-snapdragon in Ubuntu. https://bugs.launchpad.net/bugs/1834894 Title: linux-snapdragon: 5.0.0-1017.18 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-snapdragon package in Ubuntu: Invalid Status in linux-snapdragon source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Signoff phase-changed: Wednesday, 10. July 2019 10:06 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834894/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834902] Re: linux: 5.0.0-21.22 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1834902 Title: linux: 5.0.0-21.22 -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-lrm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834900 (bionic/linux-oem-osp1), bug 1835388 (bionic/linux-hwe) derivatives: bug 1834884 (linux-raspi2), bug 1834886 (linux-aws), bug 1834891 (linux-gcp), bug 1834892 (linux-kvm), bug 1834894 (linux-snapdragon), bug 1835434 (linux-azure) -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Testing phase-changed: Wednesday, 03. July 2019 11:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
This bug was fixed in the package nvidia-graphics-drivers-430 - 430.34-0ubuntu2 --- nvidia-graphics-drivers-430 (430.34-0ubuntu2) eoan; urgency=medium * debian/dkms_nvidia/patches/disable_fstack-clash-protection_fcf-protection.patch: - Refresh for 430.34 (LP: #1830961). -- Alberto Milone Wed, 10 Jul 2019 15:27:36 +0200 ** Changed in: nvidia-graphics-drivers-430 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Released Status in virtualbox package in Ubuntu: Confirmed Status in xtables-addons package in Ubuntu: New Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836117] Re: Bionic update: upstream stable patchset 2019-07-10
** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Kamal Mostafa (kamalmostafa) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836117 Title: Bionic update: upstream stable patchset 2019-07-10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-10 Ported from the following upstream stable releases: v4.14.71, v4.18.9, v4.14.72, v4.18.10 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834891] Re: linux-gcp: 5.0.0-1011.11 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Signoff - phase-changed: Wednesday, 10. July 2019 09:35 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834891 Title: linux-gcp: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834884] Re: linux-raspi2: 5.0.0-1013.13 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 - phase: Signoff - phase-changed: Thursday, 04. July 2019 13:33 UTC + phase: Ready for Testing + phase-changed: Wednesday, 10. July 2019 23:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress - security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1834884 Title: linux-raspi2: 5.0.0-1013.13 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:04 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834891] Re: linux-gcp: 5.0.0-1011.11 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-gcp in Ubuntu. https://bugs.launchpad.net/bugs/1834891 Title: linux-gcp: 5.0.0-1011.11 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Fix Released Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-gcp package in Ubuntu: Invalid Status in linux-gcp source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835904 (bionic/linux-gcp-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 23:05 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834891/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836117] [NEW] Bionic update: upstream stable patchset 2019-07-10
Public bug reported: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-10 Ported from the following upstream stable releases: v4.14.71, v4.18.9, v4.14.72, v4.18.10 from git://git.kernel.org/ ** Affects: linux (Ubuntu) Importance: Undecided Status: Confirmed ** Affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Tags: kernel-stable-tracking-bug ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Tags added: kernel-stable-tracking-bug ** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Description changed: + SRU Justification - SRU Justification + Impact: + The upstream process for stable tree updates is quite similar + in scope to the Ubuntu SRU process, e.g., each patch has to + demonstrably fix a bug, and each patch is vetted by upstream + by originating either directly from a mainline/stable Linux tree or + a minimally backported form of that patch. The following upstream + stable patches should be included in the Ubuntu kernel: - Impact: -The upstream process for stable tree updates is quite similar -in scope to the Ubuntu SRU process, e.g., each patch has to -demonstrably fix a bug, and each patch is vetted by upstream -by originating either directly from a mainline/stable Linux tree or -a minimally backported form of that patch. The following upstream -stable patches should be included in the Ubuntu kernel: + upstream stable patchset 2019-07-10 -upstream stable patchset 2019-07-10 -from git://git.kernel.org/ +Ported from the following upstream stable releases: +v4.14.71, v4.18.9, +v4.14.72, v4.18.10 + + from git://git.kernel.org/ -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836117 Title: Bionic update: upstream stable patchset 2019-07-10 Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: New Bug description: SRU Justification Impact: The upstream process for stable tree updates is quite similar in scope to the Ubuntu SRU process, e.g., each patch has to demonstrably fix a bug, and each patch is vetted by upstream by originating either directly from a mainline/stable Linux tree or a minimally backported form of that patch. The following upstream stable patches should be included in the Ubuntu kernel: upstream stable patchset 2019-07-10 Ported from the following upstream stable releases: v4.14.71, v4.18.9, v4.14.72, v4.18.10 from git://git.kernel.org/ To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836117/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834886] Re: linux-aws: 5.0.0-1011.12 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-aws in Ubuntu. https://bugs.launchpad.net/bugs/1834886 Title: linux-aws: 5.0.0-1011.12 -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: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-aws package in Ubuntu: Invalid Status in linux-aws source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1835782 (bionic/linux-aws-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Testing phase-changed: Wednesday, 03. July 2019 12:01 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834886/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834884] Re: linux-raspi2: 5.0.0-1013.13 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-raspi2 in Ubuntu. https://bugs.launchpad.net/bugs/1834884 Title: linux-raspi2: 5.0.0-1013.13 -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: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Invalid Status in Kernel SRU Workflow security-signoff series: Fix Released Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-raspi2 package in Ubuntu: Invalid Status in linux-raspi2 source package in Disco: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834902 phase: Signoff phase-changed: Thursday, 04. July 2019 13:33 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: certification-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834884/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1796292] Re: Tight timeout for bcache removal causes spurious failures
Andrea, thanks for the updated kernels.
On the first one, I got 23 installs before I ran into an issue; I'll
test the newer kernel next.
https://paste.ubuntu.com/p/2B4Kk3wbvQ/
[ 5436.870482] BUG: unable to handle kernel NULL pointer dereference at
09b8
[ 5436.873374] IP: cache_set_flush+0xf6/0x190 [bcache]
[ 5436.875208] PGD 0 P4D 0
[ 5436.876488] Oops: [#1] SMP PTI
[ 5436.877842] Modules linked in: zfs(PO) zunicode(PO) zavl(PO) icp(PO)
zcommon(PO) znvpair(PO) spl(O) nls_utf8 isofs ppdev nls_iso8859_1 kvm_intel kvm
irqbypass joydev input_leds serio_raw parport_pc parport qemu_fw_cfg mac_hid
sch_fq_codel ib_iser rdma_cm iw_cm ib_cm ib_core iscsi_tcp libiscsi_tcp
libiscsi scsi_transport_iscsi virtio_rng ip_tables x_tables autofs4 btrfs
zstd_compress raid10 raid456 async_raid6_recov async_memcpy async_pq async_xor
async_tx xor raid6_pq libcrc32c raid0 multipath linear raid1 bcache psmouse
nvme nvme_core virtio_blk virtio_net virtio_scsi floppy i2c_piix4 pata_acpi
[ 5436.896104] CPU: 0 PID: 11216 Comm: kworker/0:1 Tainted: P O
4.15.0-54-generic #58+lp1796292+1
[ 5436.899985] Hardware name: QEMU Standard PC (i440FX + PIIX, 1996), BIOS
0.0.0 02/06/2015
[ 5436.902645] Workqueue: events cache_set_flush [bcache]
[ 5436.904374] RIP: 0010:cache_set_flush+0xf6/0x190 [bcache]
[ 5436.906183] RSP: 0018:ab52826bbe58 EFLAGS: 00010202
[ 5436.909050] RAX: RBX: 94d104aa0cc0 RCX:
[ 5436.911939] RDX: RSI: 2001 RDI:
[ 5436.914448] RBP: ab52826bbe78 R08: 94d13f61ac30 R09: 94d13f342b98
[ 5436.917113] R10: ab52803b3d10 R11: 02c6 R12: 0001
[ 5436.919210] R13: 94d13f622140 R14: 94d104aa0db8 R15:
[ 5436.921401] FS: () GS:94d13f60()
knlGS:
[ 5436.923743] CS: 0010 DS: ES: CR0: 80050033
[ 5436.926299] CR2: 09b8 CR3: 38252000 CR4: 06f0
[ 5436.929093] Call Trace:
[ 5436.930818] process_one_work+0x1de/0x410
[ 5436.932818] worker_thread+0x32/0x410
[ 5436.935332] kthread+0x121/0x140
[ 5436.937309] ? process_one_work+0x410/0x410
[ 5436.939393] ? kthread_create_worker_on_cpu+0x70/0x70
[ 5436.941263] ret_from_fork+0x35/0x40
[ 5436.943060] Code: b8 00 00 00 a8 02 74 c8 31 f6 4c 89 e7 e8 43 0e ff ff eb
bc 66 83 bb 4c f7 ff ff 00 48 8b 83 58 ff ff ff 74 31 41 bc 01 00 00 00 <48> 8b
b8 b8 09 00 00 48 85 ff 74 05 e8 f9 9d 0d d3 0f b7 8b 4c
[ 5436.950188] RIP: cache_set_flush+0xf6/0x190 [bcache] RSP: ab52826bbe58
[ 5436.952796] CR2: 09b8
[ 5436.954567] ---[ end trace b771415397e98c3d ]---
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1796292
Title:
Tight timeout for bcache removal causes spurious failures
Status in curtin:
Fix Released
Status in linux package in Ubuntu:
Confirmed
Status in linux source package in Bionic:
Confirmed
Status in linux source package in Cosmic:
Confirmed
Status in linux source package in Disco:
Confirmed
Status in linux source package in Eoan:
Confirmed
Bug description:
I've had a number of deployment faults where curtin would report
Timeout exceeded for removal of /sys/fs/bcache/xxx when doing a mass-
deployment of 30+ nodes. Upon retrying the node would usually deploy
fine. Experimentally I've set the timeout ridiculously high, and it
seems I'm getting no faults with this. I'm wondering if the timeout
for removal is set too tight, or might need to be made configurable.
--- curtin/util.py~ 2018-05-18 18:40:48.0 +
+++ curtin/util.py 2018-10-05 09:40:06.807390367 +
@@ -263,7 +263,7 @@
return _subp(*args, **kwargs)
-def wait_for_removal(path, retries=[1, 3, 5, 7]):
+def wait_for_removal(path, retries=[1, 3, 5, 7, 1200, 1200]):
if not path:
raise ValueError('wait_for_removal: missing path parameter')
To manage notifications about this bug go to:
https://bugs.launchpad.net/curtin/+bug/1796292/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833136] Re: use-after-free in hns_nic_net_xmit_hw
Verification, cosmic: ubuntu@d05-3:~$ cat /proc/version Linux version 4.18.20-kasan (ubuntu@d05-3) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #2 SMP Wed Jul 10 21:42:54 UTC 2019 ubuntu@d05-3:~$ dmesg | grep SAN ubuntu@d05-3:~$ bionic: ubuntu@d05-3:~$ cat /proc/version Linux version 4.15.18-kasan (ubuntu@d05-3) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #1 SMP Wed Jul 10 21:06:43 UTC 2019 ubuntu@d05-3:~$ dmesg | grep SAN ubuntu@d05-3:~$ ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-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/1833136 Title: use-after-free in hns_nic_net_xmit_hw Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] KASAN detected a use-after-free condition, which could lead to memory corruption or a crash. [Test Case] Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg. [Fix] 3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms
$ dpkg -l gcc | grep ^ii ii gcc4:8.3.0-1ubuntu3 amd64GNU C compiler $ sudo apt install linux-headers-generic [...] $ sudo apt install openafs-modules-dkms [...] Building for 5.0.0-20-generic Building initial module for 5.0.0-20-generic Done. openafs.ko: Running module version sanity check. modinfo: ERROR: missing module or filename. - Original module - No original module exists within this kernel - Installation - Installing to /lib/modules/5.0.0-20-generic/updates/dkms/ depmod... DKMS: install completed. $ sudo apt purge openafs-modules-dkms [...] $ sudo apt install gcc [...] $ dpkg -l gcc | grep ^ii ii gcc4:9.1.0-1ubuntu4 amd64GNU C compiler $ sudo apt install openafs-modules-dkms [...] Building for 5.0.0-20-generic Building initial module for 5.0.0-20-generic Error! Bad return status for module build on kernel: 5.0.0-20-generic (x86_64) Consult /var/lib/dkms/openafs/1.8.2/build/make.log for more information. dpkg: error processing package openafs-modules-dkms (--configure): installed openafs-modules-dkms package post-installation script subprocess returned error exit status 10 Errors were encountered while processing: openafs-modules-dkms E: Sub-process /usr/bin/dpkg returned an error code (1) $ This is a regression in buildability introduced *precisely* by the change in the gcc metapackage. ** No longer affects: linux (Ubuntu) ** Changed in: auto-package-testing Status: Triaged => 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/1836100 Title: Was able to migrate out of proposed despite breaking dkms Status in Auto Package Testing: In Progress Bug description: The recent gcc update in eoan migrated out of proposed despite the fact that it was breaking dmks/nvidia users, could we have some sort of autopkgtest added to make sure that gcc gets blocked in proposed the next time we have a such situation? (see bug #1830961) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1823753] Re: arm64: cma_alloc errors at boot
Verification: ubuntu@d06-1:~$ dmesg | grep cma [0.00] cma: Reserved 32 MiB at 0x7e00 [0.00] Memory: 526954648K/536866624K available (12092K kernel code, 1694K rwdata, 5112K rodata, 5504K init, 1161K bss, 9879208K reserved, 32768K cma-reserved) ubuntu@d06-1:~$ cat /proc/version Linux version 5.0.0-21-generic (buildd@bos02-arm64-046) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #22~18.04.1-Ubuntu SMP Thu Jul 4 17:25:45 UTC 2019 ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1823753 Title: arm64: cma_alloc errors at boot Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] We enabled CONFIG_DMA_CMA to fix bug 1803206, but that led to a regression on other arm64 systems that began spewing these messages on boot - sometimes > 10K of them: [ 19.534097] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534109] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534113] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534126] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534130] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534142] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534146] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534157] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534161] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 [ 19.534173] cma: cma_alloc: alloc failed, req-size: 16 pages, ret: -12 [ 19.534177] cma: cma_alloc: alloc failed, req-size: 64 pages, ret: -12 In a previous SRU (bug 1828092), we worked around this by just rate- limiting these messages. These are "err" priority messages though, so even a lower number of them is still disconcerting. [Fix] 1) Bump up the amount of available CMA on arm64 to 32M (same as upstream defconfig) 2) A patch-set from linux-next that redirects dma-direct contiguous allocations to alloc_pages() for single page allocations (single pages are by definition contiguous), avoiding CMA usage/fragmentation. [Test Case] dmesg | grep "cma_alloc: alloc failed" Some system configs will still have some of these errors even after this fix - but this should reduce them significantly. Per-driver optimizations can be used to make further improvements, but we should track those in other bugs. [Regression Risk] Tested on a HiSilicon D06 and HP m400 (Hi1620 & X-Gene arm64). Regression tested on: - Raspberry Pi 3B (see Comment #22) - Power9 system (ppc64el) - z/VM instance (s390x) - Intel Centerton system (amd64) Test builds are staged at http://ppa.launchpad.net/~dannf/ubuntu/cma To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1823753/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836100] 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 1836100 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/1836100 Title: Was able to migrate out of proposed despite breaking dkms Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Incomplete Bug description: The recent gcc update in eoan migrated out of proposed despite the fact that it was breaking dmks/nvidia users, could we have some sort of autopkgtest added to make sure that gcc gets blocked in proposed the next time we have a such situation? (see bug #1830961) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1831799] Re: Oops during sas expander hotplugging
Verification - Smoke test on system w/ libsas-driven controller: ubuntu@d06-1:~$ cat /proc/version Linux version 5.0.0-21-generic (buildd@bos02-arm64-046) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #22~18.04.1-Ubuntu SMP Thu Jul 4 17:25:45 UTC 2019 ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1831799 Title: Oops during sas expander hotplugging Status in linux package in Ubuntu: In Progress Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: In Progress Bug description: [Impact] System can oops when hot-plugging a SAS expander [Test Case] Toggle the link to an expander off & on. I can't actually do this w/ hardware I have, so regression testing is all I'll be able to do for the SRU. [Fix] 3b0541791453f scsi: libsas: delete sas port if expander discover failed [Regression Risk] Restricted to libsas-based drivers. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1831799/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms
and your reasoning seems to be flawed. The hardening flags were already enabled in gcc-8 long before. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836100 Title: Was able to migrate out of proposed despite breaking dkms Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: Incomplete Bug description: The recent gcc update in eoan migrated out of proposed despite the fact that it was breaking dmks/nvidia users, could we have some sort of autopkgtest added to make sure that gcc gets blocked in proposed the next time we have a such situation? (see bug #1830961) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835345] Re: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey)
** Changed in: linux-firmware (Ubuntu Bionic) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux-firmware (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835345 Title: [Intel CyclonePeak] Can not turn on BT after turn off (via Hotkey) Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Bionic: Fix Committed Status in linux-firmware source package in Disco: Fix Committed Bug description: [Impact] BT fails to enable again after disabled it by hotkey with the following message Bus 001 Device 004: ID 8087:0029 Intel Corp. [248987.643125] usb 1-10: device descriptor read/64, error -110 [249003.247721] usb 1-10: device descriptor read/64, error -110 [249003.483611] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249018.855466] usb 1-10: device descriptor read/64, error -110 [249034.467589] usb 1-10: device descriptor read/64, error -110 [249034.703574] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249045.299399] usb 1-10: device not accepting address 4, error -62 [249045.427510] usb 1-10: reset full-speed USB device number 4 using xhci_hcd [249050.675715] usb 1-10: Device not responding to setup address. [249050.883541] usb 1-10: device not accepting address 4, error -71 [Fix] Found the updated firmware fixes the issue [Test] Verify on the machine couple days, and can't duplicate the issue anymore. [Regression Potential] Low, the system keeps running for 5 days, and pass s3 tests 30 times, everything works well. [Misc] The firmware for the wifi/bt card is intel/ibt-20-0-3.*, but intel/ibt-20-0-4.* have identical md5sum. To avoid the following new cards require the new fw_revision, so SRU both of them. To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1835345/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835449] Re: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260)
** Changed in: linux-firmware (Ubuntu Xenial) Status: In Progress => Fix Committed ** Changed in: linux-firmware (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-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1835449 Title: Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9260) Status in linux-firmware package in Ubuntu: In Progress Status in linux-firmware source package in Xenial: Fix Committed Status in linux-firmware source package in Bionic: Fix Committed Bug description: [Impact] Intel Wireless-AC 9260 Bluetooth doesn't pair to Bluetooth 5.0 HID devices. [Fix] Bluetooth FW Build REL0329 or newer is known to have fixed this problem on Cosmic, and for Disco we have REL0420. On Bionic and Xenial it takes a firmware backport from upstream commit c2d8f1b7f820b31b6120d741c23db23340a72821. Original patch modified to fix conflicts in the WHENCE file. [Test Case] Verified on hardware platforms with Intel Wireless AC 9260 installed, e.g. Dell Precision 7530. Copied the two blobs to /lib/firmware/intel and power off the device completely to trigger firmware reload at the next boot. [Regression Risk] Low. Tried following kernels with REL0329 firmware blobs: * 4.4.0-154-generic: Xenial, WiFi/Bluetooth doesn't work * 4.8.0-58-generic: Xenial, even doesn't boot to console * 4.10.0-42-generic: Xenial, WiFi/Bluetooth doesn't work * 4.11.0-14-generic: Xenial, WiFi/Bluetooth doesn't work * 4.13.0-45-generic: Xenial * 4.15.0-54-generic: Xenial, Bionic * 4.15.0-1043-oem: Xenial, Bionic For those WiFi/Bluetooth doesn't work versions, WiFi/Bluetooth doesn't work even with current firmware blobs shipped in Xenial's linux-firmware REL0186. So overall, these updated blobs are only loaded by hardware requires them, and they doesn't bring harm to known working configurations. Original Bug Description Same problem exactly as encountered with Intel 9560 is also happening with Intel 9260. Update to linux-firmware 1.173.8 did not fix the problem. Everything is working fine when using 4.15 kernel, but not for 4.18+ 5.0+. Reference problem: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1829737 You-Sheng Yang advised to do this by email and it fixed my issue, so I think the 9260 driver would need to be updated in the bionic branch (it seems to be updated in newer branches). -- Basically you should try copy the latest firmware (ibt-*) under https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/intel , power off the device completely and power on, then have a check on bluetooth pairing. -- Linux ideapad 5.0.0-20-generic #21~18.04.1-Ubuntu SMP Thu Jun 27 04:04:37 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux OS: Linux Mint 19.1 Tessa x86_64 Host: 81JB Lenovo ideapad 730S-13IWL Wifi/Bluetooth card is Intel 9260 @:/etc$ dmesg | egrep -i 'blue|firm' [0.099619] Spectre V2 : Enabling Restricted Speculation for firmware calls [0.173124] ACPI: [Firmware Bug]: BIOS _OSI(Linux) query ignored [2.379392] [Firmware Bug]: Invalid critical threshold (0) [2.699758] [drm] Finished loading DMC firmware i915/kbl_dmc_ver1_04.bin (v1.4) [6.259427] iwlwifi :73:00.0: loaded firmware version 43.95eb4e97.0 op_mode iwlmvm [6.337749] Bluetooth: Core ver 2.22 [6.337767] Bluetooth: HCI device and connection manager initialized [6.337770] Bluetooth: HCI socket layer initialized [6.337773] Bluetooth: L2CAP socket layer initialized [6.33] Bluetooth: SCO socket layer initialized [6.368073] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017 [7.309936] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [7.309938] Bluetooth: BNEP filters: protocol multicast [7.309943] Bluetooth: BNEP socket layer initialized [ 17.197268] Bluetooth: RFCOMM TTY layer initialized [ 17.197275] Bluetooth: RFCOMM socket layer initialized [ 17.197284] Bluetooth: RFCOMM ver 1.11 [ 104.453159] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.509148] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.551340] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.589338] Bluetooth: hci0: request failed to create LE connection: status 0x0c [ 104.623323] Bluetooth: hci0: request failed to create LE connection: status 0x0c To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-firmware/+bug/1835449/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help
[Kernel-packages] [Bug 1836100] Re: Was able to migrate out of proposed despite breaking dkms
I disagree. user space migrations should not be blocked by kernel changes. We know that the kernel is sensible to compiler changes, so it probably should build-depend on an explicit GCC version. And no, we should not block migrations on build failures, just for this case. So the kernel needs to have an explicit switch to a new GCC version once it's supported by the kernel. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836100 Title: Was able to migrate out of proposed despite breaking dkms Status in Auto Package Testing: Triaged Status in linux package in Ubuntu: New Bug description: The recent gcc update in eoan migrated out of proposed despite the fact that it was breaking dmks/nvidia users, could we have some sort of autopkgtest added to make sure that gcc gets blocked in proposed the next time we have a such situation? (see bug #1830961) To manage notifications about this bug go to: https://bugs.launchpad.net/auto-package-testing/+bug/1836100/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
As a follow-up tp my previous comment #12 (https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1830961/comments/12), I have discovered 2 new facts: - I am not able to build dpdk 19.05 on the same system anymore, (cf. build log), unless I modify the gcc symlink to point to gcc-8 instead of gcc-9 - however, the xtables -addons issue encountered on the previous system has not been seen on 2 other Ubuntu Eoan platforms with the exact same versions of: + gcc-9 (and/usr/bin/gcc -> gcc-9) + linux kernels + xtables-addons-dkms/common ** Attachment added: "DPDK 19.05 build log" https://bugs.launchpad.net/ubuntu/+source/xtables-addons/+bug/1830961/+attachment/5276174/+files/dpdk_19.05_amd64.build -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Committed Status in virtualbox package in Ubuntu: Confirmed Status in xtables-addons package in Ubuntu: New Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1775165] Re: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel
Hi Po-Hsu Lin, Sorry for not updating this bug earlier. Upstream 4.4 and 4.9 are also effected by this bug, so I went and posted the patches to be considered for upstream -stable. Upstream 4.4 thread: [1] Upstream 4.9 thread: [2] Now, I got some feedback from the original author of the upstream commits that the scenario is more complicated than I thought, and I ended up missing a lot of commits required to fix the problem completely. It turns out that the fixes prevent the system from crashing, but that some data structures silently get corrupted over time, meaning the system will eventually require a reboot anyway. If you are interested, you can read all about it here: [3] [4] [5] For now, it seems the list of commits required to actually fix the problem [6] is a little too large to include in -stable, since it changes a lot of that subsystem dramatically, and it might introduce regressions, which I want to avoid. In the end Greg K-H agreed with me [7], the patches were dropped, and this won't be getting fixed upstream. That is the status of this bug, and it likely won't be fixed. I did try, but there is just too much code to backport and support, its easier to tell people to use HWE kernels if they are hitting the problem. [1] https://www.spinics.net/lists/stable/msg296857.html [2] https://www.spinics.net/lists/stable/msg296895.html [3] https://www.spinics.net/lists/stable/msg296992.html [4] https://www.spinics.net/lists/stable/msg297024.html [5] https://www.spinics.net/lists/stable/msg297027.html [6] https://www.spinics.net/lists/stable/msg297476.html [7] https://www.spinics.net/lists/stable/msg297485.html -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1775165 Title: fanotify07/fanotify08 in LTP syscall test generates kernel trace with T/X/X-AWS kernel Status in ubuntu-kernel-tests: New Status in linux package in Ubuntu: Triaged Status in linux source package in Trusty: Triaged Status in linux source package in Xenial: In Progress Bug description: BugLink: https://bugs.launchpad.net/bugs/1775165 [Impact] When userspace tasks which are processing fanotify permission events act incorrectly, the fsnotify_mark_srcu SRCU is held indefinitely which causes the whole notification subsystem to hang. This has been seen in production, and it can also be seen when running the Linux Test Project testsuite, specifically fanotify07. [Fix] Instead of holding the SRCU lock while waiting for userspace to respond, which may never happen, or not in the order we are expecting, we drop the fsnotify_mark_srcu SRCU lock before waiting for userspace response, and then reacquire the lock again when userspace responds. The fixes are from a series of upstream commits: 05f0e38724e8449184acd8fbf0473ee5a07adc6c (cherry-pick) 9385a84d7e1f658bb2d96ab798393e4b16268aaa (backport) abc77577a669f424c5d0c185b9994f2621c52aa4 (backport) The following are upstream commits necessary for the fixes to function: 35e481761cdc688dbee0ef552a13f49af8eba6cc (backport) 0918f1c309b86301605650c836ddd2021d311ae2 (cherry-pick) [Testcase] You can reproduce the problem pretty quickly with the Linux Test Project: Steps (with root): 1. sudo apt-get install git xfsprogs -y 2. git clone --depth=1 https://github.com/linux-test-project/ltp.git 3. cd ltp 4. make autotools 5. ./configure 6. make; make install 7. cd /opt/ltp 8. echo -e "fanotify07 fanotify07 \nfanotify08 fanotify08" > /tmp/jobs 9. ./runltp -f /tmp/jobs On a stock Xenial kernel, the system will hang, and the testcase will look like: <<>> tag=fanotify07 stime=1554326200 cmdline="fanotify07 " contacts="" analysis=exit <<>> tst_test.c:1096: INFO: Timeout per run is 0h 05m 00s Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Test timeouted, sending SIGKILL! Cannot kill test processes! Congratulation, likely test hit a kernel bug. Exitting uncleanly... <<>> initiation_status="ok" duration=350 termination_type=exited termination_id=1 corefile=no cutime=0 cstime=0 <<>> Looking at dmesg, we see the following call stack [ 790.772792] LTP: starting fanotify07 (fanotify07 ) [ 960.140455] INFO: task fsnotify_mark:36 blocked for more than 120 seconds. [ 960.140867] Not tainted 4.4.0-142-generic #168-Ubuntu [ 960.141185] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 960.141498] fsnotify_mark D 8800b6703c98 036 2 0x [ 960.141516] 8800b6703c98
[Kernel-packages] [Bug 1801540]
I was wondering about this as well. It looks like not everyone have the exact same issue. For example, I have problems with sound input only while other people reported sound problem with output as well. I tried to gather and resume the reports given until now. I hope I didn't made a mistake. The values "Yes", "No" and '"Same"' in the "Input" and "Output" columns means "Does have the issue", "Does not have the issue" and 'Reported "the same problem"' respectively. Reporter Input Output Codec Motherboard == = == = icebalm[...] YesNo ALC1220 ASUS CROSSHAIR VI HERO Malte zu Klampen "Same" "Same" ? ASUS PRIME X370-PRO Luke Ricciolo Yes"Same" ALC1220 ASUS CROSSHAIR VI HERO Frédéric Pierret "Same" "Same" ALC1220 ASROCK X370 GAMING K4 thomasg"Same" "Same" ALC1220 ASUS PRIME X370-PRO Artem Hluvchynskyi ? YesALC1220 ASROCK X370 GAMING K4 henk717[...] YesNo ALC1220 MSI X370 Gaming Pro Carbon aeder.redea[...] YesNo ALC1220 ASUS ROG STRIX X470-F GAMING Sebastian Hofmann ? YesALC1220 ASUS ROG STRIX X370-F GAMING Luca "Same" "Same" ALC892? Axel "Same" "Same" ? Gigabyte X470 AORUS Parker H "Same" "Same" ? Taichi X370 Marten "Same" "Same" ALC1220 Gigabyte GA-AX370-Gaming K3 evilphish[...] YesNo ALC1220 ASUS ROG CROSSHAIR VI HERO WiFi Tomasz Pieczerak YesNo ALC1220 Gigabyte B450 AORUS PRO ben.schaaf[...]YesNo ALC887-VD ASUS PRIME B350-Plus spychodelics[...] "Same" "Same" ALC1220 ASUS PRIME X470-PRO Anders ? ? ? ASUS PRIME X370-PRO Rafael Rossi YesYesALC1220 ASUS ROG STRIX X470-F GAMING daxcore[...] "Same" "Same" ALC1220 Micro-Star MEG X399 CREATION MS-7B92 wtravisjones[...] "Same" "Same" ALC1220 ASRock B450 Gaming-ITX/ac ZigZag "Same" "Same" ? ASUS ROG Strix B450-F George Gibbs "Same" "Same" ? ASUS ROG CROSSHAIR VI HERO Marco "Same" "Same" ALC892Gigabyte B450 AORUS ELITE Benjamin Cheng Yes? ? ASUS PRIME X470-PRO Jon"Same" YesALC1220 MSI B450 Carbon Pro Gaming AC Léo El AmriYesNo ALC1220 ASRock B450 Gaming-ITX/ac -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
Seems to affect playback as well (at least for me unless tsched=0, but even then get weird bugs), probably should be something like this: snd_hda_intel - Sound input/output is distorted on AM4 platforms using Realtek codecs. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
(In reply to Jon from comment #111) > Seems to affect playback as well (at least for me unless tsched=0, but even > then get weird bugs), probably should be something like this: > > snd_hda_intel - Sound input/output is distorted on AM4 platforms using > Realtek codecs. This seems more in line with the problems in this thread, to me. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
Should this bug be renamed to something like "Sound capture is crackled with all snd_hda_intel codecs on AM4 platforms"? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1801540]
(In reply to Anders from comment #108) > better now? Thanks a lot, now I just need to go back reading the specs :P -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1801540 Title: Microphone distorted sound on ALC892/1220 on AMD chipsets Status in Linux: Confirmed Status in linux package in Ubuntu: Incomplete Status in pulseaudio package in Ubuntu: Confirmed Bug description: Not sure if I'll report this upstream but there is definitely an issue with microphone recording on my desktop, this is not happening on my laptop which has a different codec. Already tried all workarounds possible, no luck. Only with my desktop with this particular motherboard. No issues in Windows, the sound recorded in there is distorted and has some static and robotic tone on high-pitch. alsa-info on the attachments To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/1801540/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833136] Re: use-after-free in hns_nic_net_xmit_hw
** Changed in: linux (Ubuntu Disco) Status: In Progress => Fix Committed ** Changed in: linux (Ubuntu Eoan) 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/1833136 Title: use-after-free in hns_nic_net_xmit_hw Status in linux package in Ubuntu: Fix Committed Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] KASAN detected a use-after-free condition, which could lead to memory corruption or a crash. [Test Case] Rebuild kernel w/ CONFIG_KASAN=y, look for errors in dmesg. [Fix] 3a39a12ad364a net: hns: fix KASAN: use-after-free in hns_nic_net_xmit_hw() [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833136/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833138] Re: Fix occasional boot time crash in hns driver
Verification: = Disco = ubuntu@d05-3:~$ cat /proc/version Linux version 5.0.0-21-generic (buildd@bos02-arm64-046) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #22~18.04.1-Ubuntu SMP Thu Jul 4 17:25:45 UTC 2019 ubuntu@d05-3:~$ dmesg | grep hns [9.183430] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [9.964208] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [ 10.206824] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [ 10.228666] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [ 10.59] hns-nic HISI00C2:00 enahisic2i0: renamed from eth0 [ 10.573215] hns-nic HISI00C2:01 enahisic2i1: renamed from eth0 [ 10.629089] hns-nic HISI00C2:02 enahisic2i2: renamed from eth0 [ 10.704777] hns-nic HISI00C2:03 enahisic2i3: renamed from eth1 [ 51.988203] hns-nic HISI00C2:01 enahisic2i1: link up [ 196.115843] hns-nic HISI00C2:01 enahisic2i1: link ubuntu@d05-3:~$ dmesg --level=err [1.675454] Couldn't get size: 0x800e [1.675455] MODSIGN: Couldn't get UEFI db list [1.675465] Couldn't get size: 0x800e [1.675477] Couldn't get size: 0x800e [ 10.195043] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -12 [ 10.202314] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -12 [ 10.212589] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -12 [ 10.230484] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -12 [ 10.244378] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -12 [ 10.263688] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -12 [ 10.270394] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -12 [ 10.277101] cma: cma_alloc: alloc failed, req-size: 32 pages, ret: -12 [ 26.047067] sd 3:0:0:0: [sdc] No Caching mode page found [ 26.047069] sd 3:0:0:0: [sdc] Assuming drive cache: write through [ 41.137188] ipmi_si dmi-ipmi-si.0: Interface detection failed = Cosmic = ubuntu@d05-3:~$ cat /proc/version Linux version 4.18.0-26-generic (buildd@bos02-arm64-042) (gcc version 8.3.0 (Ubuntu 8.3.0-6ubuntu1~18.10.1)) #27-Ubuntu SMP Tue Jul 2 15:36:34 UTC 2019 ubuntu@d05-3:~$ dmesg | grep hns [8.820811] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [9.501482] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [9.790848] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [9.820309] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [ 10.228363] hns-nic HISI00C2:00 enahisic2i0: renamed from eth0 [ 10.323629] hns-nic HISI00C2:01 enahisic2i1: renamed from eth0 [ 10.379501] hns-nic HISI00C2:02 enahisic2i2: renamed from eth0 [ 10.447618] hns-nic HISI00C2:03 enahisic2i3: renamed from eth0 [ 43.274888] hns-nic HISI00C2:01 enahisic2i1: link up ubuntu@d05-3:~$ dmesg --level=err [ 25.609748] sd 3:0:0:0: [sdc] No Caching mode page found [ 25.609750] sd 3:0:0:0: [sdc] Assuming drive cache: write through [ 37.140540] ipmi_si dmi-ipmi-si.0: Interface detection failed = Bionic = ubuntu@d05-3:~$ cat /proc/version Linux version 4.15.0-55-generic (buildd@bos02-arm64-065) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #60-Ubuntu SMP Tue Jul 2 18:23:38 UTC 2019 ubuntu@d05-3:~$ dmesg | grep hns [8.925729] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [9.572946] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [9.821225] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [9.850841] hns_dsaf HISI00B2:00: no mc-mac-mask property, set to default value. [ 10.709111] hns-nic HISI00C2:02 enahisic2i2: renamed from eth3 [ 10.749214] hns-nic HISI00C2:01 enahisic2i1: renamed from eth1 [ 10.801003] hns-nic HISI00C2:00 enahisic2i0: renamed from eth0 [ 10.833089] hns-nic HISI00C2:03 enahisic2i3: renamed from eth4 [ 43.013034] hns-nic HISI00C2:01 enahisic2i1: link up ubuntu@d05-3:~$ dmesg ^C ubuntu@d05-3:~$ dmesg --level=err [1.603912] Couldn't get size: 0x800e [1.603914] MODSIGN: Couldn't get UEFI db list [1.603919] Couldn't get size: 0x800e [1.603926] Couldn't get size: 0x800e [ 24.976682] sd 3:0:0:0: [sdc] No Caching mode page found [ 24.976685] sd 3:0:0:0: [sdc] Assuming drive cache: write through [ 36.628347] ipmi_si dmi-ipmi-si.0: Interface detection failed ** Tags removed: verification-needed-bionic verification-needed-cosmic ** Tags added: verification-done-bionic verification-done-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/1833138 Title: Fix occasional boot time crash in hns driver Status in linux package in Ubuntu: In Progress Status in linux source package in Bionic: Fix Committed Status in linux source package in Cosmic: Fix
[Kernel-packages] [Bug 1830961] Re: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible]
If I make the same changes to the Makefile as per the link in comment #16, then the kernel compiles fine and without the zillions of warnings I mentioned in comment #13. However I can not find this anywhere "upstream" as the notes seem to indicate. doug@serv-ee:~/temp-k-git/linux$ git diff diff --git a/Makefile b/Makefile index 3e4868a6498b..d8ccc47215be 100644 --- a/Makefile +++ b/Makefile @@ -630,8 +630,8 @@ ifdef CONFIG_FUNCTION_TRACER CC_FLAGS_FTRACE := -pg endif -RETPOLINE_CFLAGS_GCC := -mindirect-branch=thunk-extern -mindirect-branch-register -RETPOLINE_VDSO_CFLAGS_GCC := -mindirect-branch=thunk-inline -mindirect-branch-register +RETPOLINE_CFLAGS_GCC := -mindirect-branch=thunk-extern -mindirect-branch-register -fcf-protection=none +RETPOLINE_VDSO_CFLAGS_GCC := -mindirect-branch=thunk-inline -mindirect-branch-register -fcf-protection=none RETPOLINE_CFLAGS_CLANG := -mretpoline-external-thunk RETPOLINE_VDSO_CFLAGS_CLANG := -mretpoline RETPOLINE_CFLAGS := $(call cc-option,$(RETPOLINE_CFLAGS_GCC),$(call cc-option,$(RETPOLINE_CFLAGS_CLANG))) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1830961 Title: Kernels & kernel drivers fail to build with gcc-9 [error: ‘-mindirect- branch’ and ‘-fcf-protection’ are not compatible] Status in gcc-9 package in Ubuntu: Invalid Status in linux package in Ubuntu: Confirmed Status in nvidia-graphics-drivers-430 package in Ubuntu: Fix Committed Status in virtualbox package in Ubuntu: Confirmed Status in xtables-addons package in Ubuntu: New Bug description: Compiling kernels & kernel modules fails due to these errors: ./include/linux/compiler.h:193:1: error: ‘-mindirect-branch’ and ‘-fcf-protection’ are not compatible (This happens with any kernel modules.) This appears to be due to the changes in 9.1.0-3ubuntu1 enabling -fcf- protection by default on 19.10's gcc-9. Switching to gcc-8 allows compilation to proceed. WORKAROUND: sudo ln -fs gcc-8 /usr/bin/gcc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-9/+bug/1830961/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834950] Re: linux-azure: 4.15.0-1051.56 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Fix Released ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834948 (trusty/linux-azure) derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Testing - phase-changed: Wednesday, 10. July 2019 16:13 UTC + phase: Signoff + phase-changed: Wednesday, 10. July 2019 20:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834950 Title: linux-azure: 4.15.0-1051.56 -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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834948 (trusty/linux-azure) derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Signoff phase-changed: Wednesday, 10. July 2019 20:43 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836045] Re: ftbfs: gnat cross targeting powerpc
> /usr/include/powerpc64le-linux-gnu/asm/socket.h: this is the wrong header, I am talking about the powerpc-linux-gnu target. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836045 Title: ftbfs: gnat cross targeting powerpc Status in gcc-8-cross package in Ubuntu: Confirmed Status in gcc-9-cross package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: both seen with gcc-8-cross and gcc-9-cross (search the build logs for "unfinished": /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ -B/usr/powerpc-linux-gnu/bin/ -B/usr/powerpc-li nux-gnu/lib/ -isystem /usr/powerpc-linux-gnu/include -isystem /usr/powerpc-linux-gnu/sys-include -isystem /< >/gcc/build/sys-include-c -g -O2 -W -Wall -gnatpg -nostdinc -gnatn a-direct.adb -o a-direct.o a-direct.adb:734:27: "NAME_MAX" is undefined a-direct.adb:743:28: "SIZEOF_struct_dirent_alloc" is undefined a-direct.adb:1210:24: "ENOENT" is undefined s-filatt.ads:62:18: "SIZEOF_struct_file_attributes" not declared in "OS_Constants" s-oscons.ads:50:26: "Target_OS" is undefined s-oscons.ads:54:01: (style) multiple blank lines s-oscons.ads:59:01: (style) multiple blank lines s-oscons.ads:64:01: (style) multiple blank lines s-oscons.ads:69:01: (style) multiple blank lines s-oscons.ads:74:01: (style) multiple blank lines s-oscons.ads:79:01: (style) multiple blank lines s-oscons.ads:86:01: (style) multiple blank lines s-oscons.ads:91:01: (style) multiple blank lines s-oscons.ads:96:01: (style) multiple blank lines s-oscons.ads:101:01: (style) multiple blank lines s-oscons.ads:106:01: (style) multiple blank lines s-oscons.ads:111:01: (style) multiple blank lines s-oscons.ads:116:01: (style) multiple blank lines s-oscons.ads:121:01: (style) multiple blank lines s-oscons.ads:126:01: (style) multiple blank lines s-oscons.ads:131:01: (style) multiple blank lines s-oscons.ads:136:01: (style) multiple blank lines s-oscons.ads:147:01: (style) multiple blank lines s-oscons.ads:166:01: (style) multiple blank lines s-oscons.ads:173:01: (style) multiple blank lines s-oscons.ads:176:01: (style) multiple blank lines s-oscons.ads:181:01: (style) multiple blank lines make[9]: *** [../gcc-interface/Makefile:299: a-direct.o] Error 1 make[9]: Leaving directory '/<>/gcc/build/gcc/ada/rts' make[8]: *** [gcc-interface/Makefile:623: gnatlib] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-8-cross/+bug/1836045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836045] Re: ftbfs: gnat cross targeting powerpc
gcc/ada/gsocket.h:#include so this is using the glibc header, no kernel header directly. It looks like that with linux-libc-dev built using linux 5.2, I'm able to build the cross compiler. I'll update once the build finishes. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836045 Title: ftbfs: gnat cross targeting powerpc Status in gcc-8-cross package in Ubuntu: Confirmed Status in gcc-9-cross package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: both seen with gcc-8-cross and gcc-9-cross (search the build logs for "unfinished": /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ -B/usr/powerpc-linux-gnu/bin/ -B/usr/powerpc-li nux-gnu/lib/ -isystem /usr/powerpc-linux-gnu/include -isystem /usr/powerpc-linux-gnu/sys-include -isystem /< >/gcc/build/sys-include-c -g -O2 -W -Wall -gnatpg -nostdinc -gnatn a-direct.adb -o a-direct.o a-direct.adb:734:27: "NAME_MAX" is undefined a-direct.adb:743:28: "SIZEOF_struct_dirent_alloc" is undefined a-direct.adb:1210:24: "ENOENT" is undefined s-filatt.ads:62:18: "SIZEOF_struct_file_attributes" not declared in "OS_Constants" s-oscons.ads:50:26: "Target_OS" is undefined s-oscons.ads:54:01: (style) multiple blank lines s-oscons.ads:59:01: (style) multiple blank lines s-oscons.ads:64:01: (style) multiple blank lines s-oscons.ads:69:01: (style) multiple blank lines s-oscons.ads:74:01: (style) multiple blank lines s-oscons.ads:79:01: (style) multiple blank lines s-oscons.ads:86:01: (style) multiple blank lines s-oscons.ads:91:01: (style) multiple blank lines s-oscons.ads:96:01: (style) multiple blank lines s-oscons.ads:101:01: (style) multiple blank lines s-oscons.ads:106:01: (style) multiple blank lines s-oscons.ads:111:01: (style) multiple blank lines s-oscons.ads:116:01: (style) multiple blank lines s-oscons.ads:121:01: (style) multiple blank lines s-oscons.ads:126:01: (style) multiple blank lines s-oscons.ads:131:01: (style) multiple blank lines s-oscons.ads:136:01: (style) multiple blank lines s-oscons.ads:147:01: (style) multiple blank lines s-oscons.ads:166:01: (style) multiple blank lines s-oscons.ads:173:01: (style) multiple blank lines s-oscons.ads:176:01: (style) multiple blank lines s-oscons.ads:181:01: (style) multiple blank lines make[9]: *** [../gcc-interface/Makefile:299: a-direct.o] Error 1 make[9]: Leaving directory '/<>/gcc/build/gcc/ada/rts' make[8]: *** [gcc-interface/Makefile:623: gnatlib] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-8-cross/+bug/1836045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836045] Re: ftbfs: gnat cross targeting powerpc
That's not true; most architectures don't have a match for SO_RCVTIMEO,
as they're using the definition from asm-generic, just as powerpc should
be. The others were updated differently because they do not include asm-
generic/socket.h. And powerpc clearly does have a definition for it,
since the build complains that SO_RCVTIMEO_OLD is not defined and not
SO_RCVTIMEO. The question is why isn't SO_RCVTIMEO_OLD defined.
I tried cross-compiling the following for ppc64el and did not receive
any errors about SO_RCVTIMEO or SO_RCVTIMEO_OLD being undefined, nor did
it complain when I used SO_RCVTIMEO_OLD, so it seems like it's working
as intended. That leaves me wondering whether something isn't including
asm-generic/socket.h when it should be including asm/socket.h, or
something like that. I don't see any such mistakes in linux-libc-dev
though.
#include
#include
int main(void)
{
printf("%d\n", SO_RCVTIMEO);
return 0;
}
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1836045
Title:
ftbfs: gnat cross targeting powerpc
Status in gcc-8-cross package in Ubuntu:
Confirmed
Status in gcc-9-cross package in Ubuntu:
Confirmed
Status in linux package in Ubuntu:
Confirmed
Bug description:
both seen with gcc-8-cross and gcc-9-cross (search the build logs for
"unfinished":
/<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/
-B/usr/powerpc-linux-gnu/bin/ -B/usr/powerpc-li
nux-gnu/lib/ -isystem /usr/powerpc-linux-gnu/include -isystem
/usr/powerpc-linux-gnu/sys-include -isystem /<
>/gcc/build/sys-include-c -g -O2 -W -Wall -gnatpg -nostdinc -gnatn
a-direct.adb -o a-direct.o
a-direct.adb:734:27: "NAME_MAX" is undefined
a-direct.adb:743:28: "SIZEOF_struct_dirent_alloc" is undefined
a-direct.adb:1210:24: "ENOENT" is undefined
s-filatt.ads:62:18: "SIZEOF_struct_file_attributes" not declared in
"OS_Constants"
s-oscons.ads:50:26: "Target_OS" is undefined
s-oscons.ads:54:01: (style) multiple blank lines
s-oscons.ads:59:01: (style) multiple blank lines
s-oscons.ads:64:01: (style) multiple blank lines
s-oscons.ads:69:01: (style) multiple blank lines
s-oscons.ads:74:01: (style) multiple blank lines
s-oscons.ads:79:01: (style) multiple blank lines
s-oscons.ads:86:01: (style) multiple blank lines
s-oscons.ads:91:01: (style) multiple blank lines
s-oscons.ads:96:01: (style) multiple blank lines
s-oscons.ads:101:01: (style) multiple blank lines
s-oscons.ads:106:01: (style) multiple blank lines
s-oscons.ads:111:01: (style) multiple blank lines
s-oscons.ads:116:01: (style) multiple blank lines
s-oscons.ads:121:01: (style) multiple blank lines
s-oscons.ads:126:01: (style) multiple blank lines
s-oscons.ads:131:01: (style) multiple blank lines
s-oscons.ads:136:01: (style) multiple blank lines
s-oscons.ads:147:01: (style) multiple blank lines
s-oscons.ads:166:01: (style) multiple blank lines
s-oscons.ads:173:01: (style) multiple blank lines
s-oscons.ads:176:01: (style) multiple blank lines
s-oscons.ads:181:01: (style) multiple blank lines
make[9]: *** [../gcc-interface/Makefile:299: a-direct.o] Error 1
make[9]: Leaving directory '/<>/gcc/build/gcc/ada/rts'
make[8]: *** [gcc-interface/Makefile:623: gnatlib] Error 2
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gcc-8-cross/+bug/1836045/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true - phase: Ready for Testing - phase-changed: Wednesday, 10. July 2019 09:34 UTC + phase: Signoff + phase-changed: Wednesday, 10. July 2019 20:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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 verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Signoff phase-changed: Wednesday, 10. July 2019 20:03 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Re: OBSOLETE_BY in DKMS.CONF does not work
It would also be good to get this fixed in Ubuntu 19.04 codename Disco Dingo. ** Summary changed: - OBSOLETE_BY in DKMS.CONF not work + OBSOLETE_BY in DKMS.CONF does not work ** Changed in: dkms (Ubuntu Bionic) Status: New => Fix Committed ** Tags added: verification-needed verification-needed-bionic -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1832909] Re: Cache line contention prevents scaling of 100Gbps performance
** Changed in: linux (Ubuntu Eoan) 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/1832909 Title: Cache line contention prevents scaling of 100Gbps performance Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Status in linux source package in Eoan: Fix Committed Bug description: [Impact] 100Gbps network performance, as measured on an hns3 controller, doesn't scale as queue size goes up. [Test Case] Use a traffic generator instrument to generate load, using the SUT as an IP forwarder. 19.04 today: 8 queue 12 queue 16 queue 24 queue 37G 45G 38G 33G With the patch applied: 8 queue 12 queue 16 queue 24 queue 37G 50G 47G 47G [Fix] 14bd9a607f908 iommu/iova: Separate atomic variables to improve performance [Regression Risk] The patch makes no functional change, just reorders members of a structure. However, it is possible that this has unforeseen negative performance impacts on some platform. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1832909/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1828948] Please test proposed package
Hello Alex, or anyone else affected, Accepted dkms into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/dkms/2.3-3ubuntu9.4 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-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to dkms in Ubuntu. https://bugs.launchpad.net/bugs/1828948 Title: OBSOLETE_BY in DKMS.CONF does not work Status in DKMS: Fix Released Status in OEM Priority Project: Fix Committed Status in dkms package in Ubuntu: Fix Released Status in dkms source package in Bionic: Fix Committed Bug description: [Impact] OBSOLETE_BY in DKMS.CONF not work Which also be reported on upstream: https://github.com/dell/dkms/issues/81 [Test case] 1. add OBSOLETE_BY in DKMS.CONF e.g. OBSOLETE_BY="4.15.0-1033" 2. the kernel module should not be built with kernel greater than the version specified by OBSOLETE_BY e.g. - user install kernel 4.15.0-1030 and 4.15.0-10360 - user install kernel oem-wifi-qualcomm-ath10k-lp1803647-4.15-dkms [1] which has OBSOLETE_BY="4.15.0-1033" - the kernel module from dkms [1] should only built for 4.15.0-1030, but not for 4.15.0-10360 [Regression potential] None as it used to work, but somehow regression there. [1] https://code.launchpad.net/~alextu/+recipe/oem-wifi-qualcomm- ath10k-lp1803647-4.15-dkms-daily To manage notifications about this bug go to: https://bugs.launchpad.net/dkms/+bug/1828948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1833132] Re: net: hns: Fix loopback test failed at copper ports
Verification: ubuntu@d05-3:~$ cat /proc/version Linux version 5.0.0-21-generic (buildd@bos02-arm64-046) (gcc version 7.4.0 (Ubuntu/Linaro 7.4.0-1ubuntu1~18.04.1)) #22~18.04.1-Ubuntu SMP Thu Jul 4 17:25:45 UTC 2019 ubuntu@d05-3:~$ sudo ethtool -t enahisic2i1 offline The test result is PASS The test extra info: MacLoopback test 0 Serdes Loopback test 0 PhyLoopback test 0 ubuntu@d05-3:~$ ** Tags removed: verification-needed-disco ** Tags added: verification-done-disco ** Changed in: linux (Ubuntu) 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/1833132 Title: net: hns: Fix loopback test failed at copper ports Status in linux package in Ubuntu: Fix Committed Status in linux source package in Disco: Fix Committed Bug description: [Impact] The ethtool offline test always fails on HNS devices w/ copper ports. [Test Case] sudo ethtool -t enahisic2i1 offline [Fix] 2e1f164861e50 net: hns: Fix loopback test failed at copper ports [Regression Risk] Fix is restricted to the hns driver, which is the driver for the nics on the Hi1616 SoC. Regressions would therefore be limited to platforms using this SoC, such as the HiSilicon D05 board. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1833132/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835270] Re: linux: 3.2.0-142.189 -proposed tracker
** Changed in: kernel-sru-workflow/security-signoff Status: Confirmed => In Progress ** Changed in: kernel-sru-workflow/security-signoff Assignee: Canonical Security Team (canonical-security) => Steve Beattie (sbeattie) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1835270 Title: linux: 3.2.0-142.189 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-lbm series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Invalid Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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 verification-testing series: Confirmed Status in linux package in Ubuntu: Invalid Status in linux source package in Precise: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true bugs-spammed: true phase: Ready for Testing phase-changed: Wednesday, 10. July 2019 09:34 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835270/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836026] 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 1836026 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/1836026 Title: There is no the screen rotation option in Settings with sensor LNG2DM Status in linux package in Ubuntu: Incomplete Bug description: If a machine has a accelerometer, the screen rotation option won't be drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836026] Re: There is no the screen rotation option in Settings with sensor LNG2DM
The upstream bug is a kernel one so reassigning to that component ** Package changed: iio-sensor-proxy (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/1836026 Title: There is no the screen rotation option in Settings with sensor LNG2DM Status in linux package in Ubuntu: New Bug description: If a machine has a accelerometer, the screen rotation option won't be drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1836026/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836026] [NEW] There is no the screen rotation option in Settings with sensor LNG2DM
You have been subscribed to a public bug: If a machine has a accelerometer, the screen rotation option won't be drawn in Settings. But, we cannot read the accelerometer raw data from the sensor LNG2DM. The value always is 0 in in_accel_x_raw, in_accel_y_raw and in_accel_y_raw. Upstream bug: https://bugzilla.kernel.org/show_bug.cgi?id=200775 ** Affects: linux (Ubuntu) Importance: Undecided Status: New -- There is no the screen rotation option in Settings with sensor LNG2DM https://bugs.launchpad.net/bugs/1836026 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 1767992] Re: Linux md raid-10 freezes during resync
Hi everyone, I was just curious if anyone's had a chance to test out Kai-Heng's test kernel from comment #8? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767992 Title: Linux md raid-10 freezes during resync Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: I'm trying to setup a few nodes with software raid-10. When array is created and resync is running i'm trying to install a few packages and frequently system stops responding, resync process stops, and I'm getting following errors in the kernel log. This looks like a deadlock for me. I had this problem in both 18.04 and 16.04. Reboot is the only way to fix the node. [ 2659.317256] INFO: task kworker/u24:13:343 blocked for more than 120 seconds. [ 2659.317313] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317350] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317401] kworker/u24:13 D0 343 2 0x8000 [ 2659.317414] Workqueue: writeback wb_workfn (flush-9:1) [ 2659.317417] Call Trace: [ 2659.317430] __schedule+0x297/0x8b0 [ 2659.317435] schedule+0x2c/0x80 [ 2659.317443] wait_barrier+0x146/0x1a0 [raid10] [ 2659.317449] ? wait_woken+0x80/0x80 [ 2659.317454] raid10_write_request+0x77/0x950 [raid10] [ 2659.317459] ? r10bio_pool_alloc+0x24/0x30 [raid10] [ 2659.317465] ? mempool_alloc+0x71/0x190 [ 2659.317469] ? ___slab_alloc+0x20a/0x4b0 [ 2659.317475] ? md_write_start+0xc8/0x200 [ 2659.317480] ? mempool_alloc_slab+0x15/0x20 [ 2659.317484] raid10_make_request+0xcc/0x140 [raid10] [ 2659.317489] md_handle_request+0x126/0x1a0 [ 2659.317494] md_make_request+0x6b/0x150 [ 2659.317501] generic_make_request+0x124/0x300 [ 2659.317506] submit_bio+0x73/0x150 [ 2659.317510] ? submit_bio+0x73/0x150 [ 2659.317579] xfs_submit_ioend+0x87/0x1c0 [xfs] [ 2659.317626] xfs_do_writepage+0x377/0x6a0 [xfs] [ 2659.317632] write_cache_pages+0x20c/0x4e0 [ 2659.317674] ? xfs_vm_writepages+0xf0/0xf0 [xfs] [ 2659.317682] ? intel_pstate_update_pstate+0x40/0x40 [ 2659.317687] ? update_load_avg+0x5c5/0x6e0 [ 2659.317727] xfs_vm_writepages+0xbe/0xf0 [xfs] [ 2659.317732] do_writepages+0x4b/0xe0 [ 2659.317738] ? check_preempt_curr+0x83/0x90 [ 2659.317742] ? ttwu_do_wakeup+0x1e/0x150 [ 2659.317746] __writeback_single_inode+0x45/0x340 [ 2659.317749] ? __writeback_single_inode+0x45/0x340 [ 2659.317752] writeback_sb_inodes+0x1e1/0x510 [ 2659.317756] __writeback_inodes_wb+0x67/0xb0 [ 2659.317759] wb_writeback+0x271/0x300 [ 2659.317764] wb_workfn+0x180/0x410 [ 2659.317766] ? wb_workfn+0x180/0x410 [ 2659.317773] process_one_work+0x1de/0x410 [ 2659.317776] worker_thread+0x32/0x410 [ 2659.317781] kthread+0x121/0x140 [ 2659.317784] ? process_one_work+0x410/0x410 [ 2659.317788] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2659.317793] ? do_syscall_64+0x73/0x130 [ 2659.317797] ? SyS_exit_group+0x14/0x20 [ 2659.317801] ret_from_fork+0x35/0x40 [ 2659.317806] INFO: task md1_resync:429 blocked for more than 120 seconds. [ 2659.317853] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317940] md1_resync D0 429 2 0x8000 [ 2659.317943] Call Trace: [ 2659.317949] __schedule+0x297/0x8b0 [ 2659.317954] schedule+0x2c/0x80 [ 2659.317959] raise_barrier+0xa1/0x1a0 [raid10] [ 2659.317963] ? wait_woken+0x80/0x80 [ 2659.317968] raid10_sync_request+0x205/0x1f10 [raid10] [ 2659.317975] ? find_next_bit+0xb/0x10 [ 2659.317980] ? cpumask_next+0x1b/0x20 [ 2659.317985] ? is_mddev_idle+0x92/0xf4 [ 2659.317990] md_do_sync+0x8ca/0xf10 [ 2659.317994] ? wait_woken+0x80/0x80 [ 2659.318000] md_thread+0x129/0x170 [ 2659.318004] ? mddev_put+0x140/0x140 [ 2659.318007] ? md_thread+0x129/0x170 [ 2659.318012] kthread+0x121/0x140 [ 2659.318015] ? find_pers+0x70/0x70 [ 2659.318019] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2659.318023] ret_from_fork+0x35/0x40 [ 2659.318031] INFO: task xfsaild/md1p1:701 blocked for more than 120 seconds. [ 2659.318077] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.318113] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.318164] xfsaild/md1p1 D0 701 2 0x8000 [ 2659.318167] Call Trace: [ 2659.318172] __schedule+0x297/0x8b0 [ 2659.318177] ? mempool_alloc_slab+0x15/0x20 [ 2659.318181] schedule+0x2c/0x80 [ 2659.318186] wait_barrier+0x146/0x1a0 [raid10] [ 2659.318189] ? wait_woken+0x80/0x80 [ 2659.318194] raid10_write_request+0x77/0x950 [raid10] [ 2659.318198] ? r10bio_pool_alloc+0x24/0x30 [raid10] [ 2659.318202] ? mempool_alloc+0x71/0x190 [ 2659.318206] ?
[Kernel-packages] [Bug 1835436] Re: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Testing phase-changed: Wednesday, 10. July 2019 16:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835436 Title: linux-azure: 4.18.0-1025.27~18.04.1 -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: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Testing phase-changed: Wednesday, 10. July 2019 16:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836045] Re: ftbfs: gnat cross targeting powerpc
comparing the source trees of 5.0 and 5.2, it looks like all architectures except powerpc were updated (fgrep -r SO_RCVTIMEO). So this is a blocker for the powerpc cross compilers, which we need to build some firmware. ** Also affects: linux (Ubuntu) Importance: Undecided Status: New ** Changed in: linux (Ubuntu) Status: New => Confirmed ** Changed in: linux (Ubuntu) Importance: Undecided => High ** Tags added: rls-ee-incoming -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836045 Title: ftbfs: gnat cross targeting powerpc Status in gcc-8-cross package in Ubuntu: Confirmed Status in gcc-9-cross package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: both seen with gcc-8-cross and gcc-9-cross (search the build logs for "unfinished": /<>/gcc/build/./gcc/xgcc -B/<>/gcc/build/./gcc/ -B/usr/powerpc-linux-gnu/bin/ -B/usr/powerpc-li nux-gnu/lib/ -isystem /usr/powerpc-linux-gnu/include -isystem /usr/powerpc-linux-gnu/sys-include -isystem /< >/gcc/build/sys-include-c -g -O2 -W -Wall -gnatpg -nostdinc -gnatn a-direct.adb -o a-direct.o a-direct.adb:734:27: "NAME_MAX" is undefined a-direct.adb:743:28: "SIZEOF_struct_dirent_alloc" is undefined a-direct.adb:1210:24: "ENOENT" is undefined s-filatt.ads:62:18: "SIZEOF_struct_file_attributes" not declared in "OS_Constants" s-oscons.ads:50:26: "Target_OS" is undefined s-oscons.ads:54:01: (style) multiple blank lines s-oscons.ads:59:01: (style) multiple blank lines s-oscons.ads:64:01: (style) multiple blank lines s-oscons.ads:69:01: (style) multiple blank lines s-oscons.ads:74:01: (style) multiple blank lines s-oscons.ads:79:01: (style) multiple blank lines s-oscons.ads:86:01: (style) multiple blank lines s-oscons.ads:91:01: (style) multiple blank lines s-oscons.ads:96:01: (style) multiple blank lines s-oscons.ads:101:01: (style) multiple blank lines s-oscons.ads:106:01: (style) multiple blank lines s-oscons.ads:111:01: (style) multiple blank lines s-oscons.ads:116:01: (style) multiple blank lines s-oscons.ads:121:01: (style) multiple blank lines s-oscons.ads:126:01: (style) multiple blank lines s-oscons.ads:131:01: (style) multiple blank lines s-oscons.ads:136:01: (style) multiple blank lines s-oscons.ads:147:01: (style) multiple blank lines s-oscons.ads:166:01: (style) multiple blank lines s-oscons.ads:173:01: (style) multiple blank lines s-oscons.ads:176:01: (style) multiple blank lines s-oscons.ads:181:01: (style) multiple blank lines make[9]: *** [../gcc-interface/Makefile:299: a-direct.o] Error 1 make[9]: Leaving directory '/<>/gcc/build/gcc/ada/rts' make[8]: *** [gcc-interface/Makefile:623: gnatlib] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gcc-8-cross/+bug/1836045/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1767992] Re: Linux md raid-10 freezes during resync
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => In Progress ** Changed in: linux (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: linux (Ubuntu Bionic) Assignee: (unassigned) => Connor Kuehl (connork) -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1767992 Title: Linux md raid-10 freezes during resync Status in linux package in Ubuntu: Confirmed Status in linux source package in Bionic: In Progress Bug description: I'm trying to setup a few nodes with software raid-10. When array is created and resync is running i'm trying to install a few packages and frequently system stops responding, resync process stops, and I'm getting following errors in the kernel log. This looks like a deadlock for me. I had this problem in both 18.04 and 16.04. Reboot is the only way to fix the node. [ 2659.317256] INFO: task kworker/u24:13:343 blocked for more than 120 seconds. [ 2659.317313] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317350] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317401] kworker/u24:13 D0 343 2 0x8000 [ 2659.317414] Workqueue: writeback wb_workfn (flush-9:1) [ 2659.317417] Call Trace: [ 2659.317430] __schedule+0x297/0x8b0 [ 2659.317435] schedule+0x2c/0x80 [ 2659.317443] wait_barrier+0x146/0x1a0 [raid10] [ 2659.317449] ? wait_woken+0x80/0x80 [ 2659.317454] raid10_write_request+0x77/0x950 [raid10] [ 2659.317459] ? r10bio_pool_alloc+0x24/0x30 [raid10] [ 2659.317465] ? mempool_alloc+0x71/0x190 [ 2659.317469] ? ___slab_alloc+0x20a/0x4b0 [ 2659.317475] ? md_write_start+0xc8/0x200 [ 2659.317480] ? mempool_alloc_slab+0x15/0x20 [ 2659.317484] raid10_make_request+0xcc/0x140 [raid10] [ 2659.317489] md_handle_request+0x126/0x1a0 [ 2659.317494] md_make_request+0x6b/0x150 [ 2659.317501] generic_make_request+0x124/0x300 [ 2659.317506] submit_bio+0x73/0x150 [ 2659.317510] ? submit_bio+0x73/0x150 [ 2659.317579] xfs_submit_ioend+0x87/0x1c0 [xfs] [ 2659.317626] xfs_do_writepage+0x377/0x6a0 [xfs] [ 2659.317632] write_cache_pages+0x20c/0x4e0 [ 2659.317674] ? xfs_vm_writepages+0xf0/0xf0 [xfs] [ 2659.317682] ? intel_pstate_update_pstate+0x40/0x40 [ 2659.317687] ? update_load_avg+0x5c5/0x6e0 [ 2659.317727] xfs_vm_writepages+0xbe/0xf0 [xfs] [ 2659.317732] do_writepages+0x4b/0xe0 [ 2659.317738] ? check_preempt_curr+0x83/0x90 [ 2659.317742] ? ttwu_do_wakeup+0x1e/0x150 [ 2659.317746] __writeback_single_inode+0x45/0x340 [ 2659.317749] ? __writeback_single_inode+0x45/0x340 [ 2659.317752] writeback_sb_inodes+0x1e1/0x510 [ 2659.317756] __writeback_inodes_wb+0x67/0xb0 [ 2659.317759] wb_writeback+0x271/0x300 [ 2659.317764] wb_workfn+0x180/0x410 [ 2659.317766] ? wb_workfn+0x180/0x410 [ 2659.317773] process_one_work+0x1de/0x410 [ 2659.317776] worker_thread+0x32/0x410 [ 2659.317781] kthread+0x121/0x140 [ 2659.317784] ? process_one_work+0x410/0x410 [ 2659.317788] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2659.317793] ? do_syscall_64+0x73/0x130 [ 2659.317797] ? SyS_exit_group+0x14/0x20 [ 2659.317801] ret_from_fork+0x35/0x40 [ 2659.317806] INFO: task md1_resync:429 blocked for more than 120 seconds. [ 2659.317853] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.317889] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.317940] md1_resync D0 429 2 0x8000 [ 2659.317943] Call Trace: [ 2659.317949] __schedule+0x297/0x8b0 [ 2659.317954] schedule+0x2c/0x80 [ 2659.317959] raise_barrier+0xa1/0x1a0 [raid10] [ 2659.317963] ? wait_woken+0x80/0x80 [ 2659.317968] raid10_sync_request+0x205/0x1f10 [raid10] [ 2659.317975] ? find_next_bit+0xb/0x10 [ 2659.317980] ? cpumask_next+0x1b/0x20 [ 2659.317985] ? is_mddev_idle+0x92/0xf4 [ 2659.317990] md_do_sync+0x8ca/0xf10 [ 2659.317994] ? wait_woken+0x80/0x80 [ 2659.318000] md_thread+0x129/0x170 [ 2659.318004] ? mddev_put+0x140/0x140 [ 2659.318007] ? md_thread+0x129/0x170 [ 2659.318012] kthread+0x121/0x140 [ 2659.318015] ? find_pers+0x70/0x70 [ 2659.318019] ? kthread_create_worker_on_cpu+0x70/0x70 [ 2659.318023] ret_from_fork+0x35/0x40 [ 2659.318031] INFO: task xfsaild/md1p1:701 blocked for more than 120 seconds. [ 2659.318077] Not tainted 4.15.0-20-generic #21-Ubuntu [ 2659.318113] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message. [ 2659.318164] xfsaild/md1p1 D0 701 2 0x8000 [ 2659.318167] Call Trace: [ 2659.318172] __schedule+0x297/0x8b0 [ 2659.318177] ? mempool_alloc_slab+0x15/0x20 [ 2659.318181] schedule+0x2c/0x80 [ 2659.318186] wait_barrier+0x146/0x1a0 [raid10] [ 2659.318189] ?
[Kernel-packages] [Bug 1834926] Re: linux-oem: 4.15.0-1046.51 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: In Progress => Incomplete ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 10. July 2019 15:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: - automated-testing: Ongoing -- testing in progress + automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1834926 Title: linux-oem: 4.15.0-1046.51 -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 verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 10. July 2019 15:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Stalled -- testing FAILED certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 - phase: Promote to Proposed - phase-changed: Wednesday, 10. July 2019 14:50 UTC + phase: Signoff + phase-changed: Wednesday, 10. July 2019 16:46 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror - sync + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: 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 stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 phase: Signoff phase-changed: Wednesday, 10. July 2019 16:46 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 - phase: Promote to Proposed - phase-changed: Wednesday, 10. July 2019 13:07 UTC + phase: Testing + phase-changed: Wednesday, 10. July 2019 16:18 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835436 Title: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Testing phase-changed: Wednesday, 10. July 2019 16:18 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834950] Re: linux-azure: 4.15.0-1051.56 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/stakeholder-signoff Status: New => Confirmed ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834948 (trusty/linux-azure) derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Promote to Proposed - phase-changed: Wednesday, 10. July 2019 13:13 UTC + phase: Testing + phase-changed: Wednesday, 10. July 2019 16:13 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + stakeholder-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834950 Title: linux-azure: 4.15.0-1051.56 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: Confirmed Status in Kernel SRU Workflow security-signoff series: In Progress Status in Kernel SRU Workflow stakeholder-signoff series: Confirmed Status in Kernel SRU Workflow verification-testing series: Confirmed Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Xenial: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow backports: bug 1834948 (trusty/linux-azure) derivatives: bug 1834945 (azure-kernel), bug 1834946 (linux-azure-edge) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 10. July 2019 16:13 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff stakeholder-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834950/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834926] Re: linux-oem: 4.15.0-1046.51 -proposed tracker
** Changed in: kernel-sru-workflow/automated-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/certification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/promote-to-proposed Status: Fix Committed => Fix Released ** Changed in: kernel-sru-workflow/regression-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/security-signoff Status: New => In Progress ** Changed in: kernel-sru-workflow/verification-testing Status: New => Confirmed ** Changed in: kernel-sru-workflow/automated-testing Status: Confirmed => In Progress ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 - phase: Promote to Proposed - phase-changed: Tuesday, 09. July 2019 20:59 UTC + phase: Testing + phase-changed: Wednesday, 10. July 2019 15:40 UTC + proposed-announcement-sent: true + proposed-testing-requested: true reason: - promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync + automated-testing: Ongoing -- testing in progress + certification-testing: Ongoing -- testing in progress + regression-testing: Ongoing -- testing in progress + security-signoff: Pending -- waiting for signoff + verification-testing: Ongoing -- testing in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-oem in Ubuntu. https://bugs.launchpad.net/bugs/1834926 Title: linux-oem: 4.15.0-1046.51 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: In Progress Status in Kernel SRU Workflow certification-testing series: Confirmed Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow 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 verification-testing series: Confirmed Status in linux-oem package in Ubuntu: Invalid Status in linux-oem source package in Bionic: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834954 phase: Testing phase-changed: Wednesday, 10. July 2019 15:40 UTC proposed-announcement-sent: true proposed-testing-requested: true reason: automated-testing: Ongoing -- testing in progress certification-testing: Ongoing -- testing in progress regression-testing: Ongoing -- testing in progress security-signoff: Pending -- waiting for signoff verification-testing: Ongoing -- testing in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834926/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Changed in: kernel-sru-workflow/promote-signing-to-proposed Status: In Progress => Fix Committed ** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 phase: Promote to Proposed phase-changed: Wednesday, 10. July 2019 14:50 UTC reason: - promote-signing-to-proposed: Ongoing -- review in progress + promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror + sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: Fix Committed 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: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 phase: Promote to Proposed phase-changed: Wednesday, 10. July 2019 14:50 UTC reason: promote-signing-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1835436] Re: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Promote to Proposed phase-changed: Wednesday, 10. July 2019 13:07 UTC reason: - promote-to-proposed: Pending -- packages copied to Proposed signed:queued + promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1835436 Title: linux-azure: 4.18.0-1025.27~18.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: New Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-to-proposed series: Fix Committed Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Bionic: Confirmed Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow derivatives: bug 1834885 (azure-kernel) -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1835438 phase: Promote to Proposed phase-changed: Wednesday, 10. July 2019 13:07 UTC reason: promote-to-proposed: Ongoing -- packages waiting in -proposed for mirror sync variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1835436/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1820530] Re: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit
** Patch added: "0002-UBUNTU-fix-missing-modules.patch" https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+attachment/5276122/+files/0002-UBUNTU-fix-missing-modules.patch -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1820530 Title: Add arm64 CONFIG_ARCH_MESON=y and related configs Edit Status in linux package in Ubuntu: Expired Bug description: Hi, Could CONFIG_ARCH_MESON=y and related configs be enabled like the armhf counterpart ? This will follow the debian kernel config. Here is the list of config that should be enabled to have optimal platform support: CONFIG_ARCH_MESON=y CONFIG_MESON_SM=y CONFIG_DWMAC_MESON=m CONFIG_MESON_GXL_PHY=m CONFIG_SERIAL_MESON=y CONFIG_SERIAL_MESON_CONSOLE=y CONFIG_HW_RANDOM_MESON=m CONFIG_I2C_MESON=m CONFIG_SPI_MESON_SPICC=m CONFIG_SPI_MESON_SPIFC=m CONFIG_PINCTRL_MESON=y CONFIG_PINCTRL_MESON_GXBB=y CONFIG_PINCTRL_MESON_GXL=y CONFIG_PINCTRL_MESON_AXG=y CONFIG_PINCTRL_MESON_AXG_PMX=y CONFIG_PINCTRL_MESON_G12A=y CONFIG_MESON_GXBB_WATCHDOG=m CONFIG_IR_MESON=m CONFIG_VIDEO_MESON_AO_CEC=m CONFIG_DRM_MESON=m CONFIG_DRM_MESON_DW_HDMI=m CONFIG_MMC_MESON_GX=m CONFIG_MESON_CANVAS=m CONFIG_MESON_GX_SOCINFO=y CONFIG_MESON_GX_PM_DOMAINS=y CONFIG_MESON_SARADC=m CONFIG_PWM_MESON=m CONFIG_MESON_IRQ_GPIO=y CONFIG_RESET_MESON=m CONFIG_PHY_MESON_GXL_USB2=m CONFIG_PHY_MESON_GXL_USB3=m To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1820530/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1834948] Re: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker
** Description changed: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 - phase: Ready for Promote to Proposed - phase-changed: Wednesday, 10. July 2019 14:45 UTC + phase: Promote to Proposed + phase-changed: Wednesday, 10. July 2019 14:50 UTC reason: - promote-signing-to-proposed: Pending -- ready for review + promote-signing-to-proposed: Ongoing -- review in progress variant: debs -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-azure in Ubuntu. https://bugs.launchpad.net/bugs/1834948 Title: linux-azure: 4.15.0-1051.56~14.04.1 -proposed tracker Status in Kernel SRU Workflow: In Progress Status in Kernel SRU Workflow automated-testing series: Invalid Status in Kernel SRU Workflow certification-testing series: Invalid Status in Kernel SRU Workflow prepare-package series: Fix Released Status in Kernel SRU Workflow prepare-package-meta series: Fix Released Status in Kernel SRU Workflow prepare-package-signed series: Fix Released Status in Kernel SRU Workflow promote-signing-to-proposed series: In Progress Status in Kernel SRU Workflow promote-to-proposed series: Fix Released Status in Kernel SRU Workflow promote-to-security series: New Status in Kernel SRU Workflow promote-to-updates series: New Status in Kernel SRU Workflow regression-testing series: New Status in Kernel SRU Workflow security-signoff series: New Status in Kernel SRU Workflow stakeholder-signoff series: New Status in Kernel SRU Workflow verification-testing series: New Status in linux-azure package in Ubuntu: Invalid Status in linux-azure source package in Trusty: New Bug description: This bug will contain status and test results related to a kernel source (or snap) as stated in the title. For an explanation of the tasks and the associated workflow see: https://wiki.ubuntu.com/Kernel/kernel-sru-workflow -- swm properties -- boot-testing-requested: true kernel-stable-master-bug: 1834950 phase: Promote to Proposed phase-changed: Wednesday, 10. July 2019 14:50 UTC reason: promote-signing-to-proposed: Ongoing -- review in progress variant: debs To manage notifications about this bug go to: https://bugs.launchpad.net/kernel-sru-workflow/+bug/1834948/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
[Kernel-packages] [Bug 1836064] Re: linux-5.2 (?) breaks the c-t-b builds
no logs missing ** Changed in: linux (Ubuntu) Status: Incomplete => Confirmed ** Changed in: glibc (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1836064 Title: linux-5.2 (?) breaks the c-t-b builds Status in glibc package in Ubuntu: Confirmed Status in linux package in Ubuntu: Confirmed Bug description: as seen in https://launchpad.net/ubuntu/+source/cross-toolchain-base-ports/30ubuntu2/+build/17249410 the c-t-b-ports package ftbfs: /bin/bash ../scripts/move-if-change /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.T /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.h touch /<>/glibc-2.29/build-tree/alpha-libc/gnu/lib-names.stmp if test -r /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new; then mv -f /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h.new /<>/glibc-2.29/build-tree/alpha-libc/csu/abi-tag.h; \ else echo >&2 'This configuration not matched in ../abi-tags'; exit 1; fi In file included from :1: ../sysdeps/unix/sysv/linux/alpha/sysdep.h:54: error: "__NR_osf_shmat" redefined [-Werror] #define __NR_osf_shmat 209 In file included from ../sysdeps/unix/sysv/linux/sys/syscall.h:24, from ../sysdeps/unix/sysdep.h:20, from ../sysdeps/unix/alpha/sysdep.h:19, from ../sysdeps/unix/sysv/linux/alpha/sysdep.h:29, from :1: /<>/glibc-2.29/debian/include/asm/unistd.h:8: note: this is the location of the previous definition #define __NR_osf_shmat __NR_shmat cc1: all warnings being treated as errors Traceback (most recent call last): File "../scripts/gen-as-const.py", line 120, in main() File "../scripts/gen-as-const.py", line 116, in main consts = glibcextract.compute_c_consts(sym_data, args.cc) File "/<>/glibc-2.29/scripts/glibcextract.py", line 62, in compute_c_consts subprocess.check_call(cmd, shell=True) File "/usr/lib/python3.7/subprocess.py", line 347, in check_call raise CalledProcessError(retcode, cmd) subprocess.CalledProcessError: Command 'alpha-linux-gnu-gcc-8 -no-pie -fno-PIE -std=gnu11 -fgnu89-inline -pipe -O2 -g -Wall -Wwrite-strings -Wundef -Werror -fmerge-all-constants -frounding-math -fno-stack-protector -Wstrict-prototypes -Wold-style-definition -fmath-errno -mlong-double-128 -mieee -mfp-rounding-mode=d-ftls-model=initial-exec -U_FORTIFY_SOURCE -isystem /<>/glibc-2.29/debian/include -I../include -I/<>/glibc-2.29/build-tree/alpha-libc/csu -I/<>/glibc-2.29/build-tree/alpha-libc -I../sysdeps/unix/sysv/linux/alpha/alpha -I../sysdeps/unix/sysv/linux/alpha/fpu -I../sysdeps/alpha/fpu -I../sysdeps/unix/sysv/linux/alpha -I../sysdeps/alpha/nptl -I../sysdeps/unix/sysv/linux/wordsize-64 -I../sysdeps/ieee754/ldbl-64-128 -I../sysdeps/ieee754/ldbl-opt -I../sysdeps/unix/sysv/linux/include -I../sysdeps/unix/sysv/linux -I../sysdeps/nptl -I../sysdeps/pthread -I../sysdeps/gnu -I../sysdeps/unix/inet -I../sysdeps/unix/sysv -I../sysdeps/unix/alpha -I../sysdeps/unix -I../sysdeps/posix -I../sysdeps/alpha -I../sysdeps/wordsize-64 -I../sysdeps/ieee754/ldbl-128 -I../sysdeps/ieee754/dbl-64/wordsize-64 -I../sysdeps/ieee754/dbl-64 -I../sysdeps/ieee754/flt-32 -I../sysdeps/ieee754 -I../sysdeps/generic -I.. -I../libio -I. -nostdinc -isystem /<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include -isystem /<>/debian/tmp.alpha/usr/bin/../lib/gcc-cross/alpha-linux-gnu/8/include-fixed -isystem /<>/glibc-2.29/debian/include -D_LIBC_REENTRANT -include /<>/glibc-2.29/build-tree/alpha-libc/libc-modules.h -DMODULE_NAME=libc -include ../include/libc-symbols.h -DTOP_NAMESPACE=glibc -DGEN_AS_CONST_HEADERS-MD -MP -MF /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.dT -MT '/<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h.d /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h' -S -o /tmp/tmpq06grbcg/test.s -x c - < /tmp/tmpq06grbcg/test.c' returned non-zero exit status 1. make[4]: *** [../Makerules:271: /<>/glibc-2.29/build-tree/alpha-libc/tcb-offsets.h] Error 1 make[4]: Leaving directory '/<>/glibc-2.29/csu' make[3]: *** [Makefile:275: csu/subdir_lib] Error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glibc/+bug/1836064/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
