All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: Vignesh Raman <vignesh.raman@collabora.com>
Cc: dmukhin@ford.com, mingo@redhat.com,
	andriy.shevchenko@linux.intel.com, x86@kernel.org,
	daniels <daniels@collabora.com>,
	Daniel Stone <daniel@fooishbar.org>,
	robdclark <robdclark@gmail.com>,
	lumag@kernel.org, linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: x86: Boot failure on select chromebooks with v6.15-rc5
Date: Fri, 9 May 2025 08:37:41 +0200	[thread overview]
Message-ID: <aB2itc2-5h3LEJi6@gmail.com> (raw)
In-Reply-To: <d966d626-458b-4a29-abe1-b645317e15d2@collabora.com>


* Vignesh Raman <vignesh.raman@collabora.com> wrote:

> > What boot cmdline does your kernel have? The MMIO-UART patches should
> > only have an effect if the feature is specifically enabled via a boot
> > option:
> > 
> > +               if (!strncmp(buf, "mmio32", 6)) {
> > +			buf += 6;
> > +                       early_mmio_serial_init(buf);
> > +                       early_console_register(&early_serial_console, keep);
> > +                       buf += 4;
> > +               }
> > 
> 
> amdgpu:stoney:
> earlyprintk=uart8250,mmio32,0xfedc6000,115200n8  console=ttyS0,115200n8
> root=/dev/nfs rw nfsroot=192.168.201.1:/var/lib/lava/dispatcher/tmp/18598802/extract-nfsrootfs-wgn1xjer,tcp,hard,v3
> init=/init rootwait usbcore.quirks=0bda:8153:k ip=dhcp
> tftpserverip=192.168.201.1
> 
> i915:amly:
> earlyprintk=uart8250,mmio32,0xde000000,115200n8  console=ttyS0,115200n8
> root=/dev/nfs rw nfsroot=192.168.201.1:/var/lib/lava/dispatcher/tmp/18598804/extract-nfsrootfs-5rlm_b6z,tcp,hard,v3
> init=/init rootwait usbcore.quirks=0bda:8153:k ip=dhcp
> tftpserverip=192.168.201.1
> 
> i915:whl:
> earlyprintk=uart8250,mmio32,0xde000000,115200n8  console=ttyS0,115200n8
> root=/dev/nfs rw nfsroot=192.168.201.1:/var/lib/lava/dispatcher/tmp/18598833/extract-nfsrootfs-3w0w5_mi,tcp,hard,v3
> init=/init rootwait usbcore.quirks=0bda:8153:k ip=dhcp
> tftpserverip=192.168.201.1

Well, if you remove the earlyprintk option then it will boot fine, 
right?

The earlyprintk=mmio32 in v6.15 is a new debugging feature that was 
tested on a single board by Denis Mukhin AFAIK, and it may or may not 
work on your particular UART - even assuming that all the parameters 
are correct.

Thanks,

	Ingo

  reply	other threads:[~2025-05-09  6:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-09  5:56 x86: Boot failure on select chromebooks with v6.15-rc5 Vignesh Raman
2025-05-09  6:06 ` Ingo Molnar
2025-05-09  6:21   ` Vignesh Raman
2025-05-09  6:37     ` Ingo Molnar [this message]
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=aB2itc2-5h3LEJi6@gmail.com \
    --to=mingo@kernel.org \
    --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@redhat.com \
    --cc=robdclark@gmail.com \
    --cc=vignesh.raman@collabora.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 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.