From: "Jason A. Donenfeld" <Jason@zx2c4.com>
To: Oliver Freyermuth <freyermuth@physik.uni-bonn.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Windows stuck in boot after WireGuard update (switch to WireGuardNT?)
Date: Thu, 23 Sep 2021 18:21:44 -0600 [thread overview]
Message-ID: <CAHmME9ojB6wt13NyoZhuGm0KHq1eJ2oyvurUGA8vwUkHtxTsuQ@mail.gmail.com> (raw)
In-Reply-To: <ddf37ac0-0d04-ad84-73c7-b334655c066c@physik.uni-bonn.de>
Hi Oliver,
On Wed, Sep 22, 2021 at 8:02 AM Oliver Freyermuth
<freyermuth@physik.uni-bonn.de> wrote:
> I tried to boot one of the machines with boot/startup logging (I'm not sure this is the correct English translation, it is one of the options next to safe mode in the WinRE),
> and ntbootlog.txt ended during network driver loading.
If you're able to supply the ntbootlog.txt and any other logs on the
system (setupapi log, wireguard log, event logs, and so on), that
would be much appreciated. I'm still a bit puzzled about this report
and I'd like to get to the bottom of it.
Jason
--
Jason A. Donenfeld
Deep Space Explorer
fr: +33 6 51 90 82 66
us: +1 513 476 1200
next prev parent reply other threads:[~2021-09-24 0:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-22 10:09 Oliver Freyermuth
[not found] ` <CAHmME9pgz6PiXdFqcRw90EafHK-Jq9RfcgLUZaJ1ARrtdnjG0w@mail.gmail.com>
2021-09-22 14:02 ` Oliver Freyermuth
2021-09-22 18:57 ` Jason A. Donenfeld
2021-09-22 19:36 ` Joshua Sjoding
2021-09-24 0:21 ` Jason A. Donenfeld [this message]
2021-09-24 7:24 ` Oliver Freyermuth
2021-09-24 6:14 ` Jason A. Donenfeld
2021-09-24 17:48 ` Jason A. Donenfeld
2021-09-24 17:53 ` Joshua Sjoding
2021-09-24 17:57 ` Oliver Freyermuth
2021-09-24 19:59 ` Jason A. Donenfeld
2021-09-24 20:15 ` Arlo Clauser
2021-09-24 20:17 ` John-Paul Andreini
2021-10-14 5:56 ` Jason A. Donenfeld
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=CAHmME9ojB6wt13NyoZhuGm0KHq1eJ2oyvurUGA8vwUkHtxTsuQ@mail.gmail.com \
--to=jason@zx2c4.com \
--cc=freyermuth@physik.uni-bonn.de \
--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).