All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: "Philip Müller" <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
Date: Fri, 22 Apr 2016 15:46:33 +0900	[thread overview]
Message-ID: <20160422064633.GA8012@kroah.com> (raw)
In-Reply-To: <5403eedc-424e-d00a-cc7c-0c1c5542cae0@manjaro.org>

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

  parent reply	other threads:[~2016-04-22  6:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-22  6:17 [regression] linux318, linux41 - kernel stack is corrupted Philip Müller
2016-04-22  6:19 ` Philip Müller
2016-04-22  6:46 ` Greg Kroah-Hartman [this message]
2016-04-22  7:47   ` Sebastian M. Bobrecki
2016-04-22  7:55     ` Greg Kroah-Hartman
2016-04-22  8:10       ` Sebastian M. Bobrecki
2016-04-22  8:23         ` Greg Kroah-Hartman
2016-04-22 10:16           ` Mike Galbraith
2016-04-23  2:02             ` Sasha Levin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160422064633.GA8012@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=manjaro-dev@manjaro.org \
    --cc=philm@manjaro.org \
    --cc=sasha.levin@oracle.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.