Re: [FFADO-user] IRQ conflict ?

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 454-5900

Filip Hoško wrote:
> Hello,
> 
> I have a M-Audio Profire 610 fw soundcard and I'm basically trying to
> get it up and running on Linux. I moved now to Fedora, things seem to
> work better here compared to my experience with Ubuntu Studio. I don't
> have a realtime kernel setup yet,

I thought that I read somewhere that the firewire driver only works 
correctly with a realtime kernel. If that's true, that could cause a lot 
of problems. I know that when I turn (off) "Realtime" in QJackCtl, 
there's all kinds of problems (I think they were lots of xruns if I 
remember correctly).

Are you aware of CCRMA? It's an audio distribution that runs "on top of" 
Fedora. It includes a working ffado, jack and QJackCtl setup; along with 
a modified Fedora Kernel with Realtime patches and any kind of audio 
related software that you may need to run correctly and smoothly.

CCRMA is built to work with Fedora, so there's no conflicts with 
Fedora... in fact, it takes care of every possible audio related concern 
there is. I spend zero time trying to get my firewire hardware working 
well. It "just works".

If interested, go to:
http://ccrma.stanford.edu/planetccrma/software/
and follow the instructions.

Hope this helped,
Rocco

> at first I'm trying to run my fw
> controller and then the card. Since now I used only a build-in Ricoh
> fw adapter in my laptop (and it didn't work at all in Ubuntu, in
> Fedora it was a bit better). So I decided to buy a cardbus card with
> Texas Instruments chipset. The only one that I could possibly get in
> my country was Belkin F5U513v. I bought it, but I still have problems.
> The card is recognized and setup by yenta, has it's irq number and
> seems to "work" (also a new /dev/fw* is created). Problem is that I
> have lots of xruns from jack (ffado errors) and after short time jack
> crashes (completely, it keeps generating error messages and has to be
> closed by force).
> I'm suspecting it could be an irq conflict that's causing this, so I'm
> asking you for some advice, since I don't know for sure.
> 
> I have jack and qjackctl from the repos, ffado is from svn trunk (up to date).
> 
> These are the "red" lines from ffado-test Discover (but Profire is discovered) -
> 
> ....
> 06927186665: Warning (ieee1394service.cpp)[ 375] initialize: Could not
> set SPLIT_TIMEOUT to min requested (1000000)
> 06927186839: Warning (ieee1394service.cpp)[ 379] initialize: Set
> SPLIT_TIMEOUT to min requested (1000000) did not succeed
> 06927206321: Warning (ieee1394service.cpp)[ 375] initialize: Could not
> set SPLIT_TIMEOUT to min requested (1000000)
> 06927206411: Warning (ieee1394service.cpp)[ 379] initialize: Set
> SPLIT_TIMEOUT to min requested (1000000) did not succeed
> .....
> 
> This from qjackctl when it crashes (well, it lasts working for maybe a
> minute and those xruns are there from the start) -
> 
> 23:59:55.475 XRUN callback (1).
> JackPosixMutex::Unlock res = 1
> JackAudioDriver::ProcessAsync: read error, skip cycle
> 00:00:00.334 XRUN callback (2).
> JackPosixMutex::Unlock res = 1
> JackAudioDriver::ProcessAsync: read error, skip cycle
> 00:00:10.565 XRUN callback (3).
> JackPosixMutex::Unlock res = 1
> JackAudioDriver::ProcessAsync: read error, skip cycle
> 
> then it crashes with this hoard of messages, that continue forever -
> 
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> JackAudioDriver::ProcessAsync: read error, skip cycle
> JackFFADODriver::ffado_driver_wait - unhandled xrun
> firewire ERR: wait status < 0! (= -1)
> ........etc
> 
> IRQ's (why is firewire_ohci there two times ?? at 5 and at 11) -
> 
> $ cat /proc/interrupts | more
>            CPU0
>   0:     522424    XT-PIC-XT        timer
>   1:       6209    XT-PIC-XT        i8042
>   2:          0    XT-PIC-XT        cascade
>   3:          4    XT-PIC-XT
>   4:          1    XT-PIC-XT        ohci_hcd:usb3
>   5:     760465    XT-PIC-XT        ehci_hcd:usb1, ohci_hcd:usb2,
> ohci_hcd:usb4, yenta, firewire_ohci, mmc0, eth0
>   7:          3    XT-PIC-XT        parport0
>   8:          0    XT-PIC-XT        rtc0
>   9:      58450    XT-PIC-XT        acpi
>  10:          4    XT-PIC-XT        nouveau
>  11:      27078    XT-PIC-XT        firewire_ohci, SiS SI7012, SiS
> SI7013 Modem, b43
>  12:      52140    XT-PIC-XT        i8042
>  14:      35244    XT-PIC-XT        pata_sis
>  15:      28610    XT-PIC-XT        pata_sis
> NMI:          0   Non-maskable interrupts
> LOC:    4039832   Local timer interrupts
> SPU:          0   Spurious interrupts
> PMI:          0   Performance monitoring interrupts
> PND:          0   Performance pending work
> RES:          0   Rescheduling interrupts
> CAL:          0   Function call interrupts
> TLB:          0   TLB shootdowns
> TRM:          0   Thermal event interrupts
> THR:          0   Threshold APIC interrupts
> MCE:          0   Machine check exceptions
> MCP:         20   Machine check polls
> ERR:          0
> MIS:          0
> 
> 
> $ dmesg | grep firewire
> firewire_ohci 0000:00:0a.1: PCI INT B -> Link[LNKC] -> GSI 11 (level,
> low) -> IRQ 11
> firewire_ohci: Added fw-ohci device 0000:00:0a.1, OHCI v1.0, 4 IR + 4
> IT contexts, quirks 0x0
> firewire_core: created device fw0: GUID 00e0180003746d51, S400
> firewire_ohci 0000:02:00.0: enabling device (0000 -> 0002)
> firewire_ohci 0000:02:00.0: PCI INT A -> Link[LNKB] -> GSI 5 (level,
> low) -> IRQ 5
> firewire_ohci 0000:02:00.0: setting latency timer to 64
> firewire_ohci: Added fw-ohci device 0000:02:00.0, OHCI v1.10, 4 IR + 8
> IT contexts, quirks 0x2
> firewire_core: created device fw1: GUID 00d0035600b23fdc, S400
> firewire_ohci: isochronous cycle inconsistent
> firewire_core: skipped bus generations, destroying all nodes
> firewire_core: rediscovered device fw1
> firewire_core: BM lock failed, making local node (ffc0) root.
> firewire_core: phy config: card 1, new root=ffc0, gap_count=5
> firewire_core: phy config: card 1, new root=ffc1, gap_count=5
> firewire_core: created device fw2: GUID 000d6c0404400002, S400, 1
> config ROM retries
> 
> 
> Thanks for any advice.
> 
> Filip
> 
> ------------------------------------------------------------------------------
> Start uncovering the many advantages of virtual appliances
> and start using them to simplify application deployment and
> accelerate your shift to cloud computing
> http://p.sf.net/sfu/novell-sfdev2dev
> _______________________________________________
> FFADO-user mailing list
> FFA...@li...
> https://lists.sourceforge.net/lists/listinfo/ffado-user