TI 포럼에 질문을 해보았지만 피드백이 별로 없어서 여기서 행운을 시험해 볼까 생각했습니다.
여기에서 제가 TI와 진행 중인 토론을 볼 수 있습니다.https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1158936/am3359-caught-segv-when-distro-s-systemd-starting
우리는 한동안 TI AM335x-ICEV2 보드를 사용하여 임베디드 Linux 애플리케이션을 개발해 왔으며 자체 맞춤형 보드 디자인을 받았습니다. 많은 디버깅과 읽기 후에 U-Boot를 올바르게 로드할 수 있었고 계속해서 매우 기본적인 FDT(플랫 장치 트리를 통한 U-Boot의 런타임 구성)를 사용하여 커널을 로드했는데 작동하는 것처럼 보였지만 일단 시작 단계에서 분할 오류 및/또는 실행 중단이 발생합니다.
처음에 우리는 DDR3 매핑의 하드웨어 문제를 의심했지만 디자인은 TI의 모든 요구 사항을 존중하는 것 같습니다. 또한 distro 시작 중에 항상 동결/세그브가 발생합니다. U-Boot 또는 Linux 커널 부팅 중에 단일 충돌/정지/segv를 본 적이 없습니다.
제가 시작할 수 있는 유일한 성공적인 구성은 SysVinit를 사용하고 모듈을 전혀 로드하지 않는 TI-Linux-SDK의 작은 파일 시스템입니다. 지금까지 모든 systemd OS(Debian 및 Arago)가 실패했습니다. 기존 Debian 10 이미지에서 Systemd를 SysV로 교체하려고 시도했지만 실패했습니다.
동일한 Uboot+ 커널이 TI IceV2 개발에서 완벽하게 실행되지만. 판자.
저는 Linux 부트로더/커널 전문가와는 거리가 멀고, 이 문제의 원인이 무엇인지, 심지어 어떤 테스트를 실행할지에 대한 이론도 부족합니다. 누구든지 몇 가지 질문에 답변할 의향이 있다면 일부 데이터를 기꺼이 공유하겠습니다.
시작 시 콘솔 출력은 다음과 같습니다.
아래 업데이트를 업데이트하기 위해 글자수 제한으로 인해 이 내용을 삭제했습니다.
이것은 내 FDT 파일입니다.
/dts-v1/;
#include "am33xx.dtsi"
/ {
model = "AM335x HELLO";
compatible = "ti,am335x-hello", "ti,am33xx";
chosen {
stdout-path = &uart3;
tick-timer = &timer2;
};
memory {
device_type = "memory";
reg = <0x80000000 0x10000000>; /* 256 MB */
};
vbat: fixedregulator@0 {
compatible = "regulator-fixed";
regulator-name = "vbat";
regulator-min-microvolt = <5000000>;
regulator-max-microvolt = <5000000>;
regulator-boot-on;
};
vmmc: fixedregulator@1 {
compatible = "regulator-fixed";
regulator-name = "vmmc";
regulator-min-microvolt = <3300000>;
regulator-max-microvolt = <3300000>;
regulator-always-on;
regulator-boot-on;
};
};
&am33xx_pinmux {
mmc0_pins_default: mmc0_pins_default {
pinctrl-single,pins = <
AM33XX_PADCONF(AM335X_PIN_MMC0_DAT3, PIN_INPUT_PULLUP, MUX_MODE0)
AM33XX_PADCONF(AM335X_PIN_MMC0_DAT2, PIN_INPUT_PULLUP, MUX_MODE0)
AM33XX_PADCONF(AM335X_PIN_MMC0_DAT1, PIN_INPUT_PULLUP, MUX_MODE0)
AM33XX_PADCONF(AM335X_PIN_MMC0_DAT0, PIN_INPUT_PULLUP, MUX_MODE0)
AM33XX_PADCONF(AM335X_PIN_MMC0_CLK, PIN_INPUT_PULLUP, MUX_MODE0)
AM33XX_PADCONF(AM335X_PIN_MMC0_CMD, PIN_INPUT_PULLUP, MUX_MODE0)
>;
};
uart1_pins: uart1_pins {
pinctrl-single,pins = <
0x180 (PIN_INPUT_PULLUP | MUX_MODE0) /* uart1_rxd.uart1_rxd */
0x184 (PIN_OUTPUT_PULLDOWN | MUX_MODE0) /* uart1_txd.uart1_txd */
>;
};
};
&uart1 {
pinctrl-names = "default";
pinctrl-0 = <&uart1_pins>;
status = "okay";
};
&mmc1 {
status = "okay";
vmmc-supply = <&vmmc>;
bus-width = <4>;
pinctrl-names = "default";
pinctrl-0 = <&mmc0_pins_default>;
};
편집 #1 초기화 로그가 항상 동일한 위치에서 충돌/멈추는 것은 아닙니다. 여기에 또 다른 것이 있지만 U-Boot를 사용하면옵션 매개변수 printk.devkmsg=on systemd.log_level=디버그 디버깅:
[ 2.175611] Run /sbin/init as init process
[ 2.863478] systemd[1]: System time before build time, advancing clock.
[ 2.996170] systemd[1]: systemd 241 running in system mode. (+PAM +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD -IDN
2 +IDN -PCRE2 default-hierarchy=hybrid)
[ 3.018180] systemd[1]: No virtualization found in DMI
[ 3.023569] systemd[1]: No virtualization found in CPUID
[ 3.028969] systemd[1]: Virtualization XEN not found, /proc/xen does not exist
[ 3.036559] systemd[1]: No virtualization found in /proc/device-tree/*
[ 3.043420] systemd[1]: UML virtualization not found in /proc/cpuinfo.
[ 3.050020] systemd[1]: This platform does not support /proc/sysinfo
[ 3.056508] systemd[1]: Found VM virtualization none
[ 3.061529] systemd[1]: Detected architecture arm.
[ 3.067154] systemd[1]: Mounting cgroup to /sys/fs/cgroup/perf_event of type cgroup with options perf_event.
[ 3.078818] systemd[1]: Mounting cgroup to /sys/fs/cgroup/blkio of type cgroup with options blkio.
[ 3.089463] systemd[1]: Mounting cgroup to /sys/fs/cgroup/cpu,cpuacct of type cgroup with options cpu,cpuacct.
[ 3.101298] systemd[1]: Mounting cgroup to /sys/fs/cgroup/freezer of type cgroup with options freezer.
[ 3.112236] systemd[1]: Mounting cgroup to /sys/fs/cgroup/memory of type cgroup with options memory.
[ 3.123482] systemd[1]: Mounting cgroup to /sys/fs/cgroup/devices of type cgroup with options devices.
[ 3.134395] systemd[1]: Mounting cgroup to /sys/fs/cgroup/pids of type cgroup with options pids.
[ 3.144778] systemd[1]: Mounting cgroup to /sys/fs/cgroup/net_cls of type cgroup with options net_cls.
Welcome to Debian GNU/Linux 10 (buster)!
[ 3.184740] systemd[1]: Set hostname to <arm>.
[ 3.197755] systemd[1]: Successfully added address 127.0.0.1 to loopback interface
[ 3.205882] systemd[1]: Successfully added address ::1 to loopback interface
[ 3.213414] systemd[1]: Successfully brought loopback interface up
[ 3.220179] systemd[1]: Setting 'fs/file-max' to '2147483647'.
[ 3.230141] systemd[1]: Found cgroup2 on /sys/fs/cgroup/unified, unified hierarchy for systemd controller
[ 3.240134] systemd[1]: Unified cgroup hierarchy is located at /sys/fs/cgroup/unified. Controllers are on legacy hierarchies.
[ 3.258918] systemd[1]: Can't allocate BPF LPM TRIE map, BPF firewalling is not supported: Function not implemented
[ 3.269658] systemd[1]: Can't load kernel CGROUP DEVICE BPF program, BPF device control is not supported: Function not implemented
[ 3.281537] systemd[1]: Controller 'cpu' supported: yes
[ 3.286948] systemd[1]: Controller 'cpuacct' supported: yes
[ 3.292562] systemd[1]: Controller 'io' supported: no
[ 3.297676] systemd[1]: Controller 'blkio' supported: yes
[ 3.303132] systemd[1]: Controller 'memory' supported: yes
[ 3.308654] systemd[1]: Controller 'devices' supported: yes
[ 3.314306] systemd[1]: Controller 'pids' supported: yes
[ 3.319657] systemd[1]: Controller 'bpf-firewall' supported: no
[ 3.325634] systemd[1]: Controller 'bpf-devices' supported: no
[ 3.331602] systemd[1]: Set up TFD_TIMER_CANCEL_ON_SET timerfd.
[ 3.339066] systemd[1]: Enabling showing of status.
[ 3.345654] systemd[1]: Successfully forked off '(sd-executor)' as PID 55.
[ 3.358258] systemd[55]: Successfully forked off '(direxec)' as PID 56.
[ 3.373243] systemd[55]: Successfully forked off '(direxec)' as PID 57.
[ 3.381122] systemd[55]: Successfully forked off '(direxec)' as PID 58.
[ 3.434440] systemd[55]: Successfully forked off '(direxec)' as PID 59.
[ 3.442219] systemd[55]: Successfully forked off '(direxec)' as PID 60.
[ 3.504363] systemd[55]: Successfully forked off '(direxec)' as PID 61.
[ 3.512081] systemd[55]: Successfully forked off '(direxec)' as PID 62.
[ 3.634380] systemd[55]: Successfully forked off '(direxec)' as PID 63.
[ 3.642125] systemd[55]: Successfully forked off '(direxec)' as PID 64.
[ 3.744461] systemd[55]: Successfully forked off '(direxec)' as PID 65.
[ 3.752179] systemd[55]: Successfully forked off '(direxec)' as PID 66.
[ 3.866714] systemd[55]: Successfully forked off '(direxec)' as PID 67.
[ 3.923497] systemd[55]: /lib/systemd/system-generators/systemd-rc-local-generator terminated by signal SEGV.
[ 3.971004] systemd-hibernate-resume-generator[62]: Not running in an initrd, quitting.
[ 4.046186] systemd[55]: /lib/systemd/system-generators/systemd-hibernate-resume-generator succeeded.
[ 4.080695] systemd[55]: /lib/systemd/system-generators/systemd-gpt-auto-generator terminated by signal SEGV.
[ 4.110089] systemd[55]: /lib/systemd/system-generators/systemd-getty-generator failed with exit status 127.
[ 4.121572] systemd[55]: /lib/systemd/system-generators/systemd-cryptsetup-generator succeeded.
[ 4.130888] systemd-sysv-generator[66]: Native unit for sendsigs.service already exists, skipping.
[ 4.142139] systemd-sysv-generator[66]: Cannot find unit udhcpd.service.
[ 4.149412] systemd-sysv-generator[66]: Native unit for bootlogs.service already exists, skipping.
[ 4.159691] systemd-sysv-generator[66]: Cannot find unit cpufrequtils.service.
[ 4.170591] systemd-sysv-generator[66]: Native unit for procps.service already exists, skipping.
[ 4.179985] systemd-sysv-generator[66]: Native unit for checkroot.service already exists, skipping.
[ 4.189433] systemd-sysv-generator[66]: Native unit for urandom.service already exists, skipping.
[ 4.200115] systemd-sysv-generator[66]: Native unit for rcS.service already exists, skipping.
[ 4.211224] systemd-sysv-generator[66]: Native unit for kmod.service already exists, skipping.
[ 4.220302] systemd-sysv-generator[66]: Native unit for checkfs.service already exists, skipping.
[ 4.229691] systemd-sysv-generator[66]: Cannot find unit loadcpufreq.service.
[ 4.237351] systemd-sysv-generator[66]: Native unit for rc.local.service already exists, skipping.
[ 4.248773] systemd-sysv-generator[66]: Native unit for udev.service already exists, skipping.
[ 4.257901] systemd-sysv-generator[66]: Native unit for bluetooth.service already exists, skipping.
[ 4.268275] systemd-sysv-generator[66]: Native unit for rsyslog.service already exists, skipping.
[ 4.277771] systemd-sysv-generator[66]: Cannot find unit exim4.service.
[ 4.284927] systemd-sysv-generator[66]: Native unit for umountroot.service already exists, skipping.
[ 4.294421] systemd-sysv-generator[66]: Native unit for halt.service already exists, skipping.
[ 4.303444] systemd-sysv-generator[66]: Native unit for mountnfs-bootclean.service already exists, skipping.
[ 4.313619] systemd-sysv-generator[66]: Native unit for hostname.service already exists, skipping.
[ 4.324009] systemd-sysv-generator[66]: Native unit for avahi-daemon.service already exists, skipping.
[ 4.333755] systemd-sysv-generator[66]: Native unit for mountall.service already exists, skipping.
[ 4.343999] systemd-sysv-generator[66]: Native unit for ofono.service already exists, skipping.
[ 4.354101] systemd-sysv-generator[66]: Native unit for connman.service already exists, skipping.
[ 4.363490] systemd-sysv-generator[66]: Native unit for mountkernfs.service already exists, skipping.
[ 4.372965] systemd-sysv-generator[66]: Native unit for reboot.service already exists, skipping.
[ 4.382251] systemd-sysv-generator[66]: Native unit for hostapd.service already exists, skipping.
[ 4.391633] systemd-sysv-generator[66]: Native unit for hwclock.service already exists, skipping.
[ 4.400903] systemd-sysv-generator[66]: Native unit for rmnologin.service already exists, skipping.
[ 4.411226] systemd-sysv-generator[66]: Native unit for dnsmasq.service already exists, skipping.
[ 4.420535] systemd-sysv-generator[66]: Native unit for mountdevsubfs.service already exists, skipping.
[ 4.431225] systemd-sysv-generator[66]: Native unit for dbus.service already exists, skipping.
[ 4.440317] systemd-sysv-generator[66]: Native unit for umountfs.service already exists, skipping.
[ 4.450598] systemd-sysv-generator[66]: Native unit for cron.service already exists, skipping.
[ 4.459795] systemd-sysv-generator[66]: Native unit for sudo.service already exists, skipping.
[ 4.468808] systemd-sysv-generator[66]: Native unit for mountall-bootclean.service already exists, skipping.
[ 4.479086] systemd-sysv-generator[66]: Native unit for mountnfs.service already exists, skipping.
[ 4.488424] systemd-sysv-generator[66]: Native unit for brightness.service already exists, skipping.
[ 4.498809] systemd-sysv-generator[66]: Native unit for dundee.service already exists, skipping.
[ 4.507999] systemd-sysv-generator[66]: Native unit for umountnfs.service already exists, skipping.
[ 4.517566] systemd-sysv-generator[66]: Native unit for rc.service already exists, skipping.
[ 4.527371] systemd-sysv-generator[66]: Native unit for ssh.service already exists, skipping.
[ 4.536340] systemd-sysv-generator[66]: Native unit for checkroot-bootclean.service already exists, skipping.
[ 4.546706] systemd-sysv-generator[66]: Native unit for apache-htcacheclean.service already exists, skipping.
[ 4.557047] systemd-sysv-generator[66]: Native unit for single.service already exists, skipping.
[ 4.567119] systemd-sysv-generator[66]: Native unit for rsync.service already exists, skipping.
[ 4.576220] systemd-sysv-generator[66]: Native unit for killprocs.service already exists, skipping.
[ 4.586582] systemd-sysv-generator[66]: Native unit for networking.service already exists, skipping.
[ 4.596250] systemd-sysv-generator[66]: Native unit for apache2.service already exists, skipping.
[ 4.605557] systemd-sysv-generator[66]: Native unit for bootmisc.service already exists, skipping.
[ 4.616340] systemd-sysv-generator[66]: Ignoring S02single symlink in rc1.d, not generating single.service.
[ 4.626331] systemd-sysv-generator[66]: Ignoring S01killprocs symlink in rc1.d, not generating killprocs.service.
[ 4.636740] systemd-sysv-generator[66]: Ignoring S01bootlogs symlink in rc1.d, not generating bootlogs.service.
[ 4.648331] systemd-sysv-generator[66]: Ignoring S01rsyslog symlink in rc2.d, not generating rsyslog.service.
[ 4.658459] systemd-sysv-generator[66]: Ignoring S04ofono symlink in rc2.d, not generating ofono.service.
[ 4.668189] systemd-sysv-generator[66]: Ignoring S03ssh symlink in rc2.d, not generating ssh.service.
[ 4.677527] systemd-sysv-generator[66]: Ignoring S01rsync symlink in rc2.d, not generating rsync.service.
[ 4.687190] systemd-sysv-generator[66]: Ignoring S04dundee symlink in rc2.d, not generating dundee.service.
[ 4.697047] systemd-sysv-generator[66]: Ignoring S01hostapd symlink in rc2.d, not generating hostapd.service.
[ 4.707054] systemd-sysv-generator[66]: Ignoring S03rsync symlink in rc2.d, not generating rsync.service.
[ 4.716720] systemd-sysv-generator[66]: Ignoring S03rmnologin symlink in rc2.d, not generating rmnologin.service.
[ 4.727116] systemd-sysv-generator[66]: Ignoring S01cron symlink in rc2.d, not generating cron.service.
[ 4.736608] systemd-sysv-generator[66]: Ignoring S01apache2 symlink in rc2.d, not generating apache2.service.
[ 4.746613] systemd-sysv-generator[66]: Ignoring S01ssh symlink in rc2.d, not generating ssh.service.
[ 4.755960] systemd-sysv-generator[66]: Ignoring S01sudo symlink in rc2.d, not generating sudo.service.
[ 4.765522] systemd-sysv-generator[66]: Ignoring S01bluetooth symlink in rc2.d, not generating bluetooth.service.
[ 4.775884] systemd-sysv-generator[66]: Ignoring S01ofono symlink in rc2.d, not generating ofono.service.
[ 4.785583] systemd-sysv-generator[66]: Ignoring S04bluetooth symlink in rc2.d, not generating bluetooth.service.
[ 4.795942] systemd-sysv-generator[66]: Ignoring S02apache2 symlink in rc2.d, not generating apache2.service.
[ 4.805969] systemd-sysv-generator[66]: Ignoring S01connman symlink in rc2.d, not generating connman.service.
[ 4.815976] systemd-sysv-generator[66]: Ignoring S04connman symlink in rc2.d, not generating connman.service.
[ 4.826024] systemd-sysv-generator[66]: Ignoring S05rc.local symlink in rc2.d, not generating rc.local.service.
[ 4.836208] systemd-sysv-generator[66]: Ignoring S01dundee symlink in rc2.d, not generating dundee.service.
[ 4.846062] systemd-sysv-generator[66]: Ignoring S01bootlogs symlink in rc2.d, not generating bootlogs.service.
[ 4.856258] systemd-sysv-generator[66]: Ignoring S01avahi-daemon symlink in rc2.d, not generating avahi-daemon.service.
[ 4.867164] systemd-sysv-generator[66]: Ignoring S04avahi-daemon symlink in rc2.d, not generating avahi-daemon.service.
[ 4.878058] systemd-sysv-generator[66]: Ignoring S01dbus symlink in rc2.d, not generating dbus.service.
[ 4.887561] systemd-sysv-generator[66]: Ignoring S03dbus symlink in rc2.d, not generating dbus.service.
[ 4.897057] systemd-sysv-generator[66]: Ignoring S03cron symlink in rc2.d, not generating cron.service.
[ 4.907950] systemd-sysv-generator[66]: Ignoring S01rsyslog symlink in rc3.d, not generating rsyslog.service.
[ 4.918100] systemd-sysv-generator[66]: Ignoring S04ofono symlink in rc3.d, not generating ofono.service.
[ 4.927809] systemd-sysv-generator[66]: Ignoring S03ssh symlink in rc3.d, not generating ssh.service.
[ 4.937169] systemd-sysv-generator[66]: Ignoring S01rsync symlink in rc3.d, not generating rsync.service.
[ 4.946831] systemd-sysv-generator[66]: Ignoring S04dundee symlink in rc3.d, not generating dundee.service.
[ 4.956668] systemd-sysv-generator[66]: Ignoring S01hostapd symlink in rc3.d, not generating hostapd.service.
[ 4.966695] systemd-sysv-generator[66]: Ignoring S03rsync symlink in rc3.d, not generating rsync.service.
[ 4.976358] systemd-sysv-generator[66]: Ignoring S03rmnologin symlink in rc3.d, not generating rmnologin.service.
[ 4.986727] systemd-sysv-generator[66]: Ignoring S01cron symlink in rc3.d, not generating cron.service.
[ 4.996231] systemd-sysv-generator[66]: Ignoring S01apache2 symlink in rc3.d, not generating apache2.service.
[ 5.006237] systemd-sysv-generator[66]: Ignoring S01ssh symlink in rc3.d, not generating ssh.service.
[ 5.015561] systemd-sysv-generator[66]: Ignoring S01sudo symlink in rc3.d, not generating sudo.service.
[ 5.025108] systemd-sysv-generator[66]: Ignoring S01bluetooth symlink in rc3.d, not generating bluetooth.service.
[ 5.035470] systemd-sysv-generator[66]: Ignoring S01ofono symlink in rc3.d, not generating ofono.service.
[ 5.045144] systemd-sysv-generator[66]: Ignoring S04bluetooth symlink in rc3.d, not generating bluetooth.service.
[ 5.055522] systemd-sysv-generator[66]: Ignoring S02apache2 symlink in rc3.d, not generating apache2.service.
[ 5.065531] systemd-sysv-generator[66]: Ignoring S01connman symlink in rc3.d, not generating connman.service.
[ 5.075557] systemd-sysv-generator[66]: Ignoring S04connman symlink in rc3.d, not generating connman.service.
[ 5.085585] systemd-sysv-generator[66]: Ignoring S05rc.local symlink in rc3.d, not generating rc.local.service.
[ 5.095786] systemd-sysv-generator[66]: Ignoring S01dundee symlink in rc3.d, not generating dundee.service.
[ 5.105621] systemd-sysv-generator[66]: Ignoring S01bootlogs symlink in rc3.d, not generating bootlogs.service.
[ 5.115840] systemd-sysv-generator[66]: Ignoring S01avahi-daemon symlink in rc3.d, not generating avahi-daemon.service.
[ 5.126722] systemd-sysv-generator[66]: Ignoring S04avahi-daemon symlink in rc3.d, not generating avahi-daemon.service.
[ 5.137635] systemd-sysv-generator[66]: Ignoring S01dbus symlink in rc3.d, not generating dbus.service.
[ 5.147118] systemd-sysv-generator[66]: Ignoring S03dbus symlink in rc3.d, not generating dbus.service.
[ 5.156631] systemd-sysv-generator[66]: Ignoring S03cron symlink in rc3.d, not generating cron.service.
[ 5.167496] systemd-sysv-generator[66]: Ignoring S01rsyslog symlink in rc4.d, not generating rsyslog.service.
[ 5.177641] systemd-sysv-generator[66]: Ignoring S04ofono symlink in rc4.d, not generating ofono.service.
[ 5.187344] systemd-sysv-generator[66]: Ignoring S03ssh symlink in rc4.d, not generating ssh.service.
[ 5.196702] systemd-sysv-generator[66]: Ignoring S01rsync symlink in rc4.d, not generating rsync.service.
[ 5.206365] systemd-sysv-generator[66]: Ignoring S04dundee symlink in rc4.d, not generating dundee.service.
[ 5.216198] systemd-sysv-generator[66]: Ignoring S01hostapd symlink in rc4.d, not generating hostapd.service.
[ 5.226224] systemd-sysv-generator[66]: Ignoring S03rsync symlink in rc4.d, not generating rsync.service.
[ 5.235886] systemd-sysv-generator[66]: Ignoring S03rmnologin symlink in rc4.d, not generating rmnologin.service.
[ 5.246259] systemd-sysv-generator[66]: Ignoring S01cron symlink in rc4.d, not generating cron.service.
[ 5.255763] systemd-sysv-generator[66]: Ignoring S01apache2 symlink in rc4.d, not generating apache2.service.
[ 5.265771] systemd-sysv-generator[66]: Ignoring S01ssh symlink in rc4.d, not generating ssh.service.
[ 5.275106] systemd-sysv-generator[66]: Ignoring S01sudo symlink in rc4.d, not generating sudo.service.
[ 5.284660] systemd-sysv-generator[66]: Ignoring S01bluetooth symlink in rc4.d, not generating bluetooth.service.
[ 5.295023] systemd-sysv-generator[66]: Ignoring S01ofono symlink in rc4.d, not generating ofono.service.
[ 5.304697] systemd-sysv-generator[66]: Ignoring S04bluetooth symlink in rc4.d, not generating bluetooth.service.
[ 5.315074] systemd-sysv-generator[66]: Ignoring S02apache2 symlink in rc4.d, not generating apache2.service.
[ 5.325082] systemd-sysv-generator[66]: Ignoring S01connman symlink in rc4.d, not generating connman.service.
[ 5.335108] systemd-sysv-generator[66]: Ignoring S04connman symlink in rc4.d, not generating connman.service.
[ 5.345135] systemd-sysv-generator[66]: Ignoring S05rc.local symlink in rc4.d, not generating rc.local.service.
[ 5.355336] systemd-sysv-generator[66]: Ignoring S01dundee symlink in rc4.d, not generating dundee.service.
[ 5.365172] systemd-sysv-generator[66]: Ignoring S01bootlogs symlink in rc4.d, not generating bootlogs.service.
[ 5.375388] systemd-sysv-generator[66]: Ignoring S01avahi-daemon symlink in rc4.d, not generating avahi-daemon.service.
[ 5.386269] systemd-sysv-generator[66]: Ignoring S04avahi-daemon symlink in rc4.d, not generating avahi-daemon.service.
[ 5.397180] systemd-sysv-generator[66]: Ignoring S01dbus symlink in rc4.d, not generating dbus.service.
[ 5.406664] systemd-sysv-generator[66]: Ignoring S03dbus symlink in rc4.d, not generating dbus.service.
[ 5.416178] systemd-sysv-generator[66]: Ignoring S03cron symlink in rc4.d, not generating cron.service.
[ 5.426959] systemd-sysv-generator[66]: Ignoring S01rsyslog symlink in rc5.d, not generating rsyslog.service.
[ 5.437110] systemd-sysv-generator[66]: Ignoring S04ofono symlink in rc5.d, not generating ofono.service.
[ 5.446818] systemd-sysv-generator[66]: Ignoring S03ssh symlink in rc5.d, not generating ssh.service.
[ 5.456174] systemd-sysv-generator[66]: Ignoring S01rsync symlink in rc5.d, not generating rsync.service.
[ 5.465836] systemd-sysv-generator[66]: Ignoring S04dundee symlink in rc5.d, not generating dundee.service.
[ 5.475671] systemd-sysv-generator[66]: Ignoring S01hostapd symlink in rc5.d, not generating hostapd.service.
[ 5.485698] systemd-sysv-generator[66]: Ignoring S03rsync symlink in rc5.d, not generating rsync.service.
[ 5.495360] systemd-sysv-generator[66]: Ignoring S03rmnologin symlink in rc5.d, not generating rmnologin.service.
[ 5.505731] systemd-sysv-generator[66]: Ignoring S01cron symlink in rc5.d, not generating cron.service.
[ 5.515235] systemd-sysv-generator[66]: Ignoring S01apache2 symlink in rc5.d, not generating apache2.service.
[ 5.525241] systemd-sysv-generator[66]: Ignoring S01ssh symlink in rc5.d, not generating ssh.service.
[ 5.534565] systemd-sysv-generator[66]: Ignoring S01sudo symlink in rc5.d, not generating sudo.service.
[ 5.544117] systemd-sysv-generator[66]: Ignoring S01bluetooth symlink in rc5.d, not generating bluetooth.service.
[ 5.554480] systemd-sysv-generator[66]: Ignoring S01ofono symlink in rc5.d, not generating ofono.service.
[ 5.564153] systemd-sysv-generator[66]: Ignoring S04bluetooth symlink in rc5.d, not generating bluetooth.service.
[ 5.574532] systemd-sysv-generator[66]: Ignoring S02apache2 symlink in rc5.d, not generating apache2.service.
[ 5.584540] systemd-sysv-generator[66]: Ignoring S01connman symlink in rc5.d, not generating connman.service.
[ 5.594567] systemd-sysv-generator[66]: Ignoring S04connman symlink in rc5.d, not generating connman.service.
[ 5.604592] systemd-sysv-generator[66]: Ignoring S05rc.local symlink in rc5.d, not generating rc.local.service.
[ 5.614792] systemd-sysv-generator[66]: Ignoring S01dundee symlink in rc5.d, not generating dundee.service.
[ 5.624629] systemd-sysv-generator[66]: Ignoring S01bootlogs symlink in rc5.d, not generating bootlogs.service.
[ 5.634845] systemd-sysv-generator[66]: Ignoring S01avahi-daemon symlink in rc5.d, not generating avahi-daemon.service.
[ 5.645726] systemd-sysv-generator[66]: Ignoring S04avahi-daemon symlink in rc5.d, not generating avahi-daemon.service.
[ 5.656638] systemd-sysv-generator[66]: Ignoring S01dbus symlink in rc5.d, not generating dbus.service.
[ 5.666122] systemd-sysv-generator[66]: Ignoring S03dbus symlink in rc5.d, not generating dbus.service.
[ 5.675635] systemd-sysv-generator[66]: Ignoring S03cron symlink in rc5.d, not generating cron.service.
[ 5.685319] systemd-sysv-generator[66]: Loading SysV script /etc/init.d/udhcpd
[ 5.694263] systemd-sysv-generator[66]: Loading SysV script /etc/init.d/exim4
[ 5.705397] systemd-sysv-generator[66]: Loading SysV script /etc/init.d/loadcpufreq
[ 5.716624] systemd-sysv-generator[66]: Loading SysV script /etc/init.d/cpufrequtils
[ 5.731392] systemd[55]: /lib/systemd/system-generators/systemd-sysv-generator succeeded.
[ 5.739965] systemd[55]: /lib/systemd/system-generators/systemd-debug-generator succeeded.
[ 5.748639] systemd[55]: /lib/systemd/system-generators/systemd-run-generator succeeded.
[ 5.757026] systemd[55]: /lib/systemd/system-generators/systemd-veritysetup-generator terminated by signal SEGV.
[ 5.767390] systemd[55]: /lib/systemd/system-generators/systemd-bless-boot-generator terminated by signal SEGV.
[ 5.777681] systemd[55]: /lib/systemd/system-generators/systemd-system-update-generator succeeded.
[ 5.786799] systemd[55]: /lib/systemd/system-generators/systemd-fstab-generator terminated by signal SEGV.
[ 5.797673] systemd[1]: (sd-executor) succeeded.
[ 5.802788] systemd[1]: Looking for unit files in (higher priority first):
[ 5.809936] systemd[1]: /etc/systemd/system.control
[ 5.815015] systemd[1]: /run/systemd/system.control
[ 5.820012] systemd[1]: /run/systemd/transient
[ 5.824629] systemd[1]: /etc/systemd/system
[ 5.828928] systemd[1]: /run/systemd/system
충돌이 발생한다는 점을 제외하면 각 부츠 사이의 상수를 찾을 수 없는 것 같습니다...
편집 2: 예상되는 개발 보드 출력은 다음과 같습니다.
Welcome to Debian GNU/Linux 10 (buster)!
[ 6.828019] systemd[1]: Set hostname to <arm>.
[ 7.793038] systemd[1]: File /lib/systemd/system/systemd-journald.service:12 configures an IP fire wall (IPAddressDeny=any), but the local system does not support BPF/cgroup based firewalling.
[ 7.810794] systemd[1]: Proceeding WITHOUT firewalling in effect! (This warning is only shown for the first loaded unit using IP firewalling.)
[ 8.292129] systemd[1]: Listening on udev Control Socket.
[ OK ] Listening on udev Control Socket.
...
(and so on)
모듈 없이 SySVInit 환경을 사용하여 셸로 부팅할 수는 없지만 특정 명령으로 인해 작동이 멈출 수 있습니다.
답변1
이 문제는 TI 포럼에서 해결되었으며 관심 있는 분은 아래 링크를 따라가실 수 있습니다.
전체적으로 문제는 내 VDD_MPU(1.1V)가 내 PMIC에 의해 구동되고 PMIC 드라이버가 올바르게 초기화되지 않았다는 것입니다. 시스템이 CPU 주파수를 높이는 경우를 의미합니다. 800MHz에서는 1.1V가 너무 낮으므로 MPU의 전원이 꺼지고 손상됩니다. 해결책은 수동으로 VDD_MPU를 더 높은 값(1.3V 미만)으로 높이거나 CPU 주파수에 따라 전압을 자동으로 관리하도록 PMIC를 구성하는 것이었습니다.