From mboxrd@z Thu Jan 1 00:00:00 1970 From: bugzilla-daemon@freedesktop.org Subject: [Bug 104274] Unable to cleanly unload kernel module: BUG: unable to handle kernel NULL pointer dereference at 0000000000000258 (mutex_lock) Date: Thu, 22 Feb 2018 19:28:20 +0000 Message-ID: References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0506665955==" Return-path: Received: from culpepper.freedesktop.org (culpepper.freedesktop.org [131.252.210.165]) by gabe.freedesktop.org (Postfix) with ESMTP id F1C756EB8E for ; Thu, 22 Feb 2018 19:28:19 +0000 (UTC) In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dri-devel-bounces@lists.freedesktop.org Sender: "dri-devel" To: dri-devel@lists.freedesktop.org List-Id: dri-devel@lists.freedesktop.org --===============0506665955== Content-Type: multipart/alternative; boundary="15193276992.feda18.11302" Content-Transfer-Encoding: 7bit --15193276992.feda18.11302 Date: Thu, 22 Feb 2018 19:28:19 +0000 MIME-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated https://bugs.freedesktop.org/show_bug.cgi?id=3D104274 --- Comment #6 from Luke McKee --- Harry I have tried the latest staging next 2 days ago. Suggest you see there is a long standing issue with powerplay and buggy AMI bioses that don't properly set up MMIO BAR regiions that need to be worked around by your driver becuase the vendor says a 2 year old motherboard is t= oo old to support firmware updates, even if Intel ME is a massive security ris= k in support emails. I'm actually thinking you guys need to add linuxbios/corebo= ot support for your driver if available the way things are going: https://forum-en.msi.com/index.php?topic=3D298468.0 I think Polaris 11 with buggy bioses that dont' properly setup PCIE MMIO BAR ranges have hell with the amdgpu driver and powerplay (no fan control) cook= ed cards etc. With your new powerplay code it gets even worse maybe and just doesn't boot in this condition. I work OK on 4.14.20 but with exactly the s= ame config and amdgpu-staging-next from last updated 4 days ago I get this mess= .=20 Feb 23 01:41:59 hojuruku kernel: [drm] amdgpu kernel modesetting enabled. Feb 23 01:41:59 hojuruku kernel: checking generic (e0000000 300000) vs hw (e0000000 10000000) Feb 23 01:41:59 hojuruku kernel: fb: switching to amdgpudrmfb from EFI VGA Feb 23 01:41:59 hojuruku kernel: Console: switching to colour dummy device 80x25 Feb 23 01:41:59 hojuruku kernel: amdgpu 0000:01:00.0: enabling device (0006= -> 0007) Feb 23 01:41:59 hojuruku kernel: [drm] initializing kernel modesetting (POLARIS11 0x1002:0x67FF 0x1462:0x8A91 0xCF). Feb 23 01:41:59 hojuruku kernel: [drm] register mmio base: 0xF7E00000 Feb 23 01:41:59 hojuruku kernel: [drm] register mmio size: 262144 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 0 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 1 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 2 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 3 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 4 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 5 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 6 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 7 Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 8 Feb 23 01:41:59 hojuruku kernel: [drm] probing gen 2 caps for device 8086:c= 01 =3D 261ad03/e Feb 23 01:41:59 hojuruku kernel: [drm] probing mlw for device 8086:c01 =3D 261ad03 Feb 23 01:41:59 hojuruku kernel: [drm] UVD is enabled in VM mode Feb 23 01:41:59 hojuruku kernel: [drm] UVD ENC is enabled in VM mode Feb 23 01:41:59 hojuruku kernel: [drm] VCE enabled in VM mode Feb 23 01:41:59 hojuruku kernel: ATOM BIOS: 113-C98121-M01 Feb 23 01:41:59 hojuruku kernel: [drm] vm size is 64 GB, 2 levels, block si= ze is 10-bit, fragment size is 9-bit Feb 23 01:41:59 hojuruku kernel: amdgpu 0000:01:00.0: VRAM: 4096M 0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used) Feb 23 01:41:59 hojuruku kernel: amdgpu 0000:01:00.0: GTT: 256M 0x0000000000000000 - 0x000000000FFFFFFF Feb 23 01:41:59 hojuruku kernel: [drm] Detected VRAM RAM=3D4096M, BAR=3D256M Feb 23 01:41:59 hojuruku kernel: [drm] RAM width 128bits GDDR5 Feb 23 01:41:59 hojuruku kernel: [TTM] Zone kernel: Available graphics mem= ory: 8174838 kiB Feb 23 01:41:59 hojuruku kernel: [TTM] Zone dma32: Available graphics mem= ory: 2097152 kiB Feb 23 01:41:59 hojuruku kernel: [TTM] Initializing pool allocator Feb 23 01:41:59 hojuruku kernel: [TTM] Initializing DMA pool allocator Feb 23 01:41:59 hojuruku kernel: [drm] amdgpu: 4096M of VRAM memory ready Feb 23 01:41:59 hojuruku kernel: [drm] amdgpu: 4096M of GTT memory ready. Feb 23 01:41:59 hojuruku kernel: [drm] GART: num cpu pages 65536, num gpu p= ages 65536 Feb 23 01:41:59 hojuruku kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400040000). Feb 23 01:41:59 hojuruku kernel: [drm] Supports vblank timestamp caching Re= v 2 (21.10.2013). Feb 23 01:41:59 hojuruku kernel: [drm] Driver supports precise vblank times= tamp query. Feb 23 01:41:59 hojuruku kernel: [drm] AMDGPU Display Connectors Feb 23 01:41:59 hojuruku kernel: [drm] Connector 0: Feb 23 01:41:59 hojuruku kernel: [drm] DP-1 Feb 23 01:41:59 hojuruku kernel: [drm] HPD2 Feb 23 01:41:59 hojuruku kernel: [drm] DDC: 0x4868 0x4868 0x4869 0x4869 0x486a 0x486a 0x486b 0x486b Feb 23 01:41:59 hojuruku kernel: [drm] Encoders: Feb 23 01:41:59 hojuruku kernel: [drm] DFP1: INTERNAL_UNIPHY1 Feb 23 01:41:59 hojuruku kernel: [drm] Connector 1: Feb 23 01:41:59 hojuruku kernel: [drm] HDMI-A-1 Feb 23 01:41:59 hojuruku kernel: [drm] HPD5 Feb 23 01:41:59 hojuruku kernel: [drm] DDC: 0x4874 0x4874 0x4875 0x4875 0x4876 0x4876 0x4877 0x4877 Feb 23 01:41:59 hojuruku kernel: [drm] Encoders: Feb 23 01:41:59 hojuruku kernel: [drm] DFP2: INTERNAL_UNIPHY1 Feb 23 01:41:59 hojuruku kernel: [drm] Connector 2: Feb 23 01:41:59 hojuruku kernel: [drm] DVI-D-1 Feb 23 01:41:59 hojuruku kernel: [drm] HPD3 Feb 23 01:41:59 hojuruku kernel: [drm] DDC: 0x4878 0x4878 0x4879 0x4879 0x487a 0x487a 0x487b 0x487b Feb 23 01:41:59 hojuruku kernel: [drm] Encoders: Feb 23 01:41:59 hojuruku kernel: [drm] DFP3: INTERNAL_UNIPHY Feb 23 01:41:59 hojuruku kernel: [drm] Chained IB support enabled! This is the issues I've had with it: Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (II) AMDGPU(0): Number of EDID sections to follow: 1 Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (II) AMDGPU(0): E= DID (in hex): Feb 23 01:42:00 hojuruku kernel: WARNING: CPU: 3 PID: 816 at drivers/gpu/drm/amd/amdgpu/amdgpu_sa.c:326 amdgpu_sa_bo_new+0x463/0x480 [amdgpu] Feb 23 01:42:00 hojuruku kernel: Modules linked in: snd_hda_codec_realtek snd_hda_codec_generic cmdlinepart amdgpu(+) chash i2c_algo_bit gpu_sched snd_hda_intel(+) snd_hda_codec ttm drm_kms_helper snd_hwdep intel_spi_platf= orm intel_spi drm spi_nor snd_hda_core ehci_pci mtd agpgart snd_pcm syscopyarea sysfillrect ehci_hcd snd_timer sysimgblt fb_sys_fops snd soundcore xhci_pci xhci_hcd Feb 23 01:42:00 hojuruku kernel: CPU: 3 PID: 816 Comm: X Tainted: G = W=20=20=20 4.15.0-rc4-haswell+ #1 Feb 23 01:42:00 hojuruku kernel: Hardware name: MSI MS-7850/B85-G41 PC Mate(MS-7850), BIOS V2.10B3 02/18/2016 Feb 23 01:42:00 hojuruku kernel: RIP: 0010:amdgpu_sa_bo_new+0x463/0x480 [amdgpu] Feb 23 01:42:00 hojuruku kernel: RSP: 0018:ffffc900025938d0 EFLAGS: 00010287 Feb 23 01:42:00 hojuruku kernel: RAX: ffff8803fd82ac00 RBX: ffff880406520000 RCX: 0000000000000100 Feb 23 01:42:00 hojuruku kernel: RDX: 0000000000000040 RSI: ffff8803fd82ae60 RDI: ffff880406523480 Feb 23 01:42:00 hojuruku kernel: RBP: ffff8803fd82ae60 R08: ffff88041dd9c600 R09: ffff8803fd82ac00 Feb 23 01:42:00 hojuruku kernel: R10: ffffc90002593aa8 R11: ffff880404c98090 R12: 0000000000000000 Feb 23 01:42:00 hojuruku kernel: R13: 0000000000000000 R14: 0000000000000400 R15: ffff880404c98000 Feb 23 01:42:00 hojuruku kernel: FS: 00007f491dd2f300(0000) GS:ffff88041dd80000(0000) knlGS:0000000000000000 Feb 23 01:42:00 hojuruku kernel: CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033 Feb 23 01:42:00 hojuruku kernel: CR2: 000055b6b5d201b8 CR3: 0000000404352006 CR4: 00000000001606e0 Feb 23 01:42:00 hojuruku kernel: Call Trace: Feb 23 01:42:00 hojuruku kernel: ? ttm_bo_handle_move_mem+0x28c/0x5b0 [ttm] Feb 23 01:42:00 hojuruku kernel: ? ___slab_alloc+0x416/0x5b0 Feb 23 01:42:00 hojuruku kernel: ? amdgpu_vram_mgr_new+0x1d9/0x2a0 [amdgpu] Feb 23 01:42:00 hojuruku kernel: ? ttm_bo_validate+0x104/0x110 [ttm] Feb 23 01:42:00 hojuruku kernel: ? security_capable+0x4f/0x70 Feb 23 01:42:00 hojuruku kernel: ? amdgpu_job_alloc+0x45/0xc0 [amdgpu] Feb 23 01:42:00 hojuruku kernel: ? ttm_bo_init_reserved+0x2d4/0x450 [ttm] Feb 23 01:42:00 hojuruku kernel: ? amdgpu_job_alloc+0x45/0xc0 [amdgpu] Feb 23 01:42:00 hojuruku kernel: ? __slab_alloc+0x2a/0x40 Feb 23 01:42:00 hojuruku kernel: amdgpu_ib_get+0x3b/0xa0 [amdgpu] Feb 23 01:42:00 hojuruku kernel: amdgpu_job_alloc_with_ib+0x50/0x90 [amdgp= u] Feb 23 01:42:00 hojuruku kernel: amdgpu_vm_clear_bo+0xe4/0x2b0 [amdgpu] Feb 23 01:42:00 hojuruku kernel: amdgpu_vm_alloc_levels+0x1f6/0x350 [amdgp= u] Feb 23 01:42:00 hojuruku kernel: amdgpu_vm_alloc_pts+0x5b/0x90 [amdgpu] Feb 23 01:42:00 hojuruku kernel: amdgpu_gem_va_ioctl+0x27c/0x510 [amdgpu] Feb 23 01:42:00 hojuruku kernel: ? amdgpu_gem_create_ioctl+0x180/0x250 [amdgpu] Feb 23 01:42:00 hojuruku kernel: ? amdgpu_gem_metadata_ioctl+0x1b0/0x1b0 [amdgpu] Feb 23 01:42:00 hojuruku kernel: ? drm_ioctl_kernel+0x63/0xb0 [drm] Feb 23 01:42:00 hojuruku kernel: drm_ioctl_kernel+0x63/0xb0 [drm] Feb 23 01:42:00 hojuruku kernel: drm_ioctl+0x2dc/0x380 [drm] Feb 23 01:42:00 hojuruku kernel: ? amdgpu_gem_metadata_ioctl+0x1b0/0x1b0 [amdgpu] Feb 23 01:42:00 hojuruku kernel: ? __handle_mm_fault+0x875/0xf50 Feb 23 01:42:00 hojuruku kernel: amdgpu_drm_ioctl+0x57/0x90 [amdgpu] Feb 23 01:42:00 hojuruku kernel: do_vfs_ioctl+0x97/0x5e0 Feb 23 01:42:00 hojuruku kernel: ? handle_mm_fault+0xd2/0x1a0 Feb 23 01:42:00 hojuruku kernel: ? __do_page_fault+0x223/0x3f0 Feb 23 01:42:00 hojuruku kernel: SyS_ioctl+0x7e/0x90 Feb 23 01:42:00 hojuruku kernel: entry_SYSCALL_64_fastpath+0x1a/0x7d Feb 23 01:42:00 hojuruku kernel: RIP: 0033:0x7f491efaa6f7 Feb 23 01:42:00 hojuruku kernel: RSP: 002b:00007fff8e587648 EFLAGS: 00000246 ORIG_RAX: 0000000000000010 Feb 23 01:42:00 hojuruku kernel: RAX: ffffffffffffffda RBX: 000055b6b5d1fcb0 RCX: 00007f491efaa6f7 Feb 23 01:42:00 hojuruku kernel: RDX: 00007fff8e5876b0 RSI: 00000000c0286448 RDI: 000000000000000e Feb 23 01:42:00 hojuruku kernel: RBP: 00007f491f2701f8 R08: 0000000100200000 R09: 000000000000000e Feb 23 01:42:00 hojuruku kernel: R10: 000000000000000c R11: 0000000000000246 R12: 00007f491f26fad8 Feb 23 01:42:00 hojuruku kernel: R13: 00000000000004f0 R14: 00007f491f26fa80 R15: 00000000000052e0 Feb 23 01:42:00 hojuruku kernel: Code: 00 00 00 e9 21 ff ff ff 8b 54 24 1c = 8b 74 24 18 48 8b 3c 24 e8 0f f7 ff ff 84 c0 74 9a eb c2 0f ff bb ea ff ff ff = e9 fc fc ff ff <0f> ff bb ea ff ff ff e9 f0 fc ff ff bb f4 ff ff ff e9 e6 fc f= f=20 Feb 23 01:42:00 hojuruku kernel: ---[ end trace de335683cd4d1a49 ]--- Feb 23 01:42:00 hojuruku kernel: amdgpu 0000:01:00.0: failed to get a new IB (-22) Feb 23 01:42:00 hojuruku kernel: amdgpu 0000:01:00.0: failed to get a new IB (-22) Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: Failed to allocate front buffer memory Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) AMDGPU(0): amdgpu_setup_kernel_mem failed Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: Fatal server erro= r: Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) AddScreen/ScreenInit failed for driver 0 Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: Please consult the The X.Org Foundation support Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: at http://wiki.x.org Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: for help. Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) Server terminated with error (1). Closing log file. Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: Unable to run X server then a systemd loop with Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (II) UnloadModul= e: "modesetting" Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) Device(s) detected, but none match those in the config file. Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: Fatal server err= or: Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) no screens found(EE) Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: Please consult t= he The X.Org Foundation support Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: at http://wiki.x.org Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: for help. Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) Please also check the log file at "/var/log/Xorg.0.log" for additional information. Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) Feb 23 01:42:07 hojuruku kernel: amdgpu 0000:01:00.0: failed to get a new IB (-22) Feb 23 01:42:07 hojuruku kernel: amdgpu 0000:01:00.0: failed to get a new IB (-22) --=20 You are receiving this mail because: You are the assignee for the bug.= --15193276992.feda18.11302 Date: Thu, 22 Feb 2018 19:28:19 +0000 MIME-Version: 1.0 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.freedesktop.org/ Auto-Submitted: auto-generated

