From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-omap@vger.kernel.org
Subject: Re: LDP broken?
Date: Sat, 16 Jan 2010 12:34:03 -0800 [thread overview]
Message-ID: <20100116203402.GP10318@atomide.com> (raw)
In-Reply-To: <20100113173337.GI2986@atomide.com>
* Tony Lindgren <tony@atomide.com> [100113 09:32]:
> * Russell King - ARM Linux <linux@arm.linux.org.uk> [100113 05:39]:
> > While trying to boot the latest kernel on the LDP platform, it appears
> > that MMC has a problem.
> >
> > Unfortunately, being a small form factor card, the only platform I have
> > which accepts it is the LDP. Not sure if this is down to crappyness
> > with the card or the host driver.
> >
> > Waiting 2sec before mounting root device...
> > mmc0: host does not support reading read-only switch. assuming write-enable.
> > mmc0: new high speed SD card at address 0002
> > mmcblk0: mmc0:0002 00000 971 MiB
> > mmcblk0: p1 p2
> > kjournald starting. Commit interval 5 seconds
> > EXT3-fs (mmcblk0p2): warning: mounting fs with errors, running e2fsck is recomme
> > nded
> > EXT3-fs (mmcblk0p2): using internal journal
> > EXT3-fs (mmcblk0p2): recovery complete
> > EXT3-fs (mmcblk0p2): mounted filesystem with writeback data mode
> > VFS: Mounted root (ext3 filesystem) on device 179:2.
> > Freeing init memory: 108K
> > mmcblk0: retrying using single block read
> > mmcblk0: retrying using single block read
> > INIT: version 2.86 booting
> > mmcblk0: retrying using single block read
> > mmcblk0: retrying using single block read
> > modprobe: FATAL: Could not load /lib/modules/2.6.33-rc4/modules.dep: No such fil
> > e or directory
> >
> > modprobe: FATAL: Could not load /lib/modules/2.6.33-rc4/modules.dep: No such fil
> > e or directory
> >
> > Error opening /dev/fb0: No such device or address
> > udev requires hotplug support, not started.
> > mmcblk0: retrying using single block read
> > WARNING: Couldn't open directory /lib/modules/2.6.33-rc4: No such file or direct
> > ory
> > FATAL: Could not open /lib/modules/2.6.33-rc4/modules.dep.temp for writing: No s
> > uch file or directory
> > modprobe: FATAL: Could not load /lib/modules/2.6.33-rc4/modules.dep: No such fil
> > e or directory
> >
> > modprobe: FATAL: Could not load /lib/modules/2.6.33-rc4/modules.dep: No such fil
> > e or directory
> >
> > mmcblk0: error -110 transferring data, sector 149929, nr 216, card status 0xc00
> > end_request: I/O error, dev mmcblk0, sector 150100
> > end_request: I/O error, dev mmcblk0, sector 150105
> > end_request: I/O error, dev mmcblk0, sector 150113
> > end_request: I/O error, dev mmcblk0, sector 150121
> > end_request: I/O error, dev mmcblk0, sector 150129
> > end_request: I/O error, dev mmcblk0, sector 150137
> > Aborting journal on device mmcblk0p2.
> > EXT3-fs (mmcblk0p2): error in ext3_reserve_inode_write: Journal has aborted
> > EXT3-fs (mmcblk0p2): error in ext3_dirty_inode: Journal has aborted
> > EXT3-fs (mmcblk0p2): error: ext3_journal_start_sb: Detected aborted journal
> > EXT3-fs (mmcblk0p2): error: remounting filesystem read-only
> > Setting up IP spoofing protection: FAILED.
> > Configuring network interfaces... done.
> > Starting portmap daemon: portmap.
> > mmcblk0: retrying using single block read
> > /sbin/ldconfig: /usr/lib/libts-0.0.so.0 is not a symbolic link
> > ...
>
> It looks like .wires = 4 is should be a safe setting. Maybe the
> card is broken or does not get enough power from twl? No LDP here,
> but MMC is working OK in general for me.
BTW, I'm also seeing tons of the same mmc warnings about
"mmcblk0: retrying using single block read" on overo.
It still mounts root fine despite the warnings, so no
errors for me. Not getting these errors on rx51.
Regards,
Tony
prev parent reply other threads:[~2010-01-16 20:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-13 13:40 LDP broken? Russell King - ARM Linux
2010-01-13 17:33 ` Tony Lindgren
2010-01-16 20:34 ` Tony Lindgren [this message]
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=20100116203402.GP10318@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
/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