dri-devel June 2011

dri-devel@lists.freedesktop.org

101 participants
499 discussions

[Bug 38675] New: Recompiled kernel crash on KMS loading
by bugzilla-daemon＠freedesktop.org 15 Jul '11

15 Jul '11

https://bugs.freedesktop.org/show_bug.cgi?id=38675 Summary: Recompiled kernel crash on KMS loading Product: DRI Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: critical Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: muziofg(a)email.it Created an attachment (id=48405) --> (https://bugs.freedesktop.org/attachment.cgi?id=48405) archive containing .config and dmesg output of my custom kernel With my custom kernel (config and dmesg attached at this message in a tar.gz archive) I have a problem with radeon DRM module. When the KMS is loading the system is freezed, the keyboard is dead, the machine doesn't answer at the ping and I can only reset the machine. I haven't any debug information because this crash show a black screen and no file (dmesg, kern.log, messages, ecc) are written. This problem doesn't happen always, but often so it is also difficult to determine when a change in the configuration in the kernel may have solved the problem I actually use a linux kernel version 2.6.39 on a debian testing. I compile a personalized kernel from the sources packaged by debian. The problem seems don't happen with the prebuild kernel (I have tried the package linux-image-2.6.39-2-686-pae) but I'm not sure, simply for now, with this, the machine was started without problem I never had problems with kernel 2.6.38 using a very similar .config file The radeon card is a HD6670 PCI Express (chip TURKS) See here http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=631567 for other details -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 5

[Bug 38800] New: glXSwapBuffersMscOML is slow on AMD Fusion but not on Intel 945 w/Atom
by bugzilla-daemon＠freedesktop.org 14 Jul '11

14 Jul '11

https://bugs.freedesktop.org/show_bug.cgi?id=38800 Summary: glXSwapBuffersMscOML is slow on AMD Fusion but not on Intel 945 w/Atom Product: Mesa Version: unspecified Platform: x86 (IA32) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Drivers/Gallium/r600 AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: simon.farnsworth(a)onelan.co.uk Created an attachment (id=48588) --> (https://bugs.freedesktop.org/attachment.cgi?id=48588) My test program to demonstrate the performance issues I'm trying to get an in-house OpenGL compositor up to the same performance on AMD Fusion as it currently achieves on Intel graphics, and I've found that glXSwapBuffersMscOML is slower (with a trivial test program) on AMD than it is on Intel. I've attached my test program (swapbufferstest.c), which I've been compiling with: gcc -O2 -ggdb -Wall -Werror -o swapbufferstest swapbufferstest.c -lX11 -lGL -lGLEW -lGLU I'm running identical Fedora 15 based software stacks on an Intel Atom D510 (integrated GMA 950 class graphics) and on an AMD Fusion board (GPU PCI ID [1002:9802]). On Intel, I get output like: # ./swapbufferstest Screen is 1920x1200 Longest frame time 17.308969 ms Biggest delta 3 frames, averaging 1.034188 frames per swap Average swap interval 17.118282 ms 121 frames, 117 swaps On AMD, I get: # ./swapbufferstest Screen is 1920x1200 Longest frame time 16.751312 ms Biggest delta 3 frames, averaging 3.000000 frames per swap Average swap interval 49.326561 ms 123 frames, 41 swaps I've confirmed that I've got a direct rendering context in both cases; on Intel, I've been able to confirm that I'm doing page-flipping, but I can't yet work out how to do that on the AMD driver; however, only hitting one frame in 3 doesn't seem right to me, especially since it's not reaching 10% CPU load. I can't however see whether I'm actually hitting the pageflip codepath, or whether I'm in a slow path. Versions of interesting components are: kernel-PAE-2.6.38.8-91.fc15.i686 mesa-dri-drivers-7.11-0.11.20110525.0.fc15.i686 libdrm-2.4.26-1.fc15.i686 xorg-x11-server-Xorg-1.10.2-1.fc15.i686 xorg-x11-drv-ati-6.14.1-1.20110504gita6d2dba6.fc15.i686 xorg-x11-drv-intel-2.15.0-3.fc15.i686 I'm able to rebuild RPMs with extra patches if needed for testing, and I have both systems to hand for testing as needed. I'll attach dmesg and Xorg.log from the AMD system to this bug. -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

2 53

[PATCH] i915: slab shrinker have to return -1 if it can't shrink any objects
by KOSAKI Motohiro 14 Jul '11

14 Jul '11

Now, i915_gem_inactive_shrink() should return -1 instead of 0 if it can't take a lock. Otherwise, vmscan is getting a lot of confusing because vmscan can't distinguish "can't take a lock temporary" and "we've shrank all of i915 objects". Signed-off-by: KOSAKI Motohiro <kosaki.motohiro(a)jp.fujitsu.com> Cc: Keith Packard <keithp(a)keithp.com> Cc: David Airlie <airlied(a)linux.ie> Cc: dri-devel(a)lists.freedesktop.org --- I've found this issue by reviewing. I hope i915 developers confirm this. Thx. drivers/gpu/drm/i915/i915_gem.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-) diff --git a/drivers/gpu/drm/i915/i915_gem.c b/drivers/gpu/drm/i915/i915_gem.c index 94c84d7..2f9a9b2 100644 --- a/drivers/gpu/drm/i915/i915_gem.c +++ b/drivers/gpu/drm/i915/i915_gem.c @@ -4104,7 +4104,7 @@ i915_gem_inactive_shrink(struct shrinker *shrinker, struct shrink_control *sc) int cnt; if (!mutex_trylock(&dev->struct_mutex)) - return 0; + return nr_to_scan ? -1 : 0; /* "fast-path" to count number of available objects */ if (nr_to_scan == 0) { -- 1.7.3.1

4 12

[RFC] drm platform multi-device support
by Rob Clark 14 Jul '11

14 Jul '11

