From: Leigh Brown [EMAIL PROTECTED]
Date: Sun, 17 Dec 2006 18:13:06 - (GMT)
It was all going so well, and then it deadlocked. What can be done
about this?
Sorry for taking so long about this.
The problem is that tcp_md5sig_pool_lock is taken in both
software-interrupt and
It was all going so well, and then it deadlocked. What can be done
about this?
SysRq : Show Regs
Pid: 2330, comm: torture
EIP: 0060:[c02a6240] CPU: 0
EIP is at _spin_lock+0x5/0xf
EFLAGS: 0282Not tainted (2.6.19.1 #2)
EAX: c03187e4 EBX: ECX: fa01a8c0 EDX: c52f81e0
