------=_Part_22521_22574179.1159325035624
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

I would submit a PR for this but I have been unable to capture the contents
of the panic message; it has happened twice.  If it happens again, I will
try to have a pen and paper handy before the "crash dump megabyte countdown"
consumes the screen.  What's happening is just what the subject says;
sometimes, as I noted previously, I must prod the USB subsystem/kue driver
by hotplugging the adapter one or two times in order to get the firmware to
load properly and/or the device probed.

How does one capture the panic message aside from writing it down, anyway?
I will look into this when I have time but a suggestion from someone more
experienced than I would be helpful.

Thanks,

--Blair


P.S. What does

 /netbsd: lfs_writeinode: looping count=2

signify?

------=_Part_22521_22574179.1159325035624
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<br>I would submit a PR for this but I have been unable to capture the contents of the panic message; it has happened twice.&nbsp; If it happens again, I will try to have a pen and paper handy before the &quot;crash dump megabyte countdown&quot; consumes the screen.&nbsp; What's happening is just what the subject says; sometimes, as I noted previously, I must prod the USB subsystem/kue driver by hotplugging the adapter one or two times in order to get the firmware to load properly and/or the device probed.
<br><br>How does one capture the panic message aside from writing it down, anyway?&nbsp; I will look into this when I have time but a suggestion from someone more experienced than I would be helpful.<br><br>Thanks,<br><br>--Blair
<br><br><br>P.S. What does <br><br>&nbsp;/netbsd: lfs_writeinode: looping count=2<br><br>signify?<br>

------=_Part_22521_22574179.1159325035624--