Description of problem: Error message on boot - mmc0: Unknown controller version (3). You may experience problems. Version-Release number of selected component (if applicable): Linux e6540 4.0.0-0.rc4.git0.1.fc22.x86_64 How reproducible: Occurs every boot Steps to Reproduce: 1. Restart or power up with Linux e6540 4.0.0-0.rc4 2. 3. Actual results: Error message mmc0: Unknown controller version (3). You may experience problems. Expected results: No error message Additional info: Sounds a bit like this bug reported in arch https://bugs.archlinux.org/task/38628
A workaround is to boot the old f21 kernel: Linux e6540 3.19.1-201.fc21.x86_64 Doesn't have the problem
Still Occuring with kernel 4.0.0-1.fc22.x86_64
Still occurs in 4.0.4-301.fc22.x86_64
Happening on Dell Precision M4800 w/i7-4940MX CPU and kernel-4.0.4-201.fc21. This wasn't happening in kernel-3.19.7-200.fc21. 11:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) (prog-if 01) Subsystem: Dell Device 05cc Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at f6f01000 (32-bit, non-prefetchable) [size=4K] Memory at f6f00000 (32-bit, non-prefetchable) [size=2K] Capabilities: [6c] Power Management version 3 Capabilities: [48] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [230] Latency Tolerance Reporting Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci
Still occurs with kernel 4.0.4-303.fc22.x86_64 on dell E6540
The problem is still occurs with kernel 4.0.6-200.fc21.x86_64 (I'm on Dell Latitude E6540). Same controller as Allen: 0e:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) (prog-if 01) Subsystem: Dell Device 05be Flags: bus master, fast devsel, latency 0, IRQ 19 Memory at f7a01000 (32-bit, non-prefetchable) [size=4K] Memory at f7a00000 (32-bit, non-prefetchable) [size=2K] Capabilities: [6c] Power Management version 3 Capabilities: [48] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [230] Latency Tolerance Reporting Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci This time nobody seems to be in hurry to patch the 4.0 kernels and fix this bug.
Seeing this on Lenovo Thinkpad W541 with 4.1.3-201.fc22.x86_64: 02:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) (prog-if 01) Subsystem: Lenovo Device 2211 Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at b2901000 (32-bit, non-prefetchable) [size=4K] Memory at b2900000 (32-bit, non-prefetchable) [size=2K] Capabilities: [6c] Power Management version 3 Capabilities: [48] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [230] Latency Tolerance Reporting Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci However it does seem to be reading SD cards ok.
Can anyone actually associate any real problems with this informational message? The fact that at some point the kernel added a message actually telling you about the unknown controller version does not imply that it will work any better or worse than a kernel that did not print the message. The message itself does not indicate an actual problem, dnd its presence does not constitute a bug. Also, could someone attach a full lspci and a complete dmesg? If there is an actual kernel problem underlying this issue, having a more complete set of information will help the kernel team. Also, if anyone is willing to try the current f23 or rawhide kernels, that would be useful as well.
Created attachment 1064520 [details] lspci output
Created attachment 1064521 [details] dmesg output
Comment on attachment 1064520 [details] lspci output I'm attaching the lspci output from my system. Kernel version: 4.1.4-100.fc21.x86_64
Created attachment 1064576 [details] lspci output from w541
(In reply to Jason Tibbitts from comment #8) > Can anyone actually associate any real problems with this informational > message? Yes, Boot is stuck on this message. I can only continue by escaping. Does not sound like a normal boot flow. BTW I have encrypted my hard drive, using Lenovo Thinkpad W541.
For me the message displays but doesn't stop the boot process, just looks ugly so I assume the system doesn't consider it to be simply informational, otherwise you wouldn't see it on a graphical boot up. That said I don't see any further issues. Happens with every 4.x kernel delivered via fedora updates so far.
Created attachment 1066305 [details] lspci from Dell Latitude E6540
Created attachment 1066308 [details] Output of journalctl -b up to the last mmc message
Re comment #13, I don't think boot being stuck is related to this, the problem you're seeing is due to the disk encryption dialog not coming up and no text propmpt for it until you hit escape, this is partially covered in bug #1231310. I think there is another bug related to the disk encryption password prompt as well but I can't find it now.
(In reply to John Dennis from comment #17) > Re comment #13, I don't think boot being stuck is related to this, the > problem you're seeing is due to the disk encryption dialog not coming up and > no text propmpt for it until you hit escape, this is partially covered in > bug #1231310. I think there is another bug related to the disk encryption > password prompt as well but I can't find it now. Yes, I almost agree with this. This message does not in itself appear to be associated with a functional problem (that I can see). However it does appear on the boot screen and somehow it is not being captured and put in the boot log as all other boot time messages are. This is the actual bug AFAICT. I'm guessing that without this bug, then on the affected machines with encrypted disks the boot would just appear to stop with no message at all!
Some more info: I don't have the graphical screen to enter the encryption passphrase, only a cmd line asking for it (though this is a workstation installation). Entering the passphrase before being asked for it when the above message appears doesn't prompt the passphrase line, and the boot process proceeds.
I confirm what Vared says. The reason it may appear to be hung is, at least in my case, this message appears and the plymouth passphrase prompt for my dm-crypt disk *does not* appear so the machine *seems* to be hung. I need to hit esc to get to the text display and then I can see the prompt for the passphrase, enter it and continue booting.
Hi, My F22 kernel just went from 4.1.6-200.fc22 to 4.1.6-201.fc22 thanks to the F22 updates and the system failed to boot fully. The above message being the last one seen on the console: mmc0: Unknown controller version (3). You may experience problems. This is on a Lenovo W541 workstation. Reverting back to 4.1.6-200 from the Grub menu works.. I'll see if I can check the issue more fully.. Regards,
False positive, sorry. System is fine with 4.1.6-201.fc22. This may have been related to my setup.
*********** MASS BUG UPDATE ************** We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. Due to this, we are doing a mass bug update across all of the Fedora 22 kernel bugs. Fedora 22 has now been rebased to 4.2.3-200.fc22. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 23, and are still experiencing this issue, please change the version to Fedora 23. If you experience different issues, please open a new bug report for those.
Still present in 4.2.3-200.fc22.x86_64
And also still there in 4.2.3-300.fc23.x86_64
Here is how I was able to solve it, * boot to single user mode * telinit 3 (load the level 3 - this works for me) * just update the entire system (sudo dnf update) problem solved... ( at least this is what worked for me )
Still there in 4.3.3-301.fc23.x86_64. See bz1289981 for the f23 bug which has some information on a potential workaround (if you don't use the card reader) and also a potential upstream fix.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Hi there, The bug is still present or at least has re-appeared on Fedora 24. I'm at kernel 4.8.15-200.fc24.x86_64 but I'm having this error with the past 3 or 4 kernels already. No sure if they are related but I'm also having this other error at the boot: radeon 0000:01:00.0: failed VCE resume (-110).
Having same message on F25: [ 1.829199] sdhci-pci 0000:03:00.0: SDHCI controller found [1217:8520] (rev 1) [ 1.831198] mmc0: Unknown controller version (3). You may experience problems. [ 1.842722] mmc0: SDHCI controller on PCI [0000:03:00.0] using ADMA kernel: 4.9.4-201.fc25.x86_64 #1 SMP Tue Jan 17 18:58:54 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux # lspci -v -s 03:00.0 03:00.0 SD Host controller: O2 Micro, Inc. SD/MMC Card Reader Controller (rev 01) (prog-if 01) Subsystem: Dell Device 05cb Flags: bus master, fast devsel, latency 0, IRQ 16 Memory at f7c01000 (32-bit, non-prefetchable) [size=4K] Memory at f7c00000 (32-bit, non-prefetchable) [size=2K] Capabilities: [6c] Power Management version 3 Capabilities: [48] MSI: Enable- Count=1/1 Maskable+ 64bit+ Capabilities: [80] Express Endpoint, MSI 00 Capabilities: [100] Virtual Channel Capabilities: [200] Advanced Error Reporting Capabilities: [230] Latency Tolerance Reporting Capabilities: [240] L1 PM Substates Kernel driver in use: sdhci-pci Kernel modules: sdhci_pci
Same issue on F25 with kernel: uname -a Linux Fedora.localdomain 4.10.10-200.fc25.x86_64 #1 SMP Thu Apr 13 01:11:51 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux
On a Dell M4800 laptop, w/ Quadro K2100M. Latest nvidia drivers installed. Get this at startup, but continues to log-in screen. Go to log in, but then screen goes black. On Fedora 28. latest kernel.
On a Thinkpad E480 bought 2 months ago, I've the same message at each boot on F28.
Also get this on startup on 4.17.12-200.fc28.x86_64 (dell Latitude e6540)