On 22 January 2011 00:43, Alan Cox alan.l@gmail.com wrote:
On Fri, Jan 21, 2011 at 2:58 PM, Alan Cox alan.l@gmail.com wrote:
On Fri, Jan 21, 2011 at 11:44 AM, John Baldwin j...@freebsd.org wrote:
On Friday, January 21, 2011 11:09:10 am Sergey Kandaurov wrote:
Hello.
Some time
Hello.
Some time ago I faced with a problem booting with 400GB physmem.
The problem is that vm.max_proc_mmap type overflows with
such high value, and that results in a broken mmap() syscall.
The max_proc_mmap value is a signed int and roughly calculated
at vmmapentry_rsrc_init() as u_long
On Friday, January 21, 2011 11:09:10 am Sergey Kandaurov wrote:
Hello.
Some time ago I faced with a problem booting with 400GB physmem.
The problem is that vm.max_proc_mmap type overflows with
such high value, and that results in a broken mmap() syscall.
The max_proc_mmap value is a signed
On 21 January 2011 20:44, John Baldwin j...@freebsd.org wrote:
On Friday, January 21, 2011 11:09:10 am Sergey Kandaurov wrote:
Hello.
Some time ago I faced with a problem booting with 400GB physmem.
The problem is that vm.max_proc_mmap type overflows with
such high value, and that results in
On Fri, Jan 21, 2011 at 12:44:13PM -0500, John Baldwin wrote:
On Friday, January 21, 2011 11:09:10 am Sergey Kandaurov wrote:
Hello.
Some time ago I faced with a problem booting with 400GB physmem.
The problem is that vm.max_proc_mmap type overflows with
such high value, and that
On Fri, Jan 21, 2011 at 11:44 AM, John Baldwin j...@freebsd.org wrote:
On Friday, January 21, 2011 11:09:10 am Sergey Kandaurov wrote:
Hello.
Some time ago I faced with a problem booting with 400GB physmem.
The problem is that vm.max_proc_mmap type overflows with
such high value, and
On Fri, Jan 21, 2011 at 2:58 PM, Alan Cox alan.l@gmail.com wrote:
On Fri, Jan 21, 2011 at 11:44 AM, John Baldwin j...@freebsd.org wrote:
On Friday, January 21, 2011 11:09:10 am Sergey Kandaurov wrote:
Hello.
Some time ago I faced with a problem booting with 400GB physmem.
The
7 matches
Mail list logo