Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bluescreen while apt-get upgrading #523

Closed
prydom opened this issue Jun 14, 2016 · 9 comments
Closed

Bluescreen while apt-get upgrading #523

prydom opened this issue Jun 14, 2016 · 9 comments
Labels

Comments

@prydom
Copy link

prydom commented Jun 14, 2016

I've run into two blue screens today while apt-get upgrading my WSL instance to Xenial (which I know is currently unsupported).

Build: 14361.rs1_release.160603-1700
Surface 3 (not Pro)

Environment during both crashes:

apt-get running in tmux session, tmux attached to Xfce4-terminal (x11 server running in Windows; for better terminal support), htop running in a background tab on xfce4-terminal (Yes, I'm making good use of the new pseudo-terminal support 👍) Otherwise, fresh WSL install (with preserved home directories).

Reproduction steps:

  1. start tmux session, xfce4-terminal, htop (this was constant during both crashes I experienced)
  2. Change sources.list to Xenial
  3. apt-get update
  4. apt-get upgrade (crash happens while configuring packages; the time I was watching it, it was processing bash-completion)
  5. Blue screen :(
  6. Can recover with dpkg --configure -a after reboot

img_20160614_0126444

I do have MEMORY.DMP, it's uploaded and I'll share a link privately, if necessary.

@benhillis
Copy link
Member

benhillis commented Jun 14, 2016

We recently fixed a networking related bugcheck that could explain this, I'd like to confirm this is the same thing. Will you please email the link to: InsiderSupport@microsoft.com. Include in the subject / message to forward to the WSL team. In the body of the email mention it is for benhill and russalex. Also include the build number you're running.

@prydom
Copy link
Author

prydom commented Jun 14, 2016

I have just sent the message to that inbox.

@benhillis
Copy link
Member

I looked at it and it turns out it was actually a different issue. We've made a fix and it will be in a Windows Insider build soon. Thank you very much for reporting and sending us the dump!

@benhillis
Copy link
Member

This is fixed in build 14376, please reopen if you continue to see any bluescreens in that build.

@simasch
Copy link

simasch commented Feb 8, 2019

@benhills This is not fixed. I have the same issue in the current Windows 10 version!

@TheSquiffy
Copy link

TheSquiffy commented Feb 8, 2019

@benhillis same here on a windows 2019 server within Azure, both using Debian and Ubuntu distros.

@benhillis
Copy link
Member

It is unlikely that the bluescreens you guys are seeing are related to this nearly 3 year old thread. Would it be possible for one of you to share a memory dump with secure@microsoft.com as per our contributing instructions? Thanks!

@benhillis
Copy link
Member

@TheSquiffy - I received your dump. The bugcheck is coming from the Tcpip driver. I followed up with the team that owns the driver and they are confident that they recently fixed the issue, and the fix is in the process of being backported.

@simasch
Copy link

simasch commented Feb 14, 2019

@benhillis I found out that Microfocus Filr was the problem. After uninstalling the Filr everything works fine.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants