<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><meta http-equiv="Content-Type" content="text/html; charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 12, 2017, at 1:10 AM, Steven M. Bellovin <<a href="mailto:smb@cs.columbia.edu" class="">smb@cs.columbia.edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><span style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant-caps: normal; font-weight: normal; letter-spacing: normal; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; word-spacing: 0px; -webkit-text-stroke-width: 0px; float: none; display: inline !important;" class="">This dump is to a directly connected USB 2.0 drive. And the CPU is about 96% idle, according to 'top'.</span></div></blockquote></div><br class=""><div class="">So, I have to admit I’m still very curious to hear what is in the runtime log and what dtruss says it is actually doing. Wondering if it behaves this way when it hits a specific filesystem object, a specific amount of i/o, etc.</div><div class=""><br class=""></div><div class="">It would be interesting to also know how much i/o is going on (could be seen from activity monitor or a number of other tools) when it stalls. I’m also kind of curious if there are funky things going on with the hardware in this case (the drive, the cable, the connector) that are causing a ton of retries.</div><div class=""><br class=""></div><div class=""> — dNb</div><div class=""><br class=""></div><div class="">P.S. Excellent letter re: FCC.</div></div></body></html>