Re: ntpd panic but only in a domu

[Sarton O'Brien <bsd-xen%roguewrt.org@localhost>]

Sarton O'Brien wrote:
> I'm still seeing this but only in a domu and only on a domu with significant 
> memory usage (ie. a domu runng slapd/postgress and a domu running 
> apache/zope) and using the 'disable kernel' option  doesn't help, if there is 
> anything else I can provide, let me know. I can trigger this at will:
>
> panic: uvm_map_pageable: stale map
> Stopped in pid 273.1 (ntpd) at  netbsd:breakpoint+0x4:  popl    %ebp
> db> bt
> breakpoint(c0432597,cc525b18,c0448080,c028cb4e,ca292320) at 
> netbsd:breakpoint+0x
> 4
> panic(c041dd73,bb96f000,bb989000,7,1) at netbsd:panic+0x1bf
> uvm_map_pageable(ca292310,bb96f000,bb989000,0,1) at 
> netbsd:uvm_map_pageable+0x44
> 7
> uvm_mmap(ca292310,cc525cc8,1a000,5,7) at netbsd:uvm_mmap+0x50d
> sys_mmap(cc4b7620,cc525d00,cc525d28,c0399d15,c038f086) at 
> netbsd:sys_mmap+0x342
> syscall(cc525d48,1f,1f,bfbf001f,bba6001f) at netbsd:syscall+0xb8
>   

Am I the only one seeing this? I've been holding off on domu updates for 
about 3 months due to this issue, as it seems timed is definately not a 
suitable replacement for ntpd, not at least with dom0 rejecting 
broadcasts. I'd feel less lonely with at least a 'me too' :)

Sarton