You are not logged in.

#1 2014-02-04 11:33:14

d1x
Member
From: Czech Republic
Registered: 2012-08-27
Posts: 13

OS freeze probably due to virtuoso

Hi all,

last week I installed fresh new (minimalistic) Arch installation with KDE (only base). Everything seemed fine but from time to time my PC freezes up and I'm not able to login in different tty.
Investigating the issue I found out that systemd-journald sometimes (not always) gets 100% of CPU and huge amounts of memory.
From journalctl it seems that virtuoso-t is the root of problem. Here are my last lines from journalctl

Feb 04 12:05:33 obst160 polkitd[280]: Registered Authentication Agent for unix-session:1 (system bus name :1.25 [/usr/lib/kde4/libexec/polkit-kde-authentication-agent-1], object path /org/kde/PolicyKit1/Au
Feb 04 12:05:41 obst160 kernel: virtuoso-t[913]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007f95de850ff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:05:41 obst160 systemd-coredump[950]: Process 571 (virtuoso-t) dumped core.
Feb 04 12:05:44 obst160 systemd-coredump[978]: Process 953 (virtuoso-t) dumped core.
Feb 04 12:05:48 obst160 systemd-coredump[1001]: Process 981 (virtuoso-t) dumped core.
Feb 04 12:05:51 obst160 systemd-coredump[1026]: Process 1004 (virtuoso-t) dumped core.
Feb 04 12:05:54 obst160 systemd-coredump[1048]: Process 1029 (virtuoso-t) dumped core.
Feb 04 12:05:57 obst160 systemd-coredump[1073]: Process 1051 (virtuoso-t) dumped core.
Feb 04 12:06:01 obst160 systemd-coredump[1095]: Process 1076 (virtuoso-t) dumped core.
Feb 04 12:06:04 obst160 systemd-coredump[1117]: Process 1098 (virtuoso-t) dumped core.
Feb 04 12:06:07 obst160 systemd-coredump[1139]: Process 1120 (virtuoso-t) dumped core.
Feb 04 12:06:11 obst160 systemd-coredump[1161]: Process 1142 (virtuoso-t) dumped core.
Feb 04 12:07:22 obst160 systemd[1]: Stopping Journal Service...
Feb 04 12:08:05 obst160 kernel: virtuoso-t[960]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007fe7b0808ff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:07:16 obst160 esets_daemon[347]: warning[015b0000]: Cannot write to socket: Broken pipe
Feb 04 12:07:22 obst160 dbus-daemon[227]: [system] Activating via systemd: service name='org.freedesktop.ModemManager1' unit='dbus-org.freedesktop.ModemManager1.service'
Feb 04 12:07:22 obst160 dbus-daemon[227]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.ModemManager1.service': Unit dbus-org.freedesktop.ModemManager1.service failed to load: No su
Feb 04 12:08:05 obst160 systemd-journal[159]: Journal stopped
Feb 04 12:08:05 obst160 systemd-journal[1394]: Permanent journal is using 4.0G (max 4.0G, leaving 4.0G of free 166.5G, current limit 4.0G).
Feb 04 12:08:05 obst160 kernel: virtuoso-t[999]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007fba29ef2ff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:08:05 obst160 kernel: virtuoso-t[1020]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007f07b512cff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:08:05 obst160 kernel: virtuoso-t[1042]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007f82adf84ff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:08:05 obst160 kernel: virtuoso-t[1067]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007fbb2de09ff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:08:05 obst160 kernel: virtuoso-t[1088]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007ffe9dc07ff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:08:05 obst160 kernel: virtuoso-t[1115]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007f37060e7ff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:08:05 obst160 kernel: virtuoso-t[1125]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007f7c481deff0 error 7 in virtuoso-t[400000+a1e000]
Feb 04 12:08:05 obst160 kernel: virtuoso-t[1159]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007ff3c69b4ff0 error 7 in virtuoso-t[400000+a1e000]

I also retrived the core dump via systemd-coredump but it has like 50MB and I didn't find much useful information in there.
I tried re-installing virtuoso-base but of course that didn't help.

Right now I tried to change my /etc/systemd/journald.conf to be less "destructive" to my SSD

Storage=none
SystemMaxUse=4G
ForwardToSyslog=yes
ForwardToConsole=no

I believe that this may be virtuoso issue but it is essential to KDE which I really get used to. Does anyone had similar issues or any suggestions what to try right now?
As I said it happens from time to time but it is really annoying and most often it results in "hard" restart.

Offline

#2 2014-02-07 00:47:20

amckee
Member
From: Cruise Ship Earth
Registered: 2012-02-13
Posts: 25
Website

Re: OS freeze probably due to virtuoso

You are not alone in this.

Google search for 'virtuoso segfault' and you'll see what I mean. It's not just Arch.

I wish I had more to offer. The fact that this is beyond Arch leads me to believe the solution must come from upstream. I do plan on looking into this more when I can, but for now it hasn't been a show stopper for me (it's my gaming rig - plenty of resources). I usually just killall -9 virtuoso until they stop (and stop coming back), then move on with my day. Then again, I know I don't need anything it provides so I haven't lost data.

This thread has some info though:  https://bbs.archlinux.org/viewtopic.php?id=160788
"In my case, the nepomuk database was corrupted, so virtuoso_t was exiting with error. The solution was simple: deleting the nepomuk database solved the problem."

mv .kde4/share/apps/nepomuk{,_backup}

I'll check this out later myself and post back if/when it happens.

Offline

#3 2014-02-07 15:23:49

d1x
Member
From: Czech Republic
Registered: 2012-08-27
Posts: 13

Re: OS freeze probably due to virtuoso

Good to know that I'm not alone:-) Actually this issue didn't occur at my machine for a while (actually don't know the reason). Anyway I created a post in virtuoso discussion but I'm afraid no-one is going to answer soon. I will monitor my journald from time to time.

Post in virtuoso discussion:
http://sourceforge.net/p/virtuoso/discu … it=50#9cc9

Offline

#4 2014-02-09 04:45:23

amckee
Member
From: Cruise Ship Earth
Registered: 2012-02-13
Posts: 25
Website

Re: OS freeze probably due to virtuoso

I finally had a chance, and found that I'm still getting these as well:

Feb 08 20:55:40 mo kernel: virtuoso-t[7418]: segfault at ffffffffffffffff ip 00000000007fb0fe sp 00007fc27de90030 error 7 in virtuoso-t[400000+a1e000]
Feb 08 20:55:40 mo systemd-coredump[7765]: Process 7410 (virtuoso-t) dumped core.
Feb 08 20:55:44 mo systemd-coredump[7785]: Process 7768 (virtuoso-t) dumped core.
Feb 08 20:55:47 mo systemd-coredump[7803]: Process 7788 (virtuoso-t) dumped core.
Feb 08 20:55:52 mo systemd-coredump[7823]: Process 7806 (virtuoso-t) dumped core.

I checked around and didn't see any backups of nepomuk files, so I don't think I've tried that yet. I'll do that now and see what happens.

Offline

Board footer

Powered by FluxBB