Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

unknown argument: '-mno-single-pic-base' in drivers/firmware/efi/libstub/arm-stub.o #175

Closed
agners opened this issue Sep 25, 2018 · 6 comments
Closed

unknown argument: '-mno-single-pic-base' in drivers/firmware/efi/libstub/arm-stub.o #175

agners opened this issue Sep 25, 2018 · 6 comments
Assignees
@adelva1984
Labels
[ARCH] arm32 This bug impacts ARCH=arm [BUG] linux A bug that should be fixed in the mainline kernel. [FIXED][LINUX] 4.20 This bug was fixed in Linux 4.20

Comments

@agners
Copy link

agners commented Sep 25, 2018

Compiling multi_v7_defconfig fails in EFI:

clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:305: drivers/firmware/efi/libstub/arm-stub.o] Error 1                                                 
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:305: drivers/firmware/efi/libstub/arm32-stub.o] Error 1                                               
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:305: drivers/firmware/efi/libstub/efi-stub-helper.o] Error 1                                          
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:305: drivers/firmware/efi/libstub/fdt.o] Error 1                                                      
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:306: drivers/firmware/efi/libstub/gop.o] Error 1                                                      
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [drivers/firmware/efi/libstub/Makefile:44: drivers/firmware/efi/libstub/lib-fdt.o] Error 1                                    
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [drivers/firmware/efi/libstub/Makefile:44: drivers/firmware/efi/libstub/lib-fdt_empty_tree.o] Error 1                         
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [drivers/firmware/efi/libstub/Makefile:44: drivers/firmware/efi/libstub/lib-fdt_ro.o] Error 1                                 
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [drivers/firmware/efi/libstub/Makefile:44: drivers/firmware/efi/libstub/lib-fdt_rw.o] Error 1                                 
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [drivers/firmware/efi/libstub/Makefile:44: drivers/firmware/efi/libstub/lib-fdt_sw.o] Error 1                                 
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [drivers/firmware/efi/libstub/Makefile:44: drivers/firmware/efi/libstub/lib-fdt_wip.o] Error 1                                
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:305: drivers/firmware/efi/libstub/random.o] Error 1                                                   
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:305: drivers/firmware/efi/libstub/secureboot.o] Error 1                                               
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:305: drivers/firmware/efi/libstub/string.o] Error 1                                                   
clang-7: error: unknown argument: '-mno-single-pic-base'
make[4]: *** [scripts/Makefile.build:306: drivers/firmware/efi/libstub/tpm.o] Error 1                                                      
make[4]: Target '__build' not remade because of errors.
make[3]: *** [scripts/Makefile.build:546: drivers/firmware/efi/libstub] Error 2                                                            
make[3]: Target '__build' not remade because of errors.
make[2]: *** [scripts/Makefile.build:546: drivers/firmware/efi] Error 2                                                                    
make[2]: Target '__build' not remade because of errors.
make[1]: *** [scripts/Makefile.build:546: drivers/firmware] Error 2
@agners agners added [BUG] linux A bug that should be fixed in the mainline kernel. [ARCH] arm32 This bug impacts ARCH=arm [PATCH] Accepted A submitted patch has been accepted upstream labels Sep 25, 2018
@agners
Copy link
Author

agners commented Sep 25, 2018 •
edited by nathanchance
Loading

This is fixed with: https://lore.kernel.org/r/20180809164042.210675-1-astrachan@google.com/

The patch has been merged but did not show up in -next yet.

@agners agners mentioned this issue Sep 25, 2018
Closed
@adelva1984
Copy link

once this lands in torvalds/linux, we should send this to stable@vger.kernel.org for 4.4, 4.9 and 4.14. do not close this bug until those patches have landed.

@nathanchance
Copy link
Member

Commit in the EFI tree: https://git.kernel.org/pub/scm/linux/kernel/git/efi/efi.git/commit/?id=41f1c48420709470c51ee0e54b6fb28b956bb4e0

@nickdesaulniers
Copy link
Member

also, 4.19 stable, since this will land in 4.20.

@agners
Copy link
Author

agners commented Sep 27, 2018

Note that c1c3866 ("ARM: 8767/1: add support for building ARM kernel with clang") only got added with 4.18. So if older kernel should work, that would be needed too. There were also other fixes which might be necessary....

@agners
Copy link
Author

agners commented Oct 23, 2018

Fixed in mainline:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=41f1c48420709470c51ee0e54b6fb28b956bb4e0

