197b:2394 [Dell XPS 17 L502X] Internal SD card reader is not working

[Sparhawk]

If I start up the computer with no SD card in the reader, it will not recognise SD cards inserted.

WORKAROUND: If you start up the computer with an SD card inserted, all is good.

WORKAROUND: The following rescan will find the SD card.

sudo su -l
echo 1 > /sys/bus/pci/rescan

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
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: PCH [HDA Intel PCH], device 0: ALC665 Analog [ALC665 Analog]
   Subdevices: 1/1
   Subdevice #0: subdevice #0
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lee 20624 F.... pulseaudio
CRDA:
 country AU:
  (2402 - 2482 @ 40), (N/A, 20)
  (5170 - 5250 @ 40), (3, 23)
  (5250 - 5330 @ 40), (3, 23), DFS
  (5735 - 5835 @ 40), (3, 30)
Card0.Amixer.info:
 Card hw:0 'PCH'/'HDA Intel PCH at 0xf3c00000 irq 55'
   Mixer name : 'Intel CougarPoint HDMI'
   Components : 'HDA:10ec0665,10280571,00100003 HDA:80862805,80860101,00100000'
   Controls : 31
   Simple ctrls : 13
Date: Mon May 7 13:52:09 2012
HibernationDevice: RESUME=UUID=131e7674-2f9b-4de3-b917-8d79a5a64e28
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64 (20111012)
MachineType: Dell Inc. Dell System XPS L702X
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic root=UUID=157174fa-f17e-471d-9008-353e4499b5f8 ro
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: Upgraded to precise on 2012-04-29 (7 days ago)
dmi.bios.date: 01/10/2012
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A16
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 0XN71K
dmi.board.vendor: Dell Inc.
dmi.board.version: FAB1
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.version: 0.1
dmi.modalias: dmi:bvnDellInc.:bvrA16:bd01/10/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDellInc.:ct8:cvr0.1:
dmi.product.name: Dell System XPS L702X
dmi.sys.vendor: Dell Inc.

[Sparhawk (sparhawkthesecond)]

Sorry for my ignorance, but the FAQ and the page you linked to doesn't quite give me enough information.

Firstly, what kind of risks are involved in installing the latest upstream kernel?

Also, are you talking about installing /~kernel-ppa/mainline/daily/current ?

Cheers.

[penalvch (penalvch)]

Sparhawk:
>"Firstly, what kind of risks are involved in installing the latest upstream kernel?"

None I am aware of.

>"Also, are you talking about installing /~kernel-ppa/mainline/daily/current ?"

The newest one mentioned in the article is http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc4-quantal/ .

[penalvch (penalvch)]

Sparhawk, in addition to providing information from https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995743/comments/2 , could you please execute your workaround at the Terminal:
sudo su -l
echo 1 > /sys/bus/pci/rescan

Then, execute the following at the Terminal and attach the result to this report:
lspci -vvnn

[Sparhawk (sparhawkthesecond)]

Christopher,
Thanks for the response. I'm not in a position to restart my computer at the moment, but I'll try installing the latest upstream kernel in the next few days. I followed your instructions in https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995743/comments/5 and I've attached the output.

[Sparhawk (sparhawkthesecond)]

Hi Christopher, I've now tested the latest upstream kernel at http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.5-rc4-quantal/ .

I'm not 100% sure if I did it right, so please tell me if it's okay. I installed the image and image-extra files, but not the headers. I thought I wouldn't need the headers as AFAIK I'm not "build[ing] any external modules". However, on installation of the two debs, I was told "Error! Error! Your kernel headers for kernel 3.5.0-030500rc4-generic cannot be found." Also, when I restarted using the new kernel, I got a whole bunch of AppArmor errors.

In any case (assuming I tested it correctly) this kernel did not solve my issues. I had to execute the workaround again.

[Sparhawk (sparhawkthesecond)]

FWIW I downloaded and installed the two headers files. I restarted and encountered no AppArmor errors, but this bug was still present.

[Sparhawk (sparhawkthesecond)]

Sorry, perhaps I was a little unclear. In the end, I installed the two header files after installing the image and image-extra files. So as per the instructions in the page you linked, I installed all *four* files. i.e. "the common headers, architecture specific headers, and the architecture specific image" and "a linux-image-extras package".
I've checked my Ubuntu system monitor, and it says "Kernel Linux 3.5.0-030500rc4-generic", so I presume it's okay now?

[Sparhawk (sparhawkthesecond)]

Right... so that's what I've already done. I've already installed all four packages. I've re-tagged the bug appropriately.

[penalvch (penalvch)]

Sparhawk, 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 the status. Thanks in advance.

