Skip to contentSkip to conversation

WARNING: arch/x86/kernel/built-in.o(.pci_fixup_final+0x1c): Section mismatch in reference from the variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node to the function .init.text:quirk_amd_nb_node()

DISCUSSION Sebastian Andrzej Siewior 3 participants 4 messages Jun 12, 2012 1 message not in the archive Kbuild

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive
Quoted 7 lines · On Tue, Jun 12, 2012 at 01:51:54PM +0800, [email protected] wrote:

FYI: there are new compile warnings show up in

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
head:   0c358c16f8154ef47df749e60186f3c835869b0b
commit: d4974983cc76a0bff5e82987c761cda4ba08be66 [51/60] scripts/modpost: check for bad refernces in .pci.fixups area
config: i386-allmodconfig (attached as .config)
Quoted 7 lines

All related error/warning messages are:

WARNING: arch/x86/kernel/built-in.o(.pci_fixup_final+0x1c): Section mismatch in reference from the variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node to the function .init.text:quirk_amd_nb_node() The variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node references
a function __init quirk_amd_nb_node().

<snip>

This should be fixed by
http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=commit;h=763268610f596d66686f8a13bc8f0c0504782dd1

that means try the complete tree instead. The alternativ would to push this patch as the last one in series. However there is no damage in bisect except this splat so......

Sebastian

#2 lore raw
Quoted 15 lines · Sebastian Andrzej Siewior
Quoted 7 lines · On Tue, Jun 12, 2012 at 01:51:54PM +0800, [email protected] wrote:

FYI: there are new compile warnings show up in

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
head:   0c358c16f8154ef47df749e60186f3c835869b0b
commit: d4974983cc76a0bff5e82987c761cda4ba08be66 [51/60] scripts/modpost: check for bad refernces in .pci.fixups area
config: i386-allmodconfig (attached as .config)
Quoted 7 lines

All related error/warning messages are:

WARNING: arch/x86/kernel/built-in.o(.pci_fixup_final+0x1c): Section mismatch in reference from the variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node to the function .init.text:quirk_amd_nb_node() The variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node references
a function __init quirk_amd_nb_node().

Quoted 8 lines

<snip>

This should be fixed by
http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=commit;h=763268610f596d66686f8a13bc8f0c0504782dd1

that means try the complete tree instead. The alternativ would to push this patch as the last one in series. However there is no damage in bisect except this splat so......

Yeah I do commit-by-commit build tests to make the kernel more bisectable and complain if any step won't compile.

However here it seems just warnings, so no problem for me :-)

Thanks,
Fengguang

#3 lore raw
Quoted 21 lines · Fengguang Wu
Quoted 20 lines · Sebastian Andrzej Siewior
Quoted 7 lines · On Tue, Jun 12, 2012 at 01:51:54PM +0800, [email protected] wrote:

FYI: there are new compile warnings show up in

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
head:   0c358c16f8154ef47df749e60186f3c835869b0b
commit: d4974983cc76a0bff5e82987c761cda4ba08be66 [51/60] scripts/modpost: check for bad refernces in .pci.fixups area
config: i386-allmodconfig (attached as .config)

Quoted 7 lines

All related error/warning messages are:

WARNING: arch/x86/kernel/built-in.o(.pci_fixup_final+0x1c): Section mismatch in reference from the variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node to the function .init.text:quirk_amd_nb_node() The variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node references
a function __init quirk_amd_nb_node().

<snip>

This should be fixed by
  http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=commit;h=763268610f596d66686f8a13bc8f0c0504782dd1

Quoted 6 lines
Quoted 3 lines

that means try the complete tree instead. The alternativ would to push this patch as the last one in series. However there is no damage in bisect except this splat so......

Yeah I do commit-by-commit build tests to make the kernel more bisectable and complain if any step won't compile.

Wow, that's awesome :)

I reordered the patches in my topic branch, and I plan to rebase my "next" branch today, so that should take care of this.

Bjorn

#4 lore raw
Quoted 22 lines · Bjorn Helgaas
Quoted 21 lines · Fengguang Wu
Quoted 20 lines · Sebastian Andrzej Siewior
Quoted 7 lines · On Tue, Jun 12, 2012 at 01:51:54PM +0800, [email protected] wrote:

FYI: there are new compile warnings show up in

tree:   git://git.kernel.org/pub/scm/linux/kernel/git/helgaas/pci.git next
head:   0c358c16f8154ef47df749e60186f3c835869b0b
commit: d4974983cc76a0bff5e82987c761cda4ba08be66 [51/60] scripts/modpost: check for bad refernces in .pci.fixups area
config: i386-allmodconfig (attached as .config)

Quoted 7 lines

All related error/warning messages are:

WARNING: arch/x86/kernel/built-in.o(.pci_fixup_final+0x1c): Section mismatch in reference from the variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node to the function .init.text:quirk_amd_nb_node() The variable __pci_fixup_PCI_VENDOR_ID_AMDPCI_DEVICE_ID_AMD_15H_NB_F5quirk_amd_nb_node references
a function __init quirk_amd_nb_node().

<snip>

This should be fixed by
  http://git.kernel.org/?p=linux/kernel/git/helgaas/pci.git;a=commit;h=763268610f596d66686f8a13bc8f0c0504782dd1

Quoted 8 lines
Quoted 6 lines
Quoted 3 lines

that means try the complete tree instead. The alternativ would to push this patch as the last one in series. However there is no damage in bisect except this splat so......

Yeah I do commit-by-commit build tests to make the kernel more bisectable and complain if any step won't compile.

Wow, that's awesome :)

Thanks! :-)

Quoted 2 lines

I reordered the patches in my topic branch, and I plan to rebase my "next" branch today, so that should take care of this.

That's great, thank you very much!

Thanks,
Fengguang