[SOLVED] Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Optimize your system for ultimate performance.

Moderators: khz, MattKingUSA

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

[SOLVED] Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Fri Sep 13, 2019 7:08 pm

I'm converging on a stable configuration of SooperLooper, Hydrogen, and Ardour, Jack connections managed by Claudia. I'm using Ubuntu Studio 19.

I've had some crashes (that is, system entirely reboots in the middle of something like web browsing) in the past few days and don't know how to interpret the info in the crash logs. I'd also imagine that sometimes the things that are crashing are not nice enough to leave a note behind saying it was their fault in case we were wondering.

[spoiler alert, inxi discovered an overheating gfx card which was subsequently found to have a seized cooling fan. Once this gfx card was replaced, I have experienced no further spontaneous reboots.]

I also don't know if these log files are from those spontaneous reboots, or happened when I killed Jack while the other apps were still running. Anyone have a clue?

larry@ub-studio:/var/log$ ls -l apport.*
-rw-r----- 1 root adm 0 Sep 13 00:01 apport.log
-rw-r----- 1 root adm 1438 Sep 12 14:28 apport.log.1
-rw-r----- 1 root adm 777 Sep 10 10:37 apport.log.2.gz
-rw-r----- 1 root adm 1102 Sep 9 12:56 apport.log.3.gz
-rw-r----- 1 root adm 409 Sep 8 06:14 apport.log.4.gz
-rw-r----- 1 root adm 604 Sep 7 21:24 apport.log.5.gz
-rw-r----- 1 root adm 873 Sep 6 18:46 apport.log.6.gz


This one implicates Ardour:

Code: Select all

ERROR: apport (pid 2943) Thu Sep 12 14:27:32 2019: called for pid 2882, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 2943) Thu Sep 12 14:27:32 2019: executable: /usr/lib/ardour5/ardour-5.12.0 (command line "/usr/lib/ardour5/ardour-5.12.0")
ERROR: apport (pid 2943) Thu Sep 12 14:27:32 2019: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 2943) Thu Sep 12 14:27:32 2019: debug: session gdbus call:
ERROR: apport (pid 2943) Thu Sep 12 14:27:32 2019: apport: report /var/crash/_usr_lib_ardour5_ardour-5.12.0.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 2964) Thu Sep 12 14:28:25 2019: called for pid 2803, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 2964) Thu Sep 12 14:28:25 2019: executable: /usr/lib/ardour5/ardour-5.12.0 (command line "/usr/lib/ardour5/ardour-5.12.0")
ERROR: apport (pid 2964) Thu Sep 12 14:28:25 2019: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 2964) Thu Sep 12 14:28:25 2019: debug: session gdbus call:
ERROR: apport (pid 2964) Thu Sep 12 14:28:25 2019: apport: report /var/crash/_usr_lib_ardour5_ardour-5.12.0.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS


this one starts off with Ardour, then Xorg chimes in.

Code: Select all

ERROR: apport (pid 8942) Tue Sep 10 10:32:46 2019: called for pid 8851, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 8942) Tue Sep 10 10:32:46 2019: executable: /usr/lib/ardour5/ardour-5.12.0 (command line "/usr/lib/ardour5/ardour-5.12.0")
ERROR: apport (pid 8942) Tue Sep 10 10:32:46 2019: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 8942) Tue Sep 10 10:32:46 2019: debug: session gdbus call:
ERROR: apport (pid 8942) Tue Sep 10 10:32:46 2019: apport: report /var/crash/_usr_lib_ardour5_ardour-5.12.0.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 8963) Tue Sep 10 10:32:53 2019: called for pid 2873, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 8963) Tue Sep 10 10:32:53 2019: executable: /usr/lib/ardour5/ardour-5.12.0 (command line "/usr/lib/ardour5/ardour-5.12.0")
ERROR: apport (pid 8963) Tue Sep 10 10:32:53 2019: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 8963) Tue Sep 10 10:32:53 2019: debug: session gdbus call:
ERROR: apport (pid 8963) Tue Sep 10 10:32:53 2019: apport: report /var/crash/_usr_lib_ardour5_ardour-5.12.0.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1262) Tue Sep 10 10:37:26 2019: called for pid 1152, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1262) Tue Sep 10 10:37:26 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1262) Tue Sep 10 10:37:26 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1262) Tue Sep 10 10:37:26 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1262) Tue Sep 10 10:37:29 2019: wrote report /var/crash/_usr_lib_xorg_Xorg.0.crash
ERROR: apport (pid 1303) Tue Sep 10 10:37:30 2019: called for pid 1295, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1303) Tue Sep 10 10:37:30 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1303) Tue Sep 10 10:37:30 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1303) Tue Sep 10 10:37:30 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1303) Tue Sep 10 10:37:30 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1334) Tue Sep 10 10:37:31 2019: called for pid 1331, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1334) Tue Sep 10 10:37:31 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1334) Tue Sep 10 10:37:31 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1334) Tue Sep 10 10:37:31 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1334) Tue Sep 10 10:37:31 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1365) Tue Sep 10 10:37:32 2019: called for pid 1362, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1365) Tue Sep 10 10:37:32 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1365) Tue Sep 10 10:37:32 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1365) Tue Sep 10 10:37:32 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1365) Tue Sep 10 10:37:32 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1397) Tue Sep 10 10:37:34 2019: called for pid 1394, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1397) Tue Sep 10 10:37:34 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1397) Tue Sep 10 10:37:34 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1397) Tue Sep 10 10:37:34 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1397) Tue Sep 10 10:37:34 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1428) Tue Sep 10 10:37:35 2019: called for pid 1425, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1428) Tue Sep 10 10:37:35 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1428) Tue Sep 10 10:37:35 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1428) Tue Sep 10 10:37:35 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1428) Tue Sep 10 10:37:35 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS


