https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #27 from John Bridgman (john.bridg...@amd.com) ---
Hmm, doesn't look like there are any amdgpu X driver changes specific to Navi.
Still, the xorg.log seems wrong.
--
You are receiving this mail because:
You are watching the assignee
https://bugzilla.kernel.org/show_bug.cgi?id=204725
John Bridgman (john.bridg...@amd.com) changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #10 from Marko Popovic ---
(In reply to Matthias Müller from comment #9)
> On my side i can report that the issue does not occur if i don't use a tool
> to modify the FANs - does anyone of you use something of the like or are
> this
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #9 from Matthias Müller ---
On my side i can report that the issue does not occur if i don't use a tool to
modify the FANs - does anyone of you use something of the like or are this
seperate issues?
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=111526
Andre Klapper changed:
What|Removed |Added
Group||spam
Status|NEW
https://bugs.freedesktop.org/show_bug.cgi?id=111273
--- Comment #1 from Trek ---
Created attachment 145226
--> https://bugs.freedesktop.org/attachment.cgi?id=145226=edit
possible fix
The proposed fix is tested on latest git.
I'm unsure if 65536 is a good limit: it could be small as 64, but
https://bugs.freedesktop.org/show_bug.cgi?id=109955
--- Comment #91 from Wilko Bartels ---
how big are your swap partitions guys? just toying around here :-)
--
You are receiving this mail because:
You are the assignee for the bug.___
dri-devel
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #8 from Marko Popovic ---
(In reply to Mathieu Belanger from comment #7)
> Created attachment 145225 [details] [review]
> Merge last adg5f code
>
> Ok, I did look at the recent kernel patch and commit and they seam to have
> fixed
https://bugs.freedesktop.org/show_bug.cgi?id=111481
--- Comment #7 from Mathieu Belanger ---
Created attachment 145225
--> https://bugs.freedesktop.org/attachment.cgi?id=145225=edit
Merge last adg5f code
Ok, I did look at the recent kernel patch and commit and they seam to have
fixed a couple
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #25 from Ant (untaintablean...@hotmail.co.uk) ---
26th* rather.
Hang in there, I'm sure this'll be sorted soon.
Is it a reference rx 5700 btw?
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #24 from Ant (untaintablean...@hotmail.co.uk) ---
Also, from the phoronix forum post, I can confirm your firmware file checksums
all match mine which are the versions dated from the 28th.
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #23 from Ant (untaintablean...@hotmail.co.uk) ---
As justification for my lack of framebuffer support in the kernel, allow me to
direct you to this from the gentoo wiki:
The framebuffer's original function is as a video RAM cache to
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #22 from Ant (untaintablean...@hotmail.co.uk) ---
2 things I notice are:
Xorg complains it can't find LLVM 9 or higher. I notice you said you have llvm
trunk (10), could you try installing version 9 to see if that appeases it?
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #21 from Dmitri Seletski (drj...@gmail.com) ---
Created attachment 284739
--> https://bugzilla.kernel.org/attachment.cgi?id=284739=edit
after xorg.conf.d/amdgpu file was created.
after xorg.conf.d/amdgpu file was created.
I start
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #20 from Dmitri Seletski (drj...@gmail.com) ---
Created attachment 284737
--> https://bugzilla.kernel.org/attachment.cgi?id=284737=edit
after amdgpu config was created in xorg.d folder
--
You are receiving this mail because:
You
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #19 from Dmitri Seletski (drj...@gmail.com) ---
since my xorg config directory is in different place I created brand new file:
/etc/X11/xorg.conf.d/10-amdgpu.conf
and put:
Section "OutputClass"
Identifier "AMDgpu"
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #18 from Dmitri Seletski (drj...@gmail.com) ---
Created attachment 284735
--> https://bugzilla.kernel.org/attachment.cgi?id=284735=edit
weston putput
--
You are receiving this mail because:
You are watching the assignee of the
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #17 from Dmitri Seletski (drj...@gmail.com) ---
Created attachment 284733
--> https://bugzilla.kernel.org/attachment.cgi?id=284733=edit
xorg log
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #16 from Dmitri Seletski (drj...@gmail.com) ---
Created attachment 284731
--> https://bugzilla.kernel.org/attachment.cgi?id=284731=edit
kill xorg and ps output
--
You are receiving this mail because:
You are watching the assignee
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #15 from Dmitri Seletski (drj...@gmail.com) ---
again, just a friendly reminder, i get problems BEFORE xorg. Xorg is not
running by default on my machine. it's first thing i manually start on my
machine when i login into console as
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #14 from Dmitri Seletski (drj...@gmail.com) ---
(none)dimko's Desktop /home/dimko # glxinfo | grep "OpenGL version"
OpenGL version string: 3.1 Mesa 19.3.0-devel (git-8709b865ce)
i also disabled those options before, they made
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #13 from Ant (untaintablean...@hotmail.co.uk) ---
I've got an RX5700 myself, so lets see if we can't get this sorted.
Can I just check something - the .config file you attached (comment 1)
for the kernel has
# Display Engine
https://bugs.freedesktop.org/show_bug.cgi?id=111527
Bug ID: 111527
Summary: obs-studio + latest mesa on amdgpu/vega64 leaks kernel
memory rapidly
Product: Mesa
Version: git
Hardware: Other
OS: All
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #12 from Dmitri Seletski (drj...@gmail.com) ---
Created attachment 284729
--> https://bugzilla.kernel.org/attachment.cgi?id=284729=edit
dmesg output with modules loaded.
dmesg output with modules loaded.
--
You are receiving this
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #11 from Dmitri Seletski (drj...@gmail.com) ---
Created attachment 284727
--> https://bugzilla.kernel.org/attachment.cgi?id=284727=edit
lsmod v2
--
You are receiving this mail because:
You are watching the assignee of the bug.
https://bugzilla.kernel.org/show_bug.cgi?id=204725
--- Comment #10 from Dmitri Seletski (drj...@gmail.com) ---
(In reply to Ant from comment #9)
> If it's any help, I had a look at your .config and noticed you've got the
> right navi10 firmware compiled in (however you've repeated
>
https://bugzilla.kernel.org/show_bug.cgi?id=204725
Ant (untaintablean...@hotmail.co.uk) changed:
What|Removed |Added
CC|
> +# nested likely/unlikely calls
> + if ($line =~
> /\b(?:(?:un)?likely)\s*\(\s*!?\s*(IS_ERR(?:_OR_NULL|_VALUE)?|WARN)/) {
> + WARN("LIKELY_MISUSE",
…
>> \b(?:un)?likely\s*
>
> This pair of brackets is required to match "unlikely"
> and it's optional in order to
Use alpha value to blend source value and destination value Instead of
just overwrite with source value.
Signed-off-by: Sidong Yang
---
drivers/gpu/drm/vkms/vkms_composer.c | 13 +++--
1 file changed, 11 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/vkms/vkms_composer.c
On 31.08.2019 19:45, Markus Elfring wrote:
+# nested likely/unlikely calls
+ if ($line =~
/\b(?:(?:un)?likely)\s*\(\s*!?\s*(IS_ERR(?:_OR_NULL|_VALUE)?|WARN)/) {
+ WARN("LIKELY_MISUSE",
>>>
>>> How do you think about to use the specification
>>>
>>> +# nested likely/unlikely calls
>>> + if ($line =~
>>> /\b(?:(?:un)?likely)\s*\(\s*!?\s*(IS_ERR(?:_OR_NULL|_VALUE)?|WARN)/) {
>>> + WARN("LIKELY_MISUSE",
>>
>> How do you think about to use the specification
>> “(?:IS_ERR(?:_(?:OR_NULL|VALUE))?|WARN)”
>> in this regular
On 31.08.2019 12:15, Markus Elfring wrote:
>> +# nested likely/unlikely calls
>> + if ($line =~
>> /\b(?:(?:un)?likely)\s*\(\s*!?\s*(IS_ERR(?:_OR_NULL|_VALUE)?|WARN)/) {
>> + WARN("LIKELY_MISUSE",
>
> How do you think about to use the specification
>
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #60 from tempel.jul...@gmail.com ---
I've applied your patch to current drm-next branch head (tag
drm-next-5.4-2019-08-30), situation is still unchanged. I've also attached a
new log with it. This time I ran Oblivion with Gallium
https://bugs.freedesktop.org/show_bug.cgi?id=110659
--- Comment #59 from tempel.jul...@gmail.com ---
Created attachment 145222
--> https://bugs.freedesktop.org/attachment.cgi?id=145222=edit
debug dmesg output for patch applied to drm-next
--
You are receiving this mail because:
You are the
In the probe function, some resources are allocated using 'dma_alloc_wc()',
they should be released with 'dma_free_wc()', not 'dma_free_coherent()'.
We already use 'dma_free_wc()' in the remove function, but not in the
error handling path of the probe function.
Also, remove a useless
+# nested likely/unlikely calls
+ if ($line =~
/\b(?:(?:un)?likely)\s*\(\s*!?\s*(IS_ERR(?:_OR_NULL|_VALUE)?|WARN)/) {
+ WARN("LIKELY_MISUSE",
How do you think about to use the specification
“(?:IS_ERR(?:_(?:OR_NULL|VALUE))?|WARN)”
in this regular
There were bugs in the DSI transfer (read and write) function
as it was only tested with displays ever needing a single byte
to be written. Fixed it up and tested so we can now write
messages of up to 16 bytes and read up to 4 bytes from the
display.
Tested with a Sony ACX424AKP display: this
https://bugs.freedesktop.org/show_bug.cgi?id=111481
Alexandr Kára changed:
What|Removed |Added
CC||alexandr.k...@gmail.com
--- Comment #6
38 matches
Mail list logo
