From: "George Spelvin" <linux@horizon.com>
To: jkosina@suse.cz, linux@horizon.com
Cc: jack@suse.cz, linux-ext4@vger.kernel.org,
linux-kernel@vger.kernel.org, torvalds@linux-foundation.org
Subject: Re: Oops in ext3_block_to_path.isra.40+0x26/0x11b
Date: 16 Mar 2012 17:04:46 -0400 [thread overview]
Message-ID: <20120316210446.2198.qmail@science.horizon.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1203161623130.18356@pobox.suse.cz>
> So it might be the culprit. As the reason of the corruption is not yet
> understood, it might be that suspend/resume cycle is not necessary
> pre-requisite for this to trigger, it might just make it more likely.
It might just be virtual console switching. Normally I live in X,
but I might have switched to a text console for some reason (I don't
specifically remember doing this, but it's very plausible for me).
> And the corruption is observed to be indeed several writes of 0x00000000,
> so it could easily lead to null pointer dereferences all over the place.
>
> Are you able to reproduce the problem if you turn kernel modesetting off?
Unfortunately, this is the only time it's happened to me with kernel
modesetting *on*. Would repeated checksums of a kernel tree be a good
way to detect random memory stomping?
next prev parent reply other threads:[~2012-03-16 21:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-13 13:39 Oops in ext3_block_to_path.isra.40+0x26/0x11b George Spelvin
2012-03-16 8:52 ` Jan Kara
2012-03-16 9:11 ` George Spelvin
2012-03-16 9:29 ` Jiri Kosina
2012-03-16 10:07 ` Jan Kara
2012-03-16 14:28 ` George Spelvin
2012-03-16 15:25 ` Jiri Kosina
2012-03-16 21:04 ` George Spelvin [this message]
2012-03-16 21:09 ` Linus Torvalds
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=20120316210446.2198.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=jack@suse.cz \
--cc=jkosina@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).