View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002100 | ardour | bugs | public | 2008-02-25 20:32 | 2020-04-19 20:12 |
| Reporter | zettberlin | Assigned To | cth103 | ||
| Priority | normal | Severity | crash | Reproducibility | random |
| Status | closed | Resolution | unable to reproduce | ||
| Product Version | SVN/2.0-ongoing | ||||
| Summary | 0002100: Ardour zombifies on region underrun | ||||
| Description | I have randomly zombifications of ardour corresponding to output as follow in the terminal: PluginWindow hidden Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkWidget::cursor-color' of type `GdkColor' from rc file value "((GString*) 0x3ca8740)" of type `GString' underrun for STZgit1 underrun for STZgit1 underrun for STZgit1 STZgit1 is a mono-track in an 96KHz session. Ardour runs on an AMD64 1GB RAM PC under 64Studio. Same has happened on a AMD64-Laptop running a different 96KHz-Session also under 64Studio. The last things: Ardour says, it was stopped because the hd was not fast enough. Jackd and qjackctl die Ardour allows to open the file-menue but after klicking save, if stops to respond to anything not even CTRL+C in the terminal does not show any results. top lists ardour2-2 as defunct. The only way to get rid of the zombie is to hit the reset-button on the computer. | ||||
| Additional Information | Feb 25. 2008 21:09 Ardour was started at 20:56 and ended zombified with the message in line 34/35: zettberlin@64studio:~$ /usr/local/bin/ardour2 Ardour/GTK 2.3 (kompiliert mit Version 3029 und GCC Version4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) ... ardour: [INFO]: Controller-Protokoll gefunden: "Generic MIDI" powermate: Opening of powermate failed - Datei oder Verzeichnis nicht gefunden ardour: [INFO]: Controller-Protokoll powermate ist nicht nutzbar ardour: [INFO]: Controller-Protokoll gefunden: "Mackie" JACK tmpdir identified as [/dev/shm] Enhanced3DNow! detected SSE2 detected Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkWidget::cursor-color' of type `GdkColor' from rc file value "((GString*) 0x1461120)" of type `GString' JACK tmpdir identified as [/dev/shm] Enhanced3DNow! detected SSE2 detected loading bindings from /home/zettberlin/.ardour2/ardour.bindings unlocking /usr/local/lib64/ardour2/ardour-2.3 Loading session /media/sda2/spareline-macbeth using snapshot erster0208master (1) cd marker ruler default to 0 Lade History von '/media/sda2/spareline-macbeth/erster0208master.history'. Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkWidget::cursor-color' of type `GdkColor' from rc file value "((GString*) 0xc7bd60)" of type `GString' Loading session /media/sda2/spareline-macbeth/ using snapshot 08-02-25T-jarZyn23 (1) cd marker ruler default to 0 Lade History von '/media/sda2/spareline-macbeth/08-02-25T-jarZyn23.history'. Gtk-Message: (for origin information, set GTK_DEBUG): failed to retrieve property `GtkTreeView::even-row-color' of type `GdkColor' from rc file value "((GString*) 0x2aaac247b4a0)" of type `GString' underrun for STH5 underrun for STH5 Jackd still showed up as working about 30 secs after Ardour stopped reacting, then it behaved as seen beginning with line 78: JACK tmpdir identified as [/dev/shm] 20:54:48.221 Startup script terminated with exit status=256. 20:54:48.222 JACK is starting... 20:54:48.223 /usr/bin/jackd -R -P84 -t2000 -u -dalsa -dhw:1 -r96000 -p512 -n2 -zs 20:54:48.230 JACK was started with PID=4764 (0x129c). jackd 0.103.0 Copyright 2001-2005 Paul Davis and others. jackd comes with ABSOLUTELY NO WARRANTY This is free software, and you are welcome to redistribute it under certain conditions; see the file COPYING for details JACK compiled with System V SHM support. loading driver .. Enhanced3DNow! detected SSE2 detected apparent rate = 96000 creating alsa driver ... hw:1|hw:1|512|2|96000|0|0|nomon|swmeter|-|32bit control device hw:1 configuring for 96000Hz, period = 512 frames, buffer = 2 periods ALSA: final selected sample format for capture: 32bit little-endian ALSA: use 2 periods for capture ALSA: final selected sample format for playback: 32bit little-endian ALSA: use 2 periods for playback Noise-shaped dithering at 16 bits 20:54:50.259 Server configuration saved to "/home/zettberlin/.jackdrc". 20:54:50.261 Statistics reset. 20:54:50.273 Client activated. 20:54:50.275 Audio connection change. 20:54:50.281 Audio connection graph change. JACK tmpdir identified as [/dev/shm] Enhanced3DNow! detected SSE2 detected **** alsa_pcm: xrun of at least 0.296 msecs 21:09:50.035 XRUN callback (1). **** alsa_pcm: xrun of at least 0.062 msecs 21:09:51.635 XRUN callback (1 skipped). 21:10:25.398 Audio connection graph change. 21:10:25.467 Audio connection graph change. subgraph starting at ardour timed out (subgraph_wait_fd=18, status = 0, state = Triggered) **** alsa_pcm: xrun of at least 1993.978 msecs 21:11:18.654 Shutdown notification. 21:11:18.656 Client deactivated. 21:11:18.658 JACK is stopping... zombified - calling shutdown handler cannot read result for request type 10 from server (Die Verbindung wurde vom Kommunikationspartner zurückgesetzt) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request typejackd watchdog: timeout - killing jackd 21:11:18.680 JACK was stopped successfully. 21:11:18.682 Post-shutdown script... 21:11:18.682 killall jackd 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server ... several 100 lines like this ... cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) 21:11:19.072 Post-shutdown script terminated with exit status=256. cannot send request type 10 to server cannot read result for request type 10 from server (Datenübergabe unterbrochen (broken pipe)) ... cannot send request type 7 to server cannot read result for request type 7 from server (Datenübergabe unterbrochen (broken pipe)) jackd: Kein Prozess abgebrochen | ||||
| Tags | No tags attached. | ||||
| Users sponsoring this issue | ||
| Sponsors List |
Total Sponsorship = US$ 20 2008-06-27 18:06: zettberlin (US$ 20) |
|
|---|---|---|
|
|
Had the same happening again today and found out something more: After the underrun the harddisk in question becomes 100% unresponsive. Every process that tries to access /dev/sda2 dies - tried this with Konqueror and Thunar. So Ardour continues running and allows "normal" operation until you try to save a file or a snapshot. One might say, could be something wrong with my system - but as I said before, I had the same type of crash on a completely different machine also... |
|
|
I have this evil on an every day basis now - any hints, what I can do about? |
|
|
Finally I think I found a workaround: I copied the session-dir to a IDE-harddisk still in the same computer. Since then I had no crash like the one abovementioned since that. Today there was another "your harddisk was to slow" message. After clicking OK the session worked whithout any trouble. So I guess it is something with the sata-drive, yet not with this actual hard disk in my workstation for I had the same nasty crash on my Notebook too. On both machines when running Ardour 2.4 on 64Studio 2.0... |
|
|
Hello; do you still have problems with this? |
|
|
I had the issue several times until I changed my mainboard. Still I do not think, that it was only a broken-hardware issue, since it happened exluselively if Ardour was running. But anyway: as of now I had no such issue with the new mainboard. |
|
|
Thanks for getting back to me. I'll have to resolve this, as we can't reproduce it and it does have the feel of a hardware problem. Feel free to re-open it if the problems resurface. |
|
|
Issue has been closed automatically, by Trigger Close Plugin. Feel free to re-open with additional information if you think the issue is not resolved. |
| Date Modified | Username | Field | Change |
|---|---|---|---|
| 2008-02-25 20:32 | zettberlin | New Issue | |
| 2008-02-26 21:14 | zettberlin | Note Added: 0004754 | |
| 2008-02-26 21:16 | zettberlin | Note Edited: 0004754 | |
| 2008-06-08 14:45 | zettberlin | Note Added: 0005003 | |
| 2008-06-08 18:48 | zettberlin | Note Edited: 0005003 | |
| 2008-06-27 18:06 | zettberlin | Sponsorship Added | zettberlin: US$ 20 |
| 2008-06-27 18:06 | zettberlin | Sponsorship Total | 0 => 20 |
| 2008-07-10 20:32 | zettberlin | Note Added: 0005105 | |
| 2009-10-23 10:09 | cth103 | Note Added: 0006854 | |
| 2009-10-23 10:09 | cth103 | Status | new => feedback |
| 2009-10-25 22:45 | zettberlin | Note Added: 0006888 | |
| 2009-10-27 11:04 | cth103 | cost | => 0.00 |
| 2009-10-27 11:04 | cth103 | Note Added: 0006897 | |
| 2009-10-27 11:04 | cth103 | Status | feedback => resolved |
| 2009-10-27 11:04 | cth103 | Resolution | open => unable to reproduce |
| 2009-10-27 11:04 | cth103 | Assigned To | => cth103 |
| 2020-04-19 20:12 | system | Note Added: 0021643 | |
| 2020-04-19 20:12 | system | Status | resolved => closed |
