From: Matthias Kaehlcke <matthias@kaehlcke.net>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: Tree for March 30: [BUG] kmemleak page fault
Date: Thu, 2 Apr 2009 19:21:56 +0200 [thread overview]
Message-ID: <20090402172156.GD14253@traven> (raw)
In-Reply-To: <1238688515.28457.120.camel@pc1117.cambridge.arm.com>
El Thu, Apr 02, 2009 at 05:08:35PM +0100 Catalin Marinas ha dit:
> On Wed, 2009-04-01 at 11:52 +0200, Matthias Kaehlcke wrote:
> > El Wed, Apr 01, 2009 at 10:30:08AM +0100 Catalin Marinas ha dit:
> >
> > > On Mon, 2009-03-30 at 14:24 +0200, Matthias Kaehlcke wrote:
> > > > linux-next 20090330 causes the following page fault on an edb9302
> > > > (ARM) like board:
> > > [...]
> > > > the fault is reproducible and happens some seconds after having
> > > > finished the boot process. please tell me if you need more information
> > > > (like the .config, ...) in order to track this down
> > >
> > > Yes, the .config would be useful. I'm mainly interested in which slab
> > > allocator you are using. I'm testing kmemleak mainly on ARM and haven't
> > > seen any issues.
> >
> > attached is the .config for linux-next 20090401, which should be
> > roughly the same than the 20090330 one.
> >
> > some hours ago i booted the board with 20090401 and the page fault
> > didn't happen
>
> Do you still get this fault with the latest linux-next? I can't
> reproduce it on my ARM platform (I tried it with the latest mainline
> kernel as well).
still haven't tried with 20090402, but with 20090401 i didn't get the
fault
--
Matthias Kaehlcke
Embedded Linux Engineer
Barcelona
Control over the use of one's ideas really constitutes control over other
people's lives; and it is usually used to make their lives more difficult.
(Richard Stallman)
.''`.
using free software / Debian GNU/Linux | http://debian.org : :' :
`. `'`
gpg --keyserver pgp.mit.edu --recv-keys 47D8E5D4 `-
next prev parent reply other threads:[~2009-04-02 17:22 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-30 9:01 linux-next: Tree for March 30 Stephen Rothwell
2009-03-30 12:24 ` linux-next: Tree for March 30: [BUG] kmemleak page fault Matthias Kaehlcke
2009-04-01 9:30 ` Catalin Marinas
2009-04-01 9:52 ` Matthias Kaehlcke
2009-04-02 16:08 ` Catalin Marinas
2009-04-02 17:21 ` Matthias Kaehlcke [this message]
2009-03-30 18:37 ` linux-next: Tree for March 30 Rafael J. Wysocki
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=20090402172156.GD14253@traven \
--to=matthias@kaehlcke.net \
--cc=catalin.marinas@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).