The only thing you can really tell from this is that in the second case there
are no interrupts.

    -- Lennart

James Burton wrote:

> Updated symptoms: Sometimes plays, (usually twice) and then the interrupts
> stop coming. I assume something is not being reset that my board revision
> is sensitive to.
>
> With debugging compiled in, a successful play looks like
>
> eap: eap_halt_output
> eap: eap_halt_input
> eap: eap_halt_output
> eap: eap_halt_input
> eap_trigger_output: sc=0xc0494a00 start=0xc5399000 end=0xc53a7fc0 blksize=4384 i
> ntr=0xc012f880(0xc048f800)
> eap_trigger_output: DAC2_ADDR=0x21000, DAC2_SIZE=0x3bef
> eap_trigger_output: set ICSC = 0x00000000
> eap_intr: ICSS=0xa0080ec2, SIC=0xff900608
> eap_intr: ICSS=0xa0080ec2, SIC=0xff900608
> ...
>
> And an unsuccessful play looks like
>
> eap: eap_halt_output
> eap: eap_halt_output
> eap: eap_halt_input
> eap: eap_halt_output
> eap: eap_halt_input
> eap: eap_halt_output
> eap: eap_halt_input
> eap_trigger_output: sc=0xc0494a00 start=0xc5399000 end=0xc53a7fc0 blksize=4384 i
> ntr=0xc012f880(0xc048f800)
> eap_trigger_output: DAC2_ADDR=0x21000, DAC2_SIZE=0x3bef
> eap_trigger_output: set ICSC = 0x00000000
>
> <at this point I press ctrl-C & wait lots>
>
> audio_sleep: woke up st=35
> eap: eap_halt_output
> eap: eap_halt_output
> eap: eap_halt_input
>
> Does this mean anything to anybody, I'm a complete beginner at kernel
> hacking?
>
> Thanks,
> James
>
> ---
> James Burton (james@jmsh.net)           "My smile is stuck, I cannot go back to
>                                         your frownland." - Capt. BH.