From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 71891] 3.13 fails to boot with the radeon module
Date: Sat, 12 Apr 2014 18:12:00 +0000 [thread overview]
Message-ID: <bug-71891-2300-xgRsZ7iLIo@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-71891-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=71891
--- Comment #15 from sdh <sh.siddhartha@gmail.com> ---
Thanks, that helped :)
Doing a 'modprobe radeon' after booting up gives the following errors:
radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000002 last fence id
0x0000000000000000 on ring 5)
[drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35).
[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-35).
Doing a startx completely hangs up the system
Full log:
# journalctl --since="2014-04-12" -o cat | grep 'drm\|radeon'
[drm] Initialized drm 1.1.0 20060810
[drm] radeon kernel modesetting enabled.
fb: conflicting fb hw usage radeondrmfb vs VESA VGA - removing generic driver
[drm] initializing kernel modesetting (RV730 0x1002:0x9480 0x1028:0x0447).
[drm] register mmio base: 0xFBE20000
[drm] register mmio size: 65536
radeon 0000:01:00.0: VRAM: 1024M 0x0000000000000000 - 0x000000003FFFFFFF (1024M
used)
radeon 0000:01:00.0: GTT: 1024M 0x0000000040000000 - 0x000000007FFFFFFF
[drm] Detected VRAM RAM=1024M, BAR=256M
[drm] RAM width 128bits DDR
[drm] radeon: 1024M of VRAM memory ready
[drm] radeon: 1024M of GTT memory ready.
[drm] Loading RV730 Microcode
[drm] Internal thermal controller with fan control
[drm] radeon: dpm initialized
[drm] GART: num cpu pages 262144, num gpu pages 262144
[drm] PCIE GART of 1024M enabled (table at 0x000000000025D000).
radeon 0000:01:00.0: WB enabled
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and
cpu addr 0xffff8800b665cc00
radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and
cpu addr 0xffff8800b665cc0c
radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c598 and
cpu addr 0xffffc90012f1c598
[drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[drm] Driver supports precise vblank timestamp query.
radeon 0000:01:00.0: irq 50 for MSI/MSI-X
radeon 0000:01:00.0: radeon: using MSI.
[drm] radeon: irq initialized.
[drm] ring test on 0 succeeded in 1 usecs
[drm] ring test on 3 succeeded in 1 usecs
[drm] ring test on 5 succeeded in 1 usecs
[drm] UVD initialized successfully.
[drm] ib test on ring 0 succeeded in 0 usecs
[drm] ib test on ring 3 succeeded in 0 usecs
radeon 0000:01:00.0: GPU lockup CP stall for more than 10000msec
radeon 0000:01:00.0: GPU lockup (waiting for 0x0000000000000002 last fence id
0x0000000000000000 on ring 5)
[drm:uvd_v1_0_ib_test] *ERROR* radeon: fence wait failed (-35).
[drm:radeon_ib_ring_tests] *ERROR* radeon: failed testing IB on ring 5 (-35).
Starting Load/Save Screen Backlight Brightness of backlight:radeon_bl0...
Started Load/Save Screen Backlight Brightness of backlight:radeon_bl0.
[drm] radeon atom DIG backlight initialized
[drm] Radeon Display Connectors
[drm] Connector 0:
[drm] VGA-1
[drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[drm] Encoders:
[drm] CRT1: INTERNAL_KLDSCP_DAC1
[drm] Connector 1:
[drm] HDMI-A-1
[drm] HPD1
[drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[drm] Encoders:
[drm] DFP1: INTERNAL_UNIPHY
[drm] Connector 2:
[drm] LVDS-1
[drm] DDC: 0x7f68 0x7f68 0x7f6c 0x7f6c 0x7f70 0x7f70 0x7f74 0x7f74
[drm] Encoders:
[drm] LCD1: INTERNAL_UNIPHY2
[drm] fb mappable at 0xC0460000
[drm] vram apper at 0xC0000000
[drm] size 4325376
[drm] fb depth is 24
[drm] pitch is 5632
fbcon: radeondrmfb (fb0) is primary device
radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
radeon 0000:01:00.0: registered panic notifier
[drm] Initialized radeon 2.37.0 20080528 for 0000:01:00.0 on minor 0
radeon 0000:01:00.0: GPU reset succeeded, trying to resume
[drm:rv770_dpm_set_power_state] *ERROR* rv770_set_sw_state failed
[drm] PCIE GART of 1024M enabled (table at 0x000000000025D000).
radeon 0000:01:00.0: WB enabled
radeon 0000:01:00.0: fence driver on ring 0 use gpu addr 0x0000000040000c00 and
cpu addr 0xffff8800b665cc00
radeon 0000:01:00.0: fence driver on ring 3 use gpu addr 0x0000000040000c0c and
cpu addr 0xffff8800b665cc0c
radeon 0000:01:00.0: fence driver on ring 5 use gpu addr 0x000000000005c598 and
cpu addr 0xffffc90012f1c598
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-04-12 18:12 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-11 14:14 [Bug 71891] New: 3.13 fails to boot with the radeon module bugzilla-daemon
2014-03-11 14:19 ` [Bug 71891] " bugzilla-daemon
2014-03-11 14:53 ` bugzilla-daemon
2014-03-11 15:46 ` bugzilla-daemon
2014-03-11 16:22 ` bugzilla-daemon
2014-04-06 15:22 ` bugzilla-daemon
2014-04-06 15:35 ` bugzilla-daemon
2014-04-06 18:23 ` bugzilla-daemon
2014-04-06 18:50 ` bugzilla-daemon
2014-04-10 9:57 ` bugzilla-daemon
2014-04-10 14:12 ` bugzilla-daemon
2014-04-12 8:59 ` bugzilla-daemon
2014-04-12 9:25 ` bugzilla-daemon
2014-04-12 10:18 ` bugzilla-daemon
2014-04-12 10:27 ` bugzilla-daemon
2014-04-12 18:12 ` bugzilla-daemon [this message]
2014-04-15 7:29 ` bugzilla-daemon
2014-04-18 14:15 ` bugzilla-daemon
2014-04-19 10:25 ` bugzilla-daemon
2014-04-19 13:58 ` bugzilla-daemon
2014-04-24 3:06 ` bugzilla-daemon
2014-04-24 7:58 ` bugzilla-daemon
2014-04-24 8:58 ` bugzilla-daemon
2014-04-24 11:59 ` bugzilla-daemon
2014-04-26 1:35 ` bugzilla-daemon
2014-04-26 8:40 ` bugzilla-daemon
2014-04-27 0:12 ` bugzilla-daemon
2014-04-27 5:52 ` bugzilla-daemon
2014-04-29 13:51 ` bugzilla-daemon
2014-04-29 13:55 ` bugzilla-daemon
2014-05-06 5:15 ` bugzilla-daemon
2014-05-12 5:25 ` bugzilla-daemon
2014-05-12 7:42 ` bugzilla-daemon
2014-05-12 14:59 ` bugzilla-daemon
2014-05-12 15:11 ` bugzilla-daemon
2014-05-12 17:07 ` bugzilla-daemon
2014-05-12 18:21 ` bugzilla-daemon
2014-05-13 5:44 ` bugzilla-daemon
2014-06-26 0:14 ` bugzilla-daemon
2014-06-26 8:21 ` bugzilla-daemon
2014-07-03 15:11 ` bugzilla-daemon
2014-07-04 13:08 ` bugzilla-daemon
2014-07-04 13:16 ` bugzilla-daemon
2014-08-15 12:51 ` bugzilla-daemon
2014-08-15 15:08 ` bugzilla-daemon
2014-10-29 18:08 ` bugzilla-daemon
2014-10-29 19:21 ` bugzilla-daemon
2015-06-03 6:57 ` bugzilla-daemon
2015-06-03 12:48 ` bugzilla-daemon
2016-09-20 1:28 ` bugzilla-daemon
2016-09-20 1:45 ` bugzilla-daemon
2020-06-08 10:26 ` 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-71891-2300-xgRsZ7iLIo@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.