From: Thomas Gleixner <tglx@linutronix.de>
To: ahgu <ahgu@ahgu.homeunix.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: simulate a bad NAND block cause kernel hang
Date: Thu, 25 Aug 2005 13:44:55 +0000 [thread overview]
Message-ID: <1124977495.20120.111.camel@tglx.tec.linutronix.de> (raw)
In-Reply-To: <10af01c5a978$c336df10$1f1a12ac@atitech.com>
On Thu, 2005-08-25 at 09:27 -0400, ahgu wrote:
> I forced the flash_erase function to fail. I expect the jffs2 will pick up
> the return error and mark the block bad and put the bad block in a bad_block
> list. But what I get is kernel failure:
> I get similar error when I simulate a write error.
> Am I doing the bad block simulation correctly? Is this a correct response?
> What is supposed to happen when the NAND flash grow a bad block?
JFFS2 should handle this.
The oops trace is worthless, as it does not show the stack trace in
human readable form (function names decoded)
Make sure that CONFIG_KALLSYMS is set in your kernel .config file.
Also information about kernel version and possibly applied MTD/JFFS2
patches is missing.
tglx
next prev parent reply other threads:[~2005-08-25 13:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-25 13:27 simulate a bad NAND block cause kernel hang ahgu
2005-08-25 13:44 ` Thomas Gleixner [this message]
2005-08-25 15:41 ` ahgu
2005-08-25 15:47 ` Thomas Gleixner
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=1124977495.20120.111.camel@tglx.tec.linutronix.de \
--to=tglx@linutronix.de \
--cc=ahgu@ahgu.homeunix.com \
--cc=linux-mtd@lists.infradead.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