From: "Dr. David Alan Gilbert" <dave@treblig.org>
To: Marcin Gibula <m.gibula@gmail.com>
Cc: linux-kernel@vger.kernel.org, aarcange@redhat.com
Subject: Re: 3.16.1 - general protection fault
Date: Wed, 24 Sep 2014 21:18:27 +0100 [thread overview]
Message-ID: <20140924201827.GA30643@gallifrey> (raw)
In-Reply-To: <CAGKO+35+H3MmkaN1m_PfHi0XhbRvtnSBqm3PDmOhs5YBmAZ1jg@mail.gmail.com>
* Marcin Gibula (m.gibula@gmail.com) wrote:
Hi Marcin,
> Hi,
>
> I've been playing with 3.16 kernel on my test machine as a KVM
> hypervisor and encountered the following crash twice (almost identical
> backtraces).
>
> Sep 24 09:39:31 dev4 kernel: general protection fault: 0000 [#1] SMP
<snip>
> This machine is serving as NFS client and KVM hypervisor. I'm still
> not sure how to trigger it reliably (right now, I just have to run
> ubuntu instalation in VM guest multiple times and sometimes it
> triggers).
>
> Attaching .config, slub.s and disassembled __kmalloc_node_track_caller function.
Yes, I hit something similar:
http://www.spinics.net/lists/linux-nfs/msg46047.html 'nfs: disallow duplicate pages in pgio page vectors'
http://www.spinics.net/lists/linux-nfs/msg46048.html 'nfs: can_coalesce_requests must enforce contiguity'
seem to stop the GPF's/crashes, although there's still something else
going on with a corruption I'm seeing every so often.
Dave
--
-----Open up your eyes, open up your mind, open up your code -------
/ Dr. David Alan Gilbert | Running GNU/Linux | Happy \
\ gro.gilbert @ treblig.org | | In Hex /
\ _________________________|_____ http://www.treblig.org |_______/
next prev parent reply other threads:[~2014-09-24 20:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 16:44 3.16.1 - general protection fault Marcin Gibula
2014-09-24 20:18 ` Dr. David Alan Gilbert [this message]
2014-09-30 14:50 ` Dr. David Alan Gilbert
2014-10-01 8:09 ` Marcin Gibula
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=20140924201827.GA30643@gallifrey \
--to=dave@treblig.org \
--cc=aarcange@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=m.gibula@gmail.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