Hi,

On Friday, 30 of September 2005 01:59, Siddha, Suresh B wrote:
> On Fri, Sep 30, 2005 at 01:04:35AM +0200, Rafael J. Wysocki wrote:
> > On Friday, 30 of September 2005 00:29, Siddha, Suresh B wrote:
> > > Did you try just only my patch on top of 2.6.14-rc2? You can get that
> > > patch from http://www.x86-64.org/lists/discuss/msg07313.html
> > 
> > The patch that I tested is attached.  I think it's the same one.  I've just applied
> > it on top of 2.6.14-rc2-git7, and it doesn't boot.
> 
> It works fine for me. Only thing I see though is a warning for UP configuration.
> Other than that UP, SMP(with and without hotplug) kernels boot fine. I will
> send the warning fix to Andrew.
> 
> > The problem (as I see it) is this:
> > In x86_64_start_kernel() you copy boot_level4_pgt[] into init_level4_pgt[],
> > and you make the latter your current PGD by loading cr3 with its address.
> > Fine.  With this PGD you call start_kernel() which calls setup_arch(), which
> > calls zap_low_mappings(0) that fills init_level4_pgt[] (which at this moment
> > is still your current PGD) with zeros ...
> 
> It clears only the zeroth entry. Not the whole pgd.

You are absolutely right.  I have misread this, sorry.

> Please send me your .config so that I can try reproducing the issue locally
> here.

Of course.  The .config is attached.  Generally, it's a non-SMP box, and commenting
out the zap_low_mappings((0) in setup_arch() makes the box boot again.

Greetings,
Rafael