https://bugs.freedesktop.org/show_bug.cgi?id=37928
Summary: foobillard has rendering errors (regression)
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: aaalmosss(a)gmail.com
Created an attachment (id=47535)
--> (https://bugs.freedesktop.…
[View More]org/attachment.cgi?id=47535)
foobillard.png
Recently foobillard started to look like on the screenshot. About a month ago
it was fine.
This is written in dmesg:
[ 536.002852] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[ 536.002859] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[ 536.002863] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[ 536.014942] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[ 536.014950] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[ 536.014953] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[ 536.017284] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[ 536.017292] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[ 536.017296] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[ 536.020344] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[ 536.020352] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[ 536.020355] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[ 536.051539] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 131072 have 90112) !
[ 536.051546] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (256 2 0 256)
[ 536.051550] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[ 536.142308] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 16384 have 12288) !
[ 536.142316] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (256 2 0 32)
[ 536.142319] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
[ 536.223631] [drm:r100_cs_track_check] *ERROR* [drm] Buffer too small for z
buffer (need 32768 have 24576) !
[ 536.223639] [drm:r100_cs_track_check] *ERROR* [drm] zbuffer (128 2 0 128)
[ 536.223642] [drm:radeon_cs_ioctl] *ERROR* Invalid command stream !
#36934 might be related.
--
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]
Hi Linus,
This is just radeon fixes, but it contains some new hw support so I've put
it outside my normal pull in case you feel its not timely.
New HW:
AMD LLano APU, this is the new Fusion part from AMD so the patches add
pci ids and internal driver tables.
It also has a patch to bring the cayman support into line with all the
other chips so it uses the proper blit support.
Otherwise its all just fixes, the pageflipping one is pretty serious lots
of sightings in F15, and the viewport …
[View More]height one affects some laptops iwth
wierd sized panels (945 high).
Dave.
The following changes since commit 2ec8a5feaf3000bf4f9744d0caad0d5f12ce1409:
drivers/gpu/drm/radeon/atom.c: fix warning (2011-05-24 09:00:37 +1000)
are available in the git repository at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/airlied/drm-2.6.git drm-radeon-fixes
Alex Deucher (12):
drm/radeon/kms/blit: workaround some hw issues on evergreen+
drm/radeon/kms: add blit support for cayman (v2)
drm/radeon/kms: add missing case for cayman thermal sensor
drm/radeon/kms: fix thermal sensor reading on juniper
drm/radeon/kms: clean up the radeon kms Kconfig
drm/radeon/kms: add family ids for llano APUs
drm/radeon/kms: fill in asic struct for llano
drm/radeon/kms: add llano pci ids
drm/radeon/kms: add support for Llano Fusion APUs
drm/radeon/kms: remove duplicate reg from r600 safe regs
drm/radeon/kms: viewport height has to be even
drm/radeon/kms/atom: fix PHY init
Dave Airlie (1):
drm/radeon: fix oops in ttm reserve when pageflipping (v2)
Marek Olšák (1):
drm/radeon/kms: add missing Evergreen texture formats to the CS parser
drivers/gpu/drm/radeon/Kconfig | 9 +-
drivers/gpu/drm/radeon/atombios_crtc.c | 12 +-
drivers/gpu/drm/radeon/cayman_blit_shaders.c | 326 +++++++++++++++-
drivers/gpu/drm/radeon/cayman_blit_shaders.h | 3 +
drivers/gpu/drm/radeon/evergreen.c | 104 ++++-
drivers/gpu/drm/radeon/evergreen_blit_kms.c | 561 +++++++++++++++-----------
drivers/gpu/drm/radeon/evergreend.h | 8 +-
drivers/gpu/drm/radeon/ni.c | 13 +-
drivers/gpu/drm/radeon/r600.c | 12 +
drivers/gpu/drm/radeon/r600_cs.c | 28 +-
drivers/gpu/drm/radeon/r600d.h | 3 +
drivers/gpu/drm/radeon/radeon_asic.c | 8 +-
drivers/gpu/drm/radeon/radeon_device.c | 2 +
drivers/gpu/drm/radeon/radeon_display.c | 13 +-
drivers/gpu/drm/radeon/radeon_encoders.c | 17 +-
drivers/gpu/drm/radeon/radeon_family.h | 2 +
drivers/gpu/drm/radeon/radeon_pm.c | 1 +
drivers/gpu/drm/radeon/reg_srcs/r600 | 1 -
include/drm/drm_pciids.h | 11 +
19 files changed, 830 insertions(+), 304 deletions(-)
[View Less]
Mostly mode setting cleanups and fixes.
The following changes since commit 55922c9d1b84b89cb946c777fddccb3247e7df2c:
Linux 3.0-rc1 (2011-05-29 17:43:36 -0700)
are available in the git repository at:
ssh://master.kernel.org/pub/scm/linux/kernel/git/keithp/linux-2.6.git drm-intel-fixes
Chris Wilson (5):
drm/i915: s/addr & ~PAGE_MASK/offset_in_page(addr)/
drm/i915: Replace ironlake_compute_wm0 with g4x_compute_wm0
drm/i915/crt: Explicitly return false if connected to …
[View More]a digital monitor
drm/i915: Remove unused enum "chip_family"
drm/i915: Share the common force-audio property between connectors
Dan Carpenter (1):
drm/i915: fix if statement in ivybridge irq handler
Daniel Vetter (2):
drm/i915: Only print out the actual number of fences for i915_error_state
drm/915: fix relaxed tiling on gen2: tile height
Hans de Goede (1):
drm/i915: Add a no lvds quirk for the Asus EeeBox PC EB1007
Jason Stubbs (1):
drm/i915: fix regression after clock gating init split
Nicolas Kaiser (1):
drm: i915: correct return status in intel_hdmi_mode_valid()
drivers/gpu/drm/i915/i915_debugfs.c | 2 +-
drivers/gpu/drm/i915/i915_drv.h | 8 +---
drivers/gpu/drm/i915/i915_gem.c | 26 +++++-----
drivers/gpu/drm/i915/i915_irq.c | 2 +-
drivers/gpu/drm/i915/intel_crt.c | 4 ++
drivers/gpu/drm/i915/intel_display.c | 89 ++++++++--------------------------
drivers/gpu/drm/i915/intel_dp.c | 15 +-----
drivers/gpu/drm/i915/intel_drv.h | 1 +
drivers/gpu/drm/i915/intel_hdmi.c | 16 +-----
drivers/gpu/drm/i915/intel_lvds.c | 8 +++
drivers/gpu/drm/i915/intel_modes.c | 30 +++++++++++
drivers/gpu/drm/i915/intel_sdvo.c | 14 +-----
12 files changed, 87 insertions(+), 128 deletions(-)
--
keith.packard(a)intel.com
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=33389
Summary: Amesia (closed source game) segfaults
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: r0ugh_l(a)yahoo.de
When trying to run Amnesia (http://www.amnesiagame.com/#…
[View More]demo) on my system it
gives me this output:
[1] 619 segmentation fault ./Amnesia.bin64
It runs fine until the loading screen and then crashes.
Steps to reproduce:
Run Amnesia with r600 driver
Additional information:
It doesn't crash if I'm using the llvm-pipe driver. I've tested it at the
lowest possible graphics settings.
Backtrace:
#0 0x000000000082ab08 in hpl::iParticleEmitter::GetMaterial() ()
#1 0x0000000000805de2 in
hpl::iRenderer::RenderObjectZAndAddToRenderList(hpl::iRenderable*) ()
#2 0x0000000000805e59 in
hpl::iRenderer::RenderObjectZAndAddToRenderListStaticCallback(hpl::iRenderer*,
hpl::iRenderable*) ()
#3 0x0000000000807d8f in
hpl::iRenderer::RenderAndAddNodeObjects(hpl::iRenderableContainerNode*, bool
(*)(hpl::iRenderer*, hpl::iRenderable*), unsigned int) ()
#4 0x000000000080808a in
hpl::iRenderer::CheckForVisibleObjectsAddToListAndRenderZ(hpl::cVisibleRCNodeTracker*,
unsigned int, unsigned int, bool, bool (*)(hpl::iRenderer*, hpl::iRenderable*))
()
#5 0x00000000007e4841 in hpl::cRendererDeferred::RenderObjects() ()
#6 0x0000000000809334 in hpl::iRenderer::Render(float, hpl::cFrustum*,
hpl::cWorld*, hpl::cRenderSettings*, hpl::cRenderTarget*, bool,
std::list<hpl::iRendererCallback*, std::allocator<hpl::iRendererCallback*> >*)
()
#7 0x000000000082496d in hpl::cScene::Render(float, unsigned int) ()
#8 0x0000000000925423 in hpl::cEngine::Run() ()
#9 0x0000000000689890 in hplMain(std::basic_string<char,
std::char_traits<char>, std::allocator<char> > const&) ()
#10 0x000000000090ff29 in main ()
Version Information:
mesa: git 835c4ea1053730c8eea98337c9da1b14fcff6b5e
OpenGL vendor string: X.Org
OpenGL renderer string: Gallium 0.4 on AMD RV770
OpenGL version string: 2.1 Mesa 7.11-devel
OpenGL shading language version string: 1.20
--
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]
Hi,
since printk_ratelimit() shouldn't be used anymore, I replaced it at several
points, where it was possible with printk_ratelimited(FMT,...). This shouldn't
change the behaviour in most cases, except that the printk will use an local
ratelimit instead of an global one shared with all other printk_ratelimit
calls.
I just must made patches for a few places where it is used. If you think that
it is worth converting all printk_ratelimits, i will send more patches. The
changes where done …
[View More]against v3.0-rc1-106-g4f1ba49.
greetz chris
Christian Dietrich (8):
powerpc/rtas-rtc: remove sideeffects of printk_ratelimit
drivers/octeon: use printk_ratelimited instead of printk_ratelimit
scsi/sg: use printk_ratelimited instead of printk_ratelimit
md/raid: use printk_ratelimited instead of printk_ratelimit
drivers/char/rtc: use printk_ratelimited instead of printk_ratelimit
drivers/gpu/drm: use printk_ratelimited instead of printk_ratelimit
arch/powerpc: use printk_ratelimited instead of printk_ratelimit
arch/x86: use printk_ratelimited instead of printk_ratelimit
arch/powerpc/kernel/rtas-rtc.c | 29 +++++++++------
arch/powerpc/kernel/signal_32.c | 57 +++++++++++++++++--------------
arch/powerpc/kernel/signal_64.c | 17 +++++----
arch/powerpc/kernel/traps.c | 22 +++++------
arch/powerpc/mm/fault.c | 10 +++---
arch/powerpc/sysdev/mpic.c | 11 +++---
arch/x86/kernel/hpet.c | 6 ++--
arch/x86/kernel/irq.c | 9 ++---
arch/x86/kvm/i8259.c | 7 ++--
arch/x86/lguest/boot.c | 6 ++--
drivers/char/rtc.c | 7 ++--
drivers/gpu/drm/drm_ioc32.c | 9 +++--
drivers/md/raid1.c | 22 ++++++-----
drivers/md/raid10.c | 22 ++++++-----
drivers/md/raid5.c | 39 ++++++++++-----------
drivers/scsi/sg.c | 18 +++++----
drivers/staging/octeon/ethernet-mdio.c | 27 +++++++-------
drivers/staging/octeon/ethernet-rgmii.c | 33 +++++++++---------
drivers/staging/octeon/ethernet-rx.c | 24 +++++++------
drivers/staging/octeon/ethernet-sgmii.c | 14 ++++---
drivers/staging/octeon/ethernet-tx.c | 11 +++---
drivers/staging/octeon/ethernet-util.h | 4 --
drivers/staging/octeon/ethernet-xaui.c | 22 ++++++-----
23 files changed, 221 insertions(+), 205 deletions(-)
[View Less]
Hello gurus,
I have two question mostly regarding libdrm_intel
1/ What is the difference between drm_intel_bo_map and drm_intel_gem_bo_map_gtt ?
2/ Will it be possible (or is it already possible) to directly share a regularly allocated piece of physical memory? Typical use case is the following one using OpenCL API:
char *ptr = malloc(sz);
cl_mem buf = clCreateBuffer(ctx, CL_MEM_USE_HOST_PTR, sz, ptr, &err);
Here, you create a buffer which directly uses the physical memory you are going …
[View More]to use for ptr. The idea, I guess, is to give GTT pages for this piece of memory. Today, I get a similar functionnality the other way using mostly:
drm_intel_bo *bo = drm_intel_bo_alloc(..)
char *ptr = drm_intel_bo_map(...)
Thanks!
Ben
[View Less]
Here's most of the patches I'm hoping to land in 2.6.40:
* Ivybridge support (Gen7)
* Forcewake fixes for Sandybridge (And ivybridge).
* Temporary FB for load detect (hoping for some cleanups here)
Still pending:
* More modesetting cleanups (as always)
* Disabling FBC on Ironlake to enable RC6 instead
This sequence also assigns me as the the drm/i915 maintainer.
The following changes since commit 2fb4e61d9471867677c97bf11dba8f1e9dfa7f7c:
drm/i915/lvds: Only act on lid notify when …
[View More]the device is on (2011-05-09 09:13:22 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/keithp/linux-2.6.git drm-intel-next
Ben Widawsky (10):
drm/i915: fix ilk rc6 teardown locking
drm/1915: ringbuffer wait for idle function
drm/i915: fix rc6 initialization on Ironlake
drm/i915: debugfs for context information
drm/i915: proper use of forcewake
drm/i915: reference counted forcewake
drm/i915: forcewake struct mutex locking fixes
drm/i915: move gen6 rps handling to workqueue
drm/i915: debugfs interface for forcewake reference count
drm/i915: forcewake debugfs fix
Chris Wilson (12):
drm/i915: Move the irq wait queue initialisation into the ring init
drm/i915: Simplify return value from intel_get_load_detect_pipe
drm/i915: Propagate failure to set mode for load-detect pipe
drm/i915: Don't store temporary load-detect variables in the generic encoder
drm/i915: Remove unused supported_crtc from intel_load_detect_pipe
drm/i915: Pass the saved adjusted_mode when adding to the load-detect crtc
drm/i915: Remove dead code from intel_get_load_detect_pipe()
drm/i915: Remove dead code from intel_release_load_detect_pipe()
drm/i915: Attach a fb to the load-detect pipe
drm/i915: Rename agp_type to cache_level
drm/i915: Do not clflush snooped objects
drm/i915: Disable all outputs early, before KMS takeover
Eric Anholt (12):
drm/i915: Split the crtc_mode_set function along HAS_PCH_SPLIT() lines.
drm/i915: Move the vblank pre/post modeset to the common crtc_mode_set.
drm/i915: Remove the PCH paths from the pre-Ironlake crtc_mode_set().
drm/i915: Drop the eDP paths from the pre-Ironlake crtc_mode_set.
drm/i915: Drop the remaining bit of Ironlake code from i9xx_crtc_mode_set().
drm/i915: Drop non-HAS_PCH_SPLIT() code from ironlake_crtc_mode_set().
drm/i915: Drop remaining pre-Ironlake code from ironlake_crtc_mode_set().
drm/i915: Clean up leftover DPLL and LVDS register choice from pch split.
drm/i915: Fold the DPLL limit defines into the structs that use them.
drm/i915: Use existing function instead of open-coding fence reg clear.
drm/i915: Add support for fence registers on Ivybridge.
drm/i915: Update the location of the ringbuffers' HWS_PGA registers for IVB.
Jesse Barnes (20):
drm/i915: use i915_enable_rc6 on SNB too
drm/i915: make FDI training a display function
drm/i915: split irq handling into per-chipset functions
drm/i915: split enable/disable vblank code into chipset specific functions
drm/i915: add IS_GEN7 macro to cover Ivy Bridge and later
drm/i915: add IS_IVYBRIDGE macro for checks
drm/i915: Ivy Bridge has split display and pipe control
drm/i915: add swizzle/tiling support for Ivy Bridge
drm/i915: manual FDI training for Ivy Bridge
drm/i915: treat Ivy Bridge watermarks like Sandy Bridge
drm/i915: interrupt & vblank support for Ivy Bridge
drm/i915: page flip support for Ivy Bridge
drm/i915: ring support for Ivy Bridge
agp/intel: add Ivy Bridge support
drm/i915: add PantherPoint PCH ID
drm/i915: add Ivy Bridge PCI IDs and driver feature structs
drm/i915: set IBX pch type explicitly
drm/i915: split clock gating init into per-chipset functions
drm/i915: add Ivybridge clock gating init function
drm/i915: split PCH clock gating init
Keith Packard (1):
MAINTAINERS: Switch maintainer for drm/i915 to Keith Packard
MAINTAINERS | 4 +-
drivers/char/agp/intel-agp.c | 3 +
drivers/char/agp/intel-agp.h | 8 +
drivers/char/agp/intel-gtt.c | 10 +
drivers/gpu/drm/i915/i915_debugfs.c | 128 ++-
drivers/gpu/drm/i915/i915_dma.c | 60 +-
drivers/gpu/drm/i915/i915_drv.c | 61 +-
drivers/gpu/drm/i915/i915_drv.h | 111 +-
drivers/gpu/drm/i915/i915_gem.c | 36 +-
drivers/gpu/drm/i915/i915_gem_gtt.c | 35 +-
drivers/gpu/drm/i915/i915_gem_tiling.c | 2 +-
drivers/gpu/drm/i915/i915_irq.c | 310 ++++-
drivers/gpu/drm/i915/i915_reg.h | 35 +-
drivers/gpu/drm/i915/i915_suspend.c | 3 +-
drivers/gpu/drm/i915/intel_crt.c | 24 +-
drivers/gpu/drm/i915/intel_display.c | 2370 ++++++++++++++++++-------------
drivers/gpu/drm/i915/intel_drv.h | 19 +-
drivers/gpu/drm/i915/intel_ringbuffer.c | 38 +-
drivers/gpu/drm/i915/intel_ringbuffer.h | 35 +-
drivers/gpu/drm/i915/intel_tv.c | 13 +-
20 files changed, 2124 insertions(+), 1181 deletions(-)
--
keith.packard(a)intel.com
[View Less]
https://bugs.freedesktop.org/show_bug.cgi?id=37785
Summary: [r600g Evergreen] GPU lockup on Blender 2.57 when
moving objects
Product: DRI
Version: XOrg CVS
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: ahlaht(a)gmail.com
Created an …
[View More]attachment (id=47353)
--> (https://bugs.freedesktop.org/attachment.cgi?id=47353)
dmesg with errors
GPU lockup (waiting for 0x00004E51 last fence id 0x00004E50)
Using the latest git:
Linux 2.6.39, drm 61be940, mesa 29ceeeb, xorg 1.10.2, ati 6.14.2
Hardware:
HP laptop, Core i5-450M + Radeon HD 5650 REDWOOD (68C1)
Steps to reproduce:
1. Start Blender 2.57 normally:
$ blender-2.5 --factory-startup
2. On the default scene with the cube press 'g' to move the cube
3. Use mouse to continuously move the cube on screen on random directions
4. After about 5 seconds Blender freezes but mouse cursor keeps moving
5. A GPU lockup occurs and the provided errors appear on dmesg
The bug is very easy to reproduce on my system. I can keep using the system
normally after the bug, but sometimes I have to reset the video mode by
switching to text console and then back to Xorg.
Also there is an alternative way to trigger the bug: Instead of moving the
cube keep resizing any of the side panels continuously.
The problem disappears if I gpu-switcheroo to i965 so I assume this is
something r600g related. Also I was not able to reproduce it on r600c.
--
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]