On 17/03/15 17:52, Michael Biebl wrote:
control: tags -1 moreinfo
control: tags -1 unreproducible

Am 17.03.2015 um 18:14 schrieb Robert Pumphrey:
Package: systemd
Version: 215-12
Severity: critical
Justification: breaks the whole system

Dear Maintainer,

running systemctl daemon-reload causes systemd to segfault :

root@host:~# systemctl daemon-reload

Message from syslogd@host at Mar 17 16:41:53 ...
  kernel:[  758.716467] systemd[1]: segfault at 7f8d3e4422a0 ip 
00007f8d3e4422a0 sp 00007ffd3c533458 error 15
Failed to execute operation: Connection reset by peer

I have disabled as many services as possible, but still get the error.
I have not been able to reproduce on another machine

Can you reproduce the step, how you got this crash? Did this happen once
or multiple times?

This problem happens every time I run systemctl daemon-reload on this particular machine. I have installed jessie on another machine and not been able to reproduce it, but the hardware is not the same.


I have not been able to change the settings on this machine to allow 
daemon-reload to work

Once the segfault happens, systemd not longer responsds to systemctl status
Unable to get systemd back into a state where it will respond to systemctl 
status without a reboot

This has been triggered by attempting to upgrade some packages (eg. sudo) whose 
postrm script calls systemctl --system daemon-reload

If systemd dies, it will freeze and no longer reacts to any requests. So
systemctl status etc no longer working, is expected.
You should still be able to reboot in a somewhat ordered fashion via
"reboot --force"

I will try that next time I am able to


systemd should have generated a core dump as /core.

it has


Please install systemd-dbg and gdb and then run

gdb --core=/core /lib/systemd/systemd

The type "set logging on" and run "bt full" afterwards and attach
gdb.txt to the bug report.



#0 0x00007f8d3e06779b in raise (sig=11) at ../nptl/sysdeps/unix/sysv/linux/pt-raise.c:37
        resultvar = 0
        pid = <optimized out>
#1  0x00007f8d3e4bd3d8 in ?? ()
No symbol table info available.
#2  <signal handler called>
No locals.
#3  0x00007f8d3e4422a0 in ?? ()
No symbol table info available.
#4  0x00007f8d3e4f8caa in ?? ()
No symbol table info available.
#5  0x00007f8d3e56777f in ?? ()
No symbol table info available.
#6  0x00007f8d3e55f558 in ?? ()
No symbol table info available.
#7  0x00007f8d3e4bac6b in ?? ()
No symbol table info available.
#8 0x00007f8d3dcd0b45 in __libc_start_main (main=0x7f8d3e4b6dd0, argc=1, argv=0x7ffd3c533ea8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd3c533e98)
    at libc-start.c:287
        result = <optimized out>
unwind_buf = {cancel_jmp_buf = {{jmp_buf = {0, 5361389912737802513, 140244612264611, 140725615541920, 0, 0, -5360124553165444847, -5369135033269130991}, mask_was_saved = 0}}, priv = {pad = {0x0, 0x0, 0x7ffd3c533eb8, 0x7f8d3e4971a8}, data = {prev = 0x0, cleanup = 0x0, canceltype = 1012088504}}}
        not_first_call = <optimized out>
#9  0x00007f8d3e4bb2cc in ?? ()
No symbol table info available.


--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to