From: David Miller <davem@davemloft.net>
To: romieu@fr.zoreil.com
Cc: dborkman@redhat.com, netdev@vger.kernel.org,
david@unsolicited.net, fredo@starox.org, hayeswang@realtek.com
Subject: Re: [PATCH net 1/1] r8169: enforce RX_MULTI_EN for the 8168f.
Date: Thu, 12 Sep 2013 02:40:41 -0400 (EDT) [thread overview]
Message-ID: <20130912.024041.1357115695225954085.davem@davemloft.net> (raw)
In-Reply-To: <20130911231543.GA29725@electric-eye.fr.zoreil.com>
From: Francois Romieu <romieu@fr.zoreil.com>
Date: Thu, 12 Sep 2013 01:15:43 +0200
> David Miller <davem@davemloft.net> :
> [...]
>> Francois, if you reply to this thread with your signoff, all will
>> be well and I will apply this.
>
> Signed-off-by: Francois Romieu <romieu@fr.zoreil.com>
>
> I slowly built an AMD IOMMU + 8168{e/f} problem report pattern but
> the picture got blurred:
> - Hayes has not heard of anything like this
> - the oracle suggests it could be an "AMD IOMMU + whatever" problem
> - "iommu=pt" seems quite effective (hardly surprizing :o/ )
>
> I still have a pile of iommu mailing-list messages to search through.
> Let aside the AMD-Vi error log message, I haven't done a thorough analysis.
>
> It's lame.
Understood. There were always IOMMU chips that sometimes prefetch one
cacheline too far (and thus potentially to the next page, which is
potentially unmapped) in certain circumstances. Maybe these settings
trigger that kind of thing.
Applied and queued up for -stable, thanks.
next prev parent reply other threads:[~2013-09-12 6:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-07 23:15 [PATCH net 1/1] r8169: enforce RX_MULTI_EN for the 8168f Francois Romieu
2013-09-08 8:45 ` Daniel Borkmann
2013-09-11 20:16 ` David Miller
2013-09-11 23:15 ` Francois Romieu
2013-09-12 6:40 ` David Miller [this message]
2013-09-09 3:25 ` hayeswang
2013-09-09 4:13 ` David Miller
2013-09-09 22:50 ` Francois Romieu
2013-09-10 8:08 ` Frédéric Leroy
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=20130912.024041.1357115695225954085.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=david@unsolicited.net \
--cc=dborkman@redhat.com \
--cc=fredo@starox.org \
--cc=hayeswang@realtek.com \
--cc=netdev@vger.kernel.org \
--cc=romieu@fr.zoreil.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).