All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Ball <cjb@laptop.org>
To: Oliver Hartkopp <socketcan@hartkopp.net>
Cc: "S, Venkatraman" <svenkatr@ti.com>,
	linux-mmc <linux-mmc@vger.kernel.org>
Subject: Re: sdhci-pci fails on 3.0.0-rc1 on Dell E6510
Date: Mon, 06 Jun 2011 15:56:49 -0400	[thread overview]
Message-ID: <m3hb82wx6m.fsf@pullcord.laptop.org> (raw)
In-Reply-To: <4DED05C4.7050903@hartkopp.net> (Oliver Hartkopp's message of "Mon, 06 Jun 2011 18:52:20 +0200")

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.

Thanks!

- Chris.
-- 
Chris Ball   <cjb@laptop.org>   <http://printf.net/>
One Laptop Per Child

  reply	other threads:[~2011-06-06 19:57 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-05 18:26 sdhci-pci fails on 3.0.0-rc1 on Dell E6510 Oliver Hartkopp
2011-06-06  6:13 ` S, Venkatraman
2011-06-06 16:52   ` Oliver Hartkopp
2011-06-06 19:56     ` Chris Ball [this message]
2011-06-07 18:36       ` Oliver Hartkopp
2011-06-07 18:36         ` Oliver Hartkopp
2011-06-07 20:06         ` Oliver Hartkopp
2011-06-07 20:06           ` Oliver Hartkopp
2011-06-07 22:18           ` Yinghai Lu
2011-06-07 22:18             ` Yinghai Lu
2011-06-08  6:26             ` Oliver Hartkopp
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=m3hb82wx6m.fsf@pullcord.laptop.org \
    --to=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=socketcan@hartkopp.net \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.