From: Rob Clark <robdclark(a)gmail.com> Include the minor device id in the bus-id to give userspace a way to open the correct "cardN" when there are multiple device instances. --- It may seem a bit strange to have multiple platform device instances, but we have a use-case for this. And this relatively simple patch does the trick. drivers/gpu/drm/drm_ioctl.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/drivers/gpu/drm/drm_ioctl.c b/drivers/gpu/drm/drm_ioctl.c index 47db4df..075024b 100644 --- a/drivers/gpu/drm/drm_ioctl.c +++ b/drivers/gpu/drm/drm_ioctl.c @@ -165,14 +165,15 @@ static int drm_set_busid(struct drm_device *dev, struct drm_file *file_priv) drm_unset_busid(dev, master); if (drm_core_check_feature(dev, DRIVER_USE_PLATFORM_DEVICE)) { - master->unique_len = 10 + strlen(dev->platformdev->name); + master->unique_len = 13 + strlen(dev->platformdev->name); + master->unique_size = master->unique_len; master->unique = kmalloc(master->unique_len + 1, GFP_KERNEL); if (master->unique == NULL) return -ENOMEM; len = snprintf(master->unique, master->unique_len, - "platform:%s", dev->platformdev->name); + "platform:%s:%02d", dev->platformdev->name, dev->primary->index); if (len > master->unique_len) { DRM_ERROR("Unique buffer overflowed\n"); -- 1.7.1

4 6

[PATCH] drm/radeon/kms: Shorten buffers in radeon_ddc_probe
by Jean Delvare 12 Jul '11

12 Jul '11

No need for 2-byte buffers, we only send one byte and receive one byte. Signed-off-by: Jean Delvare <khali(a)linux-fr.org> Cc: David Airlie <airlied(a)linux.ie> Cc: Alex Deucher <alexdeucher(a)gmail.com> --- drivers/gpu/drm/radeon/radeon_i2c.c | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) --- linux-3.0-rc4.orig/drivers/gpu/drm/radeon/radeon_i2c.c 2011-06-27 15:39:33.000000000 +0200 +++ linux-3.0-rc4/drivers/gpu/drm/radeon/radeon_i2c.c 2011-06-27 15:40:35.000000000 +0200 @@ -34,21 +34,20 @@ */ bool radeon_ddc_probe(struct radeon_connector *radeon_connector) { - u8 out_buf[] = { 0x0, 0x0}; - u8 buf[2]; + u8 out = 0x0, in; int ret; struct i2c_msg msgs[] = { { .addr = 0x50, .flags = 0, .len = 1, - .buf = out_buf, + .buf = &out, }, { .addr = 0x50, .flags = I2C_M_RD, .len = 1, - .buf = buf, + .buf = &in, } }; -- Jean Delvare

1 1

[RFC PATCH] KMS support for i.MX51/53
by Sascha Hauer 12 Jul '11

12 Jul '11

Hi All, The following adds a KMS driver for the Freescale i.MX51/53 SoCs. It is far from being ready but I think it is enough to send it out and get the first comments on it and to show that there's something going on. Currently I don't use any sophisticated memory allocater like GEM or similar. I helped myself with simple dma_alloc where needed. At the current state I don't need any more sophisticated allocator as I only focused on the KMS part. Many dumb framebuffers on embedded systems could use a simple allocator at least until something better usable for these kind of systems shows up. The driver currently does its allocations in the DRM_IOCTL_MODE_ADDFB ioctl, which of course is not very standard conform. I tested this driver on the i.MX51 with a DVI and VGA display connected in different clone and dual head modes. Also tested is the i.MX53 LOCO board with the optional HDMI adapter (I didn't get the TV encoder for VGA to work though). First part of the series is the IPU base driver which has been posted several times before, this time with generic interrupt support and fully multi instance safe. Also several smaller improvements have been made. For the DRM people probably only the last three patches are of interest. The series depends on several other patches not posted here. So for those who want to test this please pull the following branch: git://git.pengutronix.de/git/imx/linux-2.6.git imx-ipu-kms As said the driver is not fully standard conform and libkms currently is not suitable for this driver, so the only test utility (apart from the legacy framebuffer) is a little selfmade tool you can get here: git://git.pengutronix.de/git/sha/kmstest.git It is basically a KMS wrapper around the well known fbtest utility. Different mode settings can be supplied on the command line. A README is included. Sascha Sascha Hauer (5): DRM: add i.MX IPUv3 base driver DRM i.MX IPU: Add support for IPU submodules DRM: Add drm encoder/connector helper DRM: Add support for the sii902x HDMI/DVI encoder DRM: Add i.MX IPUv3 support arch/arm/plat-mxc/include/mach/ipu-v3.h | 22 + drivers/gpu/drm/Kconfig | 28 + drivers/gpu/drm/Makefile | 2 + drivers/gpu/drm/drm_encon.c | 302 ++++++++++ drivers/gpu/drm/i2c/Makefile | 3 + drivers/gpu/drm/i2c/sii902x.c | 334 +++++++++++ drivers/gpu/drm/imx/Makefile | 3 + drivers/gpu/drm/imx/imx-drm.c | 936 +++++++++++++++++++++++++++++++ drivers/gpu/drm/imx/imx-priv.h | 9 + drivers/gpu/drm/imx/ipu-v3/Makefile | 3 + drivers/gpu/drm/imx/ipu-v3/ipu-common.c | 799 ++++++++++++++++++++++++++ drivers/gpu/drm/imx/ipu-v3/ipu-dc.c | 440 +++++++++++++++ drivers/gpu/drm/imx/ipu-v3/ipu-di.c | 665 ++++++++++++++++++++++ drivers/gpu/drm/imx/ipu-v3/ipu-dmfc.c | 393 +++++++++++++ drivers/gpu/drm/imx/ipu-v3/ipu-dp.c | 342 +++++++++++ drivers/gpu/drm/imx/ipu-v3/ipu-prv.h | 218 +++++++ include/drm/drm_encon.h | 46 ++ include/drm/imx-ipu-v3.h | 308 ++++++++++ 18 files changed, 4853 insertions(+), 0 deletions(-) create mode 100644 arch/arm/plat-mxc/include/mach/ipu-v3.h create mode 100644 drivers/gpu/drm/drm_encon.c create mode 100644 drivers/gpu/drm/i2c/sii902x.c create mode 100644 drivers/gpu/drm/imx/Makefile create mode 100644 drivers/gpu/drm/imx/imx-drm.c create mode 100644 drivers/gpu/drm/imx/imx-priv.h create mode 100644 drivers/gpu/drm/imx/ipu-v3/Makefile create mode 100644 drivers/gpu/drm/imx/ipu-v3/ipu-common.c create mode 100644 drivers/gpu/drm/imx/ipu-v3/ipu-dc.c create mode 100644 drivers/gpu/drm/imx/ipu-v3/ipu-di.c create mode 100644 drivers/gpu/drm/imx/ipu-v3/ipu-dmfc.c create mode 100644 drivers/gpu/drm/imx/ipu-v3/ipu-dp.c create mode 100644 drivers/gpu/drm/imx/ipu-v3/ipu-prv.h create mode 100644 include/drm/drm_encon.h create mode 100644 include/drm/imx-ipu-v3.h

