Re: [pci:for-linus] BUILD REGRESSION f0bfeb2c51e44bee7876f2a0eda3518bd2c30a01

[Philip Li <philip.li@intel.com>]

On Thu, Oct 16, 2025 at 08:45:55PM +0300, Ilpo Järvinen wrote:
> On Thu, 16 Oct 2025, Mario Limonciello wrote:
> 
> > On 10/16/25 11:28 AM, Bjorn Helgaas wrote:
> > > On Thu, Oct 16, 2025 at 11:18:38AM -0500, Mario Limonciello wrote:
> > > > On 10/16/25 11:15 AM, Bjorn Helgaas wrote:
> > > > > On Thu, Oct 16, 2025 at 07:26:50AM +0800, kernel test robot wrote:
> > > > > > tree/branch:
> > > > > > https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git for-linus
> > > > > > branch HEAD: f0bfeb2c51e44bee7876f2a0eda3518bd2c30a01  PCI/VGA: Select
> > > > > > SCREEN_INFO on X86
> > > > > 
> > > > > Just making sure you've seen this, Mario.
> > > > 
> > > > I didn't see this, thanks for including me.
> > > > 
> > > > > I *think* f0bfeb2c51e4 is
> > > > > the most recent version, and it was on pci/for-linus, so I'll drop it
> > > > > for now.
> > > > 
> > > > Are you sure the failure is caused by "PCI/VGA: Select SCREEN_INFO on
> > > > X86"?
> > > 
> > > I'm not sure.  I looked briefly for a more detailed report but didn't
> > > find it.  Maybe didn't look hard enough.  This email seems like a
> > > summary that could possibly have included a link to details.
> > 
> > I looked at https://lore.kernel.org/oe-kbuild-all/ and don't see one there
> > either.

Hi all, sorry about this confusing report.

It was reported as an internal one (not sent out yet) because it fails to
verify "relocation truncated to fit" issue, on an early commit 17643231e977.

But not sure why it is also shown in this report, that I will check in detail
to fix the report logic issue.

tree:   https://git.kernel.org/pub/scm/linux/kernel/git/pci/pci.git for-linus
head:   17643231e97742d29227e3ed065f9a16208d3740
commit: 17643231e97742d29227e3ed065f9a16208d3740 [1/1] PCI/VGA: Select SCREEN_INFO
:::::: branch date: 16 hours ago
:::::: commit date: 16 hours ago
config: mips-allyesconfig (attached as .config)
compiler: mips-linux-gcc (GCC) 15.1.0
reproduce (this is a W=1 build): (attached as 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/202510141712.a7KcFkhp-lkp@intel.com/

All errors (new ones prefixed by >>):

   arch/mips/kernel/head.o: in function `__kernel_entry':
>> (.head.text+0x0): relocation truncated to fit: R_MIPS_26 against `kernel_entry'
   arch/mips/kernel/head.o: in function `smp_bootstrap':
>> (.ref.text+0xd8): relocation truncated to fit: R_MIPS_26 against `start_secondary'
   init/main.o: in function `set_reset_devices':


> > 
> > I think you should keep the patch in.  As it pertains to arch specific stuff
> > it behaves identically to pre-337bf13aa9dda.
> > 
> > If I'm wrong and there is actually still a problem we'll get more build robot
> > reports as they come.
> > 
> > > 
> > > > I wouldn't expect the below error to be:
> > > > 
> > > > > 
> > > > > > Error/Warning ids grouped by kconfigs:
> > > > > > 
> > > > > > recent_errors
> > > > > > `-- mips-allyesconfig
> > > > > >       |--
> > > > > > (.head.text):relocation-truncated-to-fit:R_MIPS_26-against-kernel_entry
> > > > > >       `--
> > > > > > (.ref.text):relocation-truncated-to-fit:R_MIPS_26-against-start_secondary
> 
> Looks unrelated to me. These "summary" reports from lkp often contain 
> unrelated errors, I think there's even mention about it somewhere in 
> the report text (probably before the part which was quoted to the list).
> 
> -- 
>  i.
>