'DMA: Out of SW-IOMMU space' errors using SD cards on Thinkpad X220
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux (Ubuntu) |
Expired
|
Medium
|
Unassigned |
Bug Description
Reading data from a 16GB SD card produces a lot of the following error and corrupts the data read. Sometimes I see this as an occasional messed up photo which works perfectly on a later read, and sometimes the whole directory structure is broken (permissions, names, etc).
[68316.256729] ------------[ cut here ]------------
[68316.256737] WARNING: at /build/
[68316.256738] Hardware name: 42914CG
[68316.256739] Modules linked in: nls_iso8859_1 nls_cp437 vfat fat mmc_block cdc_acm usb_storage uas openafs(P) bnep rfcomm pci_stub vboxpci vboxnetadp vboxnetflt vboxdrv parport_pc ppdev snd_hda_codec_hdmi snd_hda_
[68316.256772] Pid: 1249, comm: mmcqd/0 Tainted: P WC 3.0.0-20-generic #34-Ubuntu
[68316.256774] Call Trace:
[68316.256779] [<ffffffff8105e
[68316.256782] [<ffffffff8105e
[68316.256786] [<ffffffffa0066
[68316.256791] [<ffffffffa0067
[68316.256795] [<ffffffffa0067
[68316.256797] [<ffffffff814b6
[68316.256799] [<ffffffff814b6
[68316.256802] [<ffffffffa0580
[68316.256805] [<ffffffff814b6
[68316.256808] [<ffffffffa0581
[68316.256811] [<ffffffff812d2
[68316.256814] [<ffffffffa0582
[68316.256817] [<ffffffffa0581
[68316.256820] [<ffffffff81081
[68316.256824] [<ffffffff815fd
[68316.256827] [<ffffffff81081
[68316.256830] [<ffffffff815fd
[68316.256831] ---[ end trace 9e04b7dd2432a0c6 ]---
[68316.286028] DMA: Out of SW-IOMMU space for 65536 bytes at device 0000:0d:00.0
[68316.286030] ------------[ cut here ]------------
If I try to copy a lot of data, lots of the errors are produced and the system response, including mouse cursor movement, becomes very slow.
There are mentions of the same/a similar bug back in the 2007-2009 area for an older kernel, that had something to do with having more than 4GB of RAM (This machine has 8GB):
https:/
That was apparently fixed in 2.6.27.12 and this is 3.0.0-20.
ProblemType: Bug
DistroRelease: Ubuntu 11.10
Package: linux-image-
ProcVersionSign
Uname: Linux 3.0.0-20-generic x86_64
NonfreeKernelMo
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.23-0ubuntu4
Architecture: amd64
ArecordDevices:
**** List of CAPTURE Hardware Devices ****
card 0: PCH [HDA Intel PCH], device 0: CONEXANT Analog [CONEXANT Analog]
Subdevices: 1/1
Subdevice #0: subdevice #0
AudioDevicesInUse:
USER PID ACCESS COMMAND
/dev/snd/
/dev/snd/
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
Card hw:0 'PCH'/'HDA Intel PCH at 0xf2620000 irq 51'
Mixer name : 'Intel CougarPoint HDMI'
Components : 'HDA:14f1506e,
Controls : 20
Simple ctrls : 8
Card29.Amixer.info:
Card hw:29 'ThinkPadEC'
Mixer name : 'ThinkPad EC (unknown)'
Components : ''
Controls : 1
Simple ctrls : 1
Card29.
Simple mixer control 'Console',0
Capabilities: pswitch pswitch-joined penum
Playback channels: Mono
Mono: Playback [on]
Date: Sun May 20 09:43:39 2012
HibernationDevice: RESUME=
InstallationMedia: Xubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: LENOVO 42914CG
ProcEnviron:
SHELL=/bin/bash
PATH=(custom, no user)
LANG=en_US.UTF-8
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
linux-
linux-
linux-firmware 1.60.1
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET56WW (1.26 )
dmi.board.
dmi.board.name: 42914CG
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 42914CG
dmi.product.
dmi.sys.vendor: LENOVO
Changed in linux (Ubuntu): | |
status: | New → Confirmed |
I tried the card in a USB card reader in the same laptop and it also failed and gave a SW-IOMMU warning in dmesg (with no kernel stracktrace though).
I have now rebooted the machine and both the built-in and USB card readers work perfectly with no warnings. Beforehand, the laptop had been in and out of suspend all week and IIRC hadn't been rebooted so it might have been caused by something else and just triggered here. I will try to isolate the cause next week.
BTW, There was no kernel update applied over the reboot that fixed it.