LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Finn Thain <fthain@linux-m68k.org>
To: Mikael Pettersson <mikpelinux@gmail.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>,
	linux-m68k@lists.linux-m68k.org, stable@vger.kernel.org,
	Peter Xu <peterx@redhat.com>
Subject: Re: [BISECTED][REGRESSION] 5.10.56 longterm kernel breakage on m68k/aranym
Date: Mon, 9 Aug 2021 11:59:11 +1000 (AEST)	[thread overview]
Message-ID: <380dd57-4b60-ac9c-508c-826d8ec1b0aa@linux-m68k.org> (raw)
In-Reply-To: <CAM43=SNV4016i2ByssN9tvXDN6ZyQiYM218_NkrebyPA=p6Rcg@mail.gmail.com>

On Sun, 8 Aug 2021, Mikael Pettersson wrote:

> On Sun, Aug 8, 2021 at 1:20 AM Finn Thain <fthain@linux-m68k.org> wrote:
> >
> > On Sat, 7 Aug 2021, Mikael Pettersson wrote:
> >
> > > I updated the 5.10 longterm kernel on one of my m68k/aranym VMs from
> > > 5.10.47 to 5.10.56, and the new kernel failed to boot:
> > >
> > > ARAnyM 1.1.0
> > > Using config file: 'aranym1.headless.config'
> > > Could not open joystick 0
> > > ARAnyM RTC Timer: /dev/rtc: Permission denied
> > > ARAnyM LILO: Error loading ramdisk 'root.bin'
> > > Blitter tried to read byte from register ff8a00 at 0077ee
> > >
> > > At this point it kept running, but produced no output to the console,
> > > and would never get to the point of starting user-space. Attaching gdb
> > > to aranym showed nothing interesting, i.e. it seemed to be executing
> > > normally.
> > >
> > > A git bisect identified the following commit between 5.10.52 and
> > > 5.10.53 as the culprit:
> > > # first bad commit: [9e1cf2d1ed37c934c9935f2c0b2f8b15d9355654]
> > > mm/userfaultfd: fix uffd-wp special cases for fork()
> > >
> >
> > That commit appeared in mainline between v5.13 and v5.14-rc1. Is mainline
> > also affected? e.g. v5.14-rc4.
> 
> 5.14-rc4 boots fine. I suspect the commit has some dependency that
> hasn't been backported to 5.10 stable.
> 

On mainline, 9e1cf2d1ed3 is known as commit 8f34f1eac382 ("mm/userfaultfd: 
fix uffd-wp special cases for fork()").

There are differences between the two commits that may be relevant. I 
don't know.

If you checkout 8f34f1eac382 and if that works, it would indicate either 
missing dependencies in -stable, or those differences are important.

OTOH, if 8f34f1eac382 fails in the same way as linux-5.10.y, it would 
indicate that -stable is missing a fix that's present in v5.14-rc4.

  reply	other threads:[~2021-08-09  1:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-07 14:28 Mikael Pettersson
2021-08-07 23:19 ` Finn Thain
2021-08-08 10:44   ` Mikael Pettersson
2021-08-09  1:59     ` Finn Thain [this message]
2021-08-09 10:08       ` Mikael Pettersson
2021-08-09 13:31       ` Mikael Pettersson
2021-08-09 13:40         ` Geert Uytterhoeven
2021-08-10 15:59           ` Mike Rapoport
2021-08-11  9:24             ` Mikael Pettersson

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=380dd57-4b60-ac9c-508c-826d8ec1b0aa@linux-m68k.org \
    --to=fthain@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=mikpelinux@gmail.com \
    --cc=peterx@redhat.com \
    --cc=stable@vger.kernel.org \
    --subject='Re: [BISECTED][REGRESSION] 5.10.56 longterm kernel breakage on m68k/aranym' \
    /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

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).