From: Srihari Vijayaraghavan <sriharivijayaraghavan@yahoo.com.au>
To: Christoph Lameter <clameter@sgi.com>
Cc: Ingo Molnar <mingo@elte.hu>, Hugh Dickins <hugh@veritas.com>,
Oliver Xymoron <oxymoron@waste.org>,
Andrew Morton <akpm@linux-foundation.org>,
Jens Axboe <jens.axboe@oracle.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PROBLEM] 2.6.22-rc2 panics on x86-64 with slub
Date: Tue, 22 May 2007 18:26:33 +1000 (EST) [thread overview]
Message-ID: <404129.76498.qm@web52610.mail.re2.yahoo.com> (raw)
In-Reply-To: <20070522070738.GI4705@kernel.dk>
Just another data point: with the flick of CONFIG_SMP, I'm in control of the
hangs/crashes ;-).
Yup, with CONFIG_SMP=n, I'm unable to reproduce the problem. It's quite stable
actually (having completed a dozen kernel compile sessions so far).
I suspected this after seeing spinlock issues on both cores of my CPU in my
earlier report. Just a stab in the dark with some unexpected luck :-).
(Tested on http://www.kernel.org/hg/linux-2.6 changeset at 57106:3f42ad5de7cd.
That's the latest hg commit there.)
Thanks
PS: For the record everything except sysrq support is disabled in the kernel
hacking section. Also the CONFIG_SLAB_DEBUG is off. Kernel preemption is also
off, after proving it had no influence. Just to keep the test case simple.
___________________________________________________________________________________
How would you spend $50,000 to create a more sustainable environment in Australia? Go to Yahoo!7 Answers and share your idea.
http://advision.webevents.yahoo.com/aunz/lifestyle/answers/y7ans-babp_reg.html
next prev parent reply other threads:[~2007-05-22 8:26 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 [this message]
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
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=404129.76498.qm@web52610.mail.re2.yahoo.com \
--to=sriharivijayaraghavan@yahoo.com.au \
--cc=akpm@linux-foundation.org \
--cc=clameter@sgi.com \
--cc=hugh@veritas.com \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oxymoron@waste.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.