>> panic: amap_lookups: offset out of range
>	:
>> >Fix:
>> 	Reverting to uvm_map.c revision 1.120 prevents the panic.
>
>If the merge was bi-merge, and the prev_entry has amap, need to extend
>amap again?

bimerge only currently occurs in the kernel, where no amaps are
involved.

entries involving amaps aren't forward (or bi) merged, only possibly
back merged.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
werdna@squooshy.com       * "information is power -- share the wealth."