From: Mark Brown <broonie@kernel.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-kernel@vger.kernel.org, linux-serial@vger.kernel.org,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Jiri Slaby <jirislaby@kernel.org>
Subject: Re: [PATCH v1 1/1] serial: core: Restore sysfs fwnode information
Date: Thu, 18 Dec 2025 16:54:42 +0000 [thread overview]
Message-ID: <713aa37f-161d-4f08-9417-d7d2abdcdfd9@sirena.org.uk> (raw)
In-Reply-To: <265b9083-d744-4438-b539-9e001f2138ba@samsung.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Thu, Dec 18, 2025 at 04:29:55PM +0100, Marek Szyprowski wrote:
> On 27.11.2025 17:36, Andy Shevchenko wrote:
> > The change that restores sysfs fwnode information does it only for OF cases.
> > Update the fix to cover all possible types of fwnodes.
> This patch landed in today's linux-next as commit 24ec03cc5512 ("serial:
> core: Restore sysfs fwnode information"). In my tests I found that it
> breaks booting of most of my test boards (ARM 32 and 64 bit).
> Unfortunately I cannot provide anything useful besides the information
> that booting stops and system doesn't reach shell. There is nothing
> suspicious in the kernel logs. I suspect a memory trashing. Reverting
> $subject on top of linux-next fixes booting.
I'm also seeing this in my lab and Arm's lab, there are a few systems
that survive but it's a small minority.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-12-18 16:54 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20251218152957eucas1p196470bc80be0d8a4037edfe6e53f3d13@eucas1p1.samsung.com>
2025-11-27 16:36 ` [PATCH v1 1/1] serial: core: Restore sysfs fwnode information Andy Shevchenko
2025-11-27 19:07 ` Greg Kroah-Hartman
2025-12-18 13:50 ` Cosmin Tanislav
2025-12-18 15:29 ` Marek Szyprowski
2025-12-18 16:54 ` Mark Brown [this message]
2025-12-22 10:55 ` Marek Szyprowski
2025-12-29 3:18 ` Dmitry Baryshkov
2025-12-29 12:38 ` Andy Shevchenko
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=713aa37f-161d-4f08-9417-d7d2abdcdfd9@sirena.org.uk \
--to=broonie@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=jirislaby@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=m.szyprowski@samsung.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 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.