Re: alpha kernel hang at boot

[Nicolas Joly <njoly%pasteur.fr@localhost>]

On Wed, Feb 01, 2012 at 02:12:32PM -0700, Michael L. Hitch wrote:
> On Wed, 1 Feb 2012, Nicolas Joly wrote:
> 
> >I cannot boot my PWS500au machine with a recent kernel anymore ... It
> >hangs at some point.
> 
>   How recent?  I saw a change recently that may fix a powerpc problem and 
> there was an indication that it may help mips and alpha.

I encountered it first with 5.99.62, and 5.99.63 made no progress.

> >This seems to be related to recent kmem/vmem changes ... an old
> >5.99.60 version does show any problem.

Sorry. Must read: an old 5.99.60 version does not show any problem

> >Any idea ?
> 
>   I tried booting kernels from the 201201312100Z build, and they were able 
> to get to starting init.  Then they paniced in sysctl_locate.  It appeared 
> to be trying to access 0xfffffe0000000008 - which I think is the start of 
> the kernel virtual address space.

Yes, i saw something similar ... but now it seems stuck in init. I i
enter ddb at that time i do have :

root file system type: ffs
~Stopped in pid 1.1 (init) at    netbsd:cpu_Debugger+0x4:        ret    
zero,(ra)
db> bt
cpu_Debugger() at netbsd:cpu_Debugger+0x4
comintr() at netbsd:comintr+0x79c
alpha_shared_intr_dispatch() at netbsd:alpha_shared_intr_dispatch+0x5c
sio_iointr() at netbsd:sio_iointr+0x4c
interrupt() at netbsd:interrupt+0x24c
XentInt() at netbsd:XentInt+0x1c
--- interrupt (from ipl 0) ---
rw_enter() at netbsd:rw_enter+0x154
vm_map_lock_read() at netbsd:vm_map_lock_read+0x38
uvm_fault_internal() at netbsd:uvm_fault_internal+0xe8
trap() at netbsd:trap+0x5e8
XentMM() at netbsd:XentMM+0x20
--- memory management fault ---

-- 
Nicolas Joly

Projects and Developments in Bioinformatics
Institut Pasteur, Paris.