kernel panic with _autoload_ nvidia driver

2013-05-05 Thread devel
was and on earlier version too. Here is output of debugging (full version at http://www.stasyan.com/devel/kern_crash_nvidia_autoload.txt) Loaded symbols for /boot/kernel/udf.ko.symbols #0 doadump (textdump=0) at pcpu.h:253 253 __asm(movl %%fs:%1,%0 : =r (td

Re: kernel panic with _autoload_ nvidia driver

2013-05-05 Thread devel
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

Re: kernel panic with _autoload_ nvidia driver

2013-05-05 Thread devel
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

Re: Patch for FILE problems (was Re: -CURRENT is bad for me...)

2001-02-15 Thread Paul Richards_imap/mail.originative.co.uk/Inbox.sbd/New Mail.sbd/OpenLDAP.sbd/Devel
David O'Brien wrote: On Thu, Feb 15, 2001 at 11:14:38AM +, Paul Richards wrote: Commercial vendors will skip version numbers in their public releases if their internal development required more than one bump. Which ones? Sun Solaris still ships their libc as "libc.so.1", even in