From: David Lang <david@lang.hm>
To: Dave Taht <dave.taht@gmail.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Fwd: [IP] To keep a Boeing Dreamliner flying, reboot once every 248 days A software bug again
Date: Mon, 4 May 2015 10:21:53 -0700 (PDT) [thread overview]
Message-ID: <alpine.DEB.2.02.1505041021120.2656@nftneq.ynat.uz> (raw)
In-Reply-To: <CAA93jw4qv_UYQEEGUiTueD0hk9bvtsBrb0ZMhdLzJkq-0HLY4g@mail.gmail.com>
[-- Attachment #1: Type: TEXT/PLAIN, Size: 1817 bytes --]
The kernel starts the clock at -some hours so that it hits a wrap-around not
that long after startup.
David Lang
On Sat, 2 May 2015, Dave Taht wrote:
> Date: Sat, 2 May 2015 09:42:07 -0700
> From: Dave Taht <dave.taht@gmail.com>
> To: "cerowrt-devel@lists.bufferbloat.net"
> <cerowrt-devel@lists.bufferbloat.net>
> Subject: [Cerowrt-devel] Fwd: [IP] To keep a Boeing Dreamliner flying,
> reboot once every 248 days A software bug again
>
> Somehow I really would like to be able to run a firmware's clock
> forward WAY faster and transparently to catch bugs like this.
>
>
> ---------- Forwarded message ----------
> From: David Farber <farber@gmail.com>
> Date: Sat, May 2, 2015 at 7:41 AM
> Subject: [IP] To keep a Boeing Dreamliner flying, reboot once every
> 248 days A software bug again
> To: ip <ip@listbox.com>
>
>
>
>> http://www.engadget.com/2015/05/01/boeing-787-dreamliner-software-bug/#continued <http://www.engadget.com/2015/05/01/boeing-787-dreamliner-software-bug/#continued>
>
>
> -------------------------------------------
> Archives: https://www.listbox.com/member/archive/247/=now
> RSS Feed: https://www.listbox.com/member/archive/rss/247/26973280-5ba6a701
> Modify Your Subscription:
> https://www.listbox.com/member/?member_id=26973280&id_secret=26973280-3b04af21
> Unsubscribe Now:
> https://www.listbox.com/unsubscribe/?member_id=26973280&id_secret=26973280-063e9b28&post_id=20150502104110:446F186A-F0D9-11E4-B42B-AC84EB0E84BC
> Powered by Listbox: http://www.listbox.com
>
>
> --
> Dave Täht
> Open Networking needs **Open Source Hardware**
>
> https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
next prev parent reply other threads:[~2015-05-04 17:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <01B01A75-21DF-4C8F-91A0-5A8EF6D6DCA7@gmail.com>
2015-05-02 16:42 ` Dave Taht
2015-05-02 22:00 ` Aaron Wood
2015-05-04 17:21 ` David Lang [this message]
2015-05-04 22:25 ` Stephen Hemminger
2015-05-04 22:29 ` Dave Taht
2015-05-04 22:29 ` David Lang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.02.1505041021120.2656@nftneq.ynat.uz \
--to=david@lang.hm \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox