From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Arnd Bergmann <arnd@arndb.de>,
Russell King <rmk+kernel@armlinux.org.uk>,
Masahiro Yamada <masahiroy@kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Miguel Ojeda <ojeda@kernel.org>
Subject: Re: Linux 6.1-rc3
Date: Thu, 2 Feb 2023 09:33:54 +0100 [thread overview]
Message-ID: <CAMuHMdXfodc5UwKqe8U=xd3AxG2RFSU7st90uCLx3HwzRV6w8Q@mail.gmail.com> (raw)
In-Reply-To: <CAMuHMdVGDmRQvb2FSC5SxjxyuUhZCBkVN5Z2QU6FN2P49c-3aQ@mail.gmail.com>
On Thu, Feb 2, 2023 at 8:40 AM Geert Uytterhoeven <geert@linux-m68k.org> wrote:
> On Tue, Nov 1, 2022 at 8:11 PM Guenter Roeck <linux@roeck-us.net> wrote:
> > On Tue, Nov 01, 2022 at 10:29:01AM -0700, Linus Torvalds wrote:
> > > [ Adding Arnd and Masahiro in case they remember what the secret sauce
> > > for finding those cases was ]
> > >
> > > On Tue, Nov 1, 2022 at 10:00 AM Guenter Roeck <linux@roeck-us.net> wrote:
> > > >
> > > > There is one spurious build error. It does not happen all the time,
> > > > and even on the same SHA it is not easy to reproduce. If I see it,
> > > > I may see it on one server reliably but not at all on another with
> > > > almost the same hardware configuration.
> > > >
> > > > Building powerpc:allnoconfig ... failed
> > > > --------------
> > > > Error log:
> > > > Inconsistent kallsyms data
> > > > Try make KALLSYMS_EXTRA_PASS=1 as a workaround
> > >
> > > The random "Inconsistent kallsyms data" issue is something that we've
> > > had for over a decade.
> >
> > I know. Difference this time around, at least for me, is that the
> > table is oscillating and never converges. Another difference is that
>
> Yeah, I remember the number of retries was increased to "help"
> with this...
>
> > it looks like the problem was introduced by a change in how the table
> > is created, not by a change in the code or the compiler/linker.
> > I do have a patch that lets me run as many extra passes as I want,
> > but that doesn't help if the table never converges.
>
> Kisskb has been reporting this on-and-off for sun3_defconfig/m68k-gcc11
> since Jan 25th:
> http://kisskb.ellerman.id.au/kisskb/target/192141/
And this is not yet detected by my scripts, hence not reported in my list
of build regressions for v6.2-rc6. Fixed.
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
prev parent reply other threads:[~2023-02-02 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-30 22:35 Linux 6.1-rc3 Linus Torvalds
2022-11-01 8:02 ` Build regressions/improvements in v6.1-rc3 Geert Uytterhoeven
2022-11-01 8:08 ` Geert Uytterhoeven
2022-11-01 17:00 ` Linux 6.1-rc3 Guenter Roeck
2022-11-01 17:29 ` Linus Torvalds
2022-11-01 17:37 ` Linus Torvalds
2022-11-01 17:57 ` Arnd Bergmann
2022-11-01 18:19 ` Miguel Ojeda
2022-11-01 18:26 ` Guenter Roeck
2022-11-01 18:37 ` Guenter Roeck
2023-02-02 7:40 ` Geert Uytterhoeven
2023-02-02 8:33 ` Geert Uytterhoeven [this message]
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='CAMuHMdXfodc5UwKqe8U=xd3AxG2RFSU7st90uCLx3HwzRV6w8Q@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=arnd@arndb.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=masahiroy@kernel.org \
--cc=ojeda@kernel.org \
--cc=rmk+kernel@armlinux.org.uk \
--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 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).