Kernel Bug Tracker – Bug 37432
sdhci-pci fails on 3.0.0-rc1 on Dell E6510
Last modified: 2011-08-28 19:18:03 UTC
Subject : sdhci-pci fails on 3.0.0-rc1 on Dell E6510
Submitter : Oliver Hartkopp <firstname.lastname@example.org>
Date : 2011-06-07 20:06
References : http://article.gmane.org/gmane.linux.kernel.mmc/8442
This entry is being used for tracking a regression from 2.6.39. Please don't
close it until the problem is fixed in the mainline.
First-Bad-Commit : da7822e5ad71ec9b745b412639f1e5e0ba795a20
Author: Yinghai Lu <email@example.com>
Date: Thu May 12 17:11:37 2011 -0700
PCI: update bridge resources to get more big ranges when allocating space (again)
With Ram's fixes, this should be safe to do again. So let's give it
BIOS separates IO ranges between several IOHs, and on some slots, BIOS
assigns resources to a bridge, but stops assigning resources to the
device under that bridge, because the device needs a big resource.
1. allocate resources and record the failed device resources
2. clear the BIOS assigned resources of the parent bridge of failing device
3. go back and call pci assign unassigned
4. if it still fails, go up the tree, clear more bridges. and try again
Now Ram's allocate requested resource already got into mainline. could
put this one again.
Reviewed-by: Ram Pai <firstname.lastname@example.org>
Signed-off-by: Yinghai Lu <email@example.com>
Signed-off-by: Jesse Barnes <firstname.lastname@example.org>
On Monday, August 15, 2011, Oliver Hartkopp wrote:
> On 14.08.2011 21:02, Rafael J. Wysocki wrote:
> > This message has been generated automatically as a part of a report
> > of regressions introduced between 2.6.39 and 3.0.
> > The following bug entry is on the current list of known regressions
> > introduced between 2.6.39 and 3.0. Please verify if it still should
> > be listed and let the tracking team know (either way).
> > Bug-Entry : http://bugzilla.kernel.org/show_bug.cgi?id=37432
> > Subject : sdhci-pci fails on 3.0.0-rc1 on Dell E6510
> > Submitter : Oliver Hartkopp <email@example.com>
> > Date : 2011-06-07 20:06 (69 days old)
> the regression has been solved for 3.0 by disabling the problematic code here:
> When the new commandline argument 'pci=realloc' is not set (which is the
> default) the buggy code is disabled.
> Therefore this bug can be closed on the 2.6.39 -> 3.0 regression list.