From: Frank Wunderlich <frank-w@public-files.de>
To: Chun-Kuang Hu <chunkuang.hu@kernel.org>
Cc: chunkuang Hu <chunkuang.hu@kernel.org>,
Dafna Hirschfeld <dafna.hirschfeld@collabora.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
Enric Balletbo i Serra <enric.balletbo@collabora.com>,
David Airlie <airlied@linux.ie>,
"moderated list:ARM/Mediatek SoC support"
<linux-mediatek@lists.infradead.org>,
dri-devel <dri-devel@lists.freedesktop.org>,
Thomas Zimmermann <tzimmermann@suse.de>,
Collabora Kernel ML <kernel@collabora.com>,
Matthias Brugger <matthias.bgg@gmail.com>
Subject: Aw: Re: Re: Re: BUG: MTK DRM/HDMI broken on 5.13 (mt7623/bpi-r2)
Date: Mon, 12 Jul 2021 10:11:08 +0200 [thread overview]
Message-ID: <trinity-2d1b055a-73b0-4a15-9677-08fd13fd486d-1626077468706@3c-app-gmx-bs28> (raw)
In-Reply-To: <CAAOTY_-yi5NP_U-m==ZHeBNC9-6NrjUacKWdmmgVXZjH+sFZKw@mail.gmail.com>
Hi,
HDMI is broken again in 5.14-rc1 (of course i have applied my patch [1])
now i've got a NULL pointer dereference
[ 21.883641] PC is at mtk_dpi_bridge_atomic_check+0x38/0x78
[ 21.889158] LR is at drm_atomic_bridge_chain_check+0x150/0x30c
"dpi" is not set correctly in mtk_dpi_bridge_atomic_check
this function is new since
commit ec8747c52434b69cea2b18068e72f051e23d3839
drm/mediatek: dpi: Add bus format negotiation
i do not see where bridge->driver_private is set, but in other function it is solved like this:
bridge_to_dpi(bridge)
this fixes the NULL-pointer dereference, and system starts to xserver, but i do not see fbcon...it looks like drm is now initialized later (~ at login prompt on serial console). i stopped lightdm and still do not see loginprompt on hdmi, so it looks like fbcon is broken
send out fix for NULL issue, but fbcon ist still unclear...but i see this in dmesg:
dmesg | grep -i fbcon
[ 0.000000] Kernel command line: root=/dev/mmcblk0p2 rw rootwait earlyprintk console=ttyS0,115200 video=1280x1024 console=tty1 fbcon=map:0
[ 0.000000] Unknown command line parameters: fbcon=map:0
[ 7.040167] fbcon=map:0
and no framebuffer/fb0 in dmesg
regards Frank
[1] https://patchwork.kernel.org/project/linux-mediatek/patch/20210710132431.265985-1-linux@fw-web.de/
prev parent reply other threads:[~2021-07-12 9:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-06 9:54 BUG: MTK DRM/HDMI broken on 5.13 (mt7623/bpi-r2) Frank Wunderlich
2021-07-06 11:20 ` Daniel Vetter
2021-07-06 11:40 ` Aw: " Frank Wunderlich
2021-07-07 14:58 ` Chun-Kuang Hu
2021-07-07 15:03 ` Chun-Kuang Hu
2021-07-07 16:33 ` Aw: " Frank Wunderlich
2021-07-08 7:22 ` Dafna Hirschfeld
2021-07-08 8:00 ` Aw: " Frank Wunderlich
2021-07-08 9:35 ` Frank Wunderlich
2021-07-08 12:30 ` Dafna Hirschfeld
2021-07-08 14:01 ` Aw: " Frank Wunderlich
2021-07-08 15:31 ` Aw: " Frank Wunderlich
2021-07-09 10:02 ` Frank Wunderlich
2021-07-09 10:24 ` Enric Balletbo Serra
2021-07-09 10:38 ` Aw: " Frank Wunderlich
2021-07-09 11:28 ` Frank Wunderlich
2021-07-09 16:53 ` Chun-Kuang Hu
2021-07-12 8:11 ` Frank Wunderlich [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=trinity-2d1b055a-73b0-4a15-9677-08fd13fd486d-1626077468706@3c-app-gmx-bs28 \
--to=frank-w@public-files.de \
--cc=airlied@linux.ie \
--cc=chunkuang.hu@kernel.org \
--cc=dafna.hirschfeld@collabora.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=enric.balletbo@collabora.com \
--cc=kernel@collabora.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@gmail.com \
--cc=tzimmermann@suse.de \
/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).