kernel-packages team mailing list archive

["Christopher M. Penalver" <christopher.m.penalver@xxxxxxxxx>]

Wolf Rogner, if you revert the following commit via https://wiki.ubuntu.com/Kernel/KernelBisection , does your card begin to work again:
df89d48a8cbdc23578397c6e62d5c9c9e630c610 is the first bad commit
commit df89d48a8cbdc23578397c6e62d5c9c9e630c610
Author: Matthew Garrett <mjg@xxxxxxxxxx>
Date: Thu Nov 10 16:38:33 2011 -0500

    PCI: Rework ASPM disable code

    BugLink: http://bugs.launchpad.net/bugs/927848

    commit 3c076351c4027a56d5005a39a0b518a4ba393ce2 upstream.

    Right now we forcibly clear ASPM state on all devices if the BIOS indicates
    that the feature isn't supported. Based on the Microsoft presentation
    "PCI Express In Depth for Windows Vista and Beyond", I'm starting to think
    that this may be an error. The implication is that unless the platform
    grants full control via _OSC, Windows will not touch any PCIe features -
    including ASPM. In that case clearing ASPM state would be an error unless
    the platform has granted us that control.

    This patch reworks the ASPM disabling code such that the actual clearing
    of state is triggered by a successful handoff of PCIe control to the OS.
    The general ASPM code undergoes some changes in order to ensure that the
    ability to clear the bits isn't overridden by ASPM having already been
    disabled. Further, this theoretically now allows for situations where
    only a subset of PCIe roots hand over control, leaving the others in the
    BIOS state.

    It's difficult to know for sure that this is the right thing to do -
    there's zero public documentation on the interaction between all of these
    components. But enough vendors enable ASPM on platforms and then set this
    bit that it seems likely that they're expecting the OS to leave them alone.

    Measured to save around 5W on an idle Thinkpad X220.

    Signed-off-by: Matthew Garrett <mjg@xxxxxxxxxx>
    Signed-off-by: Jesse Barnes <jbarnes@xxxxxxxxxxxxxxxx>
    Signed-off-by: Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>
    Signed-off-by: Tim Gardner <tim.gardner@xxxxxxxxxxxxx>

** Tags added: likely-dup

** Changed in: linux (Ubuntu)
       Status: Confirmed => Incomplete

** Summary changed:

- 14e4:16bc SD Card does not work
+ 14e4:16bc [MacBookPro10,1] SD Card does not work

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1225652

Title:
  14e4:16bc [MacBookPro10,1] SD Card does not work

Status in “linux” package in Ubuntu:
  Incomplete

Bug description:
  Sep 15 12:58:25 mbr kernel: [  125.834315] mmc0: error -110 whilst initialising SD card
  Sep 15 12:58:27 mbr kernel: [  127.260464] mmc0: Switching to 1.8V signalling voltage failed, retrying with S18R set to 0
  Sep 15 12:58:51 mbr kernel: [  151.629144] mmc0: error -110 whilst initialising SD card
  Sep 15 12:59:00 mbr kernel: [  160.837187] mmc0: Switching to 1.8V signalling voltage failed, retrying with S18R set to 0

  It works on a  plain old HP8510w, on a MacBook Pro 6,2 but not on the
  new 15" Retina 10,2

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: linux-image-3.8.0-31-generic 3.8.0-31.46
  ProcVersionSignature: Ubuntu 3.8.0-31.46-generic 3.8.13.8
  Uname: Linux 3.8.0-31-generic x86_64
  NonfreeKernelModules: wl nvidia
  ApportVersion: 2.9.2-0ubuntu8.4
  Architecture: amd64
  AudioDevicesInUse:
   USER        PID ACCESS COMMAND
   /dev/snd/controlC1:  wolf       2792 F.... pulseaudio
   /dev/snd/controlC0:  wolf       2792 F.... pulseaudio
  CRDA:
   country DE:
   	(2400 - 2483 @ 40), (N/A, 20)
   	(5150 - 5250 @ 40), (N/A, 20), NO-OUTDOOR
   	(5250 - 5350 @ 40), (N/A, 20), NO-OUTDOOR, DFS
   	(5470 - 5725 @ 40), (N/A, 26), DFS
  Date: Sun Sep 15 13:30:41 2013
  HibernationDevice: RESUME=UUID=82dd2ca4-5c1e-43dc-b83e-d93e6166e5c4
  InstallationDate: Installed on 2013-05-17 (120 days ago)
  InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Release amd64+mac (20130424)
  MachineType: Apple Inc. MacBookPro10,1
  MarkForUpload: True
  ProcFB: 0 VESA VGA
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.8.0-31-generic root=UUID=3679e976-6405-4981-aa99-8c79d15e6aa3 ro quiet splash vt.handoff=7
  RelatedPackageVersions:
   linux-restricted-modules-3.8.0-31-generic N/A
   linux-backports-modules-3.8.0-31-generic  N/A
   linux-firmware                            1.106
  SourcePackage: linux
  UpgradeStatus: No upgrade log present (probably fresh install)
  dmi.bios.date: 12/21/2012
  dmi.bios.vendor: Apple Inc.
  dmi.bios.version: MBP101.88Z.00EE.B03.1212211437
  dmi.board.asset.tag: Base Board Asset Tag#
  dmi.board.name: Mac-C3EC7CD22292981F
  dmi.board.vendor: Apple Inc.
  dmi.board.version: MacBookPro10,1
  dmi.chassis.type: 10
  dmi.chassis.vendor: Apple Inc.
  dmi.chassis.version: Mac-C3EC7CD22292981F
  dmi.modalias: dmi:bvnAppleInc.:bvrMBP101.88Z.00EE.B03.1212211437:bd12/21/2012:svnAppleInc.:pnMacBookPro10,1:pvr1.0:rvnAppleInc.:rnMac-C3EC7CD22292981F:rvrMacBookPro10,1:cvnAppleInc.:ct10:cvrMac-C3EC7CD22292981F:
  dmi.product.name: MacBookPro10,1
  dmi.product.version: 1.0
  dmi.sys.vendor: Apple Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1225652/+subscriptions