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 103421] New: Kernel 4.13+ nouveau breaks screen output
Date: Mon, 23 Oct 2017 13:28:16 +0000	[thread overview]
Message-ID: <bug-103421-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 103421
           Summary: Kernel 4.13+ nouveau breaks screen output
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: kbaikov-IBi9RG/b67k@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 135010
  --> https://bugs.freedesktop.org/attachment.cgi?id=135010&action=edit
kernel log

There is a regression with my

02:00.0 VGA compatible controller [0300]: NVIDIA Corporation GF119 [NVS
310] [10de:107d] (rev a1)

where I would not get any graphics output anymore with Linux kernel
4.13.x, not even (framebuffer) text consoles.

There is a NULL pointer dereference around nvkm_dp_train_drive
visible in dmesg (attached)

and looking at the nouveau.ko disassembly, the faulting instruction was
a call to a variable address e.g. from
drivers/gpu/drm/nouveau/nvkm/engine/disp/dp.c:
        ior->func->dp.drive(ior, i, ocfg.pc, ocfg.dc,
                                    ocfg.pe, ocfg.tx_pu);

which was introduced in commit af85389c614ae
so maybe you have a hint at what might be wrong or how to further debug
this problem...


With 4.12.8, there was a different NULL pointer deref but some working
graphics.
I also tried 4.14-rc3 or such but that still had broken graphics.

Thanks in advance for any help

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

[-- Attachment #1.2: Type: text/html, Size: 3133 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:[~2017-10-23 13:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-23 13:28 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-103421-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-11-10  0:13   ` [Bug 103421] Kernel 4.13+ nouveau breaks screen output bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-10  0:18   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-10 15:12   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-10 15:14   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-11-10 15:16   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-06 16:02   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-08 12:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-16 21:09   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2018-01-17 16:25   ` 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-103421-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.