Commen= t # 6 on bug 10427= 4 from Luke McKee 
Harry I have tried the latest staging next 2 days ago.

Suggest you see there is a long standing issue with powerplay and buggy AMI
bioses that don't properly set up MMIO BAR regiions that need to be worked
around by your driver becuase the vendor says a 2 year old motherboard is t=
oo
old to support firmware updates, even if Intel ME is a massive security ris=
k in
support emails. I'm actually thinking you guys need to add linuxbios/corebo=
ot
support for your driver if available the way things are going:

https://for=
um-en.msi.com/index.php?topic=3D298468.0

I think Polaris 11 with buggy bioses that dont' properly setup PCIE MMIO BAR
ranges have hell with the amdgpu driver and powerplay (no fan control) cook=
ed
cards etc. With your new powerplay code it gets even worse maybe and just
doesn't boot in this condition. I work OK on 4.14.20 but with exactly the s=
ame
config and amdgpu-staging-next from last updated 4 days ago I get this mess=
.=20

Feb 23 01:41:59 hojuruku kernel: [drm] amdgpu kernel modesetting enabled.
Feb 23 01:41:59 hojuruku kernel: checking generic (e0000000 300000) vs hw
(e0000000 10000000)
Feb 23 01:41:59 hojuruku kernel: fb: switching to amdgpudrmfb from EFI VGA
Feb 23 01:41:59 hojuruku kernel: Console: switching to colour dummy device
80x25
Feb 23 01:41:59 hojuruku kernel: amdgpu 0000:01:00.0: enabling device (0006=
 ->
0007)
Feb 23 01:41:59 hojuruku kernel: [drm] initializing kernel modesetting
(POLARIS11 0x1002:0x67FF 0x1462:0x8A91 0xCF).
Feb 23 01:41:59 hojuruku kernel: [drm] register mmio base: 0xF7E00000
Feb 23 01:41:59 hojuruku kernel: [drm] register mmio size: 262144
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 0 <vi_common&=
gt;
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 1 <gmc_v8_0&g=
t;
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 2 <tonga_ih&g=
t;
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 3 <amdgpu_pow=
erplay>
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 4 <dce_v11_0&=
gt;
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 5 <gfx_v8_0&g=
t;
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 6 <sdma_v3_0&=
gt;
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 7 <uvd_v6_0&g=
t;
Feb 23 01:41:59 hojuruku kernel: [drm] add ip block number 8 <vce_v3_0&g=
t;
Feb 23 01:41:59 hojuruku kernel: [drm] probing gen 2 caps for device 8086:c=
01 =3D
261ad03/e
Feb 23 01:41:59 hojuruku kernel: [drm] probing mlw for device 8086:c01 =3D
261ad03
Feb 23 01:41:59 hojuruku kernel: [drm] UVD is enabled in VM mode
Feb 23 01:41:59 hojuruku kernel: [drm] UVD ENC is enabled in VM mode
Feb 23 01:41:59 hojuruku kernel: [drm] VCE enabled in VM mode
Feb 23 01:41:59 hojuruku kernel: ATOM BIOS: 113-C98121-M01
Feb 23 01:41:59 hojuruku kernel: [drm] vm size is 64 GB, 2 levels, block si=
ze
is 10-bit, fragment size is 9-bit
Feb 23 01:41:59 hojuruku kernel: amdgpu 0000:01:00.0: VRAM: 4096M
0x000000F400000000 - 0x000000F4FFFFFFFF (4096M used)
Feb 23 01:41:59 hojuruku kernel: amdgpu 0000:01:00.0: GTT: 256M
0x0000000000000000 - 0x000000000FFFFFFF
Feb 23 01:41:59 hojuruku kernel: [drm] Detected VRAM RAM=3D4096M, BAR=3D256M
Feb 23 01:41:59 hojuruku kernel: [drm] RAM width 128bits GDDR5
Feb 23 01:41:59 hojuruku kernel: [TTM] Zone  kernel: Available graphics mem=
ory:
8174838 kiB
Feb 23 01:41:59 hojuruku kernel: [TTM] Zone   dma32: Available graphics mem=
ory:
2097152 kiB
Feb 23 01:41:59 hojuruku kernel: [TTM] Initializing pool allocator
Feb 23 01:41:59 hojuruku kernel: [TTM] Initializing DMA pool allocator
Feb 23 01:41:59 hojuruku kernel: [drm] amdgpu: 4096M of VRAM memory ready
Feb 23 01:41:59 hojuruku kernel: [drm] amdgpu: 4096M of GTT memory ready.
Feb 23 01:41:59 hojuruku kernel: [drm] GART: num cpu pages 65536, num gpu p=
ages
65536
Feb 23 01:41:59 hojuruku kernel: [drm] PCIE GART of 256M enabled (table at
0x000000F400040000).
Feb 23 01:41:59 hojuruku kernel: [drm] Supports vblank timestamp caching Re=
v 2
(21.10.2013).
Feb 23 01:41:59 hojuruku kernel: [drm] Driver supports precise vblank times=
tamp
query.
Feb 23 01:41:59 hojuruku kernel: [drm] AMDGPU Display Connectors
Feb 23 01:41:59 hojuruku kernel: [drm] Connector 0:
Feb 23 01:41:59 hojuruku kernel: [drm]   DP-1
Feb 23 01:41:59 hojuruku kernel: [drm]   HPD2
Feb 23 01:41:59 hojuruku kernel: [drm]   DDC: 0x4868 0x4868 0x4869 0x4869
0x486a 0x486a 0x486b 0x486b
Feb 23 01:41:59 hojuruku kernel: [drm]   Encoders:
Feb 23 01:41:59 hojuruku kernel: [drm]     DFP1: INTERNAL_UNIPHY1
Feb 23 01:41:59 hojuruku kernel: [drm] Connector 1:
Feb 23 01:41:59 hojuruku kernel: [drm]   HDMI-A-1
Feb 23 01:41:59 hojuruku kernel: [drm]   HPD5
Feb 23 01:41:59 hojuruku kernel: [drm]   DDC: 0x4874 0x4874 0x4875 0x4875
0x4876 0x4876 0x4877 0x4877
Feb 23 01:41:59 hojuruku kernel: [drm]   Encoders:
Feb 23 01:41:59 hojuruku kernel: [drm]     DFP2: INTERNAL_UNIPHY1
Feb 23 01:41:59 hojuruku kernel: [drm] Connector 2:
Feb 23 01:41:59 hojuruku kernel: [drm]   DVI-D-1
Feb 23 01:41:59 hojuruku kernel: [drm]   HPD3
Feb 23 01:41:59 hojuruku kernel: [drm]   DDC: 0x4878 0x4878 0x4879 0x4879
0x487a 0x487a 0x487b 0x487b
Feb 23 01:41:59 hojuruku kernel: [drm]   Encoders:
Feb 23 01:41:59 hojuruku kernel: [drm]     DFP3: INTERNAL_UNIPHY
Feb 23 01:41:59 hojuruku kernel: [drm] Chained IB support enabled!


