similar to: [Bug 99954] New: Errors when using VirtualBox with 3D acceleration: gr: ILLEGAL_CLASS ch 6 [007f7f8000 VirtualBox[5063]] subc 0 class c000 mthd 2390 data 00000000

https://bugs.freedesktop.org/show_bug.cgi?id=99202 Bug ID: 99202 Summary: system freeze - fifo: SCHED_ERROR 0a [CTXSW_TIMEOUT] - MULTIPLE_WARP_ERRORS - DATA_ERROR 00000004 [INVALID_VALUE] - ILLEGAL_CLASS ch 11 - RT_STORAGE_TYPE_MISMATCH - CLASS_SUBCH_MISMATCH Product: xorg Version: unspecified

https://bugs.freedesktop.org/show_bug.cgi?id=99900 --- Comment #6 from Ralph Gauges <r.gauges at hotmail.com> --- Just managed to freeze X again. This time I just started VirtualBox. kern.log entries are as follows. Xorg shows the same backtraces as the one I already attached. Feb 28 09:08:50 zeus kernel: [ 3164.314029] nouveau 0000:01:00.0: gr: ILLEGAL_CLASS ch 7 [007f15c000

https://bugs.freedesktop.org/show_bug.cgi?id=98525 Bug ID: 98525 Summary: nouveau graphics freeze when using KDE Plasma 5 with "fifo: PBDMA0: 00200000 subc 0 mthd 000c data 00000000" Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status:

https://bugs.freedesktop.org/show_bug.cgi?id=65251 Priority: medium Bug ID: 65251 Assignee: nouveau at lists.freedesktop.org Summary: nouveau E[ PFIFO][0000:01:00.0] CACHE_ERROR - Ch 6/0 Mthd 0x0060 Data 0x8000000f Severity: normal Classification: Unclassified OS: Linux (All) Reporter:

CentOS Errata and Security Advisory 2018:2390 Important Upstream details at : https://access.redhat.com/errata/RHSA-2018:2390 The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 106a77192bd5329bcc3f7e388192dd6f180b0ab95f4680064d75f3c51d959702 kernel-2.6.32-754.3.5.el6.i686.rpm

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://bugzilla.mindrot.org/show_bug.cgi?id=2390 Bug ID: 2390 Summary: PROTOCOL.key mis-describes private section Product: Portable OpenSSH Version: 6.8p1 Hardware: All OS: All Status: NEW Severity: normal Priority: P5 Component: Documentation Assignee: unassigned-bugs at

https://bugzilla.samba.org/show_bug.cgi?id=2390 ------- Additional Comments From woodd@deshaw.com 2005-02-24 17:21 ------- Created an attachment (id=980) --> (https://bugzilla.samba.org/attachment.cgi?id=980&action=view) Proposed sender.c / receiver.c patch -- Configure bugmail: https://bugzilla.samba.org/userprefs.cgi?tab=email ------- You are receiving this mail because: -------

https://bugzilla.samba.org/show_bug.cgi?id=2390 Summary: some dry run stats inaccurate Product: rsync Version: 2.6.4 Platform: All OS/Version: All Status: NEW Severity: normal Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: woodd@deshaw.com QAContact:

This makes nouveau recognise and report more kinds of PGRAPH errors, as well as prevent GPU lockups resulting from some of them. Lots of guesswork was involved and some part of this is probably incorrect. Some potential-lockuop situations are handled by just resetting a whole PGRAPH subunit, which doesn't sound like a "proper" solution, but seems to work just fine... for now.

Just saw such warnings like: ... (XEN) printk: 387824 messages suppressed. (XEN) seg_fixup.c:282: Taken fault at bad CS c000, IP 00003aab (XEN) seg_fixup.c:282: Taken fault at bad CS c000, IP 00003ab2 (XEN) seg_fixup.c:282: Taken fault at bad CS c000, IP 00003aab (XEN) seg_fixup.c:282: Taken fault at bad CS c000, IP 00003ab2 ... It only jumped out when switching to/off X-windows within dom0, and

For targets where ADDCARRY and SUBCARRY are legal, would it make sense to expand ADDC/UADDO/ADDE/etc. into ADDCARRY (and same for sub)? Are there plans to deprecate UADDO/USUBO in favor of ADDCARRY/SUBCARRY? -Krzysztof On 5/30/2018 11:57 AM, Amaury Séchet via llvm-dev wrote: > These opcodes have been deprecated about a year ago, but still in use in > various backend. > > In

On 5/30/2018 1:16 PM, Friedman, Eli wrote: > On 5/30/2018 10:29 AM, Krzysztof Parzyszek via llvm-dev wrote: >> For targets where ADDCARRY and SUBCARRY are legal, would it make sense >> to expand ADDC/UADDO/ADDE/etc. into ADDCARRY (and same for sub)? > > SelectionDAG will never generate ADDC/ADDE on targets where they aren't > legal.  Targets which custom-lower

On 2018-05-30 16:57, Amaury Séchet via llvm-dev wrote: > These opcodes have been deprecated about a year ago, but still in use > in various backend. > > In https://reviews.llvm.org/D47422 I would like to change the behavior > of the backend to not enable the use of these opcodes by default. The > opcode remains usable by any backend that wish to use them, but that > should

On 5/30/2018 11:28 AM, Krzysztof Parzyszek wrote: > On 5/30/2018 1:16 PM, Friedman, Eli wrote: >> On 5/30/2018 10:29 AM, Krzysztof Parzyszek via llvm-dev wrote: >>> For targets where ADDCARRY and SUBCARRY are legal, would it make >>> sense to expand ADDC/UADDO/ADDE/etc. into ADDCARRY (and same for sub)? >> >> SelectionDAG will never generate ADDC/ADDE on

On 5/30/2018 10:29 AM, Krzysztof Parzyszek via llvm-dev wrote: > For targets where ADDCARRY and SUBCARRY are legal, would it make sense > to expand ADDC/UADDO/ADDE/etc. into ADDCARRY (and same for sub)? SelectionDAG will never generate ADDC/ADDE on targets where they aren't legal.  Targets which custom-lower ADDCARRY generally also custom-lower UADDO; not sure what sort of expansion

Hey all, Does someone want to look over a super-trivial patch I just submitted? It''s just correcting a typo; someone accidentally spelled "group_by_title" as "gruop_by_title" in the category.rb model in the activerecord tests. I just fixed it in the model, and in the two places it''s referenced in the habtm test. Thanks, Ben -- You received this message

https://bugs.freedesktop.org/show_bug.cgi?id=94643 Bug ID: 94643 Summary: 4K Display on Displayport goes black when pointer hits column 0 Product: xorg Version: unspecified Hardware: x86-64 (AMD64) OS: Linux (All) Status: NEW Severity: normal Priority: medium

These opcodes have been deprecated about a year ago, but still in use in various backend. In https://reviews.llvm.org/D47422 I would like to change the behavior of the backend to not enable the use of these opcodes by default. The opcode remains usable by any backend that wish to use them, but that should limit the situation where newer backend just use them as they are enabled by default. This

If the initial data element is 0, it will never be written, even though the value from the previous method may be there. Signed-off-by: Kelly Doran <kel.p.doran at gmail.com> --- drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/gpu/drm/nouveau/core/engine/graph/nvc0.c