[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160422064633.GA8012@kroah.com>
Date: Fri, 22 Apr 2016 15:46:33 +0900
From: Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To: Philip Müller <philm@...jaro.org>
Cc: Sasha Levin <sasha.levin@...cle.com>, manjaro-dev@...jaro.org,
"Linux-Kernel@...r. Kernel. Org" <linux-kernel@...r.kernel.org>
Subject: Re: [regression] linux318, linux41 - kernel stack is corrupted
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
Powered by blists - more mailing lists