Date: Thu, 29 Apr 1999 09:19:30 -0700 From: Fred Gilham <gilham@snapdragon.csl.sri.com> To: freebsd-stable@FreeBSD.ORG Subject: Change in VM_MAXUSER_ADDRESS affects CMU Lisp Message-ID: <199904291619.JAA12030@csla.csl.sri.com>
next in thread | raw e-mail | index | archive | help
Hello, I track FreeBSD-stable on three machines I use. Some time between April 14 and April 27, something changed. On one machine, with a kernel built on April 14, in assym.s in my kernel compile directory, there's the following: #define VM_MAXUSER_ADDRESS 0xefbfe000 On another machine, with a kernel built on April 28, it has changed to #define VM_MAXUSER_ADDRESS 0xbfbfe000 Unfortunately, the version of CMU lisp I use executes the following mmap (gotten from ktrace): 23673 lisp.save CALL mmap(0x48000000,0x7ffff000,0x7,0x1012,0xffffffff,0,0,0) 23673 lisp.save RET mmap -1 errno 22 Invalid argument (It's trying to map 2GB into its `dynamic memory space'.) On the machine with the older kernel, this works: 23623 lisp CALL mmap(0x48000000,0x7ffff000,0x7,0x1012,0xffffffff,0,0,0) 23623 lisp RET mmap 1207959552/0x48000000 Obviously, the change in VM_MAXUSER_ADDRESS causes the mmap to be outside the allowed memory area. I'm wondering if this is change was intentional or if it could be backed out without causing a lot of trouble. -Fred To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199904291619.JAA12030>