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 103284] Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp
Date: Mon, 16 Oct 2017 22:30:20 +0000	[thread overview]
Message-ID: <bug-103284-8800-RUY17pCFwr@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-103284-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #3 from Ilia Mirkin <imirkin-FrUbXkNCsVf2fBVCVOL8/A@public.gmane.org> ---
OK, so looks like it very successfully creates a GT214_DISP object, and then
proceeds to call nv50_display_create. This then does not trigger *any* further
traces, and errors out. It errors out before the dmac is initialized, and I
think something in the list head thing fails.

Now, as I recall, SPARC has 8k pages. You could try bumping some of those 4096
values up to 8192 and see if that magically makes it work, at least a little
(like the nouveau_bo_new).

If you're sufficiently interested, you could add a lot more prints throughout
that file to see exactly what fails, and then try to resolve it.

It might be an uphill battle though - a bunch of stuff is tied to 4K pages, I
think.

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

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

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

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

  parent reply	other threads:[~2017-10-16 22:30 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-15 21:59 [Bug 103284] New: Unable to handle kernel NULL pointer dereference on 4.13.0-1-sparc64-smp bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-103284-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-10-15 23:19   ` [Bug 103284] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-16 22:13   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-16 22:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2017-10-22 20:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-10-22 20:57   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:31   ` 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-103284-8800-RUY17pCFwr@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.