From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 48191] New: radeon: trace dumped from r600_hdmi.c
Date: Tue, 2 Oct 2012 15:55:53 +0000 (UTC) [thread overview]
Message-ID: <bug-48191-2300@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=48191
Summary: radeon: trace dumped from r600_hdmi.c
Product: Drivers
Version: 2.5
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: dgbaley27@0x01b.net
Regression: No
Created an attachment (id=81831)
--> (https://bugzilla.kernel.org/attachment.cgi?id=81831)
dmesg output
This has been happening since 3.5, but I've just booted 3.6 and I am still
getting some worrying stuff in the kernel log. dmesg output attached. The trace
begins on line 631. I am passing audio=1 to radeon.ko. Audio does work despite
this error.
--
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.
next reply other threads:[~2012-10-02 15:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 15:55 bugzilla-daemon [this message]
2013-12-23 16:37 ` [Bug 48191] radeon: trace dumped from r600_hdmi.c bugzilla-daemon
2013-12-23 16:41 ` 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-48191-2300@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).