linux-kernel - Re: [REGRESSION] e1000e failure triggered by "PCI: Remove MRRS modification from MPS setting code"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 29 Sep 2011 08:53:26 -0500
From:	Jon Mason <mason@...i.com>
To:	Benjamin Herrenschmidt <benh@...nel.crashing.org>
Cc:	Avi Kivity <avi@...hat.com>, Sven Schnelle <svens@...ckframe.org>,
	Simon Kirby <sim@...tway.ca>,
	Eric Dumazet <eric.dumazet@...il.com>,
	Niels Ole Salscheider <niels_ole@...scheider-online.de>,
	Jesse Barnes <jbarnes@...tuousgeek.org>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>
Subject: Re: [REGRESSION] e1000e failure triggered by "PCI: Remove MRRS
 modification from MPS setting code"

On Wed, Sep 28, 2011 at 11:33 PM, Benjamin Herrenschmidt
<benh@...nel.crashing.org> wrote:
>
>> Booting with "pci=pcie_bus_perf" should provide you with the same
>> behavior as before (e.g., with the patch reverted).  This should
>> enable you work around this issue until I can get it resolved.  On the
>> positive side, your system should be 10% faster than it was in 3.0
>> (due to the PCI bus payloads being 2x larger).
>
> Ugh, that's assuming your fixes for the "perf" mode are in, which I
> thought wasn't the case yet ... without them, "perf" does very wrong
> things..

Yes, but this was "working" before.  The patch he wants reverted was
the one that makes MPS "Safe" the default.  So, changing it to "perf"
would give it the same behavior as before.

>> If you can provide the same output with the patch not reverted, it
>> would be very beneficial.  Based on your description, the lockup only
>> occurs with traffic.  You can gather this before any traffic goes out
>> (perhaps booting without networking enabled).
>
> Right, the output he provided has the MRRS clearly changing in addition
> to the MPS.
>
> Ideally, we'd need the output with current upstream vs. with before your
> very first patch went in and compare that.
>
> Also, Avi, can you send these outputs like patches ? IE without wrapping
> them ? That would be handy :-)
>
> Cheers,
> Ben.
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/