[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-03-27 Thread Po-Hsu Lin
** Changed in: ubuntu-kernel-tests Status: Triaged => Fix Released -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B To manage

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-03-16 Thread Launchpad Bug Tracker
This bug was fixed in the package linux - 4.15.0-91.92 --- linux (4.15.0-91.92) bionic; urgency=medium * bionic/linux: 4.15.0-91.92 -proposed tracker (LP: #1865109) * CVE-2020-2732 - KVM: x86: emulate RDPID - KVM: nVMX: Don't emulate instructions in guest mode - KVM:

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-27 Thread Sean Feole
** Changed in: ubuntu-kernel-tests Status: New => Triaged -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B To manage

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-27 Thread Kleber Sacilotto de Souza
Confirmed this is now fixed with bionic/linux 4.15.0-90.91: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/amd64/l/linux/20200227_101305_5debc@/log.gz --- 10:00:50 DEBUG| [stdout] vm-segv STARTING

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-27 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Bionic) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B To

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-27 Thread Ubuntu Kernel Bot
This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed- bionic' to 'verification-done-bionic'. If the problem still exists, change the tag

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-26 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu Bionic) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B To

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-25 Thread Kleber Sacilotto de Souza
On a arm64 node we had some more useful console logs: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac /autopkgtest-bionic/bionic/arm64/l/linux/20200223_153549_99119@/log.gz [ 7400.666431] rcu_sched kthread starved for 240027 jiffies! g460241 c460240

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-25 Thread Kleber Sacilotto de Souza
** Changed in: linux (Ubuntu) Status: Incomplete => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B To manage

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-25 Thread Colin Ian King
I confirm in my testing I get a hard kernel lockup with no log output. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B To manage

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-25 Thread Kleber Sacilotto de Souza
** Also affects: linux (Ubuntu Bionic) Importance: Undecided Status: New ** Changed in: linux (Ubuntu Bionic) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-24 Thread Khaled El Mously
The offending commit appears to be: 5b9276f0312a apparmor: don't try to replace stale label in ptrace access check Which isn't surprising (it's both ptrace and apparmor related). Note however that I did not encounter the log-flooding that was seen in the ADT testing. The only symptom I

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-24 Thread Colin Ian King
** Changed in: stress-ng Assignee: Colin Ian King (colin-king) => Kleber Sacilotto de Souza (kleber-souza) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-24 Thread Colin Ian King
To reproduce (on an 8 CPU VM): sudo apt-get update && sudo apt-get dist-upgrade sudo apt-get build-dep stress-ng git clone git://kernel.ubuntu.com/cking/stress-ng cd stress-ng make sudo ./stress-ng --vm-segv 0 -t 10 -v Comment out a ptrace line and rebuild and re-run and the hang does not occur.

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-24 Thread Colin Ian King
I spoke too soon. I was able to trip this 4.15.0-89.89 but not 4.15.0-88. So this looks like a regression. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-24 Thread Colin Ian King
I can't reproduce this on the systems I'm using. Can I get access to onibi to try and reproduce this issue? ** Changed in: stress-ng Status: In Progress => Incomplete -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-24 Thread Colin Ian King
Do you have any info on the number of CPUs, memory and swap size of onibi? I can then see if I can reproduce the issue. Or better, access to onibi would be most helpful to see if I can repro this issue. ** Changed in: stress-ng Status: New => In Progress ** Changed in: stress-ng

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-24 Thread Po-Hsu Lin
BTW this test has passed on another node "kili" on 4.15.0-89.89~16.04.1 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1864063 Title: vm-segv from ubuntu_stress_smoke_test failed on B To manage

[Bug 1864063] Re: vm-segv from ubuntu_stress_smoke_test failed on B

2020-02-20 Thread Po-Hsu Lin
** Description changed: - Issue found on node onibi + Issue found on node onibi, with kernel 4.15.0-89.89/ 4.15.0-89.89~16.04.1 Reproduce rate: 2/2 on generic kernel, 2/2 on lowlatency kernel, 2/2 on X-hwe generic kernel Test hang with vm-segv: 05:58:36 DEBUG| [stdout] vm-addr PASSED