Bug 54996 - [SNB ILK]I-G-T/module_reload fail
Summary: [SNB ILK]I-G-T/module_reload fail
Status: CLOSED DUPLICATE of bug 54111
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Daniel Vetter
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-09-17 04:24 UTC by shui yangwei
Modified: 2017-10-06 14:48 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:


Attachments
module_reload fail dmesg (56.93 KB, text/plain)
2012-09-17 05:37 UTC, shui yangwei
no flags Details

Description shui yangwei 2012-09-17 04:24:02 UTC
System Environment:
--------------------------
Platform:        ILK SNB

The Linux Kernel, the operating system core itself
Kernel: (drm-intel-fixes)3d840a13a2f9605073b1c52fe4530df9a2fe7795
Some additional commit info:
Author: Daniel Vetter <daniel.vetter@ffwll.ch>
Date:   Tue Sep 11 12:37:55 2012 +0200


Bug detail description:
--------------------------
When only run module_reload, it's success.
May be  after run prime_self_import changed someting caused daily overnight test module_reload fail.
First run prime_self_import, then module_reload,caused error below(the last line):

[root@x-g45b tests]# ./prime_self_import
[root@x-g45b tests]# ./module_reload
module successfully unloaded
module successfully loaded again
[root@x-g45b tests]# dmesg | grep -i "error"
[ 26.360020] rmmod[2419]: ERROR: Module scsi_wait_scan does not exist in /proc/modules
[ 26.383830] rmmod[2425]: ERROR: Module scsi_wait_scan does not exist in /proc/modules
[ 183.216963] [drm:drm_mm_takedown] *ERROR* Memory manager not clean. Delaying takedown
Comment 1 shui yangwei 2012-09-17 05:37:23 UTC
Created attachment 67267 [details]
module_reload fail dmesg
Comment 2 Daniel Vetter 2012-09-17 06:23:21 UTC

*** This bug has been marked as a duplicate of bug 54111 ***
Comment 3 Elizabeth 2017-10-06 14:48:21 UTC
Closing old verified.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.