From: Domenico Andreoli <cavokz@gmail.com>
To: Paul Gortmaker <paul.gortmaker@windriver.com>
Cc: Paulo Marques <pmarques@grupopie.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
Sam Ravnborg <sam@ravnborg.org>, Michal Marek <mmarek@suse.cz>,
Arnaud Lacombe <lacombar@gmail.com>,
Nick Bowler <nbowler@elliptictech.com>,
Jan Beulich <jbeulich@novell.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: "Inconsistent kallsyms data" error
Date: Sun, 15 Jul 2012 23:58:53 +0200 [thread overview]
Message-ID: <20120715215853.GA11632@glitch> (raw)
In-Reply-To: <CAP=VYLqCNDo+3tz2RibPwwCNUNNYf1WA+wmeeUor8AmJqnfz1A@mail.gmail.com>
On Sat, Jul 07, 2012 at 12:48:23AM -0400, Paul Gortmaker wrote:
> On Fri, Jul 6, 2012 at 7:17 AM, Paulo Marques <pmarques@grupopie.com> wrote:
>
> [...]
>
> >
> > There was a recent thread from David Brown on the arm linux mailing list
> > ("ARM: two possible fixes for the KALLSYMS build problem"). He tracked
> > down the problem to having empty per_cpu sections on a non-smp build.
>
> Actually rmk diagnosed it as the empty per_cpu sections. See it here:
>
> http://marc.info/?l=linux-next&m=133267456809502&w=2
I also saw this problem in the past (a couple of months ago), mostly on a
specific machine. But I _am_ playing with the linker scripts so I expected
to be the cause in an unknown way.
Unfortunately I've never understood the cause (I also switched from reiserfs
to ext4 in the panic, moving the source tree around seemed to help). The
behaviour seemed inconsistent and could not reliably reproduce it even if
there were very few "moving targets". Very clueless.
Don't know why I'm not encountering it any more but a more useful diagnostic
would be surely useful. The second pass thing didn't help me either. I
also tried to implement an addition pass but the thing was not making any
sense to me anyway.
So yes, in case of error please leave some trace somewhere so that to poor
user has some chance to work his/her good luck out of the troubles.
cheers,
Domenico
next prev parent reply other threads:[~2012-07-15 21:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-05 21:18 "Inconsistent kallsyms data" error Linus Torvalds
2012-07-06 7:25 ` Jan Beulich
2012-07-06 11:17 ` Paulo Marques
2012-07-07 4:48 ` Paul Gortmaker
2012-07-15 21:58 ` Domenico Andreoli [this message]
2012-07-07 21:40 ` Michal Marek
2012-08-10 0:02 ` Jan Engelhardt
2012-08-10 9:59 ` Michal Marek
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=20120715215853.GA11632@glitch \
--to=cavokz@gmail.com \
--cc=jbeulich@novell.com \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=nbowler@elliptictech.com \
--cc=paul.gortmaker@windriver.com \
--cc=pmarques@grupopie.com \
--cc=sam@ravnborg.org \
--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