Here's one with Hydrogen and Ardour and then Xorg complaining:

Code: Select all

ERROR: apport (pid 9124) Mon Sep  9 09:39:09 2019: called for pid 6265, signal 11, core limit 0, dump mode 1
ERROR: apport (pid 9124) Mon Sep  9 09:39:09 2019: executable: /usr/bin/hydrogen (command line "hydrogen -d jack")
ERROR: apport (pid 9124) Mon Sep  9 09:39:09 2019: gdbus call error: Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files

ERROR: apport (pid 9124) Mon Sep  9 09:39:09 2019: debug: session gdbus call:
ERROR: apport (pid 9124) Mon Sep  9 09:39:20 2019: wrote report /var/crash/_usr_bin_hydrogen.1000.crash
ERROR: apport (pid 9667) Mon Sep  9 09:40:26 2019: called for pid 6346, signal 6, core limit 0, dump mode 1
ERROR: apport (pid 9667) Mon Sep  9 09:40:26 2019: executable: /usr/lib/ardour5/ardour-5.12.0 (command line "/usr/lib/ardour5/ardour-5.12.0")
ERROR: apport (pid 9667) Mon Sep  9 09:40:31 2019: gdbus call error: Error connecting: Error receiving data: Connection reset by peer

ERROR: apport (pid 9667) Mon Sep  9 09:40:31 2019: debug: session gdbus call:
ERROR: apport (pid 9667) Mon Sep  9 09:40:31 2019: apport: report /var/crash/_usr_lib_ardour5_ardour-5.12.0.1000.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1236) Mon Sep  9 09:41:48 2019: called for pid 1144, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1236) Mon Sep  9 09:41:48 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1236) Mon Sep  9 09:41:48 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1236) Mon Sep  9 09:41:48 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1236) Mon Sep  9 09:41:51 2019: wrote report /var/crash/_usr_lib_xorg_Xorg.0.crash
ERROR: apport (pid 1236) Mon Sep  9 09:41:51 2019: writing core dump to /core (limit: -1)
ERROR: apport (pid 1236) Mon Sep  9 09:41:51 2019: writing core dump /core of size 18882560
ERROR: apport (pid 1282) Mon Sep  9 09:41:52 2019: called for pid 1276, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1282) Mon Sep  9 09:41:52 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1282) Mon Sep  9 09:41:52 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1282) Mon Sep  9 09:41:52 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1282) Mon Sep  9 09:41:55 2019: wrote report /var/crash/_usr_lib_xorg_Xorg.0.crash
ERROR: apport (pid 1409) Mon Sep  9 09:41:56 2019: called for pid 1369, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1409) Mon Sep  9 09:41:56 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1409) Mon Sep  9 09:41:56 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1409) Mon Sep  9 09:41:56 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1409) Mon Sep  9 09:41:56 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1502) Mon Sep  9 09:41:57 2019: called for pid 1456, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1502) Mon Sep  9 09:41:57 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1502) Mon Sep  9 09:41:57 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1502) Mon Sep  9 09:41:57 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1502) Mon Sep  9 09:41:57 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1588) Mon Sep  9 09:41:58 2019: called for pid 1551, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1588) Mon Sep  9 09:41:58 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1588) Mon Sep  9 09:41:58 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1588) Mon Sep  9 09:41:58 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1588) Mon Sep  9 09:41:58 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1652) Mon Sep  9 09:41:59 2019: called for pid 1618, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1652) Mon Sep  9 09:41:59 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1652) Mon Sep  9 09:41:59 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1652) Mon Sep  9 09:41:59 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1652) Mon Sep  9 09:41:59 2019: apport: report /var/crash/_usr_lib_xorg_Xorg.0.crash already exists and unseen, doing nothing to avoid disk usage DoS
ERROR: apport (pid 1189) Mon Sep  9 12:56:44 2019: called for pid 1102, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1189) Mon Sep  9 12:56:44 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1189) Mon Sep  9 12:56:44 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1189) Mon Sep  9 12:56:44 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1189) Mon Sep  9 12:56:44 2019: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1230) Mon Sep  9 12:56:46 2019: called for pid 1224, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1230) Mon Sep  9 12:56:46 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1230) Mon Sep  9 12:56:46 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1230) Mon Sep  9 12:56:46 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1230) Mon Sep  9 12:56:46 2019: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1261) Mon Sep  9 12:56:47 2019: called for pid 1258, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1261) Mon Sep  9 12:56:47 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1261) Mon Sep  9 12:56:47 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1261) Mon Sep  9 12:56:47 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1261) Mon Sep  9 12:56:47 2019: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1292) Mon Sep  9 12:56:48 2019: called for pid 1289, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1292) Mon Sep  9 12:56:48 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1292) Mon Sep  9 12:56:48 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1292) Mon Sep  9 12:56:48 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1292) Mon Sep  9 12:56:48 2019: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1323) Mon Sep  9 12:56:49 2019: called for pid 1320, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1323) Mon Sep  9 12:56:49 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1323) Mon Sep  9 12:56:49 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1323) Mon Sep  9 12:56:49 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1323) Mon Sep  9 12:56:49 2019: this executable already crashed 2 times, ignoring
ERROR: apport (pid 1354) Mon Sep  9 12:56:51 2019: called for pid 1351, signal 6, core limit 18446744073709551615, dump mode 1
ERROR: apport (pid 1354) Mon Sep  9 12:56:51 2019: ignoring implausibly big core limit, treating as unlimited
ERROR: apport (pid 1354) Mon Sep  9 12:56:51 2019: executable: /usr/lib/xorg/Xorg (command line "/usr/lib/xorg/Xorg -core :0 -seat seat0 -auth /var/run/lightdm/root/:0 -nolisten tcp vt7 -novtswitch")
ERROR: apport (pid 1354) Mon Sep  9 12:56:51 2019: is_closing_session(): no DBUS_SESSION_BUS_ADDRESS in environment
ERROR: apport (pid 1354) Mon Sep  9 12:56:51 2019: this executable already crashed 2 times, ignoring
Last edited by Digital Larry on Tue Sep 17, 2019 3:37 pm, edited 2 times in total.

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Fri Sep 13, 2019 7:15 pm

