From: Jens Axboe <jens.axboe@oracle.com>
To: Christoph Lameter <clameter@sgi.com>
Cc: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>,
Hugh Dickins <hugh@veritas.com>, Ingo Molnar <mingo@elte.hu>,
Oliver Xymoron <oxymoron@waste.org>,
Andrew Morton <akpm@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub
Date: Fri, 25 May 2007 08:12:01 +0200 [thread overview]
Message-ID: <20070525061200.GG7653@kernel.dk> (raw)
In-Reply-To: <Pine.LNX.4.64.0705240953270.28086@schroedinger.engr.sgi.com>
On Thu, May 24 2007, Christoph Lameter wrote:
> On Thu, 24 May 2007, Jens Axboe wrote:
>
> > On Wed, May 23 2007, Christoph Lameter wrote:
> > > On Wed, 23 May 2007, Jens Axboe wrote:
> > >
> > > > That works for me with the patch, .config attached.
> > >
> > > Hmmmm... That means the .config sent initially here was bogus.
> >
> > ?
> >
> > Considering we're trying to help you fix bugs in your code, you could be
> > considerably more helpful.
>
> I am trying figure out what is wrong and somehow that is not helpful? The
> data that we have right now about the bug does not give us a clear
You are doing what you are supposed to do, fixing your broken code. We
are the ones that are helping you do that, by reporting the problem and
testing solutions. I think you have your attributions backwards.
> picture. One explanation that would have made it consistent would be that
> the .config posted was not reflecting the actual kernel in use.
The .config I sent is the one that the last boot of the machine was
based on. The kernel is 2.6.22-rc2 with the patch moving the #ifdef from
you, and it works for me with or without CONFIG_SLUB_DEBUG set.
--
Jens Axboe
next prev parent reply other threads:[~2007-05-25 6:15 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-20 13:35 [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub Srihari Vijayaraghavan
2007-05-21 16:30 ` Christoph Lameter
2007-05-21 17:41 ` Hugh Dickins
2007-05-21 18:25 ` Christoph Lameter
2007-05-21 18:44 ` Hugh Dickins
2007-05-21 18:48 ` Christoph Lameter
2007-05-21 19:00 ` Jens Axboe
2007-05-21 19:06 ` Hugh Dickins
2007-05-21 19:09 ` Jens Axboe
2007-05-21 19:13 ` Christoph Lameter
2007-05-21 19:26 ` Jens Axboe
2007-05-21 19:29 ` Hugh Dickins
2007-05-21 19:34 ` Christoph Lameter
2007-05-21 22:27 ` Christoph Lameter
2007-05-21 23:46 ` Christoph Lameter
2007-05-22 7:07 ` Jens Axboe
2007-05-22 8:26 ` Srihari Vijayaraghavan
2007-05-22 9:24 ` Ingo Molnar
2007-05-22 11:01 ` Srihari Vijayaraghavan
2007-05-22 11:20 ` Ingo Molnar
2007-05-22 11:26 ` Srihari Vijayaraghavan
2007-05-22 13:01 ` Hugh Dickins
2007-05-22 15:36 ` Jens Axboe
2007-05-22 18:30 ` Christoph Lameter
2007-05-22 20:10 ` Jens Axboe
2007-05-22 22:15 ` Srihari Vijayaraghavan
2007-05-22 22:25 ` Christoph Lameter
2007-05-23 7:11 ` Jens Axboe
2007-05-23 17:04 ` Christoph Lameter
2007-05-24 7:25 ` Jens Axboe
2007-05-24 16:55 ` Christoph Lameter
2007-05-25 6:12 ` Jens Axboe [this message]
2007-05-25 13:40 ` Christoph Lameter
2007-05-25 14:00 ` Jens Axboe
2007-05-26 1:52 ` Christoph Lameter
2007-05-26 2:49 ` Srihari Vijayaraghavan
2007-05-23 10:18 ` Srihari Vijayaraghavan
2007-05-23 17:10 ` Christoph Lameter
2007-05-23 17:19 ` Christoph Lameter
2007-05-23 22:23 ` Srihari Vijayaraghavan
2007-05-23 22:32 ` Christoph Lameter
2007-05-24 13:12 ` Srihari Vijayaraghavan
2007-05-24 16:58 ` Christoph Lameter
2007-05-24 21:30 ` Srihari Vijayaraghavan
2007-05-24 22:19 ` Christoph Lameter
2007-05-24 22:39 ` Srihari Vijayaraghavan
2007-05-21 19:04 ` Hugh Dickins
-- strict thread matches above, loose matches on Subject: below --
2007-05-20 3:09 Srihari Vijayaraghavan
2007-05-20 7:12 ` Christoph Lameter
2007-05-20 7:40 ` Srihari Vijayaraghavan
2007-05-20 13:24 ` Satyam Sharma
2007-05-20 13:37 ` Srihari Vijayaraghavan
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=20070525061200.GG7653@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oxymoron@waste.org \
--cc=sriharivijayaraghavan@yahoo.com.au \
/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