All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Anders Grafström" <grfstrm@users.sourceforge.net>
To: E Robertson <e.robertson.svg@gmail.com>
Cc: Marek Vasut <marek.vasut@gmail.com>,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	linux-arm-kernel@lists.arm.linux.org.uk,
	linux-mtd@lists.infradead.org
Subject: Re: Internal error: Oops: 817 [#1]
Date: Mon, 03 Aug 2009 17:43:37 +0200	[thread overview]
Message-ID: <4A7705A9.3040402@users.sourceforge.net> (raw)
In-Reply-To: <3972542e0907301429n45c4597ar36907386bf00637e@mail.gmail.com>

E Robertson wrote:
> On Thu, Jul 30, 2009 at 4:21 PM, Russell King - ARM
> Linux<linux@arm.linux.org.uk> wrote:
>> It's worth pointing out that media errors should not cause a kernel
>> oops or BUG() - especially in the case of a synchronous write.
>>
>> So one way to look at this is you have the perfect setup at the moment
>> for jffs2 developers to fix this problem in addition to locating what
>> ever is causing the CRC errors.
>>
> 
> agree. I'll test on this with 2.6.28.4/ .31-rc4.

Could you try this patch?

http://lists.infradead.org/pipermail/linux-mtd/2009-August/026754.html

  reply	other threads:[~2009-08-03 15:43 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 [this message]
2009-08-04 13:21               ` E Robertson
2009-08-04 19:03                 ` E Robertson
2009-07-30 20:29     ` Daniel Mack
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=4A7705A9.3040402@users.sourceforge.net \
    --to=grfstrm@users.sourceforge.net \
    --cc=e.robertson.svg@gmail.com \
    --cc=linux-arm-kernel@lists.arm.linux.org.uk \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --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 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.