https://bugs.freedesktop.org/show_bug.cgi?id=99353
Vedran Miletić changed:
What|Removed |Added
Resolution|WORKSFORME |FIXED
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bong Cosca changed:
What|Removed |Added
Resolution|--- |WORKSFORME
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #51 from Alex Deucher ---
(In reply to Bong Cosca from comment #48)
> Created attachment 137740 [details] [review]
> kaveri.patch
>
> Alex, the patch you suggested overrides the cu_per_sh and backends_per_se
>
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #52 from Alex Deucher ---
(In reply to Bong Cosca from comment #50)
> Will we see this patch/commit on the stable kernel too?
Yes, I will CC stable.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #50 from Bong Cosca ---
Will we see this patch/commit on the stable kernel too?
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #49 from Bong Cosca ---
I have no objection to the patch you recommended since it works for me. You
would be the better resource person on this subject matter. Hoping this gets to
the mainline asap.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #48 from Bong Cosca ---
Created attachment 137740
--> https://bugs.freedesktop.org/attachment.cgi?id=137740=edit
kaveri.patch
Alex, the patch you suggested overrides the cu_per_sh and backends_per_se for
ALL
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #47 from Alex Deucher ---
Created attachment 137722
--> https://bugs.freedesktop.org/attachment.cgi?id=137722=edit
possible fix for amdgpu
Same patch for amdgpu as well for anyone using that.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #46 from Alex Deucher ---
Created attachment 137721
--> https://bugs.freedesktop.org/attachment.cgi?id=137721=edit
possible fix for radeon
Does this kernel patch fix it?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Michel Dänzer changed:
What|Removed |Added
Product|Mesa|DRI
QA
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bong Cosca changed:
What|Removed |Added
Priority|medium |highest
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #44 from Bong Cosca ---
This bug has been on this tracker for more than a year and it now has a
proposed working solution. What's the hold up? Don't we even get the courtesy
of a response?
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #43 from Bong Cosca ---
Created attachment 137682
--> https://bugs.freedesktop.org/attachment.cgi?id=137682=edit
radeonsi: force si_write_harvested_raster_configs when we fail to determine
enabled backends
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #42 from Bong Cosca ---
Created attachment 137550
--> https://bugs.freedesktop.org/attachment.cgi?id=137550=edit
radeonsi: force si_write_harvested_raster_configs
Here's what finally worked.
Force the call
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #41 from Bong Cosca ---
cik.c reports the following in cik_setup_rb():
max_rb_num_per_se: 1
enabled_rbs: 0
disabled_rbs: 1
mask: 2
se_num: 1
sh_per_se: 1
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #40 from Bong Cosca ---
I'm afraid forcing si_write_harvested_raster_configs() doesn't help any. We're
back to the old tiled garbage.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #39 from Bong Cosca ---
Created attachment 137521
--> https://bugs.freedesktop.org/attachment.cgi?id=137521=edit
dmesg
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #38 from Alex Deucher ---
Does forcing si_write_harvested_raster_configs() in si_state.c help?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #37 from Alex Deucher ---
(In reply to Bong Cosca from comment #36)
> Mesa 18.1 shows no problems with this patch. Are we going to see this code
> change in the mainstream anytime soon?
That will break other
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #36 from Bong Cosca ---
Mesa 18.1 shows no problems with this patch. Are we going to see this code
change in the mainstream anytime soon?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #35 from Bong Cosca ---
Created attachment 137448
--> https://bugs.freedesktop.org/attachment.cgi?id=137448=edit
Proposed patch
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #34 from Bong Cosca ---
@Michel, are there any impediments in getting this patch merged with mesa-git?
I tried this with both 17.3.3 and 17.3.4 without any side effects.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #33 from Bong Cosca ---
Wine works perfect with above change.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel mailing list
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #32 from Bong Cosca ---
Piglit results improved with only 70 fails, after stopping at 23705 tests.
This also works:
raster_config = 0x000f;
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #31 from Bong Cosca ---
This fixes the problem for me:
case CHIP_KAVERI:
/* KV should be 0x0002, but that causes problems with
radeon */
raster_config = 0x0003;
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bong Cosca changed:
What|Removed |Added
Product|DRI |Mesa
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #30 from Bong Cosca ---
Created attachment 137374
--> https://bugs.freedesktop.org/attachment.cgi?id=137374=edit
Gnome desktop
The situation has improved somehow - but screen is still unusable. I tried to
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #29 from Michel Dänzer ---
(In reply to Bong Cosca from comment #28)
> [drm:radeon_crtc_handle_flip [radeon]] radeon_crtc->flip_status = 0 !=
> RADEON_FLIP_SUBMITTED(2)
This is harmless and not related to the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #28 from Bong Cosca ---
I find this message particularly interesting because it occurs several times in
the dmesg log:
[drm:radeon_crtc_handle_flip [radeon]] radeon_crtc->flip_status = 0 !=
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #27 from Bong Cosca ---
Created attachment 137313
--> https://bugs.freedesktop.org/attachment.cgi?id=137313=edit
drm.debug=0x1e
Output generated by: dmesg | grep drm
Additional trace log to aid perhaps in
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #26 from Bong Cosca ---
(In reply to Michel Dänzer from comment #25)
>
> Where do you see that?
Xorg.0.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #25 from Michel Dänzer ---
(In reply to Bong Cosca from comment #24)
> My screen width is 1280px. Is there a reason why the amdgpu driver says the
> GPU has a front buffer pitch of 6144 bytes in non-accelerated
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #24 from Bong Cosca ---
My screen width is 1280px. Is there a reason why the amdgpu driver says the GPU
has a front buffer pitch of 6144 bytes in non-accelerated mode while the pitch
in accelerated mode is 5120?
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #23 from Bong Cosca ---
Created attachment 137183
--> https://bugs.freedesktop.org/attachment.cgi?id=137183=edit
Video BIOS
Attached video BIOS may also prove useful in isolating this bug in the graphics
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bong Cosca changed:
What|Removed |Added
QA Contact|dri-devel@lists.freedesktop |
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bong Cosca changed:
What|Removed |Added
Version|17.1|17.3
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #22 from Bong Cosca ---
Created attachment 137014
--> https://bugs.freedesktop.org/attachment.cgi?id=137014=edit
umr -c
Here's the output generated from `umr -c` in case it provides anything useful.
Again I
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #21 from Bong Cosca ---
Created attachment 137013
--> https://bugs.freedesktop.org/attachment.cgi?id=137013=edit
glxgears -info
Thanks for responding, Michel. Here's the output of `glxgears -info` that I
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #20 from Michel Dänzer ---
(In reply to Bong Cosca from comment #19)
> If I may add, compositing works by setting DRI_PRIME=1 with KMS and
> AccelMethod "none" despite having only the APU.
AccelMethod "none"
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #19 from Bong Cosca ---
If I may add, compositing works by setting DRI_PRIME=1 with KMS and AccelMethod
"none" despite having only the APU.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #18 from Bong Cosca ---
The only saving grace with all this display corruption is that there's a mouse
cursor when I use amdgpu with 2D acceleration disabled.
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #17 from Bong Cosca ---
Disabling hardware acceleration isn't exactly the workaround I was looking for.
I use modesetting with "AccelMethod" "none" just to make this work and I am
forced to use Win10 to do 3D
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #16 from Vedran Miletić ---
(In reply to Bong Cosca from comment #14)
> I have the same setup and I'm experiencing the same symptoms. 7400K on Asus
> A68HM-K with VGA/DVI-D output on ArchLinux 4.14.12 Xorg 1.19.6,
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #15 from Bong Cosca ---
[39409/39409] skip: 2874, pass: 15671, warn: 12, fail: 20845, crash: 7
Piglit results haven't changed much since, but notably with more crashes.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #14 from Bong Cosca ---
I have the same setup and I'm experiencing the same symptoms. 7400K on Asus
A68HM-K with VGA/DVI-D output on ArchLinux 4.14.12 Xorg 1.19.6, colored noise
(sometimes tiled garbage). I
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #13 from Vedran Miletić ---
Kernel 4.12.4-300.fc26.x86_64, no change. Should I try AMDGPU-PRO? What kind of
action would be useful next?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #12 from Vedran Miletić ---
Interestingly enough, not exactly the same result, amdgpu again:
[39371/39371] skip: 3231, pass: 15458, warn: 13, fail: 20668, crash: 1
Then on the next try:
[39371/39371] skip:
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #11 from Vedran Miletić ---
dmesg with radeon:
[ 1443.752932] show_signal_msg: 8 callbacks suppressed
[ 1443.752936] glslparsertest[31344]: segfault at 20 ip 7f10f2a45a25 sp
7ffd7c7b4ea0 error 4 in
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #10 from Vedran Miletić ---
Fedora does not enable AMDGPU CIK, but I rebuilt the kernel manually. Same
story with Xorg/Wayland with the amdgpu kernel driver.
As for piglit, managed to run till the end this time
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #9 from Vedran Miletić ---
(In reply to Michel Dänzer from comment #8)
> (In reply to Vedran Miletić from comment #6)
> > $ PIGLIT_PLATFORM=gbm ./piglit run quick results/quick
> > hang at
>
> Does it always hang
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #8 from Michel Dänzer ---
(In reply to Vedran Miletić from comment #6)
> $ PIGLIT_PLATFORM=gbm ./piglit run quick results/quick
> hang at
Does it always hang at the same test? If so, can you find out which test
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #7 from Vedran Miletić ---
Created attachment 132565
--> https://bugs.freedesktop.org/attachment.cgi?id=132565=edit
dmesg during piglit testing
Quite a number of errors, but they could be a separate problem as
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Vedran Miletić changed:
What|Removed |Added
Severity|normal |major
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #6 from Vedran Miletić ---
Created attachment 132564
--> https://bugs.freedesktop.org/attachment.cgi?id=132564=edit
Piglit test results
$ PIGLIT_PLATFORM=gbm ./piglit run quick results/quick
hang at
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #5 from Vedran Miletić ---
Few more random details:
1) monitor is attached via VGA, the only output on the motherboard
2) different monitors show the same behaviour
3) GDM vs SDDM, no difference
4) in both GDM and
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #4 from Vedran Miletić ---
dmesg doesn't show anything suspicious:
[1.526705] [drm] radeon kernel modesetting enabled.
[1.537819] fb: switching to radeondrmfb from EFI VGA
[1.538312] radeon
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #3 from Vedran Miletić ---
Created attachment 132559
--> https://bugs.freedesktop.org/attachment.cgi?id=132559=edit
Xorg.log
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #2 from Vedran Miletić ---
Michel, I missed this reply, sorry! I will test ASAP.
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=99353
--- Comment #1 from Michel Dänzer ---
Please attach the dmesg output and maybe Xorg log file corresponding to the
problem.
You could try running some piglit tests PIGLIT_PLATFORM=gbm . That could help
us narrow down if the problem is with the
https://bugs.freedesktop.org/show_bug.cgi?id=99353
Bug ID: 99353
Summary: Kaveri 7400K shows random colored noise instead of GUI
in X or Wayland
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
60 matches
Mail list logo