[GSoD] Suspend/resume troubleshooting

[enjeck]

I renamed "Wireless Troubleshooting" to "Suspend/Resume Troubleshooting" and added more content to it.

[andrewdavidwong]

@PROTechThor: FYI, if you notice a failing Travis CI check, you can click "Details," then "View more details on Travis CI" at the bottom, then scroll all the way to the bottom of the (long) log, and it will show you what caused the failures. (I don't know why they make it so hard to find.) In this case, the relevant portion is:

The following new unknown spellings were introduced:
    +hyperthreading
    +wirele
In addition, the following suspicious spellings were eliminated:
    -suspendi
The introduced suspects in context are:
./_doc/user/troubleshooting/resume-suspend-troubleshooting.md:124:To solve the problem, disable hyperthreading in the BIOS. This [external guide](https://www.pcmag.com/news/how-to-disable-hyperthreading) explains how to disable hyperthreading. 
./_doc/user/troubleshooting/resume-suspend-troubleshooting.md:125:Since Qubes does disable hyperthreading by default (by not using secondary threads), you won't pay any performance cost.
+all_ok=false
+echo
+htmlproofer ./_site --disable-external --checks-to-ignore ImageCheck --file-ignore ./_site/video-tours/index.html --only_4xx --url-ignore /qubes-issues/
Running ["ScriptCheck", "LinkCheck"] on ["./_site"] on *.html... 
Ran on 1006 files!
- ./_site/doc/index.html
  *  internally linking to /doc/installation-troubleshooting/, which does not exist (line 331)
     <a href="/doc/installation-troubleshooting/">Installation Troubleshooting</a>
htmlproofer 3.16.0 | Error:  HTML-Proofer found 1 failure!

I can't find the instance of wirele, so I'm not sure what to make of that. hyperthreading is ok, but technically it should be hyper-threading. The real problem is the broken link. Would you mind fixing that up before we merge this?

[enjeck]

I can't find the instance of wirele, so I'm not sure what to make of that. hyperthreading is ok, but technically it should be hyper-threading. The real problem is the broken link. Would you mind fixing that up before we merge this?

@andrewdavidwong
All fixed! Thanks for mentioning. I did see the broken link, but I assumed the Installation Troubleshooting will be merged before this, and the link will eventually exist :D

[andrewdavidwong]

All fixed! Thanks for mentioning. I did see the broken link, but I assumed the Installation Troubleshooting will be merged before this, and the link will eventually exist :D

Ohh, I see. As Marek mentioned, we usually try to keep PRs independent of each other so that they can be merged in any order, or at least so that merging one doesn't cause any problems (e.g. merge conflicts) in others.

However, since you've already got all these PRs open, I would be happy to merge them in whichever order would make things easiest for you. Would that just be the order in which they were opened?

[enjeck]

However, since you've already got all these PRs open, I would be happy to merge them in whichever order would make things easiest for you. Would that just be the order in which they were opened?

Yes, in that order. If any conflicts arise, I'll resolve them somehow.

[andrewdavidwong]

@PROTechThor, ready for you to resolve merge conflicts on this one now.

[enjeck]

@andrewdavidwong

[enjeck]

@marmarek
Can you please review my latest commit?

[marmarek]

Since this solution is specific to Windows, add "Windows HVM" to the section header.