From: Jacek Kawa <jfk@zeus.polsl.gliwice.pl>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test8, oops, [__remove_from_page_cache+36/112] __remove_from_page_cache+0x24/0x70
Date: Thu, 23 Oct 2003 14:34:46 +0200 [thread overview]
Message-ID: <20031023123446.GA4515@finwe.eu.org> (raw)
In-Reply-To: <20031022111427.GL2617@rdlg.net>
Robert L. Harris wrote:
> > > This machine has new RAM, but after about 7 hours of testing,
> > > memtest.86 didn't show any errors...
> > Well, it's RAM anyway... I've just got few segfaults in vim...
> This sounds like what mine was doing, the oops looked similar as well
> (with the null pointer part atleast). Reboot and I bet it'll run fine
> for a while and then start up again. For me it seemed to start faulting
> when "free" showed over 250 Megs used.
In next run memtest found some errors (after nine hours though ;)
So hardware, not Linux. :)
bye
--
Jacek Kawa
prev parent reply other threads:[~2003-10-23 12:34 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 8:44 2.6.0-test8, oops, [__remove_from_page_cache+36/112] __remove_from_page_cache+0x24/0x70 Jacek Kawa
2003-10-22 8:56 ` Jacek Kawa
2003-10-22 11:14 ` Robert L. Harris
2003-10-23 12:34 ` Jacek Kawa [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=20031023123446.GA4515@finwe.eu.org \
--to=jfk@zeus.polsl.gliwice.pl \
--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 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.