https://bugs.freedesktop.org/show_bug.cgi?id=106496
--- Comment #1 from Aaron ---
Created attachment 139537
--> https://bugs.freedesktop.org/attachment.cgi?id=139537&action=edit
kernel config used to build test kernel
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=106496
Bug ID: 106496
Summary: Hung screen at modprobe amdgpu
Product: DRI
Version: XOrg git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: norm
https://bugs.freedesktop.org/show_bug.cgi?id=105425
--- Comment #70 from MirceaKitsune ---
(In reply to iive from comment #69)
Just tried mesa_glthread=false RADEON_THREAD=false MESA_DEBUG=flush and got the
same results. The others seem a lot more complex: I might try them later, but
currently I
https://bugs.freedesktop.org/show_bug.cgi?id=106493
Mariusz Ceier changed:
What|Removed |Added
Attachment #139529|0 |1
is obsolete|
https://bugs.freedesktop.org/show_bug.cgi?id=106289
--- Comment #1 from Dave Coffin ---
This bug also crashes "mplayer" but not "mpv". I compiled mesa 18.0.3 from
source and got a more informative stack trace, though many parameters are still
"optimized out":
r300: DRM version: 2.50.0, Name: AT
https://bugs.freedesktop.org/show_bug.cgi?id=105684
--- Comment #29 from Aaron ---
Created attachment 139530
--> https://bugs.freedesktop.org/attachment.cgi?id=139530&action=edit
Arch current default kernel config
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=105684
--- Comment #28 from Aaron ---
I am getting this issue on the default kernel configuration for Arch Linux as
well as my 4.17 rc build. I'll attach both configs.
--
You are receiving this mail because:
You are the assignee for the bug._
https://bugs.freedesktop.org/show_bug.cgi?id=106493
Bug ID: 106493
Summary: "New game" in stellaris triggers Assertion
`rtex->surface.u.legacy.level[level].dcc_fast_clear_si
ze' failed.
Product: Mesa
Version: git
On Tue, May 08, 2018 at 05:14:25PM -0700, Eric Anholt wrote:
> drm_minor_alloc() does multiplication on this enum, so the removal
> ended up moving render nodes down from 128 base to 64. This caused
> Mesa's surfaceless backend to be unable to open the render nodes,
> since it was still looking up
https://bugs.freedesktop.org/show_bug.cgi?id=106473
Matt Whitlock changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
On 2018-05-10 10:10, Andrzej Hajda wrote:
> On 04.05.2018 15:52, Peter Rosin wrote:
>> If the bridge supplier is unbound, this will bring the bridge consumer
>> down along with the bridge. Thus, there will no longer linger any
>> dangling pointers from the bridge consumer (the drm_device) to some
>
We report the crash:
"KASAN: use-after-free Write in vgacon_scroll"
This crash was found in v4.17-rc3. Specifically, memory access (write
operation) is invalid, and it is detected by KASAN.
C repro code:
https://kiwi.cs.purdue.edu/static/alexkkid-fuzzer/repro-bd11a.c
kernel config:
https://kiwi
On 2018-05-08 03:48, Stephen Boyd wrote:
Quoting spa...@codeaurora.org (2018-05-03 02:41:29)
On 2018-05-02 22:31, Stephen Boyd wrote:
> Quoting Sandeep Panda (2018-05-01 21:32:00)
>> diff --git
>> a/Documentation/devicetree/bindings/display/bridge/ti,sn65dsi86.txt
>> b/Documentation/devicetree/b
On Mon, Apr 23, 2018 at 4:24 PM, Matthew Wilcox wrote:
> On Wed, Apr 18, 2018 at 10:24:39AM +0200, Thierry Reding wrote:
>> > @@ -437,20 +436,7 @@ static int tegra_bo_fault(struct vm_fault *vmf)
>> > offset = (vmf->address - vma->vm_start) >> PAGE_SHIFT;
>> > page = bo->pages[offset];
>> >
Hi Rob, Thierry
> On Fri, May 4, 2018 at 5:28 AM, Lukasz Majewski wrote:
> > Hi Rob,
> >
> >> On Thu, Apr 12, 2018 at 04:37:15PM +0200, Lukasz Majewski wrote:
> >> > This commit adds support for KOE's 5.7" display.
> >> >
> >> > Signed-off-by: Lukasz Majewski
> >> > ---
> >> > .../bindings/
On Thu, May 10, 2018 at 08:34:48PM +0530, Souptick Joarder wrote:
> Use new return type vm_fault_t for fault handler in
> struct vm_operations_struct. For now, this is just
> documenting that the function returns a VM_FAULT
> value rather than an errno. Once all instances are
> converted, vm_fault_
On 2018-05-08 03:50, Stephen Boyd wrote:
Quoting Sean Paul (2018-05-02 12:03:16)
On Wed, May 02, 2018 at 10:01:59AM +0530, Sandeep Panda wrote:
> + struct drm_display_mode curr_mode;
> + struct mutex lock;
> + unsigned int ctrl_ref_count;
> +};
> +
> +static const struct regmap_rang
On Fri, May 11, 2018 at 1:24 PM, Inki Dae wrote:
>
> 2018년 05월 10일 23:27에 Souptick Joarder 이(가) 쓴 글:
>> On Sat, Apr 14, 2018 at 9:34 PM, Souptick Joarder
>> wrote:
>>> Use new return type vm_fault_t for fault handler
>>> in struct vm_operations_struct.
>>>
>>> Signed-off-by: Souptick Joarder
>>
https://bugs.freedesktop.org/show_bug.cgi?id=106490
Bug ID: 106490
Summary: VA-API video deconding broken for Chromium on Mesa
18.0.3
Product: Mesa
Version: 18.0
Hardware: x86-64 (AMD64)
OS: Linux (All)
https://bugs.freedesktop.org/show_bug.cgi?id=102709
--- Comment #3 from Vitalii ---
(In reply to Vitalii from comment #2)
> (In reply to Samuel Pitoiset from comment #1)
> > Well, War Thunder doesn't check that GL_EXT_texture_compression_s3tc is
> > exposed before using those compressed formats.
https://bugs.freedesktop.org/show_bug.cgi?id=102709
--- Comment #2 from Vitalii ---
(In reply to Samuel Pitoiset from comment #1)
> Well, War Thunder doesn't check that GL_EXT_texture_compression_s3tc is
> exposed before using those compressed formats.
>
> Though, if you have libtxc_dxtn install
https://bugs.freedesktop.org/show_bug.cgi?id=104300
Bug ID: 104300
Summary: Kernel 4.15-rc2 on Polaris RX 480 with amdgpu.dc=1 has
trouble waking up displays after suspend
Product: DRI
Version: unspecified
Hardware: x86-64
https://bugs.freedesktop.org/show_bug.cgi?id=106456
Ilia Mirkin changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=91880
--- Comment #198 from Jon Doane ---
I would like to add that the problem appears to be resolved on my installation
of Ubuntu 18.04 with the MSI R9 390 8GB GAMING GPU using the current mainline
kernel (4.17-rc4,) with the kernel flags of "amdgpu.d
https://bugs.freedesktop.org/show_bug.cgi?id=99403
--- Comment #11 from i...@yahoo.com ---
(In reply to Roman Elshin from comment #10)
> so it may be closed?
> p.s. thanks a lot to all participated
If it works OK for you, you are free to close it.
You may also mark it as duplicate of
https://bugs
https://bugs.freedesktop.org/show_bug.cgi?id=104347
--- Comment #14 from Norbert Klar ---
And looks like this bug not only happening with Chrome. Just installed Discord,
and getting the same behaviour.
--
You are receiving this mail because:
You are the assignee for the bug.
On Thu, May 3, 2018 at 12:49 AM, Kees Cook wrote:
> On Fri, Apr 13, 2018 at 2:24 PM, Laura Abbott wrote:
>>
>> There's an ongoing effort to remove VLAs[1] from the kernel to eventually
>> turn on -Wvla. Switch to a constant value that covers all hardware.
>>
>> [1] https://lkml.org/lkml/2018/3/7/
https://bugs.freedesktop.org/show_bug.cgi?id=106427
--- Comment #5 from txtoxtox...@googlemail.com ---
Created attachment 139515
--> https://bugs.freedesktop.org/attachment.cgi?id=139515&action=edit
Xorg.log 4k@60
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106427
--- Comment #4 from txtoxtox...@googlemail.com ---
Created attachment 139514
--> https://bugs.freedesktop.org/attachment.cgi?id=139514&action=edit
dmesg-4.16.7 4K@60
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=106427
txtoxtox...@googlemail.com changed:
What|Removed |Added
Attachment #139402|dmesg-4.16.7|dmesg-4.16.7 5K@60
d
https://bugs.freedesktop.org/show_bug.cgi?id=106427
txtoxtox...@googlemail.com changed:
What|Removed |Added
Attachment #139403|Xorg.log|Xorg.log 5k@60
descr
https://bugs.freedesktop.org/show_bug.cgi?id=106427
--- Comment #3 from txtoxtox...@googlemail.com ---
I would like to mention that “cvt 4096 2304 -r” is a mode that works under X so
it may not be the 60 Hz as such but rather the increased bandwidth, which needs
DisplayPort 1.3 instead of just 1.2
https://bugs.freedesktop.org/show_bug.cgi?id=97025
--- Comment #27 from Bernd Steinhauser ---
Thanks, I'm testing it right now on linux 4.16.8.
Although I'm not sure if it works as expected, since the display does still
seem to disconnect when I turn the screen off.
At least the messages in dme
https://bugzilla.kernel.org/show_bug.cgi?id=199619
--- Comment #3 from Elmar Stellnberger (estel...@elstel.org) ---
persists with 4.17.0-rc4+
--
You are receiving this mail because:
You are watching the assignee of the bug.
___
dri-devel mailing list
d
34 matches
Mail list logo
