From owner-freebsd-current@FreeBSD.ORG Sun May 5 08:26:53 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 182466C6 for ; Sun, 5 May 2013 08:26:53 +0000 (UTC) (envelope-from rhurlin@gwdg.de) Received: from amailer.gwdg.de (amailer.gwdg.de [134.76.10.18]) by mx1.freebsd.org (Postfix) with ESMTP id D37F13FB for ; Sun, 5 May 2013 08:26:52 +0000 (UTC) Received: from p5dc3fdaa.dip0.t-ipconnect.de ([93.195.253.170] helo=krabat.raven.hur) by mailer.gwdg.de with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1UYuHR-00075m-3X; Sun, 05 May 2013 10:26:49 +0200 Message-ID: <518617C5.70404@gwdg.de> Date: Sun, 05 May 2013 10:26:45 +0200 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130505 Thunderbird/17.0.5 MIME-Version: 1.0 To: devel@stasyan.com Subject: Re: kernel panic with _autoload_ nvidia driver References: <20130505100100.62750v3fqplti0t8@webmail01.providersolutions.ru> <5185FD5D.1090502@gwdg.de> <20130505112446.33066vaj8hyph932@webmail01.providersolutions.ru> In-Reply-To: <20130505112446.33066vaj8hyph932@webmail01.providersolutions.ru> Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: 7bit X-Authenticated: Id:rhurlin X-Spam-Level: - X-Virus-Scanned: (clean) by exiscan+sophie 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 08:26:53 -0000 On 05.05.2013 09:24 (UTC+2), devel@stasyan.com wrote: > 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 ... Perhaps danfe@ as the maintainer has more ideas?