From: "Paul E. McKenney" <paulmck@kernel.org>
To: Philip Li <philip.li@intel.com>
Cc: kernel test robot <lkp@intel.com>,
oe-kbuild-all@lists.linux.dev,
Linux Memory Management List <linux-mm@kvack.org>,
Neeraj Upadhyay <neeraj.upadhyay@kernel.org>
Subject: Re: [linux-next:master 3671/10296] ERROR: start_text address is c000000000000700, should be c000000000000200
Date: Mon, 9 Sep 2024 23:33:00 -0700 [thread overview]
Message-ID: <70e609f3-57bb-432a-8363-3ed020380bcb@paulmck-laptop> (raw)
In-Reply-To: <Zt+Vf2E42Qi5GdcC@rli9-mobl>
On Tue, Sep 10, 2024 at 08:40:31AM +0800, Philip Li wrote:
> On Mon, Sep 09, 2024 at 09:20:00AM -0700, Paul E. McKenney wrote:
> > On Mon, Sep 09, 2024 at 08:42:42AM +0800, kernel test robot wrote:
> > > tree: https://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git master
> > > head: 9aaeb87ce1e966169a57f53a02ba05b30880ffb8
> > > commit: fe91cf39db0939ac8d523b5a1c31840f7cbe205c [3671/10296] rcu/tasks: Add detailed grace-period and barrier diagnostics
> > > config: powerpc64-randconfig-003-20240908 (https://download.01.org/0day-ci/archive/20240909/202409090839.Gz712lD2-lkp@intel.com/config)
> > > compiler: powerpc64-linux-gcc (GCC) 14.1.0
> > > reproduce (this is a W=1 build): (https://download.01.org/0day-ci/archive/20240909/202409090839.Gz712lD2-lkp@intel.com/reproduce)
> > >
> > > If you fix the issue in a separate patch/commit (i.e. not just a new version of
> > > the same patch/commit), kindly add following tags
> > > | Reported-by: kernel test robot <lkp@intel.com>
> > > | Closes: https://lore.kernel.org/oe-kbuild-all/202409090839.Gz712lD2-lkp@intel.com/
> > >
> > > All errors (new ones prefixed by >>):
> > >
> > > >> ERROR: start_text address is c000000000000700, should be c000000000000200
> > > ERROR: try to enable LD_HEAD_STUB_CATCH config option
> > > ERROR: see comments in arch/powerpc/tools/head_check.sh
> >
> > I have no idea how this patch could have caused this. Help?
>
> Sorry about the false report, kindly ignore this. Seems it can't bisect to the actual
> bad commit, another similar false report is at [1] with a different bad commit.
>
> [1] https://lore.kernel.org/oe-kbuild-all/202409100106.A8692079-lkp@intel.com/
No problem, and I know that feeling!
Thanx, Paul
prev parent reply other threads:[~2024-09-10 6:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-09 0:42 kernel test robot
2024-09-09 16:20 ` Paul E. McKenney
2024-09-10 0:40 ` Philip Li
2024-09-10 6:33 ` Paul E. McKenney [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=70e609f3-57bb-432a-8363-3ed020380bcb@paulmck-laptop \
--to=paulmck@kernel.org \
--cc=linux-mm@kvack.org \
--cc=lkp@intel.com \
--cc=neeraj.upadhyay@kernel.org \
--cc=oe-kbuild-all@lists.linux.dev \
--cc=philip.li@intel.com \
/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