5 13

[Bug 33889] New: kwin crashes when enabling Desktop Cube Effects crashed via gallium r600g driver
by bugzilla-daemon＠freedesktop.org 12 Jul '11

12 Jul '11

https://bugs.freedesktop.org/show_bug.cgi?id=33889 Summary: kwin crashes when enabling Desktop Cube Effects crashed via gallium r600g driver Product: Mesa Version: 7.10 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: shawn.starr(a)rogers.com Stack trace with a little bit of what kwin was doing and gallium specific calls Fedora rawhide: Kernel: 2.6.38-0.rc3.git0.1.fc15.x86_64 DRM library: libdrm-2.4.24-0.1.20110106.fc15.x86_64 Mesa: mesa-dri-drivers-7.10-0.24.fc15.x86_64 X Server: xorg-x11-server-Xorg-1.9.99.1-3.20101201.fc15.x86_64 Don't think you need this but doesn't hurt: DDX: xorg-x11-drv-ati-6.14.0-1.20110204gita27b5dbd9.fc15.x86_64 Thread 1 (Thread 0x7fd77e242860 (LWP 3820)): [KCrash Handler] #6 0x00007fd7708863c9 in r600_bo (radeon=0x23b02b0, size=128, alignment=4096, binding=32, usage=0) at r600_bo.c:43 #7 0x00007fd77087b909 in r600_buffer_create (screen=0x23b0420, templ=0x7fffc5bd2d10) at r600_buffer.c:62 #8 0x00007fd7709cdb3f in pipe_buffer_create (size=128, bind=32, screen=<value optimized out>) at ../../src/gallium/auxiliary/util/u_inlines.h:183 #9 st_upload_constants (st=0x2a1cfb0, params=0x2288640, shader_type=0) at state_tracker/st_atom_constbuf.c:80 #10 0x00007fd7709cd275 in st_validate_state (st=0x2a1cfb0) at state_tracker/st_atom.c:172 #11 0x00007fd77092dcc3 in st_draw_vbo (ctx=0x29dabc0, arrays=0x2a201c8, prims=0x2a1e8e4, nr_prims=1, ib=0x0, index_bounds_valid=<value optimized out>, min_index=0, max_index=3) at state_tracker/st_draw.c:649 #12 0x00007fd77092b999 in vbo_exec_vtx_flush (exec=<value optimized out>, unmap=<value optimized out>) at vbo/vbo_exec_draw.c:381 #13 0x00007fd77092961c in vbo_exec_FlushVertices_internal (ctx=<value optimized out>, unmap=<value optimized out>) at vbo/vbo_exec_api.c:911 #14 0x00007fd770929812 in vbo_exec_FlushVertices (ctx=<value optimized out>, flags=1) at vbo/vbo_exec_api.c:945 #15 0x00007fd770992a3e in _mesa_PopAttrib () at main/attrib.c:858 #16 0x0000003d00e13c45 in KWin::PaintClipper::Iterator::~Iterator (this=0x7fffc5bd35a0, __in_chrg=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/lib/kwineffects.cpp:873 #17 0x0000003d00e1d2c2 in KWin::renderGLGeometry (region=..., count=4, vertices=0x2ef8940, texture=0x2cc04a0, color=0x0, dim=2, stride=0) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/lib/kwinglutils.cpp:180 #18 0x0000003cffad0616 in KWin::SceneOpenGL::Window::paintDecoration (this=0x2f290d0, decoration=<value optimized out>, decorationType=KWin::SceneOpenGL::Window::DecorationTop, region=..., rect=..., data=..., quads=..., updateDeco=true) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/scene_opengl.cpp:1633 #19 0x0000003cffad6679 in performPaint (data=..., region=..., mask=9, this=<value optimized out>) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/scene_opengl.cpp:1545 #20 KWin::SceneOpenGL::Window::performPaint (this=<value optimized out>, mask=9, region=..., data=...) at /usr/src/debug/kdebase-workspace-4.6.0/kwin/scene_opengl.cpp:1408 #21 0x0000003cffac10a9 in KWin::Scene::finalDrawWindow (this=<value optimized out>, w=<value optimized out>, mask=9, region=<value optimized out>, data=<value optimized out>) at -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 7

