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 56461] NV11 black screen & kernel hang on loading nouveaufb
Date: Sun, 09 Dec 2012 22:53:49 +0000	[thread overview]
Message-ID: <bug-56461-8800-cr5DMSDPoj@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-56461-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #9 from Chris Paulson-Ellis <chris-Tc38MJj1weLQT0dZR+AlfA@public.gmane.org> ---
Hi,

I only just realised that you sent me a second patch (I thought you were
referring to the first patch, so I went and did the bisect as per my previous
message). I've just tried the second patch against nouveau HEAD. Unfortunately
it causes a NULL pointer dereference. I think this is because when this line in
nv04_timer_init...

n = nouveau_hw_get_clock(((struct nouveau_drm *)nouveau_client(priv))->dev,
PLL_CORE);

...calls nouveau_client() it gets NULL, because the parent of nv04_timer_priv
is a nouveau_device, not a nouveau_drm. I can't see any way to get a pointer to
the drm_device from nv04_timer_init, so I don't think calling
nouveau_hw_get_clock from here is possible.

Chris.

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

[-- Attachment #1.2: Type: text/html, Size: 1680 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:[~2012-12-09 22:53 UTC|newest]

Thread overview: 48+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-27 13:17 [Bug 56461] New: NV11 black screen & kernel hang on loading nouveaufb bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-56461-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2012-10-27 13:19   ` [Bug 56461] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-10-27 13:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-11 20:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-12 22:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-12 23:24   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-13  1:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-13  7:40   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-11-18 15:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-09 22:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2012-12-09 23:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-09 23:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-11 12:10   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-11 19:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-11 21:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-12  0:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-12  0:08   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-12  0:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-12 12:23   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-12 19:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-13 22:04   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-13 22:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-13 22:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-13 22:42   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-15 14:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-16 17:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-16 21:38   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-16 22:32   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-17 17:11   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-18 21:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-18 21:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-18 21:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-18 21:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-25 19:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-26 16:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-26 22:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-27 13:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-27 13:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-27 13:17   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-27 13:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2012-12-27 13:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-01-07  1:53   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03 20:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03 20:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-02-03 21:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-04 19:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-16 22:27   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-04-18 18:29   ` 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-56461-8800-cr5DMSDPoj@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.