Re: [Fwd: kernel panic when using disable_mtrr_trim [was: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y]]

[Yinghai Lu]

Tejun Heo wrote:
> Yinghai Lu wrote:
>> On Tue, Jan 20, 2009 at 12:42 PM, Yinghai Lu <yinghai@xxxxxxxxxx> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/