All of lore.kernel.org
 help / color / mirror / Atom feed
From: Catalin Marinas <catalin.marinas@arm.com>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: kmemleak: Unable to handle kernel paging request
Date: Wed, 11 Jun 2014 23:00:18 +0100	[thread overview]
Message-ID: <B01EB0A1-992B-49F4-93AE-71E4BA707795@arm.com> (raw)
In-Reply-To: <CAOJe8K1TgTDX5=LdE9r6c0ami7TRa7zr0hL_uu6YpiWrsePAgQ@mail.gmail.com>

On 11 Jun 2014, at 21:04, Denis Kirjanov <kda@linux-powerpc.org> wrote:
> On 6/11/14, Catalin Marinas <catalin.marinas@arm.com> wrote:
>> On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote:
>>> I got a trace while running 3.15.0-08556-gdfb9454:
>>> 
>>> [  104.534026] Unable to handle kernel paging request for data at
>>> address 0xc00000007f000000
>> 
>> Were there any kmemleak messages prior to this, like "kmemleak
>> disabled"? There could be a race when kmemleak is disabled because of
>> some fatal (for kmemleak) error while the scanning is taking place
>> (which needs some more thinking to fix properly).
> 
> No. I checked for the similar problem and didn't find anything relevant.
> I'll try to bisect it.

Does this happen soon after boot? I guess it’s the first scan
(scheduled at around 1min after boot). Something seems to be telling
kmemleak that there is a valid memory block at 0xc00000007f000000.

Catalin

WARNING: multiple messages have this Message-ID (diff)
From: Catalin Marinas <catalin.marinas@arm.com>
To: Denis Kirjanov <kda@linux-powerpc.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: Re: kmemleak: Unable to handle kernel paging request
Date: Wed, 11 Jun 2014 23:00:18 +0100	[thread overview]
Message-ID: <B01EB0A1-992B-49F4-93AE-71E4BA707795@arm.com> (raw)
In-Reply-To: <CAOJe8K1TgTDX5=LdE9r6c0ami7TRa7zr0hL_uu6YpiWrsePAgQ@mail.gmail.com>

On 11 Jun 2014, at 21:04, Denis Kirjanov <kda@linux-powerpc.org> wrote:
> On 6/11/14, Catalin Marinas <catalin.marinas@arm.com> wrote:
>> On Wed, Jun 11, 2014 at 04:13:07PM +0400, Denis Kirjanov wrote:
>>> I got a trace while running 3.15.0-08556-gdfb9454:
>>> 
>>> [  104.534026] Unable to handle kernel paging request for data at
>>> address 0xc00000007f000000
>> 
>> Were there any kmemleak messages prior to this, like "kmemleak
>> disabled"? There could be a race when kmemleak is disabled because of
>> some fatal (for kmemleak) error while the scanning is taking place
>> (which needs some more thinking to fix properly).
> 
> No. I checked for the similar problem and didn't find anything relevant.
> I'll try to bisect it.

Does this happen soon after boot? I guess it’s the first scan
(scheduled at around 1min after boot). Something seems to be telling
kmemleak that there is a valid memory block at 0xc00000007f000000.

Catalin
--
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:[~2014-06-11 22:00 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-11 12:13 kmemleak: Unable to handle kernel paging request Denis Kirjanov
2014-06-11 12:13 ` Denis Kirjanov
2014-06-11 17:38 ` Catalin Marinas
2014-06-11 17:38   ` Catalin Marinas
2014-06-11 20:04   ` Denis Kirjanov
2014-06-11 20:04     ` Denis Kirjanov
2014-06-11 22:00     ` Catalin Marinas [this message]
2014-06-11 22:00       ` Catalin Marinas
2014-06-12  7:39       ` Denis Kirjanov
2014-06-12  7:39         ` Denis Kirjanov
2014-06-12 12:00         ` Denis Kirjanov
2014-06-12 12:00           ` Denis Kirjanov
2014-06-12 13:29           ` Naoya Horiguchi
2014-06-12 14:39           ` Catalin Marinas
2014-06-12 14:39             ` Catalin Marinas
2014-06-13  7:12             ` Denis Kirjanov
2014-06-13  7:12               ` Denis Kirjanov
2014-06-13  8:56               ` Catalin Marinas
2014-06-13  8:56                 ` Catalin Marinas
2014-06-13  8:56                 ` Catalin Marinas
2014-06-13 10:26                 ` Denis Kirjanov
2014-06-13 10:26                   ` Denis Kirjanov
2014-06-13 10:26                   ` Denis Kirjanov
2014-06-16  2:40                   ` Michael Ellerman
2014-06-16  2:40                     ` Michael Ellerman
2014-06-13 21:44                 ` Benjamin Herrenschmidt
2014-06-13 21:44                   ` Benjamin Herrenschmidt
2014-06-14 12:05                   ` Catalin Marinas
2014-06-14 12:05                     ` Catalin Marinas
2014-06-14 12:05                     ` Catalin Marinas
     [not found]           ` <5399ab3b.4825e00a.60fd.5014SMTPIN_ADDED_BROKEN@mx.google.com>
2014-06-13  6:39             ` Denis Kirjanov
2014-06-13  6:39               ` Denis Kirjanov

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=B01EB0A1-992B-49F4-93AE-71E4BA707795@arm.com \
    --to=catalin.marinas@arm.com \
    --cc=kda@linux-powerpc.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.