All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor@kernel.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	stable@vger.kernel.org, patches@lists.linux.dev,
	linux-kernel@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, srw@sladewatkins.net, rwarsow@gmx.de
Subject: Re: [PATCH 6.1 000/610] 6.1.28-rc2 review
Date: Tue, 9 May 2023 22:30:44 +0100	[thread overview]
Message-ID: <20230509-tacking-polo-d841ebfffcd0@spud> (raw)
In-Reply-To: <ce667220-5803-4b6a-a2d2-f538289af584@roeck-us.net>

[-- Attachment #1: Type: text/plain, Size: 2343 bytes --]

On Tue, May 09, 2023 at 02:18:35PM -0700, Guenter Roeck wrote:
> On Tue, May 09, 2023 at 09:41:42PM +0100, Conor Dooley wrote:
> > On Tue, May 09, 2023 at 12:57:58PM -0700, Guenter Roeck wrote:
> > > On Tue, May 09, 2023 at 05:26:31AM +0200, Greg Kroah-Hartman wrote:
> > > > This is the start of the stable review cycle for the 6.1.28 release.
> > > > There are 610 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 Thu, 11 May 2023 03:05:05 +0000.
> > > > Anything received after that time might be too late.
> > > > 
> > > 
> > > Build results:
> > > 	total: 155 pass: 155 fail: 0
> > > Qemu test results:
> > > 	total: 519 pass: 519 fail: 0
> > > 
> > > New persistent runtime warning when booting riscv32/64 images:
> > 
> > You sure this is new? I seem to be able to reproduce for QEMU (which I
> 
> New for my tests, yes.
> 
> > don't usually test) in several versions of 6.1. Don't see it in (my)
> > hardware though, as the particular platform doesn't end up calling the
> > offending function. Out of curiosity, what's your QEMU invocation?
> 
> Example boot from initrd:
> 
> qemu-system-riscv64 -M virt -m 512M \
>      -no-reboot -kernel arch/riscv/boot/Image \
>      -initrd rootfs.cpio \
>      -device e1000,netdev=net0 \
>      -netdev user,id=net0 -bios default \
>      -append "panic=-1 rdinit=/sbin/init console=ttyS0,115200 earlycon=uart8250,mmio,0x10000000,115200" \
>      -nographic -monitor none

Cool, was mainly interested in seeing if you were explicitly enabling
any ISA extensions. NGL, I expected to see some.

> qemu version is 8.0, but I don't think that makes a difference.

I'm on 7.2.50 (v7.2.0-2653-g7080c3ab79-dirty) as it is where I ended
during my last bisection of QEMU. But aye, makes no odds - I see it on a
more recent 8.0.50 version too.

> What does your command line look like ?

In this particular instance:
	qemu-system-riscv64 -M virt \
		-m 2G -smp 5 \
		-nographic \
		-kernel $(vmlinux_bin) \
		-initrd $(initramfs)

> > Anyways, looks like a partial backport is the cause. How's it look with:

> This fixes the problem for me.

Cool, shall send it as a real patch. Thanks.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]

  reply	other threads:[~2023-05-09 21:30 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-09  3:26 [PATCH 6.1 000/610] 6.1.28-rc2 review Greg Kroah-Hartman
2023-05-09 10:06 ` Bagas Sanjaya
2023-05-09 10:17 ` ogasawara takeshi
2023-05-09 13:35 ` Jon Hunter
2023-05-09 15:05 ` Markus Reichelt
2023-05-09 17:04 ` Allen Pais
2023-05-09 17:18 ` Florian Fainelli
2023-05-09 17:50 ` Naresh Kamboju
2023-05-09 19:57 ` Guenter Roeck
2023-05-09 20:41   ` Conor Dooley
2023-05-09 21:18     ` Guenter Roeck
2023-05-09 21:30       ` Conor Dooley [this message]
2023-05-10  8:47 ` Sudip Mukherjee (Codethink)
2023-05-10 11:48 ` Pavel Machek
2023-05-10 13:18   ` Roger Pau Monné

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=20230509-tacking-polo-d841ebfffcd0@spud \
    --to=conor@kernel.org \
    --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=patches@lists.linux.dev \
    --cc=pavel@denx.de \
    --cc=rwarsow@gmx.de \
    --cc=shuah@kernel.org \
    --cc=srw@sladewatkins.net \
    --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.