From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Alexander Graf <agraf@suse.de>
Cc: Scott Wood <scottwood@freescale.com>,
linuxppc-dev@ozlabs.org,
Fleming Andy-AFLEMING <afleming@freescale.com>
Subject: Re: p1020 unstable with 3.2
Date: Wed, 28 Dec 2011 16:01:14 +1100 [thread overview]
Message-ID: <1325048474.6632.33.camel@pasglop> (raw)
In-Reply-To: <025812DC-AB8E-4B60-9B16-50C3DE4DD561@suse.de>
On Sun, 2011-12-25 at 11:48 +0100, Alexander Graf wrote:
> On 24.12.2011, at 07:53, Benjamin Herrenschmidt wrote:
>
> > On Fri, 2011-12-23 at 17:54 +0100, Alexander Graf wrote:
> >> Hi guys,
> >>
> >> While trying to test my latest patch queue for ppc kvm, I realized
> >> that even though the device trees got updated, the p1020 box still is
> >> unstable. The trace below is the one I've seen the most. It only
> >> occurs during network I/O which happens a lot on that box, since I'm
> >> running it using NFS root.
> >>
> >> As for configuration, I use kumar's "merge" branch from today and the
> >> p1020rdb.dts device tree provided in that tree.
> >>
> >> The last known good configuration I'm aware of is 3.0.
> >>
> >> Any ideas what's going wrong here?
> >
> > Try SLAB instead of SLUB and let me know. It -could- be a bogon in SLUB
> > that should be fixed upstream now but I think did hit 3.2
>
> Yup, things seem a lot more stable with SLAB now :).
BTW. Fix for slub should be upstream:
42d623a8cd08eb93ab221d22cee5a62618895bbf
Cheers,
Ben.
next prev parent reply other threads:[~2011-12-28 5:01 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-23 16:54 p1020 unstable with 3.2 Alexander Graf
2011-12-24 6:53 ` Benjamin Herrenschmidt
2011-12-25 10:48 ` Alexander Graf
2011-12-28 5:01 ` Benjamin Herrenschmidt [this message]
2012-01-02 15:20 ` Alexander Graf
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=1325048474.6632.33.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=afleming@freescale.com \
--cc=agraf@suse.de \
--cc=linuxppc-dev@ozlabs.org \
--cc=scottwood@freescale.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).