Re: debugging kernel paniced system
Re: debugging kernel paniced system
- Subject: Re: debugging kernel paniced system
- From: Nikita Danilov <email@hidden>
- Date: Tue, 27 Jul 2004 14:46:36 +0400
Andrew Gallatin writes:
>
Hello, Andrew,
>
Nikita Danilov writes:
>
> faster, emitting rather loud noise. It looks like CPU monitoring
>
> hardware is confused somehow (maybe thinks that CPU is in busy loop with
>
> interrupts off?), or just cannot work correctly without constant OS
>
> feedback. So, questions are:
>
>
>
> (a) is it possible to work around this, and
>
>
I work around the noise by taking a dump of kernel memory to
>
another machine. This works remarkably like "crashdumps" on
>
tradidtional UNIX machines (ie, you don't need to keep the machine in
>
the crashed state, you can reboot and debug the crash later). Its
>
loud for a while, but usually its finished dumping before I could have
>
finished with a gdb session.
>
>
You just need to have kdumpd running via inetd somewhere on your
>
network, and you need to have the appropriate boot args.
>
I use:
>
>
boot-args -v debug=0xdae _panicd_ip=172.31.193.10
Hmm.. seems osfmk/kern/debug.h contains more flags than mentioned in
KernelProgramming.pdf. I wonder what
#define DB_PANICLOG_DUMP 0x2000 /* Send paniclog on panic,not core*/
means.
Nikita.
_______________________________________________
darwin-kernel mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/darwin-kernel
Do not post admin requests to the list. They will be ignored.