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 ;)
> 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.
Thanks,
florin
--
Bruce Schneier expects the Spanish Inquisition.
http://geekz.co.uk/schneierfacts/fact/163
Attachment:
signature.asc
Description: Digital signature
- Follow-Ups:
- Re: Oops in dentry_iput with 2.6.22-rc2 on AMD64
- From: Jan Kara <[email protected]>
- Re: Oops in dentry_iput with 2.6.22-rc2 on AMD64
- References:
- Oops in dentry_iput with 2.6.22-rc2 on AMD64
- From: [email protected] (Florin Iucha)
- Re: Oops in dentry_iput with 2.6.22-rc2 on AMD64
- From: Jan Kara <[email protected]>
- Oops in dentry_iput with 2.6.22-rc2 on AMD64
- Prev by Date: Re: how to allow board writers to customize driver behavior (watchdog here)
- Next by Date: Re: [AppArmor 01/41] Pass struct vfsmount to the inode_create LSM hook
- Previous by thread: Re: Oops in dentry_iput with 2.6.22-rc2 on AMD64
- Next by thread: Re: Oops in dentry_iput with 2.6.22-rc2 on AMD64
- Index(es):
 |