All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ@public.gmane.org
To: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
Subject: [Bug 86935] [NV106] unknown kepler chipset 0x106
Date: Wed, 03 Dec 2014 11:12:20 +0000	[thread overview]
Message-ID: <bug-86935-8800-AeJaFePQLF@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-86935-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #7 from Sven <sven.koehler-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> ---
(In reply to Ilia Mirkin from comment #6)
> (In reply to Sven from comment #5)
> > I will try to do the mmiotrace of the blob. Problem is, that the binary
> > nvidia drivers gives me a kernel OOPS. Yay!
> 
> D'oh! Maybe try a newer driver? If it oopses "later" rather than on load/X
> start, then that should be enough for a mmiotrace.

I'm on gentoo. I was using the newest nvidia driver. But I suspect the kernel
was too new. Anyhow, on the 3rd try it didn't oops. Trace has been emailed.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2014-12-03 11:12 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-02 15:19 [Bug 86935] New: unknown kepler chipset bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-86935-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-12-02 15:27   ` [Bug 86935] [NV106] unknown kepler chipset 0x106 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 15:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 15:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 16:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 16:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-02 16:25   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 11:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2014-12-03 11:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 12:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 12:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-03 13:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-18 23:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-27 18:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-12-27 18:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-02-14 20:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2015-03-20  4:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ

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-86935-8800-AeJaFePQLF@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon-cc+yj3umiyqdupfqwhejaq@public.gmane.org \
    --cc=nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.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.