All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stafford Horne <shorne@gmail.com>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org, stable@vger.kernel.org,
	torvalds@linux-foundation.org, akpm@linux-foundation.org,
	shuah@kernel.org, patches@kernelci.org,
	lkft-triage@lists.linaro.org, pavel@denx.de,
	jonathanh@nvidia.com, f.fainelli@gmail.com,
	sudipm.mukherjee@gmail.com, slade@sladewatkins.com
Subject: Re: [PATCH 5.15 00/10] 5.15.62-rc2 review
Date: Sun, 21 Aug 2022 15:32:55 +0000	[thread overview]
Message-ID: <YwJQJxpsRDc6dqTJ@oscomms1> (raw)
In-Reply-To: <20220821120903.GB2332676@roeck-us.net>

On Sun, Aug 21, 2022 at 05:09:03AM -0700, Guenter Roeck wrote:
> On Sat, Aug 20, 2022 at 08:23:24PM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.15.62 release.
> > There are 10 patches in this series, all will be posted as a response
> > to this one.  If anyone has any issues with these being applied, please
> > let me know.
> > 
> > Responses should be made by Mon, 22 Aug 2022 18:23:01 +0000.
> > Anything received after that time might be too late.
> > 
> 
> Build results:
> 	total: 159 pass: 159 fail: 0
> Qemu test results:
> 	total: 485 pass: 484 fail: 1
> Failed tests:
> 	openrisc:or1ksim_defconfig
> 
> The openrisc failure is a soft lockup during restart. I only recently
> enabled the soft lockup detector, so this is probably either a false
> positive or not a new problem. I'll try to track it down, but it is
> not a concern for now.
> 
> Tested-by: Guenter Roeck <linux@roeck-us.net>

Hi Guenter,

If you need help let me know, just let me know how to reproduce it.  I am
currently working on some qemu patches to convert qemu to multithread-tcg.  I
have fixed some lockup issues, but there are still some cases we get soft
lockups.

If you have any details I can see if it's a similar issue.

-Stafford

  reply	other threads:[~2022-08-21 15:33 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-20 18:23 [PATCH 5.15 00/10] 5.15.62-rc2 review Greg Kroah-Hartman
2022-08-21 12:09 ` Guenter Roeck
2022-08-21 15:32   ` Stafford Horne [this message]
2022-08-21 22:47     ` Guenter Roeck
2022-08-22 10:31 ` Naresh Kamboju

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=YwJQJxpsRDc6dqTJ@oscomms1 \
    --to=shorne@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=f.fainelli@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=jonathanh@nvidia.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@roeck-us.net \
    --cc=lkft-triage@lists.linaro.org \
    --cc=patches@kernelci.org \
    --cc=pavel@denx.de \
    --cc=shuah@kernel.org \
    --cc=slade@sladewatkins.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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.