Ah yes, here it is:
https://lore.kernel.org/lkml/CAK2bqVJo8TZUwu4-5VcY0MEezM7gJJq77prMpCB=fda24fe...@mail.gmail.com/
It looks like this warning started with the 5.14.x kernels.
Cheers,
Chris
Hi,
I have resurrected my old AMD R7 360 card (Bonnaire?) for a machine
that needed an upgrade, and now notice this warning in the dmesg log,
soon after logging into X. (In fact, this warning looks rather
familiar. I suspect I was already reporting it up until I removed this
R7 360 from my own mac
Hi,
I am trying to compile a Linux 5.15 kernel with the amdgpu driver for
a Radeon RX 6600. For reference, Fedora's 5.15.4-201.fc35.x86_64
kernel appears to work for me and be stable, and so I am confident
that my hardware is OK, even if my motherboard is quite old (PCIE 2.0,
I believe). However,
Alas no, other than to observe that the issue is not present in 5.13.15,
but is present in 5.14.3; i.e. the last 5.13.x and first 5.14.x kernels
that I compiled myself.
Cheers,
Chris
On Tue, 23 Nov 2021 at 20:14, Alex Deucher wrote:
> On Sun, Nov 21, 2021 at 9:47 AM Chris Rankin wr
Hi,
i have found this warning in my vanilla 5.15.4 kernel's dmesg log:
[ 87.687139] [ cut here ]
[ 87.710799] WARNING: CPU: 1 PID: 1 at
drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x1c/0x266 [ttm]
[ 87.718965] Modules linked in: nf_nat_ftp nf_conntrack_ftp cfg802
Hi.
I've already tried reporting this on the linux kernel list, without effect:
[ 95.796055] [ cut here ]
[ 95.819648] WARNING: CPU: 3 PID: 1 at
drivers/gpu/drm/ttm/ttm_bo.c:409 ttm_bo_release+0x1c/0x266 [ttm]
[ 95.827805] Modules linked in: nf_nat_ftp nf_conntrack_f
> On Thu, Dec 6, 2018 at 10:58 AM Chris Rankin wrote:
> >
> > Yes, all 4.19.x kernels have been fine without the amdgpu.dpm=1 kernel
> parameter. In fact, this is how I am running my kernel right now. With the
> 4.18.x series I did specify amdgpu.dpm=1 explicitly on the GRUB2 c
t; Alex
> On Thu, Dec 6, 2018 at 10:47 AM Alex Deucher
> wrote:
> >
> > I can't reproduce this. Can you bisect?
> >
> > Alex
> > On Thu, Dec 6, 2018 at 8:38 AM Chris Rankin wrote:
> > >
> > > Hi,
> > >
> > > I'
Hi,
I'm still unable to enable DPM with my R7 360, AMDGPU driver, Linux 4.19.7
kernel. Dmesg log is attached, showing that it is correctly using PCIE gen2
speeds.
Cheers,
Chris
On Sat, 24 Nov 2018 at 13:12, Chris Rankin wrote:
> Hi, thanks for the reply.
>
> That patch doesn&#x
at 20:25, Alex Deucher wrote:
> On Thu, Nov 22, 2018 at 7:23 PM Chris Rankin wrote:
> >
> > Hi,
> >
> > I have recently tried to use dpm=1 with the amdgpu driver for the 4.19.x
> kernel, but unfortunately the screen just went black. This is a regression
> fro
Hi,
I have recently tried to use dpm=1 with the amdgpu driver for the 4.19.x
kernel, but unfortunately the screen just went black. This is a regression
from the 4.18.x kernel.
I have attached the full dmesg log, but the relevant section look to be:
[8.958679] WARNING: CPU: 0 PID: 320 at driv
ff ff f7
[ 35.118587] f7 ff ff ff ff ff ff ff ff ff ff 02 02 ff ff ff
[ 35.167737] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 142
Signed-off-by: Chris Rankin
Cheers,
Chris
--- linux-3.5/drivers/gpu/drm/radeon/radeon_i2c.c.orig 2012-06-07 12:41:09.
ff f7
[ 35.118587] f7 ff ff ff ff ff ff ff ff ff ff 02 02 ff ff ff
[ 35.167737] [drm:drm_edid_block_valid] *ERROR* EDID checksum is
invalid, remainder is 142
Signed-off-by: Chris Rankin
Cheers,
Chris
-- next part --
A non-text attachment was scrubbed...
Hi,
My RV350 has just locked up while (presumably) running an OpenGL screensaver.
Here is the dmesg trace, in the hope that it might be useful:
radeon :01:00.0: GPU lockup CP stall for more than 1msec
[ cut here ]
radeon :01:00.0: GPU lockup CP stall for more
Hi,
My RV350 has just locked up while (presumably) running an OpenGL screensaver.
Here is the dmesg trace, in the hope that it might be useful:
radeon :01:00.0: GPU lockup CP stall for more than 1msec
[ cut here ]
radeon :01:00.0: GPU lockup CP stall for more
15 matches
Mail list logo