Marking Triaged Low as mainline tested and multiple workarounds.

[Sparhawk (sparhawkthesecond)]

I know you told me to create a new bug report in launchpad rather than presuming it was a duplicate of https://bugs.launchpad.net/linux/+bug/969583 , but given that both bugs have been identified in the upstream kernel, is it proper to link the existing bug at https://bugzilla.kernel.org/show_bug.cgi?id=43041 ?

(Also, I don't totally understand the rationale in creating another bug report in launchpad, where it seems (to me) reasonably probable that they are duplicates. N.B. Someone else asked the same question here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/703180/comments/53 , but you must have missed it.)

Cheers.

[penalvch (penalvch)]

Sparhawk:
>"I know you told me to create a new bug report in launchpad rather than presuming it was a duplicate of https://bugs.launchpad.net/linux/+bug/969583..."

The rationale for this is from https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported .

>"...but given that both bugs have been identified in the upstream kernel, is it proper to link the existing bug at https://bugzilla.kernel.org/show_bug.cgi?id=43041 ?"

The fact both bugs are identified in the upstream kernel is weak correlation at best, not causation. We definitely have stronger correlation to similar vendor ID, similar model line, mfg. etc. However, it is exactly that. Despite this, hardware differences exist and it would be prudent to report a seperate report and let a developer make that call.

>"(Also, I don't totally understand the rationale in creating another bug report in launchpad, where it seems (to me) reasonably probable that they are duplicates."

Please see above link. As well, on 2012-06-26 I already tagged this report with "likely-dup" due to what we just discussed. Again, I'm letting a developer make that call.

>"N.B. Someone else asked the same question here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/703180/comments/53 , but you must have missed it.)"

Please do not presume I missed something because someone else does not understand the bug triaging process. It's up to my discretion to field every possible question fired at me due to ignorance of the bug triage process. If you have any further questions about the bug triage process, please take this to another forum (ex. https://answers.launchpad.net/ubuntu/+source/linux/+addquestion ), as this report should remain focused on the technical details of this report.

[Sparhawk (sparhawkthesecond)]

Thanks for the reply. That all makes sense. Also, I appreciate being directed to the proper channels, and think that this is a productive response in general. I'll file the kernel bug when I get a chance.

[Sparhawk (sparhawkthesecond)]

Oops, typo. It's at https://bugzilla.kernel.org/show_bug.cgi?id=44021

[Chris Ball (chris-ubuntu)]

Hi, I'm the upstream maintainer. Can you check that ACPI PCI hotplug is enabled in your kernel, and try forcing it on if it isn't? Thanks.

[Sparhawk (sparhawkthesecond)]

Hi Chris. Could you give me details on how to achieve this? Thanks.

[Jared Dominguez (jared-dominguez)]

I'm wondering if this is similar to LP #258446: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/258446

There is a work-around stated in comment 61 of that bug report.

[Chris Ball (chris-ubuntu)]

Sparhawk, the instructions are as linked to by Jared's comment.

Also please check for a BIOS update, thanks.

[ed_qta (eduardo-sotomayor)]

Solved on DELL Inspiron 6400
Added all of the following modules on /etc/modules , and after reboot, it showed uSD:

pciehp
acpiphp
jmb38x_ms
sdhci-pci
flash_bd
xd_card
jmb38x_xd

No need to recompile anything

[Sparhawk (sparhawkthesecond)]

None of that seems to have worked. I tried ed_qta's suggestion in comment #23 first. Then, I reverted that and tried the instructions from comment 61 linked here https://bugs.launchpad.net/ubuntu/+source/linux/+bug/258446/comments/61
Upon rebooting each time, neither showed the SD card as mounting when I inserted it. Just to check, is the script in the link (at /etc/modprobe.d/aspire-fix-sd-slots.conf ) specific to the author's computer? Also, when I copy-pasted, the script consisted of two lines. Firefox shows it as three for me, but when copy-pasting, the line break between "done;" and "/sbin/modprobe" disappeared. I figure that was just launchpad inserting in a confusing word-wrap.

Also, my BIOS is up to date.

[asgard2 (kamp000x)]

in the current kernel, the problem still exists
linux-image-3.6.0-030600rc2-generic_3.6.0-030600rc2.201208161835_amd64.deb
linux-image-extra-3.6.0-030600rc2-generic_3.6.0-030600rc2.201208161835_amd64.deb

[Sparhawk (sparhawkthesecond)]

FWIW, I used the SD card reader recently, using the workaround of "echo 1 > /sys/bus/pci/rescan" as root. Then, I noticed a few entries in dmesg similar to this:

[36964.574442] mmc0: Reset 0x4 never completed.
[36964.584408] mmc0: Controller never released inhibit bit(s).
[36964.683601] mmc0: Reset 0x2 never completed.
[36964.782781] mmc0: Reset 0x4 never completed.
[36964.792752] mmc0: Controller never released inhibit bit(s).
[36964.891997] mmc0: Reset 0x2 never completed.
[36964.991203] mmc0: Reset 0x4 never completed.
[36965.001173] mmc0: Controller never released inhibit bit(s).
[36965.100354] mmc0: Reset 0x2 never completed.
[36965.199537] mmc0: Reset 0x4 never completed.
[36965.209532] mmc0: Controller never released inhibit bit(s).
[36965.308750] mmc0: Reset 0x2 never completed.
[36965.407971] mmc0: Reset 0x4 never completed.
[36965.418103] mmc0: Controller never released inhibit bit(s).
[36965.517340] mmc0: Reset 0x2 never completed.
[36965.616556] mmc0: Reset 0x4 never completed.
[36965.715913] mmc0: Reset 0x1 never completed.

[Hibou57 (Yannick Duchêne) (yannick-duchene)]

Same issue for me, on Ubuntu Precise (12.04) and was already the same with Ubuntu Maverick.

Surprinsingly, when I boot with an SD card already in the slot, Ubuntu sees the SD card. If I remove it, then get it again in the slot, it works. In short, if there was an SD card at boot time, it's OK, otherwise, it is not.

[Hibou57 (Yannick Duchêne) (yannick-duchene)]

Oops, forget to tell: machine is a DELL Inspiron 9400.

[Hibou57 (Yannick Duchêne) (yannick-duchene)]

May be a workaround for some people: I gave a label to the SD Card (from Windows XP), then it works in Ubuntu. Don't know why, seems the lack of a label is an issue for the SD Card to be automatically recognized and mounted. I got the idea of the label from another place, but forget the link, sorry for not giving it.

[penalvch (penalvch)]

ed_qta / asgard2 / Hibou57, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it. Thank you for your understanding.

[Sparhawk (sparhawkthesecond)]

I've updated my BIOS to A18, and this problem is still present. The (second) workaround still works.

As per the testing as per comment 19, I've already tested and replied in comment 24.

[Sparhawk (sparhawkthesecond)]

Still broken under A19. (Second) workaround still works.

[penalvch (penalvch)]

Sparkhawk, could you please test the latest upstream kernel available (v3.8-rc1-raring) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. 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-rc1

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

[Vladimir Korenev (vkorenev)]

I tested 3.8.0-030800rc5-generic (amd64) kernel on my Dell L502X with Quantal. The bug is still there. An SD card is not detected until I execute sudo /bin/sh -c "echo 1 > /sys/bus/pci/rescan".

[penalvch (penalvch)]

Vladimir Korenev, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Ivan (ispmarin)]

Hi all,

I just read the bug report, and it seems that Vladimir Korenev followed all the steps to reproduce the bug. Now Christopher came and said that the bug is bios-outdated????

I have exactly the same issue with a XPS 15, done all the tests, and the bug still here. Could someone mark the bug as valid again, bios updated, and move it upstream?

Thanks

[Sparhawk (sparhawkthesecond)]

I don't fully understand the bug reporting in Ubuntu, but it seems to me that Ubuntu/Christopher require testing of every new kernel for this bug to remain valid, even if a fix has not been applied upstream. I guess there is the possibility that some random change of code has unintentionally fixed this bug.

I can't really commit to re-checking and restarting so frequently, especially since there are possible duplicates of this bug in Launchpad anyway. I expect that if this bug were targeted on the basis of one of these putatively duplicate reports, my bug would also be fixed. (Also, there is a workaround for my personal use anyway.) In addition, it seems that upstream aren't currently targeting the bug anyway, based on the bug I filed there. Also, if I understand correctly, then testing the bug to make it valid for Ubuntu/Christopher doesn't have any effect on its validity upstream.

[Ivan (ispmarin)]

Hi Sparhawk,

It seems that you are correct. I also don't have the time to keep testing each combination of kernel/bios update to see if it's working. It just feels a bit weird to wait for random change to fix this instead of trying to track it down and fix it. If the problem is upstream and Ubuntu is not going to do anything about it, then they could at least put the link for the upstream bug report so the person affected by this bug can track the progress there.

Could you please post the link for your upstream bug report?

Cheers

[Sparhawk (sparhawkthesecond)]