@agners agners closed this as completed Oct 23, 2018
@agners agners added the [FIXED][LINUX] 4.20 This bug was fixed in Linux 4.20 label Oct 23, 2018
@tpimh tpimh removed the [PATCH] Accepted A submitted patch has been accepted upstream label Oct 24, 2018
nathanchance pushed a commit that referenced this issue Dec 9, 2018
thermal: armada: fix legacy resource fixup
dc6946c 
When the armada thermal module is inserted, removed and then reinserted,
the system panics as per the messages below.  The reason is that "edit"
a live resource in the resource tree twice, and end up with it pointing
to some other hardware.

Editing live resources (resources that are part of the registered
resource tree) is not permissible - the resource tree is an ordered
set of resources, sorted by start address, and when a new resource is
inserted, it is validated that it (a) fits within its parent resource
and (b) does not overlap a neighbouring resource.

Get rid of this resource editing.  We can instead adjust the return
value from ioremap() as ioremap() deals with the creation of page-
based mappings - provided the adjustment does not cross a page
boundary.

SError Interrupt on CPU1, code 0xbf000000 -- SError
CPU: 1 PID: 2749 Comm: modprobe Not tainted 4.19.0+ #175
Hardware name: Marvell 8040 MACCHIATOBin Double shot (DT)
pstate: 20400085 (nzCv daIf +PAN -UAO)
pc : regmap_mmio_read+0x3c/0x60
lr : regmap_mmio_read+0x3c/0x60
sp : ffffff800d453900
x29: ffffff800d453900 x28: ffffff800096a1d0
x27: 0000000000000100 x26: ffffff80009696d8
x25: ffffff8000969000 x24: ffffffc13a588918
x23: ffffffc13a9a28a8 x22: ffffff800d4539dc
x21: 0000000000000084 x20: ffffff800d4539dc
x19: ffffffc13a5d5480 x18: 0000000000000000
x17: 0000000000000000 x16: 0000000000000000
x15: 0000000000000000 x14: 0000000000000000
x13: 0000000000000000 x12: 0000000000000030
x11: 0101010101010101 x10: 7f7f7f7f7f7f7f7f
x9 : 0000000000000000 x8 : ffffffc13a5d5a80
x7 : 0000000000000000 x6 : 000000000000003f
x5 : 0000000000000000 x4 : 0000000000000000
x3 : ffffff800851be70 x2 : ffffff800851bd60
x1 : ffffff800d492ff8 x0 : 0000000000000000
Kernel panic - not syncing: Asynchronous SError Interrupt
CPU: 1 PID: 2749 Comm: modprobe Not tainted 4.19.0+ #175
Hardware name: Marvell 8040 MACCHIATOBin Double shot (DT)
Call trace:
 dump_backtrace+0x0/0x158
 show_stack+0x14/0x1c
 dump_stack+0x90/0xb0
 panic+0x128/0x298
 print_tainted+0x0/0xa8
 arm64_serror_panic+0x74/0x80
 do_serror+0x5c/0xb8
 el1_error+0xb4/0x144
 regmap_mmio_read+0x3c/0x60
 _regmap_bus_reg_read+0x18/0x20
 _regmap_read+0x64/0x180
 regmap_read+0x44/0x6c
 armada_ap806_init+0x24/0x5c [armada_thermal]
 armada_thermal_probe+0x2c8/0x37c [armada_thermal]
 platform_drv_probe+0x4c/0xb0
 really_probe+0x21c/0x2b4
 driver_probe_device+0x58/0xfc
 __driver_attach+0xd4/0xd8
 bus_for_each_dev+0x50/0xa0
 driver_attach+0x20/0x28
 bus_add_driver+0x1c4/0x228
 driver_register+0x6c/0x124
 __platform_driver_register+0x4c/0x54
 armada_thermal_driver_init+0x20/0x1000 [armada_thermal]
 do_one_initcall+0x30/0x204
 do_init_module+0x5c/0x1d4
 load_module+0x1a88/0x212c
 __se_sys_finit_module+0xa0/0xac
 __arm64_sys_finit_module+0x1c/0x24
 el0_svc_common+0x94/0xf0
 el0_svc_handler+0x24/0x80
 el0_svc+0x8/0x3c0
SMP: stopping secondary CPUs
Kernel Offset: disabled
CPU features: 0x0,21806000
Memory Limit: none

Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
Tested-by: Miquel Raynal <miquel.raynal@bootlin.com>
Signed-off-by: Eduardo Valentin <edubezval@gmail.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@adelva1984 adelva1984

Labels
[ARCH] arm32 This bug impacts ARCH=arm [BUG] linux A bug that should be fixed in the mainline kernel. [FIXED][LINUX] 4.20 This bug was fixed in Linux 4.20
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@agners @adelva1984 @tpimh @nickdesaulniers @nathanchance