From: Tejun Heo <tj@kernel.org>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
"H. Peter Anvin" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Fwd: kernel panic when using disable_mtrr_trim [was: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y]]
Date: Fri, 23 Jan 2009 13:14:26 +0900 [thread overview]
Message-ID: <49794422.2080109@kernel.org> (raw)
In-Reply-To: <86802c440901201249v3c877a88ie8e5f3bbf6abb871@mail.gmail.com>
Yinghai Lu wrote:
> On Tue, Jan 20, 2009 at 12:42 PM, Yinghai Lu <yinghai@kernel.org> wrote:
>> with the config
>>
>> current tip said:
>>
>> RELOCS arch/x86/boot/compressed/vmlinux.relocs
>> WARNING: Absolute relocations present
>> Offset Info Type Sym.Value Sym.Name
>> c14d2186 00920e01 R_386_32 c1514000 __per_cpu_load
>>
> and will casue system reboot after
>
> [ 0.000000] NR_CPUS:2 nr_cpumask_bits:2 nr_cpu_ids:2 nr_node_ids:1
> [ 0.000000] PERCPU: Allocating 36864 bytes of per cpu dat
Can you please try the current core/percpu branch? I tried your
config but the problem doesn't happen here.
Thanks.
--
tejun
next prev parent reply other threads:[~2009-01-23 4:14 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-20 20:42 [Fwd: kernel panic when using disable_mtrr_trim [was: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y]] Yinghai Lu
2009-01-20 20:49 ` Yinghai Lu
2009-01-20 20:58 ` Ingo Molnar
2009-01-23 4:14 ` Tejun Heo [this message]
2009-01-23 5:19 ` Yinghai Lu
2009-01-23 5:24 ` Tejun Heo
2009-01-23 7:48 ` Yinghai Lu
2009-01-23 7:51 ` Tejun Heo
2009-01-23 7:53 ` Yinghai Lu
2009-01-23 9:25 ` Ingo Molnar
2009-01-23 19:47 ` Yinghai Lu
2009-01-23 8:01 ` Yinghai Lu
2009-01-23 8:03 ` Yinghai Lu
2009-01-27 3:10 ` Tejun Heo
2009-01-27 5:33 ` Yinghai Lu
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=49794422.2080109@kernel.org \
--to=tj@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=yinghai@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 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.