Hi Alexey, Hi Vineet,

is uClibc-ng 1.0.34 broken on Linux kernel 4.19.136?
I am using gcc 9.3.0 and binutils 2.35.

I get following stacktrace:

[    9.667903] Starting Linux (built with OpenADK).
[    9.673796] Freeing unused kernel memory: 592K
[    9.678323] This architecture does not have kernel memory
protection.
[    9.684992] Run /sbin/init as init process
[    9.693619] potentially unexpected fatal signal 11.
[    9.698600] Path: /bin/busybox
[    9.701967] CPU: 2 PID: 1 Comm: init Not tainted 4.19.136-1 #2
[    9.707882] 
[    9.707882] [ECR   ]: 0x00050200 => Invalid Write @ 0x00000000 by
insn @ 0x2000181a
[    9.717373] [EFA   ]: 0x00000000
[    9.717373] [BLINK ]: 0x20001792
[    9.717373] [ERET  ]: 0x2000181a
[    9.727392]     @off 0x181a in [/lib/ld-uClibc-1.0.34.so]
[    9.727392]     VMA: 0x20000000 to 0x20008000
[    9.737355] [STAT32]: 0x80081082 : IE U     
[    9.741969] BTA: 0x20001792   SP: 0x5f8bdb9c  FP: 0x5f8bdd2c
[    9.747648] LPS: 0x00000010  LPE: 0x00000080 LPC: 0x00000000
[    9.753784] r00: 0x20005b64  r01: 0x00000025 r02: 0xffffffff 
[    9.753784] r03: 0x00000022  r04: 0x00000000 r05: 0x00000000 
[    9.753784] r06: 0x00000000  r07: 0x00000000 r08: 0x000000de 
[    9.753784] r09: 0x0000000c  r10: 0x00000001 r11: 0x00000000 
[    9.753784] r12: 0x20001792  r13: 0x00000000 r14: 0x20005b64 
[    9.753784] r15: 0x2000a070  r16: 0x5f8bddf8 r17: 0x5f8bdf2c 
[    9.753784] r18: 0x2000a070  r19: 0x00000000 r20: 0x5f8bddf8 
[    9.753784] r21: 0x00000000  r22: 0x00000000 r23: 0x00000000 
[    9.753784] r24: 0x5f8bdc18  r25: 0x00000000 
[    9.753784] 
[    9.753784] 
[    9.807098] Kernel panic - not syncing: Attempted to kill init!
exitcode=0x0000000b
[    9.807098] 

With kernel 5.4.53 it just hangs on this line here:
[    2.579235] NET: Registered protocol family 1

I am using initramfs with piggyback loaded from mmc card.

best regards
 Waldemar
_______________________________________________
devel mailing list
[email protected]
https://mailman.uclibc-ng.org/cgi-bin/mailman/listinfo/devel

Reply via email to