All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 89536] GPU lockup and kernel OOPS when using PRIME
Date: Wed, 25 Mar 2015 13:54:34 +0000	[thread overview]
Message-ID: <bug-89536-502-Hrllejbdry@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-89536-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 683 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=89536

--- Comment #9 from Rafael Ristovski <rafael.ristovski@gmail.com> ---
(In reply to Michel Dänzer from comment #8)
> (In reply to Rafael Ristovski from comment #7)
> > I just downgraded, PRIME worked flawlessly up until 3.19, I was able to test
> > up until 3.17.6-1 since the next one after that was the latest kernel in the
> > [testing] repo aka 3.19.2-1
> 
> Can you narrow it down further, ideally bisect?

I guess I could try, but not in the near future as I lack free time. Will
report back once done or when any progress is made.

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

[-- Attachment #1.2: Type: text/html, Size: 1600 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2015-03-25 13:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-11 16:44 [Bug 89536] GPU lockup and kernel OOPS when using PRIME bugzilla-daemon
2015-03-11 16:54 ` bugzilla-daemon
2015-03-11 17:02 ` bugzilla-daemon
2015-03-11 17:03 ` bugzilla-daemon
2015-03-11 17:04 ` bugzilla-daemon
2015-03-12 17:09 ` bugzilla-daemon
2015-03-14 18:58 ` bugzilla-daemon
2015-03-21 12:35 ` bugzilla-daemon
2015-03-21 13:24 ` bugzilla-daemon
2015-03-25  7:37 ` bugzilla-daemon
2015-03-25 13:54 ` bugzilla-daemon [this message]
2019-11-19  9:02 ` 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-89536-502-Hrllejbdry@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.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.