Guido van Rooij wrote:

Try to get a stacktrace from the kernel crash dump.

That's the best I could get for now. My first attempt at getting debug information from the kernel, so I'm not sure how helpful this is.


stopped at fr_queueback +0xa: movl 0x14(%ebx),%eax
ippr_pptp_inout(c3e85e64,c0902180,c0915200,c3e85d94,c0915200) at ippr_pptp_inout +0x13b
appr_check(c3e85e64,c0915200,0,c3e85dbc,c3e85e64) at appr_check +0x165
fr_natin(c3e85e64,c0915200,1,1,c3e85e64) at fr_natin +0x55
fr_checknatin(c3e85e64,c3e85e60,c3e85e64,8,c0511a00) at fr_checknatin


    +0x301
fr_check(c0514816,14,c0808800,0,c3e85f38) at fr_check +0x194
ip_input(c0511a00) at ip_input +0x289
ipintr(c0225be3,0,2f,2f,2f) at ipintr +0x4b
swi_net_next() at swi_net_next

--
Toomas Aas --------------------------------------------------------
|arvutiv�rgu peaspetsialist | head specialist on computer networks|
|Tartu Linnakantselei       | Tartu City Office                   |
----------------------------------------------------- +372 736 1274





Reply via email to