From: Justin Piszcz <jpiszcz@lucidpixels.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Lin Ming <mlin@ss.pku.edu.cn>,
linux-kernel@vger.kernel.org, Alan Piszcz <ap@solarrain.com>,
"Li, Shaohua" <shaohua.li@intel.com>,
Andrew Morton <akpm@google.com>
Subject: Re: 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues?
Date: Wed, 14 Sep 2011 09:10:17 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1109140901560.2082@p34.internal.lan> (raw)
In-Reply-To: <alpine.DEB.2.02.1109140629300.29782@p34.internal.lan>
On Wed, 14 Sep 2011, Justin Piszcz wrote:
>
>
> On Wed, 14 Sep 2011, Eric Dumazet wrote:
>
> Hi,
>
> Thanks-- patch applied and booted to the new kernel, so just so everyone
> knows, I am running three patches atop of 3.1-rc4:
>
> (for the igb problem/memory allocation issue)
> 0001-Fix-pointer-dereference-before-call-to-pcie_bus_conf.patch
> 0002-PCI-Remove-MRRS-modification-from-MPS-setting-code.patch
>
> (for the RCU/memory errors)
> 0003-filemap.patch
>
> I will try to perform more load tests on the NIC and CPU/MEM/I+O and see
> if any of my problems return!
>
> Justin.
Hi,
Been running a lot of stressful jobs and will let them continue, so far,
no ERROR, WARN or OOPS yet.
3.1-rc4 + the three patches above seem to fix the problems (thus far).
Does anyone know when the bugs were introduced into the kernel, as some/all
of these problems also happened with 3.0.x.
Justin.
next prev parent reply other threads:[~2011-09-14 13:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-11 22:17 Justin Piszcz
2011-09-11 22:44 ` Justin Piszcz
2011-09-12 7:52 ` 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues? [again w/DEBUG_VM & SLAB_DEBUG enabled] Justin Piszcz
2011-09-12 8:32 ` Lin Ming
2011-09-12 8:39 ` Justin Piszcz
2011-09-12 15:15 ` 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues? (now shows further DEBUG w/DEBUG_SLAB! possibly(?)] Justin Piszcz
2011-09-14 8:56 ` 3.0.1: pagevec_lookup+0x1d/0x30, SLAB issues? Lin Ming
2011-09-14 9:47 ` Justin Piszcz
2011-09-14 10:20 ` Eric Dumazet
2011-09-14 10:53 ` Justin Piszcz
2011-09-14 13:10 ` Justin Piszcz [this message]
2011-09-14 18:58 ` 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.1109140901560.2082@p34.internal.lan \
--to=jpiszcz@lucidpixels.com \
--cc=akpm@google.com \
--cc=ap@solarrain.com \
--cc=eric.dumazet@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mlin@ss.pku.edu.cn \
--cc=shaohua.li@intel.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
all inboxes | Powered by JetHome®