[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

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

Postby Digital Larry » Sat Sep 14, 2019 3:30 pm

ixni -Fx reports:

Code: Select all

gary@ub-studio:~$ inxi -Fx
System:    Host: ub-studio Kernel: 5.0.0-27-lowlatency x86_64 bits: 64 compiler: gcc v: 8.3.0
           Desktop: Xfce 4.13.3 Distro: Ubuntu 19.04 (Disco Dingo)
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <root required>
           Mobo: Gigabyte model: F2A88XN-WIFI v: x.x serial: <root required> UEFI: American Megatrends v: F4
           date: 05/28/2014
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 charge: 100% (should be ignored)
           status: Discharging
CPU:       Topology: Quad Core model: AMD Athlon X4 740 bits: 64 type: MCP arch: Piledriver rev: 1
           L2 cache: 2048 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 25553
           Speed: 2858 MHz min/max: 1400/3200 MHz Core speeds (MHz): 1: 2996 2: 2787 3: 2264 4: 2540
Graphics:  Device-1: NVIDIA GT218 [GeForce 8400 GS Rev. 3] vendor: eVga.com. driver: nvidia v: 340.107
           bus ID: 01:00.0
           Display: x11 server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: GeForce 8400GS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107 direct render: Yes
Audio:     Device-1: NVIDIA High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel
           bus ID: 01:00.1
           Device-2: BEHRINGER type: USB driver: snd-usb-audio bus ID: 6-1:2
           Device-3: N/A type: USB driver: snd-usb-audio bus ID: 3-3:4
           Sound Server: ALSA v: k5.0.0-27-lowlatency
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169
           v: kernel port: d000 bus ID: 02:00.0
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: fc:aa:14:75:29:04
           Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: d000 bus ID: 04:00.0
           IF: wlp4s0 state: down mac: 80:19:34:32:20:a3
Drives:    Local Storage: total: 931.51 GiB used: 13.64 GiB (1.5%)
           ID-1: /dev/sda vendor: Hitachi model: HUA721010KLA330 size: 931.51 GiB
Partition: ID-1: / size: 914.46 GiB used: 13.64 GiB (1.5%) fs: ext4 dev: /dev/dm-0
           ID-2: swap-1 size: 976.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1
Sensors:   System Temperatures: cpu: 41.1 C mobo: N/A gpu: nvidia temp: 89 C
           Fan Speeds (RPM): N/A
Info:      Processes: 217 Uptime: 14h 13m Memory: 7.72 GiB used: 960.7 MiB (12.1%) Init: systemd runlevel: 5
           Compilers: gcc: 8.3.0 Shell: bash v: 5.0.3 inxi: 3.0.33
gary@ub-studio:~$


I can try to disable Wi-Fi and Bluetooth in BIOS as I don't use those and why bother with all that.

gsmartcontrol report attached.
gsmartcontrol-report.png


Also attached is the journalctl output filtered on rtkit and upervising, so I can see the trends in threads. The max I see being supervised is 22, so it's not simply a case where "going over 10" caused a problem. Yet in a number of cases, you can see a sudden transition back to 1. If you look at the time stamps, there's often a 5 or 6 minute gap there which I'm guessing is when a reboot happened. Whether this is symptom or cause, it at least begs explanation (which I don't have).
rtkit-threads.gz


A couple of you have suggested a memory test, but no specifics. I think there is an option off the GRUB menu? Is there something else you meant by that?
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 » Sat Sep 14, 2019 4:03 pm

Much as I'd love to continue, my mouse continues to be jerky/non responsive after 6 reboots both into the low latency and "regular" kernels. Now I am wondering a bit about the "regular" kernel image. When I went into "advanced options" off the GRUB menu, the only options there were ALL marked low-latency.

It's even believable I suppose that the mouse is at the core of all these issues. I have a wired mouse I can use instead temporarily, I suppose, but this exact same Logitech wireless mouse works like a champ over on the dreaded W-word OS.

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 4:44 pm

I don't think it's anything to do with the mouse, it sounds more and more like a graphics problem. That said, I don't see anything particularly weird except for the GPU temperature, is that not pretty high? If that is overheating for whatever reason then it might explain the jerky behaviour and the shutdowns.

