Displaying 20 results from an estimated 800 matches similar to: "[Bug 104222] New: GNOME/Wayland desktop freezes when resizing Firefox window"
2017 Dec 30
24
[Bug 104421] New: System freeze on wayland with nouveau on NV137 (GP107)
https://bugs.freedesktop.org/show_bug.cgi?id=104421
Bug ID: 104421
Summary: System freeze on wayland with nouveau on NV137 (GP107)
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee:
2016 Jan 07
57
[Bug 93629] New: [NVE6] complete system freeze, PGRAPH engine fault on channel 2, SCHED_ERROR [ CTXSW_TIMEOUT ]
https://bugs.freedesktop.org/show_bug.cgi?id=93629
Bug ID: 93629
Summary: [NVE6] complete system freeze, PGRAPH engine fault on
channel 2, SCHED_ERROR [ CTXSW_TIMEOUT ]
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
2017 Nov 16
3
[Bug 103780] New: Nouveau causes lockup - fifo: read fault at 00005ac000 engine 00 [GR] client 02 [GPC1/PE_0] reason 02 [PTE] on channel 24 [103b5b2000 Xwayland[1507]]
https://bugs.freedesktop.org/show_bug.cgi?id=103780
Bug ID: 103780
Summary: Nouveau causes lockup - fifo: read fault at 00005ac000
engine 00 [GR] client 02 [GPC1/PE_0] reason 02 [PTE]
on channel 24 [103b5b2000 Xwayland[1507]]
Product: xorg
Version: unspecified
Hardware: Other
OS: All
2018 Sep 05
14
[Bug 107829] New: nouveau crash/freeze [MULTIPLE_WARP_ERRORS] warp 3f0009 [ILLEGAL_INSTR_ENCODING]
https://bugs.freedesktop.org/show_bug.cgi?id=107829
Bug ID: 107829
Summary: nouveau crash/freeze [MULTIPLE_WARP_ERRORS] warp
3f0009 [ILLEGAL_INSTR_ENCODING]
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority:
2015 Dec 15
2
Debugging INVALID_OPCODE / MULTIPLE_WARP_ERRORS ?
Hi all,
As part of my compute work I'm trying to get some TGSI compute
code to work. The code from mesa/src/gallium/tests/trivial.c
works.
So now I'm trying to get a "native" tgsi kernel to run via
clover, I'm using Francisco's nbody.c example for this:
https://fedorapeople.org/~jwrdegoede/nbody.c
Which does not work, at first I thought there was an issue
with the
2015 Dec 15
2
Debugging INVALID_OPCODE / MULTIPLE_WARP_ERRORS ?
Also, where's the exit op? Perhaps what's happening is that you don't
have an exit and it just goes off executing into the ether?
On Tue, Dec 15, 2015 at 12:00 PM, Ilia Mirkin <imirkin at alum.mit.edu> wrote:
> A few things that stand out:
>
> 0: ld u32 %r219 c0[0x0000000000000000+0x0] (0)
>
> wtf is that 0x0000000000000 thing doing there? Was it a %rX which got
2018 Jan 16
4
[Bug 104649] New: System freeze after resuming from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=104649
Bug ID: 104649
Summary: System freeze after resuming from suspend
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2018 Jan 07
4
[Bug 104523] New: System does not resume from suspend
https://bugs.freedesktop.org/show_bug.cgi?id=104523
Bug ID: 104523
Summary: System does not resume from suspend
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2015 Nov 08
13
[Bug 92863] New: Complete freeze even with NvGrUseFW=1
https://bugs.freedesktop.org/show_bug.cgi?id=92863
Bug ID: 92863
Summary: Complete freeze even with NvGrUseFW=1
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau
2015 Dec 16
4
Debugging INVALID_OPCODE / MULTIPLE_WARP_ERRORS ?
I believe that your problem is this:
/*01a0*/ LD R8, [R8];
/* 0x8000000000821c85 */
That needs to be LD.E (and your ST's need to be ST.E). You're using a
32-bit gmem address, but you need to be using a 64-bit one. I believe
the 32-bit ones work on fermi, but afaik not on Kepler.
Cheers,
-ilia
On Wed, Dec 16, 2015 at 12:06 PM, Hans de Goede
2015 Dec 04
1
NV50 compute support questions
Hi,
On 04-12-15 09:54, Samuel Pitoiset wrote:
>
>
> On 12/04/2015 09:45 AM, Hans de Goede wrote:
<snip>
>>> Please give a shot at this branch :
>>> http://cgit.freedesktop.org/~hakzsam/mesa/log/?h=nvf0_compute
>>>
>>> It fixes the initialization of the compute state and allows me to
>>> launch 'test_input_global' (ie. ./compute
2015 Dec 04
4
NV50 compute support questions
Hi,
On 02-12-15 19:33, Samuel Pitoiset wrote:
>
>
> On 12/02/2015 04:34 PM, Hans de Goede wrote:
>> On 01-12-15, Samuel Pitoiset wrote:
>>
>> >>> Ok, here is a MMT trace of vectorAdd:
>> >>>
>> >>> https://fedorapeople.org/~jwrdegoede/vectorAdd.log.gz
>> >>
>> >> Hi Hans,
>> >>
>>
2017 May 28
4
[Bug 101215] New: Graphics Crash
https://bugs.freedesktop.org/show_bug.cgi?id=101215
Bug ID: 101215
Summary: Graphics Crash
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Drivers/DRI/nouveau
Assignee: nouveau at
2018 Jan 02
0
grumble/gripe ... fifo: read fault ... channel 12 killed! (eternal freeze-frame)
Twice now with v4.15-rc6, my display has gone belly up.
Note: swiotlb: suppress warning when __GFP_NOWARN is set v2 is applied,
but I don't _think_ it was the first time it happened.
[ 3729.558261] nouveau 0000:01:00.0: gr: TRAP ch 2 [00ff842000 Xorg[3413]]
[ 3729.558269] nouveau 0000:01:00.0: gr: GPC0/TPC0/TEX: 80000041
[ 3729.558273] nouveau 0000:01:00.0: gr: GPC0/TPC1/TEX: 80000041
[
2015 Nov 12
9
[Bug 92922] New: Xorg random freeze
https://bugs.freedesktop.org/show_bug.cgi?id=92922
Bug ID: 92922
Summary: Xorg random freeze
Product: xorg
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2017 May 07
2
GT 730 freeze : how do diagnose / debug ?
Hi,
I own an Asus GT730-SL-2GD3-BRK, trying to drive two monitors at 2560x1440
resolution. Using gnome-shell with either Xorg or wayland I get screen
freezes very frequently. Those freezes usually require a reboot to get
working graphics (below a sample trace that I got yesterday).
I am running Ubuntu 17.04 with the latest kernels avalable, I also tested
various more recent kernels including
2015 May 18
2
Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles
Hello,
I've been debugging a few different tessellation shader issues with
nouveau, but let's start small. I see this issue on my GK208 with high
frequency, and I *think* I've seen it once or twice on my GF108, but
it's exceedingly rare, if it does happen. I don't have a GK10x to test
on, unfortunately, but I assume it'll have the same issue as the
GK208.
The issue is
2017 Nov 13
19
[Bug 103721] New: Frequent freezes with nouveau on Thinkpad P50
https://bugs.freedesktop.org/show_bug.cgi?id=103721
Bug ID: 103721
Summary: Frequent freezes with nouveau on Thinkpad P50
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: Driver/nouveau
Assignee: nouveau at
2016 Jul 09
7
[Bug 96876] New: system freeze "fifo: gr engine fault on channel 6" NVIDIA
https://bugs.freedesktop.org/show_bug.cgi?id=96876
Bug ID: 96876
Summary: system freeze "fifo: gr engine fault on channel 6"
NVIDIA
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component:
2015 May 26
2
Tessellation shaders get MEM_OUT_OF_BOUNDS errors / missing triangles
One additional observation that I just made is that on GK208, the blob
apparently doesn't use the result of S2R Rx, SR_INVOCATION_ID
wholesale in TCS. It either passes it through a I2I.S32.S32 Rx, |Rx|
(i.e. absolute value), or even more paradoxically, shl 2; shr 2; which
removes the top *2* bits, rather than just the top 1. However I see no
such behaviour on GF108.
I'm going to test out