similar to: [Bug 96411] New: [NVA8] reclocking not working. screen glitches.

https://bugs.freedesktop.org/show_bug.cgi?id=39101 Summary: [NVA8] VirtualBox segfault when accelerating 3D Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=46597 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|nv50_pc.h:351: |[NVA8/NV50 gallium] |nv_alloc_instruction: |nv50_pc.h:351: |Assertion

https://bugs.freedesktop.org/show_bug.cgi?id=46597 Ilia Mirkin <imirkin at alum.mit.edu> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution|--- |INVALID --- Comment #2 from Ilia Mirkin <imirkin at

On Sat, Jul 27, 2019 at 7:37 AM Ralph Corderoy <ralph at inputplus.co.uk> 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

Às 14:46 de 27/07/2019, Ilia Mirkin escreveu: > On Sat, Jul 27, 2019 at 7:37 AM Ralph Corderoy <ralph at inputplus.co.uk> 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

https://bugs.freedesktop.org/show_bug.cgi?id=91229 Bug ID: 91229 Summary: [NVA8] VDPAU only works when debug is on Product: Mesa Version: 10.5 Hardware: x86 (IA32) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

Starting with the drm merge af3c8d98508d37541d4bf57f13a984a7f73a328c for 4.13-rc1, the NVidia NVS3100M display on Dell Latitude E6410 had a nullptr crash on startup. As a result later the suspend2ram was locking up. Traced to a null ptr in nv50_mstm_service(), which seems to be called only from nouveau_connector_hotplug(). Fixed by checking if mstm is not NULL before calling the service

https://bugs.freedesktop.org/show_bug.cgi?id=101587 Bug ID: 101587 Summary: [BISECTED][REGRESSION] Nouveau kernel module (>4.10) on NVA8 renders the system unusable Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal

https://bugs.freedesktop.org/show_bug.cgi?id=89113 Bug ID: 89113 Summary: NVA8 constantly flickers when clocked to lowest pstate Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=37768 Summary: [NVA8] UT2003: Splash-screen is transparent with gnome-shell enabled Product: Mesa Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau

https://bugs.freedesktop.org/show_bug.cgi?id=89273 Bug ID: 89273 Summary: [NVA8] nouveau screen corruption and X lockup when reclocking Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

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

https://bugs.freedesktop.org/show_bug.cgi?id=88415 Bug ID: 88415 Summary: [NVA8] nouveau GPU lockup when reclocking Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau Assignee:

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

https://bugs.freedesktop.org/show_bug.cgi?id=82247 Priority: medium Bug ID: 82247 Assignee: nouveau at lists.freedesktop.org Summary: [NVA8] The DisplayPort screen does not light up at first try on Linux 3.16 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS:

http://bugs.freedesktop.org/show_bug.cgi?id=24668 Summary: KMS does not work with nva8 Product: xorg Version: unspecified Platform: Other OS/Version: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org ReportedBy:

https://bugs.freedesktop.org/show_bug.cgi?id=69029 Priority: medium Bug ID: 69029 Assignee: nouveau at lists.freedesktop.org Summary: GT218 (NVA8): GPU lockup since kernel 3.11 upgrade QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: Linux (All) Reporter: fred at

https://bugzilla.netfilter.org/show_bug.cgi?id=1072 Bug ID: 1072 Summary: coredump when parsing ip protocol with number > 6 Product: nftables Version: unspecified Hardware: x86_64 OS: All Status: NEW Severity: major Priority: P5 Component: nft Assignee: pablo at

On Mon, Jun 6, 2016 at 12:11 PM, Matt Godbolt <matt at godbolt.org> wrote: > > On Mon, Jun 6, 2016 at 1:41 PM Rui Ueyama via llvm-dev < > llvm-dev at lists.llvm.org> wrote: > >> As to leave an opportunity for the kernel, I think mmap+write would be >> enough. Because the kernel knows what address is mmap'ed, it can detect >> that write's source is

As to leave an opportunity for the kernel, I think mmap+write would be enough. Because the kernel knows what address is mmap'ed, it can detect that write's source is actually a mmap'ed file and if that's the case it can optimize as it does for sendfile. It seems that Linux doesn't do that now, though. I haven't thought about using non-temporal stores. It may work as we