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 77674] [NVE7] "failed to read DPCD" on wake up with external monitor
Date: Tue, 18 Nov 2014 07:36:03 +0000	[thread overview]
Message-ID: <bug-77674-8800-T0YRmUCDcn@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-77674-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>


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

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

--- Comment #8 from Dominique Dumont <domi.dumont-GANU6spQydw@public.gmane.org> ---
Hello

I have a similar problem with my laptop:
01:00.0 VGA compatible controller: NVIDIA Corporation GF106GLM [Quadro 2000M]
(rev a1)
kernel: SMP Debian 3.16.7-2 (2014-11-06) x86_64 GNU/Linux

The options nouveau.debug=VBIOS=trace,PDISP=trace,I2C=trace drm.debug=0xe does
make the setup more robust, but I has a crash this morning while expanding the
screen display to an external monitor connected to a dock station.

For what it's worth, I've attached a kern.log generated with the above trace
from the wake up of the machine up to the crash.


Hope this helps

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

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

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

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

  parent reply	other threads:[~2014-11-18  7:36 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-19 17:25 [Bug 77674] New: "failed to read DPCD" on wake up with external monitor bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
     [not found] ` <bug-77674-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2014-04-19 17:38   ` [Bug 77674] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-04-19 17:39   ` [Bug 77674] [NVE7] " bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-11 23:33   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-20 23:50   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-24 14:22   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-24 17:58   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-06-24 18:07   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-18  7:31   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2014-11-18  7:36   ` bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
2019-12-04  8:45   ` 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-77674-8800-T0YRmUCDcn@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.