Displaying 20 results from an estimated 4000 matches similar to: "nouveau driver locks up with 4.11 kernel"
2017 Aug 14
0
nouveau driver locks up with 4.11 kernel
On Mon, Aug 14, 2017 at 3:18 PM, Michal Hocko <mhocko at kernel.org> wrote:
> Hi,
> I am having issues with nouveau driver in 4.11 Debian distribution
> kernel. I can start X session but the screen locks up e.g. when I try to
> exit mplayer fullscreen mode. The lock is swamped with tons of
> nouveau 0000:03:00.0: fifo: SCHED_ERROR 13 []
>
> messages and I also can see
2019 May 23
4
[Bug 110748] New: [NVC1] [optimus] fifo: read fault at 0000000000 engine 00 [PGRAPH] client 00 reason 02 [PAGE_NOT_PRESENT]
https://bugs.freedesktop.org/show_bug.cgi?id=110748
Bug ID: 110748
Summary: [NVC1] [optimus] fifo: read fault at 0000000000 engine
00 [PGRAPH] client 00 [] reason 02 [PAGE_NOT_PRESENT]
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
2017 Aug 14
1
nouveau driver locks up with 4.11 kernel
On Mon 14-08-17 15:27:20, Ilia Mirkin wrote:
> On Mon, Aug 14, 2017 at 3:18 PM, Michal Hocko <mhocko at kernel.org> wrote:
[...]
> > nouveau 0000:03:00.0: fifo: channel 6 [mpv/vo[3535]] kick timeout
> > nouveau: mpv/vo[3535]:00000000:0000906f: detach gr failed, -110
>
> Are you using mpv in conjunction with the GL video output and
> VDPAU-based acceleration? That
2017 Aug 14
0
nouveau driver locks up with 4.11 kernel
On Mon, Aug 14, 2017 at 4:29 PM, Michal Hocko <mhocko at kernel.org> wrote:
> On Mon 14-08-17 15:27:20, Ilia Mirkin wrote:
>> On Mon, Aug 14, 2017 at 3:18 PM, Michal Hocko <mhocko at kernel.org> wrote:
> [...]
>> > nouveau 0000:03:00.0: fifo: channel 6 [mpv/vo[3535]] kick timeout
>> > nouveau: mpv/vo[3535]:00000000:0000906f: detach gr failed, -110
>>
2016 Mar 25
4
[Bug 94694] New: Attempt to use kde/plasma renders the system immediately unresponsive
https://bugs.freedesktop.org/show_bug.cgi?id=94694
Bug ID: 94694
Summary: Attempt to use kde/plasma renders the system
immediately unresponsive
Product: Mesa
Version: 11.1
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
2019 Aug 14
1
Video Hardware Decoding: Jittery Rectangles on Nvidia GT218 NVA8 VP4.
Hi Ilia,
A fortnight ago, you wrote:
> > The video plays, CPU load is less (my aim), but there's ‘tearing’ of
> > the picture as if small rectangles that are updates are appearing in
> > the wrong location, off by a little. If I step through the frames
> > with mpv's ‘.’ and ‘,’ then I've found a pattern: one frame's
> > picture is good, followed by
2019 Jul 27
3
Video Hardware Decoding: Jittery Rectangles on Nvidia GT218 NVA8 VP4.
Hi,
I'm having trouble with hardware decoding of video with mpv(1) having
switched from Nvidia's proprietary driver to nouveau due to Arch Linux
removing its nvidia-340xx package.
The machine is an Acer Revo.
$ lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: NVIDIA Corporation GT218 [ION] [10de:0a64] (rev a2)
I think this is codename NVA8 with the
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
2016 Apr 16
3
[Bug 94964] New: Tearing with opengl-hq and not with opengl on Gnome with MPV
https://bugs.freedesktop.org/show_bug.cgi?id=94964
Bug ID: 94964
Summary: Tearing with opengl-hq and not with opengl on Gnome
with MPV
Product: Mesa
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component:
2019 Jun 19
0
nouveau: DRM: GPU lockup - switching to software fbcon
On (06/14/19 11:50), Sergey Senozhatsky wrote:
> dmesg
>
> nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon
> nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
> nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
> nouveau 0000:01:00.0: fifo: channel 5: killed
> nouveau 0000:01:00.0: fifo: engine 6: scheduled for recovery
>
2016 Oct 07
5
[Bug 98138] New: Random Freeze - nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
https://bugs.freedesktop.org/show_bug.cgi?id=98138
Bug ID: 98138
Summary: Random Freeze - nouveau 0000:01:00.0: fifo:
SCHED_ERROR 0a [CTXSW_TIMEOUT]
Product: xorg
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component:
2017 Aug 21
2
VDPAU issues in 17.2 and master, and a test request
Hi guys,
I just wanted to record some of my observations with nouveau; I
haven't had time to debug what happened. All testing done with mplayer
-vo vdpau.
First off, it seems like master + DRI3 works, up to a point, but then
crashes in nouveau pushbuf logic with a missing kref (which means some
unknown buffer is being used ... somewhere).
Now, in 17.2-rcN (sorry, I forget which one, but
2016 Oct 28
0
[Bug 96553] Xorg freezes
https://bugs.freedesktop.org/show_bug.cgi?id=96553
--- Comment #2 from simonF <simonfalicon at gmail.com> ---
I have same trouble my computer freeze, I can mouve mouse but nothing else. in
my log:
Oct 28 16:07:12 simon-Precision-T1700 kernel: [ 2191.290651] nouveau
0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
Oct 28 16:07:12 simon-Precision-T1700 kernel: [ 2191.290656] nouveau
2019 Jun 14
2
nouveau: DRM: GPU lockup - switching to software fbcon
5.2.0-rc4-next-20190613
dmesg
nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon
nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
nouveau 0000:01:00.0: fifo: runlist 0: scheduled for recovery
nouveau 0000:01:00.0: fifo: channel 5: killed
nouveau 0000:01:00.0: fifo: engine 6: scheduled for recovery
nouveau 0000:01:00.0: fifo: engine 0: scheduled for recovery
2019 Jun 19
2
nouveau: DRM: GPU lockup - switching to software fbcon
On Wed, Jun 19, 2019 at 1:08 AM Sergey Senozhatsky
<sergey.senozhatsky.work at gmail.com> wrote:
>
> On (06/14/19 11:50), Sergey Senozhatsky wrote:
> > dmesg
> >
> > nouveau 0000:01:00.0: DRM: GPU lockup - switching to software fbcon
> > nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
> > nouveau 0000:01:00.0: fifo: runlist 0: scheduled for
2017 Aug 21
1
[Mesa-dev] VDPAU issues in 17.2 and master, and a test request
Ilia Mirkin wrote:
> As I don't have the hardware myself, I was hoping someone could
> confirm that this is a nouveau issue and not a more general one.
> Ideally this would be done by testing VDPAU on both radeonsi and r600,
> as well as both the DRI3 and the DRI2 paths. Please use mplayer for
> this, not mpv or mplayer2 or anything else -- all those have various
>
2016 Jun 28
0
[Bug 96553] Xorg freezes
https://bugs.freedesktop.org/show_bug.cgi?id=96553
--- Comment #1 from Agostino Sarubbo <ago at gentoo.org> ---
When the problem happens, In dmesg there is the following messages:
[11449.585126] nouveau 0000:01:00.0: fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT]
[11449.585132] nouveau 0000:01:00.0: fifo: sw engine fault on channel 2,
recovering...
[11451.584882] nouveau 0000:01:00.0: fifo: runlist
2015 Jun 15
3
mpv rpm
jd1008 wrote:
>
>
> On 06/14/2015 10:12 PM, Peter wrote:
>> On 06/15/2015 04:09 PM, jd1008 wrote:
>>> I downloaded mpv-0.2.4-4.fc20.src.rpm from rpmfusion, and:
>>>
>>> /usr/bin/yum-builddep -t --nogpgcheck -y mpv-0.2.4-4.fc20.src.rpm
>>> says:
>>> Error: No Package found for libquvi-devel
>> You can get that, as well as most deps
2016 Jul 04
2
[Bug 96802] New: Upgrading mesa from 11.0.6 -> 11.2.2 causes graphics deadlock
https://bugs.freedesktop.org/show_bug.cgi?id=96802
Bug ID: 96802
Summary: Upgrading mesa from 11.0.6 -> 11.2.2 causes graphics
deadlock
Product: Mesa
Version: 11.2
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: major
Priority: medium
Component:
2015 Nov 16
0
[Bug 92971] [GF110] KDE plasma locks randomly due to crash of nouveau driver
https://bugs.freedesktop.org/show_bug.cgi?id=92971
--- Comment #5 from Philippe Condé <conde.philippe at skynet.be> ---
hello,
it is kde5 (KF5).
With opensuse Tumbleweed we do a global update (snapshot). Difficult to see
thereafter if this is due to KDE or the kernel.
Three examples from journalctl:
the very first error after the boot message: the lock occurred during
reactivation of