From: Jon Christopherson <jon@jons.org>
To: Chris Mason <clm@fb.com>,
Andrew Morton <akpm@linux-foundation.org>,
Dave Jones <dsj@fb.com>,
linux-kernel@vger.kernel.org,
Btrfs mailing list <linux-btrfs@vger.kernel.org>
Subject: Re: new oops in 4.4.0-rc4
Date: Fri, 11 Dec 2015 11:54:47 -0600 [thread overview]
Message-ID: <566B0DE7.3030406@jons.org> (raw)
In-Reply-To: <20151211153559.GD11257@ret.masoncoding.com>
On 12/11/2015 09:35 AM, Chris Mason wrote:
> On Thu, Dec 10, 2015 at 10:36:17AM -0600, Jon Christopherson wrote:
<snip>
>
> Dave Jones sent in a report about this with trinity too, I'm digging in
> today. Since you can trigger this reliably, what was the last
> known-good kernel for you?
>
> -chris
>
Hello,
My last known good kernel was from Dec 5 04:00 CST:
Linux version 4.4.0-120-generic (root@enigma.jons.org) (gcc version
5.2.1 20151124 (Ubuntu 5.2.1-1ubuntu1~14.04) ) #201512050400 SMP Sat Dec
5 03:54:25 CST 2015
I will check over the commits from then till now as well.
Regards,
Jon Christopherson
prev parent reply other threads:[~2015-12-11 17:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-10 16:36 new oops in 4.4.0-rc4 Jon Christopherson
2015-12-11 15:35 ` Chris Mason
2015-12-11 17:54 ` Jon Christopherson [this message]
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=566B0DE7.3030406@jons.org \
--to=jon@jons.org \
--cc=akpm@linux-foundation.org \
--cc=clm@fb.com \
--cc=dsj@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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