site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com G'day Brent, Godfrey On Sep 20, , at 21:28, Brent Marykuca wrote: Questions: Many thanks if you can shed any light on what's just happened here. Cheers, Brent Marykuca _______________________________________________ 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/gvdl%40apple.com This email sent to gvdl@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... If a device is 'unplugged' (see later) then it is probably that your driver (kext) will be unloaded. This will automatically happen after at least 1 minute with no instances extant in the kext. I'd say that something like this happened, perhaps the system slept the bus or something. To answer question one is a bit more difficult. If you unplug and plug your device again does the driver turn up again (tty.???). If not it looks like something is happening to your kext or perhaps to the kernel state itself. 1. I thought kexts were kept in wired memory and remained loaded even if you deleted the executable. Am I wrong about this? I think my experience with previous versions of Mac OS gave me this impression. Why would kextd be running on my driver if it had been loaded for three days? 2. Where did my kext go? I certainly didn't touch it. Do the messages from the journal have any significance? This email sent to site_archiver@lists.apple.com