From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Stephen Hemminger <shemminger@vyatta.com>
Cc: netdev@vger.kernel.org
Subject: Re: Bad sky2 interrupt handling?
Date: Thu, 16 Jul 2009 16:57:41 -0700 [thread overview]
Message-ID: <20090716165741.2142a679@jbarnes-g45> (raw)
In-Reply-To: <20090716163727.666db0cc@nehalam>
On Thu, 16 Jul 2009 16:37:27 -0700
Stephen Hemminger <shemminger@vyatta.com> wrote:
> On Thu, 16 Jul 2009 16:25:52 -0700
> Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
>
> > I was debugging what I thought was a graphics driver problem today
> > (some page flipping code I'm working on was only flipping at about
> > 10Hz rather than ~60Hz) but it appears it's actually due to a bad
> > interaction with the Marvell 88E8036 controller on this machine.
> >
> > MSI fails on this box (haven't looked too much at why yet), so the
> > i915 driver shares an interrupt with USB, firewire, sdhci and the
> > NIC.
> >
> > Is sky2 the wrong driver to be using here? Or is there some way of
> > reducing its overhead when (presumably) it doesn't have anything to
> > do?
>
> No, that is the right driver. If MSI fails, does the driver still
> think it can use MSI?
No, I think it's falling back correctly... lemme get the log.
...
sky2 driver version 1.23
sky2 0000:01:00.0: PCI INT A -> Link[LNKA] -> GSI 11 (level, low) -> IRQ 11 sky2 0000:01:00.0: setting latency timer to 64 sky2
0000:01:00.0: Yukon-2 FE chip revision 1 sky2 0000:01:00.0: irq 18 for MSI/MSI-X
sky2 0000:01:00.0: No interrupt generated using MSI,
switching to INTx mode.
sky2 eth0: addr 00:a0:d1:bb:88:52
...
sky2 skge: enabling interface
sky2 skge: Link is up at 100 Mbps, full duplex, flow control both
at least it looks like it.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2009-07-16 23:57 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-16 23:25 Bad sky2 interrupt handling? Jesse Barnes
2009-07-16 23:37 ` Stephen Hemminger
2009-07-16 23:57 ` Jesse Barnes [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=20090716165741.2142a679@jbarnes-g45 \
--to=jbarnes@virtuousgeek.org \
--cc=netdev@vger.kernel.org \
--cc=shemminger@vyatta.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