On Fri, Feb 26, 2010 at 09:36:43AM -0800, Kristin Amundsen-Cubanski wrote: > So, the big question for me is if there is any way for me to work around > this? My primary server paniced again just a few mins ago on a fatal IP > null pointer deference that I've been trying to get the patch for.
Is our support organization providing you with a patch? If so, they would be the best people to contact to get this issue resolved. Here's a copy of the pstack output you provided last night: kris...@waldorf:~# pstack `pgrep pkg` 27967: /usr/bin/python2.4 /usr/bin/pkg image-update -v fed819d5 ioctl (d8aa5e0, 5a14, 8043480, 1020) + 15 fdf5e7f0 zfs_iter_snapshots (d8aa5e0, fdf5fde8, 8045d00, 0) + 7c fdf60112 zfs_promote (cd81730, fe0283a0, 0, 0) + 166 fe01612c be_promote_ds_callback (cd81730, 0, 0, 0) + d0 fe015dce be_promote_zone_ds (caa2b70, c996038, 8047268, fe0145cd) + 2da fe014609 _be_activate (caa2b70, fe029008, 804728c, fe014188) + 3d9 fe0141d0 be_activate (c5f8528) + 68 fe051be5 beActivate (0, c783b4c, 0, feeceb7c) + 69 fef03125 call_function (804738c, 1, 23fe96c1, 82d5aac) + 3f5 fef00221 PyEval_EvalFrame (8142a64, 8295660, 828be84, 0) + 2b11 fef01d23 PyEval_EvalCodeEx (8295660, 828be84, 0, c4b975c, 1, c4b9760) + 903 fef032f4 fast_function (dcb3764, 804754c, 1, 1, 0, 0) + 164 fef02dff call_function (804754c, 1, 6f, 0) + cf fef00221 PyEval_EvalFrame (c4b95e4, 807def4, 828be84, 0) + 2b11 fef01d23 PyEval_EvalCodeEx (8295720, 828be84, 0, 84789fc, 1, 8478a00) + 903 fef032f4 fast_function (829656c, 804770c, 1, 1, 0, feebadd4) + 164 fef02dff call_function (804770c, 0, 200, 0) + cf fef00221 PyEval_EvalFrame (847888c, 827b6a0, 8279acc, 0) + 2b11 fef03288 fast_function (84dbb1c, 804784c, 1, 1, 0, feebadd4) + f8 fef02dff call_function (804784c, 0, 43b, 0) + cf fef00221 PyEval_EvalFrame (85061bc, 833bb20, 8079824, 0) + 2b11 fef03288 fast_function (84dd56c, 804798c, 2, 2, 0, feebadd4) + f8 fef02dff call_function (804798c, 2, de333679, 0) + cf fef00221 PyEval_EvalFrame (8124e64, 8346920, 8079824, 0) + 2b11 fef03288 fast_function (84ddaac, 8047acc, 0, 0, 0, 0) + f8 fef02dff call_function (8047acc, 0, 322, 0) + cf fef00221 PyEval_EvalFrame (80af5fc, 8346960, 8079824, 8079824) + 2b11 fef01d23 PyEval_EvalCodeEx (8346960, 8079824, 8079824, 0, 0, 0) + 903 feefd66e PyEval_EvalCode (8346960, 8079824, 8079824, 0) + 22 fef212a1 run_node (8061338, 8047df3, 8079824, 8079824, 8047c3c, 1) + 39 fef20425 PyRun_SimpleFileExFlags (fee037e0, 8047df3, 1, 8047c3c) + 14d fef26ebb Py_Main (4, 8047d1c, 8047d30, feffb7b4) + 86b 080509bd _start (4, 8047de0, 8047df3, 8047e00, 8047e0d, 0) + 7d This shows that the looping is either occuring in libzfs or in libbe. The packaging software itself isn't what's causing the problem. I would ask on zfs-discuss or caiman-discuss, which are the zfs and libbe groups, respectively. One of those teams might be able to provide you with a workaround. However, since the problem isn't in the packaging software, we can't fix it there. -j _______________________________________________ pkg-discuss mailing list [email protected] http://mail.opensolaris.org/mailman/listinfo/pkg-discuss
