Re: dtrace return hook missing for some iokit funcs?
Re: dtrace return hook missing for some iokit funcs?
- Subject: Re: dtrace return hook missing for some iokit funcs?
- From: Andrew Gallatin <email@hidden>
- Date: Thu, 22 Apr 2010 20:16:39 -0400
Terry Lambert wrote:
On Apr 22, 2010, at 2:17 PM, Andrew Gallatin wrote:
Terry Lambert wrote:
If you compile a DEBUG kernel, you will get an IOLog telling you more
or less exactly what's going on.
Any words of wisdom for a DEBUG kernel? I"m crashing early in boot
when I try to use it (preemption (1) != 0!) from the context of kext.
It seems to happen before the ethernet driver is loaded, so I'm pretty
much DOA.
I used the instructions here (except used the versions on the 10.6.3
page since the crashbox runs 10.6.3):
http://shantonu.blogspot.com/2009/09/mac-os-x-kernel-source-xnu-has-been.html
Then I copied the resulting mach_kernel to / and rebooted.
Is there something else I need to do, or does a 10.6.3
DEBUG kernel just not boot?
Generally a panic in an otherwise unmodified DEBUG kernel is either an
invalid assertion, or there's an OSBundleRequired/Root in a plist
somewhere that's not really required and is shooting you in the foot.
>
In the case of an invalid assertion, you can either comment it out or
change it to a printf (since we use these kernels internally, there
should be no issues there, however).
To rule out a bogus KEXT, you should hold down the shift key to boot it
in "safe mode" so that it doesn't load non-required KEXTs; this may get
you all the way up. If not, check for third party KEXTs.
No, but it somehow re-orders things so that the Intel ethernet driver
gets loaded prior to the crash, so I might actually be able to get
a remote dump if I can remember the trick to make a netdump work
when the arp cache is empty and there is no IP assigned yet.
FWIW, this assertion (I assume you meant "preemption_level(1) != 0"???)
is meant to identify locations where someone is holding a simple lock
while attempting to acquire a mutex. Basically, it means they are
Yes, that's the one. No serial console or dump, so I'm transcribing
things from a monitor just at the limits of my aging vision.
FWIW, I'm loading my driver manually, so this is one bug thats not
mine ;)
So, just to be sure, it is supposed to be safe to build a kernel and
just copy it into /mach_kernel, right? Or is there more stuff I'm
supposed to be updating from my build?
Thanks again,
Drew
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-kernel mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden