From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 28622] radeon video lockup
Date: Mon, 2 Jul 2012 20:21:03 +0000 (UTC) [thread overview]
Message-ID: <20120702202103.45CBC11FA64@bugzilla.kernel.org> (raw)
In-Reply-To: <bug-28622-2300@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=28622
--- Comment #11 from Alex Deucher <alexdeucher@gmail.com> 2012-07-02 20:21:02 ---
Is this still an issue with a more recent kernel (3.x)?
--
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 prev parent reply other threads:[~2012-07-02 20:21 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 17:48 [Bug 28622] New: radeon video lookup bugzilla-daemon
2011-02-08 17:48 ` [Bug 28622] radeon video lockup bugzilla-daemon
2011-02-08 18:00 ` bugzilla-daemon
2011-02-08 18:24 ` bugzilla-daemon
2011-02-08 18:28 ` bugzilla-daemon
2011-02-08 19:05 ` bugzilla-daemon
2011-02-08 20:59 ` bugzilla-daemon
2011-02-13 10:56 ` bugzilla-daemon
2011-02-13 22:20 ` bugzilla-daemon
2011-03-13 19:13 ` bugzilla-daemon
2011-03-29 21:13 ` bugzilla-daemon
2011-06-04 0:34 ` bugzilla-daemon
2011-06-04 0:36 ` bugzilla-daemon
2012-07-02 13:51 ` bugzilla-daemon
2012-07-02 20:21 ` bugzilla-daemon [this message]
2012-11-20 16:58 ` bugzilla-daemon
-- strict thread matches above, loose matches on Subject: below --
2011-02-12 23:34 2.6.38-rc4-git5: Reported regressions 2.6.36 -> 2.6.37 Rafael J. Wysocki
[not found] ` <1z1FRILH7uF.A.ib.rfxVNB@chimera>
[not found] ` <alpine.DEB.2.00.1102121610460.4146@asgard.lang.hm>
[not found] ` <alpine.DEB.2.00.1102121610460.4146-Z4YwzcCRHZnr5h6Zg1Auow@public.gmane.org>
2011-02-13 10:57 ` [Bug #28622] radeon video lockup Rafael J. Wysocki
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=20120702202103.45CBC11FA64@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