From: David Miller <davem@davemloft.net>
To: jian-hong@endlessm.com
Cc: hkallweit1@gmail.com, steved424@gmail.com, gogen@disroot.org,
netdev@vger.kernel.org, linux@endlessm.com
Subject: Re: Experimental fix for MSI-X issue on r8169
Date: Tue, 21 Aug 2018 21:24:23 -0700 (PDT) [thread overview]
Message-ID: <20180821.212423.615788696464102670.davem@davemloft.net> (raw)
In-Reply-To: <CAPpJ_eezpOZtHKqMRhMhUHAKDtwwhBzZKmy7OXsy52Zbr0RZ_w@mail.gmail.com>
From: Jian-Hong Pan <jian-hong@endlessm.com>
Date: Wed, 22 Aug 2018 11:01:02 +0800
...
> [ 56.462464] r8169 0000:02:00.0: MSI-X entry: context resume:
> ffffffff ffffffff ffffffff ffffffff
...
> uh! The MSI-X entry seems missed after resume on this laptop!
Yeah, having all of the MSI-X entry values be all-1's is not a good
sign.
But this is quite a curious set of debugging traces we now have.
In the working case, the vector number in the DATA field seems
to change, which suggests that something is assigning new values
and programming them into these fields at resume time.
But in the failing cases, all of the values are garbage.
I would expect, given what the working trace looks like, that in the
failing case some values would be wrong and the DATA value would have
some new yet valid value. But that is not what we are seeing here.
Weird.
next prev parent reply other threads:[~2018-08-22 7:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-19 20:34 Experimental fix for MSI-X issue on r8169 Heiner Kallweit
2018-08-20 3:47 ` Jian-Hong Pan
2018-08-21 17:57 ` Steve Dodd
2018-08-21 21:19 ` Heiner Kallweit
2018-08-21 21:48 ` Steve Dodd
2018-08-21 23:32 ` David Miller
2018-08-22 3:01 ` Jian-Hong Pan
2018-08-22 4:24 ` David Miller [this message]
2018-08-22 5:56 ` Heiner Kallweit
2018-08-22 6:41 ` Steve Dodd
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=20180821.212423.615788696464102670.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=gogen@disroot.org \
--cc=hkallweit1@gmail.com \
--cc=jian-hong@endlessm.com \
--cc=linux@endlessm.com \
--cc=netdev@vger.kernel.org \
--cc=steved424@gmail.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).