linux-kernel - Re: 2.6.21-rc5-mm3 - no boot, "address not 2M aligned"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <m1mz1thlt1.fsf@ebiederm.dsl.xmission.com>
Date:	Sat, 31 Mar 2007 02:14:18 -0600
From:	ebiederm@...ssion.com (Eric W. Biederman)
To:	Andrew Morton <akpm@...ux-foundation.org>
Cc:	Helge Hafting <helgehaf@...el.hist.no>,
	linux-kernel@...r.kernel.org, Vivek Goyal <vgoyal@...ibm.com>
Subject: Re: 2.6.21-rc5-mm3 - no boot, "address not 2M aligned"

Andrew Morton <akpm@...ux-foundation.org> writes:

> On Sat, 31 Mar 2007 09:12:20 +0200 Helge Hafting <helgehaf@...el.hist.no> wrote:
>
>> A new error for me:
>> 
>> loading 2.6.21rc5mm3
>> Bios data check successful
>> Destination address not 2M aligned
>>  -- System halted
>> 
>> 
>> This is using the same lilo that loads 2.6.18rc5mm1 fine.
>> x86-64
>> 
>
> That's new.  Does changing the value of CONFIG_RELOCATABLE change anything?

I will have to dig a little deeper but this certainly sounds like the
x86_64 relocatable kernel patches.  I believe the check is in 
arch/x86_64/boot/compressed/misc.c

I think the interesting .config variable is going to be
CONFIG_PHYSICAL_START.

I suspect that isn't going to be 2M aligned, like the kernel requires
for best performance.

> Please send the .config.

Please.

Eric

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/