Originally posted by: SystemAdmin

when my disk driver returned error for each ddstrategy calling, the system suspended some application, such as dd, ls, etc. from kdb subcommand dla, i found a few thread were waiting for a complex-lock, which owned by a thread, whose stack is:
(0)> sw 252;f
Switch to thread: <pvthread+007E00>
pvthread+007E00 STACK:
0004AE78.backt+000000 (00201C87, 2FF3A868, 4E240000, 00000000,
2FF3B400, 00000106 ??)
0004BC7C.vcs_movep_excp+000020 (??, ??, ??, ??, ??, ??)
001358F4vmpcopy+0004A8 (??, ??, ??, ??, ??, ??, ??)
001367B4vmfcopyin+000570 (??, ??, ??, ??, ??, ??)
00135F54vm_uiomove+000390 (??, ??, ??, ??)
00411284writei+000108 (??, ??, ??, ??, ??)
00411C08jfs_rdwr+00054C (??, ??, ??, ??, ??, ??, ??, ??)
00395C58vnop_rdwr+000094 (??, ??, ??, ??, ??, ??, ??, ??)
00370028rwuio+0000D0 (??, ??, ??, ??, ??)
00370240rdwr+000158 (??, ??, ??, ??, ??)
0036F9D0kwrite+0000E0 (00000004, 40000000, 00008000)
00003A90.sys_call+000000 ()
D0210684write+000124 (??, ??, ??)
10001FF0wcbuf+000038 (??, ??)
10002FB8do_child+000128 ()
10002998prep_mbuf+000368 ()
10000EBCmain+000998 (??, ??)
10000188__start+000088 ()

did the above calling blocked for ever? why? AIX's bug?

my OS is AIX 5200-04

thanks.

#AIX-Forum

Originally posted by: nagger

I don't think you are going this very deep kernel internals debugging session question answered here?
It reminds me of "Name That Tune"
Where you expecting some one to recognise the call stack?

All I can suggest is a call to AIX Support and run it passed them and back to level three support.

I do note you are AIX 5.2 ML04 - ek!!
Any chance you can take the upgrade to the latest ML?
From memory ML03 and ML04 for AIX 5.2 were ... um ... challenging releases.
This is what AIX support will first ask you to do anyway.
#AIX-Forum