Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 05 May 2013 12:44:33 +0400
From:      devel@stasyan.com
To:        Rainer Hurling <rhurlin@gwdg.de>
Cc:        danfe@freebsd.org, freebsd-current@freebsd.org
Subject:   Re: kernel panic with _autoload_ nvidia driver
Message-ID:  <20130505124433.11411hx38g6ntb01@webmail01.providersolutions.ru>
In-Reply-To: <518617C5.70404@gwdg.de>
References:  <20130505100100.62750v3fqplti0t8@webmail01.providersolutions.ru> <5185FD5D.1090502@gwdg.de> <20130505112446.33066vaj8hyph932@webmail01.providersolutions.ru> <518617C5.70404@gwdg.de>

next in thread | previous in thread | raw e-mail | index | archive | help
     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?







Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130505124433.11411hx38g6ntb01>