From owner-freebsd-current@FreeBSD.ORG Sun May 5 06:34:09 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 6F237414 for ; Sun, 5 May 2013 06:34:09 +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 11EF81C7 for ; Sun, 5 May 2013 06:34:08 +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 1UYsWM-00037z-BT; Sun, 05 May 2013 08:34:06 +0200 Message-ID: <5185FD5D.1090502@gwdg.de> Date: Sun, 05 May 2013 08:34:05 +0200 From: Rainer Hurling User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:17.0) Gecko/20130404 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> In-Reply-To: <20130505100100.62750v3fqplti0t8@webmail01.providersolutions.ru> Content-Type: text/plain; charset=ISO-8859-1 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 06:34:09 -0000 On 05.05.2013 08:01 (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. This version is not in the ports yet, but you can try it by overwriting the Makefiles version number ('make makesum' also adjusts the distfile than). HTH, Rainer > > 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) > (kgdb) backtrace > #0 doadump (textdump=0) at pcpu.h:253 > #1 0xc050a991 in db_dump (dummy=-1062503683, dummy2=0, dummy3=-1, > dummy4=0xfad2c8b4 "") at /usr/src/sys/ddb/db_command.c:543 > #2 0xc050a487 in db_command (cmd_table=) at > /usr/src/sys/ddb/db_command.c:449 > #3 0xc050a1a0 in db_command_loop () at /usr/src/sys/ddb/db_command.c:502 > #4 0xc050c9e0 in db_trap (type=, code=-86848816) > at /usr/src/sys/ddb/db_main.c:231 > #5 0xc0ab8278 in kdb_trap (type=, code= optimized out>, tf=) > at /usr/src/sys/kern/subr_kdb.c:654 > #6 0xc0e9f1ae in trap (frame=) at > /usr/src/sys/i386/i386/trap.c:720 > #7 0xc0e8835c in calltrap () at /usr/src/sys/i386/i386/exception.s:169 > #8 0xc0ab7afd in kdb_enter (why=0xc10786cb "panic", msg= optimized out>) at cpufunc.h:71 > #9 0xc0a81503 in vpanic (fmt=, ap= out>) at /usr/src/sys/kern/kern_shutdown.c:747 > #10 0xc0a813ba in kassert_panic (fmt=) at > /usr/src/sys/kern/kern_shutdown.c:642 > #11 0xc0acfb55 in witness_warn (flags=, lock= optimized out>) at /usr/src/sys/kern/subr_witness.c:1727 > #12 0xc0ac7d95 in userret (td=0xc866c000, frame=) > at /usr/src/sys/kern/subr_trap.c:151 > #13 0xc0e9fff1 in syscall (frame=) at > subr_syscall.c:178 > #14 0xc0e883f1 in Xint0x80_syscall () at > /usr/src/sys/i386/i386/exception.s:267 > #15 0x00000033 in ?? () > Previous frame inner to this frame (corrupt stack?) > Current language: auto; currently minimal >