From: "Christian König" <ckoenig.leichtzumerken@gmail.com>
To: Mikael Pettersson <mikpelinux@gmail.com>,
Linux Kernel list <linux-kernel@vger.kernel.org>,
amd-gfx@lists.freedesktop.org,
Kai-Heng Feng <kai.heng.feng@canonical.com>
Subject: Re: [REGRESSION][BISECTED] 5.9-rc4 disables console on radeon
Date: Wed, 9 Sep 2020 11:15:11 +0200 [thread overview]
Message-ID: <d207de12-3143-1243-bcff-b4ccbfb32b92@gmail.com> (raw)
In-Reply-To: <CAM43=SOCs699z9E1EK3EG8BCJFw_9veWa7xWOEokvwj01NVS6Q@mail.gmail.com>
Yes, that is an already known issue.
We are most likely going to revert the patch ASAP.
Christian.
Am 08.09.20 um 18:27 schrieb Mikael Pettersson:
> Starting with linux-5.9-rc4, the Dell monitor on my desktop PC goes
> black during boot
> when the kernel activates the framebuffer console, except for this
> error message shown
> in the center of the screen:
>
> "Dell U2412M
> The current input timing is not supported by the monitor display. Please
> change your input timing to 1920x1200@60Hz or any other monitor
> listed timing as per the monitor specifications.
> <DVI symbol>"
>
> The monitor remains black until I reboot.
>
> All kernels up to and including 5.9-rc3 were Ok. A git bisect identified
>
> # first bad commit: [fc8c70526bd30733ea8667adb8b8ffebea30a8ed]
> drm/radeon: Prefer lower feedback dividers
>
> as the culprit, and reverting that from -rc4 makes the console work again.
>
> Adding a bit of debugging code to that function shows:
>
> avivo_get_fb_ref_div: fb_div_new 136 fb_div_old 137
> avivo_get_fb_ref_div: fb_div_new 142 fb_div_old 143
> avivo_get_fb_ref_div: fb_div_new 136 fb_div_old 137
> avivo_get_fb_ref_div: fb_div_new 119 fb_div_old 120
> avivo_get_fb_ref_div: fb_div_new 136 fb_div_old 137
>
> during boot, where "new" is what the commit above changed the code to compute,
> and "old" is the value computed by the working code from rc3.
>
> The graphics card is a Radeon HD6450 silent model:
> 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc.
> [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] (prog-if 00
> [VGA controller])
> _______________________________________________
> amd-gfx mailing list
> amd-gfx@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/amd-gfx
prev parent reply other threads:[~2020-09-09 9:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-08 16:27 Mikael Pettersson
2020-09-09 9:15 ` Christian König [this message]
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=d207de12-3143-1243-bcff-b4ccbfb32b92@gmail.com \
--to=ckoenig.leichtzumerken@gmail.com \
--cc=amd-gfx@lists.freedesktop.org \
--cc=christian.koenig@amd.com \
--cc=kai.heng.feng@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpelinux@gmail.com \
/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
all inboxes | Powered by JetHome®