diff --git a/python/paddle/io/dataloader/dataloader_iter.py b/python/paddle/io/dataloader/dataloader_iter.py
index 0ffe7c46e77c94c33c177a9991d83960508b7de0..c15d3377eb649c3416bde373d262ce65edb61d27 100644
--- a/python/paddle/io/dataloader/dataloader_iter.py
+++ b/python/paddle/io/dataloader/dataloader_iter.py
@@ -427,7 +427,21 @@ class _DataLoaderIterMultiProcess(_DataLoaderIterBase):
         self._shutdown = False
 
     def _init_workers(self):
-        from paddle.incubate import multiprocessing
+        # NOTE(zhangxiaoci): When trained in XPU multi-node RDMA environment, an unexpected
+        # segmentfault will be raised in dataloader process, where the traceback goes all
+        # back to a runtime error that dataloader workers exit unexpectedly. Similar problems
+        # have been discussed that lead to a misbehavior of OpenCV working in multiprocessing
+        # environment. A possible solution is to change default 'fork' mode of multiprocessing
+        # start method to 'spawn'. See https://stackoverflow.com/questions/54013846 for details.
+        # NOTE(zhangxiaoci): Replace multiprocessing with multiprocess since in some training
+        # environments the former will raise 'AttributeError: Can't pickle local object xxx',
+        # which is a side effect of changing the default start method.
+        if paddle.is_compiled_with_xpu():
+            import multiprocess as multiprocessing
+
+            multiprocessing.set_start_method('spawn', force=True)
+        else:
+            from paddle.incubate import multiprocessing
 
         # multiprocess worker and indice queue list initial as empty
         self._workers = []