20.09.2017 01:00, Stefan Bruens пишет: > On Dienstag, 19. September 2017 21:15:54 CEST Matwey V. Kornilov wrote: >> d503201f 8a180320 92750001 365ffc20 (d5380001) > > Decoded: > cat /tmp/code.s > .4byte 0xd503201f > .4byte 0x8a180320 > .4byte 0x92750001 > .4byte 0x365ffc20 > .4byte 0xd5380001 >
Hi, There is no such code in modprobe binary itself, not sure where it did come from. > rpi3:~ # as /tmp/code.s -o /tmp/code.o ; strip /tmp/code.o ; objdump -S /tmp/ > code.o > > /tmp/code.o: file format elf64-littleaarch64 > > > Disassembly of section .text: > > 0000000000000000 <.text>: > 0: d503201f nop > 4: 8a180320 and x0, x25, x24 > 8: 92750001 and x1, x0, #0x800 > c: 365ffc20 tbz w0, #11, 0xffffffffffffff90 > 10: d5380001 mrs x1, midr_el > > The last is the faulting instruction. According to: > http://infocenter.arm.com/help/index.jsp?topic=/com.arm.doc.den0024a/ > BABGBFBF.html > > modprobe tries to read the MIDR register, which is exception level 1 (EL1) > only, but I think modprobe is running in EL0. > > Kind regards, > > Stefan > > -- To unsubscribe, e-mail: [email protected] To contact the owner, e-mail: [email protected]
