Source: systemd Version: 44-11+deb7u4 Severity: normal Hi,
I'm aware that older kernels are unsupported in systemd and I have to forward-port my kernel before I can hope to boot using systemd. I'm booting an ARM system with a 2.6.38 kernel, which works fine using sysvinit, with a newly built debootstrapped root file system via NFS. SystemD starts, and immediately exits with a segmentation fault, leading to a kernel panic. Would it be possible to provide diagnostic output in this case and halt the system via the appropriate system call? Simon -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.16-3-amd64 (SMP w/8 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
