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 105916] New: "xset dpms force off" can't be undone on hp omen 17-an0xx laptop
Date: Thu, 05 Apr 2018 22:51:00 +0000	[thread overview]
Message-ID: <bug-105916-8800@http.bugs.freedesktop.org/> (raw)


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

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

            Bug ID: 105916
           Summary: "xset dpms force off" can't be undone on hp omen
                    17-an0xx laptop
           Product: xorg
           Version: git
          Hardware: x86-64 (AMD64)
                OS: Linux (All)
            Status: NEW
          Severity: normal
          Priority: medium
         Component: Driver/nouveau
          Assignee: nouveau-PD4FTy7X32lNgt0PjOBp9y5qC8QIuHrW@public.gmane.org
          Reporter: bero-Qev7zP1q8vftRgLqZ5aouw@public.gmane.org
        QA Contact: xorg-team-go0+a7rfsptAfugRpC6u6w@public.gmane.org

After turning the display off with "xset dpms force off", "xset dpms force
suspend" or "xset dpms force standby", the display can't be turned back on
(short of turning the entire laptop off and back on), even "xset dpms force on"
has no effect.

lspci reports this about the GPU:
01:00.0 0300: 10de:1be1 (rev a1) (prog-if 00 [VGA controller])
        Subsystem: 103c:8393
        Flags: bus master, fast devsel, latency 0, IRQ 132
        Memory at db000000 (32-bit, non-prefetchable) [size=16M]
        Memory at b0000000 (64-bit, prefetchable) [size=256M]
        Memory at c0000000 (64-bit, prefetchable) [size=32M]
        I/O ports at e000 [size=128]
        Expansion ROM at dc000000 [disabled] [size=512K]
        Capabilities: [60] Power Management version 3
        Capabilities: [68] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [78] Express Endpoint, MSI 00
        Capabilities: [100] Virtual Channel
        Capabilities: [250] Latency Tolerance Reporting
        Capabilities: [258] L1 PM Substates
        Capabilities: [128] Power Budgeting <?>
        Capabilities: [420] Advanced Error Reporting
        Capabilities: [600] Vendor Specific Information: ID=0001 Rev=1 Len=024
<?>
        Capabilities: [900] #19
        Kernel driver in use: nouveau
        Kernel modules: nvidiafb, nouveau

related dmesg bits after normal startup:
[Fri Apr  6 00:34:36 2018] fb: switching to nouveaufb from EFI VGA
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: NVIDIA GP104 (134000a1)
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: bios: version 86.04.67.00.17
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: fb: 8192 MiB GDDR5
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: VRAM: 8192 MiB
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: GART: 536870912 MiB
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: BIT table 'A' not found
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: BIT table 'L' not found
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: TMDS table version 2.0
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB version 4.1
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB outp 00: 02803f76
04400020
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB outp 01: 02012f62
00020010
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB outp 02: 04824f86
04400010
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB outp 03: 04824f82
00020010
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB outp 04: 04835f96
04400020
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB outp 05: 04835f92
00020020
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB conn 02: 00010261
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB conn 03: 00020347
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB conn 04: 01000446
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: DCB conn 05: 02000546
[Fri Apr  6 00:34:36 2018] nouveau 0000:01:00.0: DRM: MM: using COPY for buffer
copies
[Fri Apr  6 00:34:37 2018] nouveau 0000:01:00.0: DRM: allocated 3840x2160 fb:
0x200000, bo 0000000055fe5b7c
[Fri Apr  6 00:34:37 2018] fbcon: nouveaufb (fb0) is primary device
[Fri Apr  6 00:34:37 2018] nouveau 0000:01:00.0: disp: 0x0000643b[0]:
INIT_GENERIC_CONDITON: unknown 0x07
[Fri Apr  6 00:34:37 2018] nouveau 0000:01:00.0: disp: 0x00005fcc[2]:
INIT_GENERIC_CONDITON: unknown 0x07
[Fri Apr  6 00:34:37 2018] nouveau 0000:01:00.0: fb0: nouveaufb frame buffer
device
[Fri Apr  6 00:34:37 2018] [drm] Initialized nouveau 1.3.1 20120801 for
0000:01:00.0 on minor 0

Kernel 4.16.0, Mesa 18.0.0, libdrm 2.4.90, xorg-server 1.19.6, using
modesetting DDX from xorg-server 1.19.6

dmesg after (successful but irreversible) "xset dpms force off":
[Fri Apr  6 00:49:48 2018] nouveau 0000:01:00.0: disp: 0x0000643b[0]:
INIT_GENERIC_CONDITON: unknown 0x07

dmesg after (unsuccessful) "xset dpms force on" issued over ssh:
[Fri Apr  6 00:50:15 2018] nouveau 0000:01:00.0: disp: 0x00005fcc[2]:
INIT_GENERIC_CONDITON: unknown 0x07

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

[-- Attachment #1.2: Type: text/html, Size: 6199 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:[~2018-04-05 22:51 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 22:51 bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ [this message]
     [not found] ` <bug-105916-8800-V0hAGp6uBxMKqLRl/0Ahz6D7qz1kEfGD2LY78lusg7I@public.gmane.org/>
2018-04-05 22:52   ` [Bug 105916] "xset dpms force off" can't be undone on hp omen 17-an0xx laptop bugzilla-daemon-CC+yJ3UmIYqDUpFQwHEjaQ
2019-12-04  9:37   ` 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-105916-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.