From owner-freebsd-test@FreeBSD.ORG Sun Jul 20 00:23:52 2008 Return-Path: Delivered-To: freebsd-test@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 89A24106566B for ; Sun, 20 Jul 2008 00:23:52 +0000 (UTC) (envelope-from fbsd-ml@scrapper.ca) Received: from pd4mo3so.prod.shaw.ca (idcmail-mo1so.shaw.ca [24.71.223.10]) by mx1.freebsd.org (Postfix) with ESMTP id 7B7738FC12 for ; Sun, 20 Jul 2008 00:23:52 +0000 (UTC) (envelope-from fbsd-ml@scrapper.ca) Received: from pd3mr3so.prod.shaw.ca (pd3mr3so-qfe3.prod.shaw.ca [10.0.141.179]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K4A00JO10ZRZI90@l-daemon> for freebsd-test@freebsd.org; Sat, 19 Jul 2008 17:23:51 -0600 (MDT) Received: from pn2ml4so.prod.shaw.ca ([10.0.121.148]) by pd3mr3so.prod.shaw.ca (Sun Java System Messaging Server 6.2-7.05 (built Sep 5 2006)) with ESMTP id <0K4A0036Y0ZRIZ10@pd3mr3so.prod.shaw.ca> for freebsd-test@freebsd.org; Sat, 19 Jul 2008 17:23:52 -0600 (MDT) Received: from proven.lan ([24.85.241.34]) by l-daemon (Sun ONE Messaging Server 6.0 HotFix 1.01 (built Mar 15 2004)) with ESMTP id <0K4A007G60ZQ4P30@l-daemon> for freebsd-test@freebsd.org; Sat, 19 Jul 2008 17:23:50 -0600 (MDT) Received: from proven.lan (localhost [127.0.0.1]) by proven.lan (8.14.2/8.14.2) with ESMTP id m6JNNorW003892 for ; Sat, 19 Jul 2008 16:23:50 -0700 (PDT envelope-from fbsd-ml@scrapper.ca) Received: from localhost (localhost [[UNIX: localhost]]) by proven.lan (8.14.2/8.14.2/Submit) id m6JNNnJv003891 for freebsd-test@freebsd.org; Sat, 19 Jul 2008 16:23:49 -0700 (PDT envelope-from fbsd-ml@scrapper.ca) Date: Sat, 19 Jul 2008 16:23:49 -0700 From: Norbert Papke To: freebsd-test@freebsd.org Message-id: <200807191623.49766.fbsd-ml@scrapper.ca> Organization: Archaeological Filing MIME-version: 1.0 Content-type: Text/Plain; charset=iso-8859-1 Content-transfer-encoding: 7bit Content-disposition: inline X-Authentication-warning: proven.lan: npapke set sender to fbsd-ml@scrapper.ca using -f User-Agent: KMail/1.9.7 Subject: Fwd: ZFS and nvidia driver -- panic with spontaneous reboot X-BeenThere: freebsd-test@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Test posting area List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 20 Jul 2008 00:23:52 -0000 ---------- Forwarded Message ---------- Subject: Fwd: ZFS and nvidia driver -- panic with spontaneous reboot Date: July 17, 2008 From: Norbert Papke To: freebsd-test@freebsd.org Not showing up in either -questions or -stable ... ---------- Forwarded Message ---------- Subject: ZFS and nvidia driver -- panic with spontaneous reboot Date: July 16, 2008 From: Norbert Papke To: freebsd-stable@freebsd.org I am having a terrible time trying to get my desktop system (recent 7.0-Stable) working with both ZFS and the nvidia proprietary driver (nvidia-driver-173.14.09). The nvidia driver, of course, restricts me to i386. I tried to follow the recommended practice of increasing KVA_PAGES. With this change, I cannot start X -- the nvidia driver errors out. Without the KVA change, I cannot increase kmem sufficiently. It is limited to 512M. ZFS doesn't seem to have any problems with 512M kmem on my workload. Unfortunately, the nvidia driver is less happy. After some time (a couple of days usually), it triggers panics that cause a spontaneous reboot. There is no core dump nor does the kernel debugger take control. Sometimes details are logged, sometimes the details are lost. The details that have been logged always look similar to this: panic: kmem_malloc(847872): kmem_map too small: 322166784 total allocated KDB: stack backtrace: db_trace_self_wrapper(c072d320,f4663990,c052aeaa,c072b6b3,c0794e80,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c072b6b3,c0794e80,c073cd53,f466399c,f466399c,...) at kdb_backtrace+0x29 panic(c073cd53,cf000,1333e000,c073cd4d,7d0,...) at panic+0xaa kmem_malloc(c185408c,cf000,102,f4663a1c,c06b1da0,...) at kmem_malloc+0x28a page_alloc(0,cf000,f4663a0f,102,2000000,...) at page_alloc+0x27 uma_large_malloc(cf000,102,102,c6bd4800,c61dcc60,...) at uma_large_malloc+0x50 malloc(cf000,c1067420,102,c6bd4800,c55e1a00,...) at malloc+0x88 nv_alloc_system_pages(c55e1d00,cf,0,c6bd4858,c6bd4838,...) at nv_alloc_system_pages+0x5d nv_alloc_pages(c55e1d00,cf,0,0,0,...) at nv_alloc_pages+0x115 _nv003436rm(c55f3c00,0,c9024000,20,cf567000,...) at _nv003436rm+0x3b Am I correct to interpret this as simply "out of memory"? If so, presumably the solution is make more kmem available. What can I do to make ZFS and nvidia work together? Does it work for anybody? Cheers, -- Norbert. ------------------------------------------------------- -------------------------------------------------------