subject:"\[Bug 1968040\] Re\: Blanked screen doesn't wake up after locking \[drmModeAtomicCommit\: Argument invalide\] \[drmModeAtomicCommit\: Invalid argument\]"

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-17 Thread Daniel van Vugt

This is looking like a kernel bug (comment #81) and increasingly unlike
mutter has done anything wrong. Sounds like it is specifically about
i915 HDMI handling.

** Also affects: linux (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux (Ubuntu)
   Status: New => Confirmed

** Summary changed:

- Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument 
invalide] [drmModeAtomicCommit: Invalid argument]
+ [i915] Blanked screen doesn't wake up after locking [drmModeAtomicCommit: 
Argument invalide] [drmModeAtomicCommit: Invalid argument]

** Also affects: linux-hwe-5.19 (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: linux-hwe-5.19 (Ubuntu)
   Status: New => Confirmed

** Tags added: i915

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

Title:
  [i915] Blanked screen doesn't wake up after locking
  [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid
  argument]

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-17 Thread Daniel van Vugt

Thanks!

It looks like most of the errors are in fact caused by previous errors:

i915 :00:02.0: [drm:drm_atomic_crtc_check [drm]] [CRTC:45:pipe A] 
requesting event but off
i915 :00:02.0: [drm:drm_atomic_check_only [drm]] [CRTC:45:pipe A] atomic 
core check failed
...
KMS: [atomic] KMS update failed: drmModeAtomicCommit: Invalid argument

So those could be improved, but they're not the root cause.

The root cause seems to be a failure of the first frame (modeset) when
waking from sleep:

i915 :00:02.0: [drm:intel_hdmi_compute_clock [i915]] picking 12 bpc for 
HDMI output (pipe bpp: 36)
i915 :00:02.0: [drm:intel_hdmi_compute_config [i915]] bad AVI infoframe
i915 :00:02.0: [drm:intel_modeset_pipe_config [i915]] Encoder config 
failure: -22

That "-22" is the first "Invalid argument".

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-14 Thread aleksey

Hi, Daniel

I performed next changes:
1. GRUB_CMDLINE_LINUX_DEFAULT="quiet splash drm.debug=0xff"
2. Add to /etc/environment: MUTTER_DEBUG=kms



** Attachment added: "journal.txt"
   
https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5664106/+files/journal.txt

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-12 Thread Daniel van Vugt

Note to self:

One possible explanation here is that we're setting this twice in the
same commit, which some drivers might reject(?):

Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting connector 79 
(/dev/dri/card0) property 'CRTC_ID' (20) to 0
Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting connector 79 
(/dev/dri/card0) property 'CRTC_ID' (20) to 45

Another possible cause might be a bad size in:

Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting CRTC (45, 
/dev/dri/card0) gamma, size: 256
Apr 12 19:36:45 ty gnome-shell[1455]: KMS: [atomic] Setting CRTC 45 
(/dev/dri/card0) property 'GAMMA_LUT' (28) to 97

Although that doesn't explain all instances of the error.

Also curious that I don't see any confirmed cases of this bug in 22.10
and later.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-12 Thread Daniel van Vugt

Thanks but we do need drm.debug=0xff to make any progress here. You add
it in /etc/default/grub as part of GRUB_CMDLINE_LINUX_DEFAULT and then
run:

  sudo update-grub

and reboot.

-- 
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

Title:
  Blanked screen doesn't wake up after locking [drmModeAtomicCommit:
  Argument invalide] [drmModeAtomicCommit: Invalid argument]

To manage notifications about this bug go to:
https://bugs.launchpad.net/gnome-shell/+bug/1968040/+subscriptions


-- 
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs

[Bug 1968040] Re: Blanked screen doesn't wake up after locking [drmModeAtomicCommit: Argument invalide] [drmModeAtomicCommit: Invalid argument]

2023-04-12 Thread aleksey

Hi team and all.

I'm stuck with a similar issue.
The solution with MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 helped me! Thanks guys!

I created logs for you (without kernel parameter: drm.debug=0xff, can't find
how do it).
If somebody wants to help collect logs it easy perform without working screen:
1. Disable authorization after sleep in the settings->privacy->screen.
2. Send Ubuntu sleep.
3. Start Ubuntu.

Now goes steps with a black screen but PC looks working:
1. Ctrl + Alt + T for open terminal.
2. Write journalctl -b0 > journal.txt ( I used the UP key for using the last
terminal command).
3. restart your PC.
4. journal.txt will be in the HOME directory.

Good luck all us!

** Attachment added: "journal.txt"

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/566/+files/journal.txt

** Attachment removed: "journal.txt"

https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1968040/+attachment/5663331/+files/journal.txt

--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1968040

77 matches

Mail list logo