----- Original Message ----- From: "Dan Mack" <mack_at_macktronics.com> > I think I may have hit the same problem; I'm going to stay connected > to the console and see if it happens again; this is what I see > currently with the back-trace: > > db> bt > Tracing pid 0 tid 100070 td 0xfffff8000e088920 > kdb_enter() at kdb_enter+0x3e/frame 0xfffffe085ef1d980 > vpanic() at vpanic+0x146/frame 0xfffffe085ef1d9c0 > panic() at panic+0x43/frame 0xfffffe085ef1da20 > deadlkres() at deadlkres+0x35c/frame 0xfffffe085ef1da70 > fork_exit() at fork_exit+0x84/frame 0xfffffe085ef1dab0 > fork_trampoline() at fork_trampoline+0xe/frame 0xfffffe085ef1dab0 > --- trap 0, rip = 0, rsp = 0xfffffe085ef1db70, rbp = 0 --- > > I just updated to I think 268921 earlier today and this is the first > time I've had a panic (HEAD-268921 that is) > > I'll try to get some more data if I can get it back up and running. That doesn't look like a related trace tbh. Regards SteveReceived on Sun Jul 20 2014 - 21:57:46 UTC
This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:40:51 UTC