Re: panic: kthread_create called too soon

["Adrian M. Nida" <nida@xxxxxxxx>]

Quoting Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>:
>     I've committed a fix to the SMB module startup problem.  Please try
>     again with the latest HEAD.
<Snip/>

Ok, we're getting further.  It now hangs on the password prompt for about a 
minute and then panics with:

"td_pri is/would-go negative! 0xc133c300 -22"

Now that I'm successfully generating cores, you can grab the latest (*.0) from:

http://www.labthug.com/DragonFly/PanicsAndDumps/

2005-12-05.jpg is a digicam pic of the backtrace as it appeared on the screen.  
The backtrace below is generated from the gdb program.  However, it doesn't 
seem to be as complete as the one in the picture, ideas?  I'm running GENERIC.

Also, I want to thank the people that turned on my lights about generating 
these things.  I'll be an uber UNIX hacker yet :-)

Adrian

---BackTrace from gdb---------
#0  dumpsys () at /usr/src/sys/kern/kern_shutdown.c:527
#1  0xc02aa324 in boot (howto=260) at /usr/src/sys/kern/kern_shutdown.c:360
#2  0xc02aa7d6 in panic (fmt=0xc04f3bdc "from debugger") at /usr/src/sys/kern/
kern_shutdown.c:673
#3  0xc016228e in db_panic (addr=-1068907666, have_addr=0, count=-1, modif=0xd01
b7640 "") at /usr/src/sys/ddb/db_command.c:449
#4  0xc0162223 in db_command (last_cmdp=0xc05a9750, cmd_table=0x0, aux_cmd_
tablep=0xc054d250, aux_cmd_tablep_end=0xc054d268) at /usr/src/sys/ddb/db_
command.c:345
#5  0xc0162303 in db_command_loop () at /usr/src/sys/ddb/db_command.c:471
#6  0xc0164fe0 in db_trap (type=3, code=0) at /usr/src/sys/ddb/db_trap.c:72
#7  0xc049c018 in kdb_trap (type=3, code=0, regs=0xd01b7758) at /usr/src/sys/i
386/i386/db_interface.c:150
#8  0xc04b0592 in trap (frame=
      {tf_fs = -1053622248, tf_es = -803536880, tf_ds = -803536880, tf_edi = 1, 
tf_esi = -1068288588, tf_ebp = -803506272, tf_isp = -803506300, tf_ebx = 260, tf
_edx = -1072988160, tf_ecx = 0, tf_eax = 18, tf_trapno = 3, tf_err = 0, tf_eip =
 -1068907666, tf_cs = 8, tf_eflags = 642, tf_esp = -1068410832, tf_ss = -
1068483857})
    at /usr/src/sys/i386/i386/trap.c:811
#9  0xc049d2ff in calltrap () at /usr/src/sys/i386/i386/exception.s:774
#10 0xc1330018 in ?? ()
#11 0xd01b0010 in ?? ()
#12 0xd01b0010 in ?? ()
#13 0x00000001 in ?? ()
#14 0xc05335b4 in ?? ()
#15 0xd01b77a0 in ?? ()
#16 0xd01b7784 in ?? ()
#17 0x00000104 in ?? ()
#18 0xc00b8000 in ?? ()
#19 0x00000000 in ?? ()
#20 0x00000012 in ?? ()
#21 0x00000003 in ?? ()
#22 0x00000000 in ?? ()
#23 0xc049c36e in Debugger (msg=0x0) at cpufunc.h:68
#24 0xc02aa7ce in panic (fmt=0xc05335b4 "td_pri is/would-go negative! %p %d") at
 /usr/src/sys/kern/kern_shutdown.c:671
#25 0xc02b0be1 in crit_panic () at /usr/src/sys/kern/lwkt_thread.c:1404
#26 0xc02a0511 in lockmgr (lkp=0xc15d7e98, flags=65542, interlkp=0xd01b7818, td=
0xc133c300) at thread2.h:162
#27 0xd0e29cb8 in ?? ()
----End--------
The rest is pretty much still in the same format.  If it helps to go back 
further, let me know and I will.




-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/