Bug 10924 - XAA crash on NV17
Summary: XAA crash on NV17
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/nouveau (show other bugs)
Version: unspecified
Hardware: x86 (IA32) Linux (All)
: medium normal
Assignee: Nouveau Project
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 10957
  Show dependency treegraph
 
Reported: 2007-05-12 02:16 UTC by Matthieu CASTET
Modified: 2007-08-11 05:50 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
set NV04_GDI_RECTANGLE_SET_MONOCHROME_FORMAT to avoid crash (699 bytes, patch)
2007-06-30 01:39 UTC, Matthieu CASTET
no flags Details | Splinter Review

Description Matthieu CASTET 2007-05-12 02:16:49 UTC
When using XAA mode, if I open a xterm, the X crash because of a PGRAPH error. It seems related to 
RECT_EXPAND_TWO_COLOR_DATA.



May 11 23:48:11 localhost kernel: [16461.792975] [drm:nouveau_pgraph_irq_handler
] *ERROR* NV: PGRAPH error interrupt
May 11 23:48:11 localhost kernel: [16461.792988] [drm:nouveau_pgraph_irq_handler
] *ERROR* nsource:0x00000800^Instatus:0x01000000
May 11 23:48:11 localhost kernel: [16461.792993] [drm:nouveau_pgraph_irq_handler
] *ERROR* instance:0x000011c8
May 11 23:48:11 localhost kernel: [16461.792999] [drm:nouveau_graph_dump_trap_in
fo] *ERROR* NV: nSource: 0x00000800, nStatus: 0x01000000
May 11 23:48:11 localhost kernel: [16461.793005] [drm:nouveau_graph_dump_trap_in
fo] *ERROR* NV: Channel 0/1 (class 0x804a) -Method 0x0c00, Data 0x00000000
Comment 1 Matthieu CASTET 2007-06-30 01:39:56 UTC
Created attachment 10518 [details] [review]
set NV04_GDI_RECTANGLE_SET_MONOCHROME_FORMAT to avoid crash

The problem is that to get correct output, I should set the wrong big endian order
Comment 2 Matthieu CASTET 2007-06-30 01:41:33 UTC
The problem still happen with last git version.
Comment 3 Matthieu CASTET 2007-08-11 05:50:11 UTC
The patch is commited in git. Work for nv17.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.