From: Theodore Tso <tytso@mit.edu>
To: Eric Lacombe <tuxiko@free.fr>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: EXT3-fs error
Date: Thu, 21 Aug 2008 09:36:55 -0400 [thread overview]
Message-ID: <20080821133655.GG16634@mit.edu> (raw)
In-Reply-To: <200808211302.55530.tuxiko@free.fr>
On Thu, Aug 21, 2008 at 01:02:55PM +0200, Eric Lacombe wrote:
> > Might be worth running memtest86 on the box overnight and seeing if its
> > memory or other problems. smartmontools will give you info on the disk
> > status (as the disk sees it) which can sometimes give clues.
>
> I will run memtest86 very soon. But in the meantime my computer just crashed.
> The logs are presented below (I know that the module nvidia is loaded, but I
> never have problem with it before.).
> I remark that a general protection fault occur, and I saw a lot of them
> recently (see also the second log trail for another error 2 hours earlier).
I would definitely run memtest86 very soon, and if that doesn't work,
I'd try running for a little while without the nvidia driver. I know
you say it hasn't given you any trouble, but it's always good to rule
out problems. The sort of errors which you are reporting do make me
very suspicious about some kind of memory fault, though. (Either
hardware induced or wild pointer induced, perhaps by some evil
binary-only module. :-)
- Ted
next prev parent reply other threads:[~2008-08-21 13:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 9:06 EXT3-fs error Eric Lacombe
2008-08-21 9:46 ` Alan Cox
2008-08-21 11:02 ` Eric Lacombe
2008-08-21 13:36 ` Theodore Tso [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-08-21 2:38 Eric Lacombe
2006-08-31 18:02 Richard Amick
2006-08-31 19:16 ` Theodore Tso
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=20080821133655.GG16634@mit.edu \
--to=tytso@mit.edu \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=tuxiko@free.fr \
/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