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 101764] New: [regression] eaa2c988033b breaks GTX1050TI (GP107 / NV137)
Date: Wed, 12 Jul 2017 10:07:03 +0000	[thread overview]
Message-ID: <bug-101764-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 101764
           Summary: [regression] eaa2c988033b breaks GTX1050TI (GP107 /
                    NV137)
           Product: xorg
           Version: unspecified
          Hardware: Other
                OS: All
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: carlo-KA+7E9HrN00dnm+yROfE0A@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

Created attachment 132629
  --> https://bugs.freedesktop.org/attachment.cgi?id=132629&action=edit
GP107_regression_oops_log

Hi,
we have verified that commit eaa2c988033b ("drm/nouveau/gr/gp107: initial
support") is actually breaking the GTX1050TI on an Acer laptop.
It's not possible to reach Xorg anymore and the journal is filled with Oops as
shown in the attachment.

Thanks,

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

[-- Attachment #1.2: Type: text/html, Size: 2529 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-07-12 10:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 10:07 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-101764-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2017-07-12 10:22   ` [Bug 101764] [regression] eaa2c988033b breaks GTX1050TI (GP107 / NV137) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-12 10:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-12 14:05   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-12 14:06   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-12 15:44   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-12 15:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-12 15:45   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-12 16:56   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-17  9:52   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2017-07-20 14:01   ` 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-101764-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.