https://bugs.freedesktop.org/show_bug.cgi?id=104344
Bug ID: 104344
Summary: Display Adapter Chain, Cable Disconnect causes Nouveau
crash
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux
This is parallel to the pre-SM50 change which does this. Adjusts the
shuffles / quadops to make the values correct relative to lane 0, and
then splat the results to all lanes for the final move into the target
register.
Signed-off-by: Ilia Mirkin
---
Entirely untested beyond compilation. Should
https://bugs.freedesktop.org/show_bug.cgi?id=104340
S. Gilles changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bugs.freedesktop.org/show_bug.cgi?id=100423
--- Comment #7 from Ben Skeggs ---
(In reply to Ilia Mirkin from comment #6)
> Looks like 22554 is no longer available on Maxwell. See where ltc reads it
> from for the new location. Needs to be split out of ramgk104 somehow.
I have WIP patches
https://bugs.freedesktop.org/show_bug.cgi?id=104340
--- Comment #4 from Ben Skeggs ---
I've pushed a fix for a rather stupid memory leak bug that's likely the cause
of what you're seeing.
--
You are receiving this mail because:
You are the assignee for the bug.__
https://bugs.freedesktop.org/show_bug.cgi?id=104291
--- Comment #11 from Andrew Randrianasulu ---
I tried few older mesa releases (17.1.10 - without llvm, 17.2.7 and 17.3.0 -
with llvm 5.0.0), and they all segfaults :/
This is kinda strange, because according to this bugreport it was working in
https://bugs.freedesktop.org/show_bug.cgi?id=100423
--- Comment #6 from Ilia Mirkin ---
Looks like 22554 is no longer available on Maxwell. See where ltc reads it from
for the new location. Needs to be split out of ramgk104 somehow.
--
You are receiving this mail because:
You are the assignee f
https://bugs.freedesktop.org/show_bug.cgi?id=104340
--- Comment #3 from S. Gilles ---
Created attachment 136295
--> https://bugs.freedesktop.org/attachment.cgi?id=136295&action=edit
output of slabtop after running X for a few weeks
--
You are receiving this mail because:
You are the assignee
https://bugs.freedesktop.org/show_bug.cgi?id=104340
--- Comment #2 from S. Gilles ---
Created attachment 136294
--> https://bugs.freedesktop.org/attachment.cgi?id=136294&action=edit
contents of /proc/meminfo after running X for a few weeks, then killing it
--
You are receiving this mail becau
https://bugs.freedesktop.org/show_bug.cgi?id=104340
--- Comment #1 from S. Gilles ---
Created attachment 136292
--> https://bugs.freedesktop.org/attachment.cgi?id=136292&action=edit
first few lines of /sys/kernel/debug/kmemleak
--
You are receiving this mail because:
You are the assignee for
https://bugs.freedesktop.org/show_bug.cgi?id=104340
Bug ID: 104340
Summary: Memory leak with GEM objects
Product: xorg
Version: git
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
https://bugs.freedesktop.org/show_bug.cgi?id=104222
--- Comment #2 from Olli Helenius ---
Another “me too”. Sorry if this is redunant. On Arch Linux with:
> Linux emi 4.14.6-1-ARCH #1 SMP PREEMPT Thu Dec 14 21:26:16 UTC 2017 x86_64
> GNU/Linux
Output from `lspci`:
> 01:00.0 VGA compatible con
On 2017-12-19 11:37 AM, Michel Dänzer wrote:
> On 2017-12-18 08:01 PM, Tobias Klausmann wrote:
>> On 12/18/17 7:06 PM, Mike Galbraith wrote:
>>> Greetings,
>>>
>>> Kernel bound workloads seem to trigger the below for whatever reason.
>>> I only see this when beating up NFS. There was a kworker w
On 2017-12-18 08:01 PM, Tobias Klausmann wrote:
> On 12/18/17 7:06 PM, Mike Galbraith wrote:
>> Greetings,
>>
>> Kernel bound workloads seem to trigger the below for whatever reason.
>> I only see this when beating up NFS. There was a kworker wakeup
>> latency issue, but with a bandaid applied t
14 matches
Mail list logo
