text stringlengths 14 502 |
|---|
[1087.00 --> 1093.80] So, as of January 11th, Intel was notified that the first patch they issued for Meltdown Inspector vulnerabilities was causing random reboot issues. |
[1093.80 --> 1097.54] It was later learned that the bug was affecting Haswell and Broadwell platforms. |
[1097.54 --> 1107.36] And on January 22nd, they made a blog post advising that OEMs, cloud service providers, system manufacturers, software vendors, and end users stop the deployment of current versions of the patches, |
[1107.86 --> 1111.66] as they may introduce higher than expected reboots. |
[1112.34 --> 1115.44] And other unpredictable system behavior. |
[1116.44 --> 1119.00] So, let's jump into our... |
[1119.00 --> 1121.42] This was posted originally by Evan Air on the forum. |
[1121.52 --> 1123.26] And our next one is from Vegetable Stew. |
[1123.38 --> 1125.02] And the original article is from PC World. |
[1125.14 --> 1127.30] This is just another update on Meltdown Inspector. |
[1128.02 --> 1129.42] Let's go ahead and pull this up. |
[1130.20 --> 1130.70] Boop-a-d-boop-boop-boop-boop. |
[1130.70 --> 1135.00] Oh, actually, I remember there's no point in me going over my stuff because we covered it on the first show that we covered. |
[1135.54 --> 1136.20] Oh, okay. |
[1136.66 --> 1144.02] So, Intel's plan to fix Meltdown in silicon apparently raises more questions than it answers. |
[1144.44 --> 1149.52] So, Intel has said that they plan to deploy a hardware fix. |
[1149.96 --> 1150.12] What? |
[1150.32 --> 1157.02] So, these will be silicon-based changes to future products that directly address the Spectre and Meltdown threats. |
[1157.54 --> 1160.70] Those products will begin appearing later this year. |
[1160.70 --> 1165.78] Intel's chief executive, Brian Kruzanich, told investors, |
[1166.12 --> 1169.56] I've assigned some of the very best minds at Intel to work through this. |
[1169.56 --> 1170.50] My best people are on it. |
[1171.00 --> 1171.64] The best. |
[1171.74 --> 1172.86] I've assigned the best. |
[1172.90 --> 1173.84] They're the best people. |
[1173.84 --> 1176.28] You know what? |
[1176.40 --> 1183.10] Just because I didn't watch that particular episode of the WAN show, can you give me the TLDR of how Meltdown Inspector have affected float plane? |
[1183.10 --> 1188.96] I'm going to forget part of it, which is the technicality of exactly why this happens this way. |
[1189.12 --> 1192.00] But we use a piece of software for virtual machines. |
[1192.58 --> 1195.44] And we use a version of it that's free. |
[1195.58 --> 1197.10] And there's a version of it that's paid. |
[1197.28 --> 1200.36] I don't remember exactly the reason why we use the other one. |
[1200.48 --> 1201.76] I covered it properly last time. |
[1202.22 --> 1203.48] AJ's going to skin me alive. |
[1203.48 --> 1212.12] I believe that the reason why we had to use the paid one now is that's the only one that got the update to manage this stuff. |
[1213.98 --> 1218.06] I don't remember why we were able to use the free one before, though. |
[1218.24 --> 1220.20] I think the free one's just older versions. |
[1220.90 --> 1226.72] So if we wanted to not be super owned by Meltdown, well, yeah, I believe it's Meltdown specifically. |
[1226.86 --> 1227.44] I could be wrong, though. |
[1227.46 --> 1228.34] I forget which one is which. |
[1228.34 --> 1230.62] Then we needed to upgrade. |
[1231.02 --> 1235.76] That upgrade would have been at the cost of $900 per CPU. |
[1236.96 --> 1238.38] Like per physical CPU? |
[1238.50 --> 1239.46] Per physical CPU. |
[1241.42 --> 1243.64] So that's kind of a little bit of a unique situation. |
[1243.76 --> 1246.34] Because most people are like, oh, no, our things are vulnerable now. |
[1246.50 --> 1247.30] We have to patch. |
[1247.60 --> 1248.64] Oh, no, we patched. |
[1248.82 --> 1249.78] Performance went way down. |
[1249.86 --> 1251.36] We saw that with Fortnite, the game. |
[1253.04 --> 1258.32] Actually, if you want to look at a really, really cool rundown of how this could potentially affect, |
[1258.34 --> 1263.48] an organization, check out Fortnite's breakdown of how it impacted their servers. |
[1263.62 --> 1266.66] It was actually really, really good graphs and write-ups and stuff that they did. |
[1267.46 --> 1271.80] But, yeah, our biggest issue was like, hey, we want to not be vulnerable. |
[1273.08 --> 1276.70] So super expensive amounts of money. |
[1276.70 --> 1282.30] Now, through a lot of brain-kajiggering and planning and all this other kind of stuff. |
[1282.56 --> 1284.00] I do not want to update now, Windows. |
[1284.16 --> 1285.38] Get out of my face, please. |
[1287.62 --> 1289.78] We have a plan and everything's fine and whatnot. |
[1290.02 --> 1290.66] But, like, ugh. |
[1290.96 --> 1293.16] Pilpari says, should have just used AMD. |
[1294.66 --> 1295.04] Okay. |
[1296.14 --> 1297.38] You should breed more. |
[1300.26 --> 1301.30] There's a WAN show. |
[1301.36 --> 1301.72] Ouch! |
[1301.72 --> 1308.08] I believe it was, uh, was it just before CES? |
[1308.26 --> 1309.38] You should breed more. |
[1309.52 --> 1309.78] Ouch. |
[1310.28 --> 1310.52] Okay. |
[1310.84 --> 1314.68] Aside from just reading more, what AMD servers? |
[1316.48 --> 1318.92] That's part of the read more that I'm talking about, actually. |
[1319.18 --> 1320.18] We looked into this. |
[1320.32 --> 1322.90] We were like, hey, let's just do that. |
[1324.26 --> 1325.60] No, not a thing. |
[1325.66 --> 1326.50] What AMD servers? |
[1326.50 --> 1328.86] Yeah, we're not building our own servers, just in case anyone's wondering. |
[1328.86 --> 1331.14] How many Epics do you really think they've shipped? |
[1332.80 --> 1333.84] Most, like... |
[1333.84 --> 1334.52] Just saying. |
[1335.06 --> 1336.84] So we use OVH for floatplane. |
[1337.00 --> 1341.82] People are like Epic, which, by the way, wasn't released when we began building out floatplane's infrastructure. |
[1341.92 --> 1343.10] Okay, yeah, one, for that. |
[1343.38 --> 1346.18] Two, we're not hand-building every server that we use for floatplane. |
[1346.84 --> 1349.46] We're essentially renting servers off of OVH. |
[1349.54 --> 1352.18] Which is what most people do. |
[1352.18 --> 1354.32] That are using dedicated stuff. |
[1354.44 --> 1355.68] If they're not using dedicated... |
[1355.68 --> 1360.66] Or public cloud, but if they are using public cloud type situations, you don't get the choice anyways. |
[1360.82 --> 1361.00] Yeah. |
[1361.16 --> 1369.96] You use whatever validated setup, which, by the way, someone like OVH is going to have hardware on hand. |
[1370.02 --> 1372.56] Whether it's hard drives, SSDs... |
[1372.56 --> 1372.88] Sometimes. |
[1373.44 --> 1374.10] Motherboards, CPUs... |
[1374.10 --> 1375.46] Sometimes they're really slow at rolling things out. |
[1375.46 --> 1376.78] No, no, no, that's not what I'm talking about. |
[1377.30 --> 1379.18] No, no, they're going to have hardware on hand... |
[1379.18 --> 1379.92] Oh, yeah, yeah, yeah, yeah. |
[1379.94 --> 1382.38] For upcoming platforms. |
[1382.80 --> 1385.86] We're talking three, six, nine months in advance. |
[1386.34 --> 1392.74] If you're an important partner that's buying literally thousands upon thousands of Xeon CPUs, |
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.