From: Oliver Hartkopp <socketcan@hartkopp.net>
To: Chris Ball <cjb@laptop.org>
Cc: "S\, Venkatraman" <svenkatr@ti.com>,
linux-mmc <linux-mmc@vger.kernel.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: sdhci-pci fails on 3.0.0-rc1 on Dell E6510
Date: Tue, 07 Jun 2011 20:36:54 +0200 [thread overview]
Message-ID: <4DEE6FC6.9040308@hartkopp.net> (raw)
In-Reply-To: <m3hb82wx6m.fsf@pullcord.laptop.org>
On 06.06.2011 21:56, Chris Ball wrote:
> Hi Oliver,
>
> On Mon, Jun 06 2011, Oliver Hartkopp wrote:
>>>> dmesg is a bit more detailed:
>>>> [ 6.242510] sdhci-pci 0000:03:00.1: SDHCI controller found [1180:e822] (rev 3)
>>>> [ 6.244168] sdhci-pci 0000:03:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
>>>> [ 6.245788] sdhci-pci 0000:03:00.1: BAR 0 is not iomem. Aborting.
>>>> [ 6.247609] sdhci-pci 0000:03:00.1: PCI INT B disabled
>
> If you get a chance to do some bisecting, that would be extremely
> helpful -- even just building 3.0 from *before* the MMC tree was
> merged would help a lot, since if the problem still happens before
> the MMC merge we might be looking at some kind of generic PCI bug.
>
Hi Chris,
i just reverted this pull of your merge window patches in my 3.0.0-rc2 tree:
http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commitdiff;h=8c1c77ff9be27137fa7cbbf51efedef1a2ae915b;hp=f3ae1c75203535f65448517e46c8dd70a56b6c71
And you were right: The problem still exists. So it might be from the PCI subsystem :-(
[ 6.167106] sdhci: Secure Digital Host Controller Interface driver
[ 6.167108] sdhci: Copyright(c) Pierre Ossman
[ 6.194731] ehci_hcd 0000:00:1a.0: cache line size of 64 is not supported
[ 6.195140] ehci_hcd 0000:00:1a.0: irq 16, io mem 0xf6970000
[ 6.196423] sdhci-pci 0000:03:00.1: SDHCI controller found [1180:e822] (rev 3)
[ 6.196429] sdhci-pci 0000:03:00.1: found 1 slot(s)
[ 6.196447] sdhci-pci 0000:03:00.1: PCI INT B -> GSI 19 (level, low) -> IRQ 19
[ 6.196451] sdhci-pci 0000:03:00.1: BAR 0 is not iomem. Aborting.
[ 6.196459] sdhci-pci 0000:03:00.1: PCI INT B disabled
Well then, i'll reset my tree and look for differences in the PCI boot messages.
Thanks,
Oliver
next parent reply other threads:[~2011-06-07 18:36 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4DEBCA3F.8050205@hartkopp.net>
[not found] ` <BANLkTin_WHuy5MExNBHdeLiDmdmn7SZYkg@mail.gmail.com>
[not found] ` <4DED05C4.7050903@hartkopp.net>
[not found] ` <m3hb82wx6m.fsf@pullcord.laptop.org>
2011-06-07 18:36 ` Oliver Hartkopp [this message]
2011-06-07 20:06 ` sdhci-pci fails on 3.0.0-rc1 on Dell E6510 Oliver Hartkopp
2011-06-07 22:18 ` Yinghai Lu
2011-06-08 6:26 ` Oliver Hartkopp
2011-06-12 20:44 ` Ram Pai
2011-06-15 16:40 ` Oliver Hartkopp
2011-06-15 16:54 ` Ram Pai
2011-06-15 16:58 ` Oliver Hartkopp
2011-06-15 18:31 ` Bjorn Helgaas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4DEE6FC6.9040308@hartkopp.net \
--to=socketcan@hartkopp.net \
--cc=cjb@laptop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=svenkatr@ti.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox