On Mon, Jul 7, 2014 at 5:21 PM, Leonid Isaev <lis...@umail.iu.edu> wrote: > Hi, > > On Mon, Jul 07, 2014 at 03:02:47PM +0200, Tom Gundersen wrote: >> On Sun, Jul 6, 2014 at 6:43 PM, Leonid Isaev <lis...@umail.iu.edu> wrote: >> > Hi, >> > >> > Sorry for a delayed reply. >> > >> > On Thu, Jul 03, 2014 at 01:46:53PM +0200, Lennart Poettering wrote: >> >> it would be good to know what the precise error output is you get now >> >> with this new change... >> > >> > With systemd-215 udevd still complains (and segfaults) about the virtual >> > interface: >> > ------ >> > $ journalctl | grep udevd >> > Jul 06 12:21:05 hermes systemd-udevd[46]: starting version 215 >> > Jul 06 12:21:05 hermes systemd-udevd[226]: starting version 215 >> > Jul 06 12:21:06 hermes systemd-udevd[234]: renamed network interface wlan0 >> > to wlp1s0 >> > Jul 06 12:21:09 hermes systemd-udevd[226]: worker [233] terminated by >> > signal 11 (Segmentation fault) >> > Jul 06 12:21:09 hermes kernel: systemd-udevd[233]: segfault at 0 ip >> > 00007ff524a0571a sp 00007fffc8a69540 error 4 in >> > libc-2.19.so[7ff524907000+1a4000] >> > Jul 06 12:21:09 hermes systemd-udevd[226]: worker [233] failed while >> > handling '/devices/virtual/net/veth7DH07K' >> > ------ >> >> The original problem (with the error message) should be fixed now in >> git, please let me know if that is not the case. > > Great, thanks -- I'll test it as soon as I get back to my build machine. > >> >> This seems to be a different issue though. One that I am not able to >> reproduce. Could you get the backtrace for this? > > You mean the segmentation fault?
Yeah. > This is very irregular (it occurs approx. > every 3nd boot), so I'll have to chase it... Maybe the journal caught the coredump? Cheers, Tom _______________________________________________ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
