Weird crash causes computer to shut off

I’ve been having a very weird crash while uses ardour for a couple of version now. When I click the export button my computer just instantly shuts off and restarts. I thought that it is possibly my CPU overheating but I’ve not been able to replicate this by doing any other intense processing other than Ardour export. Does anybody have any ideas about how I could diagnose this or test the heat theory with another piece of software?

At the moment I can still export by routing the master our to another stereo track and recording it but this is not ideal.

more info like which OS you are using may help.

Im doubtfull that it is an overheating cpu if other intensive programs dont cause the same issue.

First thing to check is what your CPU temp is at to begin with before any crashes, this will give you an indication on how well your CPU is being cooled to begin with.

At idle, my cpu on both cores are around 20C.

You can type “sensors” in a terminal to get a reading of your cpu.

If its not installed then look for lmsensors i think its called.

But i dont think its an overheating issue, sounds more like hardware instability that could be caused by other issues. A bad power supply can cause this. having unstable voltage rails can cause wierd crashes.

Hi,

Are you using any sort of ALSA to JACK bridge? (ie Cadence on KXStudio). Supposedly it causes crashes if there is any ALSA i/o when Ardour3 is exporting, however to my knowledge those crashes aren’t severe machine killers like yours. I have also had a few versions of Ardour3 go kaboom when setting up the first Export but it then seems to work OK once the settings are established.

the closest i get to that is in Mixbus, when the session takes more than around 35% of DSP - Exporting makes Jackd go nuts, Mixbus stops responding and i have to kill both Mixbus and Jackd, however Qjackctl is not affected.

It is pretty disapointing since that makes me bounce Mix buses to remix them after i’ve De-activated all other tracks and plugins to get Mixbus to take only around 20% of DSP, other than exporting, i get no problems Mixbus runs up to 80-90% DSP no problem… just won’t export.

the alsa jack bridge on my kx studio causes export to freeze, but it doesnt cause any instability any where else, it just causes export to sit ther doing nothing. i can still click cancel and try again. It only works if i disable the alsa jack bridge.

Ill need to mention that to falktx and see if he can work out why its causing problems.

I’m using Ubuntu 13.04 with qjackctl and 3.8.0-30-lowlatency kernel. No ALSA to JACK bridge that I know of.

My CPU at the moment idles at about 50°C with an ambient room temperature of around 19°C, I think I need to redo the thermal paste from what I’ve read about removing and refitting the heatsink. I tested my heat theory using Handbrake to convert a video file. All 8 threads running at 100% and the cores hit almost 100°C (I’m told this is about where throttling hits in) but the computer did not turn off.

I’ve had a look at the system log files but I can’t really see anything that I expect would be causing it. Are there any Ardour specific log files that would be good to view?

50C is a big problem,

Id sort out your thermal issues first.

It could also be something in your system causing load on your system all the time, like a rogue program or something not behaving properly eating CPU cycles.

But even still my CPU under 100% load when rendering video files never excepps 40c

Check your heatsink isnt blocked with dust, check your fan is working properly. Are you overclocking?

My cpu is only an athlon 64 dual core running at 2ghz so for that the stock heatsink and fan that comes with the cpu cools it fine, but more powerfull cpus with more cores i dont think the oem heatsinks and fans may cope aswell. it may be a good idea to upgrade it to cool better.

Also if your running a high performance system make sure that you have good airflow through the case coming in from the front and being exhausted through the back. I also have a fan on the side of my case which draws are in ontop of the CPU section.

Another quick thing you could check is to try 12.04 on a Live DVD or USB stick incase 13.04 is causing odd problems. 13.04 os bleeding edge and not as stable and also 12.04 is LTS

