I've got a USB network driver that is working well, for the most part. Running OS X 10.1.5. When resuming from a system sleep, if I generate a lot of disk activity immediately after wakeup (by starting IE for example), our driver crashes. So far, we've been able to debug everything with IOLog, not having to figure out kernel debugging and symbols. However, this one is elusive, so its time to do kernel debugging. I've got the source for my kernel and I'm successfully building and running a version of the kernel that I've built. The bug exhibits itself exactly the same with my kernel as with the stock kernel from my machine. I also can successfully connect gdb remotely once the trap has occurred. I've got the symbols / source for my driver loaded into gdb. I can see exactly what line in the driver is crashing - I just don't know why. I don't know how to understand what the kernel is telling me - ie: what the real problem is. Here's the trap info - can someone enlighten me on the 0x300 Data access trap? Thanks, -Chris --------------------- Unresolved kernel trap(cpu 0): 0x300 - Data access DAR=0x00000108 PC=0x21a70584 Latest crash info for cpu 0: Exception state (sv=0x1d146800) PC=0x21A70584; MSR=0x00009030; DAR=0x00000108; DSISR=0x40000000; LR=0x21a704b4; R1=0x0d8db5b0; XCP=0x0000000c (0x300 - Data access) _______________________________________________ darwin-kernel mailing list | darwin-kernel@lists.apple.com Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/darwin-kernel Do not post admin requests to the list. They will be ignored.