From owner-freebsd-current@FreeBSD.ORG Sun May 5 08:44:44 2013 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C6674AE4 for ; Sun, 5 May 2013 08:44:44 +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 F19E6655 for ; Sun, 5 May 2013 08:44:43 +0000 (UTC) Received: (qmail 1676 invoked from network); 5 May 2013 08:44:33 -0000 Received: from unknown (HELO mx.providersolutions.ru) ([89.253.252.14]) by 89.253.252.22 with SMTP; 5 May 2013 08:44:33 -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 12:44:33 +0400 Message-ID: <20130505124433.11411hx38g6ntb01@webmail01.providersolutions.ru> Date: Sun, 05 May 2013 12:44:33 +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> <20130505112446.33066vaj8hyph932@webmail01.providersolutions.ru> <518617C5.70404@gwdg.de> In-Reply-To: <518617C5.70404@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: danfe@freebsd.org, 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 08:44:44 -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. > Do you know the workaround to build the port with > 'env USE_GCC=any make' ? > With this it should not panic anymore, but start normal again ... Yes, it works normal with GCC. Thank you ! > Perhaps danfe@ as the maintainer has more ideas?