https://bugs.freedesktop.org/show_bug.cgi?id=32688
Summary: Some games have a wireframe or outline visible
Product: Mesa
Version: git
Platform: Other
URL: http://www.amnesiagame.com/
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: sa(a)whiz.se
Created an attachment (id=…
[View More]41478)
--> (https://bugs.freedesktop.org/attachment.cgi?id=41478)
Screenshot of bug in Amnesia
Some games have some sort of visible wireframe, or an outline visible when
r300g is used (softpipe does not have this problem). I'm pretty sure this is a
known bug, but I haven't found any open bug reports about it.
This bug is very noticeable in the game Amnesia (where the screenshot is from).
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: e9928fe036e9382fd7bc353f3f05531445f08977
-- xserver: 1.9.0.902 (1.9.1 RC 2)
-- mesa: b832ae8a4a77563c50a6e82c49b4732f6a0dbf11
-- drm: 2.4.22
-- kernel: 2.6.36
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=32945
Summary: Lower part of the screen corrupt with HyperZ enabled
Product: Mesa
Version: git
Platform: Other
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: sa(a)whiz.se
Created an attachment (id=41815)
--> (https://bugs.freedesktop.…
[View More]org/attachment.cgi?id=41815)
Screenshot of gears
When HyperZ is used on my RV570 the lower part of the screen isn't rendered
correctly. I'm attaching a screenshot of glxgears, but it's also visible in
most real-world games and apps.
I'm not sure if this is the same as bug 29851 since the hardware differs.
(HyperZ gives a pretty nice performance boost otherwise, about a 30% fps
increase with Doom 3 in 1680x1050!)
System environment:
-- system architecture: 32-bit
-- Linux distribution: Debian unstable
-- GPU: RV570
-- Model: Asus EAX1950Pro 256MB
-- Display connector: DVI
-- xf86-video-ati: 6.13.2
-- xserver: 1.9.2
-- mesa: ac6306e9ca904ae9674bf2a15222efe4cb861bf5
-- drm: 2.4.23
-- kernel: 2.6.37
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
Hello,
Since 2.6.38-rc I get screen corruption (mostly horizontal grabage stripes on
the right side of the screen). After a long time bisecting the offending commit
ends up being:
commit a00b10c360b35d6431a94cbf130a4e162870d661
Author: Chris Wilson <chris(a)chris-wilson.co.uk>
Date: Fri Sep 24 21:15:47 2010 +0100
drm/i915: Only enforce fence limits inside the GTT.
So long as we adhere to the fence registers rules for alignment and no
overlaps (including with unfenced …
[View More]accesses to linear memory) and account
for the tiled access in our size allocation, we do not have to allocate
the full fenced region for the object. This allows us to fight the bloat
tiling imposed on pre-i965 chipsets and frees up RAM for real use. [Inside
the GTT we still suffer the additional alignment constraints, so it doesn't
magic allow us to render larger scenes without stalls -- we need the
expanded GTT and fence pipelining to overcome those...]
Signed-off-by: Chris Wilson <chris(a)chris-wilson.co.uk>
This commit caused other problems too, which Daniel tried to fix with commits:
5e78330126e23e00950 drm/i915: fix relaxed tiling for gen <= 3 && !g33
75e9e9158f38e5cb21e drm/i915: kill mappable/fenceable disdinction
818f2a3cc34b0673dcc drm/i915: revert pageflip/mappable related abi breakage
But those don't fix my screen corruption.
Unfortunately, it's a big commit and it doesn't revert cleanly, and its size
makes it unclear what the source of the problem is. Daniel's commits don't
revert cleanly either, so reverting all of them didn't work.
I'll start poking at it and see if I can find anything.
Greetings,
Indan
[View Less]
Signed-off-by: Alex Riesen <raa.lkml(a)gmail.com>
---
Linus Torvalds, Wed, Feb 16, 2011 05:16:01 +0100:
> Most of the changes are pretty spread out and small, with drivers/gpu
> (radeon and i915) somewhat standing out from the pack. ...
The backlight level on this Dell XPS M1330 reduces every time I reopen the
lid, and BIOS does not seem to know anything about that (the keyboard
shortcuts to set backlight brightness cause it to jump to the level next to
the one set before closing …
[View More]the lid).
Maybe i915 code for LVDS panels have lost some parts of the backlight
enable/disable balancing patch by Chris Wilson? Or maybe it just got broken
along the way...
This part of the patch by Chris helped here, but I afraid it might be not
complete or just wrong (for instance, the original patch didn't have to remove
the i915_read_blc_pwm_ctl function).
drivers/gpu/drm/i915/intel_panel.c | 65 ++++++++++--------------------------
1 files changed, 18 insertions(+), 47 deletions(-)
diff --git a/drivers/gpu/drm/i915/intel_panel.c b/drivers/gpu/drm/i915/intel_panel.c
index c65992d..c4b1ca4 100644
--- a/drivers/gpu/drm/i915/intel_panel.c
+++ b/drivers/gpu/drm/i915/intel_panel.c
@@ -125,55 +125,15 @@ static int is_backlight_combination_mode(struct drm_device *dev)
return 0;
}
-static u32 i915_read_blc_pwm_ctl(struct drm_i915_private *dev_priv)
-{
- u32 val;
-
- /* Restore the CTL value if it lost, e.g. GPU reset */
-
- if (HAS_PCH_SPLIT(dev_priv->dev)) {
- val = I915_READ(BLC_PWM_PCH_CTL2);
- if (dev_priv->saveBLC_PWM_CTL2 == 0) {
- dev_priv->saveBLC_PWM_CTL2 = val;
- } else if (val == 0) {
- I915_WRITE(BLC_PWM_PCH_CTL2,
- dev_priv->saveBLC_PWM_CTL);
- val = dev_priv->saveBLC_PWM_CTL;
- }
- } else {
- val = I915_READ(BLC_PWM_CTL);
- if (dev_priv->saveBLC_PWM_CTL == 0) {
- dev_priv->saveBLC_PWM_CTL = val;
- dev_priv->saveBLC_PWM_CTL2 = I915_READ(BLC_PWM_CTL2);
- } else if (val == 0) {
- I915_WRITE(BLC_PWM_CTL,
- dev_priv->saveBLC_PWM_CTL);
- I915_WRITE(BLC_PWM_CTL2,
- dev_priv->saveBLC_PWM_CTL2);
- val = dev_priv->saveBLC_PWM_CTL;
- }
- }
-
- return val;
-}
-
u32 intel_panel_get_max_backlight(struct drm_device *dev)
{
struct drm_i915_private *dev_priv = dev->dev_private;
u32 max;
- max = i915_read_blc_pwm_ctl(dev_priv);
- if (max == 0) {
- /* XXX add code here to query mode clock or hardware clock
- * and program max PWM appropriately.
- */
- printk_once(KERN_WARNING "fixme: max PWM is zero.\n");
- return 1;
- }
-
if (HAS_PCH_SPLIT(dev)) {
- max >>= 16;
+ max = I915_READ(BLC_PWM_PCH_CTL2) >> 16;
} else {
+ max = I915_READ(BLC_PWM_CTL);
if (IS_PINEVIEW(dev)) {
max >>= 17;
} else {
@@ -186,6 +146,14 @@ u32 intel_panel_get_max_backlight(struct drm_device *dev)
max *= 0xff;
}
+ if (max == 0) {
+ /* XXX add code here to query mode clock or hardware clock
+ * and program max PWM appropriately.
+ */
+ DRM_ERROR("fixme: max PWM is zero.\n");
+ max = 1;
+ }
+
DRM_DEBUG_DRIVER("max backlight PWM = %d\n", max);
return max;
}
@@ -255,11 +223,11 @@ void intel_panel_disable_backlight(struct drm_device *dev)
{
struct drm_i915_private *dev_priv = dev->dev_private;
- if (dev_priv->backlight_enabled) {
- dev_priv->backlight_level = intel_panel_get_backlight(dev);
- dev_priv->backlight_enabled = false;
- }
+ if (!dev_priv->backlight_enabled)
+ return;
+ dev_priv->backlight_enabled = false;
+ dev_priv->backlight_level = intel_panel_get_backlight(dev);
intel_panel_set_backlight(dev, 0);
}
@@ -267,6 +235,9 @@ void intel_panel_enable_backlight(struct drm_device *dev)
{
struct drm_i915_private *dev_priv = dev->dev_private;
+ if (dev_priv->backlight_enabled)
+ return;
+
if (dev_priv->backlight_level == 0)
dev_priv->backlight_level = intel_panel_get_max_backlight(dev);
@@ -278,6 +249,6 @@ void intel_panel_setup_backlight(struct drm_device *dev)
{
struct drm_i915_private *dev_priv = dev->dev_private;
- dev_priv->backlight_level = intel_panel_get_backlight(dev);
+ dev_priv->backlight_level = intel_panel_get_max_backlight(dev);
dev_priv->backlight_enabled = dev_priv->backlight_level != 0;
}
--
1.7.4.27.gf5729
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=28995
Summary: [r300g] dri rejects command buffers
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: All
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/DRI/r300
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: aaalmosss(a)gmail.com
In some games hexadecimal numbers are printed into the console, rendering
…
[View More]errors occur and performance drops significantly. Affected games: VDrift,
Nexuiz, certain levels in Sauerbraten (eg. venice), certain places in Doom3.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=33075
Summary: [Runescape] "low detail" lighting option makes
character models disappear
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: Drivers/Gallium/r600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: bpaterni(a)gmail.com
…
[View More]This bug appears in the browser-, java-based MMORPG game, runescape (you may or
may not be familiar with it) The game provides an OpenGL mode if it detects
your graphics drivers are capable, which it does now with r600g from mesa git
master.
In order to reproduce this bug, you will need to create an account at
runescape.com which should be a trivial process. After that, you should be able
to enter the game and driver autodection should recognize that r600g is capable
of driving runescape. Lighting detail defaults to "high" on my machine, so you
will need to find the display options interface in-game and make sure low
detail is selected. Now you should see that all characters have been "removed"
from display, but ground and other geometry remain drawn.
Linux desktop 2.6.37+ #4 SMP PREEMPT Tue Jan 11 15:01:00 CST 2011 x86_64
GNU/Linux
OpenGL renderer string: Gallium 0.4 on AMD RV770
Mozilla Iceweasel 3.6.13
OpenJDK Runtime Environment (IcedTea6 1.9.2) (6b20-1.9.2-2)
Let me know if there's anything else I can do.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=31391
Summary: Heroes of Newerth crashes with cs parser error
Product: Mesa
Version: git
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Keywords: regression
Severity: normal
Priority: medium
Component: Drivers/DRI/R600
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: stephan(a)ehilb.de
The game Heroes of …
[View More]Newerth (also referred to as HoN) crashes in certain
circumstances with the following error message in dmesg:
[ 1797.294324] [drm:radeon_cs_parser_init] *ERROR* cs IB too big: 26607
[ 1797.294327] [drm:radeon_cs_ioctl] *ERROR* Failed to initialize parser !
It's occuring during normal gameplay in situations with high graphic workload
(as far as I can tell).
I was up until recently using older libs for playing HoN with the r600 driver
and thus noticed this bug as a regression.
It is possible to reproduce the bug quite reliably by following these steps:
1. Start HoN
2. Create a practice game
3. Select a slot and start the game
4. Select any hero and wait for the countdown or skip the countdown by pressing
ready
5. As the game starts, open the test-menu at the top left of the screen and
press the “Spawn”-button right of where it reads “Creeps” multiple times
(~20-30 times). There should be spawning many creeps at your base.
6. Pan the viewport to include as many creeps as possible.
7. Press the “Kill”-button right next to the “Spawn”-button.
8. 1-2 seconds later the game crashes.
9. You notice the error messages in dmesg
Bisecting issued the following bad commit:
e62e5b0922b6554431234a8a71c7aec7cff91864 is the first bad commit
commit e62e5b0922b6554431234a8a71c7aec7cff91864
Author: Andre Maasikas <amaasikas(a)gmail.com>
Date: Wed Aug 11 14:30:18 2010 +0300
r600: add support for draw_elements_base_vertex
use VTX_BASE_VTX_LOC for offset, last time using INDEX_OFFSET was
probably a wrong register for this
:040000 040000 2daa2236ba96c969c80cd62b1199d0eacb56ecce
376ee1345c8cbbb51c2b1c36cb7adafac276d5d6 M src
I tried to the best of my ability to manually revert the commit and it proved
to be the cause of the bug.
I'm running mesa-git right now with that commit manually reverted and HoN is
running fine.
Note: This might be the same bug as described in this comment:
https://bugs.freedesktop.org/show_bug.cgi?id=25114#c7
Let me know if there is any information missing.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=33042
Summary: RV770: Broken Mipmap creation/display
Product: DRI
Version: unspecified
Platform: x86-64 (AMD64)
OS/Version: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Radeon
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: andreas.bombe(a)mytum.de
Created an attachment (id=41946)
--> (https://bugs.…
[View More]freedesktop.org/attachment.cgi?id=41946)
Celestia screenshot
I'm using mainline Linux kernels, and this bug is a regression from 2.6.36. It
got broken already in 37-rc series but I haven't noticed it (compiz desktop
works fine) and didn't get around to report it in time.
The latest kernel I've tested is 2.6.37-05292-g7bc4a4c running Debian sid.
It appears that the vertical size assumed during display of the mipmap is twice
the mipmap's height. See attached screenshot from Celestia which shows the
first level mipmap on the central star. Horizontal size seems to be correct.
Zooming outward reveals further mipmap levels with unrelated data as can be
seen on the other two stars in the image.
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]
Hello,
starting with 2.6.36 my monitor detects a resolution of 1920x1199
instead of 1920x1200. The monitor displays 1920x1199 on its OSD, and as
a result, I guess, the display is blurred in the middle section (top to
down) - most likely due to stretching applied by the monitor.
This issue shows up when loading i915 (KMS enabled) with 2.6.37 and
2.6.36 (also 2.6.36.2). With 2.6.35 (up to 2.6.35.10) the monitor
correctly detects (and displays on OSD) 1920x1200 and doesn't blur
anything.
The …
[View More]Chipset is an Intel G35 on an Asus P5E-V HDMI, the monitor is a
Yuraku YV24WBH1 connected via DVI (DVI to HDMI adapter, the board
doesn't have a separate DVI port).
The `fbset' output with 2.6.37 and 2.6.35.10 doesn't differ:
mode "1920x1200"
geometry 1920 1200 1920 1200 32
timings 0 0 0 0 0 0 0
rgba 8/16,8/8,8/0,0/0
endmode
dmesg excerpt for 2.6.37:
[ 2.733019] efifb: probing for efifb
[ 2.744452] efifb: framebuffer at 0xd0000000, mapped to 0xf8280000, using 7552k, total 7552k
[ 2.769712] efifb: mode is 1600x1200x32, linelength=6400, pages=1
[ 2.787964] efifb: scrolling: redraw
[ 2.798678] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 2.927422] fb0: EFI VGA frame buffer device
[ 71.202957] [drm] Initialized drm 1.1.0 20060810
[ 71.374419] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 71.374423] i915 0000:00:02.0: setting latency timer to 64
[ 71.474329] i915 0000:00:02.0: irq 44 for MSI/MSI-X
[ 71.669097] [drm] initialized overlay support
[ 71.942025] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver
[ 72.223827] fb0: inteldrmfb frame buffer device
[ 72.223829] drm: registered panic notifier
[ 72.223961] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
[ 87.492007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 87.572007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 87.652006] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 87.732007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 87.812007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 87.892007] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 87.972008] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 88.052006] [drm] GMBUS timed out, falling back to bit banging on pin 0 [i915 gmbus disabled]
[ 89.692006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
[ 89.772006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
[ 89.852006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
[ 89.932007] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
[ 90.012007] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
[ 90.092006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
[ 90.172006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
[ 90.252006] [drm] GMBUS timed out, falling back to bit banging on pin 6 [i915 gmbus reserved]
dmesg excerpt for 2.6.35.10:
[ 3.401792] efifb: probing for efifb
[ 3.412804] efifb: framebuffer at 0xd0000000, mapped to 0xf8280000, using 3072k, total 3072k
[ 3.438065] efifb: mode is 1024x768x32, linelength=4096, pages=1
[ 3.456058] efifb: scrolling: redraw
[ 3.466773] efifb: Truecolor: size=8:8:8:8, shift=24:16:8:0
[ 3.540728] fb0: EFI VGA frame buffer device
[ 52.667436] [drm] Initialized drm 1.1.0 20060810
[ 52.824746] i915 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
[ 52.824750] i915 0000:00:02.0: setting latency timer to 64
[ 52.901066] i915 0000:00:02.0: irq 47 for MSI/MSI-X
[ 52.901076] [drm] set up 7M of stolen space
[ 53.255059] [drm] initialized overlay support
[ 53.806061] fb: conflicting fb hw usage inteldrmfb vs EFI VGA - removing generic driver
[ 54.171524] fb0: inteldrmfb frame buffer device
[ 54.171525] drm: registered panic notifier
[ 54.171681] [drm] Initialized i915 1.6.0 20080730 for 0000:00:02.0 on minor 0
The monitor's EDID information via `get-edid | parse-edid':
# EDID version 1 revision 3
Section "Monitor"
# Block type: 2:0 3:fc
Identifier "MB24W"
VendorName "NTS"
ModelName "MB24W"
# Block type: 2:0 3:fc
# Block type: 2:0 3:fd
HorizSync 30-74
VertRefresh 50-61
# Max dot clock (video bandwidth) 160 MHz
# Block type: 2:0 3:ff
# DPMS capabilities: Active off:yes Suspend:no Standby:no
Mode "1920x1200" # vfreq 59.950Hz, hfreq 74.038kHz
DotClock 154.000000
HTimings 1920 1968 2000 2080
VTimings 1200 1203 1209 1235
Flags "-HSync" "+VSync"
EndMode
# Block type: 2:0 3:fc
# Block type: 2:0 3:fd
# Block type: 2:0 3:ff
EndSection
PS: I mailed this to lkml about a week ago, maybe dri-devel@ will suit
better?
regards
Mario
--
File names are infinite in length where infinity is set to 255 characters.
-- Peter Collinson, "The Unix File System"
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=32889
Summary: [i915g] SIGSEGV
src/gallium/drivers/i915/i915_state_emit.c:414
Product: Mesa
Version: git
Platform: x86 (IA32)
OS/Version: Linux (All)
Status: NEW
Severity: critical
Priority: medium
Component: Drivers/Gallium/i915g
AssignedTo: dri-devel(a)lists.freedesktop.org
ReportedBy: vlee(a)vmware.com
mesa: …
[View More]6d9ca78ef7bf831b9b63f4bda68623cbae627508 (master)
chipset: 945GM (Intel GMA 950)
system architecture: i686
xserver-xorg-video-intel: 2:2.12.0-1ubuntu5.1
libdrm-intel1: 2.4.21-1ubuntu2.1
kernel version: 2.6.35-24-generic
Linux distribution: Ubuntu 10.10 i386
Run piglit fbo-blit-d24s8 test.
$ ./bin/fbo-blit-d24s8 -auto
Segmentation fault (core dumped)
Program terminated with signal 11, Segmentation fault.
#0 0x01102b3b in i915_emit_hardware_state (i915=0x8a6e370) at
src/gallium/drivers/i915/i915_state_emit.c:414
414 struct i915_texture *tex = i915_texture(cbuf_surface->texture);
(gdb) bt
#0 0x01102b3b in i915_emit_hardware_state (i915=0x8a6e370) at
src/gallium/drivers/i915/i915_state_emit.c:414
#1 0x010fe0e6 in i915_vbuf_render_draw_arrays (render=0x8a84788, start=0,
nr=4) at src/gallium/drivers/i915/i915_prim_vbuf.c:516
#2 0x01194f9d in draw_pt_emit_linear (emit=0x8a6ad30, vert_info=0xbff42328,
prim_info=0xbff4239c) at src/gallium/auxiliary/draw/draw_pt_emit.c:265
#3 0x0112fc82 in emit (emit=0x8a6ad30, vert_info=0xbff42328,
prim_info=0xbff4239c) at
src/gallium/auxiliary/draw/draw_pt_fetch_shade_pipeline.c:168
#4 0x01130023 in fetch_pipeline_generic (middle=0x8a6acc8, fetch_info=0x0,
prim_info=0xbff4239c) at
src/gallium/auxiliary/draw/draw_pt_fetch_shade_pipeline.c:286
#5 0x01130144 in fetch_pipeline_linear_run (middle=0x8a6acc8, start=0,
count=4, prim_flags=0) at
src/gallium/auxiliary/draw/draw_pt_fetch_shade_pipeline.c:345
#6 0x01135155 in vsplit_segment_simple_linear (vsplit=0x8a7ee30, flags=0,
istart=0, icount=4) at src/gallium/auxiliary/draw/draw_pt_vsplit_tmp.h:229
#7 0x011354ee in vsplit_run_linear (frontend=0x8a7ee30, start=0, count=4) at
src/gallium/auxiliary/draw/draw_split_tmp.h:61
#8 0x0112d494 in draw_pt_arrays (draw=0x8a69348, prim=6, start=0, count=4) at
src/gallium/auxiliary/draw/draw_pt.c:113
#9 0x0112e049 in draw_vbo (draw=0x8a69348, info=0xbff425a4) at
src/gallium/auxiliary/draw/draw_pt.c:481
#10 0x010fc5d3 in i915_draw_vbo (pipe=0x8a6e370, info=0xbff425a4) at
src/gallium/drivers/i915/i915_context.c:81
#11 0x019d3690 in util_draw_arrays (pipe=0x8a6e370, mode=6, start=0, count=4)
at src/gallium/auxiliary/util/u_draw.h:58
#12 0x019d3757 in util_draw_vertex_buffer (pipe=0x8a6e370, vbuf=0x8b17920,
offset=0, prim_type=6, num_verts=4, num_attribs=2) at
src/gallium/auxiliary/util/u_draw_quad.c:63
#13 0x01952f15 in draw_quad (st=0x8ad80a0, x0=-1, y0=-1, x1=1, y1=1,
z=0.54321003, color=0x8a97324) at src/mesa/state_tracker/st_cb_clear.c:175
#14 0x019535be in clear_with_quad (ctx=0x8a96618, color=0 '\000', depth=2
'\002', stencil=4 '\004') at src/mesa/state_tracker/st_cb_clear.c:299
#15 0x01953cfd in st_Clear (ctx=0x8a96618, mask=48) at
src/mesa/state_tracker/st_cb_clear.c:530
#16 0x018ddbb0 in _mesa_Clear (mask=1280) at src/mesa/main/clear.c:242
#17 0x0804b907 in run_test () at piglit/tests/fbo/fbo-blit-d24s8.c:179
#18 0x0804bce9 in piglit_display () at piglit/tests/fbo/fbo-blit-d24s8.c:242
#19 0x0804dce3 in display () at piglit/tests/util/piglit-framework.c:52
#20 0x002d2820 in fghRedrawWindow (window=DWARF-2 expression error: DW_OP_reg
operations must be used either alone or in conjuction with DW_OP_piece or
DW_OP_bit_piece.
) at freeglut_main.c:210
#21 fghcbDisplayWindow (window=DWARF-2 expression error: DW_OP_reg operations
must be used either alone or in conjuction with DW_OP_piece or DW_OP_bit_piece.
) at freeglut_main.c:227
#22 0x002d6660 in fgEnumWindows (enumCallback=0x2d2790 <fghcbDisplayWindow>,
enumerator=0xbff42948) at freeglut_structure.c:394
#23 0x002d2cdb in fghDisplayAll () at freeglut_main.c:249
#24 glutMainLoopEvent () at freeglut_main.c:1450
#25 0x002d3605 in glutMainLoop () at freeglut_main.c:1498
#26 0x0804de8c in main (argc=1, argv=0xbff42bd4) at
piglit/tests/util/piglit-framework.c:118
(gdb) frame 0
#0 0x01102b3b in i915_emit_hardware_state (i915=0x8a6e370) at
src/gallium/drivers/i915/i915_state_emit.c:414
414 struct i915_texture *tex = i915_texture(cbuf_surface->texture);
(gdb) print cbuf_surface
$1 = (struct pipe_surface *) 0x0
--
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
[View Less]