3) No Wifi modem running, nor any activity in its supporting software. The sshd loaded, but not handling any activity.
telnetd is a separate utility, and should be "safe" over the USB cable.
PS: Which sshd are you using on the Kindle?
Dropbear or OpenSSH?
It would be nice to know which one we are eliminating from the possible causes.
- - - -
Background - -
"SegFaults" is something reported because of user-land code.
*) It is not reported in Kernel code space, that is a "Kernel Oops".
*) User-land code **should not**,
**ever**, cause a "Kernel Oops". (In theory, but it can happen in practice although very rare.)
As a data point -
With the older version of USBnetworking (it was recently rebuilt);
Using TelNet, not either of the sshd deamons;
Device displaying its screensaver, but **not** in cpu suspend;
In "airplane mode" (Wifi modem powered down);
TelNet in "command mode" and connection up to Kindle;
TelNet deamon not responding (normal at this point);
I can cause a "Kernel Reboot" by causing the local telnet instance to query the remote deamon for its status.
Translation: Clearly an error in Amazon's kernel build and/or patches.
It is very hard to get the Linux network stack to crash in an un-modified kernel that is properly built.
Ref: Hawhill's posts - -
At this point in the testing -
Start checking on the warranty term of your Kpw -
it may be going back for replacement.
In fact, it probably is going back for replacement.
My guess at this point is very close to Hawhill's -
Either RAM failures or failures related to the watchdog timer(s).