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 12:32:20 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1109131156050.7113@p34.internal.lan> (raw)
In-Reply-To: <CAMaF-rMxTWRAO7WRdYoEM57k66MC6Vuwk1mcfgCgMO6Z+KBvzQ@mail.gmail.com>
On Tue, 13 Sep 2011, Jon Mason wrote:
> On Tue, Sep 13, 2011 at 10:42 AM, Justin Piszcz <jpiszcz@lucidpixels.com> wrote:
>>
>>
>> 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:
>>>>
Thanks,
# patch -p1 < ../0001-Fix-pointer-dereference-before-call-to-pcie_bus_conf.patch
patching file arch/x86/pci/acpi.c
patching file drivers/pci/hotplug/pcihp_slot.c
patching file drivers/pci/probe.c
# patch -p1 < ../0002-PCI-Remove-MRRS-modification-from-MPS-setting-code.patch
patching file drivers/pci/pci.c
patching file drivers/pci/probe.c
#
Rebooted & running with new patches for 3.1-rc4.
Will let you know if any further issues, I wonder if this will fix
the RCU/SLAB issues too, thanks.
Justin.
prev parent reply other threads:[~2011-09-13 16:32 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
2011-09-13 15:51 ` Jon Mason
2011-09-13 16:32 ` Justin Piszcz [this message]
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.1109131156050.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