Netdev List
 help / color / mirror / Atom feed
From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Jon Mason <mason@myri.com>
Cc: Eric Dumazet <eric.dumazet@gmail.com>,
	Jesse Brandeburg <jesse.brandeburg@gmail.com>,
	Alan Piszcz <ap@solarrain.com>,
	NetDEV list <netdev@vger.kernel.org>,
	xfs@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: 3.1-rc4: spectacular kernel errors / filesystem crash
Date: Tue, 13 Sep 2011 11:42:38 -0400 (EDT)	[thread overview]
Message-ID: <alpine.DEB.2.02.1109131142010.7113@p34.internal.lan> (raw)
In-Reply-To: <CAMaF-rN-qeXBDoc9=7kwu40Wj8=G8YuPKWXPRhOuhdYX_VO34w@mail.gmail.com>

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1906 bytes --]



On Tue, 13 Sep 2011, Jon Mason wrote:

> On Tue, Sep 13, 2011 at 9:54 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>>
>>
>> On Tue, 13 Sep 2011, Eric Dumazet wrote:
>>
>>> Please Justin make sure you pulled commit
>>> commit ed2888e906b56769b4ffabb9c577190438aa68b8
>>> Author: Jon Mason <mason@myri.com>
>>> Date:   Thu Sep 8 16:41:18 2011 -0500
>>>
>>>   PCI: Remove MRRS modification from MPS setting code
>>>
>>>   Modifying the Maximum Read Request Size to 0 (value of 128Bytes) has
>>>   massive negative ramifications on some devices.  Without knowing which
>>>   devices have this issue, do not modify from the default value when
>>>   walking the PCI-E bus in pcie_bus_safe mode.  Also, make pcie_bus_safe
>>>   the default procedure.
>>>
>>>   Tested-by: Sven Schnelle <svens@stackframe.org>
>>>   Tested-by: Simon Kirby <sim@hostway.ca>
>>>   Tested-by: Stephen M. Cameron <scameron@beardog.cce.hp.com>
>>>   Reported-and-tested-by: Eric Dumazet <eric.dumazet@gmail.com>
>>>   Reported-and-tested-by: Niels Ole Salscheider
>>> <niels_ole@salscheider-online.
>>>   References: https://bugzilla.kernel.org/show_bug.cgi?id=42162
>>>   Signed-off-by: Jon Mason <mason@myri.com>
>>>   Acked-by: Jesse Barnes <jbarnes@virtuousgeek.org>
>>>   Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>>
>> Hello,
>>
>> I found this commit here:
>> http://permalink.gmane.org/gmane.linux.kernel.pci/11700
>
> This is an early version of the patch.  This is the patch that you want:
> https://github.com/torvalds/linux/commit/ed2888e906b56769b4ffabb9c577190438aa68b8
>
> It appears that this patch didn't make it to lkml or linux-pci list
> due to kernel.org DNS being down when it was sent.
>
> Thanks,
> Jon

I need to learn how to use git at some point, can you please provide plain
text patches so I can apply them and reboot?

Justin.

  reply	other threads:[~2011-09-13 15:42 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.DEB.2.02.1109110511250.8626@p34.internal.lan>
2011-09-13  3:59 ` 3.1-rc4: spectacular kernel errors / filesystem crash Jesse Brandeburg
2011-09-13  4:05   ` Eric Dumazet
2011-09-13 14:54     ` Justin Piszcz
2011-09-13 14:58       ` Eric Dumazet
2011-09-13 15:35       ` Jon Mason
2011-09-13 15:42         ` Justin Piszcz [this message]
2011-09-13 15:51           ` Jon Mason
2011-09-13 16:32             ` Justin Piszcz

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=alpine.DEB.2.02.1109131142010.7113@p34.internal.lan \
    --to=jpiszcz@lucidpixels.com \
    --cc=ap@solarrain.com \
    --cc=eric.dumazet@gmail.com \
    --cc=jesse.brandeburg@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mason@myri.com \
    --cc=netdev@vger.kernel.org \
    --cc=xfs@oss.sgi.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