From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 65761] HD 7970M Hybrid - hangs and errors and rmmod causes crash
Date: Fri, 07 Feb 2014 22:44:12 +0000 [thread overview]
Message-ID: <bug-65761-2300-sxShF30ySe@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-65761-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=65761
--- Comment #35 from Alex Deucher <alexdeucher@gmail.com> ---
(In reply to Christoph Haag from comment #33)
> But I have an awful lot of this block in dmesg, I guess from every time
> starting X:
Those are the messages from the driver each time the card is powered off or on.
>
> [Feb 6 13:39] [drm] Disabling audio 0 support
> [ +0,000004] [drm] Disabling audio 1 support
> [ +0,000002] [drm] Disabling audio 2 support
> [ +0,000001] [drm] Disabling audio 3 support
> [ +0,000001] [drm] Disabling audio 4 support
> [ +0,000002] [drm] Disabling audio 5 support
Card is powered off.
> [ +1,257992] [drm] probing gen 2 caps for device 8086:151 = 261ad01/e
> [ +0,000005] [drm] PCIE gen 3 link speeds already enabled
> [ +0,004127] [drm] PCIE GART of 1024M enabled (table at 0x0000000000478000).
> [ +0,000102] radeon 0000:01:00.0: WB enabled
> [ +0,000004] radeon 0000:01:00.0: fence driver on ring 0 use gpu addr
> 0x0000000080000c00 and cpu addr 0xffff8807fd9f8c00
> [ +0,000003] radeon 0000:01:00.0: fence driver on ring 1 use gpu addr
> 0x0000000080000c04 and cpu addr 0xffff8807fd9f8c04
> [ +0,000002] radeon 0000:01:00.0: fence driver on ring 2 use gpu addr
> 0x0000000080000c08 and cpu addr 0xffff8807fd9f8c08
> [ +0,000002] radeon 0000:01:00.0: fence driver on ring 3 use gpu addr
> 0x0000000080000c0c and cpu addr 0xffff8807fd9f8c0c
> [ +0,000002] radeon 0000:01:00.0: fence driver on ring 4 use gpu addr
> 0x0000000080000c10 and cpu addr 0xffff8807fd9f8c10
> [ +0,000390] radeon 0000:01:00.0: fence driver on ring 5 use gpu addr
> 0x0000000000075a18 and cpu addr 0xffffc90008b35a18
> [ +0,144839] [drm] ring test on 0 succeeded in 2 usecs
> [ +0,000004] [drm] ring test on 1 succeeded in 1 usecs
> [ +0,000003] [drm] ring test on 2 succeeded in 1 usecs
> [ +0,000059] [drm] ring test on 3 succeeded in 2 usecs
> [ +0,000007] [drm] ring test on 4 succeeded in 1 usecs
> [ +0,187260] [drm] ring test on 5 succeeded in 2 usecs
> [ +0,000004] [drm] UVD initialized successfully.
> [ +0,001745] [drm] Enabling audio 0 support
> [ +0,000001] [drm] Enabling audio 1 support
> [ +0,000000] [drm] Enabling audio 2 support
> [ +0,000001] [drm] Enabling audio 3 support
> [ +0,000001] [drm] Enabling audio 4 support
> [ +0,000001] [drm] Enabling audio 5 support
> [ +0,000035] [drm] ib test on ring 0 succeeded in 0 usecs
> [ +0,000029] [drm] ib test on ring 1 succeeded in 0 usecs
> [ +0,000029] [drm] ib test on ring 2 succeeded in 0 usecs
> [ +0,000019] [drm] ib test on ring 3 succeeded in 0 usecs
> [ +0,000018] [drm] ib test on ring 4 succeeded in 0 usecs
> [ +0,158619] [drm] ib test on ring 5 succeeded
Card is powered back on.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2014-02-07 22:44 UTC|newest]
Thread overview: 58+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-25 16:49 [Bug 65761] New: HD 7970M Hybrid - hangs and errors and rmmod causes crash bugzilla-daemon
2013-11-25 17:15 ` [Bug 65761] " bugzilla-daemon
2013-11-26 20:03 ` bugzilla-daemon
2013-11-30 12:12 ` bugzilla-daemon
2013-12-06 22:21 ` bugzilla-daemon
2013-12-06 22:34 ` bugzilla-daemon
2013-12-07 1:06 ` bugzilla-daemon
2013-12-07 1:17 ` bugzilla-daemon
2013-12-24 15:45 ` bugzilla-daemon
2013-12-24 19:43 ` bugzilla-daemon
2013-12-24 19:45 ` bugzilla-daemon
2013-12-24 21:40 ` bugzilla-daemon
2014-01-06 11:57 ` bugzilla-daemon
2014-01-06 21:52 ` bugzilla-daemon
2014-01-19 23:22 ` bugzilla-daemon
2014-01-21 0:15 ` bugzilla-daemon
2014-01-21 0:23 ` bugzilla-daemon
2014-01-21 0:55 ` bugzilla-daemon
2014-01-21 21:58 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-22 1:53 ` bugzilla-daemon
2014-01-24 2:20 ` bugzilla-daemon
2014-01-31 0:10 ` bugzilla-daemon
2014-01-31 14:14 ` bugzilla-daemon
2014-01-31 20:00 ` bugzilla-daemon
2014-01-31 20:46 ` bugzilla-daemon
2014-01-31 21:24 ` bugzilla-daemon
2014-01-31 23:00 ` bugzilla-daemon
2014-02-01 0:08 ` bugzilla-daemon
2014-02-02 23:58 ` bugzilla-daemon
2014-02-06 13:48 ` bugzilla-daemon
2014-02-07 0:49 ` bugzilla-daemon
2014-02-07 14:52 ` bugzilla-daemon
2014-02-07 22:39 ` bugzilla-daemon
2014-02-07 22:44 ` bugzilla-daemon [this message]
2014-02-07 22:47 ` bugzilla-daemon
2014-02-11 1:58 ` bugzilla-daemon
2014-02-11 7:30 ` bugzilla-daemon
2014-02-12 7:55 ` bugzilla-daemon
2014-02-12 9:41 ` bugzilla-daemon
2014-02-13 2:53 ` bugzilla-daemon
2014-02-13 9:00 ` bugzilla-daemon
2014-02-13 12:12 ` bugzilla-daemon
2014-02-14 2:59 ` bugzilla-daemon
2014-02-15 17:33 ` bugzilla-daemon
2014-02-17 17:04 ` bugzilla-daemon
2014-02-19 0:45 ` bugzilla-daemon
2014-02-19 0:46 ` bugzilla-daemon
2014-02-19 1:26 ` bugzilla-daemon
2014-02-19 2:45 ` bugzilla-daemon
2014-03-03 0:19 ` bugzilla-daemon
2014-03-03 0:20 ` bugzilla-daemon
2014-03-03 8:22 ` bugzilla-daemon
2014-03-03 23:16 ` bugzilla-daemon
2014-03-03 23:25 ` bugzilla-daemon
2014-04-01 9:00 ` bugzilla-daemon
2015-01-04 1:09 ` 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-65761-2300-sxShF30ySe@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 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).