From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: k@vodka.home.kg
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] mips32 crash
Date: Mon, 7 Nov 2016 11:26:43 +0100 [thread overview]
Message-ID: <CAHmME9rm1dYZGsOZ1bfZnzZt2LXohgM=7oFmLrH6=faJPJd8cQ@mail.gmail.com> (raw)
In-Reply-To: <7365258.20161107095446@vodka.home.kg>
Hey k,
Excellent work!
My MIPS VM is still alive. :)
On Mon, Nov 7, 2016 at 7:54 AM, <k@vodka.home.kg> wrote:
> After 10 hours of testing it crashed but another way.
> I did mistake. It did not shutdown arm<>mips connection. It was almost
> idle but still on.
Do you mean to indicate that this crash is the result of the same
issue as before? Or of a different one?
> <4>[56173.377275] Unhandled kernel unaligned access[#1]:
> <4>[56173.377970] [<80241948>] add_interrupt_randomness+0xa8/0x208
Either memory corruption resulted in add_interrupt_randomness getting
a bad pointer from irq_randomness, which was unaligned, or there's
more sinister misgivings in Linux itself... Let's just assume the
former, rather than the latter.
Jason
prev parent reply other threads:[~2016-11-07 10:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 7:02 k
2016-11-06 8:07 ` k
2016-11-06 10:18 ` Jason A. Donenfeld
2016-11-06 10:20 ` Jason A. Donenfeld
2016-11-06 10:55 ` Jason A. Donenfeld
2016-11-06 11:20 ` Jason A. Donenfeld
2016-11-06 12:16 ` Jason A. Donenfeld
2016-11-06 12:22 ` Jason A. Donenfeld
2016-11-07 2:06 ` Jason A. Donenfeld
2016-11-07 8:37 ` Baptiste Jonglez
2016-11-07 10:22 ` Jason A. Donenfeld
2016-11-07 10:02 ` k
2016-11-07 10:30 ` Jason A. Donenfeld
2016-11-09 9:56 ` k
[not found] ` <7365258.20161107095446@vodka.home.kg>
2016-11-07 10:26 ` Jason A. Donenfeld [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAHmME9rm1dYZGsOZ1bfZnzZt2LXohgM=7oFmLrH6=faJPJd8cQ@mail.gmail.com' \
--to=jason@zx2c4.com \
--cc=k@vodka.home.kg \
--cc=wireguard@lists.zx2c4.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;
as well as URLs for NNTP newsgroup(s).