From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Fwd: udev problem (and fix) for /dev/mtdblock*
Date: Wed, 18 Mar 2009 19:44:22 +0000 [thread overview]
Message-ID: <200903181244.23025.david-b@pacbell.net> (raw)
Marco suggested this goes "the upstream list" but didn't
forward it or say what that list is... udev still goes
to the hotplug list?
---------- Forwarded Message ----------
Subject: udev problem (and fix) for lenny/armel
Date: Thursday 20 November 2008
From: David Brownell <david-b@pacbell.net>
To: md@linux.it
Hi,
I have a machine running Debian and it's been getting nasty
boot messages like:
...
Synthesizing the initial hotplug events...done.
Waiting for /dev to be fully populated...uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0
Buffer I/O error on device mtdblock0, logical block 0
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 8
Buffer I/O error on device mtdblock0, logical block 1
end_request: I/O error, dev mtdblock0, sector 16
Buffer I/O error on device mtdblock0, logical block 2
end_request: I/O error, dev mtdblock0, sector 24
Buffer I/O error on device mtdblock0, logical block 3
uncorrectable error : <3>end_request: I/O error, dev mtdblock0, sector 0
Buffer I/O error on device mtdblock0, logical block 0
done.
Setting parameters of disc: (none).
...
Where /dev/mtdblock0 is something of a special NAND partition,
used by the mask ROM on the ARM to get a second stage loader,
which is then loaded from /dev/mtdblock1 etc. The messages
about "uncorrectable error" are from the kernel, since that
first partition uses a different ECC scheme than the rest of
the flash.
What's happening is that it's trying to read partition data
from the MTD devices ... which is inappropriate, they don't
use internal partition data. And the mtdblock0 read fails,
because of the ECC differences, producing messages ... ones
that should never have appeared, since it shouldn't have
been trying to read partition data.
The boot is easily cleaned up by a patch to a udev rules
file: /etc/udev/rules.d/60-persistent-storage.rules is
already skipping a bunch of devices, it just needs to add
the "mtd*" devices to what should be skipped:
KERNEL="ram*|loop*|fd*|mtd*|nbd*|gnbd*|dm-*|md*", GOTO="persistent_storage_end"
It'd be good to see this bug fixed before lenny goes final...
- Dave
-------------------------------------------------------
next reply other threads:[~2009-03-18 19:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-18 19:44 David Brownell [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-19 1:45 udev problem (and fix) for /dev/mtdblock* Kay Sievers
2009-03-19 10:08 ` Scott James Remnant
2009-03-20 18:46 ` David Brownell
2009-03-22 15:39 ` Kay Sievers
2009-03-23 18:49 ` David Brownell
2009-03-23 20:17 ` Kay Sievers
2009-03-24 21:14 ` David Brownell
2009-03-23 20:39 ` David Brownell
2009-03-23 21:21 ` Kay Sievers
2009-03-23 22:23 ` David Brownell
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=200903181244.23025.david-b@pacbell.net \
--to=david-b@pacbell.net \
--cc=linux-hotplug@vger.kernel.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).