From: Tony Lindgren <tony@atomide.com>
To: David Shah <dave@ds0.me>
Cc: Discussions about the Letux Kernel <letux-kernel@openphoenux.org>,
"; kernel@pyra-handheld.com; Linux-OMAP"
<linux-omap@vger.kernel.org>
Subject: Re: Lockup inside omap4_prminst_read_inst_reg on OMAP5 uEVM
Date: Sun, 26 Jul 2020 23:47:16 -0700 [thread overview]
Message-ID: <20200727064716.GA2811@atomide.com> (raw)
In-Reply-To: <115bcd43a5d01f2df26b58ffcd7e1a9f9e551c83.camel@ds0.me>
* David Shah <dave@ds0.me> [200726 17:59]:
> Hi all,
>
> I am looking into random lockups - significantly rarer than once a day
> in typical usage, various patterns like lots of bursty network traffic
> increase frequency - that affect both the uEVM and the Pyra (also
> OMAP5432 based) on newer kernels (currently testing with 5.6 but I have
> seen lockups with 5.7 too).
Just wondering.. Is this with USB Ethernet or with WLAN?
Regards,
Tony
next prev parent reply other threads:[~2020-07-27 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-26 17:59 Lockup inside omap4_prminst_read_inst_reg on OMAP5 uEVM David Shah
2020-07-27 6:47 ` Tony Lindgren [this message]
2020-08-01 20:57 ` David Shah
2020-08-16 17:13 ` [Letux-kernel] " David Shah
2020-08-17 6:38 ` Tony Lindgren
2020-08-17 8:18 ` David Shah
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=20200727064716.GA2811@atomide.com \
--to=tony@atomide.com \
--cc=dave@ds0.me \
--cc=letux-kernel@openphoenux.org \
--cc=linux-omap@vger.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;
as well as URLs for NNTP newsgroup(s).