Ok, I’ve applied the new thermal paste and the computer now runs at about 35-40°C and tops off about 49°C while doing intensive stuff so that seems much better. However, the first time I tried to bounce a project after that the computer just halted and was not responding so I did a hard reset. The next time bouncing down it got about half way and just shut off like before, so I think it is not being caused by heat.
My other thoughts were whether the memory is causing it? I ran a memtest a little while ago for a few hours and it did not show any errors though.
After looking at the logs either side of the crash, my only other thought is that maybe it is something to do with my USB audio card disconnecting or something. My JACK has a horrible habiting of just quitting every now and then without any warning.
Here is kernel.log:
Sep 13 12:02:17 christie-desktop kernel: [ 6.596288] ath: Country alpha2 being used: 00
Sep 13 12:02:17 christie-desktop kernel: [ 6.596289] ath: Regpair used: 0x60
Sep 13 12:02:17 christie-desktop kernel: [ 6.600271] ieee80211 phy0: Atheros AR9271 Rev:1
Sep 13 12:02:17 christie-desktop kernel: [ 6.806204] scsi 12:0:0:0: Direct-Access WD My Book 1140 1016 PQ: 0 ANSI: 6
Sep 13 12:02:17 christie-desktop kernel: [ 6.806958] scsi 12:0:0:1: Enclosure WD SES Device 1016 PQ: 0 ANSI: 6
Sep 13 12:02:17 christie-desktop kernel: [ 6.807620] sd 12:0:0:0: Attached scsi generic sg5 type 0
Sep 13 12:02:17 christie-desktop kernel: [ 6.807699] scsi 12:0:0:1: Attached scsi generic sg6 type 13
Sep 13 12:02:17 christie-desktop kernel: [ 6.807791] sd 12:0:0:0: [sdd] 3906963456 512-byte logical blocks: (2.00 TB/1.81 TiB)
Sep 13 12:02:17 christie-desktop kernel: [ 6.808382] sd 12:0:0:0: [sdd] Write Protect is off
Sep 13 12:02:17 christie-desktop kernel: [ 6.808386] sd 12:0:0:0: [sdd] Mode Sense: 47 00 10 08
Sep 13 12:02:17 christie-desktop kernel: [ 6.809053] sd 12:0:0:0: [sdd] No Caching mode page present
Sep 13 12:02:17 christie-desktop kernel: [ 6.809056] sd 12:0:0:0: [sdd] Assuming drive cache: write through
Sep 13 12:02:17 christie-desktop kernel: [ 6.810479] sd 12:0:0:0: [sdd] No Caching mode page present
Sep 13 12:02:17 christie-desktop kernel: [ 6.810481] sd 12:0:0:0: [sdd] Assuming drive cache: write through
Sep 13 12:02:17 christie-desktop kernel: [ 7.241994] sdd: sdd1
Sep 13 12:02:17 christie-desktop kernel: [ 7.245986] sd 12:0:0:0: [sdd] No Caching mode page present
Sep 13 12:02:17 christie-desktop kernel: [ 7.245991] sd 12:0:0:0: [sdd] Assuming drive cache: write through
Sep 13 12:02:17 christie-desktop kernel: [ 7.245995] sd 12:0:0:0: [sdd] Attached SCSI disk
Sep 13 12:02:17 christie-desktop kernel: [ 7.254401] ses 12:0:0:1: Attached Enclosure device
Sep 13 12:02:17 christie-desktop kernel: [ 7.971018] EXT4-fs (sdd1): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 12:02:17 christie-desktop kernel: [ 27.737304] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Sep 13 12:02:17 christie-desktop kernel: [ 27.807557] ppdev: user-space parallel port driver
Sep 13 12:02:17 christie-desktop kernel: [ 27.814616] type=1400 audit(1379070137.503:5): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-uccsconfigure/uccsconfigure-session-wrapper" pid=1281 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.814866] type=1400 audit(1379070137.504:6): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-uccsconfigure/uccsconfigure-session-wrapper//chromium_browser" pid=1281 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.815235] type=1400 audit(1379070137.504:7): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper" pid=1280 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.815530] type=1400 audit(1379070137.504:8): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/x86_64-linux-gnu/lightdm-remote-session-freerdp/freerdp-session-wrapper//chromium_browser" pid=1280 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.817208] type=1400 audit(1379070137.506:9): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/cups/backend/cups-pdf" pid=1287 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.817362] type=1400 audit(1379070137.506:10): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper" pid=1279 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.817451] type=1400 audit(1379070137.506:11): apparmor=“STATUS” operation=“profile_load” name="/usr/sbin/tcpdump" pid=1289 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.817567] type=1400 audit(1379070137.506:12): apparmor=“STATUS” operation=“profile_load” name="/usr/sbin/cupsd" pid=1287 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.817735] type=1400 audit(1379070137.506:13): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/lightdm/lightdm/lightdm-guest-session-wrapper//chromium_browser" pid=1279 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.818157] type=1400 audit(1379070137.507:14): apparmor=“STATUS” operation=“profile_load” name="/usr/lib/telepathy/mission-control-5" pid=1285 comm=“apparmor_parser”
Sep 13 12:02:17 christie-desktop kernel: [ 27.961673] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
Sep 13 12:02:17 christie-desktop kernel: [ 27.962098] IPv6: ADDRCONF(NETDEV_UP): wlan2: link is not ready
Sep 13 12:02:17 christie-desktop kernel: [ 27.967352] sky2 0000:05:00.0 eth2: enabling interface
Sep 13 12:02:17 christie-desktop kernel: [ 27.967417] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 13 12:02:17 christie-desktop kernel: [ 27.967920] IPv6: ADDRCONF(NETDEV_UP): eth2: link is not ready
Sep 13 12:02:20 christie-desktop kernel: [ 30.716492] wlan2: authenticate with 00:1e:2a:6e:0e:a8
Sep 13 12:02:20 christie-desktop kernel: [ 30.812625] wlan2: send auth to 00:1e:2a:6e:0e:a8 (try 1/3)
Sep 13 12:02:20 christie-desktop kernel: [ 30.814550] wlan2: authenticated
Sep 13 12:02:20 christie-desktop kernel: [ 30.814781] ath9k_htc 1-5:1.0 wlan2: disabling HT/VHT due to WEP/TKIP use
Sep 13 12:02:20 christie-desktop kernel: [ 30.814785] ath9k_htc 1-5:1.0 wlan2: disabling HT as WMM/QoS is not supported by the AP
Sep 13 12:02:20 christie-desktop kernel: [ 30.814788] ath9k_htc 1-5:1.0 wlan2: disabling VHT as WMM/QoS is not supported by the AP
Sep 13 12:02:20 christie-desktop kernel: [ 30.815670] wlan2: associate with 00:1e:2a:6e:0e:a8 (try 1/3)
Sep 13 12:02:20 christie-desktop kernel: [ 30.818316] wlan2: RX AssocResp from 00:1e:2a:6e:0e:a8 (capab=0x431 status=0 aid=4)
Sep 13 12:02:20 christie-desktop kernel: [ 30.822421] IPv6: ADDRCONF(NETDEV_CHANGE): wlan2: link becomes ready
Sep 13 12:02:20 christie-desktop kernel: [ 30.822484] wlan2: associated
Sep 13 12:02:21 christie-desktop kernel: [ 32.048371] usb 1-6: USB request error -18: unknown error
Sep 13 12:02:21 christie-desktop kernel: [ 32.059942] usb 1-6: USB request error -18: unknown error
Sep 13 12:06:41 christie-desktop kernel: imklog 5.8.11, log source = /proc/kmsg started.
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Initializing cgroup subsys cpuset
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Initializing cgroup subsys cpu
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Linux version 3.8.0-30-lowlatency (buildd@lamiak) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #22-Ubuntu SMP PREEMPT Mon Aug 26 22:31:40 UTC 2013 (Ubuntu 3.8.0-30.22-lowlatency 3.8.13.6)
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-lowlatency root=UUID=6fcf2847-cda2-4bd1-b63a-c6d3128d321e ro quiet splash
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] KERNEL supported cpus:
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Intel GenuineIntel
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] AMD AuthenticAMD
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Centaur CentaurHauls
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000e4c00-0x00000000000fffff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bf77ffff] usable
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bf780000-0x00000000bf797fff] ACPI data
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bf798000-0x00000000bf7dbfff] ACPI NVS
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bf7dc000-0x00000000bfffffff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000001bfffffff] usable
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] NX (Execute Disable) protection: active
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] SMBIOS 2.5 present.
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] DMI: System manufacturer System Product Name/P6X58D-E, BIOS 0303 05/25/2010
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] e820: update [mem 0x00000000-0x0000ffff] usable ==> reserved

