Subject: Re: current-i386 mv failures
To: Hisashi T Fujinaka <htodd@twofifty.com>
From: Kurt Schreiner <ks@ub.uni-mainz.de>
List: current-users
Date: 05/22/2007 08:56:54
On Mon, May 21, 2007 at 05:55:24PM -0700, Hisashi T Fujinaka wrote:
> My kernel keeps panicking while I'm trying to "build world" with:
> 
> uvm_fault(0xce59f9a8, 0x72646000, 1) -> 0xe
> kernel: supervisor trap page fault, code=0
> Stopped in pid 12460.1 (mv) at netbsd:malloc+0x72: movl 0(%esi),%eax
> db{1}> bt
> malloc(4,c0539580,0c02b7003,ce64fbf0) at netbsd:malloc+0x72
> rename_files(0,ce64fc48,ce64c68,2,c037a07d) at netbsd:rename_files+0x25c
> syscall_plain() at netbsd:syscall_plain+0x11b
> --- syscall (number 128) ---
> 0xbbba6cf:
> db{1}>
> 
> Any help?
Hm, looks like what I had yesterday on amd64. Tobias Nygren <tnn@...>
said:
> Most likely another manifestation of kern/36358.
> Until someone fixes it, it can be worked around by removing
> pseudo-device veriexec from your kernel configuration.
I compiled a kernel without the whole veriexec stuff and the system
has no problems anymore...

Kurt