linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Mel Gorman <mgorman@suse.de>
To: Alexander H <1zeeky@gmail.com>
Cc: linux-mm@kvack.org
Subject: Re: PROBLEM: kernel oops on page fault
Date: Fri, 3 May 2013 16:01:45 +0100	[thread overview]
Message-ID: <20130503150145.GA17260@suse.de> (raw)
In-Reply-To: <CAEN0ZYDaHDhNZoJuRn3ZRUCYQyaP4DLwKheh2VFO00bo==0bLg@mail.gmail.com>

On Fri, May 03, 2013 at 11:28:22AM +0200, Alexander H wrote:
> [ 2103.689560] Pid: 7640, comm: cc1plus Not tainted 3.8.11-1-ck #1
> SAMSUNG ELECTRONICS CO., LTD. N150P/N210P/N220P
> /N150P/N210P/N220P

This looks like a vendor kernel of some description. Is it reproducible
with the mainline 3.8.11 kernel?

-- 
Mel Gorman
SUSE Labs

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>

      reply	other threads:[~2013-05-03 15:01 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-03  9:28 PROBLEM: kernel oops on page fault Alexander H
2013-05-03 15:01 ` Mel Gorman [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=20130503150145.GA17260@suse.de \
    --to=mgorman@suse.de \
    --cc=1zeeky@gmail.com \
    --cc=linux-mm@kvack.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;
as well as URLs for NNTP newsgroup(s).