[ Replying to pkg-discuss, since that's where we discuss these things. ] sanjay nadkarni wrote:
> My desktop is running build 136. I tried to upgrade it to build 138 > and pkg image-update hung. > I have taken a pstack of this and it is available at: > http://paste.east.sun.com/1821 > My system has 8GB memory. 2503: /usr/bin/python2.6 /usr/bin/pkg image-update --be-name osol-138 -v feee1476 __clock_gettime (4, 8045d80, 0, fcd9f31c) + 36 fcd9f331 curlx_tvnow (8045dc8, f66b098, 51b6519f) + 21 fcdc7ef1 curl_multi_perform (85998c0) + 71 fce0850f do_multi_perform (88662d4, 0, 8045e78, fed48d92) + 83 fed490c0 call_function (8045eec, 0, 30, 0) + 33c fed46221 PyEval_EvalFrameEx (88e1d34, 0, 875ed74, 0) + 3029 That stack doesn't look like it's hung, just like it's waiting for the network (but johansen might know better). What does a truss look like? If that's silent, how about some dtrace? Or grab the bits needed to get pstack and mdb to spit out Python stack traces? Danek _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
