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 105174] New: [regression] BUG unable to handle kernel NULL pointer dereference in kernel 4.15.3
Date: Tue, 20 Feb 2018 11:06:05 +0000	[thread overview]
Message-ID: <bug-105174-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 105174
           Summary: [regression] BUG unable to handle kernel NULL pointer
                    dereference in kernel 4.15.3
           Product: xorg
           Version: unspecified
          Hardware: x86-64 (AMD64)
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: dominik-IZ6Av6enwRKJQ7yn63+t2w@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 137463
  --> https://bugs.freedesktop.org/attachment.cgi?id=137463&action=edit
full dmesg

After updating to Fedora kernel 4.15.3-300.fc27.x86_64, I got:
BUG: unable to handle kernel NULL pointer dereference at 0000000000000040
IP: nouveau_mem_host+0x47/0x1b0 [nouveau]

Full dmesg attached. The hardware is Dell XPS 15 with Intel and nVidia GPU in
Optimus configuration.

Note: this looks different from bug 105173.

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

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

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

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

             reply	other threads:[~2018-02-20 11:06 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-20 11:06 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-105174-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-02-20 11:15   ` [Bug 105174] [regression] BUG unable to handle kernel NULL pointer dereference in kernel 4.15.3 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-20 11:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-20 11:20   ` [Bug 105174] [GF108][Regression] Unable to handle NULL pointer dereference in nouveau_mem_host since " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-20 16:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-22 15:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-22 15:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-22 15:21   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-24 20:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-02-24 20:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-01 18:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-05 12:34   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-09 19:51   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-13 14:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-13 14:59   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-15 10:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-17 14:54   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-17 14:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-19  9:35   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-20 14:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-22 17:43   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-23  9:30   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-26  9:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-26  9:47   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-03-26 11:01   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-05-09 12:18   ` 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-105174-8800@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.