From: Mikhail Krylov <sqarert@gmail.com>
To: Alex Deucher <alexdeucher@gmail.com>
Cc: amd-gfx list <amd-gfx@lists.freedesktop.org>,
Maling list - DRI developers <dri-devel@lists.freedesktop.org>
Subject: Re: Screen corruption using radeon kernel driver
Date: Mon, 16 May 2022 16:01:58 +0300 [thread overview]
Message-ID: <YoJLRq69Kg1ljXUj@sqrt.uni.cx> (raw)
In-Reply-To: <CADnq5_PXgFBXZ03LXE8qOdimzfKYGhzX1JnycJQcHWcMZdgJug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2830 bytes --]
On Mon, Apr 25, 2022 at 01:22:04PM -0400, Alex Deucher wrote:
> + dri-devel
>
> On Mon, Apr 25, 2022 at 3:33 AM Krylov Michael <sqarert@gmail.com> wrote:
> >
> > Hello!
> >
> > After updating my Linux kernel from version 4.19 (Debian 10 version) to
> > 5.10 (packaged with Debian 11), I've noticed that the image
> > displayed on my older computer, 32-bit Pentium 4 using ATI Radeon X1950
> > AGP video card is severely corrupted in the graphical (Xorg and Wayland)
> > mode: all kinds of black and white stripes across the screen, some
> > letters missing, etc.
> >
> > I've checked several options (Xorg drivers, Wayland instead of
> > Xorg, radeon.agpmode=-1 in kernel command line and so on), but the
> > problem persisted. I've managed to find that the problem was in the
> > kernel, as everything worked well with 4.19 kernel with everything
> > else being from Debian 11.
> >
> > I have managed to find the culprit of that corruption, that is the
> > commit 33b3ad3788aba846fc8b9a065fe2685a0b64f713 on the linux kernel.
> > Reverting this commit and building the kernel with that commit reverted
> > fixes the problem. Disabling HIMEM also gets rid of that problem. But it
> > also leaves the system with less that 1G of RAM, which is, of course,
> > undesirable.
> >
> > Apparently this problem is somewhat known, as I can tell after googling
> > for the commit id, see this link for example:
> > https://lkml.org/lkml/2020/1/9/518
> >
> > Mageia distro, for example, reverted this commit in the kernel they are
> > building:
> >
> > http://sophie.zarb.org/distrib/Mageia/7/i586/by-pkgid/b9193a4f85192bc57f4d770fb9bb399c/files/32
> >
> > I've reported this bug to Debian bugtracker, checked the recent verion
> > of the kernel (5.17), bug still persists. Here's a link to the Debian
> > bug page:
> >
> > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=993670
> >
> > I'm not sure if reverting this commit is the correct way to go, so if
> > you need to check any changes/patches that I could apply and test on
> > the real hardware, I'll be glad to do that (but please keep in mind
> > that testing could take some time, I don't have access to this computer
> > 24/7, but I'll do my best to respond ASAP).
>
> I would be happy to revert that commit. I attempted to revert it a
> year or so ago, but Christoph didn't want to. He was going to look
> further into it. I was not able to repro the issue. It seemed to be
> related to highmem support. You might try disabling that. Here is
> the previous thread for reference:
> https://lists.freedesktop.org/archives/amd-gfx/2020-September/053922.html
>
> Alex
Yeah, I tried to disable HIMEM, and that indeed fixes the problem, but
it leaves me with less than 1G of available memory which is undesirable.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2022-05-16 13:03 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-23 16:31 Screen corruption using radeon kernel driver Krylov Michael
2022-04-25 17:22 ` Alex Deucher
2022-05-16 13:01 ` Mikhail Krylov [this message]
2022-11-28 14:31 ` Mikhail Krylov
2022-11-28 14:50 ` Alex Deucher
2022-11-28 20:48 ` Mikhail Krylov
2022-11-29 14:44 ` Alex Deucher
2022-11-29 15:59 ` Mikhail Krylov
2022-11-29 16:05 ` Alex Deucher
2022-11-29 17:11 ` Mikhail Krylov
2022-11-30 12:54 ` Robin Murphy
2022-11-30 14:28 ` Alex Deucher
2022-11-30 15:42 ` Robin Murphy
2022-11-30 16:07 ` Alex Deucher
2022-11-30 19:59 ` Mikhail Krylov
2022-12-01 14:00 ` Robin Murphy
2022-12-01 14:06 ` Alex Deucher
2022-12-01 15:28 ` Mikhail Krylov
2022-12-01 15:28 ` Mikhail Krylov
2022-12-10 15:32 ` Mikhail Krylov
2022-12-11 5:52 ` Luben Tuikov
2022-12-11 11:42 ` [PATCH] drm/radeon: Fix screen corruption Luben Tuikov
2022-12-12 2:08 ` [PATCH] drm/radeon: Fix screen corruption (v2) Luben Tuikov
2022-12-14 21:53 ` Robin Murphy
2022-12-14 22:02 ` Alex Deucher
2022-12-14 23:08 ` Robin Murphy
2022-12-15 8:07 ` Christian König
2022-12-15 9:08 ` Luben Tuikov
2022-12-15 9:46 ` Christian König
2022-12-15 10:19 ` Luben Tuikov
2022-12-15 11:27 ` Christian König
2022-12-15 11:40 ` Luben Tuikov
2022-12-15 11:53 ` Robin Murphy
2022-12-15 12:07 ` Luben Tuikov
2023-01-19 16:56 ` Krylov Michael
2023-01-19 16:56 ` Krylov Michael
2023-01-20 4:31 ` Luben Tuikov
2023-01-20 4:31 ` Luben Tuikov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YoJLRq69Kg1ljXUj@sqrt.uni.cx \
--to=sqarert@gmail.com \
--cc=alexdeucher@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.