Date: Tue, 7 Apr 2020 08:27:43 +0000 From: Grzegorz Junka <list1@gjunka.com> To: freebsd-ports@freebsd.org Subject: Re: amdgpu panics Message-ID: <2c1d5679-811f-0b01-f032-7261e9f57259@gjunka.com> In-Reply-To: <16501c75-24b0-54f6-972c-1a03dfe50276@selasky.org> References: <be363a85-cf11-f0d9-b6ca-39f0013322c7@gjunka.com> <d9f2137e-8e23-b00f-fe82-a1f83a6fe778@selasky.org> <6b0092f3-8d90-f1bc-b2ae-cf2fa2f029e0@gjunka.com> <d037e4dd-75a1-dcab-74f6-0cbfde452b7d@selasky.org> <47774b7a-0a6d-8806-6dee-4f0036651ace@gjunka.com> <20200312163447.GB42880@phouka1.phouka.net> <e880d6b2-92a5-ed60-5ef8-21812f193aa3@gjunka.com> <8d8ae2c8-1ecd-5c8c-2437-4e47cf48bd60@gmx.de> <96c03c59-b28e-3af1-e98b-e95517c20010@gjunka.com> <83bfb6f7-0a84-2905-7849-e4e93d9f6fb1@selasky.org> <9426b9bb-4fe6-37ba-ecb4-13a1ade47f92@gjunka.com> <9bc766aa-b17f-e8bc-bea2-11431972cf5d@selasky.org> <c5a5a71e-a1e2-2efd-b45d-d68daa893fa4@gjunka.com> <2ddfe444-7a20-9835-0875-6f93aa0f6ab3@gmx.de> <5fb0aa95-9aa1-e170-15fe-ba5ce77869db@gjunka.com> <ee76773a-26c9-b504-2f3f-4e8f3df450ac@selasky.org> <72befef2-16f2-a452-9e36-a3986988c556@gjunka.com> <16501c75-24b0-54f6-972c-1a03dfe50276@selasky.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 06/04/2020 23:49, Hans Petter Selasky wrote: > On 2020-04-07 00:07, Grzegorz Junka wrote: >> >> Is it possible to at least gather some debug info where this happens? >> I don't think there is any core dumped if the system doesn't panic? > > Can you SSH to this machine and get dmesg? > I sent the dmesg after booting privately as it was quite long. One interesting thing I just noticed is that the halt is not a complete halt. The system responds to ping and an ssh user session was active, in the sense that I could do ls -l and get a response. But it hung as soon as I tried su. Same with initiating any new ssh session - the system responds with prompt for password but after that nothing happens. This is the content of the messages log starting at the moment when I try to load the modules: Apr 7 07:54:30 venus kernel: [drm] amdgpu kernel modesetting enabled. Apr 7 07:54:30 venus kernel: drmn0: <drmn> on vgapci0 Apr 7 07:54:30 venus kernel: vgapci0: child drmn0 requested pci_enable_io Apr 7 07:54:30 venus syslogd: last message repeated 1 times Apr 7 07:54:30 venus kernel: [drm] initializing kernel modesetting (VEGA10 0x1002:0x687F 0x1002:0x0B36 0xC0). Apr 7 07:54:30 venus kernel: [drm] register mmio base: 0xFD100000 Apr 7 07:54:30 venus kernel: [drm] register mmio size: 524288 Apr 7 07:54:30 venus kernel: [drm] PCI I/O BAR is not found. Apr 7 07:54:30 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_gpu_info.bin Apr 7 07:54:30 venus kernel: [drm] probing gen 2 caps for device 1022:1471 = 700d03/e Apr 7 07:54:30 venus kernel: [drm] probing mlw for device 1002:687f = 400d03 Apr 7 07:54:30 venus kernel: [drm] UVD is enabled in VM mode Apr 7 07:54:30 venus kernel: [drm] UVD ENC is enabled in VM mode Apr 7 07:54:30 venus kernel: [drm] VCE enabled in VM mode Apr 7 07:54:30 venus kernel: ATOM BIOS: 113-D0500500-104 Apr 7 07:54:30 venus kernel: [drm] vm size is 262144 GB, 4 levels, block size is 9-bit, fragment size is 9-bit Apr 7 07:54:30 venus kernel: drmn0: VRAM: 8176M 0x000000F400000000 - 0x000000F5FEFFFFFF (8176M used) Apr 7 07:54:30 venus kernel: drmn0: GTT: 256M 0x000000F600000000 - 0x000000F60FFFFFFF Apr 7 07:54:30 venus kernel: Successfully added WC MTRR for [0xe0000000-0xefffffff]: 0; Apr 7 07:54:30 venus kernel: [drm] Detected VRAM RAM=8176M, BAR=256M Apr 7 07:54:30 venus kernel: [drm] RAM width 2048bits HBM Apr 7 07:54:30 venus kernel: [TTM] Zone kernel: Available graphics memory: 33495488 kiB Apr 7 07:54:30 venus kernel: [TTM] Zone dma32: Available graphics memory: 2097152 kiB Apr 7 07:54:30 venus kernel: [TTM] Initializing pool allocator Apr 7 07:54:30 venus kernel: [drm] amdgpu: 8176M of VRAM memory ready Apr 7 07:54:30 venus kernel: [drm] amdgpu: 8176M of GTT memory ready. Apr 7 07:54:30 venus kernel: i_size_write unimplemented Apr 7 07:54:30 venus kernel: [drm] GART: num cpu pages 65536, num gpu pages 65536 Apr 7 07:54:30 venus kernel: [drm] PCIE GART of 256M enabled (table at 0x000000F400800000). Apr 7 07:54:31 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_sos.bin Apr 7 07:54:32 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_asd.bin Apr 7 07:54:32 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_acg_smc.bin Apr 7 07:54:33 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_pfp.bin Apr 7 07:54:33 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_me.bin Apr 7 07:54:34 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_ce.bin Apr 7 07:54:34 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_rlc.bin Apr 7 07:54:35 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_mec.bin Apr 7 07:54:35 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_mec2.bin Apr 7 07:54:35 venus kernel: i_size_write unimplemented Apr 7 07:54:35 venus syslogd: last message repeated 9 times Apr 7 07:54:36 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_sdma.bin Apr 7 07:54:36 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_sdma1.bin Apr 7 07:54:36 venus kernel: [drm] use_doorbell being set to: [true] Apr 7 07:54:36 venus kernel: i_size_write unimplemented Apr 7 07:54:36 venus kernel: [drm] use_doorbell being set to: [true] Apr 7 07:54:36 venus kernel: i_size_write unimplemented Apr 7 07:54:37 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_uvd.bin Apr 7 07:54:37 venus kernel: [drm] Found UVD firmware Version: 65.29 Family ID: 17 Apr 7 07:54:37 venus kernel: [drm] PSP loading UVD firmware Apr 7 07:54:37 venus kernel: i_size_write unimplemented Apr 7 07:54:37 venus syslogd: last message repeated 2 times Apr 7 07:54:37 venus kernel: drmn0: successfully loaded firmware image with name: amdgpu/vega10_vce.bin Apr 7 07:54:37 venus kernel: [drm] Found VCE firmware Version: 57.4 Binary ID: 4 Apr 7 07:54:37 venus kernel: [drm] PSP loading VCE firmware Apr 7 07:54:37 venus kernel: i_size_write unimplemented Apr 7 07:54:37 venus syslogd: last message repeated 2 times Apr 7 07:54:38 venus kernel: [drm] Display Core initialized with v3.1.27! Apr 7 07:54:38 venus kernel: [drm] Connector DP-1: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-1 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-2: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-2 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode Apr 7 07:54:38 venus kernel: [drm] Connector DP-3: get mode from tunables: Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.modes.DP-3 Apr 7 07:54:38 venus kernel: [drm] - kern.vt.fb.default_mode GrzegorzJ
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2c1d5679-811f-0b01-f032-7261e9f57259>