From owner-freebsd-current@FreeBSD.ORG Sun Jun 26 23:56:35 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D543216A41F for ; Sun, 26 Jun 2005 23:56:35 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from harmony.village.org (vc4-2-0-87.dsl.netrack.net [199.45.160.85]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8EC3A43D4C for ; Sun, 26 Jun 2005 23:56:35 +0000 (GMT) (envelope-from imp@bsdimp.com) Received: from localhost (localhost.village.org [127.0.0.1]) by harmony.village.org (8.13.3/8.13.3) with ESMTP id j5QNra2M017743; Sun, 26 Jun 2005 17:53:36 -0600 (MDT) (envelope-from imp@bsdimp.com) Date: Sun, 26 Jun 2005 17:55:10 -0600 (MDT) Message-Id: <20050626.175510.78315080.imp@bsdimp.com> To: eta@lclark.edu From: "M. Warner Losh" In-Reply-To: <1119829345.3817.62.camel@leguin> References: <1119816026.3817.20.camel@leguin> <20050626191956.A59922@cons.org> <1119829345.3817.62.camel@leguin> X-Mailer: Mew version 3.3 on Emacs 21.3 / Mule 5.0 (SAKAKI) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Cc: cracauer@cons.org, freebsd-current@freebsd.org, adamk@voicenet.com Subject: Re: 6.0-current panic: loading radeon module X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Jun 2005 23:56:36 -0000 In message: <1119829345.3817.62.camel@leguin> Eric Anholt writes: : On Sun, 2005-06-26 at 19:19 -0400, Martin Cracauer wrote: : > > OK, one more try, for everyone who's been having hangs/reboots on X : > > startup since April. Attached is a patch that will hopefully kill the : > > problem off. : > : > The candidate gets 100 points. It fixes the panic and hardware 3D : > worked for a few tests. No other side effects observed. Thanks so : > much! : > : > Out of curiosity, why does a 32 MB VRAM card try to map 128 MB? : : Do you only had 32MB? If so, oops on my part. Every other case of this : I had seen was 128MB, so I was just assuming. Basically the issue : (afaik) is that you're running out of KVA because framebuffers are large : and KVA isn't all that huge. pmap_mapdev was not designed to handle : failure to allocate memory, so it just paniced instead of returning NULL : (which wouldn't have helped us anyway, due to other issues). Yes. I believe that's correct... Warner