Macbook Pro Retina 11,1 SD Card Reader Doesn't Work

Bug #1531653 reported by Randy Syring
40
This bug affects 6 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

I have a Macbook Pro (MBP) Retina 11,1 with an SD card reader that will not work.

The SD card reader:

* has device code 05ac:8406
* does work in OS X.
* does not work in SystemRescueCD running kernel 3.14.56-std461-amd64
    - I have a friend with an identical Macbook Pro and his SD card reader does work in SystemRescueCD
* Does not show up in lsusb
* Does not display any messages in dmesg when an SD card is inserted
* Device 05ac:8406 does not show up in dmesg
* Does not work in kernel 4.2.0-22.27~14.04.1. All issues reported here seem to be the same regardless if I use 3.13 or 4.2.
* Uses the following drivers on my friends MBP: sd, usb-storage, usb, xhci_hcd

The last point made me look closer at the xhci_hcd logs:

rsyring@loftex:~$ dmesg | grep xhci_hcd
[ 2.681478] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 2.681498] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 1
[ 2.681589] xhci_hcd 0000:00:14.0: cache line size of 256 is not supported
[ 2.681607] xhci_hcd 0000:00:14.0: irq 63 for MSI/MSI-X
[ 2.681755] usb usb1: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
[ 2.682098] xhci_hcd 0000:00:14.0: xHCI Host Controller
[ 2.682115] xhci_hcd 0000:00:14.0: new USB bus registered, assigned bus number 2
[ 2.682219] usb usb2: Manufacturer: Linux 3.13.0-57-generic xhci_hcd
[ 3.980423] usb 2-1: new SuperSpeed USB device number 2 using xhci_hcd
[ 9.352422] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 14.560476] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 20.549170] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 25.757227] xhci_hcd 0000:00:14.0: Timeout while waiting for address device command
[ 26.129482] usb 1-1: new high-speed USB device number 2 using xhci_hcd
[ 26.321707] usb 1-3: new full-speed USB device number 3 using xhci_hcd
[ 26.505802] usb 1-5: new full-speed USB device number 4 using xhci_hcd
[ 26.603224] usb 2-1.1: new SuperSpeed USB device number 6 using xhci_hcd
[ 26.754245] usb 1-1.2: new low-speed USB device number 5 using xhci_hcd
[ 26.954315] usb 1-1.4: new low-speed USB device number 6 using xhci_hcd
[ 27.050323] usb 1-3.1: new full-speed USB device number 7 using xhci_hcd
[ 27.142383] usb 1-3.2: new full-speed USB device number 8 using xhci_hcd
[ 27.234476] usb 1-3.3: new full-speed USB device number 9 using xhci_hcd
[ 81.685139] usb 1-1.4: new low-speed USB device number 10 using xhci_hcd

The "Timeout while waiting" messages are suspicious to me. dmesg on my friend's MBP does not show those messages.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-57-generic 3.13.0-57.95
ProcVersionSignature: Ubuntu 3.13.0-57.95-generic 3.13.11-ckt21
Uname: Linux 3.13.0-57-generic x86_64
NonfreeKernelModules: wl zfs zunicode zcommon znvpair zavl
ApportVersion: 2.14.1-0ubuntu3.19
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: rsyring 5051 F.... pulseaudio
 /dev/snd/controlC0: rsyring 5051 F.... pulseaudio
CurrentDesktop: XFCE
Date: Wed Jan 6 17:57:28 2016
HibernationDevice: RESUME=UUID=8b8a41c8-2030-4f92-b7d6-1143a081ec85
InstallationDate: Installed on 2014-02-15 (690 days ago)
InstallationMedia: Xubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016)
MachineType: Apple Inc. MacBookPro11,1
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: \vmlinuz-3.13.0-57-generic.efi.signed root=ZFS=/ROOT ro libata.force=noncq cryptopts=target=cryptdev,source=/dev/disk/by-uuid/6993c5ec-7308-420d-bbe2-1ed18c15e2bc,discard boot=zfs initrd=\initrd.img-3.13.0-57-generic
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-57-generic N/A
 linux-backports-modules-3.13.0-57-generic N/A
 linux-firmware 1.127.19
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-07-21 (534 days ago)
dmi.bios.date: 09/08/2015
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP111.88Z.0138.B16.1509081438
dmi.board.asset.tag: Base Board Asset Tag#
dmi.board.name: Mac-189A3D4F975D5FFC
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro11,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.version: Mac-189A3D4F975D5FFC
dmi.modalias: dmi:bvnAppleInc.:bvrMBP111.88Z.0138.B16.1509081438:bd09/08/2015:svnAppleInc.:pnMacBookPro11,1:pvr1.0:rvnAppleInc.:rnMac-189A3D4F975D5FFC:rvrMacBookPro11,1:cvnAppleInc.:ct10:cvrMac-189A3D4F975D5FFC:
dmi.product.name: MacBookPro11,1
dmi.product.version: 1.0
dmi.sys.vendor: Apple Inc.

Revision history for this message
Randy Syring (rsyring) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.4 kernel[0].

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'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.4-rc8-wily

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Randy Syring (rsyring) wrote :

> Did this issue start happening after an update/upgrade? Was there a prior kernel version where you were not having this particular problem?

This is the first time I've tried using the SD card. So I can't say if any system changes have affected it.

However, the fact that my SD card reader doesn't show up when booted into SystemRescueCD, and it does show up when booted into my friends MBP, makes me think it's not a system configuration issue.

> Would it be possible for you to test the latest upstream kernel?

I tried, but I'm using a ZFS filestystem for my root. I tried to build but I guess there are issues due to my relying on "out of tree" modules. I'm not familiar enough with building kernels to know how to proceed at this point. If you could point to instructions that would tell me how to use a mainline kernel with my dkms zfs module (so I can boot), I'd be happy to give it a try.

