[SOLVED?] Re: Horrific jackd xrun behaviour after upgrade from US 10.04 to 12.04 (Re: R: Audio issues in 10.04)
Am Tue, 18 Sep 2012 12:50:32 +0200 schrieb Thomas Orgis : > And, having read up a bit ... AHCI seems to be known to cause audio > issues I must admit that the box seems to be stable now. And it is always using AHCI enforced via kernel, regardless of BIOS setting. So that is ruled out as source of the issues. The onboard soundchip performance is still not stellar, but it is able to do 2x1024 in an apparently stable manner. What matters, is the Edirol FA-101 on Firewire and there, I can happily record with 3x64 if I really want to. My standard setup of 3x512 periods was idling around (jack and meterbridge running) over the whole day and did not experience a single xrun. I still added the rtc setting to rtirq, which didn't change anything I could perceive. I also swapped the firewire card back into its previous slot. No difference, still fine. I have to conclude that this really is about either a BIOS setting (I didn't do that much ... could disabling the internal audio chip trip things up?!) that got reset when I took out the battery or that indeed, the flaky power train triggered unstable behaviour of the machine; which would confoundedly confuse me as I would expect a more drastic failure mode. Thanks for jumping to help me about this ... I'll keep an eye on this box and report if I find a definite clue. For now, I'll try to just use it, not waste time breaking the setup again. I hope you can understand that;-) Alrighty then, Thomas signature.asc Description: PGP signature -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: Horrific jackd xrun behaviour after upgrade from US 10.04 to 12.04 (Re: R: Audio issues in 10.04)
Am Tue, 18 Sep 2012 12:37:21 +0200 schrieb Ralf Mardorf : > > Change the config to > > RTIRQ_NAME_LIST="rtc [and add anything as it was before, excepted of a > > second rtc entry]" > > PS: After editing the config stop and start might not do the job and a > reboot could be required No biggie ... I'll bear with some reboots when I get the thing stable afterwards. As for rtc being first in the list: If that is necessary (I could imagine that it is), I wonder why that is not default on UbuntuStudio (I remember the update modifying that config anyway). And, having read up a bit ... AHCI seems to be known to cause audio issues, also on Windows machines (where people endure greate pain to switch between AHCI and IDE mode ... registry hacking, or even reinstall ... I didn't have to do a thing with Linux and I don't see why I should). Is this a consensus here: If building a DAW, stay away from AHCI? Though, I think that I also had it enabled in 10.04 (on another mainboard, though); that could be a regression in the kernel behaviour, which would be depressing (I'm getting old, as I see lots of regressing with Linux in general, especially considering reliability). Alrighty then, Thomas signature.asc Description: PGP signature -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: Horrific jackd xrun behaviour after upgrade from US 10.04 to 12.04 (Re: R: Audio issues in 10.04)
> I'm short in time and can't read your email right now, so I only take a > look at the output of rtirq status. > Usually you can't do anything against the shared IRQ, however it's ok, > since firewire and snd_hda are head of the IRQs. But the first IRQ, > before firewire has to be the timer rtc0. > > Change the config to > RTIRQ_NAME_LIST="rtc [and add anything as it was before, excepted of a second > rtc entry]" PS: After editing the config stop and start might not do the job and a reboot could be required, restart usually won't work too, perhaps reset and force-reload will work. However, a reboot is safe. -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Re: Horrific jackd xrun behaviour after upgrade from US 10.04 to 12.04 (Re: R: Audio issues in 10.04)
On Tue, 2012-09-18 at 11:39 +0200, Thomas Orgis wrote: > rtirq: > > PID CLS RTPRIO NI PRI %CPU STAT COMMAND > 302 FF 90 - 130 0.6 Sirq/18-firewire > 994 FF 83 - 123 0.0 Sirq/16-snd_hda_ >84 FF 80 - 120 0.0 Sirq/17-ehci_hcd >88 FF 80 - 120 0.0 Sirq/16-ohci_hcd >86 FF 79 - 119 0.0 Sirq/19-ehci_hcd >90 FF 79 - 119 0.0 Sirq/16-ohci_hcd >99 FF 75 - 115 0.0 Sirq/1-i8042 >98 FF 74 - 114 0.1 Sirq/12-i8042 >23 FF 50 - 90 0.0 Sirq/9-acpi >73 FF 50 - 90 0.4 Sirq/22-ahci >92 FF 50 - 90 0.1 Sirq/18-ohci_hcd >94 FF 50 - 90 0.1 Sirq/18-ohci_hcd >96 FF 50 - 90 0.1 Sirq/18-ohci_hcd > 100 FF 50 - 90 0.0 Sirq/8-rtc0 > 287 FF 50 - 90 0.0 Sirq/14-pata_ati > 288 FF 50 - 90 0.0 Sirq/15-pata_ati > 295 FF 50 - 90 0.1 Sirq/18-radeon > 965 FF 50 - 90 0.0 Sirq/7-parport0 > 1212 FF 50 - 90 0.0 Sirq/42-eth3 > 3 TS - 0 19 1.0 Rksoftirqd/0 > 9 TS - 0 19 1.0 Sksoftirqd/1 >13 TS - 0 19 1.0 Sksoftirqd/2 I'm short in time and can't read your email right now, so I only take a look at the output of rtirq status. Usually you can't do anything against the shared IRQ, however it's ok, since firewire and snd_hda are head of the IRQs. But the first IRQ, before firewire has to be the timer rtc0. Change the config to RTIRQ_NAME_LIST="rtc [and add anything as it was before, excepted of a second rtc entry]" Hth, Ralf -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
Horrific jackd xrun behaviour after upgrade from US 10.04 to 12.04 (Re: R: Audio issues in 10.04)
Am Mon, 17 Sep 2012 15:30:49 +0200 schrieb Thomas Orgis : > > Please post the output of > > $ /etc/init.d/rtirq status > > Will try to get to that tonight. Well ... this is interesting. I tried AVLinux and this also showed massive xruns, with the added twist of ffado giving up on the device after some time. I then thought that maybe swapping the firewire card to another slot might help. It shared IRQ with some USB ports. I shoved it into the x16 slot (using onboard graphics). Now, would I have been properly awake at that time, I'd have thought that the generally abysmal performance cannot have something to do with the firewire card, as it also shows for internal audio and a USB card. But, perhaps it was a step towards the final goal. Thing is, the machine did not want to start after swapping the firewire card. Pulling the card out, waiting, connecting/disconnecting power ... and the machine boots again. To shorten it a bit: I must have had something funky with the power connection to the card. On the same wire branch s a SATA power adapter for the 3rd hard disk and I suspect it having had some bad insulation, causing flaky current / shorting out. That would explain the box dying on moving said branch about a bit, and some protection circuit preventing powering on again (for some time). I managed to get the thing running again after adding insulation to the supposedly faulty adapter, and what might play a part: The BIOS got reset. I'm with defaults there now. I'm leaving the box running for the day with JACK on firewire under UbuntuStudio (my partial KXStudio). During the first minutes I did not see one underrun and could record a bit with Ardour. II faintly remember that I checked internal audio, too, and it seemed to be fine. So it could be down to flaky power to the firewire card / the system at all (but how could that subtly influence the machine without killing it outright?) or, what I think is more probable, some BIOS setting. I'll check that later, if the test is successful. Anoter remote possibility would be that the machine freaks out generally when the first PCIe slot is occupied --- I'll move the firewire card back to see if that makes a change. Anyhow, here's the current interrupts (see how the one for firewire is the most populated?): CPU0 CPU1 CPU2 0:124 0 1 IO-APIC-edge timer 1:465 0 25 IO-APIC-edge i8042 7: 1 0 0 IO-APIC-edge parport0 8: 0 0 1 IO-APIC-edge rtc0 9: 0 0 0 IO-APIC-fasteoi acpi 12: 12464 19 1858 IO-APIC-edge i8042 14: 0 0 0 IO-APIC-edge pata_atiixp 15: 0 0 0 IO-APIC-edge pata_atiixp 16: 0 2838 IO-APIC-fasteoi ohci_hcd:usb3, ohci_hcd:usb4, snd_hda_intel 17: 1 1682 2187 IO-APIC-fasteoi ehci_hcd:usb1 18: 50797 4975 IO-APIC-fasteoi ohci_hcd:usb5, ohci_hcd:usb6, ohci_hcd:usb7, radeon, firewire_ohci 19: 0 5 1747 IO-APIC-fasteoi ehci_hcd:usb2 22: 1442 60 15896 IO-APIC-fasteoi ahci 42: 0 0 0 PCI-MSI-edge eth3 NMI: 0 0 0 Non-maskable interrupts LOC: 215017 224583 218795 Local timer interrupts SPU: 0 0 0 Spurious interrupts PMI: 0 0 0 Performance monitoring interrupts IWI: 0 0 0 IRQ work interrupts RES: 38575 50657 61704 Rescheduling interrupts CAL:498451613 Function call interrupts TLB:759889843 TLB shootdowns TRM: 0 0 0 Thermal event interrupts THR: 0 0 0 Threshold APIC interrupts MCE: 0 0 0 Machine check exceptions MCP: 1 1 1 Machine check polls ERR: 1 MIS: 0 rtirq: PID CLS RTPRIO NI PRI %CPU STAT COMMAND 302 FF 90 - 130 0.6 Sirq/18-firewire 994 FF 83 - 123 0.0 Sirq/16-snd_hda_ 84 FF 80 - 120 0.0 Sirq/17-ehci_hcd 88 FF 80 - 120 0.0 Sirq/16-ohci_hcd 86 FF 79 - 119 0.0 Sirq/19-ehci_hcd 90 FF 79 - 119 0.0 Sirq/16-ohci_hcd 99 FF 75 - 115 0.0 Sirq/1-i8042 98 FF 74 - 114 0.1 Sirq/12-i8042 23 FF 50 - 90 0.0 Sirq/9-acpi 73 FF 50 - 90 0.4 Sirq/22-ahci 92 FF 50 - 90 0.1 Sirq/18-ohci_hcd 94 FF 50 - 90 0.1 Sirq/18-ohci_hcd 96 FF 50 - 90 0.1 Sirq/18-ohci_hcd 100 FF 50 - 90 0.0 Sirq/8-rtc0 287 FF 50 - 90
