LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Harald Dunkel <harald.dunkel@t-online.de>
To: linux-kernel@vger.kernel.org
Subject: 2.6.24-rc6: ricoh_mmc woes
Date: Sat, 05 Jan 2008 21:28:50 +0100 [thread overview]
Message-ID: <477FE882.1030901@t-online.de> (raw)
Hi folks,
I've got a problem with a Ricoh mmc reader. As soon as I insert a
sd card I get tons of I/O errors. syslog says:
Jan 5 21:19:12 daffy kernel: ricoh-mmc: Ricoh MMC Controller disabling driver
Jan 5 21:19:12 daffy kernel: ricoh-mmc: Copyright(c) Philip Langdale
Jan 5 21:19:12 daffy kernel: ricoh-mmc: Ricoh MMC controller found at 0000:03:01.2 [1180:0843] (rev 12)
Jan 5 21:19:12 daffy kernel: ricoh-mmc: Controller is now disabled.
Jan 5 21:19:25 daffy kernel: mmc0: new high speed SD card at address 1234
Jan 5 21:19:25 daffy kernel: mmcblk0: mmc0:1234 SD01G 995328KiB
Jan 5 21:19:25 daffy kernel: mmcblk0:<3>mmcblk0: error -84 transferring data
Jan 5 21:19:25 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0
Jan 5 21:19:25 daffy kernel: printk: 32 messages suppressed.
Jan 5 21:19:25 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0
Jan 5 21:19:25 daffy kernel: mmcblk0: error -84 transferring data
Jan 5 21:19:25 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0
Jan 5 21:19:25 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0
Jan 5 21:19:25 daffy kernel: mmcblk0: error -84 transferring data
Jan 5 21:19:25 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0
Jan 5 21:19:25 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0
Jan 5 21:19:25 daffy kernel: mmcblk0: error -84 transferring data
Jan 5 21:19:25 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0
Jan 5 21:19:25 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0
Jan 5 21:19:26 daffy kernel: mmcblk0: error -84 transferring data
Jan 5 21:19:26 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0
Jan 5 21:19:26 daffy kernel: Buffer I/O error on device mmcblk0, logical block 0
Jan 5 21:19:26 daffy kernel: ldm_validate_partition_table(): Disk read failed.
Jan 5 21:19:26 daffy kernel: mmcblk0: error -84 transferring data
Jan 5 21:19:26 daffy kernel: end_request: I/O error, dev mmcblk0, sector 0
:
:
The ricoh_mmc disabler module is installed as a module. udev loads it
at boot time. But AFAICS I get the same errors if ricoh_mmc is removed.
lspci says
# lspci | grep -i ricoh
03:01.0 FireWire (IEEE 1394): Ricoh Co Ltd Unknown device 0832 (rev 05)
03:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host Adapter (rev 22)
03:01.2 System peripheral: Ricoh Co Ltd Unknown device 0843 (rev 12)
03:01.3 System peripheral: Ricoh Co Ltd R5C592 Memory Stick Bus Host Adapter (rev 12)
03:01.4 System peripheral: Ricoh Co Ltd xD-Picture Card Controller (rev ff)
# lspci -n | grep 03:01
03:01.0 0c00: 1180:0832 (rev 05)
03:01.1 0805: 1180:0822 (rev 22)
03:01.2 0880: 1180:0843 (rev 12)
03:01.3 0880: 1180:0592 (rev 12)
03:01.4 0880: 1180:0852 (rev ff)
Of course the SD card works fine in another PC.
Any idea how to track this down? Please mail
Regards
Harri
next reply other threads:[~2008-01-05 20:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-05 20:28 Harald Dunkel [this message]
2008-01-09 12:48 ` 2.6.24-rc6: ricoh_mmc woes Pierre Ossman
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=477FE882.1030901@t-online.de \
--to=harald.dunkel@t-online.de \
--cc=linux-kernel@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).