and sys.log:
Sep 13 12:02:23 christie-desktop NetworkManager[1224]: dnsmasq not available on the bus, can’t update servers.
Sep 13 12:02:23 christie-desktop NetworkManager[1224]: [1379070143.245975] [nm-dns-dnsmasq.c:402] update(): dnsmasq owner not found on bus: Could not get owner of name ‘org.freedesktop.NetworkManager.dnsmasq’: no such name
Sep 13 12:02:23 christie-desktop NetworkManager[1224]: DNS: plugin dnsmasq update failed
Sep 13 12:02:23 christie-desktop NetworkManager[1224]: Writing DNS information to /sbin/resolvconf
Sep 13 12:02:23 christie-desktop dnsmasq[2306]: started, version 2.65 cache disabled
Sep 13 12:02:23 christie-desktop dnsmasq[2306]: compile time options: IPv6 GNU-getopt DBus i18n IDN DHCP DHCPv6 no-Lua TFTP conntrack
Sep 13 12:02:23 christie-desktop dnsmasq[2306]: DBus support enabled: connected to system bus
Sep 13 12:02:23 christie-desktop dnsmasq[2306]: warning: no upstream servers configured
Sep 13 12:02:23 christie-desktop NetworkManager[1224]: Activation (wlan2) successful, device activated.
Sep 13 12:02:23 christie-desktop dbus[1163]: [system] Activating service name=‘org.freedesktop.nm_dispatcher’ (using servicehelper)
Sep 13 12:02:23 christie-desktop NetworkManager[1224]: dnsmasq appeared on DBus: :1.29
Sep 13 12:02:23 christie-desktop NetworkManager[1224]: Writing DNS information to /sbin/resolvconf
Sep 13 12:02:23 christie-desktop dnsmasq[2306]: setting upstream servers from DBus
Sep 13 12:02:23 christie-desktop dnsmasq[2306]: using nameserver 192.168.1.1#53
Sep 13 12:02:23 christie-desktop dbus[1163]: [system] Successfully activated service ‘org.freedesktop.nm_dispatcher’
Sep 13 12:02:23 christie-desktop dbus[1163]: [system] Activating service name=‘org.freedesktop.UDisks2’ (using servicehelper)
Sep 13 12:02:23 christie-desktop udisksd[2473]: udisks daemon version 2.1.0 starting
Sep 13 12:02:23 christie-desktop dbus[1163]: [system] Successfully activated service ‘org.freedesktop.UDisks2’
Sep 13 12:02:23 christie-desktop udisksd[2473]: Acquired the name org.freedesktop.UDisks2 on the system message bus
Sep 13 12:02:23 christie-desktop dbus[1163]: [system] Activating service name=‘org.freedesktop.UDisks’ (using servicehelper)
Sep 13 12:02:23 christie-desktop dbus[1163]: [system] Successfully activated service ‘org.freedesktop.UDisks’
Sep 13 12:02:29 christie-desktop ntpdate[2455]: step time server 91.189.89.199 offset -0.651190 sec
Sep 13 12:02:38 christie-desktop gnome-session[1943]: WARNING: Could not launch application ‘gnome-user-share.desktop’: Unable to start application: Failed to execute child process “/usr/lib/gnome-user-share/gnome-user-share” (No such file or directory)
Sep 13 12:02:40 christie-desktop NetworkManager[1224]: (wlan2): IP6 addrconf timed out or failed.
Sep 13 12:02:40 christie-desktop NetworkManager[1224]: Activation (wlan2) Stage 4 of 5 (IPv6 Configure Timeout) scheduled…
Sep 13 12:02:40 christie-desktop NetworkManager[1224]: Activation (wlan2) Stage 4 of 5 (IPv6 Configure Timeout) started…
Sep 13 12:02:40 christie-desktop NetworkManager[1224]: Activation (wlan2) Stage 4 of 5 (IPv6 Configure Timeout) complete.
Sep 13 12:06:41 christie-desktop kernel: imklog 5.8.11, log source = /proc/kmsg started.
Sep 13 12:06:41 christie-desktop rsyslogd: [origin software=“rsyslogd” swVersion=“5.8.11” x-pid=“1203” x-info=“http://www.rsyslog.com”] start
Sep 13 12:06:41 christie-desktop rsyslogd: rsyslogd’s groupid changed to 103
Sep 13 12:06:41 christie-desktop rsyslogd: rsyslogd’s userid changed to 101
Sep 13 12:06:41 christie-desktop rsyslogd-2039: Could not open output pipe ‘/dev/xconsole’ [try http://www.rsyslog.com/e/2039 ]
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Initializing cgroup subsys cpuset
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Initializing cgroup subsys cpu
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Linux version 3.8.0-30-lowlatency (buildd@lamiak) (gcc version 4.7.3 (Ubuntu/Linaro 4.7.3-1ubuntu1) ) #22-Ubuntu SMP PREEMPT Mon Aug 26 22:31:40 UTC 2013 (Ubuntu 3.8.0-30.22-lowlatency 3.8.13.6)
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-3.8.0-30-lowlatency root=UUID=6fcf2847-cda2-4bd1-b63a-c6d3128d321e ro quiet splash
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] KERNEL supported cpus:
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Intel GenuineIntel
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] AMD AuthenticAMD
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] Centaur CentaurHauls
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] e820: BIOS-provided physical RAM map:
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009fbff] usable
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x000000000009fc00-0x000000000009ffff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000000e4c00-0x00000000000fffff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000bf77ffff] usable
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bf780000-0x00000000bf797fff] ACPI data
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bf798000-0x00000000bf7dbfff] ACPI NVS
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000bf7dc000-0x00000000bfffffff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x00000001bfffffff] usable
Sep 13 12:06:41 christie-desktop kernel: [ 0.000000] NX (Execute Disable) protection: active