This is the issues I've had with it:
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (II) AMDGPU(0):
Number of EDID sections to follow: 1
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (II) AMDGPU(0): E=
DID
(in hex):
Feb 23 01:42:00 hojuruku kernel: WARNING: CPU: 3 PID: 816 at
drivers/gpu/drm/amd/amdgpu/amdgpu_sa.c:326 amdgpu_sa_bo_new+0x463/0x480
[amdgpu]
Feb 23 01:42:00 hojuruku kernel: Modules linked in: snd_hda_codec_realtek
snd_hda_codec_generic cmdlinepart amdgpu(+) chash i2c_algo_bit gpu_sched
snd_hda_intel(+) snd_hda_codec ttm drm_kms_helper snd_hwdep intel_spi_platf=
orm
intel_spi drm spi_nor snd_hda_core ehci_pci mtd agpgart snd_pcm syscopyarea
sysfillrect ehci_hcd snd_timer sysimgblt fb_sys_fops snd soundcore xhci_pci
xhci_hcd
Feb 23 01:42:00 hojuruku kernel: CPU: 3 PID: 816 Comm: X Tainted: G        =
W=20=20=20
    4.15.0-rc4-haswell+ #1
Feb 23 01:42:00 hojuruku kernel: Hardware name: MSI MS-7850/B85-G41 PC
Mate(MS-7850), BIOS V2.10B3 02/18/2016
Feb 23 01:42:00 hojuruku kernel: RIP: 0010:amdgpu_sa_bo_new+0x463/0x480
[amdgpu]
Feb 23 01:42:00 hojuruku kernel: RSP: 0018:ffffc900025938d0 EFLAGS: 00010287
Feb 23 01:42:00 hojuruku kernel: RAX: ffff8803fd82ac00 RBX: ffff880406520000
RCX: 0000000000000100
Feb 23 01:42:00 hojuruku kernel: RDX: 0000000000000040 RSI: ffff8803fd82ae60
RDI: ffff880406523480
Feb 23 01:42:00 hojuruku kernel: RBP: ffff8803fd82ae60 R08: ffff88041dd9c600
R09: ffff8803fd82ac00
Feb 23 01:42:00 hojuruku kernel: R10: ffffc90002593aa8 R11: ffff880404c98090
R12: 0000000000000000
Feb 23 01:42:00 hojuruku kernel: R13: 0000000000000000 R14: 0000000000000400
R15: ffff880404c98000
Feb 23 01:42:00 hojuruku kernel: FS:  00007f491dd2f300(0000)
GS:ffff88041dd80000(0000) knlGS:0000000000000000
Feb 23 01:42:00 hojuruku kernel: CS:  0010 DS: 0000 ES: 0000 CR0:
0000000080050033
Feb 23 01:42:00 hojuruku kernel: CR2: 000055b6b5d201b8 CR3: 0000000404352006
CR4: 00000000001606e0
Feb 23 01:42:00 hojuruku kernel: Call Trace:
Feb 23 01:42:00 hojuruku kernel:  ? ttm_bo_handle_move_mem+0x28c/0x5b0 [ttm]
Feb 23 01:42:00 hojuruku kernel:  ? ___slab_alloc+0x416/0x5b0
Feb 23 01:42:00 hojuruku kernel:  ? amdgpu_vram_mgr_new+0x1d9/0x2a0 [amdgpu]
Feb 23 01:42:00 hojuruku kernel:  ? ttm_bo_validate+0x104/0x110 [ttm]
Feb 23 01:42:00 hojuruku kernel:  ? security_capable+0x4f/0x70
Feb 23 01:42:00 hojuruku kernel:  ? amdgpu_job_alloc+0x45/0xc0 [amdgpu]
Feb 23 01:42:00 hojuruku kernel:  ? ttm_bo_init_reserved+0x2d4/0x450 [ttm]
Feb 23 01:42:00 hojuruku kernel:  ? amdgpu_job_alloc+0x45/0xc0 [amdgpu]
Feb 23 01:42:00 hojuruku kernel:  ? __slab_alloc+0x2a/0x40
Feb 23 01:42:00 hojuruku kernel:  amdgpu_ib_get+0x3b/0xa0 [amdgpu]
Feb 23 01:42:00 hojuruku kernel:  amdgpu_job_alloc_with_ib+0x50/0x90 [amdgp=
u]
Feb 23 01:42:00 hojuruku kernel:  amdgpu_vm_clear_bo+0xe4/0x2b0 [amdgpu]
Feb 23 01:42:00 hojuruku kernel:  amdgpu_vm_alloc_levels+0x1f6/0x350 [amdgp=
u]
Feb 23 01:42:00 hojuruku kernel:  amdgpu_vm_alloc_pts+0x5b/0x90 [amdgpu]
Feb 23 01:42:00 hojuruku kernel:  amdgpu_gem_va_ioctl+0x27c/0x510 [amdgpu]
Feb 23 01:42:00 hojuruku kernel:  ? amdgpu_gem_create_ioctl+0x180/0x250
[amdgpu]
Feb 23 01:42:00 hojuruku kernel:  ? amdgpu_gem_metadata_ioctl+0x1b0/0x1b0
[amdgpu]
Feb 23 01:42:00 hojuruku kernel:  ? drm_ioctl_kernel+0x63/0xb0 [drm]
Feb 23 01:42:00 hojuruku kernel:  drm_ioctl_kernel+0x63/0xb0 [drm]
Feb 23 01:42:00 hojuruku kernel:  drm_ioctl+0x2dc/0x380 [drm]
Feb 23 01:42:00 hojuruku kernel:  ? amdgpu_gem_metadata_ioctl+0x1b0/0x1b0
[amdgpu]
Feb 23 01:42:00 hojuruku kernel:  ? __handle_mm_fault+0x875/0xf50
Feb 23 01:42:00 hojuruku kernel:  amdgpu_drm_ioctl+0x57/0x90 [amdgpu]
Feb 23 01:42:00 hojuruku kernel:  do_vfs_ioctl+0x97/0x5e0
Feb 23 01:42:00 hojuruku kernel:  ? handle_mm_fault+0xd2/0x1a0
Feb 23 01:42:00 hojuruku kernel:  ? __do_page_fault+0x223/0x3f0
Feb 23 01:42:00 hojuruku kernel:  SyS_ioctl+0x7e/0x90
Feb 23 01:42:00 hojuruku kernel:  entry_SYSCALL_64_fastpath+0x1a/0x7d
Feb 23 01:42:00 hojuruku kernel: RIP: 0033:0x7f491efaa6f7
Feb 23 01:42:00 hojuruku kernel: RSP: 002b:00007fff8e587648 EFLAGS: 00000246
ORIG_RAX: 0000000000000010
Feb 23 01:42:00 hojuruku kernel: RAX: ffffffffffffffda RBX: 000055b6b5d1fcb0
RCX: 00007f491efaa6f7
Feb 23 01:42:00 hojuruku kernel: RDX: 00007fff8e5876b0 RSI: 00000000c0286448
RDI: 000000000000000e
Feb 23 01:42:00 hojuruku kernel: RBP: 00007f491f2701f8 R08: 0000000100200000
R09: 000000000000000e
Feb 23 01:42:00 hojuruku kernel: R10: 000000000000000c R11: 0000000000000246
R12: 00007f491f26fad8
Feb 23 01:42:00 hojuruku kernel: R13: 00000000000004f0 R14: 00007f491f26fa80
R15: 00000000000052e0
Feb 23 01:42:00 hojuruku kernel: Code: 00 00 00 e9 21 ff ff ff 8b 54 24 1c =
8b
74 24 18 48 8b 3c 24 e8 0f f7 ff ff 84 c0 74 9a eb c2 0f ff bb ea ff ff ff =
e9
fc fc ff ff <0f> ff bb ea ff ff ff e9 f0 fc ff ff bb f4 ff ff ff e9 e=
6 fc ff=20
Feb 23 01:42:00 hojuruku kernel: ---[ end trace de335683cd4d1a49 ]---
Feb 23 01:42:00 hojuruku kernel: amdgpu 0000:01:00.0: failed to get a new IB
(-22)
Feb 23 01:42:00 hojuruku kernel: amdgpu 0000:01:00.0: failed to get a new IB
(-22)
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: Failed to allocate
front buffer memory
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) AMDGPU(0):
amdgpu_setup_kernel_mem failed
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE)
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: Fatal server erro=
r:
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE)
AddScreen/ScreenInit failed for driver 0
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE)
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: Please consult the
The X.Org Foundation support
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]:          at
http://wiki.x.org
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]:  for help.
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) Please also
check the log file at "/var/log/Xorg.0.log" for additional inform=
ation.
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE)
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: (EE) Server
terminated with error (1). Closing log file.
Feb 23 01:42:00 hojuruku /usr/libexec/gdm-x-session[814]: Unable to run X
server