Revision history for this message
penalvch (penalvch) wrote :

Randy Syring, it would be helpful to test for this in a live environment via http://cdimage.ubuntu.com/daily-live/current/ . Could you please advise?

Revision history for this message
Randy Syring (rsyring) wrote :

Christopher Penalver, I have downloaded today's ISO and booted my laptop with it. No changes noted. Inserting an SD card did show any messages in dmesg and the card reader device does not show up in lsusb or dmesg.

Revision history for this message
penalvch (penalvch) wrote :

Randy Syring, the next step would be to install Ubuntu to another partition with default settings (i.e. no out-of-tree modules) if you need to preserve the original install.

Once this is in place, at your earliest convenience, could you please test the latest upstream kernel available from the very top line at the top of the page from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D (the release names are irrelevant for testing, and please do not test the daily folder)? Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds . This will allow additional upstream developers to examine the issue.

If the latest kernel did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Once testing of the latest upstream kernel is complete, please mark this report's Status as Confirmed. Please let us know your results.

Thank you for your understanding.

tags: added: xenial
Revision history for this message
Jerome Kieffer (jerome-kieffer) wrote :

I have a MacBook Pro 13" from 2013, running Debian8 with the backported kernel (4.2).
The SD-card reader works randomly: sometimes it is perfectly recognized at boot and works as expected without a glitch as long as you don't suspend/restart the computer.

But most of the time (>50% of the boot) the card reader is not recognized. Then inserting a card, nothing in dmesg, not seen in the lsusb, ... and there is a "timeout" message about xhci-hcd (USB3 driver).

Are there option to load xhci with longer timeout ?

Cheers,

Jerome

Revision history for this message
graingert (tagrain) wrote :

according to the fedora bug it's working better in 4.6.6

Revision history for this message
graingert (tagrain) wrote :

I've also tried setting:

options xhci_hcd quirks=0x80

in /etc/modprobe.d/xhci-reset-on-suspend.conf but that doesn't work for me either.

https://wiki.archlinux.org/index.php/User:Elinux/MacBook_Pro_12,1#SD_Card_Reader

penalvch (penalvch)
no longer affects: linux (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

graingert, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

affects: linux (Debian) → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
graingert (tagrain) wrote :
Revision history for this message
graingert (tagrain) wrote :

Still doesn't work on 4.4.0-9136-generic

Revision history for this message
graingert (tagrain) wrote :

@penalvch doesn't work on 4.8.0-17-generic

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
graingert (tagrain) wrote :
Revision history for this message
graingert (tagrain) wrote :

the SD card is USB 2-3:

[ 18.656434] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ 23.529455] random: fast init done
[ 24.032360] xhci_hcd 0000:00:14.0: Timeout while waiting for setup device command
[ 24.240351] usb 2-3: device not accepting address 3, error -62

Revision history for this message
penalvch (penalvch) wrote :

graingert, you would want to make your comments in the report you made to keep the reports focused on their respective original reporters, and their hardware.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in fedora:
importance: Unknown → Low
status: Unknown → Confirmed
Revision history for this message
penalvch (penalvch) wrote :
no longer affects: linux (Ubuntu)
affects: fedora → linux (Ubuntu)
Changed in linux (Ubuntu):
importance: Low → Undecided
status: Confirmed → New
importance: Undecided → Medium
status: New → Incomplete
Revision history for this message
Randy Syring (rsyring) wrote :

Christopher M. Penalver,

Regarding the request in comment #7, I don't think I have the skill or patience to go through all that work. This laptop is almost EOL for me anyway. Sorry, if you are only holding this bug open for me to do that work and report back, feel free to close it. I wish I could be more help, but I just don't have the time to mess with this kind of stuff like I used to.

Thanks for your help.

Revision history for this message
penalvch (penalvch) wrote :

Randy Syring, we can see what can be done anyways without it. However, please keep expectations reasonable as not testing the upstream kernel limits the probability of getting this addressed as fast as possible.

With this in mind:
1) Do you have the 2013 or 2014 model as per https://support.apple.com/en-us/HT201518 ?
2) To see if this is resolved in Ubuntu, could you please test the latest live Ubuntu via http://cdimage.ubuntu.com/daily-live/current/ and advise to the results?
3) Do you have a dual-boot of macOS and Ubuntu? If so, is the latest version of macOS installed?

Revision history for this message
Jim Hodapp (jhodapp) wrote :

I'm able to help test if that's helpful to anybody. I've got a mid-2015 MB Pro but I don't have the latest OS X installed (one off of latest) and I rarely ever boot into it.

Revision history for this message
penalvch (penalvch) wrote :

Jim Hodapp, in order to review hardware and logs, it will be most helpful if you filed a new report with Ubuntu via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

Revision history for this message
Jim Hodapp (jhodapp) wrote :

@Christopher: created bug #1730505

Revision history for this message
Randy Syring (rsyring) wrote :

FWIW, I recently got a new computer and finally took the MBP into Apple to run some diagnostics. The internal hardware diagnostics never found anything wrong. However, when I took it to Apple, they had some more advanced diagnostics that immediately identified a problem with my SD card reader. Interesting that the reader still worked with MacOS.

I'm giving the laptop to my son who wants to run MacOS and not Linux, so I won't be able to contribute to this issue anymore. Thanks to those who put effort into it.

Revision history for this message
Eugene Trotsan (eugene-trotsan-o) wrote :

This issue has been bugging me for 2.5 years since I got the machine - as the 256GB JetDrive becomes useless after resume from sleep.

Do we know what's causing this yet and any workarounds?

Thanks

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

@Eugene,

Please file a new bug if your machine is not MBPR 11,1.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.