linux-kernel - Re: sdhci-pci fails on 3.0.0-rc1 on Dell E6510

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20110615165414.GA11421@ram-laptop>
Date:	Wed, 15 Jun 2011 09:54:14 -0700
From:	Ram Pai <linuxram@...ibm.com>
To:	Oliver Hartkopp <socketcan@...tkopp.net>
Cc:	Yinghai Lu <yinghai@...nel.org>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: sdhci-pci fails on 3.0.0-rc1 on Dell E6510

On Wed, Jun 15, 2011 at 06:40:35PM +0200, Oliver Hartkopp wrote:
> On 12.06.2011 22:44, Ram Pai wrote:
> > On Wed, Jun 08, 2011 at 08:26:14AM +0200, Oliver Hartkopp wrote:
> >> On 08.06.2011 00:18, Yinghai Lu wrote:
> >>> thanks.
> >>>
> >>> second report.
> >>>
> >>> can you send out whole boot log.
> >>
> >> See attached dmesg output. The 'dirty' is due to the revert test of the sd/mmc
> >> stuff (see below) - the rest is plain 3.0.0-rc2.
> >>
> >> Good luck :-)
> > 
> > Looks like the kernel; by default, tries to allocate mem resource of size
> > 0x4000000 each to the BARs of the cardbus bridge. This cannot be satisfied
> > meeting all the constraints. The BIOS had not allocated the resource to
> > begin with.
> > 
> > Anyone knows if the default value can be reduced to something smaller?
> > Or Should the resource requirements of cardbus bridge be made nice-to-have?
> 
> Don't know ...
> 
> Is anyone already working on this issue?
> 
> I'm currently running 3.0.0-rc3-00055-gada9c93 which still does not work.
> 
> Will say: 'Send more patches!' ... that i can test, if you still like the
> problematic commit's idea ;-)

Oliver,

	Yes. I am working on this. I will send you a patch soon; probably by
the end of this week. See if they work for you.

Currently my thought is to make cardbus-bridge resource allocation
nice-to-have, which means it will be attempted to allocate. But if in case of
failures, we wont go the full length of releasing other resources to satisfy
this resource.


RP
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/