Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Robert Nelson <robertcnelson@gmail.com>
Cc: <linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <devicetree@vger.kernel.org>,
	Rob Herring <robh@kernel.org>,
	"Krzysztof Kozlowski" <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	Andrew Davis <afd@ti.com>, Roger Quadros <rogerq@kernel.org>,
	Siddharth Vadapalli <s-vadapalli@ti.com>,
	Judith Mendez <jm@ti.com>, Andrei Aldea <a-aldea@ti.com>,
	Dhruva Gole <d-gole@ti.com>,
	Jason Kridner <jkridner@beagleboard.org>,
	Deepak Khatri <lorforlinux@beagleboard.org>,
	Ayush Singh <ayush@beagleboard.org>, <kamlesh@ti.com>,
	<praneeth@ti.com>
Subject: Re: [PATCH v2 2/2] arm64: dts: ti: Add k3-am62-pocketbeagle2
Date: Thu, 10 Apr 2025 17:35:45 -0500	[thread overview]
Message-ID: <20250410223545.m747qkoqpwsz57ae@septum> (raw)
In-Reply-To: <CAOCHtYh7LWhTBOSsua9_=wxSTNt9HmvUaAFCiVS6a8G6dV4AoA@mail.gmail.com>

On 12:15-20250410, Robert Nelson wrote:
> On Thu, Apr 10, 2025 at 7:08 AM Nishanth Menon <nm@ti.com> wrote:
> >
> > On 10:12-20250409, Robert Nelson wrote:
> > [..]
> >
> > > > Any idea why we are crashing?
> > > > https://gist.github.com/RobertCNelson/c68c96a8a1dc6e4d39d8c48fc13ca1c1#file-gistfile1-txt-L311
> > > >
> > > > I don't see the same crash in beagleplay:
> > > > https://gist.github.com/nmenon/5709a8714d3ab31cac5c00b515d04752
> > >
> > > On 6.14.x i have a little more, info...
> > >
> > > I've got all the CRYPTO stuff enabled, pretty sure that comes from
> > > CONFIG_CRYPTO_MANAGER
> > >
> > > CONFIG_CRYPTO_MANAGER=y
> > > CONFIG_CRYPTO_MANAGER2=y
> > > CONFIG_CRYPTO_USER=y
> > > # CONFIG_CRYPTO_MANAGER_DISABLE_TESTS is not set
> > > # CONFIG_CRYPTO_MANAGER_EXTRA_TESTS is not set
> > >
> > > https://openbeagle.org/RobertCNelson/arm64-multiplatform/-/blob/v6.15.x-arm64-k3/patches/defconfig?ref_type=heads#L9578
> >
> > OK this looks like to be a independent pre-existing bug then and needs
> > to be investigated, but it is probably independent of this patch itself.
> >
> > Could you share a clean defconfig bootlog? I have no existing scheme to
> > test this on my end. In the logs, please also print
> > /sys/kernel/debug/devices_deferred to ensure we have nothing sticking
> > out in our defconfig?
> 
> Okay stable v6.15-rc1 with arm64 defconfig..
> 
> https://gist.github.com/RobertCNelson/666638abac8eee4ed573997996362450
> 
> root@am6232-pb2-87:~# ls -lha /sys/kernel/debug/device_component/


umm..  It was cat /sys/kernel/debug/devices_deferred

> total 0
> drwxr-xr-x  2 root root 0 Dec 31  1969 .
> drwx------ 44 root root 0 Dec 31  1969 ..

Thank you Robert. I will assume there are no deferred devices or
additional defconfig components to enable.

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D


  reply	other threads:[~2025-04-10 22:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-08 23:18 [PATCH v2 1/2] dt-bindings: arm: ti: Add PocketBeagle2 Robert Nelson
2025-04-08 23:18 ` [PATCH v2 2/2] arm64: dts: ti: Add k3-am62-pocketbeagle2 Robert Nelson
2025-04-08 23:19   ` Robert Nelson
2025-04-09 13:09     ` Nishanth Menon
2025-04-09 15:12       ` Robert Nelson
2025-04-10 12:08         ` Nishanth Menon
2025-04-10 17:15           ` Robert Nelson
2025-04-10 22:35             ` Nishanth Menon [this message]
2025-04-09  6:03   ` Dhruva Gole
2025-04-10 16:15   ` Nishanth Menon
2025-04-10 17:26     ` Jason Kridner
2025-04-10 22:53       ` Nishanth Menon
2025-04-09  4:55 ` [PATCH v2 1/2] dt-bindings: arm: ti: Add PocketBeagle2 Dhruva Gole

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=20250410223545.m747qkoqpwsz57ae@septum \
    --to=nm@ti.com \
    --cc=a-aldea@ti.com \
    --cc=afd@ti.com \
    --cc=ayush@beagleboard.org \
    --cc=conor+dt@kernel.org \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=jkridner@beagleboard.org \
    --cc=jm@ti.com \
    --cc=kamlesh@ti.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorforlinux@beagleboard.org \
    --cc=praneeth@ti.com \
    --cc=robertcnelson@gmail.com \
    --cc=robh@kernel.org \
    --cc=rogerq@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=vigneshr@ti.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