[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <24493b95-d994-4a42-a825-38ce2bf47c92@spud>
Date: Fri, 31 Mar 2023 19:55:42 +0100
From: Conor Dooley <conor@...nel.org>
To: Heiko Stübner <heiko@...ech.de>
Cc: guoren@...nel.org, arnd@...db.de, palmer@...osinc.com,
tglx@...utronix.de, peterz@...radead.org, luto@...nel.org,
conor.dooley@...rochip.com, jszhang@...nel.org,
lazyparser@...il.com, falcon@...ylab.org, chenhuacai@...nel.org,
apatel@...tanamicro.com, atishp@...shpatra.org,
mark.rutland@....com, ben@...adent.org.uk, bjorn@...nel.org,
palmer@...belt.com, linux-arch@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-riscv@...ts.infradead.org,
Guo Ren <guoren@...ux.alibaba.com>,
Björn Töpel <bjorn@...osinc.com>,
Yipeng Zou <zouyipeng@...wei.com>
Subject: Re: [PATCH -next V17 4/7] riscv: entry: Convert to generic entry
On Fri, Mar 31, 2023 at 08:46:44PM +0200, Heiko Stübner wrote:
> Hi,
>
> Am Freitag, 31. März 2023, 20:41:35 CEST schrieb Conor Dooley:
> > On Fri, Mar 31, 2023 at 07:34:38PM +0100, Conor Dooley wrote:
> > > On Tue, Feb 21, 2023 at 10:30:18PM -0500, guoren@...nel.org wrote:
> > > > From: Guo Ren <guoren@...ux.alibaba.com>
> > > >
> > > > This patch converts riscv to use the generic entry infrastructure from
> > > > kernel/entry/*. The generic entry makes maintainers' work easier and
> > > > codes more elegant. Here are the changes:
> > > >
> > > > - More clear entry.S with handle_exception and ret_from_exception
> > > > - Get rid of complex custom signal implementation
> > > > - Move syscall procedure from assembly to C, which is much more
> > > > readable.
> > > > - Connect ret_from_fork & ret_from_kernel_thread to generic entry.
> > > > - Wrap with irqentry_enter/exit and syscall_enter/exit_from_user_mode
> > > > - Use the standard preemption code instead of custom
> > >
> > > This has unfortunately broken booting my usual NFS rootfs on both my D1
> > > and Icicle. It's one of the Fedora images from David, I think this one:
> > > http://fedora.riscv.rocks/kojifiles/work/tasks/3933/1313933/
> > >
> > > It gets pretty far into things, it's once systemd is operational that
> > > things go pear shaped:
> >
> > Shoulda said, can share the full logs if required of course, but they're
> > quite verbose cos systemd etc.
>
> I was just investigating the same thing just now. So that saves me some
> tracking down the culprit :-) .
>
> My main qemu is living as a "board" in my boardfarm (also doing nfsroot)
> as well as my d1 nezha with nfsroot was affected.
>
> Though my board is stuck in some failure loop with both the journal- as
> well as the timesyncd service failing again and again. And I haven't
> figured out how to get logs without a working login console yet.
I'll attach the full output from a run I guess. journald fails ad
infinitum for me too after I cut this log off.
Cheers,
Conor.
View attachment "nfsroot.fail" of type "text/plain" (34195 bytes)
Download attachment "signature.asc" of type "application/pgp-signature" (229 bytes)
Powered by blists - more mailing lists