From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.sourceforge.net
Subject: [Bug 35472] New: [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730)
Date: Fri, 20 May 2011 04:03:22 GMT [thread overview]
Message-ID: <bug-35472-2300@https.bugzilla.kernel.org/> (raw)
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@kernel-bugs.osdl.org
ReportedBy: virtuousfox@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@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel
next reply other threads:[~2011-05-20 4:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-20 4:03 bugzilla-daemon [this message]
2011-05-20 4:05 ` [Bug 35472] [r600] radeondrmfb rendering is broken and running X makes GPU lock-up on RV770 CE (Radeon HD 4730) bugzilla-daemon
2011-05-20 4:08 ` bugzilla-daemon
2011-05-20 4:12 ` bugzilla-daemon
2011-05-20 4:15 ` bugzilla-daemon
2011-05-20 5:01 ` bugzilla-daemon
2011-05-20 14:42 ` bugzilla-daemon
2011-05-20 14:43 ` bugzilla-daemon
2011-05-20 14:48 ` bugzilla-daemon
2011-05-20 14:51 ` bugzilla-daemon
2011-05-20 14:53 ` bugzilla-daemon
2011-06-26 7:08 ` bugzilla-daemon
2011-06-29 9:04 ` [Bug 35472] [bisected] " bugzilla-daemon
2011-06-29 9:06 ` bugzilla-daemon
2011-06-30 8:41 ` bugzilla-daemon
2011-06-30 13:01 ` bugzilla-daemon
2011-06-30 13:14 ` bugzilla-daemon
2011-07-05 10:43 ` bugzilla-daemon
2011-07-05 11:38 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-35472-2300@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).