Date: Mon, 31 Jan 2022 13:05:12 +0100 From: Emmanuel Vadot <manu@bidouilliste.com> To: Vladimir Kondratyev <wulf@FreeBSD.org> Cc: freebsd-current@freebsd.org Subject: Re: Kernel changes causing AMDGPU / DRM to fail? i2c related? Message-ID: <20220131130512.ebc9efe4877db832e657af01@bidouilliste.com> In-Reply-To: <41f0a849-f2c9-75fe-e0ed-e60356ac4728@FreeBSD.org> References: <a9560156-4d67-7ca2-e276-31e5585ce58e@FreeBSD.org> <4611d16a-ef17-d8f3-c2c0-1b1091723646@FreeBSD.org> <c415393e-1cf0-2f7f-36c8-9d4bde73cfdc@FreeBSD.org> <41f0a849-f2c9-75fe-e0ed-e60356ac4728@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 31 Jan 2022 14:19:53 +0300 Vladimir Kondratyev <wulf@FreeBSD.org> wrote: > On 30.01.2022 22:43, Stefan Esser wrote: > > Am 30.01.22 um 19:23 schrieb Vladimir Kondratyev: > >> 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". > >>> > > [...] > >>> [drm] AMDGPU Display Connectors > >>> [drm] Connector 0: > >>> [drm]=A0=A0 DP-1 > >>> [drm]=A0=A0 HPD4 > >>> [drm]=A0=A0 DDC: 0x1950 0x1950 0x1951 0x1951 0x1952 0x1952 0x1953 0x1= 953 > >>> [drm]=A0=A0 Encoders: > >>> [drm]=A0=A0=A0=A0 DFP1: INTERNAL_UNIPHY2 > >>> [drm] Connector 1: > >>> [drm]=A0=A0 HDMI-A-1 > >>> [drm]=A0=A0 HPD1 > >>> [drm]=A0=A0 DDC: 0x195c 0x195c 0x195d 0x195d 0x195e 0x195e 0x195f 0x1= 95f > >>> [drm]=A0=A0 Encoders: > >>> [drm]=A0=A0=A0=A0 DFP2: INTERNAL_UNIPHY2 > >>> [drm] Connector 2: > >>> [drm]=A0=A0 DVI-I-1 > >>> [drm]=A0=A0 HPD2 > >>> [drm]=A0=A0 DDC: 0x1958 0x1958 0x1959 0x1959 0x195a 0x195a 0x195b 0x1= 95b > >>> [drm]=A0=A0 Encoders: > >>> [drm]=A0=A0=A0=A0 DFP3: INTERNAL_UNIPHY > >>> [drm]=A0=A0=A0=A0 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]=A0=A0=A0=A0 CRT1: INTERNAL_KLDSCP_DAC1 > >>> [drm] fb mappable at 0xE0503000 > >>> [drm] vram apper at 0xE0000000 > >>> [drm] size 33177600 > >>> [drm] fb depth is 24 > >>> [drm]=A0=A0=A0 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. > >=20 > > Hi Vladimir, > >=20 > > thank you for the information! I'm using drm-devel-kmod, and in fact fo= und > > that 5.5.19.g20211230 works, while 5.7.19.g20220126 (committed as 0c386= 74b389ad > > on 2022-01-26) causes the failure. > >=20 > >> You may try to checkout previous revision (444dc58f0247) to find out i= f in-base > >> i2c is guilty or not. > >=20 > > Assuming that the same change to use the system i2c code has been in th= e latest > > commit to the drm-devel-kmod port, this should be proven, now. ;-) > >=20 > > These is the list of in-kernel i2c modules on my system (a Ryzen 9 5950= on an > > ASUS mainboard with B550 chip-set): > >=20 > > $ kldstat -v | grep iic > > 68 iicsmb/smbus > > 67 iicbus/iicsmb > > 66 iichb/iicbus > > 65 iicbb/iicbus > > 64 iicbus/iic > > 63 iicbus/ic > > 213 lkpi_iicbb/iicbb > > 212 lkpi_iic/lkpi_iicbb > > 211 lkpi_iic/iicbus > > 210 drmn/lkpi_iic > > 56 iichid/hidbus > >=20 > > Can I help debug this issue? > >=20 > > I could re-install the latest version and boot with hw.dri.drm_debug or > > dev.drm.drm_debug set? > >=20 > > Or are there other settings to get a debug log from the i2c side? > >=20 > > Regards, STefan > >=20 > > PS: I'm keeping the CC to current@, since this might be an issue in the= i2c > > kernel code ... >=20 > There are no successful lkpi_iic attachments in your output. They look li= ke: >=20 > lkpi_iic0: <LinuxKPI I2C> on drmn0 >=20 > Please share your `devinfo -v` output. > Kldload output with verbose boot enabled can be helpful too. That's because this card is probably using the bitbang part. As stated in the commit this wasn't tested as I don't have compatible hardware. It's likely a timing issue in the bitbang part. That's the main reason it's only in master and 5.7 branch of drm-kmod, so people can debug/fix. --=20 Emmanuel Vadot <manu@bidouilliste.com> <manu@FreeBSD.org>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20220131130512.ebc9efe4877db832e657af01>