From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Josh Boyer <jwboyer@linux.vnet.ibm.com>
Cc: kvm-ppc-devel <kvm-ppc-devel@lists.sourceforge.net>,
linuxppc-dev <linuxppc-dev@ozlabs.org>,
Hollis Blanchard <hollisb@us.ibm.com>
Subject: Re: Bamboo PCI interrupt issues
Date: Tue, 04 Mar 2008 17:18:21 +1100 [thread overview]
Message-ID: <1204611501.21545.48.camel@pasglop> (raw)
In-Reply-To: <20080303213718.12291eee@zod.rchland.ibm.com>
On Mon, 2008-03-03 at 21:37 -0600, Josh Boyer wrote:
> I plugged in an old 3Com ethernet card tonight. Slot 0. It was
> assigned dev #4 IRQ 25. Using the device tree as-is, I could see
> interrupts happening in /proc/interrupts but ethernet traffic failed.
>
> Then I changed the sense level to 4 as you suggested, and my card hung
> hard on the first ethernet traffic. I've no idea if we're dealing
> with
> a crappy card or a crappy driver but the device tree seems to be
> working ok. If I can find a different card to test with I will.
>
> Ben, do you have any input here?
Other than bamboo has the weirdest combination of FPGA/CPLD/DIP switches
that I could never figure out if PCI was clocked properly ?
That might just be the problem :-)
I do remember having issues now that we talk about it. Though not
specifically what they were.
Ben.
prev parent reply other threads:[~2008-03-04 6:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 0:02 Bamboo PCI interrupt issues Hollis Blanchard
2008-03-04 0:59 ` David Gibson
2008-03-04 1:42 ` Benjamin Herrenschmidt
2008-03-04 1:53 ` David Gibson
2008-03-04 2:07 ` Segher Boessenkool
2008-03-04 2:15 ` David Gibson
2008-03-04 3:37 ` Josh Boyer
2008-03-04 6:15 ` Stefan Roese
2008-03-04 6:33 ` Benjamin Herrenschmidt
2008-03-04 20:39 ` Segher Boessenkool
2008-03-04 20:41 ` Benjamin Herrenschmidt
2008-03-04 20:59 ` Segher Boessenkool
2008-03-04 21:01 ` Benjamin Herrenschmidt
2008-03-04 6:18 ` 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=1204611501.21545.48.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=hollisb@us.ibm.com \
--cc=jwboyer@linux.vnet.ibm.com \
--cc=kvm-ppc-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.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).