From: Stefan Wahren <stefan.wahren@i2se.com>
To: Peter Robinson <pbrobinson@gmail.com>
Cc: Peter Mattern <pmattern@arcor.de>,
Maxime Ripard <maxime@cerno.tech>,
dri-devel@lists.freedesktop.org
Subject: Re: drm/vc4: module dysfunctional on Raspberry Pi 3B as of 5.18.0
Date: Thu, 9 Jun 2022 23:33:01 +0200 [thread overview]
Message-ID: <fb2035d3-5322-7b03-e9fc-89ce1f892db6@i2se.com> (raw)
In-Reply-To: <CALeDE9OkN5Vq-_L=VzSdKK0=6dKrNBX1q3zm3ZaNX8Jy9VJ35w@mail.gmail.com>
Hi Peter,
Am 09.06.22 um 13:52 schrieb Peter Robinson:
>>>>> As of Linux 5.18.0, module vc4 apparently isn't working on Raspberry Pi
>>>>> 3B any more.
>>>>>
>>>>> If a monitor is attached to the device, the boot messages show up as
>>>>> usual, but right when KMS starts, the screen turns black. Similarly, the
>>>>> screen also turns black when the module is blacklisted at boot time and
>>>>> loaded from the running system.
>>>>> The problem looks quite similar to the one posted some months ago in [1].
>>> If I understand you properly, it results in a blank screen if the
>>> monitor is connected, but the system is still responsive?
>>>
>>> If so, it's a very different problem than the link you provided, since
>>> it was occurring when no monitor was connected and resulted in a total
>>> system hang.
>>>
>>>>> Unfortunately, looking through systemd's journal didn't seem to yield
>>>>> any real hint. Nevertheless, the results from grepping vc4 are
>>>> I'm seeing the same issue with vc4 on a RPi3 on 5.18.1 on Fedora so
>>>> can confirm the regression. Maxime would know what might be up here?
>> i assume you are using the downstream DTB?
> In this case it's the one in the Linux kernel (not sure if that's
> upstream or downstream in this context) not the one provided by the
> RPi firmware.
okay thanks. I tried the kernel config but its huge.
Is it correct that the issue occurs with your kernel config, but not
with multi_v7_defconfig?
>
>> Please provide the version/date of the GPU firmware?
> [ 6.205121] raspberrypi-firmware soc:firmware: Attached to firmware
> from 2022-05-24T13:26:52
> Which is git f145afc
This is good. I had issues with older firmware which didn't implement
RPI_FIRMWARE_NOTIFY_DISPLAY_DONE. So it must be something different.
next prev parent reply other threads:[~2022-06-09 21:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-05 18:01 drm/vc4: module dysfunctional on Raspberry Pi 3B as of 5.18.0 Peter Mattern
2022-06-08 13:10 ` Peter Robinson
2022-06-08 14:36 ` Maxime Ripard
2022-06-08 15:14 ` Peter Robinson
2022-06-08 15:36 ` Maxime Ripard
2022-06-09 9:23 ` Maxime Ripard
2022-06-09 11:49 ` Peter Robinson
2022-06-09 13:37 ` Peter Mattern
2022-06-08 22:47 ` Stefan Wahren
2022-06-09 11:52 ` Peter Robinson
2022-06-09 21:33 ` Stefan Wahren [this message]
2022-06-10 20:06 ` Stefan Wahren
2022-06-10 22:02 ` Peter Robinson
2022-06-09 13:08 ` Peter Mattern
2022-06-05 23:57 Stefan Wahren
2022-06-09 12:49 Peter Mattern
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=fb2035d3-5322-7b03-e9fc-89ce1f892db6@i2se.com \
--to=stefan.wahren@i2se.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=maxime@cerno.tech \
--cc=pbrobinson@gmail.com \
--cc=pmattern@arcor.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 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.