From: Martin Rode <Martin.Rode@programmfabrik.de>
To: Rik van Riel <riel@conectiva.com.br>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.1 crashes every two days, oopses included
Date: Mon, 19 Feb 2001 09:59:30 +0100 [thread overview]
Message-ID: <3A90E072.BCF45429@programmfabrik.de> (raw)
In-Reply-To: <Pine.LNX.4.31.0102151645110.25331-100000@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 1489 bytes --]
Rik van Riel wrote:
> On Thu, 15 Feb 2001, Martin Rode wrote:
>
> > My last bug report did not seem to attract to much attention.
>
> > For now we have switched back to 2.2.18 which stays up for about
> > a week before it crashes because of the VM too.
>
> [snip]
> > VM: reclaim_page, wrong page on list.
> > VM: refill_inactive, wrong page on list.
> > Unable to handle kernel paging request at virtual address 00002208
>
> Since:
> 1. you see this kind of bug with both 2.2 and the completely
> changed 2.4 VM code and
> 2. this bug usually only happens when people have RAM problems,
>
> could you try running memtest86 on that machine to see if it indeed
> has memory errors or if the problem is coming from somewhere else ?
Hello Rik,
my maschine has spent the entire week-end running memtest86. It ran for
over 60 hours with all tests and it finished 3 passes with 0 errors.
Here's one more interesting aspect about the behaviour I'm seeing:
with 256 MB RAM:
<= 2.2.18: > 7 days, crashes randomly, no pattern.
>= 2.2.19pre2: 1 hour. Crashes as soon as I start hylafax daemon,
reproducable.
with 512 MB RAM
<= 2.2.18: same behaviour as with 2.4.1
2.4.1: Stands up 1 day, crashes as soon as arekeia has started the
backup (happend twice, second oopses included in my last mail)
Is there anything I can do? Is my problem kernel related? I believe
somehow it is. Is my maschine busted?
Any help appreciates
; Martin
[-- Attachment #2: Card for Martin Rode --]
[-- Type: text/x-vcard, Size: 365 bytes --]
begin:vcard
n:Rode;Martin
tel;cell:+49-171-1259525
tel;fax:+49-30-4281-8008
tel;work:+49-30-4281-8001
x-mozilla-html:TRUE
url:www.programmfabrik.de/~martin
org:Programmfabrik GmbH;Entwicklung
adr:;;Frankfurter Allee 73d;10247 Berlin;;;Germany
version:2.1
email;internet:Martin.Rode@programmfabrik.de
title:Dipl.-Kfm.
x-mozilla-cpt:;-28960
fn:Martin Rode
end:vcard
next prev parent reply other threads:[~2001-02-19 8:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-15 15:19 2.4.1 crashes every two days, oopses included Martin Rode
2001-02-15 15:48 ` Rik van Riel
2001-02-19 8:59 ` Martin Rode [this message]
2001-02-19 17:17 ` Eric W. Biederman
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=3A90E072.BCF45429@programmfabrik.de \
--to=martin.rode@programmfabrik.de \
--cc=linux-kernel@vger.kernel.org \
--cc=riel@conectiva.com.br \
/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