Oliver Yang wrote:
Eric Saxe wrote:
You mean, the a13fade0 was unpinned due to block on a mutex, and
it was in turnstile before.
Later, it was placed into run queue, because the the mutex was
released by other ?
The clock interrupt was at some pointer pinning a13f7de0 (the
priority 105 thr
Eric Saxe wrote:
You mean, the a13fade0 was unpinned due to block on a mutex, and it
was in turnstile before.
Later, it was placed into run queue, because the the mutex was
released by other ?
The clock interrupt was at some pointer pinning a13f7de0 (the priority
105 thread). When it passiv
Oliver Yang wrote:
Eric Saxe wrote:
> ::cpuinfo -v
ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC
0 fec254f8 1b5 10 105 nono t-5676 a13f7de0 sched
|||
RUNNING <--+|+--> PIL THREAD
READY | 10 a13fade0
EXISTS
Eric Saxe wrote:
> ::cpuinfo -v
ID ADDR FLG NRUN BSPL PRI RNRN KRNRN SWITCH THREAD PROC
0 fec254f8 1b5 10 105 nono t-5676 a13f7de0 sched
|||
RUNNING <--+|+--> PIL THREAD
READY | 10 a13fade0
EXISTS | 6
Hi Oliver,
Responses in line below:
Oliver Yang wrote:
Hi All,
Recently, I ran into a hang issue, and I enabled deadman timer by
setting "set snooping =1" in /etc/system file. Finally, we got a
crashdump file.
Does anybody can give me a hint on how to debug hang issue with
enabling deadma
On Monday 27 November 2006 12:40 am, Oliver Yang wrote:
> Hi All,
>
> Recently, I ran into a hang issue, and I enabled deadman timer by
> setting "set snooping =1" in /etc/system file. Finally, we got a
> crashdump file.
This still hung during stress testing last night.
ajd
>
> Does anybody can
Hi All,
Recently, I ran into a hang issue, and I enabled deadman timer by
setting "set snooping =1" in /etc/system file. Finally, we got a
crashdump file.
Does anybody can give me a hint on how to debug hang issue with enabling
deadman?
Here are steps what I have tried on one of crashdump
