From: Michal Illich <michal@illich.cz>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 crash
Date: Fri, 09 Aug 2002 14:13:25 +0200 [thread overview]
Message-ID: <3D53B1E5.1010301@illich.cz> (raw)
In-Reply-To: 1028894485.28882.208.camel@irongate.swansea.linux.org.uk
>>Happened again, now with "kernel BUG at buffer.c:510!" message.
> Looks very much like random memory corruption. Could be many things.
> Does the box pass memtest86 ?
It just passed memtest-2.93.1 (I don't have physical access to machine to
run standalone test). BIOS memcheck also runs ok. It usually crashes after
1-5 days, in the meantime all programs run perfectly.
---------------------------------------------------- memtest.log:
Testing 469684224 bytes at 0x42136000 (4088 bytes lost to page alignment).
Run 1:
Test 1: Stuck Address: Setting...Passed.
Test 2: Random value: Setting...Testing...Passed.
Test 3: XOR comparison: Setting...Testing...Passed.
Test 4: SUB comparison: Setting...Testing...Passed.
Test 5: MUL comparison: Setting...Testing...Passed.
Test 6: DIV comparison: Setting...Testing...Passed.
Test 7: OR comparison: Setting...Testing...Passed.
Test 8: AND comparison: Setting...Testing...Passed.
Test 9: Sequential Increment: Setting...Testing...Passed.
Test 10: Solid Bits: Setting...Passed.
Test 11: Block Sequential: Setting...Passed.
Test 12: Checkerboard: Setting...Passed.
Test 13: Bit Spread: Setting...Passed.
Test 14: Bit Flip: Setting...Passed.
Test 15: Walking Ones: Setting...Passed.
Test 16: Walking Zeroes: Setting...Passed.
Run 1 completed in 1476 seconds (0 tests showed errors).
munlock'ed memory.
1 runs completed. 0 errors detected. Total runtime: 1476 seconds.
next prev parent reply other threads:[~2002-08-09 12:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 10:02 2.4.19 crash Michal Illich
2002-08-09 12:01 ` Alan Cox
2002-08-09 12:13 ` Michal Illich [this message]
-- strict thread matches above, loose matches on Subject: below --
2002-08-07 19:50 Michal Illich
2002-08-07 18:17 Michal Illich
2002-08-07 22:04 ` Alan Cox
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=3D53B1E5.1010301@illich.cz \
--to=michal@illich.cz \
--cc=alan@lxorguk.ukuu.org.uk \
--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