From: Jesse Brandeburg <jesse.brandeburg@intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "Waskiewicz Jr, Peter P" <peter.p.waskiewicz.jr@intel.com>,
"Ronciak, John" <john.ronciak@intel.com>,
"Kirsher, Jeffrey T" <jeffrey.t.kirsher@intel.com>,
"Allan, Bruce W" <bruce.w.allan@intel.com>,
"Wyborny, Carolyn" <carolyn.wyborny@intel.com>,
"Skidmore, Donald C" <donald.c.skidmore@intel.com>,
"Rose, Gregory V" <gregory.v.rose@intel.com>,
"Duyck, Alexander H" <alexander.h.duyck@intel.com>,
"Dave, Tushar N" <tushar.n.dave@intel.com>,
"e1000-devel@lists.sourceforge.net"
<e1000-devel@lists.sourceforge.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
jesse.brandeburg@intel.com
Subject: Re: e1000e on thinkpad x60: interrupt problem
Date: Tue, 9 Jul 2013 14:40:41 -0700 [thread overview]
Message-ID: <20130709144041.0000045f@unknown> (raw)
In-Reply-To: <20130709204854.GA21438@amd.pavel.ucw.cz>
On Tue, 9 Jul 2013 22:48:54 +0200
Pavel Machek <pavel@ucw.cz> wrote:
> Yeah, of course you need to ask e1000e if it generated the
> interrupt. That part works. The part that actually generates the
> interrupt does not. Take a look at original mail...
>
> packet comes
> e1000e sets E1000_ICR_INT_ASSERTED bit
> e1000e tries to generate an interrupt and fails
> 50msec passes
^^ thats the ASPM timeout length.
> AHCI generates interrupt
> all the handlers are called
> AHCI processes its interrupt, handles disk read
> e1000_intr notices E1000_ICR_INT_ASSERTED bit, delivers the packet.
>
> Network still works, only slowly. Ping goes lower when I use the
> disk. That matches what I see.
>
> Do you have other explanation?
Regardless of what others are saying I believe you have an issue with
ASPM being enabled. All the discussion about shared interrupts, is
just a distraction. This issue would still occur (and just be worse)
without a shared interrupt.
You already mentioned that a kernel hack to disable ASPM fixes it, but
you can just boot with different options to turn off ASPM.
pcie_aspm=off
There are known issues with ASPM on this part, and it definitely needs
to be off. If your bios has the option to turn it off, that is the
best way to disable it, second choice is to turn it off using the
kernel option.
Hope this helps,
Jesse
next prev parent reply other threads:[~2013-07-09 21:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-09 1:05 e1000e on thinkpad x60: interrupt problem Pavel Machek
2013-07-09 15:51 ` Ronciak, John
2013-07-09 17:02 ` Pavel Machek
2013-07-09 17:15 ` Waskiewicz Jr, Peter P
2013-07-09 20:48 ` Pavel Machek
2013-07-09 20:59 ` Ronciak, John
2013-07-09 21:40 ` Jesse Brandeburg [this message]
2013-07-10 3:43 ` [E1000-devel] " Fujinaka, Todd
2013-07-10 11:37 ` Pavel Machek
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=20130709144041.0000045f@unknown \
--to=jesse.brandeburg@intel.com \
--cc=alexander.h.duyck@intel.com \
--cc=bruce.w.allan@intel.com \
--cc=carolyn.wyborny@intel.com \
--cc=donald.c.skidmore@intel.com \
--cc=e1000-devel@lists.sourceforge.net \
--cc=gregory.v.rose@intel.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=peter.p.waskiewicz.jr@intel.com \
--cc=tushar.n.dave@intel.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;
as well as URLs for NNTP newsgroup(s).