All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 206299] [nouveau/xen] RTX 20XX instant reboot
Date: Sun, 26 Jan 2020 20:20:05 +0000	[thread overview]
Message-ID: <bug-206299-2300-yD2wkOXd7a@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206299-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=206299

--- Comment #7 from Frédéric Pierret (frederic.epitre@orange.fr) ---
With Marek, we think to found the problem. In nv50_disp_chan_mthd function, the
exact NULL pointer reference is mthd->data[0]->mthd. Precisely,  mthd->data is
not null but mthd->data[0] seems so.

Trying to access mthd->data[0] we get:
  BUG: kernel NULL pointer dereference, address: 0000000000000010
while trying to access mthd->data[0]->mthd, we get:
  BUG: kernel NULL pointer dereference, address: 0000000000000020

So this is exactly the issue. Any idea why mthd->data and not mthd->data[0]?

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2020-01-26 20:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-24 23:24 [Bug 206299] New: [nouveau/xen] RTX 20XX instant reboot bugzilla-daemon
2020-01-25  0:45 ` [Bug 206299] " bugzilla-daemon
2020-01-25  9:51 ` bugzilla-daemon
2020-01-25  9:51 ` bugzilla-daemon
2020-01-26 15:02 ` bugzilla-daemon
2020-01-26 15:07 ` bugzilla-daemon
2020-01-26 15:55 ` bugzilla-daemon
2020-01-26 20:20 ` bugzilla-daemon [this message]
2020-01-26 21:45 ` bugzilla-daemon
2020-01-26 22:02 ` bugzilla-daemon
2020-01-28  8:36 ` 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-206299-2300-yD2wkOXd7a@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.