similar to: [Bug 96968] New: [NVC0] disp: ERROR 7 [INVALID_HANDLE] 00 chid 0 mthd 0088 data f000000

https://bugs.freedesktop.org/show_bug.cgi?id=103889 Bug ID: 103889 Summary: [NV50/G86] disp: ERROR 1 [] 01 [] chid 0 mthd 0000 data 00000000 Product: xorg Version: 7.7 (2012.06) Hardware: PowerPC OS: All Status: NEW Severity: normal Priority: medium Component:

https://bugs.freedesktop.org/show_bug.cgi?id=103467 Bug ID: 103467 Summary: [NVC0/GF108] fifo: read fault at cd90f4d000 engine 07 [PFIFO] client 07 [BAR_READ] reason 00 [PT_NOT_PRESENT] on channel 1 [003fe11000 DRM] Product: xorg Version: 7.7 (2012.06) Hardware: PowerPC OS: All

https://bugs.freedesktop.org/show_bug.cgi?id=73924 Priority: medium Bug ID: 73924 Assignee: nouveau at lists.freedesktop.org Summary: E[ PDISP][0000:01:00.0] chid 0 mthd 0x0080 data 0x00000000 0x00055080 QA Contact: xorg-team at lists.x.org Severity: normal Classification: Unclassified OS: All

https://bugs.freedesktop.org/show_bug.cgi?id=90390 Bug ID: 90390 Summary: [NV98] Modesetting causes blank screen because of INVALID_STATE [UNK0B] chid 1 mthd 0x0080 data 0x00000000 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW

https://bugs.freedesktop.org/show_bug.cgi?id=99858 Bug ID: 99858 Summary: disp: ERROR 4 [INVALID_VALUE] 84 [] chid 0 mthd 0828 data 000099bb Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

https://bugs.freedesktop.org/show_bug.cgi?id=87436 Bug ID: 87436 Summary: INVALID_STATE [UNK05] chid 0 mthd 0x0080 data 0x00000000 Product: xorg Version: 7.7 (2012.06) Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

Hi, Am using wine-1.1.17 version compiled for 64 bit linux to run 64bit windows applications. When my application tries to open any RegistryKey's, I find always the INVALID_HANDLE for open_keys.Is there any specific configuration required either thru winetricks or any form to access the registry keys? Thanks, Yugandhar

https://bugs.freedesktop.org/show_bug.cgi?id=37445 Summary: Nouveau regulary reports the TRAP_VFETCH FAULT errors. Product: Mesa Version: git Platform: x86-64 (AMD64) OS/Version: All Status: NEW Severity: minor Priority: medium Component: Drivers/DRI/nouveau AssignedTo: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=58378 --- Comment #34 from Andreas Loew <awl1 at gmx.net> --- Bad news once again... I applied the following single-line patch to a stock 3.12.4 kernel in order to switch to the NV50 fence: diff -Nrpu linux-3.12.4.orig/drivers/gpu/drm/nouveau/nouveau_drm.c linux-3.12.4/drivers/gpu/drm/nouveau/nouveau_drm.c ---

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

Twice in a little over a week, nouveau has locked up on my system with an Asus ENGT430 that is "Detected [as] an NVc0 generation card (0x0c1080a1)" at boot time. OS is Mageia 2, kernel 3.4.45-server-1.mga2. At the time of both lockups, I had a couple dozen Firefox windows plus several other miscellaneous windows open. Here are the some snippets from /var/log/messages a few days before

I've been stuck on this one for days and can't seem to find anything referencing the same problem; help would be greatly appreciated. I have a functioning Samba 3.5.4-63 installation acting as a PDC - users can log in from Windows 7 machines without problems etc. etc. The issue is with using wbinfo -a to authenticate users (without going into too much detail, I'm trying to use the

Hey, This patch causes a regression on my display-less nvd7. Commenting out the aux, aux_stat and aux_mask members in nvd0_i2c_oclass fixes boot, and makes things work normally again. broken dmesg: [ 40.314470] ACPI Warning: \_SB_.PCI0.GFX0._DSM: Argument #4 type mismatch - Found [Buffer], ACPI requires [Package] (20140424/nsarguments-95) [ 40.314729] ACPI Warning: \_SB_.PCI0.GFX0._DSM:

There's a short window between module load and fbcon initalization when it's possible for vgacon to write to VGA RAM. Nouveau uses this memory for different purposes, so if we are unlucky, it causes mysterious memory corruptions. For me, booting with nv_printk debug levels set to 5 was enough to trigger it. It manifested as long stream of: "trapped write at ... on channel 0x0001fea0

https://bugs.freedesktop.org/show_bug.cgi?id=105173 --- Comment #11 from Nick Lee <nvlbox at gmail.com> --- (In reply to Pierre Moreau from comment #10) > What exactly is reproducible? The artefacts I would assume, but which error > exactly? The NULL pointer dereference, or the “trapped read at 0080000000 on > channel 1 [0fbb0000 DRM] engine 00 [PGRAPH] client 03 [DISPATCH]

https://bugs.freedesktop.org/show_bug.cgi?id=95212 Bug ID: 95212 Summary: GT215GLM Rendering hickups with gnome-shell Product: Mesa Version: 11.2 Hardware: Other OS: All Status: NEW Severity: normal Priority: medium Component: Drivers/DRI/nouveau Assignee: nouveau at

https://bugs.freedesktop.org/show_bug.cgi?id=92971 --- Comment #8 from Philippe Condé <conde.philippe at skynet.be> --- Hello, I desactivated kscreenlocker which resolve the reactivate problem. But the problem of corrupt screen when starting different programs remains and is worst since the last zypper dup. I found this error still related to nouveau when the two screen got corrupted ov

From: Xia Yang <xiay at nvidia.com> Fix the channel id bit mask in FIFO schedule timeout error handling. FIFO_ENGINE_STATUS_NEXT_ID is bit 27:16 thus 0x0fff0000. FIFO_ENGINE_STATUS_ID is bit 11:0 thus 0x00000fff. Signed-off-by: Xia Yang <xiay at nvidia.com> Reviewed-by: Alexandre Courbot <acourbot at nvidia.com> --- drm/nouveau/nvkm/engine/fifo/gk104.c | 4 ++-- 1 file

On Wed, Apr 04, 2018 at 03:48:39PM +0300, Māris Nartišs wrote: > 2018-04-03 23:00 GMT+03:00, Adam Borowski <kilobyte at angband.pl>: > > In commit da5e45e619b3f101420c38b3006a9ae4f3ad19b0 > > > > yet it is still reproducible for me on 4.16-rc7 and 4.16.0, which already > > have your fix. I don't know about earlier versions -- my newer card went > > into

CentOS Errata and Enhancement Advisory 2012:0088 Upstream details at : https://rhn.redhat.com/errata/RHEA-2012-0088.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 1e95d3b4772e0d6dfa54cdf005739f3734514d294ccf9d08a085af219089e581 kmod-igb-PAE-rhel5u7-3.0.6_k2_1.1-1.el5_7.i686.rpm