[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221101183717.GB1328619@roeck-us.net>
Date: Tue, 1 Nov 2022 11:37:17 -0700
From: Guenter Roeck <linux@...ck-us.net>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Arnd Bergmann <arnd@...db.de>,
Russell King <rmk+kernel@...linux.org.uk>,
Masahiro Yamada <masahiroy@...nel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Miguel Ojeda <ojeda@...nel.org>
Subject: Re: Linux 6.1-rc3
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@...ck-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
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.
If anyone has an idea how I can track this down, I'll be happy
to give it a try.
Thanks,
Guenter
Powered by blists - more mailing lists