Hi Ivan, the link is in the bug info at the top of the page, where it says "Assigned to… linux-kernel-bugs #44021".
(It's http://bugzilla.kernel.org/show_bug.cgi?id=44021 )

[Ivan (ispmarin)]

Thanks! Gonna check it out and see if I can help there. There is a
workaround, I know, but is a tad annoying :-)

Cheers

2013/3/7 Sparhawk <email address hidden>

> Hi Ivan, the link is in the bug info at the top of the page, where it says
> "Assigned to… linux-kernel-bugs #44021".
> (It's http://bugzilla.kernel.org/show_bug.cgi?id=44021 )
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/995743
>
> Title:
> 197b:2394 Internal SD card reader is not working on Dell XPS 17 L502X
>
> Status in The Linux Kernel:
> Confirmed
> Status in “linux” package in Ubuntu:
> Confirmed
>
> Bug description:
> If I start up the computer with no SD card in the reader, it will not
> recognise SD cards inserted.
>
> WORKAROUND: If you start up the computer with an SD card inserted, all
> is good.
>
> WORKAROUND: The following rescan will find the SD card.
>
> sudo su -l
> echo 1 > /sys/bus/pci/rescan
>
> 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
> AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
> ApportVersion: 2.0.1-0ubuntu7
> Architecture: amd64
> ArecordDevices:
> **** List of CAPTURE Hardware Devices ****
> card 0: PCH [HDA Intel PCH], device 0: ALC665 Analog [ALC665 Analog]
> Subdevices: 1/1
> Subdevice #0: subdevice #0
> AudioDevicesInUse:
> USER PID ACCESS COMMAND
> /dev/snd/controlC0: lee 20624 F.... pulseaudio
> CRDA:
> country AU:
> (2402 - 2482 @ 40), (N/A, 20)
> (5170 - 5250 @ 40), (3, 23)
> (5250 - 5330 @ 40), (3, 23), DFS
> (5735 - 5835 @ 40), (3, 30)
> Card0.Amixer.info:
> Card hw:0 'PCH'/'HDA Intel PCH at 0xf3c00000 irq 55'
> Mixer name : 'Intel CougarPoint HDMI'
> Components : 'HDA:10ec0665,10280571,00100003
> HDA:80862805,80860101,00100000'
> Controls : 31
> Simple ctrls : 13
> Date: Mon May 7 13:52:09 2012
> HibernationDevice: RESUME=UUID=131e7674-2f9b-4de3-b917-8d79a5a64e28
> InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release amd64
> (20111012)
> MachineType: Dell Inc. Dell System XPS L702X
> ProcFB: 0 inteldrmfb
> ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-24-generic
> root=UUID=157174fa-f17e-471d-9008-353e4499b5f8 ro
> 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: Upgraded to precise on 2012-04-29 (7 days ago)
> dmi.bios.date: 01/10/2012
> dmi.bios.vendor: Dell Inc.
> dmi.bios.version: A16
> dmi.board.asset.tag: Base Board Asset Tag
> dmi.board.name: 0XN71K
> dmi.board.vendor: Dell Inc.
> dmi.board.version: FAB1
> dmi.chassis.type: 8
> dmi.chassis.vendor: Dell Inc.
> dmi.chassis.version: 0.1
> dmi.modalias:
> dmi:bvnDellInc.:bvrA16:bd01/10/2012:svnDellInc.:pnDellSystemXPSL702X:pvr:rvnDellInc.:rn0XN71K:rvrFAB1:cvnDe...

[Rael Gugelmin Cunha (rael-gc)]

Using 12.04 LTS updated, still no card automatically mounted.

[Rael Gugelmin Cunha (rael-gc)]

Guys, I tried the last JMicron driver, and it worked for some cards. Including automount.

See my comment here: http://ubuntuforums.org/showthread.php?t=1718934&p=12594006#post12594006

[asgard2 (kamp000x)]

I tried 13.04 with image 3.8.0.19 sd-slot is not working.

[penalvch (penalvch)]

Sparhawk, was this problem reproducible in a release prior to Precise? If so, which?

Rael / asgard2, if you have a bug in Ubuntu, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Please note, not filing a new report may delay your problem being addressed as quickly as possible.

Thank you for your understanding.

[Sparhawk (sparhawkthesecond)]

Precise was where I first noticed it, but I hadn't attempted using the SD card reader before then.

[Sparhawk (sparhawkthesecond)]

Christopher, I started from a Lucid live environment and the bug exists there. It's exactly as before. In addition, both workarounds work, as per the original bug post.

[Sparhawk (sparhawkthesecond)]

(I'm not sure what tags to change, so I might leave that for you to do.)

[Jógvan Olsen (jeggy)]

I have a Dell XPS 15 L502X also, and thanks a lot for the workaround :D

[Amente Bullo (amenteknows)]

I have a Dell XPS 15 L502X also. I am running precise1 with 3.5.0-34-generic and this bug still exists.

[Michael Aquilina (michaelaquilina)]

Running Kubuntu 12.04 with a Dell XPS l702x and i have the exact same bug. The workaround mentioned in the description works for me.

[Sparhawk (sparhawkthesecond)]

This is fixed for me in kernel v3.12-rc1, as per https://bugzilla.kernel.org/show_bug.cgi?id=44021

[LENHOF Jean-Yves (jean-yves)]

I can confirm that 3.12 kernel fix it... It is certainly better late than not at all.

[penalvch (penalvch)]

Sparhawk, thank you for testing v3.12-rc1. Could you please test Trusty via http://cdimage.ubuntu.com/daily-live/current/ and advise on if this is reproducible?

[asgard2 (kamp000x)]

I testet the current live image and lubuntu 64Bit (saucy) with kernel 3.13, it is working.

[Teo (teo1978)]

My Acer Aspire V3-571G does detect and mount the SD card when inserted but ONLY THE FIRST TIME.
After ejecting and removing it, when I insert it again nothing will happen.
The suggested pci rescan workaround does not work.

[penalvch (penalvch)]

matteo sisti sette, thank you for your comment. 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 a Ubuntu repository 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.

Thank you for your understanding.

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

[Sparhawk (sparhawkthesecond)]

I can confirm that it's also working fine in Trusty too, with kernel 3.13.0-24-generic. This can now be closed.

[penalvch (penalvch)]

Sparhawk, this bug report is being closed due to your last comment https://bugs.launchpad.net/ubuntu/+source/linux/+bug/995743/comments/62 regarding this being fixed with an update. For future reference you can manage the status of your own bugs by clicking on the current status in the yellow line and then choosing a new status in the revealed drop down box. You can learn more about bug statuses at https://wiki.ubuntu.com/Bugs/Status. Thank you again for taking the time to report this bug and helping to make Ubuntu better. Please submit any future bugs you may find.

[asgard2 (kamp000x)]

My sd card is not recognized with lubuntu 14.04 64bit and kernel 3.13.0-32.
Maybe not fixed at all?

[penalvch (penalvch)]

asgard2, thank you for your comment. Unfortunately, this bug report is closed, and isn't scoped to you or your hardware. 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.

Thank you for your understanding.

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

[hrna (hammett86)]

This bug still present on ubuntu 16.04 with kernel 4.4.0. At the moment i have no logs/reports to offer and sorry about that.

[Worik (worik-stanton)]

This is effecting me (or something similar) on:
~$ cat /etc/issue
Ubuntu Bionic Beaver (development branch)

But

# echo 1 > /sys/bus/pci/rescan has no effect

[Worik (worik-stanton)]

dmesg on inserting card

[Thu Jan 11 13:18:28 2018] mmc0: Timeout waiting for hardware interrupt.
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: ============ SDHCI REGISTER DUMP ===========
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Sys addr: 0x00000000 | Version: 0x00001502
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Blk size: 0x00007008 | Blk cnt: 0x00000001
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Argument: 0x00000000 | Trn mode: 0x00000013
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Present: 0x1fff0202 | Host ctl: 0x00000019
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Power: 0x0000000f | Blk gap: 0x00000000
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Wake-up: 0x00000000 | Clock: 0x0000fa07
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Timeout: 0x0000000a | Int stat: 0x00000000
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Int enab: 0x02ff008b | Sig enab: 0x02ff008b
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: AC12 err: 0x00000000 | Slot int: 0x00000000
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Caps: 0x176ec8b0 | Caps_1: 0x03002177
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Cmd: 0x0000333a | Max curr: 0x00000000
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Resp[0]: 0x00000920 | Resp[1]: 0x00000000
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Resp[2]: 0x00000000 | Resp[3]: 0x00000000
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: Host ctl2: 0x00000008
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: ADMA Err: 0x00000001 | ADMA Ptr: 0x0000000432665200
[Thu Jan 11 13:18:28 2018] mmc0: sdhci: ============================================
[Thu Jan 11 13:18:28 2018] mmc0: error -110 whilst initialising SD card
[Thu Jan 11 13:18:34 2018] mmc0: Skipping voltage switch

[asgard2 (kamp000x)]

The workaround is not working here too.

The report from 2014 is here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1367366

@penalvch
why no longer affects linux?

[penalvch (penalvch)]

asgard2 (kamp000x), this issue was addressed for the original reporter 3 years ago. Hence, it has nothing to do with your problem.

If you want your issue addressed, file a new report via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.