From: martin <martin@luminoussheep.net>
To: Andreas Dilger <adilger@dilger.ca>
Cc: Jan Kara <jack@ucw.cz>, Linux FS Devel <linux-fsdevel@vger.kernel.org>
Subject: Re: PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage?
Date: Sat, 12 Feb 2011 08:01:23 +0000 [thread overview]
Message-ID: <4D563E53.1020803@luminoussheep.net> (raw)
In-Reply-To: <A3CAB504-3F18-4C34-AE13-E39E7ACEE5D4@dilger.ca>
On 21/01/11 21:49, Andreas Dilger wrote:
> On Fri, 21 Jan 2011 20:55:35 -0000 (GMT)
> "M"<martin@luminoussheep.net> wrote:
>
>> I'm getting very regular crashes on a stock 2.6.37 kernel that I've
>> compiled myself. The crashes seem to regularly contain references to
>> filesystem code but are difficult to capture.
>>
>> I was about to type but for once it was captured in the log. I was seeing
>> similar issues with the previous release 2.6.36 so I'm guessing it's
>> something triggering on my machine more than most peoples.
>>
> I assume from the subject that you do NOT have crashes on some other kernel version that you are running? It isn't really clear from your email. Otherwise, the first suspect in frequent and mysterious crashes is bad RAM, and running memtest86 for a couple of days is the recommended course of action.
>
Good news, though memtest86 wasn't showing any errors I tried my laptop
with some other memory and it's working fine now even the graphics
problems have gone away.
Sorry to trouble you with these reports, many thanks for the advice.
Not quite sure why the memory isn't failing the test program but I'll
try a few more things...
--
M
next prev parent reply other threads:[~2011-02-12 8:01 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <888ef2e56b2ab414fdb72771db8d673f.squirrel@luminoussheep.net>
2011-01-21 21:03 ` PROBLEM: Regular crashes on 2.6.37 ext3_ordered_writepage? Andrew Morton
2011-01-21 21:49 ` Andreas Dilger
2011-01-21 22:06 ` M
2011-01-22 13:38 ` M
2011-02-12 8:01 ` martin [this message]
2011-01-21 21:27 M
2011-01-21 21:45 ` Andrew Morton
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=4D563E53.1020803@luminoussheep.net \
--to=martin@luminoussheep.net \
--cc=adilger@dilger.ca \
--cc=jack@ucw.cz \
--cc=linux-fsdevel@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.