I tried mainline kernel 4.20-rc2, 4.18, 4.17, 4.16 and 4.15. They all passed a 50 run test. To validate when the issue is introduced, I installed several Ubuntu kernel packages and address the issue/regression happens between 4.15.0-34 and 4.15.0-36.
Finished the kernel bisect and probably found the first bad commit. $ git bisect log # bad: [fd01374000c83b59d3ce234fbb970cb91404bd42] UBUNTU: Ubuntu-4.15.0-36.39 # good: [ffaad0a9f46742f6d71af975a6a061ffe6963aca] UBUNTU: Ubuntu-4.15.0-34.37 git bisect start 'Ubuntu-4.15.0-36.39' 'Ubuntu-4.15.0-34.37' # good: [003ae88ae88d48643e71dc69c18d4eda598339d5] Revert "UBUNTU: SAUCE: net: hns3: Fix for VF mailbox receiving unknown message" git bisect good 003ae88ae88d48643e71dc69c18d4eda598339d5 # good: [d3d4b20788eee72dcb1ed5ace7dbee6aafbe65cf] net: hns3: Fix for mac pause not disable in pfc mode git bisect good d3d4b20788eee72dcb1ed5ace7dbee6aafbe65cf # good: [8e499f213175b65bcc08a3c685ea6717e7668cec] arm64: ssbd: Introduce thread flag to control userspace mitigation git bisect good 8e499f213175b65bcc08a3c685ea6717e7668cec # good: [11cdaf61c1986ea682398b48e238fd915393b2e6] KVM: PPC: Check if IOMMU page is contained in the pinned physical page git bisect good 11cdaf61c1986ea682398b48e238fd915393b2e6 # good: [db6800337d38a5b2adbaa78fcb2c299362222e1d] s390: fix br_r1_trampoline for machines without exrl git bisect good db6800337d38a5b2adbaa78fcb2c299362222e1d # good: [f1f016ed54582502d59de991ddbecfe2373722c0] x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ git bisect good f1f016ed54582502d59de991ddbecfe2373722c0 # good: [f1f016ed54582502d59de991ddbecfe2373722c0] x86/speculation/l1tf: Increase l1tf memory limit for Nehalem+ git bisect good f1f016ed54582502d59de991ddbecfe2373722c0 # bad: [cb3b0751997c8bd45c76a7401e2edb019cdaaab3] UBUNTU: Start new release git bisect bad cb3b0751997c8bd45c76a7401e2edb019cdaaab3 # bad: [cb3b0751997c8bd45c76a7401e2edb019cdaaab3] UBUNTU: Start new release git bisect bad cb3b0751997c8bd45c76a7401e2edb019cdaaab3 # bad: [d5bad4136d14cda66cb7c06b10b80c64ae695c78] UBUNTU: Ubuntu-4.15.0-35.38 git bisect bad d5bad4136d14cda66cb7c06b10b80c64ae695c78 # bad: [876dcb5f4576934a1a11b091b40ce548f048340e] UBUNTU: SAUCE: vfio -- release device lock before userspace requests git bisect bad 876dcb5f4576934a1a11b091b40ce548f048340e # first bad commit: [876dcb5f4576934a1a11b091b40ce548f048340e] UBUNTU: SAUCE: vfio -- release device lock before userspace requests -- 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/1803942 Title: System randomly hangs during suspend when mei_wdt is loaded Status in linux package in Ubuntu: Confirmed Bug description: Problem description: System randomly hangs during suspend when mei_wdt is loaded. Platform: Intel Dawson Canyon I5 (NUC7i5DNHE) and I7 (NUC7i7DNHE) Test procedure: 1. Install Ubuntu 18.04 and do apt full-upgrade 2. Enable mei_wdt: $ sudo modprobe mei_wdt 3. Do system S3 test: $ sudo systemctl suspend or $ sudo rtcwake -v -m mem -s 15 4. Afterward, I noticed that somehow system will hang during suspend/resume. Expect result: Suspend/resume won't impact system. Actual result: System will hang during S3 test. Additional info: - BIOS version: V57 - Another i3 platform (NUC7i3DNHNC) doesn't have this issue. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1803942/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
