From: "Sebastian M. Bobrecki" <sebastian@bobrecki.pl>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: "Philip Müller" <philm@manjaro.org>,
"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 10:10:59 +0200 [thread overview]
Message-ID: <5719DC93.1080901@bobrecki.pl> (raw)
In-Reply-To: <20160422075549.GA6689@kroah.com>
W dniu 22.04.2016 o 09:55, Greg Kroah-Hartman pisze:
> On Fri, Apr 22, 2016 at 09:47:04AM +0200, Sebastian M. Bobrecki wrote:
>> Hi,
>>
>> I just hit the same with 4.1.22 on Gentoo. 4.1.21 are working fine.
>>
>> On 22.04.2016 at 08:46, Greg Kroah-Hartman wrote:
>>> ...
>>> 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?
>>>
>> Greg have you seen screenshots linked by Philip?
> I saw no such screenshots in the email.
They are here: https://github.com/manjaro/packages-core/issues/36
--
Sebastian M. Bobrecki
next prev parent reply other threads:[~2016-04-22 8:11 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
2016-04-22 7:47 ` Sebastian M. Bobrecki
2016-04-22 7:55 ` Greg Kroah-Hartman
2016-04-22 8:10 ` Sebastian M. Bobrecki [this message]
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=5719DC93.1080901@bobrecki.pl \
--to=sebastian@bobrecki.pl \
--cc=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).