ia64 -> panic: deadlkres: possible deadlock detected for 0xe00000001187d880, blocked for 1801437 ticks

[Marcel Moolenaar]

On Apr 2, 2010, at 3:55 PM, Anton Shterenlikht wrote:

> Hi Marcel
> 
> I got this panic while trying to build some port
> on -current (csup'ed on 1-APR-2010)
> 
> panic: deadlkres: possible deadlock detected for 0xe00000001187d880, blocked for 1801437 ticks
> 
> cpuid = 1
> KDB: enter: panic
> [ thread pid 0 tid 100046 ]
> Stopped at      kdb_enter+0x92: [I2]    addl r14=0xffffffffffe1fbf0,gp ;;
> db> 
> db> bt
> Tracing pid 0 tid 100046 td 0xe000000010d4f500
> kdb_enter(0xe000000004853640, 0xe000000004853640, 0xe00000000439d170, 0x793) at kdb_enter+0x92
> panic(0xe00000000484b490, 0xe00000000484b6d0, 0xe00000001187d880, 0x1b7cdd) at panic+0x2f0
> deadlkres(0xa00000007ebca2d8, 0xe00000001187d880, 0xe00000000484b410, 0x1b7cdd) at deadlkres+0x470
> fork_exit(0xe000000004893250, 0x0, 0xa0000000bd3db550) at fork_exit+0x110
> enter_userland() at enter_userland
> db> 
> 
> The panic followed a long freeze, of a sort that
> I've seen a lot on ia64 in the last couple of weeks.
> Do I get the panic (as opposed to a seemingly endless freeze)
> because of a recently added
> 
> 	options         DEADLKRES
> 
> in my kernel config?

Yes, exactly.

At the db> prompt, can you type:
	db> show thread 0xe00000001187d880

This should give you something like:
	Thread 100001 at 0xe00000001187d880:
	 proc (pid 1): 0xe00000301220c000
	 name: kernel
	 stack: 0xa00000021afd2000-0xa00000021afd9fff
	 flags: 0x10005  pflags: 0
	 state: RUNNING (CPU 0)
	 priority: 52
	 container lock: sched lock 0 (0xe000003400ad5080) 

With the thread ID, 100001 in the example above, type:
	db> thread 100001

This should give you something like:
	[ thread pid 1 tid 100001 ]
	kdb_enter+0x92: [I2] addl r14=0xffffffffffe279b8,gp ;;

Then type the following for a backtrace:
	db> bt


FYI,

-- 
Marcel Moolenaar
xcllnt at mac.com