dri-devel.lists.freedesktop.org archive mirror
 help / color / mirror / Atom feed
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: Mon, 03 Mar 2014 23:25:39 +0000	[thread overview]
Message-ID: <bug-65761-2300-Q3lkMmZpzP@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 #55 from Christoph Haag <haagch.christoph@googlemail.com> ---
(In reply to saadnaji89 from comment #54)

> Are we going to see this patch applied to fix the  problem in future kernel
> veriosn  ?. I don't know whether you work for AMD or just someone is
> contributing to fix the problem

I wondered whether to reply, but now...

He works for AMD. It's even on Wikipedia.

This patch is not to the kernel, it is to mesa.

It has been in mesa for 14 days:
http://cgit.freedesktop.org/mesa/mesa/commit/?id=cf0172d46ab940a691da6516057c81f28961482f

(Is it necessary to keep talking about already fixed stuff?)



I'd say the only reason this is not closed yet is because of the radeon module
unloading problems. Thinking of it, I haven't tried in a while.. Should I try
to get some more information for it or is the delay just until someone has time
to look at it?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2014-03-03 23:25 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
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 [this message]
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-Q3lkMmZpzP@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).