The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Florin Iucha <florin@iucha.net>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Oops in dentry_iput with 2.6.22-rc2 on AMD64
Date: Mon, 28 May 2007 12:42:51 +0200	[thread overview]
Message-ID: <20070528104251.GB20591@duck.suse.cz> (raw)
In-Reply-To: <20070525040752.GB5762@iucha.net>

On Thu 24-05-07 23:07:52, Florin Iucha wrote:
> On Tue, May 22, 2007 at 11:57:11AM +0200, Jan Kara wrote:
> > > I was running a multithreaded perl application that leaks some memory
> > > so it gets to eat up a significant chunk of my 2 GB and even push a
> > > bit into swap.  I left it running before going out for a walk.
> >   Hmm, what seems suspitious is, that in R12 (which probably contains
> > the address dereferenced later) is address ffff9100... while all other
> > addresses start with ffff8100. So it seems to me it could be a 1-bit
> > flip. Care to check your memory with memtest?
> 
> I let it run overnight: 8 passes and no surprises.  This is a system
> that has been quite stable for a year and a half, except finding the
> occasional kernel bug ;)
  OK, then it might be some gamma ray hitting your memory :)

> >   Also this is a code all other people use all the time so I guess we
> > would see more reports if this was some general bug...
> 
> Haven't got any more oopses like that, either.
  Hmm, unless you'll see the oops again, it's probably undebuggable...

								Honza
-- 
Jan Kara <jack@suse.cz>
SuSE CR Labs

      reply	other threads:[~2007-05-28 10:31 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-22  4:10 Oops in dentry_iput with 2.6.22-rc2 on AMD64 Florin Iucha
2007-05-22  9:57 ` Jan Kara
2007-05-25  4:07   ` Florin Iucha
2007-05-28 10:42     ` Jan Kara [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=20070528104251.GB20591@duck.suse.cz \
    --to=jack@suse.cz \
    --cc=florin@iucha.net \
    --cc=linux-kernel@vger.kernel.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