From: Vignesh Raman <vignesh.raman@collabora.com>
To: dmukhin@ford.com, mingo@kernel.org, mingo@redhat.com,
andriy.shevchenko@linux.intel.com, x86@kernel.org
Cc: daniels <daniels@collabora.com>,
Daniel Stone <daniel@fooishbar.org>,
robdclark <robdclark@gmail.com>,
lumag@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: x86: Boot failure on select chromebooks with v6.15-rc5
Date: Fri, 9 May 2025 11:26:01 +0530 [thread overview]
Message-ID: <a8638f85-1cc2-4f51-97ba-7106a4662885@collabora.com> (raw)
Hi,
With v6.15-rc5, the below chromebooks were not booting with the
following message. These tests were run in drm-ci.
Starting kernel ...
[ 1.843801] ? __pfx_kernel_init+0x10/0x10
[ 1.909838] ? __pfx_kernel_init+0x10/0x10
https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1420485
Failing jobs:
amdgpu:stoney (AMD Stoney Ridge chipset):
https://gitlab.freedesktop.org/vigneshraman/linux/-/jobs/76000926
i915:amly (64 bit Intel Whiskey Lake):
https://gitlab.freedesktop.org/vigneshraman/linux/-/jobs/76000929
i915:whl (64 bit Intel Amber Lake):
https://gitlab.freedesktop.org/vigneshraman/linux/-/jobs/76000931
These tests were passing till v6.14-rc7, and the issue was seen starting
in v6.15-rc1. This issue is seen only with these 3 boards and does not
affect other chromebooks (the pipeline log shows the other i915 driver
tests).
On bisecting the commits, the commit which introduced this issue is,
3181424aeac2f6596534bf43021a10eae294a9b0 x86/early_printk: Add support
for MMIO-based UARTs
After reverting the below commits in v6.15-rc5, the board boots and
tests are executed:
3181424aeac2 x86/early_printk: Add support for MMIO-based UARTs
996457176bb7 x86/early_printk: Use 'mmio32' for consistency, fix
comments (this fixes 3181424aeac2)
pipeline after reverting the commits,
https://gitlab.freedesktop.org/vigneshraman/linux/-/pipelines/1420493
Please could you look into this issue. Thank you.
Regards,
Vignesh
next reply other threads:[~2025-05-09 5:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 5:56 Vignesh Raman [this message]
2025-05-09 6:06 ` Ingo Molnar
2025-05-09 6:21 ` Vignesh Raman
2025-05-09 6:37 ` Ingo Molnar
2025-05-09 7:37 ` Vignesh Raman
2025-05-12 17:30 ` dmkhn
2025-05-14 9:57 ` Vignesh Raman
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=a8638f85-1cc2-4f51-97ba-7106a4662885@collabora.com \
--to=vignesh.raman@collabora.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=daniel@fooishbar.org \
--cc=daniels@collabora.com \
--cc=dmukhin@ford.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lumag@kernel.org \
--cc=mingo@kernel.org \
--cc=mingo@redhat.com \
--cc=robdclark@gmail.com \
--cc=x86@kernel.org \
/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®