From nobody Sun Jan 30 18:23:49 2022 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id B7F7B1981F20 for ; Sun, 30 Jan 2022 18:23:55 +0000 (UTC) (envelope-from wulf@FreeBSD.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4Jn02M33Nbz4b3j for ; Sun, 30 Jan 2022 18:23:55 +0000 (UTC) (envelope-from wulf@FreeBSD.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643567035; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Pra/yrAM2fg4F6Qe9Lzl/mJUWmGcMY9Fq/MBg3ZEG0Q=; b=p0tsuLVfdn2Eg6e0M8MmRDBuqdugZxK/jlgr103y/ZfV3JMZJbztXDYRUyDdjl5A+3N+rg vmlOHEaNtxWCawf3PkIhI9ba8UyT9GrHYrcRTbC8VF2XeL8bZ8HxEvr+uybnuQAyYDpJAp zwjDfJPrvhzdsEe2xBI/tnA3YdAjwyfikDZ/9hdeN3E2y8HivYd8j05+GlIb7Fy7OAoEUN YSjdTUtLg7lCkURUuoXukO8uBRJSGpJic+Fb/77k9rgNxMLCGEQEHiB9ELYD3+9ilz0CM0 NSYd3JqCQapizifDSUtv4+lzRGG0CNTeszfA27BQcHoFJsgiaqFd8uMG7E8/xw== Received: from [192.168.0.30] (unknown [176.120.228.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: wulf) by smtp.freebsd.org (Postfix) with ESMTPSA id 022B280BA for ; Sun, 30 Jan 2022 18:23:54 +0000 (UTC) (envelope-from wulf@FreeBSD.org) Message-ID: <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org> Date: Sun, 30 Jan 2022 21:23:49 +0300 List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:91.0) Gecko/20100101 Thunderbird/91.5.0 Subject: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related? Content-Language: en-US To: freebsd-current@freebsd.org References: From: Vladimir Kondratyev In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1643567035; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=Pra/yrAM2fg4F6Qe9Lzl/mJUWmGcMY9Fq/MBg3ZEG0Q=; b=e+L4nq+SQoMQazsGvsO49kx/kDQPxUWR8X7U4q5xZmuksIcHlZfqWgVoe9m94aQ8Tgs7V/ bNBBSEH/FRowNOEH7LCxE0XjRsImkWKXyj4AmwdSCEQ9+bDyOaylTsWAJt3I0eA34QFEJd TnFAPSMTuF52WzLyLftjTbm0Lhp1miQAGIVRDlpJ6H9aYugsNu+xB2Gw6RbN6dAMA+ZcFA KdoN37BdX78RVCL+ycaLHSXaw0OnqRM+0p6SsgcdaE6OWUzgGRqFgX6Hn2RMaLhN0MNDxC +ryl0Oljzc/g7d8WP43BVjclytnAKkoo0OwuMMhBZa3dG8DfkzwxO1N9c3fmyg== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1643567035; a=rsa-sha256; cv=none; b=duHWVx0+A910hwjRVKgMtb3i9g+9573qDJD362lNzV08nHOwIN7MQIcZ1zLF/2XXmm1vO0 HjPcJd0h3s3XUAUUU54FOxf7jBcWUYMK42QbuMs4nygvwg+MYIvnWSHWDP68gEM/zF/cD+ 0ezP+SlIuwpGM+5pa74fYzmvI5Tg6hd8dojfjbkXmaZiFHQmkFStH2BJHwcL+508ybnopi IfaAyDX3hl9at47Opwe+ae/psnDil1/a76WCXKk5MlVdawv8XwUCsMy/whtU/Hy88pkL4N NqlfL/3w5hC7PKlmkHKNRZp0mfYlrlo3mX0O7ZDF/o9gaU5LyRnlBaZuLtcTwA== ARC-Authentication-Results: i=1; mx1.freebsd.org; none X-ThisMailContainsUnwantedMimeParts: N On 30.01.2022 00:25, Stefan Esser wrote: > After rebooting with freshly built world, kernel and the amdgpu driver > my console stopped working. It goes blank and the display goes into a > power save mode, as soon as the amdgpu driver is loaded. > > The GPU (a Radeon R7 250E) is correctly detected as before, but there > is an error message "drmn0: [drm] Cannot find any crtc or sizes". > > I'm asking here and not on the ports list, since the AMDGPU driver has > not been updated for half a year. But to be sure that there is no mismatch > between kernel and user land, I have rebuilt all X11 server and library > ports. > > There have been changes affecting the i2c driver, IIRC, and the error > message seems to point at an issue obtaining information from the LCD > display. > > The output of "grep drm /var/run/dmesg.boot" follows: > > [drm] amdgpu kernel modesetting enabled. > drmn0: on vgapci0 > vgapci0: child drmn0 requested pci_enable_io > vgapci0: child drmn0 requested pci_enable_io > [drm] initializing kernel modesetting (VERDE 0x1002:0x683F 0x174B:0xA001 0x00). > [drm] register mmio base: 0xFCE00000 > [drm] register mmio size: 262144 > [drm] add ip block number 0 > [drm] add ip block number 1 > [drm] add ip block number 2 > [drm] add ip block number 3 > [drm] add ip block number 4 > [drm] add ip block number 5 > [drm] add ip block number 6 > [drm] BIOS signature incorrect 0 0 > [drm] vm size is 512 GB, 2 levels, block size is 10-bit, fragment size is 9-bit > drmn0: successfully loaded firmware image 'amdgpu/verde_mc.bin' > drmn0: VRAM: 1024M 0x000000F400000000 - 0x000000F43FFFFFFF (1024M used) > drmn0: GART: 1024M 0x000000FF00000000 - 0x000000FF3FFFFFFF > [drm] Detected VRAM RAM=1024M, BAR=256M > [drm] RAM width 128bits GDDR5 > [drm] amdgpu: 1024M of VRAM memory ready > [drm] amdgpu: 3072M of GTT memory ready. > [drm] GART: num cpu pages 262144, num gpu pages 262144 > drmn0: PCIE GART of 1024M enabled (table at 0x000000F400500000). > [drm] Supports vblank timestamp caching Rev 2 (21.10.2013). > drmn0: successfully loaded firmware image 'amdgpu/verde_pfp.bin' > drmn0: successfully loaded firmware image 'amdgpu/verde_me.bin' > drmn0: successfully loaded firmware image 'amdgpu/verde_ce.bin' > drmn0: successfully loaded firmware image 'amdgpu/verde_rlc.bin' > drmn0: successfully loaded firmware image 'amdgpu/verde_smc.bin' > [drm] Internal thermal controller without fan control > [drm] amdgpu: dpm initialized > [drm] Connector DP-1: get mode from tunables: > [drm] - kern.vt.fb.modes.DP-1 > [drm] - kern.vt.fb.default_mode > [drm] Connector HDMI-A-1: get mode from tunables: > [drm] - kern.vt.fb.modes.HDMI-A-1 > [drm] - kern.vt.fb.default_mode > [drm] Connector DVI-I-1: get mode from tunables: > [drm] - kern.vt.fb.modes.DVI-I-1 > [drm] - kern.vt.fb.default_mode > [drm] AMDGPU Display Connectors > [drm] Connector 0: > [drm] DP-1 > [drm] HPD4 > [drm] DDC: 0x1950 0x1950 0x1951 0x1951 0x1952 0x1952 0x1953 0x1953 > [drm] Encoders: > [drm] DFP1: INTERNAL_UNIPHY2 > [drm] Connector 1: > [drm] HDMI-A-1 > [drm] HPD1 > [drm] DDC: 0x195c 0x195c 0x195d 0x195d 0x195e 0x195e 0x195f 0x195f > [drm] Encoders: > [drm] DFP2: INTERNAL_UNIPHY2 > [drm] Connector 2: > [drm] DVI-I-1 > [drm] HPD2 > [drm] DDC: 0x1958 0x1958 0x1959 0x1959 0x195a 0x195a 0x195b 0x195b > [drm] Encoders: > [drm] DFP3: INTERNAL_UNIPHY > [drm] CRT1: INTERNAL_KLDSCP_DAC1 > drmn0: [drm] Cannot find any crtc or sizes > drmn0: [drm] Cannot find any crtc or sizes > drmn0: [drm] Cannot find any crtc or sizes > [drm] Initialized amdgpu 3.37.0 20150101 for drmn0 on minor 0 > > A successful driver attach from a reboot a few days ago had ended in: > > [drm] CRT1: INTERNAL_KLDSCP_DAC1 > [drm] fb mappable at 0xE0503000 > [drm] vram apper at 0xE0000000 > [drm] size 33177600 > [drm] fb depth is 24 > [drm] pitch is 15360 > [drm] Initialized amdgpu 3.36.0 20150101 for drmn0 on minor 0 > > Regards, STefan drm-kmod commit 534aa199c10d forced it to use i2c from base. You may try to checkout previous revision (444dc58f0247) to find out if in-base i2c is guilty or not. -- WBR Vladimir Kondratyev