This answer record applies to the MIG 7 series DDR3/DDR2 design with the AXI interface enabled. When a long write or read burst is requested on the AXI interface and AXI is currently servicing a read request, there is chance for AXI to service the write request before read request is completed. After all write requests are served, AXI will send out the remaining read requests.
This is an AXI arbiter problem. The logic should not switch to write before read is completed. This generally does not impact the functionality, but for the design that requires strict write and read order, this may cause a functional problem. The workaround now is not to assert write and read at the same time. After the read is completed, the write should be then requested on AXI. There is no starvation timeout or wait timeout. This issue is planed to be fixed in 2013.