mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Philip Li <philip.li@intel.com>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: kernel test robot <lkp@intel.com>,
	<oe-kbuild-all@lists.linux.dev>, <linux-kernel@vger.kernel.org>
Subject: Re: ERROR: start_text address is c000000000000700, should be c000000000000200
Date: Tue, 10 Sep 2024 08:41:57 +0800	[thread overview]
Message-ID: <Zt+V1fRCG+rspXub@rli9-mobl> (raw)
In-Reply-To: <20240909141319.0cd59cef@gandalf.local.home>

On Mon, Sep 09, 2024 at 02:13:19PM -0400, Steven Rostedt wrote:
> On Tue, 10 Sep 2024 02:05:29 +0800
> kernel test robot <lkp@intel.com> wrote:
> 
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> > head:   da3ea35007d0af457a0afc87e84fddaebc4e0b63
> > commit: 6e2fdceffdc6bd7b8ba314a1d1b976721533c8f9 tracing: Use refcount for trace_event_file reference counter
> > date:   5 weeks ago
> > config: powerpc64-randconfig-003-20240908 (https://download.01.org/0day-ci/archive/20240910/202409100106.A8692079-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/20240910/202409100106.A8692079-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/202409100106.A8692079-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
> > 
> 
> How is the associated commit anywhere close to being the cause of this bug?

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.

We will avoid sending reports on this issue.

[1] https://lore.kernel.org/oe-kbuild-all/202409090839.Gz712lD2-lkp@intel.com/

> 
> -- Steve
> 

      reply	other threads:[~2024-09-10  0:42 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-09 18:05 kernel test robot
2024-09-09 18:13 ` Steven Rostedt
2024-09-10  0:41   ` Philip Li [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=Zt+V1fRCG+rspXub@rli9-mobl \
    --to=philip.li@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=oe-kbuild-all@lists.linux.dev \
    --cc=rostedt@goodmis.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

all inboxes | Powered by JetHome®