[Bug 34778] New: [r600g, wine] FEAR / depth-stencil rendering triggers SW fallback
by bugzilla-daemon＠freedesktop.org 12 Jul '11

12 Jul '11

https://bugs.freedesktop.org/show_bug.cgi?id=34778 Summary: [r600g, wine] FEAR / depth-stencil rendering triggers SW fallback Product: DRI Version: DRI CVS Platform: x86-64 (AMD64) URL: http://www.gamershell.com/download_10167.shtml OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: DRM/Radeon AssignedTo: dri-devel(a)lists.freedesktop.org ReportedBy: liquid.acid(a)gmx.net System: ATI Technologies Inc Radeon HD 4770 [RV740] drm-radeon-testing kernel (git tip) libdrm, mesa and xf86-video-intel git master xorg-server-1.9.4 mesa git master = 99b9019716d0a5cfc7438677d2e11090d676c054 Hi there, this is sort of copy&paste from bug #34674. The problem (fallback to software rendering) described there also happens on r600g, and probably (judging from the state tracker code) on all gallium drivers. Anyway, from profiling I found out that pipe_put_tile_z and pipe_get_tile_z consume like 90% of the CPU time. These two get called by fallback_copy_texsubimage, which is called from st_copy_texsubimage. Greets, Tobias -- Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 2

[Bug 32402] New: Oops associated with radeon_unpin_work_func
by bugzilla-daemon＠bugzilla.kernel.org 10 Jul '11

10 Jul '11

https://bugzilla.kernel.org/show_bug.cgi?id=32402 Summary: Oops associated with radeon_unpin_work_func Product: Drivers Version: 2.5 Kernel Version: 2.6.38.2 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: high Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: smf.linux(a)ntlworld.com Regression: No If this system (LFS build) is left idle for several hours with xscreensaver running(don't currently know which screen saver app. I am assuming one of the Mesa 3D ones) the system will oops. The system is locked solid and there is no trace in messages.old on reboot. The attached jpg is a photo of the screen at system failure. I first noticed the problem in 2.6.38-rc8 but have waited until now to report the problem in the hope of obtaining a more repeatable scenario. Version info: Xorg server 1.10.0 Xorg ati driver 6.14.1 libdrm-2.4.24 Mesa-7.10.1 Processor AMD Phenom(tm) II X4 940 Processor Linux Andromeda 2.6.38.2 #1 SMP Mon Mar 28 22:17:13 BST 2011 i686 athlon-4 i386 GNU/Linux Gnu C 4.6.0 Gnu make 3.81 binutils 2.21 util-linux 2.14.1 mount support module-init-tools 3.5 e2fsprogs 1.41.4 Linux C Library 2.13 Dynamic linker (ldd) 2.13 Linux C++ Library 6.0.15 Procps 3.2.7 Net-tools 1.60 Kbd 1.15 Sh-utils 7.4 Modules Loaded md4 md5 hmac cryptomgr aead nls_cp437 cifs crypto_hash crypto_algapi microcode nfs fscache nfsd lockd sunrpc exportfs fuse usbhid firewire_ohci sr_mod sg firewire_core cdrom psmouse i2c_piix4 crc_itu_t button vboxnetflt fifo splitter ohci_hcd ehci_hcd usbcore nls_base vboxnetadp snd_hda_codec_hdmi snd_hda_codec_analog snd_hda_intel snd_hda_codec snd_seq_dummy snd_seq_oss snd_seq_midi_event snd_seq snd_seq_device snd_pcm_oss snd_mixer_oss snd_hwdep snd_pcm snd_page_alloc snd_timer snd soundcore brd loop asus_atk0110 powernow_k8 processor thermal_sys mperf pata_atiixp vboxdrv sky2 rtc eeprom unix -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ Create and publish websites with WebMatrix Use the most popular FREE web apps or write code yourself; WebMatrix provides all the features you need to develop and publish your website. http://p.sf.net/sfu/ms-webmatrix-sf -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 23

