Attachment 128070 Details for Bug 98779 – syslog 2016-11-19 at 15:47 with the segfault

syslog 2016-11-19 at 15:47 with the segfault

messages_161119_1547 (text/plain), 5.42 KB, created by Miroslav Rovis on 2016-11-19 15:58:36 UTC

(hide)

Description:

Filename:

MIME Type:

Creator: Miroslav Rovis

Created: 2016-11-19 15:58:36 UTC

Size: 5.42 KB

patch

obsolete

>Nov 19 15:32:46 g5n sudo:     miro : TTY=pts/9 ; PWD=/home/miro ; USER=root ; COMMAND=/bin/bash
>Nov 19 15:42:14 g5n kernel: [  726.901271] virbr0: port 2(vnet0) entered blocking state
>Nov 19 15:42:14 g5n kernel: [  726.901277] virbr0: port 2(vnet0) entered disabled state
>Nov 19 15:42:14 g5n kernel: [  726.901448] device vnet0 entered promiscuous mode
>Nov 19 15:42:14 g5n kernel: [  726.906350] virbr0: port 2(vnet0) entered blocking state
>Nov 19 15:42:14 g5n kernel: [  726.906357] virbr0: port 2(vnet0) entered listening state
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet0: waiting for carrier
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet0: carrier acquired
>Nov 19 15:42:14 g5n kernel: [  726.927203] virbr1: port 2(vnet1) entered blocking state
>Nov 19 15:42:14 g5n kernel: [  726.927206] virbr1: port 2(vnet1) entered disabled state
>Nov 19 15:42:14 g5n kernel: [  726.927272] device vnet1 entered promiscuous mode
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet0: IAID 00:82:b6:32
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet0: adding address fe80::68ef:c02f:4235:3133
>Nov 19 15:42:14 g5n kernel: [  726.934238] virbr1: port 2(vnet1) entered blocking state
>Nov 19 15:42:14 g5n kernel: [  726.934241] virbr1: port 2(vnet1) entered listening state
>Nov 19 15:42:14 g5n kernel: [  726.947700] virbr0: port 2(vnet0) entered disabled state
>Nov 19 15:42:14 g5n kernel: [  726.947821] device vnet0 left promiscuous mode
>Nov 19 15:42:14 g5n kernel: [  726.947825] virbr0: port 2(vnet0) entered disabled state
>Nov 19 15:42:14 g5n kernel: [  726.954257] virbr1: port 2(vnet1) entered disabled state
>Nov 19 15:42:14 g5n kernel: [  726.954308] device vnet1 left promiscuous mode
>Nov 19 15:42:14 g5n kernel: [  726.954309] virbr1: port 2(vnet1) entered disabled state
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet1: if_up: No such device
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet1: waiting for carrier
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet1: carrier acquired
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet1: IAID 00:04:f4:d9
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet1: adding address fe80::a968:65ba:28ef:2ae4
>Nov 19 15:42:14 g5n dhcpcd[3010]: if_addaddress6: No such device
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet0: carrier lost
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet0: deleting address fe80::68ef:c02f:4235:3133
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet0: removing interface
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet1: carrier lost
>Nov 19 15:42:14 g5n dhcpcd[3010]: vnet1: removing interface
>Nov 19 15:45:09 g5n kernel: [  901.450339] virbr0: port 2(vnet0) entered blocking state
>Nov 19 15:45:09 g5n kernel: [  901.450344] virbr0: port 2(vnet0) entered disabled state
>Nov 19 15:45:09 g5n kernel: [  901.450515] device vnet0 entered promiscuous mode
>Nov 19 15:45:09 g5n kernel: [  901.456444] virbr0: port 2(vnet0) entered blocking state
>Nov 19 15:45:09 g5n kernel: [  901.456450] virbr0: port 2(vnet0) entered listening state
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet0: waiting for carrier
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet0: carrier acquired
>Nov 19 15:45:09 g5n kernel: [  901.479314] virbr1: port 2(vnet1) entered blocking state
>Nov 19 15:45:09 g5n kernel: [  901.479319] virbr1: port 2(vnet1) entered disabled state
>Nov 19 15:45:09 g5n kernel: [  901.479543] device vnet1 entered promiscuous mode
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet0: IAID 00:82:b6:32
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet0: adding address fe80::68ef:c02f:4235:3133
>Nov 19 15:45:09 g5n kernel: [  901.483363] virbr1: port 2(vnet1) entered blocking state
>Nov 19 15:45:09 g5n kernel: [  901.483365] virbr1: port 2(vnet1) entered listening state
>Nov 19 15:45:09 g5n kernel: [  901.489712] cgroup: libvirtd (3817) created nested cgroup for controller "memory" which has incomplete hierarchy support. Nested cgroups may change behavior in the future.
>Nov 19 15:45:09 g5n kernel: [  901.489714] cgroup: "memory" requires setting use_hierarchy to 1 on the root
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet1: IAID 00:04:f4:d9
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet1: carrier lost
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet1: carrier acquired
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet1: IAID 00:04:f4:d9
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet0: soliciting a DHCP lease
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet1: soliciting a DHCP lease
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet0: soliciting an IPv6 router
>Nov 19 15:45:09 g5n dhcpcd[3010]: vnet1: soliciting an IPv6 router
>Nov 19 15:45:10 g5n kernel: [  902.333514] qemu-system-x86[4707]: segfault at 20 ip 00007f07aa8efb3e sp 00007fffa9320570 error 4 in libspice-server.so.1.12.0[7f07aa89c000+15b000]
>Nov 19 15:45:10 g5n dhcpcd[3010]: vnet1: carrier lost
>Nov 19 15:45:10 g5n kernel: [  902.338748] virbr1: port 2(vnet1) entered disabled state
>Nov 19 15:45:10 g5n kernel: [  902.338893] device vnet1 left promiscuous mode
>Nov 19 15:45:10 g5n kernel: [  902.338898] virbr1: port 2(vnet1) entered disabled state
>Nov 19 15:45:10 g5n kernel: [  902.345431] virbr0: port 2(vnet0) entered disabled state
>Nov 19 15:45:10 g5n kernel: [  902.345471] device vnet0 left promiscuous mode
>Nov 19 15:45:10 g5n kernel: [  902.345473] virbr0: port 2(vnet0) entered disabled state
>Nov 19 15:45:10 g5n dhcpcd[3010]: vnet0: dhcp if_readrawpacket: Network is down
>Nov 19 15:45:10 g5n dhcpcd[3010]: vnet1: removing interface
>Nov 19 15:45:10 g5n dhcpcd[3010]: vnet0: carrier lost
>Nov 19 15:45:10 g5n dhcpcd[3010]: vnet0: deleting address fe80::68ef:c02f:4235:3133
>Nov 19 15:45:10 g5n dhcpcd[3010]: vnet0: removing interface
>Nov 19 15:46:44 g5n kernel: [  996.970993] kworker/dying (4583) used greatest stack depth: 12264 bytes left

Actions: View

Attachments on bug 98779: 128070

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.