Summary: | [IVB] Running module_reload after calling function drm_open_any() will cause GPU hang | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Du Yan <yanx.du> | ||||||||
Component: | DRM/Intel | Assignee: | Daniel Vetter <daniel> | ||||||||
Status: | CLOSED FIXED | QA Contact: | |||||||||
Severity: | normal | ||||||||||
Priority: | medium | CC: | ben, chris, daniel, jbarnes | ||||||||
Version: | unspecified | ||||||||||
Hardware: | Other | ||||||||||
OS: | All | ||||||||||
Whiteboard: | |||||||||||
i915 platform: | i915 features: | ||||||||||
Attachments: |
|
Description
Du Yan
2012-07-02 18:34:45 UTC
Being lazy and not having reproduced this... Is this still an issue? Issue still can reproduce. Both dmesg log and error states are attached. Kernel: (drm-intel-fixes)c4aed353b1b079eb4843e6a708fc68b4b28f72aa Some additional commit info: Merge: 6bc5154 e15ebe0 Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Thu Jul 5 13:20:02 2012 -0700 Created attachment 64252 [details]
dmesg file
Created attachment 64253 [details]
errorstate
Oops, we've lost a bit track of this one. Is this still an issue with latest -fixes/-queued? Kernel: (drm-intel-fixes)a51d4ed01e5bb39d2cf36a12f9976ab08872c192 Some additional commit info: Author: Calvin Walton <calvin.walton@kepstin.ca> Date: Fri Aug 24 07:56:31 2012 -0400 i915: Quirk no_lvds on Gigabyte GA-D525TUD ITX motherboard This issue not appear in this version. So can we close this, or does it still happen somewhere? I somewhat suspect it's a timing thing, does few seconds of sleep between drm_open_any and the module reload "fix" the issue? Kernel: (drm-intel-testing)c3c3d4e9c2daeca01c42040cda0e5e0579c5c80b Now this issue can't reproduced. so I think it's possible to close this bug. Ok, two kernels with quite a few things changed in between worked, I guess we can close this one. Please reopen if you see this issue again, thanks. |
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.