LinuxQuestions.org - SD Cards not working in FC17

- Linux - Newbie (https://www.linuxquestions.org/questions/linux-newbie-8/)

- - SD Cards not working in FC17 (https://www.linuxquestions.org/questions/linux-newbie-8/sd-cards-not-working-in-fc17-4175444851/)

SD Cards not working in FC17

On my Acer Aspire One 756-2623 netbook running Fedora Core 17 I am having trouble mounting SD Cards. Once in a while if I do a cold boot with an SD card in the drive I will be able to see it after the system boots. Below is all the steps I have taken and diagnostic data I can think of and find on this and Fedora Core's forums. I appreciate any suggestions you can make.

Code:

# uname -a

Linux localhost.localdomain 3.6.11-1.fc17.x86_64 #1 SMP Mon Dec 17 22:16:35 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux



# whoami

root



# lspci -v

04:00.1 SD Host controller: Broadcom Corporation NetXtreme BCM57765 Memory Card Reader (rev 10) (prog-if 01)

        Subsystem: Acer Incorporated [ALI] Device 0742

        Flags: bus master, fast devsel, latency 0, IRQ 19

        Memory at 90400000 (64-bit, prefetchable) [size=64K]

        Capabilities: [48] Power Management version 3

        Capabilities: [58] MSI: Enable- Count=1/1 Maskable- 64bit+

        Capabilities: [ac] Express Endpoint, MSI 00

        Capabilities: [100] Advanced Error Reporting

        Capabilities: [150] Power Budgeting <?>

        Capabilities: [160] Virtual Channel

        Kernel driver in use: sdhci-pci



# lsmod | grep pci

sdhci_pci              18658  0 

sdhci                  37836  1 sdhci_pci



# yum whatprovides *\sdhci-pci*

kernel-3.6.11-1.fc17.x86_64 : The Linux kernel

Repo        : @updates

Matched from:

Filename    : /lib/modules/3.6.11-1.fc17.x86_64/kernel/drivers/mmc/host/sdhci-pci.ko

remove card

Code:

# modprobe -r sdhci

# modprobe -r sdhci-pci

# modprobe sdhci

# modprobe sdhci-pci



# dmesg

[ 1831.490062] sdhci: Secure Digital Host Controller Interface driver

[ 1831.490066] sdhci: Copyright(c) Pierre Ossman

[ 1833.608042] sdhci-pci 0000:04:00.1: SDHCI controller found [14e4:16bc] (rev 10)

[ 1833.608113] sdhci-pci 0000:04:00.1: Invalid iomem size. You may experience problems.

[ 1833.608390] Registered led device: mmc0::

[ 1833.637775] mmc0: SDHCI controller on PCI [0000:04:00.1] using ADMA

Insert Card

Code:

# dmesg

[ 1935.988186] mmc0: Timeout waiting for hardware interrupt.

[ 1946.002967] mmc0: Timeout waiting for hardware interrupt.

"Invalid iomem size. You may experience problems."
I would have a look at boot parameters for using one for your subject
http://www.mjmwired.net/kernel/Docum...parameters.txt
quirks.. pci.. related to iomem..?
Just an idea (one time I had a SD card making few messages during boot and the messages could disappear by using a boot code; this was NOT your issue here.. but perhaps a similar topic?).

From what you just sent me [MSI Message Signaled Interrupts (PCI)] looks interesting as it relates to a different way PCI uses interupts? I will have to see if using this option has makes any change. Thanks for your reply I will report back.

pci=nomsi did not work for this issue out of the box. After I put the system to sleep for a long period and woke it up it did see the card in the drive. I am uncertain if it was due to the option or unrelated. I will have to do some more testing. Any more ideas would be appreciated.

disconnect interrupt routing with a bootparameter?
according google "timeout waiting for hardware interrupt", the issue seems a kernel issue; so, a kernel parameter could solve? Which one? dont know. I will read a bit more when I have time and post here again if I have another idea.

I tried debug_quirks=0x40 without success.

I did find that if I plug in Ethernet cable it works perfectly. The wired network also must be enabled it appears.

Great.
Post both dmesg.txt (in a terminal make dmesg > dmesg.txt) here after
1. boot without LAN cable (your SD card has issues)
2. boot with LAN cable (SD card recognized)
We should look at the differences and try to understand what is going on (in relation with LAN card activation).

I started a look at the boot parameters.. quick guess would be
apci=noirq or acpi_irq_balance
acpi_irq_pci="IRQ" where the "IRQ" the IRQ is when your cable is in.
I dont have the HW, so Im a bit in the dark.

or.. Bug? have a look at https://bugs.launchpad.net/ubuntu/+s...x/+bug/1067222
A bug report says "apport-bug bios-outdated i386 kernel-bug-exists-upstream kernel-bug-exists-upstream-v3.6.2-quantal needs-firmware-check precise regression-release running-unity staging". Perhaps a workaround exists before the kernel is upgraded.

or here http://osdir.com/ml/ubuntu-bugs/2013-01/msg01739.html "In addition I had a talk with a nice gui with broadcom-knowledgeâ.
It looks like this card has an additional (private) mmio-block above the
normal 0x100 bytes in the PCI bar." Im scratching my (small) head to understand how to go around it. Contact these guys? or broadcom; they should know a workaround?

Sorry I have been traveling. I will try to put a dmesg up here soon. I think this is a bug at this point, I am just unsure were to file it, Fedora does not seam to be appropriate as it is somewhat crossing the distribution divide. Thanks for your continued help.