From: Yinghai Lu <yinghai@kernel.org>
To: Tejun Heo <tj@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: Thu, 22 Jan 2009 23:48:04 -0800 [thread overview]
Message-ID: <49797634.7040500@kernel.org> (raw)
In-Reply-To: <49794422.2080109@kernel.org>
Tejun Heo wrote:
> 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.
current tip:
still got
WARNING: Absolute relocations present
Offset Info Type Sym.Value Sym.Name
c14d21ef 00921101 R_386_32 c1514000 __per_cpu_load
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 data
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 2079274
[ 0.000000] Kernel command line: console=uart8250,io,0x3f8,115200n8 initrd=kernel.org/mydisk11_x86.gz rw root=/dev/ram0 loglevel=10,apic:13,acpi:10,dev:10,pci:10 initcall_debug apic=verbose pci=routeirq ip=dhcp load_ramdisk=1 ramdisk_size=131072 BOOT_IMAGE=kernel.org/bzImage_2.6.29_x86.1
[ 0.000000] Enabling fast FPU save and restore... done.
[ 0.000000] Enabling unmasked SIMD FPU exception support... done.
[ 0.000000] Initializing CPU#0
[ 0.000000] NR_IRQS:320
[ 0.000000] PID hash table entries: 4096 (order: 12, 16384 bytes)
[ 0.000000] Fast TSC calibration using PIT
[ 0.000000] Detected 2700.114 MHz processor.
YH
next prev parent reply other threads:[~2009-01-23 7:48 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 [this message]
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=49797634.7040500@kernel.org \
--to=yinghai@kernel.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--cc=tj@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