More to the point. Try running the command I gave above *AFTER* the audio already stops. That'll at least tell you where, and why it fails. After that you can investigate these reason why. Perhaps providing a fruitful google search, or at minimum giving you something to report.
On Mon, Jan 2, 2017 at 2:57 PM, William Hermans <[email protected]> wrote: > $ strace -o /path/file speaker-test > > > It'll at least tell you where it stops, and most likely why. > > On Mon, Jan 2, 2017 at 2:54 PM, John Franey <[email protected]> wrote: > >> William, >> >> Thanks. >> >> If your suggestion is that the speaker-test program itself is silencing >> the hdmi output with some driver call....I'm really doubtful. I hope you >> don't mind me saying so. For a couple of reasons, but mainly: The audio >> stops 10 minutes after boot time even if there is no audio process running >> at the time. For example, I can run speaker-test before 10min mark to >> prove audio comes out right after boot. Then turn off speaker-test before >> the 10min mark, and run it after. There is no audio. >> >> Do I understand you correctly? That is, strace speaker-test? >> >> ...or maybe I should strace another process that maybe disabling sound. >> Guessing which one is the root question anyway. >> >> >> John >> >> >> On Monday, January 2, 2017 at 3:05:14 PM UTC-5, William Hermans wrote: >>> >>> >>> >>> On Mon, Jan 2, 2017 at 12:28 PM, John Franey <[email protected]> wrote: >>> >>>> What do you think strace would show? >>>> >>>> I used strace a long time ago. Back then, it traced the system calls >>>> of an application process. What should I look for in that output? >>>> >>>> Thanks, >>>> John >>>> >>> >>> Ok so then you know what strace is then I suppose. In your case, I would >>> *imagine* strace would make things really easy to understand what is >>> happening at that 10 minute mark. Since in your shoes, I'd run everything >>> normally, but through strace. There is very likely going to be a lot of >>> output. So you'd want to output that to a file, using the -o option( dash >>> oh, as in Oscar ). Passed that I then( I would think ) becomes a matter of >>> reading the file in reverse, until you find a potential culprit. That is: >>> start of the end of the output file reading towards the beginning. >>> >>> Quite honestly, I have no idea what you should be looking for, But I >>> suspect you'll know it when you see it. But if you do not, You could paste >>> the last 10 lines of output here, or so. Then see if any one else here can >>> spot a potential problem. I think that it could be very likely you will not >>> see an exact cause, but instead see something that should give a very good >>> indication as to what the problem is. >>> >> -- >> For more options, visit http://beagleboard.org/discuss >> --- >> You received this message because you are subscribed to the Google Groups >> "BeagleBoard" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To view this discussion on the web visit https://groups.google.com/d/ms >> gid/beagleboard/49e4bbaa-0b7d-4e52-8b75-09f402c7db9d%40googlegroups.com >> <https://groups.google.com/d/msgid/beagleboard/49e4bbaa-0b7d-4e52-8b75-09f402c7db9d%40googlegroups.com?utm_medium=email&utm_source=footer> >> . >> >> For more options, visit https://groups.google.com/d/optout. >> > > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/CALHSORp5F6Ap5x51-PkOSv_-r5%3DSGN%3DA%2BTcTOZkbPC8tXiM77g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
