Bug 208263 - flickering black lines on Mobility Radeon 7500 with kernel 5.x.x
Summary: flickering black lines on Mobility Radeon 7500 with kernel 5.x.x
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Video(AGP) (show other bugs)
Hardware: All Linux
: P1 normal
Assignee: Dave Airlie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-21 12:50 UTC by lebkoungcity
Modified: 2021-01-31 12:08 UTC (History)
1 user (show)

See Also:
Kernel Version: 5.x.x
Subsystem:
Regression: No
Bisected commit-id:


Attachments
bisect.log (4.21 KB, text/plain)
2020-06-21 12:53 UTC, lebkoungcity
Details
Photo of flickering black lines on screen. (318.30 KB, image/jpeg)
2020-06-21 12:55 UTC, lebkoungcity
Details
Xorg.0.log (30.70 KB, text/plain)
2020-06-21 12:56 UTC, lebkoungcity
Details
dmesg (47.68 KB, text/plain)
2020-06-21 12:57 UTC, lebkoungcity
Details
config-5.4.28-gentoo (122.87 KB, text/plain)
2020-06-21 12:58 UTC, lebkoungcity
Details
emerge --info (6.51 KB, text/plain)
2020-06-21 12:58 UTC, lebkoungcity
Details

Description lebkoungcity 2020-06-21 12:50:55 UTC
Hello,

unfortunatly I have to report a bug.

Distribution:
gentoo

Hardware:
IBM ThinkPad R40 with a 32bit Pentium-M
RV200/M7 [Mobility Radeon 7500]

Bug report on gentoo:
https://bugs.gentoo.org/717360



I have flickering black lines on X when booting the kernel I compiled from sys-kernel/gentoo-sources-5.4.28 and several following 5.x.x-kernels. No problems with sys-kernel/gentoo-sources-4.19.97.

When the problem persisted I did a bisect. Result is:

commit 33b3ad3788aba846fc8b9a065fe2685a0b64f713
Author: Christoph Hellwig <hch@lst.de>
Date:   Thu Aug 15 09:27:00 2019 +0200

    drm/radeon: handle PCIe root ports with addressing limitations
    
    radeon uses a need_dma32 flag to indicate to the drm core that some
    allocations need to be done using GFP_DMA32, but it only checks the
    device addressing capabilities to make that decision.  Unfortunately
    PCIe root ports that have limited addressing exist as well.  Use the
    dma_addressing_limited instead to also take those into account.
    
    Reviewed-by: Christian König <christian.koenig@amd.com>
    Reported-by: Atish Patra <Atish.Patra@wdc.com>
    Signed-off-by: Christoph Hellwig <hch@lst.de>
    Signed-off-by: Alex Deucher <alexander.deucher@amd.com>

 drivers/gpu/drm/radeon/radeon.h        |  1 -
 drivers/gpu/drm/radeon/radeon_device.c | 12 +++++-------
 drivers/gpu/drm/radeon/radeon_ttm.c    |  2 +-
 3 files changed, 6 insertions(+), 9 deletions(-)


I hope this is relevant and I provide sufficent information! Please let me know if there's more I can provide.
Comment 1 lebkoungcity 2020-06-21 12:53:08 UTC
Created attachment 289761 [details]
bisect.log
Comment 2 lebkoungcity 2020-06-21 12:55:32 UTC
Created attachment 289763 [details]
Photo of flickering black lines on screen.
Comment 3 lebkoungcity 2020-06-21 12:56:39 UTC
Created attachment 289765 [details]
Xorg.0.log
Comment 4 lebkoungcity 2020-06-21 12:57:30 UTC
Created attachment 289767 [details]
dmesg
Comment 5 lebkoungcity 2020-06-21 12:58:10 UTC
Created attachment 289769 [details]
config-5.4.28-gentoo
Comment 6 lebkoungcity 2020-06-21 12:58:51 UTC
Created attachment 289771 [details]
emerge --info
Comment 7 lebkoungcity 2020-07-12 10:52:23 UTC
Hello,

are there any news about this issue?
Is there anything I can do?

Thanks for your attention!
Comment 8 lebkoungcity 2020-08-09 17:57:41 UTC
Hello,

today I tried sys-kernel/gentoo-sources-5.8.0-r1 and the flickering is still there.

When I disable 'High Memory Support' the flickering does not happen. (I found that somewhere on the net.) But with 'High Memory Support' set to '4GB' it shows up. Unfortunately I need all of the installed 2GB RAM so I need to set 'High Memory Support' to '4GB'...

Is there anything I can do / provide?

Thanks a lot for your attention!
Comment 9 lebkoungcity 2021-01-31 12:08:03 UTC
Seems to be resolved.
Tried it again with sys-kernel/gentoo-sources-5.4.92 and nothing flickers.

Note You need to log in before you can comment on or make changes to this bug.