From: Gavin Lambert <intel@mirality.co.nz>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [e1000e] Linux 4.9: unable to send packets after link recovery with patched driver
Date: Tue, 20 Aug 2019 14:15:02 +1200 [thread overview]
Message-ID: <f6b7b539ece1ba352c60c6dc976a3ce2@mirality.co.nz> (raw)
In-Reply-To: <f4a18bf808e6f30e9691e127722f851b@mirality.co.nz>
On 2019-07-19 13:02, I wrote:
> On 2019-07-19 12:40, I wrote:
>> FWIW, I added some extra logging around the new code. I can confirm
>> that it does execute on link regain but doesn't actually enter the
>> loop in my problem case. The pcim_state is 0x00080083 at the time.
>> So the e1000_phy_hw_reset is never actually called. If I try changing
>> it to call that unconditionally, then it can't successfully establish
>> a link in the first place.
>
> I added a call to e1000e_dump at the point of link regain, in hopes
> that it might shed more light.
[register dumps clipped]
Does anyone have any ideas about this? Either towards further
investigation or to a possible resolution?
This is at the point of hardware internals now, so I have no idea how to
proceed in either area.
next prev parent reply other threads:[~2019-08-20 2:15 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-11 6:50 [Intel-wired-lan] [e1000e] Linux 4.9: unable to send packets after link recovery with patched driver Gavin Lambert
2019-07-12 3:23 ` Gavin Lambert
2019-07-18 8:06 ` Gavin Lambert
2019-07-18 8:22 ` Paul Menzel
2019-07-18 8:24 ` Neftin, Sasha
2019-07-19 0:40 ` Gavin Lambert
2019-07-19 1:02 ` Gavin Lambert
2019-08-20 2:15 ` Gavin Lambert [this message]
2019-09-03 7:56 ` Gavin Lambert
2019-09-03 8:35 ` Paul Menzel
2019-09-03 9:20 ` Greg Kroah-Hartman
2019-09-03 9:28 ` Winkler, Tomas
2019-09-03 9:39 ` Paul Menzel
2019-09-03 11:00 ` Gavin Lambert
2019-09-04 10:06 ` Winkler, Tomas
2019-09-04 11:08 ` Gavin Lambert
2019-09-04 12:31 ` Lifshits, Vitaly
2019-09-05 3:59 ` Gavin Lambert
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=f6b7b539ece1ba352c60c6dc976a3ce2@mirality.co.nz \
--to=intel@mirality.co.nz \
--cc=intel-wired-lan@osuosl.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