I noticed the Sep 13 12:02:21 christie-desktop kernel: [ 32.048371] usb 1-6: USB request error -18: unknown error just before it restarts but I don’t know how to find out which device that is.

lsusb

It’s bus 1 device 6

I don’t think it’s related to the problem though, it doesn’t look serious. And it doesn’t happen quite “just before it restarts” either, your sys.log shows the computer’s still working 20 seconds later. I’d probably take a closer look at wlan2 myself, although I don’t think that’s the problem either. It looks like you’ll have a lot of fun chasing this one.

I don’t see any device attached at bus 1 device 6. Could it be that the order of devices changed when it rebooted?
Here is the output of lsusb:

Bus 001 Device 002: ID 0846:9030 NetGear, Inc. WNA1100 Wireless-N 150 [Atheros AR9271]
Bus 001 Device 003: ID 0582:007d Roland Corp. EDIROL UA-101
Bus 008 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 010 Device 002: ID 1058:1140 Western Digital Technologies, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub

No, obviously the 1-6 doesn’t mean that. I was mistaken.

If I was you I’d put the wireless and the soundcard on different buses, BTW. In theory it doesn’t matter but, you know, just in case.

What kind of power supply do you have?

unstable voltages can sometimes cause wierd crashes like that, or not having a powerfull enough power supply

