https://bugs.freedesktop.org/show_bug.cgi?id=98784
Michel Dänzer changed:
What|Removed |Added
Resolution|--- |NOTOURBUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=91880
--- Comment #145 from Harald Judt ---
You are certainly right and the files differ, so I assume it could be a problem
with the firmware. But since amdgpu works fine for me now, I will simply use
this and bother no longer.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #7 from Michel Dänzer ---
Please attach the dmesg output, preferably captured after the problem occurred.
(In reply to Vedran MiletiÄ from comment #6)
> Jan 10 17:44:30 localhost.localdomain gnome-shell[22110]: Failed to flip:
>
https://bugs.freedesktop.org/show_bug.cgi?id=99323
--- Comment #8 from kartik ---
First I Have explicitly set radeon.dpm = 1 which did not solve the problem.
Then I have explicitly set radeon.dpm = 1 and forced High performance mode. It
did not solve the problem either.
Then finally I did not
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #15 from Michel Dänzer ---
For any commits that you can't test, run
git bisect skip
Eventually, git bisect will either show the commit which introduced the
problem, or the minimal set of candidates.
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=99143
--- Comment #6 from Harald Judt ---
Hi, sorry for not reporting earlier, but the holidays and lack of time...
I will test this and also the reverting patch send to the mailing list tonight
and verify that it helps.
--
You are receiving this
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=99323
--- Comment #7 from kartik ---
Created attachment 128886
--> https://bugs.freedesktop.org/attachment.cgi?id=128886=edit
Without explictly setting dpm and without curruption
forced high performance mode
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=99323
--- Comment #6 from kartik ---
Created attachment 128885
--> https://bugs.freedesktop.org/attachment.cgi?id=128885=edit
explicit dmesg without forcing
--
You are receiving this mail because:
You are the assignee for the bug.
--
https://bugs.freedesktop.org/show_bug.cgi?id=99323
--- Comment #5 from kartik ---
Created attachment 128884
--> https://bugs.freedesktop.org/attachment.cgi?id=128884=edit
explicit dmesg setting with curruption
--
You are receiving this mail because:
You are the assignee for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=98856
--- Comment #5 from Gregor Münch ---
(In reply to Samuel Pitoiset from comment #3)
> Does reverting that commit fix the issue?
I can't test (I would do if someone could show me how). I do weekly Mesa builds
and Im quite sure it broke in the
https://bugs.freedesktop.org/show_bug.cgi?id=98856
--- Comment #4 from Gregor Münch ---
I managed to get a trace. Hope it works for you.
https://drive.google.com/open?id=0B5KUmMDAwP-iUFNDdEpkd2xUMXc
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=97338
--- Comment #7 from Samuel Pitoiset ---
People might be interested by
https://github.com/virtual-programming/specops-linux/issues/20
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
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
https://bugs.freedesktop.org/show_bug.cgi?id=99352
Bug ID: 99352
Summary: DRM/IMX first primary plane with pixel format
DRM_FORMAT_YUV420 the screen is discolored
Product: DRI
Version: DRI git
Hardware: ARM
https://bugs.freedesktop.org/show_bug.cgi?id=98984
--- Comment #10 from randomsalad at gmail.com ---
(In reply to Samuel Pitoiset from comment #8)
> Thanks for confirming.
>
> This has probably been fixed in LLVM between 3.9.1 and 4.0.0.
This I can confirm.
OpenGL renderer string: Gallium 0.4
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #14 from Vitaly Ostrosablin ---
85a3057f651a1c56348f1af18343d9cc0a5c93f3 used to work fine.
After that, in at most 3 commits to future from this point something was broken
and mesa didn't run (checked on
https://bugs.freedesktop.org/show_bug.cgi?id=99350
Bug ID: 99350
Summary: libdrm-2.4.74/xf86drmMode.c:904:15: warning:
dereferencing type-punned pointer will break
strict-aliasing rules [-Wstrict-aliasing]
Product: DRI
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #13 from Ilia Mirkin ---
Vitaly - commit id's please. Dates are largely meaningless - the default date
shown by git has little to do with when the commit made it into a particular
tree, even with mesa's rebase policy.
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=99349
--- Comment #1 from Enver Balalic ---
With the R600_DEBUG=sbsafemath flag the game starts, it still spams the console
with the error. The skybox is not being rendered and an box of pink flickers on
the screen
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=99349
Bug ID: 99349
Summary: Failed to build shader (translation from TGSI)
Product: Mesa
Version: 13.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #12 from Vitaly Ostrosablin ---
Looks like it broke on Dec 07. There was a lot of radeonsi-related commits, but
I had difficulty compiling a working mesa out of them. On Dec 6, there was no
bug. No commits on Dec 7 seems to work,
https://bugs.freedesktop.org/show_bug.cgi?id=97879
--- Comment #50 from Marek Olšák ---
It would be useful to have a debug build of the game and run it with a profiler
or debugger to see where it's looping.
--
You are receiving this mail because:
You are on the CC list for the bug.
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #6 from Vedran MiletiÄ ---
Got it, thanks Ernst:
Jan 10 17:44:30 localhost.localdomain gnome-shell[22110]: Failed to flip:
Invalid argument
I also got the following in dmesg, but it's likely unrelated as I get it with
Xorg as
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #5 from Vedran MiletiÄ ---
(In reply to Ernst Sjöstrand from comment #3)
> I happen to have 2 4K monitors and a Fury as well actually.
>
> I actually couldn't run Wayland at all for some time, perhaps it was fixed
> by:
> mutter
https://bugs.freedesktop.org/show_bug.cgi?id=99343
Bug ID: 99343
Summary: dEQP-GLES31.functional.shaders.builtin_functions.preci
sion.{min,max}.highp_compute.scalar failures
Product: Mesa
Version: git
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=99143
--- Comment #5 from Michel Dänzer ---
Please attach the dmesg output and Xorg log file corresponding to the problem.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=98984
--- Comment #9 from Ernst Sjöstrand ---
Ah, I'm using the padoka ppa which has llvm 4.0 snapshots,
I must have been on 1:4.0~svn291444-0~x~padoka0
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=99143
--- Comment #4 from Jacky Hu ---
I reverted both a1f49cc179ce and 7c83d7abc999, the hardware cursor is back
working.
Obviously 7c83d7abc999 is wrong, and a1f49cc179ce is doubling it.
--
You are receiving this mail because:
You are the
https://bugs.freedesktop.org/show_bug.cgi?id=98856
--- Comment #3 from Samuel Pitoiset ---
Does reverting that commit fix the issue?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=98984
--- Comment #8 from Samuel Pitoiset ---
Thanks for confirming.
This has probably been fixed in LLVM between 3.9.1 and 4.0.0.
Ernst, which version of LLVM are you using?
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=98984
--- Comment #7 from José Suárez ---
Sorry, I forgot to add that the mesa and llvm packages come from the oibaf ppa.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=98984
--- Comment #6 from José Suárez ---
For me it was still reproducible with mesa as of 5 January. See the following
screenshots:
http://steamcommunity.com/sharedfiles/filedetails/?id=837496648
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #49 from Kelly Anderson ---
(In reply to Kelly Anderson from comment #43)
> Amdgpu eems to be fixed since my last testing!
>
> Kernel 4.9.1
> Mesa 13.0.3
> LibDrm 2.4.74
I spoke too soon...it's black screening as per usual. Maybe
https://bugs.freedesktop.org/show_bug.cgi?id=97879
--- Comment #49 from iuno at posteo.net ---
(In reply to Jani Kärkkäinen from comment #48)
> Using AMDGPU-PRO the hangs are non-existent. So there must be SOMETHING in
> the whole mesa-driver stack, that causes the hangs, if not the GL drivers
https://bugs.freedesktop.org/show_bug.cgi?id=98743
--- Comment #8 from piejacker875 at gmail.com ---
I did experience that icon bug last week week but it is fixed now, and I was
not having issues in Verdun during that time.
--
You are receiving this mail because:
You are the assignee for the
https://bugs.freedesktop.org/show_bug.cgi?id=98984
--- Comment #5 from Ernst Sjöstrand ---
Can't reproduce with Fiji, drm-next-4.10 and mesa
13.0-branchpoint-2089-g230b756
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=99078
calexil at yahoo.com changed:
What|Removed |Added
CC||calexil at yahoo.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=98984
--- Comment #4 from randomsalad at gmail.com ---
OpenGL renderer string: Gallium 0.4 on AMD HAWAII (DRM 3.8.0 / 4.9.0, LLVM
3.9.1)
OpenGL version string: 3.0 Mesa 17.0.0-devel (git-8bc39e251b)
Bug is still there as of git-8bc39e251b.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=98897
--- Comment #24 from Paul Gier ---
The patch in comment 22 works for me.
Running Fedora 24 with 4.8.16 kernel. MacBookPro11,5.
Fedora Copr repo available here:
https://copr.fedorainfracloud.org/coprs/pgier/macbook-kernel/
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #4 from Ernst Sjöstrand ---
Wait, actually after some DPMS and
[ 4378.466823] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR* clock
recovery tried 5 times
[ 4378.466834] [drm:amdgpu_atombios_dp_link_train [amdgpu]] *ERROR*
https://bugs.freedesktop.org/show_bug.cgi?id=98856
--- Comment #2 from Gregor Münch ---
I tried getting this to work but I dont get any output file.
DEBUGGER="apitrace trace" steam steam://rungameid/201700
What am Im doing wrong here?
I installed:
apitrace
lib32-apitrace
If you want to do a
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #48 from cyrwyn ---
Created attachment 128841
--> https://bugs.freedesktop.org/attachment.cgi?id=128841=edit
latest xorg.conf file for amdgpu
The xorg.conf renamed .new so it won't work. Created by XFdrake.
--
You are receiving
https://bugs.freedesktop.org/show_bug.cgi?id=98856
Gregor Münch changed:
What|Removed |Added
Summary|Dirt: Showdown broken |[Regression, SI] DIRT:
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #47 from cyrwyn ---
Created attachment 128840
--> https://bugs.freedesktop.org/attachment.cgi?id=128840=edit
xorg log after trying to boot with amdgpu enabled
Tried booting using new 4.8.16 kernel. Back to blank screen.
--
You
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #3 from Ernst Sjöstrand ---
I happen to have 2 4K monitors and a Fury as well actually.
I actually couldn't run Wayland at all for some time, perhaps it was fixed by:
mutter (3.22.2-3) unstable; urgency=medium
[ Jeremy Bicha ]
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #11 from Vitaly Ostrosablin ---
Further narrowed date range: between Dec 6 and Dec 12.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #10 from Vitaly Ostrosablin ---
Yes, will try to bisect mesa. Unfortunately, in looks like I'll have to do that
manually, since Gentoo doesn't seem to have bisect tools for portage. So far I
can say following initial info:
1) Bug
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #2 from Vedran MiletiÄ ---
(In reply to Ernst Sjöstrand from comment #1)
> Which exact version is that of gnome-shell and mutter?
gnome-shell-3.22.2-2.fc25.x86_64
mutter-3.22.2-3.fc25.x86_64
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=99312
Vedran MiletiÄ changed:
What|Removed |Added
Summary|Long-running OpenCL kernels |Long-running OpenCL kernels
https://bugs.freedesktop.org/show_bug.cgi?id=99330
--- Comment #1 from Ernst Sjöstrand ---
Which exact version is that of gnome-shell and mutter?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #46 from Patrick Laurin ---
Heh, nan, EUSERDRUNKONFLOOR error usually rotates both ways and displays
some blurring effects!
I'm not near the machine having this behaviour i'll give feed back asap on
this.
On 9 January 2017 at 10:18,
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #45 from Tom St Denis ---
Just to rule out the low hanging fruit. There was no celebratory champagne
involved in the screen rotation issues right? :-) (EUSERDRUNKONFLOOR error
happens from time to time)
What does xrandr report
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #44 from Patrick Laurin ---
I confirm I didn't get the black screen after more than 20 minutes while
trying kernel 4.10. This is GREAT new !!!
But, My screen was rotating by itself in a random manner, after a couple of
minutes.
https://bugs.freedesktop.org/show_bug.cgi?id=99330
Bug ID: 99330
Summary: Severe flickering with Fiji on Wayland
Product: Mesa
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=99323
--- Comment #4 from Alex Deucher ---
Please attach your dmesg output with radeon.dpm=1 explicitly set.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=99236
--- Comment #9 from Michel Dänzer ---
Any chance you can bisect Mesa?
(In reply to Vitaly Ostrosablin from comment #8)
> But if that's mesa-only bug, shouldn't Ctrl+Alt+F1 work? Here GPU appears to
> have stopped output completely (most
https://bugs.freedesktop.org/show_bug.cgi?id=97879
--- Comment #48 from Jani Kärkkäinen ---
Using AMDGPU-PRO the hangs are non-existent. So there must be SOMETHING in the
whole mesa-driver stack, that causes the hangs, if not the GL drivers
themselves.
--
You are receiving this mail because:
https://bugs.freedesktop.org/show_bug.cgi?id=95306
--- Comment #43 from Kelly Anderson ---
Amdgpu eems to be fixed since my last testing!
Kernel 4.9.1
Mesa 13.0.3
LibDrm 2.4.74
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=95206
--- Comment #19 from mrj at advancedcontrols.com.au ---
Alex, I've created Bug 99326.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=99326
Bug ID: 99326
Summary: Boot problem and White
dots/noise/speckling/shimmering/corruption on Radeon
HD6320
Product: DRI
Version: unspecified
Hardware:
https://bugs.freedesktop.org/show_bug.cgi?id=99310
--- Comment #1 from Michel Dänzer ---
Could be bug 99078.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=98743
--- Comment #7 from Michel Dänzer ---
Could be bug 99078. Maybe this only happens with LLVM 3.9.1, not current LLVM
SVN/Git.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=99323
Michel Dänzer changed:
What|Removed |Added
Assignee|xorg-driver-ati at lists.x.org |dri-devel at
lists.freedesktop
https://bugs.freedesktop.org/show_bug.cgi?id=98897
--- Comment #23 from Tyler Hampton ---
Running this patch on Linux kernel version 4.9.1 fixes the problem for me.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML
https://bugs.freedesktop.org/show_bug.cgi?id=74335
Christian König changed:
What|Removed |Added
Status|RESOLVED|CLOSED
--
You are receiving this
https://bugs.freedesktop.org/show_bug.cgi?id=74335
Christian König changed:
What|Removed |Added
Status|REOPENED|RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=97861
--- Comment #3 from Gregor Münch ---
I have the same problem. Purple Line on left side and overall blurry screen.
When Audio off, the issues go away.
AMDGPU 1.20
Kernel 4.10 RC2
Radeon HD 7970
--
You are receiving this mail because:
You are
https://bugs.freedesktop.org/show_bug.cgi?id=74335
--- Comment #10 from Andy Furniss ---
That looks normal, I have that sample and it's 1444 frames / 60Hz = 24 seconds.
You can't really turn off vsync for vdpau and mplayer doesn't do gl interop.
Cpu times can mislead if cpufreq on_demand is in
https://bugs.freedesktop.org/show_bug.cgi?id=99321
Vlad changed:
What|Removed |Added
Summary|Videoplaying applications |Videoplaying applications
https://bugs.freedesktop.org/show_bug.cgi?id=99321
Bug ID: 99321
Summary: Videoplaying applications hangs on latest r600
Product: Mesa
Version: 13.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=98743
--- Comment #6 from piejacker875 at gmail.com ---
I'm running mesa 13.0.3-1 and llvm 3.9.1-2 on Arch. R9 390.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment
https://bugs.freedesktop.org/show_bug.cgi?id=96600
--- Comment #12 from Vladimir Usikov ---
No more artifacts in this video on mesa-git 1d529cba02
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was
https://bugs.freedesktop.org/show_bug.cgi?id=74335
--- Comment #9 from Vladimir Usikov ---
mplayer -benchmark -nosound -lavdopts threads=16
Planet_Earth_From_Pole_to_Pole_1080p_sample.mkv -vo gl
BENCHMARKs: VC: 0.827s VO: 22.917s A: 0.000s Sys: 0.494s = 24.238s
BENCHMARK%: VC:
https://bugs.freedesktop.org/show_bug.cgi?id=99316
--- Comment #6 from Samuel Anderson ---
Created attachment 128812
--> https://bugs.freedesktop.org/attachment.cgi?id=128812=edit
kernel panic
I get these sometimes when I reboot after testing the card. Usually after
testing it with something
https://bugs.freedesktop.org/show_bug.cgi?id=99316
--- Comment #5 from Samuel Anderson ---
Created attachment 128811
--> https://bugs.freedesktop.org/attachment.cgi?id=128811=edit
hwinfo
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=99316
--- Comment #4 from Samuel Anderson ---
It has no effect.
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment was scrubbed...
URL:
https://bugs.freedesktop.org/show_bug.cgi?id=99309
Arek RuÅniak changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=99309
--- Comment #3 from Arek RuÅniak ---
ok, after commit "Revert recent GLSL slot counting fiasco" this raport should
disappear
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An
https://bugs.freedesktop.org/show_bug.cgi?id=99311
Kai changed:
What|Removed |Added
Component|Drivers/Gallium/radeonsi|Mesa core
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=99261
Alex Deucher changed:
What|Removed |Added
Resolution|--- |NOTABUG
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=99316
--- Comment #3 from Alex Deucher ---
Possibly a duplicate of bug 98897. Does attachment 128780 fix the issue?
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part --
An HTML attachment
https://bugs.freedesktop.org/show_bug.cgi?id=99316
--- Comment #2 from Samuel Anderson ---
Created attachment 128809
--> https://bugs.freedesktop.org/attachment.cgi?id=128809=edit
AC Power glxgears
The last part of the log, 121 onward is the second failed attempt for glxgears.
The previous
https://bugs.freedesktop.org/show_bug.cgi?id=99309
--- Comment #2 from Edmondo Tommasina ---
Same here. After updating to mesa-git Chromium with gpu acceleration shows only
garbage.
OpenGL renderer string: Gallium 0.4 on AMD POLARIS10 (DRM 3.8.0 / 4.9.0-gentoo,
LLVM 3.9.0)
--
You are
https://bugs.freedesktop.org/show_bug.cgi?id=99316
Samuel Anderson changed:
What|Removed |Added
CC||LordSamanon at gmail.com
--- Comment
https://bugs.freedesktop.org/show_bug.cgi?id=99316
Bug ID: 99316
Summary: Radeon crash when laptop on AC power
Product: DRI
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: major
https://bugs.freedesktop.org/show_bug.cgi?id=80419
Marek Olšák changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=80419
--- Comment #150 from ArneJ ---
I also suffered a lot from this issue on my R9 270X.
I was never able to go past the first tutorial mission because my PC hung
during that mission.
Now I tried it again with mesa 13.0.3 and I was finally able to
https://bugs.freedesktop.org/show_bug.cgi?id=99313
--- Comment #1 from SET ---
Erratum :
iGPU : 00:01.0 VGA compatible controller: Advanced Micro Devices, Inc.
[AMD/ATI] Kaveri [Radeon R6 Graphics]
--
You are receiving this mail because:
You are the assignee for the bug.
-- next
https://bugs.freedesktop.org/show_bug.cgi?id=99313
Bug ID: 99313
Summary: A few amdgpu errors with kernel 4.10-rc2 (Kaveri +
Topaz)
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=99261
--- Comment #4 from SET ---
Well, the hang up on switch to amdgpudrmfb was due to the kernel boot parameter
'acpi=off' I had to use to go beyond the 'loading initramfs' step. Initial
hangup in the latter step was due to a UEFI bug of the laptop.
https://bugs.freedesktop.org/show_bug.cgi?id=99312
--- Comment #1 from John Bridgman ---
If you have not already done so, try disabling the watchdog timer:
MODULE_PARM_DESC(lockup_timeout, "GPU lockup timeout in ms (default 1 = 10
seconds, 0 = disable)");
module_param_named(lockup_timeout,
https://bugs.freedesktop.org/show_bug.cgi?id=99312
Vedran MiletiÄ changed:
What|Removed |Added
Hardware|Other |x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=99312
Bug ID: 99312
Summary: Long-running OpenCL kernels cause ring stalls and GPU
lockups on Kabini
Product: Mesa
Version: 13.0
Hardware: Other
OS: All
https://bugs.freedesktop.org/show_bug.cgi?id=99311
Bug ID: 99311
Summary: [regression,radeonsi] Updating to 1edc53a66b breaks
SDDM (white screen on launch)
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
https://bugs.freedesktop.org/show_bug.cgi?id=99310
mr.swaagger at mail.ru changed:
What|Removed |Added
URL||https://imgur.com/a/A8LDW
--
https://bugs.freedesktop.org/show_bug.cgi?id=99309
--- Comment #1 from Arek RuÅniak ---
Created attachment 128805
--> https://bugs.freedesktop.org/attachment.cgi?id=128805=edit
chomium look
--
You are receiving this mail because:
You are the assignee for the bug.
-- next part
https://bugs.freedesktop.org/show_bug.cgi?id=99310
Bug ID: 99310
Summary: Ubuntu 16.04/16.10 AMD Radeonsi - wrong colors (oibaf
ppa) in XFCE and eog.
Product: Mesa
Version: git
Hardware: x86-64 (AMD64)
OS:
https://bugs.freedesktop.org/show_bug.cgi?id=99309
Bug ID: 99309
Summary: [radeonsi]glsl: Override the # of varying slots for
ClipDistance and TessLevel*. broke chromium browser
Product: Mesa
Version: git
Hardware: Other
https://bugs.freedesktop.org/show_bug.cgi?id=97116
--- Comment #1 from Andy Furniss ---
Old bug - mpv --vo=vaapi is unstable with or without the env on current head
and may well have only lucked into apparently working with
VAAPI_DISABLE_INTERLACE=1
all along.
Will open new bug soon(ish).
1 - 100 of 32557 matches
Mail list logo