From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: linux-arm-kernel@lists.infradead.org, Nishanth Menon <nm@ti.com>,
"Bajjuri, Praneeth" <praneeth@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: Random stack corruption on v5.13 with dra76
Date: Fri, 21 May 2021 08:36:38 +0300 [thread overview]
Message-ID: <YKdG5rsNCRYVLDpj@atomide.com> (raw)
In-Reply-To: <0f48c7e5-6acd-1143-35ef-3dea2255bec6@ideasonboard.com>
* Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> [210520 08:27]:
> Hi,
>
> I've noticed that the v5.13 rcs crash randomly (but quite often) on dra76 evm
> (I haven't tested other boards). Anyone else seen this problem?
I have not seen this so far and beagle-x15 is behaving for me.
Does it always happen on boot?
Regards,
Tony
WARNING: multiple messages have this Message-ID (diff)
From: Tony Lindgren <tony@atomide.com>
To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>
Cc: linux-arm-kernel@lists.infradead.org, Nishanth Menon <nm@ti.com>,
"Bajjuri, Praneeth" <praneeth@ti.com>,
linux-omap@vger.kernel.org
Subject: Re: Random stack corruption on v5.13 with dra76
Date: Fri, 21 May 2021 08:36:38 +0300 [thread overview]
Message-ID: <YKdG5rsNCRYVLDpj@atomide.com> (raw)
In-Reply-To: <0f48c7e5-6acd-1143-35ef-3dea2255bec6@ideasonboard.com>
* Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> [210520 08:27]:
> Hi,
>
> I've noticed that the v5.13 rcs crash randomly (but quite often) on dra76 evm
> (I haven't tested other boards). Anyone else seen this problem?
I have not seen this so far and beagle-x15 is behaving for me.
Does it always happen on boot?
Regards,
Tony
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2021-05-21 5:36 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <0f48c7e5-6acd-1143-35ef-3dea2255bec6@ideasonboard.com>
2021-05-21 5:36 ` Tony Lindgren [this message]
2021-05-21 5:36 ` Random stack corruption on v5.13 with dra76 Tony Lindgren
2021-05-21 7:04 ` Tomi Valkeinen
2021-05-21 7:04 ` Tomi Valkeinen
2021-05-21 7:39 ` Tony Lindgren
2021-05-21 7:39 ` Tony Lindgren
2021-05-21 8:45 ` Tomi Valkeinen
2021-05-21 8:45 ` Tomi Valkeinen
2021-05-21 9:14 ` Tony Lindgren
2021-05-21 9:14 ` Tony Lindgren
2021-05-21 10:30 ` Tomi Valkeinen
2021-05-21 10:30 ` Tomi Valkeinen
2021-05-21 12:57 ` Tomi Valkeinen
2021-05-21 12:57 ` Tomi Valkeinen
2021-05-21 13:06 ` Tony Lindgren
2021-05-21 13:06 ` Tony Lindgren
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=YKdG5rsNCRYVLDpj@atomide.com \
--to=tony@atomide.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=nm@ti.com \
--cc=praneeth@ti.com \
--cc=tomi.valkeinen@ideasonboard.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.