also you could try redicing your memory clock and frequency.

I wondered if it was the dirty power in the house but I have just moved house and I am still having the problem.
I’m not sure what the power supply is and because of the way it is mounted I can’t find out without taking the computer to bits. However, when I bought it I did use an online power supply calculator to make sure it was powerful enough. Maybe it’s quality has degraded over time?

I also thought that maybe it is the USB audio card causing it, so I tried bouncing using the onboard intel card and got the same issue.
As the network adapter popped up in the logs a lot, I removed that, disabled networking and tried to bounce but the same thing happened.

Would my RAM have this kind of effect? I don’t know how Ardour works, but maybe my memory can’t handle the bounce and just flops out?

At the moment, I am a bit worried that this constant untidy rebooting is going to damage my SSD

at boot where you can select the kernel you want to boot, there should also be a memtest option, it may take a while though to test all 4gb but that should tell you if there are any problems with ram, but id think it would crashes or freezes rather than just shutting off. But it could be, so test the memery.

My only other thoughts are the north bridge overheating.

I wondered if it was the dirty power in the house but I have just moved house and I am still having the problem.
I hope you didn't move just for that reason :) swapping out components in a PC / DAW to try to fix a problem is reasonable, but swapping your entire house seems a bit extreme :) !

@veda_sticks I ran a memtest for about 8 hours the other day and it said everything is fine. Should I run it for longer? I’ve heard about people running it for days.
What is the north bridge?

