public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	Andrea Arcangeli <aarcange@redhat.com>,
	Hugh Dickins <hughd@google.com>,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: oops in copy_page_rep()
Date: Sun, 6 Jan 2013 19:37:18 -0500	[thread overview]
Message-ID: <20130107003718.GA1336@redhat.com> (raw)
In-Reply-To: <CA+55aFwkP=nA32pBO0gNm51nPxqWiq1e1zWzGEJoVQ1gP=CgDQ@mail.gmail.com>

On Sat, Jan 05, 2013 at 07:57:39PM -0800, Linus Torvalds wrote:
 > Adding more people in case somebody else has any idea. Anybody?
 > 
 > On Sat, Jan 5, 2013 at 7:22 AM, Dave Jones <davej@redhat.com> wrote:
 > > I have no idea what happened here, but this is the first time I've seen this one.
 > > This was running a tree pulled yesterday afternoon.
 > >
 > > BUG: unable to handle kernel paging request at ffff880100201000
 > 
 > This is %rsi, which is the source for the page copy:
 > 
 >   copy_user_highpage()->
 >     copy_user_page()->
 >       copy_page()->
 >         copy_page_rep
 > 
 > I don't know exactly which copy_user_highpage() case this is from, the
 > call trace implies this *could* be a hugepage, and those functions do
 > copy pages individually in a loop too.

investigating the huge page theory a little further I'm a bit confused.
The kernel on that machine has THP enabled, and the cpu supports it (an old amd64), but..

$ cat /sys/kernel/mm/hugepages/hugepages-2048kB/*
0
0
0
0
0
0

I was expecting at least one of those to be non-zero.

/sys/kernel/mm/transparent_hugepage/khugepaged/full_scans and pages_collapsed
are both non-zero, so it's been busy doing _something_.

Is this expected behaviour ?

	Dave


  reply	other threads:[~2013-01-07  0:37 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-05 15:22 oops in copy_page_rep() Dave Jones
2013-01-06  3:57 ` Linus Torvalds
2013-01-07  0:37   ` Dave Jones [this message]
2013-01-07  3:38     ` Hugh Dickins
2013-01-06 11:55 ` Hillf Danton
2013-01-06 16:10   ` Dave Jones
2013-01-06 19:06   ` Hugh Dickins
2013-01-07 12:24     ` Hillf Danton
2013-01-07 17:34       ` Linus Torvalds
2013-01-08 13:04         ` Hillf Danton
2013-01-08 15:37           ` Linus Torvalds
2013-01-08 16:31             ` Kirill A. Shutemov
2013-01-08 16:52               ` Linus Torvalds
2013-01-08 17:30                 ` Kirill A. Shutemov
2013-01-08 17:38                   ` Linus Torvalds
2013-01-08 17:49                   ` Andrea Arcangeli
2013-01-08 18:03                     ` Kirill A. Shutemov
2013-01-11  7:50                     ` Simon Jeons
2013-01-11 14:01                       ` Andrea Arcangeli
2013-01-08 17:37                 ` Andrea Arcangeli
2013-01-08 17:51                   ` Linus Torvalds
2013-01-08 18:03                     ` Andrea Arcangeli
2013-01-08 18:21                       ` Linus Torvalds
2013-01-09 11:38                         ` Hillf Danton
2013-01-09  4:23                   ` Hugh Dickins
2013-01-09 11:44                 ` Mel Gorman

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=20130107003718.GA1336@redhat.com \
    --to=davej@redhat.com \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=hughd@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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