Re: kernel panic with _autoload_ nvidia driver

From: Rainer Hurling <rhurlin_at_gwdg.de>
Date: Sun, 05 May 2013 08:34:05 +0200
On 05.05.2013 08:01 (UTC+2), devel_at_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=<value optimized out>) 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=<value optimized out>, code=-86848816)
> at /usr/src/sys/ddb/db_main.c:231
> #5  0xc0ab8278 in kdb_trap (type=<value optimized out>, code=<value
> optimized out>, tf=<value optimized out>)
>     at /usr/src/sys/kern/subr_kdb.c:654
> #6  0xc0e9f1ae in trap (frame=<value optimized out>) 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=<value
> optimized out>) at cpufunc.h:71
> #9  0xc0a81503 in vpanic (fmt=<value optimized out>, ap=<value optimized
> out>) at /usr/src/sys/kern/kern_shutdown.c:747
> #10 0xc0a813ba in kassert_panic (fmt=<value optimized out>) at
> /usr/src/sys/kern/kern_shutdown.c:642
> #11 0xc0acfb55 in witness_warn (flags=<value optimized out>, lock=<value
> optimized out>) at /usr/src/sys/kern/subr_witness.c:1727
> #12 0xc0ac7d95 in userret (td=0xc866c000, frame=<value optimized out>)
> at /usr/src/sys/kern/subr_trap.c:151
> #13 0xc0e9fff1 in syscall (frame=<value optimized out>) 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
> 
Received on Sun May 05 2013 - 04:34:09 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:37 UTC