Created attachment 632732 [details]
Photo of flickering black lines on screen.
I have flickering black lines on X when booting the kernel I compiled from sys-kernel/gentoo-sources-5.4.28. No problems with sys-kernel/gentoo-sources-4.19.97.
I re-compiled the kernel three times, the last one after 'make clean', 'make mrproper and 'make distclean' and re-creating .config from the working '4.19.97' with 'make oldconfig'.
ThinkPad R40 with RV200/M7 [Mobility Radeon 7500]
in make.conf: VIDEO_CARDS="radeon r100"
- picture of screen with flickering fine black lines
- config (5.4.28-gentoo)
- emerge --info
Created attachment 632734 [details]
Created attachment 632736 [details]
Created attachment 632738 [details]
Thanks for your attention!
Why do you think this is a gentoo related bug?
Created attachment 633274 [details]
Forgot to add emerge --info, now added.
(In reply to Jonas Stein from comment #5)
> Why do you think this is a gentoo related bug?
I searched the net for problems like this but found only topics that are either several years old and/or have other impacts.
Maybe I just didn't find related postings? Then I'd be sorry for opening this bug...
In the meantime I have also tried sys-kernel/gentoo-sources-5.6.3 and the result is the same - flickering black lines.
Standard steps here:
Try the latest vanilla-sources 5.6.X kernel and see if it's there.
You can also try the latest vanilla-sources 5.4.X kernel (latest)
If the problem still exists, find the last working kernel and first non-working kernel and attempt a git bisect.
It's a little tedious, but it does sometimes identify an offending commit.
Thanks a lot for your suggestion.
By coincidence I did start that last weekend and now I have the results. (I followed these instructions: https://wiki.gentoo.org/wiki/Kernel_git-bisect )
I add the log as attachment and it seems this is the commit in question:
Author: Christoph Hellwig <email@example.com>
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 <firstname.lastname@example.org>
Reported-by: Atish Patra <Atish.Patra@wdc.com>
Signed-off-by: Christoph Hellwig <email@example.com>
Signed-off-by: Alex Deucher <firstname.lastname@example.org>
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(-)
Created attachment 640964 [details]
Now that there is the result of the bisect - What to do next? Where should I take it/report it?
Thanks a lot! :)
(In reply to lebkoungcity from comment #11)
> Now that there is the result of the bisect - What to do next? Where should I
> take it/report it?
> Thanks a lot! :)
This might be the best place --> https://bugzilla.kernel.org/
I reported it here: https://bugzilla.kernel.org/show_bug.cgi?id=208263 weeks ago but there was never any reaction to this. (And today I updated it, see below.) Is there any other place to put it?
Anyway, 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'...