The first thing I would do is update your nvidia driver, you have 340.107 and the latest version is 430 (or around that) so that could be the problem. I think you should be able to install it by default now but there is a ppa as well (I think ubuntu studio doesn't have the regular ubuntu repos or something?).

If it is available then purge the nvidia stuff you have and then

Code: Select all

sudo apt install nvidia-driver-430

merlyn
Established Member
Posts: 480
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 4:51 pm

Is this a dual boot machine that works with Windows?

That's evidence against a hardware problem.

I found the low latency kernel worked with Nvidia proprietary drivers -- it was only the RT kernel that was a problem.

I have seen a machine completely crash. It was because the CPU was overheating due to dust in the processor fan. It may sound low tech but it's worth checking out. :)

merlyn
Established Member
Posts: 480
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 5:03 pm

@sysrqer : He's got a GeForce 8400 GS Rev. 3. The 340 drivers are the most up to date for that card I think.

tramp
Established Member
Posts: 1413
Joined: Mon Jul 01, 2013 8:13 am

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

Postby tramp » Sat Sep 14, 2019 5:04 pm

Code: Select all

System:
  Host: box Kernel: 5.0.7-rt4 x86_64 bits: 64 compiler: gcc v: 8.3.0
  Desktop: Cinnamon 3.8.8
  Distro: siduction 18.3.0 Patience - cinnamon - (201805132102)
  base: Debian GNU/Linux buster/sid
CPU:
  Topology: Quad Core model: Intel Core i5-7400 bits: 64 type: MCP
  arch: Kaby Lake rev: 9 L2 cache: 6144 KiB
  flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 24000
  Speed: 3300 MHz min/max: 800/3001 MHz Core speeds (MHz): 1: 3300 2: 3300
  3: 3300 4: 3300
Graphics:
  Device-1: NVIDIA GP108 [GeForce GT 1030] vendor: Dell driver: nvidia
  v: 410.104 bus ID: 01:00.0
  Display: x11 server: X.Org 1.20.4 driver: nvidia
  resolution: 1920x1080~60Hz
  OpenGL: renderer: GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 410.104
  direct render: Yes


I'm using rt kernel with nvidia driver now for several month, without any issue.

But indeed I remember seen machines crashing because of dusted fans.
On the road again.

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:37 pm

merlyn wrote:@sysrqer : He's got a GeForce 8400 GS Rev. 3. The 340 drivers are the most up to date for that card I think.

Oh ok, I didn't check. I have a crappy integrated one and use the latest driver so I assumed that theirs was better/newer than mine.
I would suggest hardware as well then, if graphics/kernel is definitely ruled out. I suppose the leading question is whether this is a dual boot and works ok in another OS.

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 6:11 pm

I'm powering the system off and going to vaccuum it out.

I will see if the video card my son gave me might fit in here. It's some mid range gaming card and may be too next gen for this old box.

This is not a dual boot system. I have it on a KVM switch with a W-word box and an Ubuntu 16.04 system I use for work. Mouse works fine on both of those. I have used this Athlon box sporadically in the past 5 years with Ubuntu 14.04 and then 18.04, but in the last week it's gotten a lot more use than in most of that time.

89 C on the GPU is pretty suspect and worth pursuing.

Thanks! back later... :)

Meanwhile I set everything up on my M-word laptop and now I'm working through some workflow issues for different scenarios. I'll still be happy if I get this running on the Ubuntu (or whatever) box as file sharing with the W-word machine across the network is easier. And for some reason there's more of a feeling of accomplishment, though I have to say compiling Hydrogen on the M-word to get JACK support got me pretty satisfied with myself.

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 7:00 pm

May you live in interesting times. I do. :roll:

#1 the CPU was not terribly dusty, but
#2 the fan on the graphics card was indeed seized up. So
#3 I replaced it with a coincidentally identical card I had sitting around (except for the seized fan part).

And then I booted again into LL kernel. Mouse was smooth at login screen, then a few seconds later, frozen/jerky again.
Rebooted into second GRUB option (turns out this is LL also), mouse is OK, so here I am again.

It seems like one of those situations where there may be more than one problem and we will have to unravel the mystery one bit at a time.

