site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com or So 2 questions: _______________________________________________ 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... When you do some bad things in your Kernel Extension (such as writing where you should not, reading a bit too far in buffers, etc...), should a Kernel Panic occur in your Kernel Extension or can it occur later? Since yesterday, I'm "enjoying" random Kernel Panics. I know that I changed something in my work-in-progress kernel extensions but every panic.log I look at is pointing to KP in: com.apple.ATIRadeon9700 (Data access DAR=0x0000000000000000 PC=0x00000000002FB7C8) com.apple.driver.AppleFWOHCI (Data access DAR=0x0000000000000000 PC=0x000000000070D4C0) I know that GPU drivers are not 100% perfect (for instance there are still bugs in the current NVidia drivers) and that since yesterday I have an external Firewire drive (actually a Mac running in Firewire Target mode) plugged to my machine. I tested my code in user land for different scenarios and I didn't experience any crash. - are there known issues with these (both PCI) com.apple. drivers (Mac OS X 10.4.8)? - can you kernel panic outside your own kernel extension if you're doing bad things with memory (till now I've always KPed in my code)? This email sent to site_archiver@lists.apple.com