From: Pavel Machek <pavel@ucw.cz>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>
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>
Subject: Re: e1000e on thinkpad x60: interrupt problem
Date: Wed, 10 Jul 2013 13:37:43 +0200 [thread overview]
Message-ID: <20130710113742.GA9113@amd.pavel.ucw.cz> (raw)
In-Reply-To: <20130709144041.0000045f@unknown>
Hi!
> > 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.
Agreed.
> 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
Are you sure? AFAICT linux will not turn off aspm if ACPI says
so.. hence the hack.
# From: Robert Hancock <hancockrwd@gmail.com>
# To: Pavel Machek <pavel@ucw.cz>
# CC: Greg KH <greg@kroah.com>, kernel list
# <linux-kernel@vger.kernel.org>,
# joe.lawrence@stratus.com, myron.stowe@redhat.com,
# bhelgaas@google.com
# Subject: Re: /sys/module/pcie_aspm/parameters/policy not writable?
# ...
# > pavel@amd:~$ dmesg | grep -i aspm
# > ACPI FADT declares the system doesn't support PCIe ASPM, so disable
# it
#
# IIRC, this message is somewhat misleading. When that FADT flag is set
# by the BIOS, the kernel doesn't so much disable ASPM as disable the
# kernel's control over ASPM. I believe this was to match Windows
# behavior.
It looks like ASPM needs to be off, but BIOS enables ASPM and tells
kernel it is not supported... and that means that kernel will not
disable it :-(.
I guess there's no way to do ASPM disable for single device from the
driver?
Thanks,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
prev parent reply other threads:[~2013-07-10 11:37 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
2013-07-10 3:43 ` [E1000-devel] " Fujinaka, Todd
2013-07-10 11:37 ` Pavel Machek [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=20130710113742.GA9113@amd.pavel.ucw.cz \
--to=pavel@ucw.cz \
--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=jesse.brandeburg@intel.com \
--cc=john.ronciak@intel.com \
--cc=netdev@vger.kernel.org \
--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).