@linuxdsp Haha, no I was just moving back to university for the new year.

Does anybody have any other ideas? This is quite worrying as it only happens when bouncing a session in Ardour.

Does anybody know how I can recreate the load of a bounce in some other software?
So far I have found that:

  • it is not heat (I can run a video converter at 100% CPU on all cores without a problem and no throttling even)
  • It is not the memory (memtest found no faults).
  • It is not the USB soundcard (still happens on the internal soundcard when the USB one is unplugged)

The only possibility I can see is problems with voltage (how do I test this? and why would this happen only when I bounce in Ardour?)
Could this be something to do with using an SSD for my operating system? /home is on a 1tb HDD and / is on a 64GB SSD.

Im not sure how you would monitor voltages in linux, it may be possible to configure lmsensors but im not sure how. In the bios it should show you what your voltages are but thats not under load. The only other way is to buy a PSU tester. I saw one on aria.co.uk but then it may not be that.

The northbridge typically handles communications among the CPU, in some cases RAM, and PCI Express (or AGP) video cards, and the southbridge.[4][5] Some northbridges also contain integrated video controllers, also known as a Graphics and Memory Controller Hub (GMCH) in Intel systems. Because different processors and RAM require different signaling, a given northbridge will typically work with only one or two classes of CPUs and generally only one type of RAM.

There are a few chipsets that support two types of RAM (generally these are available when there is a shift to a new standard). For example, the northbridge from the Nvidia nForce2 chipset will only work with Socket A processors combined with DDR SDRAM; the Intel i875 chipset will only work with systems using Pentium 4 processors or Celeron processors that have a clock speed greater than 1.3 GHz and utilize DDR SDRAM, and the Intel i915g chipset only works with the Intel Pentium 4 and the Celeron, but it can use DDR or DDR2 memory.

Taken from wiki http://en.wikipedia.org/wiki/Northbridge_(computing)

If it overheats it can cause resets, i found pages on searching that mentioned it causing crashes during games if it overheats so it could be possible that other things could do the same.

also did you try reducing your memory clock/frequency?

Years ago i had the same thing happen but only in games, but i never figured out why until i got a new computer, but my guess is instability somewhere caused by an overheat, or hardware configuration. Try reducing the memory clock and go from there.

You could also try a fresh install, id recomend 12.04 , its a little more stable though 12.04 is still pretty new. Pure debian systems use older software for a reason. 13.04 isnt considered stable.