From: "Thorsten Schulz" <stehbrettsegeln@gmx.de>
To: linux-mips@linux-mips.org
Subject: "Bad eraseblock"-problem with au1550nd-NAND-driver after kernel update to 2.6.23.1
Date: Sun, 04 Nov 2007 10:10:57 +0100 [thread overview]
Message-ID: <op.t09fsjv333s53m@localhost.localdomain> (raw)
Hi,
I am fiddeling around with an Au1550-System (Lippert CoolMoteMaster).
After I updated the Kernel from 2.6.17.7 to 2.6.23.1 the flash driver complaints about Bad eraseblocks at kernel start:
[17179570.224000] NAND device: Manufacturer ID: 0x20, Chip ID: 0xda (ST Micro NAND 256MiB 3,3V 8-bit)
[17179570.232000] Scanning device for bad blocks
[17179570.236000] Bad eraseblock 0 at 0x00000000
[17179570.240000] Bad eraseblock 1 at 0x00020000
[17179570.248000] Bad eraseblock 2 at 0x00040000
[..]
[17179579.748000] Bad eraseblock 2046 at 0x0ffc0000
[17179579.752000] Bad eraseblock 2047 at 0x0ffe0000
[17179579.756000] Creating 1 MTD partitions on "NAND 256MiB 3,3V 8-bit":
[17179579.760000] 0x00000000-0x10000000 : "NAND FS 0"
[17179579.772000] au1xxx-ohci au1xxx-ohci.0: Au1xxx OHCI
[..]
I get the same output from the .17.7. kernel apart from the 'Bad'-messages. The size seems correct, as I should get one 256MB-flash-device. I did use the patch from Lippert to set their platform data, which was intended for 2.6.17.7. With small changes it also succeeds on 2.6.23.1 but this doesn't mean that it's correct ;)
The 2.6.17.7 kernel still runs fine with that flash.
I am quite new to kernel hacking and after some cause searching I'm still lost. Were there any changes in the necessary configuration / platform setup that I am missing? Any ideas / hints what I can look for? Any common mistakes?
ciao,
Thorsten
reply other threads:[~2007-11-04 9:11 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=op.t09fsjv333s53m@localhost.localdomain \
--to=stehbrettsegeln@gmx.de \
--cc=linux-mips@linux-mips.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