[Bug 35472] New: [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730)
by bugzilla-daemon＠bugzilla.kernel.org 05 Jul '11

05 Jul '11

https://bugzilla.kernel.org/show_bug.cgi?id=35472 Summary: [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730) Product: Drivers Version: 2.5 Kernel Version: 2.6.38 Platform: All OS/Version: Linux Tree: Mainline Status: NEW Severity: normal Priority: P1 Component: Video(DRI - non Intel) AssignedTo: drivers_video-dri(a)kernel-bugs.osdl.org ReportedBy: virtuousfox(a)gmail.com Regression: Yes with 2.6.37 it's all OK but since 2.6.38 from very framebuffer initialization screen is filled with dense grey lines looking like ugly grid. also per every 3cm on my 1920x1080/23' screen there is a distinctive whitish vertical line. when X try to startup i can see cursor and can move it around for a while (that grey grid is there too) but kdm does not starting up and GPU locks up. it is the same with 2.6.39. here is `dmesg|grep drm` for 2.6.39: [ 0.462282] [drm] Initialized drm 1.1.0 20060810 [ 0.462315] [drm] radeon defaulting to kernel modesetting. [ 0.462337] [drm] radeon kernel modesetting enabled. [ 0.462575] [drm] initializing kernel modesetting (RV770 0x1002:0x944E). [ 0.462608] [drm] register mmio base: 0xFDFE0000 [ 0.462630] [drm] register mmio size: 65536 [ 0.463313] [drm] Detected VRAM RAM=512M, BAR=256M [ 0.463343] [drm] RAM width 128bits DDR [ 0.463526] [drm] radeon: 512M of VRAM memory ready [ 0.463549] [drm] radeon: 512M of GTT memory ready. [ 0.463571] [drm] Supports vblank timestamp caching Rev 1 (10.10.2010). [ 0.463594] [drm] Driver supports precise vblank timestamp query. [ 0.463708] [drm] radeon: irq initialized. [ 0.463733] [drm] GART: num cpu pages 131072, num gpu pages 131072 [ 0.465260] [drm] Loading RV770 Microcode [ 0.512429] [drm] ring test succeeded in 1 usecs [ 0.512544] [drm] radeon: ib pool ready. [ 0.512584] [drm] ib test succeeded in 0 usecs [ 0.512609] [drm] Enabling audio support [ 0.512805] [drm] Radeon Display Connectors [ 0.512827] [drm] Connector 0: [ 0.512847] [drm] DVI-I [ 0.512868] [drm] HPD2 [ 0.512889] [drm] DDC: 0x7e60 0x7e60 0x7e64 0x7e64 0x7e68 0x7e68 0x7e6c 0x7e6c [ 0.512915] [drm] Encoders: [ 0.512936] [drm] DFP1: INTERNAL_UNIPHY [ 0.512957] [drm] CRT2: INTERNAL_KLDSCP_DAC2 [ 0.512979] [drm] Connector 1: [ 0.512999] [drm] DIN [ 0.513028] [drm] Encoders: [ 0.513049] [drm] TV1: INTERNAL_KLDSCP_DAC2 [ 0.513070] [drm] Connector 2: [ 0.513091] [drm] DVI-I [ 0.513111] [drm] HPD1 [ 0.513132] [drm] DDC: 0x7e20 0x7e20 0x7e24 0x7e24 0x7e28 0x7e28 0x7e2c 0x7e2c [ 0.513158] [drm] Encoders: [ 0.513179] [drm] CRT1: INTERNAL_KLDSCP_DAC1 [ 0.513201] [drm] DFP2: INTERNAL_KLDSCP_LVTMA [ 0.577285] [drm] Internal thermal controller without fan control [ 0.578307] [drm] radeon: power management initialized [ 0.657478] [drm] fb mappable at 0xD0142000 [ 0.657500] [drm] vram apper at 0xD0000000 [ 0.657521] [drm] size 8294400 [ 0.657541] [drm] fb depth is 24 [ 0.657562] [drm] pitch is 7680 [ 0.657632] fbcon: radeondrmfb (fb0) is primary device [ 1.073319] fb0: radeondrmfb frame buffer device [ 1.073349] drm: registered panic notifier [ 1.073379] [drm] Initialized radeon 2.9.0 20080528 for 0000:01:00.0 on minor 0 [ 252.565034] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 252.565102] [<ffffffff8137c334>] ? drm_ioctl+0x394/0x450 [ 252.565145] [drm] Disabling audio support [ 252.731618] [drm] ring test succeeded in 1 usecs [ 252.908838] [drm:r600_ib_test] *ERROR* radeon: ib test failed (scratch(0x8504)=0xCAFEDEAD) [ 252.908841] [drm:rv770_resume] *ERROR* radeon: failed testing IB (-22). [ 267.523039] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 267.523107] [<ffffffff8137c334>] ? drm_ioctl+0x394/0x450 [ 268.216464] [drm] ring test succeeded in 1 usecs [ 268.216473] [drm] ib test succeeded in 1 usecs [ 268.216475] [drm] Enabling audio support [ 273.719044] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 273.719114] [<ffffffff8137c334>] ? drm_ioctl+0x394/0x450 [ 273.719159] [drm] Disabling audio support [ 274.411517] [drm] ring test succeeded in 1 usecs [ 274.588784] [drm:r600_ib_test] *ERROR* radeon: ib test failed (scratch(0x8504)=0xCAFEDEAD) [ 274.588787] [drm:rv770_resume] *ERROR* radeon: failed testing IB (-22). [ 290.090036] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 290.090103] [<ffffffff8137c334>] ? drm_ioctl+0x394/0x450 [ 290.779828] [drm] ring test succeeded in 1 usecs [ 290.957091] [drm:r600_ib_test] *ERROR* radeon: ib test failed (scratch(0x8504)=0xCAFEDEAD) [ 290.957094] [drm:rv770_resume] *ERROR* radeon: failed testing IB (-22). [ 306.459037] WARNING: at drivers/gpu/drm/radeon/radeon_fence.c:246 radeon_fence_wait+0x3a6/0x400() [ 306.459105] [<ffffffff8137c334>] ? drm_ioctl+0x394/0x450 [ 307.153106] [drm] ring test succeeded in 1 usecs [ 307.330842] [drm:r600_ib_test] *ERROR* radeon: ib test failed (scratch(0x8504)=0xCAFEDEAD) [ 307.330845] [drm:rv770_resume] *ERROR* radeon: failed testing IB (-22). -- Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are watching the assignee of the bug. ------------------------------------------------------------------------------ What Every C/C++ and Fortran developer Should Know! Read this article and learn how Intel has extended the reach of its next-generation tools to help Windows* and Linux* C/C++ and Fortran developers boost performance applications - including clusters. http://p.sf.net/sfu/intel-dev2devmay -- _______________________________________________ Dri-devel mailing list Dri-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel

1 18

← Newer
1
...
27
28
29
30
31
32
33
...
50
Older →

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

dri-devel June 2011