then a systemd loop with

Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (II) UnloadModul=
e:
"modesetting"
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) Device(s)
detected, but none match those in the config file.
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE)
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: Fatal server err=
or:
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) no screens
found(EE)
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE)
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: Please consult t=
he
The X.Org Foundation support
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]:          at
http://wiki.x.org
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]:  for help.
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE) Please also
check the log file at "/var/log/Xorg.0.log" for additional inform=
ation.
Feb 23 01:42:07 hojuruku /usr/libexec/gdm-x-session[1070]: (EE)
Feb 23 01:42:07 hojuruku kernel: amdgpu 0000:01:00.0: failed to get a new IB
(-22)
Feb 23 01:42:07 hojuruku kernel: amdgpu 0000:01:00.0: failed to get a new IB
(-22)

You are receiving this mail because:
  • You are the assignee for the bug.
= --15193276992.feda18.11302-- --===============0506665955== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZHJpLWRldmVs IG1haWxpbmcgbGlzdApkcmktZGV2ZWxAbGlzdHMuZnJlZWRlc2t0b3Aub3JnCmh0dHBzOi8vbGlz dHMuZnJlZWRlc2t0b3Aub3JnL21haWxtYW4vbGlzdGluZm8vZHJpLWRldmVsCg== --===============0506665955==--