Re: 2.6.23-rc1-mm1: boot hang on ia64 with memoryless nodes

On Thu, 2007-07-26 at 23:00 +0900, KAMEZAWA Hiroyuki wrote:
> On Thu, 26 Jul 2007 09:53:27 -0400
> Lee Schermerhorn <Lee.Schermerhornhp.com> wrote:
> 
> > On Wed, 2007-07-25 at 17:18 -0400, Lee
Schermerhorn wrote: 
> > > On Wed, 2007-07-25 at 12:38 -0700, Christoph
Lameter wrote:
> > > > (ccing Andy who did the work on the
config stuff)
> > > > 
> > > > On Wed, 25 Jul 2007, Lee Schermerhorn
wrote:
> > > > 
> > > > > I tried to deselect
SPARSEMEM_VMEMMAP.  Kconfig's "def_bool=y"
wouldn't
> > > > > let me :-(.  After hacking the
Kconfig and mm/sparse.c to allow that,
> > > > > boot hangs with no error messages
shortly after "Built N zonelists..."
> > > > > message.
> > > > 
> > > > I get a similar hang here and see the
system looping in softirq / hrtimer 
> > > > code.
> > > > 
> > > > > Backed off to
DISCONTIGMEM+VIRTUAL_MEMORY_MAP, and saw same hang as with
> > > > > (SPARSMEM &&
!SPARSEMEM_VMEMMAP).   
> > > > 
> > > > So its not related to SPARSE VMEMMAP?
General VMEMMAP issue on IA64?
> > > 
> > > This hang is different from the one I see
with SPARSE VMEMMAP -- no
> > > "Unable to handle kernel paging
request..." message.  Just hangs after
> > > "Built N zonelists..."  and some
message about "color" that I didn't
> > > capture.  Next time [:-(]...
> > 
> > The "color" message was actually:
> > 
> > Console:  colour dummy device 80x25
> > 
> > So, now I'm wondering if I'm hitting the
"Regression in serial
> > console..." issue, and the system was
actually booting--I just didn't
> > see any output.  If so, the "Unable to handle
kernel paging request..."
> > hang might well be a problem with
SPARSEMEM_VMEMMAP...
> > 
> About SPARSEMEM_VMEMMAP try this:
> http://lkml.org/lk
ml/2007/7/26/161
> 

Kame-san:

Thank you.  This solved my problem.  I can now boot with
both zx1 and
[with other patches from the mailing lists], generic kernels
on my ia64
platform.

Lee

-
To unsubscribe from this list: send the line
"unsubscribe linux-ia64" in
the body of a message to majordomovger.kernel.org
More majordomo info at  http://vge
r.kernel.org/majordomo-info.html