Bug 91708

Summary: Tonga boots to terminal with drm-next-4.3, va conflict
Product: DRI Reporter: Mathias Tillman <master.homer>
Component: DRM/AMDgpuAssignee: Default DRI bug account <dri-devel>
Status: RESOLVED DUPLICATE QA Contact:
Severity: normal    
Priority: medium CC: master.homer
Version: XOrg git   
Hardware: Other   
OS: All   
Whiteboard:
i915 platform: i915 features:
Attachments:
Description Flags
Kernel log when failing to boot normally none

Description Mathias Tillman 2015-08-20 20:41:14 UTC
Created attachment 117829 [details]
Kernel log when failing to boot normally

I've been having problems booting when using a self-compiled kernel of the drm-next-4.3 branch from the agd5f repo. The amdgpu kernel driver complains that some va (virtual address?) conflicts with another, which makes it boot to a terminal.
You can see the conflict in the kernel log:
Aug 20 22:29:14 homer-desktop kernel: [    6.762949] amdgpu 0000:01:00.0: bo ffff880620b34800 va 0x0000100000-0x0000100400 conflict with 0x0000100000-0x0000100400
Aug 20 22:29:14 homer-desktop kernel: [    6.763693] amdgpu 0000:01:00.0: bo ffff880620b34800 va 0x0000100000-0x0000100400 conflict with 0x0000100000-0x0000100400
Aug 20 22:29:14 homer-desktop kernel: [    6.764357] amdgpu 0000:01:00.0: bo ffff880620b34800 va 0x0000100000-0x0000100400 conflict with 0x0000100000-0x0000100400
Aug 20 22:29:14 homer-desktop kernel: [    6.765032] amdgpu 0000:01:00.0: bo ffff880620b34800 va 0x0000100000-0x0000100400 conflict with 0x0000100000-0x0000100400

I do not have these problems when using a self-compiled kernel from the drm-next-4.2 or drm-fixes-4.2 branch, so something must have changed from 4.2 to 4.3 that causes the conflict.

Using a Radeon R9 285 (TONGA) on Kubuntu vivid with mesa 11 from the oibaf ppa and a self-compiled xf86-video-amdgpu.
Comment 1 Alex Deucher 2015-08-20 20:50:07 UTC

*** This bug has been marked as a duplicate of bug 91704 ***

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.