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 64772] New: nouveau GF108 kernel errors and graphics corruption when enabling second output
Date: Sun, 19 May 2013 20:42:09 +0000	[thread overview]
Message-ID: <bug-64772-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 64772
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: nouveau GF108 kernel errors and graphics corruption
                    when enabling second output
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: All
          Reporter: pasik-X3B1VOXEql0@public.gmane.org
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

Created attachment 79548
  --> https://bugs.freedesktop.org/attachment.cgi?id=79548&action=edit
nouveau errors, dmesg from Linux kernel 3.9.2

I'm using Lenovo T430 laptop with intel/nvidia hybrid graphics, but optimus is
disabled in BIOS, and only the Nvidia discreet GPU is enabled currently:

$ lspci | grep VGA
01:00.0 VGA compatible controller: NVIDIA Corporation GF108 [Quadro NVS 5400M]
(rev a1)

I boot up the laptop with only using the laptop internal LVDS panel, and when
in X session, I connect DVI cable to the docking station. xrandr now correctly
shows DP2 as connected, and when I enable the DVI display, I get these nouveau
errors in the kernel dmesg:

[  103.196252] nouveau  [   PLTCG][0000:01:00.0] LTC0_LTS0: 0x036f0040
[  103.196257] nouveau  [   PLTCG][0000:01:00.0] LTC0_LTS1: 0x036f0040
[  103.353160] nouveau E[      VM][0000:01:00.0] failed to create 0x04000000,
-28
[  103.353163] nouveau E[      VM][0000:01:00.0] failed to create 0x02000000,
-28
[  103.353923] nouveau E[      VM][0000:01:00.0] failed to create 0x04000000,
-28
[  103.353925] nouveau E[      VM][0000:01:00.0] failed to create 0x02000000,
-28
..
..

DVI monitor output actually gets enabled, and I can see the desktop there, but
both the LVDS display and the DVI display are all messed up.

For example moving a window around leaves traces of other window contents, and
the background image gets replaced with all kinds of corrupted patterns, so
graphics looks quite weird and corrupted on both displays.

Switching back to only using the internal LVDS (disabling DVI/DP2 output) fixes
the graphics corruptions.

$ uname -a
Linux localhost.localdomain 3.8.11-200.fc18.x86_64 #1 SMP Wed May 1 19:44:27
UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

I also tried Linux kernel 3.9.2, and there I get exactly the same graphics
corruption behaviour, but the kernel errors are slightly different:

[   91.533612] nouveau  [   PLTCG][0000:01:00.0] LTC0_LTS0: 0x036f0040
[   91.533618] nouveau  [   PLTCG][0000:01:00.0] LTC0_LTS1: 0x036f0040
[   91.533856] nouveau E[    PBUS][0000:01:00.0] MMIO read of 0x00000000 FAULT
at 0x141820 [ IBUS ]
[  246.466283] nouveau E[      VM][0000:01:00.0] failed to create 0x04000000,
-28
[  246.466287] nouveau E[      VM][0000:01:00.0] failed to create 0x02000000,
-28
[  246.499229] nouveau E[      VM][0000:01:00.0] failed to create 0x04000000,
-28
[  246.499232] nouveau E[      VM][0000:01:00.0] failed to create 0x02000000,
-28


Dmesg from Linux 3.9.2 attached.

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

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

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

_______________________________________________
Nouveau mailing list
Nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
http://lists.freedesktop.org/mailman/listinfo/nouveau

             reply	other threads:[~2013-05-19 20:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-19 20:42 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-64772-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2013-09-06 22:12   ` [Bug 64772] [NVC1] nouveau GF108 kernel errors and graphics corruption when enabling second output bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-23 15:19   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-09-27 16:55   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2013-11-09 20:20   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-11 12:54   ` 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-64772-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.