From: Boris Brezillon <boris.brezillon@collabora.com>
To: Dominik Brodowski <linux@dominikbrodowski.net>
Cc: narmstrong@baylibre.com, laurent.pinchart@ideasonboard.com,
jernej.skrabec@siol.net, jonas@kwiboo.se,
linux-kernel@vger.kernel.org
Subject: Re: drm/bridge and lockup on boot
Date: Mon, 17 Feb 2020 22:08:52 +0100 [thread overview]
Message-ID: <20200217220852.55cbac43@collabora.com> (raw)
In-Reply-To: <20200217200942.GA2433@light.dominikbrodowski.net>
On Mon, 17 Feb 2020 21:09:42 +0100
Dominik Brodowski <linux@dominikbrodowski.net> wrote:
> On my old Dell XPS 13 laptop with
>
> 00:00.0 Host bridge: Intel Corporation Broadwell-U Host Bridge -OPI (rev 09)
> 00:02.0 VGA compatible controller: Intel Corporation HD Graphics 5500 (rev 09) (prog-if 00 [VGA controller])
>
> booting 5.6-rc1 and -rc2 fails after the dmesg line
>
> fb0: switching to inteldrmfb from simple
>
> while the next lines should be something like (v5.5):
>
> Console: switching to colour dummy device 80x25
> i915 0000:00:02.0: vgaarb: deactivate vga console
> [drm] ACPI BIOS requests an excessive sleep of 25000 ms, using 1500 ms instead
> [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
> [drm] Driver supports precise vblank timestamp query.
> i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
>
> A git bisect lead to
>
> commit b86d895524ab ("drm/bridge: Add an ->atomic_check() hook")
This commit has been reverted: you should ignore any failures between
b86d895524ab ("drm/bridge: Add an ->atomic_check() hook") and
099126352303 ("Revert "drm/bridge: Add a drm_bridge_state object").
>
> as the first bad commit, as unlikely as that sounds. f7619a58ef92 is good,
> as is bf046007641a, and 3cacb2086e41 is definitely broken on my setup.
> Any ideas?
>
> Oh, and this might be the same issue as reported here:
>
> https://lore.kernel.org/lkml/99fb887f-4a1b-6c15-64a6-9d089773cdd4@4net.rs/
>
> though I do not see such a warning, but nothing new once the line "fb0: switching
> to inteldrmfb from simple" is printed.
>
> Thanks,
> Dominik
next prev parent reply other threads:[~2020-02-17 21:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 20:09 drm/bridge and lockup on boot Dominik Brodowski
2020-02-17 21:08 ` Boris Brezillon [this message]
2020-02-18 11:48 ` lockup on boot -- drm/i915/display: Force the state compute phase once to enable PSR Dominik Brodowski
2020-02-18 18:01 ` Souza, Jose
2020-02-18 18:58 ` Dominik Brodowski
2020-03-01 15:15 ` 5.5.6-rc1+: " Dominik Brodowski
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=20200217220852.55cbac43@collabora.com \
--to=boris.brezillon@collabora.com \
--cc=jernej.skrabec@siol.net \
--cc=jonas@kwiboo.se \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@dominikbrodowski.net \
--cc=narmstrong@baylibre.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;
as well as URLs for NNTP newsgroup(s).