Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Oliver Freyermuth <freyermuth@physik.uni-bonn.de>
To: WireGuard Team <team@wireguard.com>
Cc: wireguard@lists.zx2c4.com
Subject: Re: Windows stuck in boot after WireGuard update (switch to WireGuardNT?)
Date: Wed, 22 Sep 2021 16:02:37 +0200	[thread overview]
Message-ID: <ddf37ac0-0d04-ad84-73c7-b334655c066c@physik.uni-bonn.de> (raw)
In-Reply-To: <CAHmME9pgz6PiXdFqcRw90EafHK-Jq9RfcgLUZaJ1ARrtdnjG0w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1022 bytes --]

Hi Jason,

Am 22.09.21 um 15:56 schrieb WireGuard Team:
> Thanks for the report. Could you send a log of the hung machines and
> mention the time at which the hang happened in the log?

which log exactly do you mean, the Windows event log, parts of it, or the logs by Wireguard itself?
The problem is that the hang happens on bootup, before user login (but indeed I was not clever enough to check the WireGuard logs from before the failure).

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.

I don't have the file at hand, but could access this and the WireGuard log hopefully later this week when the affected user is back from travelling.

Cheers,
	Oliver


-- 
Oliver Freyermuth
Universität Bonn
Physikalisches Institut, Raum 1.047
Nußallee 12
53115 Bonn
--
Tel.: +49 228 73 2367
Fax:  +49 228 73 7869
--


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 5432 bytes --]

  parent reply	other threads:[~2021-09-22 14:05 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 [this message]
2021-09-22 18:57     ` Jason A. Donenfeld
2021-09-22 19:36       ` Joshua Sjoding
2021-09-24  0:21     ` Jason A. Donenfeld
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=ddf37ac0-0d04-ad84-73c7-b334655c066c@physik.uni-bonn.de \
    --to=freyermuth@physik.uni-bonn.de \
    --cc=team@wireguard.com \
    --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).