title: Weird (py)serial linux corruption
body: <p>I have a Linux SBC based on the Atmel SAMA5D36. I have another device hooked up to it via /dev/ttyS2 via TTL lines (115200 8N1). Using pyserial, I have a pretty high bandwidth query/response conversation with that device.</p>
  
  <p>Periodically (at least once a minute), I see a very repeatable corruption of the date coming back from the other device. If it were to respond with some text like</p>
  
  <pre><code>"123456" (ascii character values)
  </code></pre>
  
  <p>It will drop one character AND add character-0 after the following character:</p>
  
  <pre><code>"13\x00456"
  </code></pre>
  
  <p>Hopefully that's clear. It will drop the 2, the next character is as expected, a character-0 follows, and then back to normal. </p>
  
  <p>I am using kernel 4.1.10. Via some debug statements, I'm pretty sure this is not happening in my python loop, because the 0's show up in random spots of the read() buffer. I have also hooked up a scope on the incoming lines and have verified that the wire is not carrying this corruption.</p>
  
  <p>I am looking for an answer that can get me in the right direction of figuring out why this is happening. CPU load does <em>seem</em> to increase the frequency (for example, when I'm doing a bunch of DBUS traffic for a BLE adaptor attached).</p>