hi,

the first panic has been reported by a couple other people now too,
but I haven't had a chance to look at it yet.

the stack trace in the second panic looks pretty messed up,
since ltsleep() doesn't call uvm_aio_aiodone(),
but there was a bug with that panic message that was fixed last week,
so updating your kernel wouldn't be a bad idea.

-Chuck


On Tue, Oct 16, 2001 at 11:25:47AM +0300, Staffan Thomén wrote:
>  Hi,
>   My AlphaPC164 has gotten into the bad habit of panicing after my update to
>   1.5Y on the 3:rd of October. It has done so twice under some (not idle) 
>   network/filesystem load.
> 
>   I didn't manage to get a dump for some reason the first time, but these
>   are the messages I caught in dmesg.
> 
> --- 8< ---
> 
> panic: kernel diagnostic assertion "pcg->pcg_objects[idx] == NULL" failed:
> file "../../../../kern/subr_pool.c", line 1646
> 
> syncing disks... 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18 18
> giving up
> 
> dumping to dev 8,1 offset 536001
> dump i/o error
> 
> 
> sd0(ahc0:0:2:0): polling command not done
> panic: scsipi_execute_xs
> 
> dumping to dev 8,1 offset 536001
> dump device not ready
> 
> --- 8< ---
>  
>   On the second occasion, I had the presence of mind to do a trace, and also
>   received a dump. Tell me if you want it or what you want me to do with it.
> 
>   Trace as follows
> 
> --- 8< ---
> 
> panic: softdep_pageiodone: resid < 0, vp 0xfffffc0007a299a0 lbn 0x0 pcbp 0xfffffc0003b82b50
> Stopped in pid 147 (nfsd) at   cpu_Debugger+0x4:        ret     zero,(ra)
> db> t
> cpu_Debugger() at cpu_Debugger+0x4
> panic() at panic+0x15c
> softdep_pageiodone() at softdep_pageiodone+0x188
> uvm_aio_aiodone() at uvm_aio_aiodone+0xe4
> ltsleep() at ltsleep+0x318
> genfs_gop_write() at genfs_gop_write+0x454
> *ABS*() at      0x4
> 
> CPU 0: fatal kernel trap:
> 
> CPU 0   trap entry      = 0x2 (memory management fault)
> CPU 0   a0              = 0x0
> CPU 0   a1              = 0x1
> CPU 0   a2              = 0x0
> CPU 0   pc              = 0xfffffc00004e54f0
> CPU 0   ra              = 0xfffffc00004e5410
> CPU 0   pv              = 0xfffffc0000325500
> CPU 0   curproc         = 0xfffffc00034b6b68
> CPU 0           pid = 147, comm = nfsd
> 
> Caught exception in ddb.
> 
> db> sync
> syncing disks... ex0: splistptr was 0
> panic lockmgr: locking against myself
> Stopped in pid 147 (nfsd) at    cpu_Debugger+0x4:       ret     zero,(ra)
> db> sync
> 
> dumping to dev 8,1 offset 536001
> [...]
> 
> --- 8< ---
> 
>   If you want, I can make the dump available if anyone wishes to have a look,
>   or tell me what to do.
>   The box has worked *perfectly* up til these two occasions.
> 
>  /Staffan
> 
> --
> -- Staffan Thomén (0x00C37E1F) ---------------------------------------------
> Totally illogical, there was no chance.
> 		-- Spock, "The Galileo Seven", stardate 2822.3