[Bug 94123] [APL] [IGT Basic] drv_module_reload_basic never ends
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Thu Apr 7 18:22:03 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=94123
--- Comment #7 from Imre Deak <imre.deak at intel.com> ---
(In reply to Jairo Miramontes from comment #6)
> So looks like it's no longer taking forever, it ends now, find below the
> Output I get when executing the ./drv_module_reload_basic test:
>
> Reloading i915.ko with
> unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device
> module successfully unloaded
> module successfully loaded again
> Reloading i915.ko with inject_load_failure=1
> unbinding /sys/class/vtconsole/vtcon1/: (M) frame buffer device
> module successfully unloaded
> Reloading i915.ko with inject_load_failure=2
> module successfully unloaded
> Reloading i915.ko with inject_load_failure=3
> module successfully unloaded
> Reloading i915.ko with inject_load_failure=4
> module successfully unloaded
> Reloading i915.ko with
> module successfully unloaded
> module successfully loaded again
>
>
> Used the following kernel:
>
> commit aedfaaef290af9c8df7d9f4adf22cbe21704d091
> Author: Tvrtko Ursulin <tvrtko.ursulin at intel.com>
> Date: Mon Apr 4 14:10:49 2016 +0100
>
> drm-intel-nightly: 2016y-04m-04d-13h-09m-54s UTC integration manifest
>
>
> However I am not sure why it doesn't show a test status after it's
> completed... (success, fail) anything.
The above output indicates success but you should also check dmesg for any
errors/WARNs. The script itself won't provide the standard success/fail test
status message, you'll only get that when executing the test as part of a
piglit run. piglit will in turn check the exit status of the script and check
for errors/WARNs in dmesg as usual.
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160407/3835f86c/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list