Re: Kernel crashes after sleep: how to debug?

2013-07-19 Thread John Baldwin
On Thursday, July 18, 2013 8:56:58 pm Yuri wrote: > On 07/18/2013 13:52, John Baldwin wrote: > > Are you in frame 8? > > For some reason the debug info is missing in frame 8, but is present in > surrounding frames 7 and 9. > The might be a bug in makefiles that debug flag isn't passed into > sys

UFS related panic (daily <-> find)

2013-07-19 Thread rank1seeker
I had 2 panics: (Both occured at 3 AM, so had to be daily task) First (Jul 2 03:06:50 2013): -- Fatal trap 12: page fault while in kernel mode fault virtual address = 0x19 fault code = supervisor read, page not present instruction pointer = 0x20:0xc06caf34 stack pointer

Re: Kernel crashes after sleep: how to debug?

2013-07-19 Thread Yuri
On 07/19/2013 08:00, John Baldwin wrote: Well, you can probably find the value of 'm' in a register if you look at the dissassembly around the fault. You can then cast that pointer to the right type and print its contents. Here is the value of *m in frame 8: (kgdb) p *(struct vm_page*)0xfe

Re: Kernel crashes after sleep: how to debug?

2013-07-19 Thread John Baldwin
On Friday, July 19, 2013 3:32:43 pm Yuri wrote: > On 07/19/2013 08:00, John Baldwin wrote: > > Well, you can probably find the value of 'm' in a register if you look at the > > dissassembly around the fault. You can then cast that pointer to the right > > type and print its contents. > > Here i

Re: Kernel crashes after sleep: how to debug?

2013-07-19 Thread Yuri
On 07/19/2013 14:04, John Baldwin wrote: Hmm, that definitely looks like garbage. How are you with gdb scripting? You could write a script that walks the PQ_ACTIVE queue and see if this pointers ends up in there. It would then be interesting to see if the previous page's next pointer is corrupt