[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

Markng this invalid. SOMETHING resolved it, but we never figured out what. ** Changed in: linux (Ubuntu) Status: Confirmed => Invalid -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

Re: [Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

Not yet... I've tried 4.7.0-040700 on a 64GB arm64 system with no failures. I've also tried 4.4.0-33.52 on a 32GB ARM64 system with no failures. Currently trying 4.4.0-21.37 on the 32GB system and 4.4.0-34.53 on the 64GB system. I initially saw this on 4.4.0-31.50 on both systems, so I had

[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

Do we know what change fixed the issue? commit id? -- 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/1610320 Title: stress-ng memory testing causes Arm64 system to hang Status in linux

Re: [Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

Any chance you can back to -31 (16.04.1 stock) and see if it fails there? That's where I was failing on my systems, I'll see if I can grab -34 and give that a try too) On Fri, Aug 12, 2016 at 10:59 AM, Michael Reed wrote: > I just ran this on 4.4.0-34-generic from

[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

I just ran this on 4.4.0-34-generic from the dev ppa on an arm64 system and it passed. I am re-running this now to see if it reliably passes. ubuntu@ubuntu:~$ sudo apt-cache policy canonical-certification-server canonical-certification-server: Installed: 0.28+201607151353~ubuntu16.04.1

[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

I built a v4.4.16 kernel, which can be downloaded from: http://kernel.ubuntu.com/~jsalisbury/lp1610320/v4.4.16/ Can you give that kernel a try? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu.

[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

That is good news the 4.7 kernel does not exhibit the bug. We should be able to perform a "Reverse" bisect to identify the commit that fixes the bug. We should next test the latest 4.4.16 upstream stable kernel to see if the fix was already sent to upstream stable? If 4.4.16 still has the bug,

[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

** Tags removed: kernel-key ** Tags added: kernel-da-key -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1610320 Title: stress-ng memory testing causes Arm64 system to hang Status in

[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

So running the upstream 4.7.0 kernel and had 0 failures out of 31 runs so it's pretty safe to assume that this isn't an affect upstream. ** Tags added: kernel-fixed-upstream -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in

[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

This appears to reliably happen with the bigheap test on ARM64. I've tried two systems and both lock up shortly after the bigheap test begins. This may need some input from @cking as stress-ng is his test. -- You received this bug notification because you are a member of Kernel Packages, which

[Kernel-packages] [Bug 1610320] Re: stress-ng memory testing causes Arm64 system to hang

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.7 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix