On Fri, 17 Jun 2016 22:11:22 -0700
David A. wrote:
> On Fri, 17 Jun 2016 20:03:26 -0300, Nenhum_de_Nos
> wrote:
>
> >I think I got one of those out-of-nowhere-dead net6501. It was fine, then
> >one reboot and never again it booted. No serial, no
On Jun 18, 2016, at 9:13 AM, Jed Clear wrote:
On Jun 14, 2016, at 8:50 PM, Jed Clear wrote:
> On Jun 9, 2016, at 11:01 PM, Andrew Atrens wrote:
>> On 2016-06-09 8:47 PM, Jed Clear wrote:
Thanks for the replies so far. Looks like
On Jun 14, 2016, at 8:50 PM, Jed Clear wrote:
On Jun 9, 2016, at 11:01 PM, Andrew Atrens wrote:
> On 2016-06-09 8:47 PM, Jed Clear wrote:
>>> Thanks for the replies so far. Looks like I’ll have to wait until Saturday
>>> to test further. Starting with an
On Jun 18, 2016, at 6:37 AM, Embedding Linux wrote:
> We have a bunch of net6501 boxes around here. The hardware clock suffers
> from quite high clock drift (4 to 10 secs a day, depending on the box).
>
> We are using NTP, so the soft clock is in sync (this is how we
>
This sounds very familiar. Read through the archives on overheating issues.
> On Jun 17, 2016, at 7:03 PM, Nenhum_de_Nos wrote:
>
> Hi,
>
> I think I got one of those out-of-nowhere-dead net6501. It was fine, then one
> reboot and never again it booted. No serial, no
Hello,
We have a bunch of net6501 boxes around here. The hardware clock suffers
from quite high clock drift (4 to 10 secs a day, depending on the box).
We are using NTP, so the soft clock is in sync (this is how we
discovered the hw clock drift). But when the boxes reboot, the soft
clock starts
On Fri, 17 Jun 2016 20:03:26 -0300, Nenhum_de_Nos
wrote:
>I think I got one of those out-of-nowhere-dead net6501. It was fine, then one
>reboot and never again it booted. No serial, no boot, nothing. Just Power and
>error leds are on.
It's a 98% probability that your