I/O errors writing to SD card

[Mark Greenwood]

There are Kubuntu 10.04, all current updates.

There are a few similar bug reports to this one but they're all related to USB devices. I'm having trouble with the built-in card reader on my laptop. When writing large numbers of files, especially large ones, to a large capacity card (8GB or more) I get lots of I/O errors and after a while the card unmounts itself.

I get the same kind of errors when reading from my CD drive too.

I'm able to improve the issue by doing
sudo sh -c "echo 120 > /sys/block/mmcblk0/queue/max_sectors_kb"
However I don't regard this as a solution because it's not obvious or automatic. There should at least be some documentation somewhere about how to make that happen automatically when an SD card is inserted.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: linux-image-generic 2.6.32.22.23
Regression: No
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.21.
Architecture: i386
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: bob 4075 F.... knotify4
                      bob 4171 F.... kmix
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xfc400000 irq 32'
   Mixer name : 'SigmaTel STAC9872AK'
   Components : 'HDA:83847662,104d1c00,00100201 HDA:14f12c06,104d1700,00100000'
   Controls : 17
   Simple ctrls : 10
Date: Tue Jun 22 15:00:56 2010
HibernationDevice: RESUME=UUID=268b116b-6212-4018-983b-ab632cdae336
InstallationMedia: Kubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100427)
MachineType: Sony Corporation VGN-FZ31M
PccardctlIdent:
 Socket 0:
   no product info available
PccardctlStatus:
 Socket 0:
   no card
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.32-22-generic root=UUID=bc896133-3a66-4618-a31e-83a0344d31ed ro quiet splash
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
RelatedPackageVersions: linux-firmware 1.34
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: yes
SourcePackage: linux
dmi.bios.date: 12/21/2007
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R2110J7
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrR2110J7:bd12/21/2007:svnSonyCorporation:pnVGN-FZ31M:pvrC6005TES:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: VGN-FZ31M
dmi.product.version: C6005TES
dmi.sys.vendor: Sony Corporation

[Jeremy Foshee (jeremyfoshee)]

Hi Mark,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]