All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 210321] /display/dc/dcn20/dcn20_resource.c:3240 dcn20_validate_bandwidth_fp+0x8b/0xd0 [amdgpu]
Date: Tue, 19 Jan 2021 22:25:46 +0000	[thread overview]
Message-ID: <bug-210321-2300-LvLr47qJ9L@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-210321-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=210321

--- Comment #3 from Florian Evers (florian-evers@gmx.de) ---
Hi,

new info: this "crash" can be reproduced very easily here on my system. It is
enough to switch the screen off and on again to find the dump in the dmesg log.
I did not test yet whether it happens during switching off or while switiching
it back on, but I may test that using a second box.

I first noticed that the crash never happens if I work or play on my computer,
but if I come back after a pause I certainly found it in the logs. Thus I got
the assumption that it happens during the power saving phase of the screen.
Interestingly, using the power switch of the screen the dump can be triggered
very easily and 100% reliably.

Hope this helps!

Regards,
Florian

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2021-01-19 22:25 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-23 16:45 [Bug 210321] New: /display/dc/dcn20/dcn20_resource.c:3240 dcn20_validate_bandwidth_fp+0x8b/0xd0 [amdgpu] bugzilla-daemon
2020-12-27 20:17 ` [Bug 210321] " bugzilla-daemon
2021-01-07  2:49 ` bugzilla-daemon
2021-01-19 22:25 ` bugzilla-daemon [this message]
2021-03-12 12:31 ` bugzilla-daemon
2021-03-12 15:58 ` bugzilla-daemon

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-210321-2300-LvLr47qJ9L@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dri-devel@lists.freedesktop.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.