Date: Fri, 22 Apr 2016 15:46:33 +0900
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Philip =?iso-8859-1?Q?M=FCller?= <philm@manjaro.org>
Cc: Sasha Levin <sasha.levin@oracle.com>, manjaro-dev@manjaro.org,
        "Linux-Kernel@Vger. Kernel. Org" <linux-kernel@vger.kernel.org>
Subject: Re: [regression] linux318, linux41 - kernel stack is corrupted
Message-ID: <20160422064633.GA8012@kroah.com>
References: <5403eedc-424e-d00a-cc7c-0c1c5542cae0@manjaro.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <5403eedc-424e-d00a-cc7c-0c1c5542cae0@manjaro.org>
User-Agent: Mutt/1.6.0 (2016-04-01)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 662
Lines: 19

On Fri, Apr 22, 2016 at 08:17:58AM +0200, Philip M?ller wrote:
> Hi Greg, hi Sasha,
> 
> seems I found another regression within the latest point-releases of
> 3.18 and 4.1 kernel series. We tested it on AMD and Intel CPUs so far.
> They hit the same regression. Other kernels released on that day are not
> affected. Do you guys have a clue what might been have missed here?
> 
> 3.18.30 and 4.1.21 didn't had that issue on the same hardware.

You are going to have to be a bit more specific here...
What is the oops message?  How do you reproduce this?  Does it also
happen on 4.6-rc4?

Can you run 'git bisect' to find the offending patch?

thanks,

greg k-h