Your message dated Tue, 14 Apr 2015 21:14:00 +0200
with message-id <[email protected]>
and subject line Re: Bug#768370: systemd: segmentation fault on old kernel
has caused the Debian Bug report #768370,
regarding systemd: segmentation fault on old kernel
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
768370: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=768370
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Am 07.11.2014 um 00:46 schrieb Michael Biebl:
> Control: tags -1 moreinfo
>
> Am 06.11.2014 um 22:54 schrieb Simon Richter:
>> Source: systemd
>> Version: 44-11+deb7u4
>> Severity: normal
>
> Are you using systemd on wheezy?
>
>> 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
>
> Just a nitpick, it's called systemd, not SystemD.
>
>> a kernel panic.
>
>> Would it be possible to provide diagnostic output in this case and halt the
>> system via the appropriate system call?
>
> systemd freezes execution, when it dies, so there shouldn't be a kernel
> panic.
>
> Can you please try with systemd 215 from jessie on a jessie system?
No further information was provided, therefor closing the bug report.
Michael
--
Why is it that all of the instruments seeking intelligent life in the
universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature
--- End Message ---