Just for a sanity check I started JACK then Ardour. I killed JACK and Ardour complained but stayed open. No info was written into /var/log/apport.log.

Some additional info about Ubuntu crash logs:

https://codeyarns.com/2016/08/13/how-ubuntu-dumps-core/

merlyn
Established Member
Posts: 479
Joined: Thu Oct 11, 2018 4:13 pm

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby merlyn » Fri Sep 13, 2019 8:12 pm

I would think the system rebooting is a symptom of something wrong at a lower level. The apps crashing may be caused by this more fundamental problem.

To see what the kernel was doing you can use journalctl.

Here's a link to the Arch wiki on journalctl.

https://wiki.archlinux.org/index.php/Systemd/Journal

Even though it's the Arch wiki I would think journalctl uses the same commands everywhere.

My experience has been that apps may crash, but the operating system doesn't . Even if X crashed , which it never has, I would still have several ttys I could log in on to see what had happened.

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Fri Sep 13, 2019 8:43 pm

OK, thanks for the info. I was just sitting here reading the article on journalctl and running a few commands when it rebooted again. :evil:

Here's the tail end of the previous boot (after coming back up of course).

Code: Select all

Sep 13 13:28:03 ub-studio kernel: input: Microsoft Wired Keyboard 600 System Control as /devices/pci0000:00/0000:00:12.0/usb3/3-1/3-1:1.1/0003:045E:07F8.0008/
Sep 13 13:28:03 ub-studio kernel: hid-generic 0003:045E:07F8.0008: input,hidraw1: USB HID v1.11 Device [Microsoft Wired Keyboard 600] on usb-0000:00:12.0-1/in
Sep 13 13:28:03 ub-studio mtp-probe[3745]: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-1"
Sep 13 13:28:03 ub-studio mtp-probe[3745]: bus: 3, device: 5 was not an MTP device
Sep 13 13:28:03 ub-studio systemd-logind[733]: Watching system buttons on /dev/input/event3 (Microsoft Wired Keyboard 600)
Sep 13 13:28:03 ub-studio systemd-logind[733]: Watching system buttons on /dev/input/event5 (Microsoft Wired Keyboard 600 System Control)
Sep 13 13:28:03 ub-studio systemd-logind[733]: Watching system buttons on /dev/input/event4 (Microsoft Wired Keyboard 600 Consumer Control)
Sep 13 13:28:03 ub-studio mtp-probe[3766]: checking bus 3, device 5: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-1"
Sep 13 13:28:03 ub-studio mtp-probe[3766]: bus: 3, device: 5 was not an MTP device
Sep 13 13:28:04 ub-studio kernel: usb 3-2: new full-speed USB device number 6 using ohci-pci
Sep 13 13:28:04 ub-studio kernel: usb 3-2: New USB device found, idVendor=046d, idProduct=c52b, bcdDevice=12.08
Sep 13 13:28:04 ub-studio kernel: usb 3-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Sep 13 13:28:04 ub-studio kernel: usb 3-2: Product: USB Receiver
Sep 13 13:28:04 ub-studio kernel: usb 3-2: Manufacturer: Logitech
Sep 13 13:28:04 ub-studio kernel: logitech-djreceiver 0003:046D:C52B.000B: hiddev0,hidraw2: USB HID v1.11 Device [Logitech USB Receiver] on usb-0000:00:12.0-2
Sep 13 13:28:04 ub-studio mtp-probe[3802]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-2"
Sep 13 13:28:04 ub-studio mtp-probe[3802]: bus: 3, device: 6 was not an MTP device
Sep 13 13:28:04 ub-studio mtp-probe[3806]: checking bus 3, device 6: "/sys/devices/pci0000:00/0000:00:12.0/usb3/3-2"
Sep 13 13:28:04 ub-studio mtp-probe[3806]: bus: 3, device: 6 was not an MTP device
Sep 13 13:28:04 ub-studio kernel: input: Logitech M325 as /devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.2/0003:046D:C52B.000B/0003:046D:400A.000C/input/inpu
Sep 13 13:28:04 ub-studio kernel: logitech-hidpp-device 0003:046D:400A.000C: input,hidraw3: USB HID v1.11 Mouse [Logitech M325] on usb-0000:00:12.0-2:1
Sep 13 13:28:04 ub-studio upowerd[2944]: treating change event as add on /sys/devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.2/0003:046D:C52B.000B/0003:046D:4
Sep 13 13:30:01 ub-studio CRON[3858]: pam_unix(cron:session): session opened for user root by (uid=0)
Sep 13 13:30:01 ub-studio CRON[3859]: (root) CMD ([ -x /etc/init.d/anacron ] && if [ ! -d /run/systemd/system ]; then /usr/sbin/invoke-rc.d anacron start >/de
Sep 13 13:30:01 ub-studio CRON[3858]: pam_unix(cron:session): session closed for user root
Sep 13 13:31:00 ub-studio systemd[1]: Started Run anacron jobs.
Sep 13 13:31:00 ub-studio anacron[3861]: Anacron 2.3 started on 2019-09-13
Sep 13 13:31:00 ub-studio anacron[3861]: Normal exit (0 jobs run)
Sep 13 13:31:00 ub-studio systemd[1]: anacron.service: Succeeded.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 8 threads of 5 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 8 threads of 5 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 8 threads of 5 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Successfully made thread 3913 of process 3891 owned by '1000' RT at priority 10.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 9 threads of 6 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 9 threads of 6 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Successfully made thread 3914 of process 3891 owned by '1000' RT at priority 10.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 10 threads of 6 processes of 1 users.


Here are all the errors from the previous boot:

Code: Select all

$ journalctl -p err..alert -b -1
-- Logs begin at Thu 2019-09-05 12:48:43 PDT, end at Fri 2019-09-13 13:42:03 PDT. --
Sep 13 12:20:56 ub-studio kernel: Couldn't get size: 0x800000000000000e
Sep 13 12:20:56 ub-studio kernel: MODSIGN: Couldn't get UEFI db list
Sep 13 12:20:56 ub-studio kernel: Couldn't get size: 0x800000000000000e
Sep 13 12:20:56 ub-studio kernel: Couldn't get size: 0x800000000000000e
Sep 13 12:21:01 ub-studio kernel: PKCS#7 signature not signed with a trusted key
Sep 13 12:21:03 ub-studio kernel: PKCS#7 signature not signed with a trusted key
Sep 13 12:21:34 ub-studio lightdm[1244]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or d
Sep 13 12:21:34 ub-studio lightdm[1244]: PAM adding faulty module: pam_kwallet.so
Sep 13 12:21:34 ub-studio lightdm[1244]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or
Sep 13 12:21:34 ub-studio lightdm[1244]: PAM adding faulty module: pam_kwallet5.so
Sep 13 12:21:42 ub-studio lightdm[2578]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or d
Sep 13 12:21:42 ub-studio lightdm[2578]: PAM adding faulty module: pam_kwallet.so
Sep 13 12:21:42 ub-studio lightdm[2578]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or
Sep 13 12:21:42 ub-studio lightdm[2578]: PAM adding faulty module: pam_kwallet5.so
Sep 13 12:21:45 ub-studio lightdm[2578]: gkr-pam: unable to locate daemon control file
Sep 13 12:21:53 ub-studio spice-vdagent[2906]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0


Here are all the errors from the current boot:

Code: Select all

$ journalctl -p err..alert -b 0
-- Logs begin at Thu 2019-09-05 12:48:43 PDT, end at Fri 2019-09-13 13:42:03 PDT. --
Sep 13 13:36:33 ub-studio kernel: Couldn't get size: 0x800000000000000e
Sep 13 13:36:33 ub-studio kernel: MODSIGN: Couldn't get UEFI db list
Sep 13 13:36:33 ub-studio kernel: Couldn't get size: 0x800000000000000e
Sep 13 13:36:33 ub-studio kernel: Couldn't get size: 0x800000000000000e
Sep 13 13:36:37 ub-studio kernel: PKCS#7 signature not signed with a trusted key
Sep 13 13:36:37 ub-studio kernel: PKCS#7 signature not signed with a trusted key
Sep 13 13:37:08 ub-studio lightdm[1267]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or d
Sep 13 13:37:08 ub-studio lightdm[1267]: PAM adding faulty module: pam_kwallet.so
Sep 13 13:37:08 ub-studio lightdm[1267]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or
Sep 13 13:37:08 ub-studio lightdm[1267]: PAM adding faulty module: pam_kwallet5.so
Sep 13 13:37:12 ub-studio lightdm[1334]: PAM unable to dlopen(pam_kwallet.so): /lib/security/pam_kwallet.so: cannot open shared object file: No such file or d
Sep 13 13:37:12 ub-studio lightdm[1334]: PAM adding faulty module: pam_kwallet.so
Sep 13 13:37:12 ub-studio lightdm[1334]: PAM unable to dlopen(pam_kwallet5.so): /lib/security/pam_kwallet5.so: cannot open shared object file: No such file or
Sep 13 13:37:12 ub-studio lightdm[1334]: PAM adding faulty module: pam_kwallet5.so
Sep 13 13:37:17 ub-studio lightdm[1334]: gkr-pam: unable to locate daemon control file
Sep 13 13:37:22 ub-studio spice-vdagent[1536]: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0


Nothing's really leaping out at me here.

merlyn
Established Member
Posts: 479
Joined: Thu Oct 11, 2018 4:13 pm

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby merlyn » Fri Sep 13, 2019 10:16 pm

Is that all messages? I normally run it as root, or on Ubuntu with sudo in front of it.

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Fri Sep 13, 2019 11:28 pm

Here is the list of my actual crash files, which don't seem to correlate with the random reboots.

Code: Select all

$ cat crash
total 295040
-rw-r----- 1 larry     whoopsie     44700 Sep 10 14:16 _usr_bin_autojack.1000.crash
-rw-rw-r-- 1 larry     whoopsie         0 Sep  5 13:58 _usr_bin_autojack.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  5 13:59 _usr_bin_autojack.1000.uploaded
-rw-r----- 1 larry     whoopsie   9391853 Sep  9 09:39 _usr_bin_hydrogen.1000.crash
-rw-r--r-- 1 larry     whoopsie         0 Sep  9 09:39 _usr_bin_hydrogen.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  9 09:39 _usr_bin_hydrogen.1000.uploaded
-rw-r----- 1 larry     whoopsie 244168602 Sep  7 21:04 _usr_bin_non-mixer.1000.crash
-rw-r--r-- 1 larry     whoopsie         0 Sep  7 21:04 _usr_bin_non-mixer.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  7 21:04 _usr_bin_non-mixer.1000.uploaded
-rw-r----- 1 larry     whoopsie    122568 Sep  7 21:03 _usr_bin_nsmd.1000.crash
-rw-r--r-- 1 larry     whoopsie         0 Sep  7 21:03 _usr_bin_nsmd.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  7 21:03 _usr_bin_nsmd.1000.uploaded
-rw-r----- 1 larry     whoopsie   2724573 Sep  6 17:08 _usr_bin_patchage.1000.crash
-rw-rw-r-- 1 larry     whoopsie         0 Sep  6 17:08 _usr_bin_patchage.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  6 17:08 _usr_bin_patchage.1000.uploaded
-rw-r----- 1 larry     whoopsie   4418970 Sep  7 18:37 _usr_bin_slgui.1000.crash
-rw-rw-r-- 1 larry     whoopsie         0 Sep  5 13:44 _usr_bin_slgui.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  5 13:44 _usr_bin_slgui.1000.uploaded
-rw-r----- 1 larry     whoopsie  31673275 Sep  5 13:43 _usr_bin_sooperlooper.1000.crash
-rw-rw-r-- 1 larry     whoopsie         0 Sep  5 13:43 _usr_bin_sooperlooper.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  5 13:44 _usr_bin_sooperlooper.1000.uploaded
-rw-r----- 1 larry     whoopsie   2151876 Sep  7 21:03 _usr_bin_xfce4-panel.1000.crash
-rw-r--r-- 1 larry     whoopsie         0 Sep  7 21:03 _usr_bin_xfce4-panel.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  7 21:03 _usr_bin_xfce4-panel.1000.uploaded
-rw-r----- 1 larry     whoopsie   4769062 Sep  7 21:24 _usr_lib_ardour5_ardour-5.12.0.1000.crash
-rw-r--r-- 1 larry     whoopsie         0 Sep  7 21:24 _usr_lib_ardour5_ardour-5.12.0.1000.upload
-rw------- 1 whoopsie whoopsie        37 Sep  7 21:24 _usr_lib_ardour5_ardour-5.12.0.1000.uploaded
-rw-r----- 1 root     whoopsie   2593883 Sep 10 10:37 _usr_lib_xorg_Xorg.0.crash
-rw-r--r-- 1 root     whoopsie         0 Sep  9 09:42 _usr_lib_xorg_Xorg.0.upload
-rw------- 1 whoopsie whoopsie        37 Sep  9 09:42 _usr_lib_xorg_Xorg.0.uploaded
gary@ub-studio:~$

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Fri Sep 13, 2019 11:34 pm

merlyn wrote:Is that all messages? I normally run it as root, or on Ubuntu with sudo in front of it.

I don't see that sudo makes any difference. In any case, no it's not all messages, as I have added filters to the command line.

I've attached the "full" journal for the period earlier today leading up to a spontaneous reboot. You'll notice a lot of keyboard and mouse detection, this is due to me using a KVM switch.

Code: Select all

$ sudo journalctl -b -1 > journal.txt
You do not have the required permissions to view the files attached to this post.

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Fri Sep 13, 2019 11:38 pm

Filtering on the rtkit messages, I see that the crash happens soon after the thread count hits 10.

Code: Select all

gary@ub-studio:~$ grep rtkit journal.txt
Sep 13 12:21:53 ub-studio dbus-daemon[732]: [system] Activating via systemd: service name='org.freedesktop.RealtimeKit1' unit='rtkit-daemon.service' requested by ':1.79' (uid=1000 pid=2877 comm="/usr/bin/pulseaudio --daemonize=no " label="unconfined")
Sep 13 12:21:53 ub-studio rtkit-daemon[2907]: Successfully called chroot.
Sep 13 12:21:53 ub-studio rtkit-daemon[2907]: Successfully dropped privileges.
Sep 13 12:21:53 ub-studio rtkit-daemon[2907]: Successfully limited resources.
Sep 13 12:21:53 ub-studio rtkit-daemon[2907]: Running.
Sep 13 12:21:53 ub-studio rtkit-daemon[2907]: Watchdog thread running.
Sep 13 12:21:53 ub-studio rtkit-daemon[2907]: Canary thread running.
Sep 13 12:21:53 ub-studio rtkit-daemon[2907]: Successfully made thread 2877 of process 2877 owned by '1000' high priority at nice level -11.
Sep 13 12:21:53 ub-studio rtkit-daemon[2907]: Supervising 1 threads of 1 processes of 1 users.
Sep 13 12:46:36 ub-studio rtkit-daemon[2907]: Supervising 1 threads of 1 processes of 1 users.
Sep 13 12:46:36 ub-studio rtkit-daemon[2907]: Supervising 1 threads of 1 processes of 1 users.
Sep 13 12:46:36 ub-studio rtkit-daemon[2907]: Successfully made thread 3487 of process 3473 owned by '1000' RT at priority 10.
Sep 13 12:46:36 ub-studio rtkit-daemon[2907]: Supervising 2 threads of 2 processes of 1 users.
Sep 13 12:46:41 ub-studio rtkit-daemon[2907]: Supervising 2 threads of 2 processes of 1 users.
Sep 13 12:46:41 ub-studio rtkit-daemon[2907]: Supervising 2 threads of 2 processes of 1 users.
Sep 13 12:46:41 ub-studio rtkit-daemon[2907]: Supervising 2 threads of 2 processes of 1 users.
Sep 13 12:46:41 ub-studio rtkit-daemon[2907]: Successfully made thread 3557 of process 3533 owned by '1000' RT at priority 10.
Sep 13 12:46:41 ub-studio rtkit-daemon[2907]: Supervising 3 threads of 3 processes of 1 users.
Sep 13 12:46:41 ub-studio rtkit-daemon[2907]: Supervising 3 threads of 3 processes of 1 users.
Sep 13 12:46:41 ub-studio rtkit-daemon[2907]: Successfully made thread 3558 of process 3533 owned by '1000' RT at priority 10.
Sep 13 12:46:41 ub-studio rtkit-daemon[2907]: Supervising 4 threads of 3 processes of 1 users.
Sep 13 12:46:42 ub-studio rtkit-daemon[2907]: Supervising 4 threads of 3 processes of 1 users.
Sep 13 12:46:42 ub-studio rtkit-daemon[2907]: Supervising 4 threads of 3 processes of 1 users.
Sep 13 12:46:42 ub-studio rtkit-daemon[2907]: Successfully made thread 3605 of process 3586 owned by '1000' RT at priority 10.
Sep 13 12:46:42 ub-studio rtkit-daemon[2907]: Supervising 5 threads of 4 processes of 1 users.
Sep 13 12:46:42 ub-studio rtkit-daemon[2907]: Supervising 5 threads of 4 processes of 1 users.
Sep 13 12:46:42 ub-studio rtkit-daemon[2907]: Supervising 5 threads of 4 processes of 1 users.
Sep 13 12:46:42 ub-studio rtkit-daemon[2907]: Successfully made thread 3606 of process 3586 owned by '1000' RT at priority 10.
Sep 13 12:46:42 ub-studio rtkit-daemon[2907]: Supervising 6 threads of 4 processes of 1 users.
Sep 13 12:46:43 ub-studio rtkit-daemon[2907]: Supervising 6 threads of 4 processes of 1 users.
Sep 13 12:46:43 ub-studio rtkit-daemon[2907]: Supervising 6 threads of 4 processes of 1 users.
Sep 13 12:46:43 ub-studio rtkit-daemon[2907]: Supervising 6 threads of 4 processes of 1 users.
Sep 13 12:46:43 ub-studio rtkit-daemon[2907]: Supervising 6 threads of 4 processes of 1 users.
Sep 13 12:46:43 ub-studio rtkit-daemon[2907]: Successfully made thread 3637 of process 3614 owned by '1000' RT at priority 10.
Sep 13 12:46:43 ub-studio rtkit-daemon[2907]: Supervising 7 threads of 5 processes of 1 users.
Sep 13 12:46:43 ub-studio rtkit-daemon[2907]: Successfully made thread 3638 of process 3614 owned by '1000' RT at priority 10.
Sep 13 12:46:43 ub-studio rtkit-daemon[2907]: Supervising 8 threads of 5 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 8 threads of 5 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 8 threads of 5 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 8 threads of 5 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Successfully made thread 3913 of process 3891 owned by '1000' RT at priority 10.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 9 threads of 6 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 9 threads of 6 processes of 1 users.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Successfully made thread 3914 of process 3891 owned by '1000' RT at priority 10.
Sep 13 13:33:29 ub-studio rtkit-daemon[2907]: Supervising 10 threads of 6 processes of 1 users.

User avatar
sysrqer
Established Member
Posts: 1821
Joined: Thu Nov 14, 2013 11:47 pm
Contact:

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby sysrqer » Sat Sep 14, 2019 12:00 am

Which graphics card do you have and which driver?

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Sat Sep 14, 2019 12:30 am

Happened again while I was totally rocking out on SooperLooper. Now the world will never hear THAT masterpiece (cough). USB disconnect?

Code: Select all

Sep 13 16:58:02 ub-studio upowerd[1562]: treating change event as add on /sys/devices/pci0000:00/0000:00:12.0/usb3/3-2/3-2:1.2/0003:046D:C52B.0011/0003:046D:400A.0012/power_supply/hidpp_battery_2
Sep 13 16:58:59 ub-studio dbus-daemon[1372]: [session uid=1000 pid=1372] Activating service name='org.gnome.GConf' requested by ':1.118' (uid=1000 pid=3133 comm="hydrogen " label="unconfined")
Sep 13 16:58:59 ub-studio dbus-daemon[1372]: [session uid=1000 pid=1372] Successfully activated service 'org.gnome.GConf'
Sep 13 16:59:47 ub-studio kernel: usb 6-1: USB disconnect, device number 2
Sep 13 16:59:48 ub-studio kernel: usb 6-1: new high-speed USB device number 3 using xhci_hcd
Sep 13 16:59:48 ub-studio kernel: usb 6-1: New USB device found, idVendor=1397, idProduct=0509, bcdDevice= 1.12
Sep 13 16:59:48 ub-studio kernel: usb 6-1: New USB device strings: Mfr=1, Product=3, SerialNumber=0
Sep 13 16:59:48 ub-studio kernel: usb 6-1: Product: UMC404HD 192k
Sep 13 16:59:48 ub-studio kernel: usb 6-1: Manufacturer: BEHRINGER
Sep 13 16:59:49 ub-studio mtp-probe[3174]: checking bus 6, device 3: "/sys/devices/pci0000:00/0000:00:10.0/usb6/6-1"
Sep 13 16:59:49 ub-studio mtp-probe[3174]: bus: 6, device: 3 was not an MTP device
Sep 13 16:59:49 ub-studio systemd-udevd[3166]: Process '/usr/sbin/alsactl -E HOME=/run/alsa restore 1' failed with exit code 99.
Sep 13 16:59:49 ub-studio mtp-probe[3183]: checking bus 6, device 3: "/sys/devices/pci0000:00/0000:00:10.0/usb6/6-1"
Sep 13 16:59:49 ub-studio mtp-probe[3183]: bus: 6, device: 3 was not an MTP device
Sep 13 16:59:50 ub-studio kernel: xhci_hcd 0000:00:10.0: WARN: buffer overrun event for slot 1 ep 4 on endpoint
Sep 13 16:59:50 ub-studio kernel: xhci_hcd 0000:00:10.0: WARN: buffer overrun event for slot 1 ep 4 on endpoint
Sep 13 16:59:50 ub-studio kernel: xhci_hcd 0000:00:10.0: WARN: buffer overrun event for slot 1 ep 4 on endpoint
Sep 13 16:59:50 ub-studio kernel: xhci_hcd 0000:00:10.0: WARN: buffer overrun event for slot 1 ep 4 on endpoint
Sep 13 17:10:36 ub-studio org.gna.home.a2jmidid[1372]: Cannot lock down 82280346 byte memory area (Cannot allocate memory)
Sep 13 17:10:36 ub-studio org.gna.home.a2jmidid[1372]: Jack: JackClient::SetupDriverSync driver sem in flush mode
Sep 13 17:10:36 ub-studio org.gna.home.a2jmidid[1372]: Jack: JackLinuxFutex::Connect name = jack_sem.1000_default_a2j
Sep 13 17:10:36 ub-studio org.gna.home.a2jmidid[1372]: Jack: Clock source : system clock via clock_gettime
Last edited by Digital Larry on Sat Sep 14, 2019 12:36 am, edited 1 time in total.

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Sat Sep 14, 2019 12:32 am

sysrqer wrote:Which graphics card do you have and which driver?


See attached.
You do not have the required permissions to view the files attached to this post.

merlyn
Established Member
Posts: 479
Joined: Thu Oct 11, 2018 4:13 pm

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby merlyn » Sat Sep 14, 2019 1:59 am

I had problems with Nvidia and a real time kernel. It never rebooted my machine though. The GUI hung.

If it was my machine I would definitely think this was a hardware issue. I don't see any software problem in the logs.

If you have onboard graphics available they would be worth a try.

Lots of crashes could make a mess of your filesystem. ext4 isn't designed to withstand crashing every day, let alone more than once a day. Is there a disk check and 'removing orphaned nodes' every time you boot?

So do a memory test, check the filesystem. You can't check a mounted filesystem -- it will damage it. I use a bootable USB to do a filesystem check. Also you could use gsmartcontrol to see if your hard disk is healthy.

User avatar
sysrqer
Established Member
Posts: 1821
Joined: Thu Nov 14, 2013 11:47 pm
Contact:

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby sysrqer » Sat Sep 14, 2019 5:47 am

As mentioned above, Nvidia can be problematic. It can also cause crashes if you use Jack with the Nouveau driver. So I guess it would be helpful to know some details about the kernel.

And are you sure the Nvidia driver is actually being used? Inxi -Fx will tell you, can you post that here as it will tell us that as well as the necessary kernel information. You might need to install inxi.

User avatar
Linuxmusician01
Established Member
Posts: 631
Joined: Mon Feb 23, 2015 2:38 pm
Location: Holland

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Linuxmusician01 » Sat Sep 14, 2019 11:02 am

merlyn wrote:I would think the system rebooting is a symptom of something wrong at a lower level. The apps crashing may be caused by this more fundamental problem.

Intuitively I agree. A Linux system spontaneously rebooting is pretty darn serious. Could be hardware related (broken memory) could be video driver.

@Digital Larry: the successor of Xorg is Wayland. Are you using Gnome 3 (I thought that I saw some XFCE messages flying by, so I don't think so)? A lot of distro's are using Gnome3/Wayland per default. If I were you I'd install an LTS version of Ubuntu (i.e. ver. 18) and try Mate or XFCE with Xorg for a while. I agree with the others that your videocard driver might be the culprit, but I was under the impression that we've left those stone age Linux video driver problems behind us.

With problems like this immediately after installing Linux (and the right video card driver) we at NedLinux used to advise to switch distro immediately or to check your internal memory.

Good luck in solving this very serious problem!

User avatar
Digital Larry
Established Member
Posts: 97
Joined: Thu Jan 09, 2014 5:25 am

Re: Any clue on these crash logs? Ubuntu Studio, SooperLooper, Hydrogen, Ardour

Postby Digital Larry » Sat Sep 14, 2019 1:41 pm

All right. First let me say thanks to those of you who are interested in my dilemma and trying to help. :D

I think it's interesting that in the last second of its life, the rtkit thread count suddenly went from 8 to 10 and then bye-bye. That is literally the last thing in the journalctl output. OK, rtkit is clearly involved in the low latency kernel right?

The other thing about this particular setup is the mouse behavior. At boot time the mouse might be smooth or it might be really jerky and barely move at all. Reboot a few times, it comes back to normal. Either/or. Nothing in between. I had Ubuntu 14.04 on this box for years, never saw that.

I do have a GRUB option here to boot using the regular rather than the LL kernel and will try that also, but previously (on Fedora 30) that was glitch city with Hydrogen. Apples and kumquats I realize.

I felt myself going down a frustrating rabbit hole, and so last night I started seeing if I could compile Hydrogen on my Mac so that I could use JACK the way I've been on Ubuntu. SooperLooper and Ardour (currently the other bits of my "ideal" looping rig) are also supported on macOS. I've just gotten Hydrogen compiled, JACK turned on, and sync'ing SL and Hydrogen. Bringing Ardour in.... This may or may not be any more stable than it was on Ubuntu Studio but I guess I will find out.

I actually am interested in seeing what/why I was having problems on Linux, and I am willing to do some experiments, but it will put all of us to the test because I do not want to proceed by guessing. I am also reluctant to purchase new hardware simply for this exercise. The nVidia card I have is one of those $35 cheapest-possible-video card things you get when you don't want your kid to use your computer to play games on. Also, this system has an Athlon X4 740 which is one of those ones that doesn't have internal graphics so I can't test that.

I do have an extra laptop laying around somewhere that has Fedora 24 or something on it (from my previous attempt to "go Linux" a few years back).

A little later today I will check some things out per the suggestions in this thread and we can see where to go from there.

DL


Return to “System Tuning and Configuration”

Who is online

Users browsing this forum: No registered users and 1 guest