Bug#1022025: fails to boot on machines with AMD integrated graphics
# raising severity for now
Control: severity -1 serious
Hi,
On Wed, Oct 19, 2022 at 10:01:58PM +, Dan Coleman wrote:
> I tried again, same result. Either the patches aren't working OR I
> don't adequately know how to install test kernels. In no uncertain
> terms, it could very well be my lack of knowledge and ability in
> this regard.
On the https://gitlab.freedesktop.org/drm/amd/-/issues/2216 Alex
Deucher is claiming the issue should be fixed by
https://gitlab.freedesktop.org/drm/amd/-/issues/2216#note_1599805 .
So can you (or someone else affected) try next the attached patch?
(interestingly though the mentioned commit which uncovers the issue
was first applied in 5.10.137, then reverted in 5.10.141, so it's
unclear why the issue would still manifest).
Else if anyone with affected hardware is able to bisect between
5.10.140 and 5.10.149 that would be great.
Regards,
Salvatore
>From 62fda3a8cbc93d50974bb320c0e95e2b6308f4b9 Mon Sep 17 00:00:00 2001
From: Alex Deucher
Date: Wed, 19 Oct 2022 16:57:42 -0400
Subject: [PATCH] drm/amdgpu: fix sdma doorbell init ordering on APUs
Commit 8795e182b02d ("PCI/portdrv: Don't disable AER reporting in get_port_device_capability()")
uncovered a bug in amdgpu that required a reordering of the driver
init sequence to avoid accessing a special register on the GPU
before it was properly set up leading to an PCI AER error. This
reordering uncovered a different hw programming ordering dependency
in some APUs where the SDMA doorbells need to be programmed before
the GFX doorbells. To fix this, move the SDMA doorbell programming
back into the soc15 common code, but use the actual doorbell range
values directly rather than the values stored in the ring structure
since those will not be initialized at this point.
This is a partial revert, but with the doorbell assignment
fixed so the proper doorbell index is set before it's used.
Fixes: e3163bc8ffdfdb ("drm/amdgpu: move nbio sdma_doorbell_range() into sdma code for vega")
Signed-off-by: Alex Deucher
Cc: sk...@linuxfoundation.org
---
drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c | 5 -
drivers/gpu/drm/amd/amdgpu/soc15.c | 21 +
2 files changed, 21 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c b/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
index 298fa11702e7..1122bd4eae98 100644
--- a/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
+++ b/drivers/gpu/drm/amd/amdgpu/sdma_v4_0.c
@@ -1417,11 +1417,6 @@ static int sdma_v4_0_start(struct amdgpu_device *adev)
WREG32_SDMA(i, mmSDMA0_CNTL, temp);
if (!amdgpu_sriov_vf(adev)) {
- ring = >sdma.instance[i].ring;
- adev->nbio.funcs->sdma_doorbell_range(adev, i,
-ring->use_doorbell, ring->doorbell_index,
-adev->doorbell_index.sdma_doorbell_range);
-
/* unhalt engine */
temp = RREG32_SDMA(i, mmSDMA0_F32_CNTL);
temp = REG_SET_FIELD(temp, SDMA0_F32_CNTL, HALT, 0);
diff --git a/drivers/gpu/drm/amd/amdgpu/soc15.c b/drivers/gpu/drm/amd/amdgpu/soc15.c
index 183024d7c184..e3b2b6b4f1a6 100644
--- a/drivers/gpu/drm/amd/amdgpu/soc15.c
+++ b/drivers/gpu/drm/amd/amdgpu/soc15.c
@@ -1211,6 +1211,20 @@ static int soc15_common_sw_fini(void *handle)
return 0;
}
+static void soc15_sdma_doorbell_range_init(struct amdgpu_device *adev)
+{
+ int i;
+
+ /* sdma doorbell range is programed by hypervisor */
+ if (!amdgpu_sriov_vf(adev)) {
+ for (i = 0; i < adev->sdma.num_instances; i++) {
+ adev->nbio.funcs->sdma_doorbell_range(adev, i,
+true, adev->doorbell_index.sdma_engine[i] << 1,
+adev->doorbell_index.sdma_doorbell_range);
+ }
+ }
+}
+
static int soc15_common_hw_init(void *handle)
{
struct amdgpu_device *adev = (struct amdgpu_device *)handle;
@@ -1230,6 +1244,13 @@ static int soc15_common_hw_init(void *handle)
/* enable the doorbell aperture */
soc15_enable_doorbell_aperture(adev, true);
+ /* HW doorbell routing policy: doorbell writing not
+ * in SDMA/IH/MM/ACV range will be routed to CP. So
+ * we need to init SDMA doorbell range prior
+ * to CP ip block init and ring test. IH already
+ * happens before CP.
+ */
+ soc15_sdma_doorbell_range_init(adev);
return 0;
}
--
2.37.3
Bug#1022025: fails to boot on machines with AMD integrated graphics
I tried again, same result. Either the patches aren't working OR I don't adequately know how to install test kernels. In no uncertain terms, it could very well be my lack of knowledge and ability in this regard. On Wed, 19 Oct 2022 16:01:14 + Dan Coleman wrote: > I'm recompiling to start from scratch and make sure I did this correctly, > but I'll be away from my computer for several hours. If anyone else wants to > jump in and report their own findings, feel free! Hopefully there's some new > info when I get back. > > Thanks very much to Salvatore and Diederik for their help. > > On 10/19/22 10:38 AM, Dan Coleman wrote: > > Ok, I think I succeeded in getting the test kernel to install, but it did > > not solve the issue. The fans ramped up a bit, and I didn't get any errors > > about DRM on the console, but it still hung on the black screen. > > > > Of course, I may have royally screwed up installing the kernel (thank > > goodness for Timeshift), so I welcome another, more experienced tester to > > verify my own findings. > > > > On 10/19/22 10:26 AM, Salvatore Bonaccorso wrote: > >> Hi Dan, hi Diederik > >> > >> On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote: > >>> On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: > $ sudo dpkg -i > ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: > considering removing linux-image-5.10.0-19-amd64 in favour of > linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with > removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): > linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) > linux-image-5.10.0-19-amd64 is to be removed. > >>> AFAICT, the last line indicates the problem. > >>> I do know how I would resolve it on my system and if my initial attempt > >>> fails > >>> how to fix that, but I don't feel comfortable suggesting that to you. > >>> > >>> So, I'll let Salvatore take over as he's (WAY) more experienced then I > >>> am. > >> You need to have (temporarily at least) removed the signed package > >> indeed, as they are conflicting. If you do it with apt-get install > >> ./path/to/local/package.deb all the surronding work should be done as > >> well. > >> > >> (And you have the 18 ABI kernel still installed to which you can go > >> back if th test package does no work). > >> > >> After testing, make sure to reinstall the linux-image-amd64 package > >> again. > >> > >> Regards, > >> Salvatore > > >
Bug#1022025: fails to boot on machines with AMD integrated graphics
I'm recompiling to start from scratch and make sure I did this correctly, but I'll be away from my computer for several hours. If anyone else wants to jump in and report their own findings, feel free! Hopefully there's some new info when I get back. Thanks very much to Salvatore and Diederik for their help. On 10/19/22 10:38 AM, Dan Coleman wrote: > Ok, I think I succeeded in getting the test kernel to install, but it did not > solve the issue. The fans ramped up a bit, and I didn't get any errors about > DRM on the console, but it still hung on the black screen. > > Of course, I may have royally screwed up installing the kernel (thank > goodness for Timeshift), so I welcome another, more experienced tester to > verify my own findings. > > On 10/19/22 10:26 AM, Salvatore Bonaccorso wrote: >> Hi Dan, hi Diederik >> >> On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote: >>> On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: $ sudo dpkg -i ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: considering removing linux-image-5.10.0-19-amd64 in favour of linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) linux-image-5.10.0-19-amd64 is to be removed. >>> AFAICT, the last line indicates the problem. >>> I do know how I would resolve it on my system and if my initial attempt >>> fails >>> how to fix that, but I don't feel comfortable suggesting that to you. >>> >>> So, I'll let Salvatore take over as he's (WAY) more experienced then I am. >> You need to have (temporarily at least) removed the signed package >> indeed, as they are conflicting. If you do it with apt-get install >> ./path/to/local/package.deb all the surronding work should be done as >> well. >> >> (And you have the 18 ABI kernel still installed to which you can go >> back if th test package does no work). >> >> After testing, make sure to reinstall the linux-image-amd64 package >> again. >> >> Regards, >> Salvatore
Bug#1022025: fails to boot on machines with AMD integrated graphics
Ok, I think I succeeded in getting the test kernel to install, but it did not solve the issue. The fans ramped up a bit, and I didn't get any errors about DRM on the console, but it still hung on the black screen. Of course, I may have royally screwed up installing the kernel (thank goodness for Timeshift), so I welcome another, more experienced tester to verify my own findings. On 10/19/22 10:26 AM, Salvatore Bonaccorso wrote: > Hi Dan, hi Diederik > > On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote: >> On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: >>> $ sudo dpkg -i >>> ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: >>> considering removing linux-image-5.10.0-19-amd64 in favour of >>> linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with >>> removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): >>> linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) >>> linux-image-5.10.0-19-amd64 is to be removed. >> AFAICT, the last line indicates the problem. >> I do know how I would resolve it on my system and if my initial attempt fails >> how to fix that, but I don't feel comfortable suggesting that to you. >> >> So, I'll let Salvatore take over as he's (WAY) more experienced then I am. > You need to have (temporarily at least) removed the signed package > indeed, as they are conflicting. If you do it with apt-get install > ./path/to/local/package.deb all the surronding work should be done as > well. > > (And you have the 18 ABI kernel still installed to which you can go > back if th test package does no work). > > After testing, make sure to reinstall the linux-image-amd64 package > again. > > Regards, > Salvatore
Bug#1022025: fails to boot on machines with AMD integrated graphics
Hi Dan, hi Diederik On Wed, Oct 19, 2022 at 05:09:01PM +0200, Diederik de Haas wrote: > On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: > > $ sudo dpkg -i > > ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: > > considering removing linux-image-5.10.0-19-amd64 in favour of > > linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with > > removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): > > linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) > > linux-image-5.10.0-19-amd64 is to be removed. > > AFAICT, the last line indicates the problem. > I do know how I would resolve it on my system and if my initial attempt fails > how to fix that, but I don't feel comfortable suggesting that to you. > > So, I'll let Salvatore take over as he's (WAY) more experienced then I am. You need to have (temporarily at least) removed the signed package indeed, as they are conflicting. If you do it with apt-get install ./path/to/local/package.deb all the surronding work should be done as well. (And you have the 18 ABI kernel still installed to which you can go back if th test package does no work). After testing, make sure to reinstall the linux-image-amd64 package again. Regards, Salvatore
Bug#1022025: fails to boot on machines with AMD integrated graphics
On Wednesday, 19 October 2022 16:34:49 CEST Dan Coleman wrote: > $ sudo dpkg -i > ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: > considering removing linux-image-5.10.0-19-amd64 in favour of > linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with > removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): > linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) > linux-image-5.10.0-19-amd64 is to be removed. AFAICT, the last line indicates the problem. I do know how I would resolve it on my system and if my initial attempt fails how to fix that, but I don't feel comfortable suggesting that to you. So, I'll let Salvatore take over as he's (WAY) more experienced then I am. signature.asc Description: This is a digitally signed message part.
Bug#1022025: fails to boot on machines with AMD integrated graphics
$ sudo dpkg -i ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb dpkg: considering removing linux-image-5.10.0-19-amd64 in favour of linux-image-5.10.0-19-amd64-unsigned ... dpkg: no, cannot proceed with removal of linux-image-5.10.0-19-amd64 (--auto-deconfigure will help): linux-image-amd64 depends on linux-image-5.10.0-19-amd64 (= 5.10.149-1) linux-image-5.10.0-19-amd64 is to be removed. dpkg: regarding .../linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb containing linux-image-5.10.0-19-amd64-unsigned: linux-image-5.10.0-19-amd64-unsigned conflicts with linux-image-5.10.0-19-amd64 linux-image-5.10.0-19-amd64 (version 5.10.149-1) is present and installed. dpkg: error processing archive ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb (--install): conflicting packages - not installing linux-image-5.10.0-19-amd64-unsigned Errors were encountered while processing: ./linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb On 10/19/22 09:32 AM, Diederik de Haas wrote: > On Wednesday, 19 October 2022 16:12:22 CEST Dan Coleman wrote: >> I've built the test kernel successfully, how do I install it? I have the >> following four files. >> >> linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb >> linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb >> linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb >> linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb > # = do as root or with 'sudo' > > # dpkg -i linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb
Bug#1022025: fails to boot on machines with AMD integrated graphics
On Wednesday, 19 October 2022 16:12:22 CEST Dan Coleman wrote: > I've built the test kernel successfully, how do I install it? I have the > following four files. > > linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb > linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb > linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb > linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb # = do as root or with 'sudo' # dpkg -i linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb signature.asc Description: This is a digitally signed message part.
Bug#1022025: fails to boot on machines with AMD integrated graphics
Hi, I've built the test kernel successfully, how do I install it? I have the following four files. linux-headers-5.10.0-19-amd64_5.10.149-1a~test_amd64.deb linux-image-5.10.0-19-amd64-dbg_5.10.149-1a~test_amd64.deb linux-image-5.10.0-19-amd64-unsigned_5.10.149-1a~test_amd64.deb linux-image-amd64-dbg_5.10.149-1a~test_amd64.deb On 10/19/22 08:18 AM, Salvatore Bonaccorso wrote: > Hi Dan, > > On Wed, Oct 19, 2022 at 12:55:16PM +, Dan Coleman wrote: >> Hi, >> >> I would love to, but I'm afraid I don't know how. If you or anyone on the >> chain is willing to show me what commands to enter (I tried following >> thishttps://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html >> but got as far as 4.2.2 and couldn't find a debian directory in the source >> that I unpacked by following the prior instructions), I would be grateful. >> >> That said, I understand time and resources are limited, so no worries if >> that's not possible! > When you do fetch the source package the output will look like: > > # apt-get source linux > Reading package lists... Done > NOTICE: 'linux' packaging is maintained in the 'Git' version control system > at: > https://salsa.debian.org/kernel-team/linux.git > Please use: > git clonehttps://salsa.debian.org/kernel-team/linux.git > to retrieve the latest (possibly unreleased) updates to the package. > Need to get 124 MB of source archives. > Get:1http://security.debian.org/debian-security bullseye-security/main linux > 5.10.149-1 (dsc) [197 kB] > Get:2http://security.debian.org/debian-security bullseye-security/main linux > 5.10.149-1 (tar) [122 MB] > Get:3http://security.debian.org/debian-security bullseye-security/main linux > 5.10.149-1 (diff) [1549 kB] > Fetched 124 MB in 1s (95.7 MB/s) > dpkg-source: info: extracting linux in linux-5.10.149 > dpkg-source: info: unpacking linux_5.10.149.orig.tar.xz > dpkg-source: info: unpacking linux_5.10.149-1.debian.tar.xz > dpkg-source: info: using patch list from debian/patches/series > dpkg-source: info: applying debian/gitignore.patch > dpkg-source: info: applying > debian/dfsg/arch-powerpc-platforms-8xx-ucode-disable.patch > [...] > dpkg-source: info: applying > bugfix/all/tools-perf-pmu-events-fix-reproducibility.patch > dpkg-source: info: applying > bugfix/all/bpftool-fix-version-string-in-recursive-builds.patch > dpkg-source: info: applying debian/overlayfs-permit-mounts-in-userns.patch > > Now you have in the current working directory the linux-5.10.149 directory. > > Did you process went that far? If so change into that directory where the > debian/ > directory which will include the debian/bin/test-patches to test-apply the > patches > we would like to test. > > If that will not help I will try to respin a build so anyone affected can test > > Hope this helps already, > > Regards, > Salvatore
Bug#1022025: fails to boot on machines with AMD integrated graphics
Hi Dan, On Wed, Oct 19, 2022 at 12:55:16PM +, Dan Coleman wrote: > Hi, > > I would love to, but I'm afraid I don't know how. If you or anyone on the > chain is willing to show me what commands to enter (I tried following this > https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html > but got as far as 4.2.2 and couldn't find a debian directory in the source > that I unpacked by following the prior instructions), I would be grateful. > > That said, I understand time and resources are limited, so no worries if > that's not possible! When you do fetch the source package the output will look like: # apt-get source linux Reading package lists... Done NOTICE: 'linux' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/kernel-team/linux.git Please use: git clone https://salsa.debian.org/kernel-team/linux.git to retrieve the latest (possibly unreleased) updates to the package. Need to get 124 MB of source archives. Get:1 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (dsc) [197 kB] Get:2 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (tar) [122 MB] Get:3 http://security.debian.org/debian-security bullseye-security/main linux 5.10.149-1 (diff) [1549 kB] Fetched 124 MB in 1s (95.7 MB/s) dpkg-source: info: extracting linux in linux-5.10.149 dpkg-source: info: unpacking linux_5.10.149.orig.tar.xz dpkg-source: info: unpacking linux_5.10.149-1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series dpkg-source: info: applying debian/gitignore.patch dpkg-source: info: applying debian/dfsg/arch-powerpc-platforms-8xx-ucode-disable.patch [...] dpkg-source: info: applying bugfix/all/tools-perf-pmu-events-fix-reproducibility.patch dpkg-source: info: applying bugfix/all/bpftool-fix-version-string-in-recursive-builds.patch dpkg-source: info: applying debian/overlayfs-permit-mounts-in-userns.patch Now you have in the current working directory the linux-5.10.149 directory. Did you process went that far? If so change into that directory where the debian/ directory which will include the debian/bin/test-patches to test-apply the patches we would like to test. If that will not help I will try to respin a build so anyone affected can test Hope this helps already, Regards, Salvatore
Bug#1022025: fails to boot on machines with AMD integrated graphics
Hi, I would love to, but I'm afraid I don't know how. If you or anyone on the chain is willing to show me what commands to enter (I tried following this https://www.debian.org/doc/manuals/debian-kernel-handbook/ch-common-tasks.html but got as far as 4.2.2 and couldn't find a debian directory in the source that I unpacked by following the prior instructions), I would be grateful. That said, I understand time and resources are limited, so no worries if that's not possible! Best, Dan On 10/19/22 07:35 AM, Salvatore Bonaccorso wrote: > Control: tags -1 + moreinfo > > Hi, > > On Wed, Oct 19, 2022 at 06:22:05AM +, Doublychargedhiggs wrote: >> Same problem here. Kernel version 5.10.149-1 (linux-image-5.10.0-19-amd64) >> hangs on initialisation of amdgpu >> driver, while version 5.10.140-1 (linux-image-5.10.0-18-amd64) boots without >> any problem. >> >> According to the changelogs on kernel.org there were several changes to >> amdgpu in versions >> 5.10.141, 5.10.143, 5.10.144 5.10.146 and 5.10.148. >> >> Some extract from my /var/log/messages just in case it is of any help: >> >> Oct 19 07:05:24 omikron kernel: [0.00] Linux version 5.10.0-19-amd64 >> (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, >> GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-1 >> (2022-10-17) >> Oct 19 07:05:24 omikron kernel: [0.00] Command line: >> BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 >> root=UUID=28af0276-7bd6-468f-b9c9-c743233a9468 ro quiet mem_encrypt=off >> snd_hda_intel.power_save=0 >> ... >> Oct 19 07:05:24 omikron kernel: [2.325914] [drm] amdgpu kernel >> modesetting enabled. >> Oct 19 07:05:24 omikron kernel: [2.327288] amdgpu: Topology: Add APU >> node [0x0:0x0] >> Oct 19 07:05:24 omikron kernel: [2.327398] fb0: switching to amdgpudrmfb >> from EFI VGA >> Oct 19 07:05:24 omikron kernel: [2.328120] Console: switching to colour >> dummy device 80x25 >> Oct 19 07:05:24 omikron kernel: [2.328366] amdgpu :05:00.0: vgaarb: >> deactivate vga console >> Oct 19 07:05:24 omikron kernel: [2.328431] amdgpu :05:00.0: enabling >> device (0006 -> 0007) >> Oct 19 07:05:24 omikron kernel: [2.328516] [drm] initializing kernel >> modesetting (RAVEN 0x1002:0x15DD 0x1002:0x15DD 0x83). >> Oct 19 07:05:24 omikron kernel: [2.328519] amdgpu :05:00.0: amdgpu: >> Trusted Memory Zone (TMZ) feature disabled as experimental (default) >> Oct 19 07:05:24 omikron kernel: [2.328536] [drm] register mmio base: >> 0xFE60 >> Oct 19 07:05:24 omikron kernel: [2.328537] [drm] register mmio size: >> 524288 >> Oct 19 07:05:24 omikron kernel: [2.328559] [drm] add ip block number 0 >> >> Oct 19 07:05:24 omikron kernel: [2.328561] [drm] add ip block number 1 >> >> Oct 19 07:05:24 omikron kernel: [2.328562] [drm] add ip block number 2 >> >> Oct 19 07:05:24 omikron kernel: [2.328564] [drm] add ip block number 3 >> >> Oct 19 07:05:24 omikron kernel: [2.328565] [drm] add ip block number 4 >> >> Oct 19 07:05:24 omikron kernel: [2.328567] [drm] add ip block number 5 >> >> Oct 19 07:05:24 omikron kernel: [2.328568] [drm] add ip block number 6 >> >> Oct 19 07:05:24 omikron kernel: [2.328570] [drm] add ip block number 7 >> >> Oct 19 07:05:24 omikron kernel: [2.328571] [drm] add ip block number 8 >> >> Oct 19 07:05:24 omikron kernel: [2.333054] input: HD-Audio Generic >> HDMI/DP,pcm=3 as >> /devices/pci:00/:00:08.1/:05:00.1/sound/card0/input6 >> Oct 19 07:05:24 omikron kernel: [2.334135] amdgpu :05:00.0: >> firmware: direct-loading firmware amdgpu/raven_gpu_info.bin >> Oct 19 07:05:24 omikron kernel: [2.334155] amdgpu :05:00.0: amdgpu: >> Fetched VBIOS from VFCT >> Oct 19 07:05:24 omikron kernel: [2.334157] amdgpu: ATOM BIOS: >> 113-RAVEN-113 >> Oct 19 07:05:24 omikron kernel: [2.334462] amdgpu :05:00.0: >> firmware: direct-loading firmware amdgpu/raven_sdma.bin >> Oct 19 07:05:24 omikron kernel: [2.334469] [drm] VCN decode is enabled >> in VM mode >> Oct 19 07:05:24 omikron kernel: [2.334470] [drm] VCN encode is enabled >> in VM mode >> Oct 19 07:05:24 omikron kernel: [2.334471] [drm] JPEG decode is enabled >> in VM mode >> Oct 19 07:05:24 omikron kernel: [2.334527] [drm] vm size is 262144 GB, 4 >> levels, block size is 9-bit, fragment size is 9-bit >> Oct 19 07:05:24 omikron kernel: [2.334539] amdgpu :05:00.0: amdgpu: >> VRAM: 2048M 0x00F4 - 0x00F47FFF (2048M used) >> Oct 19 07:05:24 omikron kernel: [2.334541] amdgpu :05:00.0: amdgpu: >> GART: 1024M 0x - 0x3FFF >> Oct 19 07:05:24 omikron kernel: [2.334543] amdgpu :05:00.0: amdgpu: >> AGP: 267419648M 0x00F8 - 0x >> Oct 19 07:05:24 omikron kernel: [2.334551] [drm] Detected VRAM >> RAM=2048M, BAR=2048M >> Oct 19 07:05:24 omikron kernel: [2.334552]
Bug#1022025: fails to boot on machines with AMD integrated graphics
Control: tags -1 + moreinfo Hi, On Wed, Oct 19, 2022 at 06:22:05AM +, Doublychargedhiggs wrote: > Same problem here. Kernel version 5.10.149-1 (linux-image-5.10.0-19-amd64) > hangs on initialisation of amdgpu > driver, while version 5.10.140-1 (linux-image-5.10.0-18-amd64) boots without > any problem. > > According to the changelogs on kernel.org there were several changes to > amdgpu in versions > 5.10.141, 5.10.143, 5.10.144 5.10.146 and 5.10.148. > > Some extract from my /var/log/messages just in case it is of any help: > > Oct 19 07:05:24 omikron kernel: [0.00] Linux version 5.10.0-19-amd64 > (debian-ker...@lists.debian.org) (gcc-10 (Debian 10.2.1-6) 10.2.1 20210110, > GNU ld (GNU Binutils for Debian) 2.35.2) #1 SMP Debian 5.10.149-1 (2022-10-17) > Oct 19 07:05:24 omikron kernel: [0.00] Command line: > BOOT_IMAGE=/boot/vmlinuz-5.10.0-19-amd64 > root=UUID=28af0276-7bd6-468f-b9c9-c743233a9468 ro quiet mem_encrypt=off > snd_hda_intel.power_save=0 > ... > Oct 19 07:05:24 omikron kernel: [2.325914] [drm] amdgpu kernel > modesetting enabled. > Oct 19 07:05:24 omikron kernel: [2.327288] amdgpu: Topology: Add APU node > [0x0:0x0] > Oct 19 07:05:24 omikron kernel: [2.327398] fb0: switching to amdgpudrmfb > from EFI VGA > Oct 19 07:05:24 omikron kernel: [2.328120] Console: switching to colour > dummy device 80x25 > Oct 19 07:05:24 omikron kernel: [2.328366] amdgpu :05:00.0: vgaarb: > deactivate vga console > Oct 19 07:05:24 omikron kernel: [2.328431] amdgpu :05:00.0: enabling > device (0006 -> 0007) > Oct 19 07:05:24 omikron kernel: [2.328516] [drm] initializing kernel > modesetting (RAVEN 0x1002:0x15DD 0x1002:0x15DD 0x83). > Oct 19 07:05:24 omikron kernel: [2.328519] amdgpu :05:00.0: amdgpu: > Trusted Memory Zone (TMZ) feature disabled as experimental (default) > Oct 19 07:05:24 omikron kernel: [2.328536] [drm] register mmio base: > 0xFE60 > Oct 19 07:05:24 omikron kernel: [2.328537] [drm] register mmio size: > 524288 > Oct 19 07:05:24 omikron kernel: [2.328559] [drm] add ip block number 0 > > Oct 19 07:05:24 omikron kernel: [2.328561] [drm] add ip block number 1 > > Oct 19 07:05:24 omikron kernel: [2.328562] [drm] add ip block number 2 > > Oct 19 07:05:24 omikron kernel: [2.328564] [drm] add ip block number 3 > > Oct 19 07:05:24 omikron kernel: [2.328565] [drm] add ip block number 4 > > Oct 19 07:05:24 omikron kernel: [2.328567] [drm] add ip block number 5 > > Oct 19 07:05:24 omikron kernel: [2.328568] [drm] add ip block number 6 > > Oct 19 07:05:24 omikron kernel: [2.328570] [drm] add ip block number 7 > > Oct 19 07:05:24 omikron kernel: [2.328571] [drm] add ip block number 8 > > Oct 19 07:05:24 omikron kernel: [2.333054] input: HD-Audio Generic > HDMI/DP,pcm=3 as > /devices/pci:00/:00:08.1/:05:00.1/sound/card0/input6 > Oct 19 07:05:24 omikron kernel: [2.334135] amdgpu :05:00.0: firmware: > direct-loading firmware amdgpu/raven_gpu_info.bin > Oct 19 07:05:24 omikron kernel: [2.334155] amdgpu :05:00.0: amdgpu: > Fetched VBIOS from VFCT > Oct 19 07:05:24 omikron kernel: [2.334157] amdgpu: ATOM BIOS: > 113-RAVEN-113 > Oct 19 07:05:24 omikron kernel: [2.334462] amdgpu :05:00.0: firmware: > direct-loading firmware amdgpu/raven_sdma.bin > Oct 19 07:05:24 omikron kernel: [2.334469] [drm] VCN decode is enabled in > VM mode > Oct 19 07:05:24 omikron kernel: [2.334470] [drm] VCN encode is enabled in > VM mode > Oct 19 07:05:24 omikron kernel: [2.334471] [drm] JPEG decode is enabled > in VM mode > Oct 19 07:05:24 omikron kernel: [2.334527] [drm] vm size is 262144 GB, 4 > levels, block size is 9-bit, fragment size is 9-bit > Oct 19 07:05:24 omikron kernel: [2.334539] amdgpu :05:00.0: amdgpu: > VRAM: 2048M 0x00F4 - 0x00F47FFF (2048M used) > Oct 19 07:05:24 omikron kernel: [2.334541] amdgpu :05:00.0: amdgpu: > GART: 1024M 0x - 0x3FFF > Oct 19 07:05:24 omikron kernel: [2.334543] amdgpu :05:00.0: amdgpu: > AGP: 267419648M 0x00F8 - 0x > Oct 19 07:05:24 omikron kernel: [2.334551] [drm] Detected VRAM RAM=2048M, > BAR=2048M > Oct 19 07:05:24 omikron kernel: [2.334552] [drm] RAM width 128bits DDR4 > Oct 19 07:05:24 omikron kernel: [2.334618] [TTM] Zone kernel: Available > graphics memory: 15381802 KiB > Oct 19 07:05:24 omikron kernel: [2.334620] [TTM] Zone dma32: Available > graphics memory: 2097152 KiB > Oct 19 07:05:24 omikron kernel: [2.334621] [TTM] Initializing pool > allocator > Oct 19 07:05:24 omikron kernel: [2.334626] [TTM] Initializing DMA pool > allocator > Oct 19 07:05:24 omikron kernel: [2.334738] [drm] amdgpu: 2048M of VRAM > memory ready > Oct 19 07:05:24 omikron kernel: [2.334741] [drm] amdgpu: 3072M of GTT > memory ready. > Oct 19 07:05:24 omikron
