From owner-freebsd-current@FreeBSD.ORG Sun May 5 07:24:57 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 5DB9DBBB for ; Sun, 5 May 2013 07:24:57 +0000 (UTC) (envelope-from devel@stasyan.com) Received: from mx.providersolutions.ru (mx.providersolutions.ru [89.253.252.22]) by mx1.freebsd.org (Postfix) with ESMTP id 869BB2BF for ; Sun, 5 May 2013 07:24:55 +0000 (UTC) Received: (qmail 30580 invoked from network); 5 May 2013 07:24:46 -0000 Received: from unknown (HELO mx.providersolutions.ru) ([89.253.252.14]) by 89.253.252.22 with SMTP; 5 May 2013 07:24:46 -0000 Received: from b-internet.212.164.232.186.nsk.rt.ru (b-internet.212.164.232.186.nsk.rt.ru [212.164.232.186]) by rsnx.ru (Horde Framework) with HTTP; Sun, 05 May 2013 11:24:46 +0400 Message-ID: <20130505112446.33066vaj8hyph932@webmail01.providersolutions.ru> Date: Sun, 05 May 2013 11:24:46 +0400 From: devel@stasyan.com To: Rainer Hurling Subject: Re: kernel panic with _autoload_ nvidia driver References: <20130505100100.62750v3fqplti0t8@webmail01.providersolutions.ru> <5185FD5D.1090502@gwdg.de> In-Reply-To: <5185FD5D.1090502@gwdg.de> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251; DelSp="Yes"; format="flowed" Content-Disposition: inline Content-Transfer-Encoding: 7bit User-Agent: Internet Messaging Program (IMP) H3 (4.3) Cc: freebsd-current@freebsd.org X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.14 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, 05 May 2013 07:24:57 -0000 Hello ! >> This problems appears about 4-6 months ago after updating of -CURRENT >> host. >> Unable to boot host with nvidia_load="YES" in loader.conf because panic. >> But when nvidia driver loads manually via kldload, everything OK. >> Nvidia driver version is 310.44 at this moment, but problem was and on >> earlier version too. > As far as I can tell this is OK again with nvidia version 319.17. I've got panic with nvidia-driver 319.17 too.