1180:0822 SD card not detected on insertion

[Anton]

Quite simply, when I insert an SD card (which works fine inserted into the camera or my wife's laptop), nothing happens. No icons, no filebrowser opening. Also, no noticeable activity in /var/log. The device is visible on the PCI, with or without card.

Also occurs in 3.4.0-999. The file was called linux-image-3.4.0-999-generic_3.4.0-999.201205060405_amd64.deb .

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.37
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: fglrx
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
AplayDevices:
 **** List of PLAYBACK Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: AD198x Analog [AD198x Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: feenstra 3889 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd8420000 irq 49'
   Mixer name : 'Analog Devices AD1984A'
   Components : 'HDA:11d4194a,103c30dc,00100400'
   Controls : 18
   Simple ctrls : 11
Date: Sat May 5 20:39:22 2012
HibernationDevice: RESUME=UUID=92c92b0a-05c8-423e-a01a-5e80e3b0af85
MachineType: Hewlett-Packard HP EliteBook 6930p
PccardctlStatus:
 Socket 0:
   3.3V
  16-bit
  PC Card
   Subdevice 0 (function 0) bound to driver "pata_pcmcia"
ProcFB: 0 VESA VGA
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=21da2f5d-74ae-4f92-bafe-1ee80dcee5c9 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
SourcePackage: linux
StagingDrivers: mei
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/31/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68PCD Ver. F.12
dmi.board.name: 30DC
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 87.27
dmi.chassis.asset.tag: CZC9351JJ6
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68PCDVer.F.12:bd07/31/2009:svnHewlett-Packard:pnHPEliteBook6930p:pvrF.12:rvnHewlett-Packard:rn30DC:rvrKBCVersion87.27:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 6930p
dmi.product.version: F.12
dmi.sys.vendor: Hewlett-Packard

[penalvch (penalvch)]

Anton, thank you for reporting this and helping make Ubuntu better. 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.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.

Please let us know your results. Thanks in advance.

[Anton (feenstra)]

Just booted into mainline. Still no volume mounted on the desktop, but on insertion of the SD card, I do see the following in both syslog and kern.log:
May 6 12:23:02 note-feenstra kernel: [ 421.590414] sdhci-pci 0000:86:09.1: Will use DMA mode even though HW doesn't fully claim to support it.
So, something is coming through to the kernel at least.

[penalvch (penalvch)]

Anton, thank you for testing mainline. Just to be clear, which did you test specifically?

[Anton (feenstra)]

3.4.0-999. The file was called linux-image-3.4.0-999-generic_3.4.0-999.201205060405_amd64.deb

[penalvch (penalvch)]

Anton, the issue you are reporting is an upstream one and it would be nice if somebody having it could send the bug to the developers of the software by following the instructions, verbatim, at https://wiki.ubuntu.com/Bugs/Upstream/kernel . If you have done so, please tell us the number of the upstream bug (or the link), so we can add a bugwatch that will inform us about its status. Thanks in advance.

[penalvch (penalvch)]

Anton, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the kernel in the mainline kernels archive directory daily folder. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.8-rc3

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Helpful bug reporting tips:
https://help.ubuntu.com/community/ReportingBugs

[Horst Schirmeier (horst)]

This problem persists in Ubuntu 14.04 with x86_64 kernel 3.13.0-36-generic.

[penalvch (penalvch)]

Horst Schirmeier, thank you for your comment. Unfortunately, this bug report is not scoped to you, or your problem. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

As well, please do not announce in this report you created a new bug report.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs