site_archiver@lists.apple.com Delivered-To: darwin-kernel@lists.apple.com Hi, 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/site_archiver%40lists.a... I'm not working in the kernel, but I just experienced some behavior that I hope that someone can explain for me, because I'm totally at a loss. The scenario is that I have an application which talks to a serial device using POSIX serial commands. The device connection is USB and the vendor of the USB chip has provided a kernel driver which lets us use the POSIX interfaces. Earlier today, I ran the application a few times. I have logs that show connections to the device. This evening when I ran the app, it reported there was no device. I checked kextstat and the driver was no longer loaded. I checked /System/Library/Extensions and the kext was no longer even there. (I didn't delete it or unload the kext). I haven't restarted my machine in three days. I check the system log and see this: ... Sep 20 16:06:36 Gemini kernel: jnl: close: flushing the buffer cache (start 0x73e000 end 0x742400) Sep 20 16:07:58 Gemini kernel: UniNEnet::monitorLinkStatus - Link is up at 100 Mbps - Full Duplex Sep 20 16:47:22 Gemini kextd[4363]: error mapping module file /System/Library/Extensions/WalkAndTalkSerial.kext/Contents/MacOS/ FTDIUSBSerialDriver Sep 20 16:47:22 Gemini kextd[4363]: can't map module files Sep 20 16:47:22 Gemini kextd[4363]: can't check load addresses of modules Sep 20 16:47:22 Gemini kextd[4363]: a link/load error occured for kernel extension /System/Library/Extensions/WalkAndTalkSerial.kext Sep 20 16:48:54 Gemini kernel: jnl: journal start/end pointers reset! (jnl 0x2696c88; s 0x742400 e 0x742400) Sep 20 16:48:54 Gemini diskarbitrationd[136]: disk1s6 hfs 0409E0E9-6206-3610-AB17-9287A2E688C5 Extra /Volumes/Extra So, it looks like at 16:47:22 something happened to cause a kextd error. Based on the messages, it looks like the kext got deleted and kextd got an error. 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