From: William Lee Irwin III <wli@holomorphy.com>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Andrew Morton <akpm@osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Panic on 2.6.0-test1-mm1
Date: Thu, 31 Jul 2003 15:37:10 -0700 [thread overview]
Message-ID: <20030731223710.GI15452@holomorphy.com> (raw)
In-Reply-To: <5110000.1059489420@[10.10.2.4]>
On Tue, Jul 29, 2003 at 07:37:00AM -0700, Martin J. Bligh wrote:
> The big box had this on the console ... looks like it was doing a
> compile at the time ... sorry, only just noticed it after returning
> from OLS, so don't have more context (2.6.0-test1-mm1).
> kernel BUG at include/linux/list.h:149!
> invalid operand: 0000 [#1]
> SMP
> CPU: 3
> EIP: 0060:[<c0117f98>] Not tainted VLI
> EFLAGS: 00010083
> EIP is at pgd_dtor+0x64/0x8c
This is on PAE, so you're in far deeper trouble than I could have caused:
pgd_cache = kmem_cache_create("pgd",
PTRS_PER_PGD*sizeof(pgd_t),
0,
SLAB_HWCACHE_ALIGN | SLAB_MUST_HWCACHE_ALIGN,
pgd_ctor,
PTRS_PER_PMD == 1 ? pgd_dtor : NULL);
You've applied mingo's patch, which needs to check for PAE in certain
places like the above. Backing out highpmd didn't make this easier, it
just gave you performance problems because now all your pmd's are stuck
on node 0 and another side-effect of those changes is that you're now
pounding pgd_lock on 16x+ boxen. You could back out the preconstruction
altogether, if you're hellbent on backing out everyone else's patches
until your code has nothing to merge against.
-- wli
next prev parent reply other threads:[~2003-07-31 22:35 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 14:37 Panic on 2.6.0-test1-mm1 Martin J. Bligh
2003-07-29 21:18 ` Martin J. Bligh
2003-07-30 15:01 ` 2.6.0-test2-mm1 results Martin J. Bligh
2003-07-30 15:28 ` Con Kolivas
2003-07-30 16:27 ` Martin J. Bligh
2003-07-31 14:56 ` Martin J. Bligh
2003-07-31 15:13 ` Con Kolivas
2003-07-31 15:19 ` Martin J. Bligh
2003-07-31 15:35 ` Con Kolivas
2003-07-31 16:01 ` Martin J. Bligh
2003-07-31 16:11 ` Con Kolivas
2003-07-31 21:19 ` William Lee Irwin III
2003-07-31 17:03 ` Bill Davidsen
2003-07-31 22:37 ` William Lee Irwin III [this message]
2003-07-31 22:41 ` Panic on 2.6.0-test1-mm1 William Lee Irwin III
2003-07-31 22:40 ` Andrew Morton
2003-08-01 0:15 ` William Lee Irwin III
2003-08-01 0:18 ` Zwane Mwaikambo
2003-08-01 0:20 ` William Lee Irwin III
2003-08-01 0:47 ` Martin J. Bligh
2003-08-01 0:53 ` William Lee Irwin III
2003-08-01 0:57 ` Martin J. Bligh
2003-08-01 1:02 ` William Lee Irwin III
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=20030731223710.GI15452@holomorphy.com \
--to=wli@holomorphy.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.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).