| Summary: | amdgpu/dpm: NULL pointer dereference | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | DRI | Reporter: | Adam Wolk <adam.wolk> | ||||||
| Component: | DRM/AMDgpu | Assignee: | Default DRI bug account <dri-devel> | ||||||
| Status: | RESOLVED MOVED | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | medium | CC: | adam.wolk, funfunctor | ||||||
| Version: | XOrg git | ||||||||
| Hardware: | x86-64 (AMD64) | ||||||||
| OS: | Linux (All) | ||||||||
| Whiteboard: | |||||||||
| i915 platform: | i915 features: | ||||||||
| Attachments: |
|
||||||||
|
Description
Adam Wolk
2017-03-04 12:45:06 UTC
I just tried on a newer kernel from Archlinux [testing]. [mulander@napalm ~]$ uname -a Linux napalm 4.10.1-1-ARCH #1 SMP PREEMPT Sun Feb 26 21:08:53 UTC 2017 x86_64 GNU/Linux Same problem. Here is a photo I managed to grab while trying to boot it up. https://imgur.com/PCC42Bj OK so we narrowed the problem down to dpm. (12:17:01 AM) mulander: yep, blacklisted radeon, amdgpu.dpm=0 and booted to X properly without a crash (In reply to Adam Wolk from comment #0) > I noticed my external display constantly turning on and off unless a DRI app > is active (ie. running DRI_PRIME=1 glxgears). Which GPU is the external display connected to? If you're not sure, attach the output of xrandr. Here is the xrandr output. [mulander@napalm ~]$ xrandr Screen 0: minimum 8 x 8, current 3286 x 1080, maximum 32767 x 32767 eDP1 connected 1366x768+1920+0 (normal left inverted right x axis y axis) 340mm x 190mm 1366x768 59.97*+ 1024x768 60.00 1024x576 60.00 960x540 60.00 800x600 60.32 56.25 864x486 60.00 640x480 59.94 720x405 60.00 680x384 60.00 640x360 60.00 DP1 connected 1920x1080+0+0 (normal left inverted right x axis y axis) 480mm x 270mm 1920x1080 60.00*+ 1680x1050 59.95 1280x1024 75.02 60.02 1152x864 75.00 1024x768 75.03 60.00 800x600 75.00 60.32 640x480 75.00 59.94 720x400 70.08 HDMI1 disconnected (normal left inverted right x axis y axis) HDMI2 disconnected (normal left inverted right x axis y axis) VIRTUAL1 disconnected (normal left inverted right x axis y axis) FWIW, since all display outputs are connected to the iGPU, it's unlikely that using amdgpu instead of radeon will have any effect on the external display turning on and off. You'd have to bring that up with the iGPU drivers. Regarding the display flicking on/off (the effect feels like changing resolution - the way it goes out and back). This is completely mitigated by running DRI_PRIME=1 glxgears hence why I thought it might be AMD driver related. Regardless, the main thing reported here is a null pointer dereference in the kernel and a system unable to boot completely. I can live with the flicker - I just workaround it by running DRI_PRIME=1 glxgears all day... (In reply to Adam Wolk from comment #7) > Regarding the display flicking on/off (the effect feels like changing > resolution - the way it goes out and back). This is completely mitigated by > running DRI_PRIME=1 glxgears hence why I thought it might be AMD driver > related. It can't really be directly related, since the display isn't connected to the AMD GPU. I'd report it against the i915 kernel driver. > Do the patches in bug 99387 help? This is a machine I use for work unfortunately I can't fiddle with it more. Regarding the flickering issue I reported it as a separate bug. https://bugs.freedesktop.org/show_bug.cgi?id=100386 (In reply to Adam Wolk from comment #10) > > Do the patches in bug 99387 help? > > This is a machine I use for work unfortunately I can't fiddle with it more. > > Regarding the flickering issue I reported it as a separate bug. > > https://bugs.freedesktop.org/show_bug.cgi?id=100386 [edward@skytop linux]$ git tag --contains c10c8f7 -l v4.10.0 v4.11-rc1 v4.11-rc2 v4.11-rc3 v4.11-rc4 v4.11-rc5 v4.11-rc6 v4.11-rc7 @Adam, can you please try updating to at minimum kernel v4.10.0 and seeing if that fixes the issue for you? @Alex Deucher I confirmed with Adam that, even with c10c8f7 he still has the null pointer issue. Created attachment 130967 [details] [review] dpm patch @Adam, please try applying the attached patch and let me know if it helps with your issue? -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/147. |
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.