I think I need to benchmark this system against some standard of stability before complicating it with trying to actually use it for something important.

The GRUB currently doesn't have a memtest86 option but I can get a USB boot thing for that.

What else should I do?

GPU temp is 56 now instead of 89, phew! :P

Code: Select all

gary@ub-studio:~$ inxi -Fx
System:    Host: ub-studio Kernel: 5.0.0-27-lowlatency x86_64 bits: 64 compiler: gcc v: 8.3.0 Desktop: Xfce 4.13.3
           Distro: Ubuntu 19.04 (Disco Dingo)
Machine:   Type: Desktop System: Gigabyte product: N/A v: N/A serial: <root required>
           Mobo: Gigabyte model: F2A88XN-WIFI v: x.x serial: <root required> UEFI: American Megatrends v: F4
           date: 05/28/2014
Battery:   Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M325 charge: 100% (should be ignored)
           status: Discharging
CPU:       Topology: Quad Core model: AMD Athlon X4 740 bits: 64 type: MCP arch: Piledriver rev: 1 L2 cache: 2048 KiB
           flags: lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm bogomips: 25552
           Speed: 3307 MHz min/max: 1400/3200 MHz Core speeds (MHz): 1: 3139 2: 3115 3: 2561 4: 3193
Graphics:  Device-1: NVIDIA GT218 [GeForce 8400 GS Rev. 3] vendor: eVga.com. driver: nvidia v: 340.107 bus ID: 01:00.0
           Display: x11 server: X.Org 1.20.4 driver: nvidia unloaded: fbdev,modesetting,nouveau,vesa
           resolution: 1920x1080~60Hz
           OpenGL: renderer: GeForce 8400GS/PCIe/SSE2 v: 3.3.0 NVIDIA 340.107 direct render: Yes
Audio:     Device-1: NVIDIA High Definition Audio vendor: eVga.com. driver: snd_hda_intel v: kernel bus ID: 01:00.1
           Sound Server: ALSA v: k5.0.0-27-lowlatency
Network:   Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Gigabyte driver: r8169 v: kernel
           port: d000 bus ID: 02:00.0
           IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: fc:aa:14:75:29:04
           Device-2: Intel Wireless 7260 driver: iwlwifi v: kernel port: d000 bus ID: 04:00.0
           IF: wlp4s0 state: down mac: 80:19:34:32:20:a3
Drives:    Local Storage: total: 931.51 GiB used: 13.72 GiB (1.5%)
           ID-1: /dev/sda vendor: Hitachi model: HUA721010KLA330 size: 931.51 GiB temp: 50 C
Partition: ID-1: / size: 914.46 GiB used: 13.71 GiB (1.5%) fs: ext4 dev: /dev/dm-0
           ID-2: swap-1 size: 976.0 MiB used: 0 KiB (0.0%) fs: swap dev: /dev/dm-1
Sensors:   System Temperatures: cpu: 17.1 C mobo: N/A gpu: nvidia temp: 56 C
           Fan Speeds (RPM): N/A
Info:      Processes: 218 Uptime: 26m Memory: 7.72 GiB used: 836.5 MiB (10.6%) Init: systemd Compilers: gcc: 8.3.0
           Shell: bash v: 5.0.3 inxi: 3.0.33
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 » Sat Sep 14, 2019 11:13 pm

Get the popcorn.

I'm running memtest86 now. It took me 3 tries to get a USB stick that worked. They were all from 2 jobs ago and that was a little weird (before I erased them). One's 512 MB USB stick. It's so cute! anyway...

My wired mouse works better than the wireless mouse. As there is some discussion of issues with Logitech Unifying receivers in the greater Ubuntu support community, I won't pester you here with that sort of thing.

I also figured you might want to hear my update from testing these apps on the M-word computer. I think I know why JACK is not enabled on Hydrogen's M-word version by default. I compiled it with JACK turned on and sync'ing that to SooperLooper is a total mess. It works as expected on Ubuntu Studio. Also, SooperLooper did crash once on the M-word, so it's not all skipping through the daisies over there.

I also have not had any reboots since changing my video card, knock on wood etc.


Return to “System Tuning and Configuration”

Who is online

Users browsing this forum: No registered users and 1 guest