From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: linuxppc-dev@ozlabs.org, paulus@samba.org
Subject: Re: [bugme-daemon@bugzilla.kernel.org: [Bug 7306] Yenta-socket causes oops on insertion of any PCMCIA card]
Date: Wed, 30 Jul 2008 07:31:37 +1000 [thread overview]
Message-ID: <1217367097.11188.257.camel@pasglop> (raw)
In-Reply-To: <20080729182819.GA30961@isilmar.linta.de>
On Tue, 2008-07-29 at 20:28 +0200, Dominik Brodowski wrote:
> Ben, Paul,
>
> any ideas?
Strange. Paul has a lombard, so if he can bring it to the office, I'll
have a look. Paul, bring some legacy PCMCIA cards too if you have any,
I'm not sure I do (though I think we have one or two somewhere in the
lab).
Cheers,
Ben.
> Best,
> Dominik
>
> On Thu, Jul 17, 2008 at 11:14:44AM +0200, Dominik Brodowski wrote:
> > Hi,
> >
> > on an Apple Powerbook G3 (Lombard) with a PPC 740 running at 333 MHz, the
> > PCI host bridge is condigured to allow "downstream" devices to use iomem
> >
> > 0xfd000000 - 0xfdffffff
> >
> > However, when using it for PCMCIA purposes, there's a machine check. Any
> > ideas on why this PCI host bridge is mis-configured, and how to resolve this
> > issue (besides adding reserved=0xfd000000,0xffffff as kernel boot option)?
> >
> > Best,
> > Dominik
> >
> >
> > ----- Forwarded message from bugme-daemon@bugzilla.kernel.org -----
> >
> > Subject: [Bug 7306] Yenta-socket causes oops on insertion of any PCMCIA card
> > To: linux-pcmcia@lists.infradead.org
> > From: bugme-daemon@bugzilla.kernel.org
> > Date: Thu, 17 Jul 2008 01:45:44 -0700 (PDT)
> >
> > http://bugzilla.kernel.org/show_bug.cgi?id=7306
> >
> >
> >
> >
> >
> > ------- Comment #17 from linux@brodo.de 2008-07-17 01:45 -------
> > Now this contains interesting information:
> >
> > pcmcia: parent PCI bridge Memory window:
> >
> > means the PCI host bridge is configured to allow "downstream" devices to use
> > this memory area. However, when the PCMCIA socket tries to do so, you get the
> > machine check. So my question would be to the powerpc folks: why is the PCI
> > host bridge configured this way, even if this memory area is not usable?
> >
> >
> > --
> > Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
> > ------- You are receiving this mail because: -------
> > You are on the CC list for the bug, or are watching someone who is.
> >
> > _______________________________________________
> > Linux PCMCIA reimplementation list
> > http://lists.infradead.org/mailman/listinfo/linux-pcmcia
> >
> > ----- End forwarded message -----
prev parent reply other threads:[~2008-07-29 21:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-17 9:14 [bugme-daemon@bugzilla.kernel.org: [Bug 7306] Yenta-socket causes oops on insertion of any PCMCIA card] Dominik Brodowski
2008-07-29 18:28 ` Dominik Brodowski
2008-07-29 21:31 ` Benjamin Herrenschmidt [this message]
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=1217367097.11188.257.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=linux@dominikbrodowski.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=paulus@samba.org \
/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;
as well as URLs for NNTP newsgroup(s).