[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20230428043517.h5x4jkx2k26jyqoi@treble>
Date: Thu, 27 Apr 2023 21:35:17 -0700
From: Josh Poimboeuf <jpoimboe@...nel.org>
To: "Paul E. McKenney" <paulmck@...nel.org>
Cc: Borislav Petkov <bp@...en8.de>, peterz@...radead.org,
linux-kernel@...r.kernel.org
Subject: Re: An objtool warning from mainline
On Thu, Apr 27, 2023 at 09:55:41AM -0700, Paul E. McKenney wrote:
> On Thu, Apr 27, 2023 at 11:14:21AM +0200, Borislav Petkov wrote:
> > On Wed, Apr 26, 2023 at 04:50:49PM -0700, Paul E. McKenney wrote:
> > > vmlinux.o: warning: objtool: exc_nmi+0x2b3: call to __const_udelay() leaves .noinstr.text section
> >
> > What does
> >
> > ./scripts/faddr2line vmlinux.o exc_nmi+0x2b3
> >
> > say?
>
> $ ./scripts/faddr2line vmlinux.o exc_nmi+0x2b3
> exc_nmi+0x2b3/0x3c0:
> exc_nmi at ??:?
>
> Which might mean something to you, but does not look all that helpful
> to me. :-/
This means DWARF is missing. Can you enable one of the
CONFIG_DEBUG_INFO_DWARF* options and try that again?
And yes, we should improve the error message for faddr2line.
--
Josh
Powered by blists - more mailing lists