@@ -66,6 +66,19 @@ bool __i915_inject_load_failure(const char *func, int line)
return false;
}
+#define BUGS_FDO_URL "https://bugs.freedesktop.org/enter_bug.cgi?product=DRI"
+#define i915_load_error(fmt, ...) do { \
+ if (i915.inject_load_failure && \
+ i915_load_fail_count == i915.inject_load_failure) { \
+ DRM_DEBUG_DRIVER(fmt, ##__VA_ARGS__); \
+ } else { \
+ DRM_ERROR(fmt, ##__VA_ARGS__); \
+ DRM_INFO("Please file a bug at " BUGS_FDO_URL " " \
+ "against DRM/Intel providing the dmesg log " \
+ "by booting with drm.debug=0xf\n"); \
+ } \
+} while(0)
+
static int i915_getparam(struct drm_device *dev, void *data,
struct drm_file *file_priv)
{
@@ -1332,10 +1345,8 @@ int i915_driver_load(struct drm_device *dev, unsigned long flags)
}
ret = i915_load_modeset_init(dev);
- if (ret < 0) {
- DRM_ERROR("failed to init modeset\n");
+ if (ret < 0)
goto out_cleanup_vblank;
- }
i915_driver_register(dev_priv);
@@ -1357,6 +1368,8 @@ out_runtime_pm_put:
out_free_priv:
kfree(dev_priv);
+ i915_load_error("Device initialization failed (%d)\n", ret);
+
return ret;
}
Atm, in case failure injection forces an error the subsequent "*ERROR* failed to init modeset" error message will make automated tests (CI) report this event as a breakage even though the event is expected. To fix this print the error message with debug log level in this case. While at it print the error message for any init failure and change it to "*ERROR* Device initialization failed (errno)" for consistency. v2: - Include the problematic error message in the commit log, add a request to file an fdo bug to the message (Chris) v3: - Include the new error message too in the commit log, make the fdo link more precise and print part of the message with info log level (Chris) CC: Chris Wilson <chris@chris-wilson.co.uk> Signed-off-by: Imre Deak <imre.deak@intel.com> --- drivers/gpu/drm/i915/i915_dma.c | 19 ++++++++++++++++--- 1 file changed, 16 insertions(+), 3 deletions(-)