From: Mark Brown <broonie@kernel•org>
To: David Heidelberg <david@ixit•cz>
Cc: Linux Next Mailing List <linux-next@vger•kernel.org>,
phone-devel <phone-devel@vger•kernel.org>,
linux-arm-msm@vger•kernel.org, Pavel Pisa <pisa@cmp•felk.cvut.cz>,
Petr Hodina <petr.hodina@protonmail•com>
Subject: Re: sdm845 broken on next-20260119 & 20
Date: Wed, 21 Jan 2026 00:07:34 +0000 [thread overview]
Message-ID: <aXAYxjgZxHl49Cp2@sirena.co.uk> (raw)
In-Reply-To: <7b29f6a4-7ca3-41ef-a8ea-969c401a5c38@ixit.cz>
[-- Attachment #1: Type: text/plain, Size: 829 bytes --]
On Wed, Jan 21, 2026 at 12:03:05AM +0100, David Heidelberg wrote:
> Heya,
>
> not bisected yet, but we having problems with 20260119 & 20.
>
> No usb initalization on any device.
>
> Pixel 3
> - serial doesn't work
> - framebuffer shows early fb init and logos, freeing initrd memory
>
> OnePlus 6T
> - we get a penguins logos, but nothing else than blinking cursor
>
> For now, working version is based on next-20260109 (we have to test more
> recent tags). Version next-20260115 somehow (with some IRQ issues) worked
> too.
>
> If anyone has tips what to look for, we're grateful.
Is this possibly the issue reported in:
https://lore.kernel.org/r/7ae38e31-ef31-43ad-9106-7c76ea0e8596@sirena.org.uk
with boot hangs late in boot? That was affecting a number of other
Qualcomm platforms.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2026-01-21 0:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 23:03 sdm845 broken on next-20260119 & 20 David Heidelberg
2026-01-21 0:07 ` Mark Brown [this message]
2026-01-21 7:38 ` David Heidelberg
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=aXAYxjgZxHl49Cp2@sirena.co.uk \
--to=broonie@kernel$(echo .)org \
--cc=david@ixit$(echo .)cz \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=petr.hodina@protonmail$(echo .)com \
--cc=phone-devel@vger$(echo .)kernel.org \
--cc=pisa@cmp$(echo .)felk.cvut.cz \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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