From: Nix <nix@esperi•org.uk>
To: "Wyborny\, Carolyn" <carolyn.wyborny@intel•com>
Cc: "Kirsher\, Jeffrey T" <jeffrey.t.kirsher@intel•com>,
"davem\@davemloft.net" <davem@davemloft•net>,
Chris Boot <bootc@bootc•net>,
"netdev\@vger.kernel.org" <netdev@vger•kernel.org>,
"gospo\@redhat.com" <gospo@redhat•com>,
"sassmann\@redhat.com" <sassmann@redhat•com>
Subject: Re: [net-next 5/9] e1000e: Disable ASPM L1 on 82574
Date: Thu, 03 May 2012 21:17:04 +0100 [thread overview]
Message-ID: <87sjfhaukf.fsf@spindle.srvr.nix> (raw)
In-Reply-To: <9BBC4E0CF881AA4299206E2E1412B6261882C3A9@FMSMSX151.amr.corp.intel.com> (Carolyn Wyborny's message of "Thu, 3 May 2012 20:12:47 +0000")
On 3 May 2012, Carolyn Wyborny told this:
> It would be good to know why/how your system is re-enabling the
> setting. The problem is not solvable in firmware unfortunately and is
> somewhat platform dependent. MMIO-tracer might be used to try and see
I entirely forgot about that tool! *Definitely* worth trying.
I'll give it a try this weekend.
> when the re-enabling config space is written, but it might be too
> heavyweight for a live production system.
Given that the re-enabling happens at around the same time as the boot
scripts finish running (it's done by the time I can log in), that's not
going to be a problem. Hence my speculation that it's being re-enabled
when the interface stabilizes (which is, of course, asynchronous) or
something like that.
> I am also working on a patch to the driver to detect the condition and
> then do a slot reset to avoid a whole system reboot. Would you be
> willing to test it in your problem system?
Yes, definitely. The whole-system reboot is irritating because the
system is headless, and with its NICs dead that means a big red switch
to reboot when this problem strikes, which gives me the heebie-jeebies
:)
(Turning off ASPM definitely completely fixes it, so it *is* this bug.
It's just getting the disabling to stick that's proving tricky.)
--
NULL && (void)
next prev parent reply other threads:[~2012-05-03 20:17 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-03 9:56 [net-next 0/9][pull request] Intel Wired LAN Dirver Updates Jeff Kirsher
2012-05-03 9:56 ` [net-next 1/9] e1000e: suggest a possible workaround to a device hang on 82577/8 Jeff Kirsher
2012-05-03 9:56 ` [net-next 2/9] e1000e: cleanup long [read|write]_reg_locked PHY ops function pointers Jeff Kirsher
2012-05-03 9:56 ` [net-next 3/9] e1000e: Resolve intermittent negotiation issue on 82574/82583 Jeff Kirsher
2012-05-03 9:56 ` [net-next 4/9] e1000e: Driver workaround for IPv6 Header Extension Erratum Jeff Kirsher
2012-05-03 9:56 ` [net-next 5/9] e1000e: Disable ASPM L1 on 82574 Jeff Kirsher
2012-05-03 10:08 ` Nix
2012-05-03 20:12 ` Wyborny, Carolyn
2012-05-03 20:17 ` Nix [this message]
2012-05-05 16:33 ` Nix
2012-05-09 14:02 ` Nix
2012-05-03 9:56 ` [net-next 6/9] e1000e: Remove special case for 82573/82574 ASPM L1 disablement Jeff Kirsher
2012-05-03 9:56 ` [net-next 7/9] ixgbevf: Add support to recognize 100mb link speed Jeff Kirsher
2012-05-03 9:56 ` [net-next 8/9] ixgbevf: Make sure jumbo frames are set correctly after PF reset Jeff Kirsher
2012-05-03 9:56 ` [net-next 9/9] ixgbevf: Update version string Jeff Kirsher
2012-05-03 17:30 ` [net-next 0/9][pull request] Intel Wired LAN Dirver Updates David Miller
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=87sjfhaukf.fsf@spindle.srvr.nix \
--to=nix@esperi$(echo .)org.uk \
--cc=bootc@bootc$(echo .)net \
--cc=carolyn.wyborny@intel$(echo .)com \
--cc=davem@davemloft$(echo .)net \
--cc=gospo@redhat$(echo .)com \
--cc=jeffrey.t.kirsher@intel$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
--cc=sassmann@redhat$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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