Date: Sun, 25 Aug 1996 01:55:37 -0600 (MDT) From: Dave Andersen <angio@aros.net> To: tinguely@plains.nodak.edu (Mark Tinguely) Cc: freebsd-hackers@freebsd.org Subject: Re: kernel vm_page_alloc_contig() can indirectly cause kernel page faults Message-ID: <199608250755.BAA26732@terra.aros.net> In-Reply-To: <199608250327.WAA26323@plains.nodak.edu> from "Mark Tinguely" at Aug 24, 96 10:27:02 pm
next in thread | previous in thread | raw e-mail | index | archive | help
Is this related to an interesting kernel panic I stumbled across a while ago? It was on a -stable SNAP system from just before 2.1.5R came out. I mmapped() a relatively large block of data (about 50 megs) and, if I accessed somewhere near the end of it, it would cause a kernel panic. This was in a non-priviledged user program. The bug appears to have been corrected in 2.1.5R, however, so I didn't bother looking in to it. I don't read the commit logs too often. -Dave Andersen Lo and behold, Mark Tinguely once said: > > I reported this panic last summer when I started writing the Meteor driver. > THe work around I used wast to start the allocation starting at the > first Meg mark, at that time I speculated it was treating the low memory > and the first meg as being contiguous even though there is a memory > hole between them. Starting contiguous allocation at/after the first > meg never caused anymore panics, so I left it at that. > > --mark. > -- angio@aros.net Complete virtual hosting and business-oriented system administration Internet services. (WWW, FTP, email) http://www.aros.net/ http://www.aros.net/about/virtual "There are only two industries that refer to their customers as 'users'."
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199608250755.BAA26732>