From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: aurora-sparc-devel@lists.auroralinux.org,
linux-kernel@vger.kernel.org, davem@redhat.com,
sparclinux@vger.kernel.org
Subject: Re: [Aurora-sparc-devel] [2.6.13-rc6-git13/sparc64]: Slab corruption (possible stack or buffer-cache corruption)
Date: Mon, 12 Sep 2005 15:45:05 -0500 [thread overview]
Message-ID: <1126557905.3375.3.camel@localhost.localdomain> (raw)
In-Reply-To: <20050912.134122.54246336.davem@davemloft.net>
On Mon, 2005-09-12 at 13:41 -0700, David S. Miller wrote:
> From: "Tom 'spot' Callaway" <tcallawa@redhat.com>
> Date: Mon, 12 Sep 2005 09:45:16 -0500
>
> > We've been seeing this intermittently on arthur since Aurora 1.0 (2.4).
>
> That's amazing given that half of those SLAB functions in
> the backtrace simply do not exist in 2.4.x :-) Can you quote
> a 2.4.x version of such a backtrace? Thanks a lot.
You're right. I first saw this on 2.6.4:
http://marc.theaimsgroup.com/?l=linux-sparc&m=107823740703651&w=2
~spot
--
Tom "spot" Callaway: Red Hat Senior Sales Engineer || GPG ID: 93054260
Fedora Extras Steering Committee Member (RPM Standards and Practices)
Aurora Linux Project Leader: http://auroralinux.org
Lemurs, llamas, and sparcs, oh my!
next prev parent reply other threads:[~2005-09-13 1:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-12 14:37 [2.6.13-rc6-git13/sparc64]: Slab corruption (possible stack or buffer-cache corruption) Tomasz Kłoczko
2005-09-12 14:45 ` [Aurora-sparc-devel] " Tom 'spot' Callaway
2005-09-12 15:39 ` Tomasz Kłoczko
2005-09-12 20:41 ` David S. Miller
2005-09-12 20:45 ` Tom 'spot' Callaway [this message]
2005-09-12 23:13 ` David S. Miller
2005-09-13 10:12 ` Tomasz Kłoczko
2005-09-13 20:08 ` David S. Miller
2005-09-14 11:16 ` Tomasz Kłoczko
2005-09-14 11:40 ` Tomasz Kłoczko
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=1126557905.3375.3.camel@localhost.localdomain \
--to=tcallawa@redhat.com \
--cc=aurora-sparc-devel@lists.auroralinux.org \
--cc=davem@davemloft.net \
--cc=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sparclinux@vger.kernel.org \
/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