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: Tue, 27 Jan 2009 12:10:52 +0900 [thread overview]
Message-ID: <497E7B3C.1040606@kernel.org> (raw)
In-Reply-To: <497979C1.3030103@kernel.org>
Yinghai Lu wrote:
>>>> WARNING: Absolute relocations present
>>>> Offset Info Type Sym.Value Sym.Name
>>>> c14d21ef 00921101 R_386_32 c1514000 __per_cpu_load
>>> Hmm... weird. Can you please attach the .config file you used and the
>>> commit ID and the version of toolchain? I'll try to reproduce it
>>> here.
>>>
>> my own config full, got that too
>> WARNING: Absolute relocations present
>> Offset Info Type Sym.Value Sym.Name
>> 40c22260 00d94801 R_386_32 40c7a000 __per_cpu_load
Brian just committed a patch to fix the relocation bug. Can you
please test the current core/percpu[1]?
[1] 5a611268b69f05262936dd177205acbce4471358
--
tejun
next prev parent reply other threads:[~2009-01-27 3:12 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
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 [this message]
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=497E7B3C.1040606@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox