Re: why sometimes can't I find the panic.log file when kernel panic occurred?
site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Hi Jason, On Nov 4, 2004, at 12:57 AM, Jason Geng wrote: Normally yes. --gc __________________________________________________________________ Garth Cummings Apple Developer Technical Support gcummings@apple.com _______________________________________________ Do not post admin requests to the list. They will be ignored. Darwin-kernel mailing list (Darwin-kernel@lists.apple.com) Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/darwin-kernel/site_archiver%40lists.a... This email sent to site_archiver@lists.apple.com Thanks for Garth Cummings' kind help, in the email
Re: single machine debugging?/advice for noob on OS X panic analysis
Take a look at Technical Note 2063
<http://developer.apple.com/technotes/tn2002/tn2063.html>, titled
"Understanding and Debugging Kernel Panics."
I have read the article carefully, and it is quite helpful. But my question is: Sometimes after kernel panic occurred, I could find the 'panic.log' file in the directory '/Library/Logs', however, sometimes I couldn't. Why? There are a couple of reasons for this. One is described in the technote: if the debug flags are set in boot-args you won't get a panic log. But the other reason is a known bug in 10.2.x where certain long panic dumps would not be saved properly. This was fixed in Panther. The workaround is to turn on the debug flags so that you get the panic log dumped to the screen as was done prior to 10.2. My kernel version is MAC OS 10.2.8, kern.version = Darwin Kernel Version 6.8: Wed Sep 10 15:20:55 PDT 2003; root:xnu/xnu-344.49.obj~2/RELEASE_PPC I guess those unlogged kernel panics were caused by handlers of my driver dealing with DMA operation or hardware interrupt. In these situations, can darwin save the panic.log correctly? http://developer.apple.com/technicalsupport smime.p7s
participants (1)
-
Garth Cummings