On 12/18/2019 01:13 PM, deloptes wrote: > look in the message > Invalid write to eventfd: Bad file descriptor - could be even something > outside PA. Agreed, this is bad-Juju. "eventfd Bad file descriptor" likely means the 64-bit value contained in the eventfd has been trampled by another memory problem resulting in Undefined Behavior. It is likely an Amarok problem as the virtual address space for the process should keep Amarok walled off from the rest of the processes. That doesn't mean that PA can't be going haywire and causing the problem if Amarok and PA are communicated over the descriptor (or other parts of TDE), but my bet is Amarok is the source of the problem. Grab a strace of Amarok when the issue occurs and post that will the bug-report. That should identify exactly what is failing if it is something that is hard to reproduce. -- David C. Rankin, J.D.,P.E. --------------------------------------------------------------------- To unsubscribe, e-mail: trinity-users-unsubscribe@xxxxxxxxxxxxxxxxxxxxxxxxxx For additional commands, e-mail: trinity-users-help@xxxxxxxxxxxxxxxxxxxxxxxxxx Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
