From: Thorsten Leemhuis <regressions@leemhuis.info>
To: "regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: Dual monitor with amd 5700 causes system to,hang at startup (fwd from bugzilla) #forregzbot
Date: Sat, 22 Jan 2022 09:56:23 +0100 [thread overview]
Message-ID: <99dc2b1f-2c46-04fb-86ea-92a748e495de@leemhuis.info> (raw)
Lo! There is a regression dealt with in bugzilla I'd like to add to the
tracking:
#regzbot introduced: v5.15.8..v5.15.13
#regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=215511
#regzbot from: Jose Mestre <pmestre@gmail.com>
#regzbot title: drm: amdgpu: Dual monitor with amd 5700 causes system to
hang at startup.
Note: also present in 5.16.1
Quote:
> Hello, system mostly crashes (sometimes in different ways) when i
> start with more than one monitor attached.
>
> If i switch off one monitor then system boots correctly (i don't need
> to detach the displayport cable, just to switch off the monitor).
>
>
> When both monitors are connected, most of the times it just crashes
> as the attached log, sometimes it boots but screen is flickering and
> with artifacts.
>
> This happened with kernel 5.10 and 5.11, it was fixed i don't
> remember exactly when, and is happening again. For me it worked with
> kernel 5.15.8 and failed with 5.15.13. It is still failing with
> 5.16.1.
>
> Kind regards and many thanks for your work in the most crucial
> open-source project.
Ciao, Thorsten
TWIMC: this mail is primarily send for documentation purposes and for
regzbot, my Linux kernel regression tracking bot. These mails usually
contain '#forregzbot' in the subject, to make them easy to spot and filter.
next reply other threads:[~2022-01-22 8:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-22 8:56 Thorsten Leemhuis [this message]
2022-02-16 14:33 ` Dual monitor with amd 5700 causes system to,hang at startup (fwd from bugzilla) #forregzbot Thorsten Leemhuis
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=99dc2b1f-2c46-04fb-86ea-92a748e495de@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).