Thread-topic: Kernel panic on Intel based Mac with more than 2GB of memory
We have a universal binary driver for a SATA HBA that seems to work fine
unless its running on an Intel Mac with more than 2GB of memory
installed. If there is more than 2GB of memory the system eventually
will panic with the following message in the panic log:
panic(cpu 3 caller 0x003A1D25): getPhysicalSegment() out of 32b range
0x100000000, len 0x8000, class IOGeneralMemoryDescriptor
>From the backtrace I can see that at the time of the panic the driver is
in the process of building a scatter/gather table in preperation for a
DMA transfer.
What I don't get is how our driver can be causing this problem since
getPhysicalSegment takes an offset instead of an address as an argument.
It seems to me that for our driver to be causing this problem it would
have to be passing a completely invalid offset argument, which I doubt
it is doing since the driver seems to work fine if the system has 2GB or
less of memory.
Anybody out there able to shed some light on what's going on here?
Thanks,
Dave Canfield
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-drivers mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-drivers/email@hidden
This email sent to email@hidden
