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 64774] nouveau GF108 kernel crash in optimus mode when enabling external display output
Date: Wed, 21 Aug 2013 17:03:59 +0000	[thread overview]
Message-ID: <bug-64774-8800-mR6YOu5KUN@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-64774-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #22 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
We should figure out why it's getting stuff that it doesn't expect. I had
suggested adding the warn solely to avoid the crash down the line. I guess it's
reasonable for the upstream kernel to have that, as if it ever fires, we're
going to be in trouble later... I think. Will have to re-check the code. I can
post it with my analysis if you like, or you can.

Could you retest this with 3.11-rc6 BTW? The whole fb pinning/etc logic was
reworked, and your issue may have been fixed by it.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

  parent reply	other threads:[~2013-08-21 17:03 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 20:54 [Bug 64774] New: nouveau GF108 kernel crash in optimus mode when enabling external display output bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-64774-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-05-19 20:55   ` [Bug 64774] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 20:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-05-19 21:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:37   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 20:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 21:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-18 21:15   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 12:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-19 14:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-07-21 10:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 18:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-13 20:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 16:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-08-21 17:03   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2013-08-21 17:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-10-01 16:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-02  0:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-02  1:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-01-06 16:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  8:34   ` 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-64774-8800-mR6YOu5KUN@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.