From: Daniel Mack <daniel@caiaq.de>
To: E Robertson <e.robertson.svg@gmail.com>
Cc: Marek Vasut <marek.vasut@gmail.com>,
linux-mtd@lists.infradead.org,
linux-arm-kernel@lists.arm.linux.org.uk
Subject: Re: Internal error: Oops: 817 [#1]
Date: Thu, 30 Jul 2009 22:29:13 +0200 [thread overview]
Message-ID: <20090730202913.GB13236@buzzloop.caiaq.de> (raw)
In-Reply-To: <3972542e0907301314p4a8c9539uc7b5fdd80abec443@mail.gmail.com>
On Thu, Jul 30, 2009 at 03:14:43PM -0500, E Robertson wrote:
> I got 2.6.31-rc4 and patch it which wasn't painful.
> However, no change.
> Here are the results: My initramfs initially mount the two nand
> partitions and that's where the initial
> uncorrectable error comes from.
Some thoughts.
Could you try running the torture test from drivers/mtd/tests? Which
platform is that? Are you sure you're running the NAND chip well inside
its timing specs? Does the flash access work from the bootloader?
I recently had similar trouble which disappeared after I switched off
CPU frequency scaling.
Daniel
next prev parent reply other threads:[~2009-07-30 20:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3972542e0907301124n104c9eafnc99e989d1a9f8d51@mail.gmail.com>
2009-07-30 18:35 ` Internal error: Oops: 817 [#1] Russell King - ARM Linux
[not found] ` <200907302036.24243.marek.vasut@gmail.com>
2009-07-30 18:43 ` E Robertson
2009-07-30 20:14 ` E Robertson
2009-07-30 20:26 ` Russell King - ARM Linux
2009-07-30 21:08 ` E Robertson
2009-07-30 21:21 ` Russell King - ARM Linux
2009-07-30 21:29 ` E Robertson
2009-08-03 15:43 ` Anders Grafström
2009-08-04 13:21 ` E Robertson
2009-08-04 19:03 ` E Robertson
2009-07-30 20:29 ` Daniel Mack [this message]
2009-07-30 21:22 ` E Robertson
2009-07-30 21:40 ` Daniel Mack
2009-07-31 13:49 ` E Robertson
2009-07-31 13:56 ` Daniel Mack
2009-07-31 14:08 ` E Robertson
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=20090730202913.GB13236@buzzloop.caiaq.de \
--to=daniel@caiaq.de \
--cc=e.robertson.svg@gmail.com \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
/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).