From: Gordan Bobic <gordan@bobich.net>
To: linux-ext4@vger.kernel.org
Subject: Re: [Bug 45621] Kernel ooops: BUG: unable to handle kernel paging request at 000000080000001c
Date: Mon, 06 Aug 2012 23:21:19 +0100 [thread overview]
Message-ID: <5020435F.5000304@bobich.net> (raw)
In-Reply-To: <20120806221442.D539011FA3A@bugzilla.kernel.org>
On 08/06/2012 11:14 PM, bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=45621
>
>
>
>
>
> --- Comment #6 from markus.doits@googlemail.com 2012-08-06 22:14:42 ---
> Just ran memtest for 3+ hours, 3 passes finished successfully. I know, longer
> is better, but cannot run it longer atm (since it's a server with crucial
> infrastructure). System is not overclocked or so, everything default.
memtest86 is completely useless at finding marginal memory. It'll only
typically find a problem if there is a properly, permanently dead or
stuck bit in the RAM.
If Windows is an option temporarily for testing use OCCT. If it isn't,
I've found something like this to work pretty well for finding CPU and
memory stability issues:
#####
# Assuming your /dev/shm is mounted on tmpfs - make sure it's big
# enough. Adjust count= accordingly
dd if=/dev/urandom bs=1M count=1024 of=/dev/shm/test
# Run one instance of this per CPU thread
#!/bin/bash
sum=`sha512sum /tmp/test`
while (/bin/true); do
echo -n .
sum2=`sha512sum /tmp/test`
if [ "$sum" != "$sum2" ]; then
echo “”
echo “Error detected. $sum != $sum2″
exit
fi
done
#####
That should be a lot better at finding CPU/cache/MCH/RAM issues.
Gordan
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2012-08-06 22:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-04 23:33 [Bug 45621] New: Kernel ooops: BUG: unable to handle kernel paging request at 000000080000001c bugzilla-daemon
2012-08-04 23:45 ` [Bug 45621] " bugzilla-daemon
2012-08-05 22:12 ` bugzilla-daemon
2012-08-05 22:24 ` bugzilla-daemon
2012-08-05 22:36 ` bugzilla-daemon
2012-08-06 15:15 ` bugzilla-daemon
2012-08-06 22:14 ` bugzilla-daemon
2012-08-06 22:21 ` Gordan Bobic [this message]
2012-11-07 9:58 ` bugzilla-daemon
2012-11-07 12:42 ` bugzilla-daemon
2012-11-07 14:18 ` bugzilla-daemon
2013-11-19 23:43 ` bugzilla-daemon
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=5020435F.5000304@bobich.net \
--to=gordan@bobich.net \
--cc=linux-ext4@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;
as well as URLs for NNTP newsgroup(s).