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 84203] New: HDMI gives no more signal
Date: Mon, 22 Sep 2014 22:40:48 +0000	[thread overview]
Message-ID: <bug-84203-8800@http.bugs.freedesktop.org/> (raw)


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

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

          Priority: medium
            Bug ID: 84203
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
           Summary: HDMI gives no more signal
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org
          Severity: normal
    Classification: Unclassified
                OS: Linux (All)
          Reporter: jean-louis-h84OYfGOAs2zQB+pC5nmwQ@public.gmane.org
          Hardware: Other
            Status: NEW
           Version: unspecified
         Component: Driver/nouveau
           Product: xorg

This week I tried HDMI again on my system, and noticed it was completely
broken.
Got just no signal on my screen.

I knew it was working some months (and upgrades) ago.
After testing I found out the issue was introduced between kernel v3.14 and
v3.15.

Situation:
Insert HDMI cable into my laptop, and no signal on the external display.

The dmesg fills with errors also:
[  186.210622] nouveau E[   PDISP][0000:01:00.0] INVALID_STATE [UNK08] chid 0
mthd 0x0080 data 0x00000000
[  186.210627] nouveau E[   PDISP][0000:01:00.0] Core:
[  186.210634] nouveau E[   PDISP][0000:01:00.0]     0x0084: 0x5dc34da1 ->
0x80000000
[  186.210640] nouveau E[   PDISP][0000:01:00.0]     0x0088: 0x00000000         

etc.

After some git bisect playtime, I found out the following commit caused the
issue:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/gpu/drm/nouveau?id=05c63c2ff23a80b654d6c088ac3ba21628db0173

So I went back to stable 3.16 (Ubuntu Utopic version), and did a git revert for
that commit.
And yep, HDMI output was working again, and no more nouveau errors in dmesg.


My device:
[   30.823267] nouveau  [  DEVICE][0000:01:00.0] BOOT0  : 0x0c1a00a1
[   30.823269] nouveau  [  DEVICE][0000:01:00.0] Chipset: GF108 (NVC1)
[   30.823270] nouveau  [  DEVICE][0000:01:00.0] Family : NVC0

Laptop dell xps 15 l502x

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

[-- Attachment #1.2: Type: text/html, Size: 3446 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:[~2014-09-22 22:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-22 22:40 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-84203-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-09-22 22:44   ` [Bug 84203] [NVC1] HDMI gives no more signal since 3.15 (optimus) bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-09-22 22:46   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-10-03 18:33   ` 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-84203-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.