NUC7CJYH 0043 BIOS更新时出现MCE错误，无法恢复

我在这里有同样的问题。
bios也不会回复。
尽管上面的消息，Archlinux确实在没有GUI的情况下继续启动。
使用NoMachine远程访问非常有效。
在注意到nic活动指示灯随机闪烁后，我意识到显示器出现问题并成功登录。问题出在电视显示器上。
使用计算机显示器正常工作。



以下为原文

I have the same issue here. The bios won't revert back either.
 
Despite the message above Archlinux does continue to boot  without the GUI. Using NoMachine remote access works perfectly.
 
After noticing that the nic activity lights were blinking randomly, I realized that the display had an issue and successfully logged in. The problem was with a tv as display. Using a computer monitor works normally.

因此，当您使用显示器时，您看到的是GUI而不是电视？
电视的品牌和年龄是多少？
您是否尝试在BIOS中关闭HDMI CEC Control？
有时可能会对旧电视造成严重破坏。



以下为原文

So when you used a monitor you saw the GUI but not with a TV?  What brand and how old is the TV? Did you try turning off HDMI CEC Control in the BIOS? Sometimes with can cause havoc with older TVs.

大家好，请允许我对此进行更深入的研究。
一旦我有更新，我会通知你.Antony S.



以下为原文

Hello, everyone!

Allow me to perform a deeper research into this. Once I have an update I will let you know.


Antony S.

是的，显示器工作，电视不起作用。
关闭cec控制意味着什么都没有用。
电视的年龄介于5到10岁之间。



以下为原文

Yes, monitor works, TV doesn't work.
 
Turning off cec control meant nothing worked.
 
TV are between five and 10 years old.

嗨azuresong，
有一个较新的BIOS版本，你可能想尝试：版本44，下载BIOS更新[JYGLKCPX.86A]
现在，在BIOS 43上有一个更新的CPU微码（安全建议-00115），我不知道这个更新是否可能产生MCE错误，你有可能将微码从4.17.11更新到4.18.5吗？
您使用的Linux发行版是什么？
BIOS更新到BIOS 43后，您是否立即收到此错误？
另一方面，当尝试降级BIOS（我不建议）你尝试使用[F7]进程吗？
您尝试了什么过程以及什么文件以及何时收到错误。
问候，
罗尼G.



以下为原文

Hi azuresong,
 
There is a newer BIOS release out there that you may want to try: version 44, Download BIOS Update [JYGLKCPX.86A] 
Now, on BIOS 43 there is an Updated CPU Microcode (Security Advisory-00115), I dont know if this update may be generating the MCE errors, is it possible that you update your microcode from 4.17.11 to 4.18.5? What Linux distribution are you using? Did you get this error right away after the BIOS was updated to BIOS 43?
On the other hand, when trying to downgrade BIOS (which I dont recommend) Did you try with the [F7] process? What process did you try and what file and when do you get the error.
 
Regards,
Ronny G

嗨rguevara，
我更新到版本44，并且4.17.11和4.18.5的mce错误保持不变，我仍然无法恢复到以前的任何版本。
[〜] $ dmesg |
grep -i错误
[0.053361] mce：[硬件错误]：记录机器检查事件
[0.053364] mce：[硬件错误]：CPU 0：机器检查：0 Bank 4：a600000000020408
[0.053372] mce：[硬件错误]：TSC 0 ADDR fef4c9e0
[0.053378] mce：[硬件错误]：处理器0：706a1时间1535503652 SOCKET 0 APIC 0微代码28
[0.575717] RAS：已初始化可纠正错误收集器。
[2.460149] platform regulatory.0：regulatory.db的直接固件加载失败，错误-2
我正在运行Arch Linux，我在0027之后的任何版本上都会遇到mce错误，所以这就是我在新BIOS发布后尝试新BIOS的原因，如果遇到mce错误则恢复到0027。
我使用[F7]进程升级/降级BIOS，我将多个旧BIOS加载到USB驱动器并逐个尝试，我无法降级到任何以前的版本。
降级BIOS的错误信息是不兼容的BIOS版本，更新中止。



以下为原文

Hi rguevara,
 
I updated to the version 44 and the mce error remain the same for both 4.17.11 and 4.18.5, I still cannot revert back to any previous versions.
 
[~]$ dmesg | grep -i error
[    0.053361] mce: [Hardware Error]: Machine check events logged
[    0.053364] mce: [Hardware Error]: CPU 0: Machine Check: 0 Bank 4: a600000000020408
[    0.053372] mce: [Hardware Error]: TSC 0 ADDR fef4c9e0
[    0.053378] mce: [Hardware Error]: PROCESSOR 0:706a1 TIME 1535503652 SOCKET 0 APIC 0 microcode 28
[    0.575717] RAS: Correctable Errors collector initialized.
[    2.460149] platform regulatory.0: Direct firmware load for regulatory.db failed with error -2
 
I am running  Arch Linux, I am getting mce errors on any version after 0027, so that's the reason I try the new BIOS once it's released and revert back to 0027 if I encountered mce errors.
 
I used the [F7] process to upgrade/downgrade BIOS, I loaded multiple old BIOS to USB drive and try one by one, I could not downgrade to any previous version.
The error information for downgrading BIOS is Incompatible BIOS version, Update Aborted.

嗨Rguevara，
自JY0042之后BIOS更新uCode后，您只能从JY0044降级到JY0043。
JY0044 uCode 0x28
JY0043 uCode 0x28
JY0042 uCode 0x22
生物圈，
玩笑



以下为原文

Hi Rguevara,
You can only downgrade from JY0044 to JY0043 since BIOS update uCode after JY0042.
 
JY0044 uCode 0x28
JY0043 uCode 0x28
JY0042 uCode 0x22
 
BRs,
Josh

嗨，
我刚刚再次检查了这一点，BIOS版本43包括更新的CPU微码（安全建议-00115），一旦BIOS更新到此版本，由于安全原因，您无法返回到以前的版本。
文档中缺少这一小部分，我已经要求添加。
它不能通过任何常规方法降级：BIOS更新，[F7]或BIOS恢复跳线。
我带来的不便表示歉意。
问候，
罗尼G.



以下为原文

Hi,
 
I just checked on this again, BIOS version 43 includes an updated CPU Microcode (Security Advisory-00115), once BIOS is updated to this version you cannot go back to previous versions due to security reasons.
That tiny part is missing from the documentation and I already request that to be added. It cannot be downgraded through any regular method: BIOS update, [F7] or BIOS recovery jumper.
I apologize for the inconvenience.
 
Regards,
Ronny G

嗨azuresong，
我正在调查您报告的MCE错误。
见下图，这是我得到的：     
截图2018-08-29 18-40-00.png 
76.6 K.



以下为原文

Hi azuresong,
 
I am looking into the MCE error that you reported.
See image below, this is what I am getting:
 
 
 
 

•   Screenshot from 2018-08-29 18-40-00.png 76.6 K
  
  

嗨rguevara，
是的，这是我得到的确切的MCE错误，感谢您对此进行调查。



以下为原文

Hi rguevara,
 
Yes, that's the exact MCE error I am getting, thanks for looking into this.

我需要阅读日志，为此我曾经使用mcelog，但它似乎不是内核4.15.0的一部分，我正在运行的那个，我正在读取mcelog已从该内核版本中删除。
我从4.15.0更新。
更新到4.18.5仍然没有mcelog我尝试手动添加它没有成功。
你有办法阅读日志，也许发布截图？



以下为原文

I would need to read the logs and for that I used to use mcelog but it seems it is not part of kernel 4.15.0 which is the one that I am running and I am reading that mcelog was removed from that kernel version.
I updated from 4.15.0. updated to 4.18.5 still no mcelog and I tried to manually add it with no success.
Do you have a way to read the logs and perhaps post a screenshot?

嗨rguevara，
mcelog包已弃用，已被rasdaemon取代。
你可以试一试。
我试图安装rasdaemon来读取mce错误信息并失败，似乎我没有启用几个内核选项，例如EDAS相关的东西。
希望rasdaemon可以帮助你调试。



以下为原文

Hi rguevara,
 
The mcelog package is deprecated and has been replaced by rasdaemon. You could give it a shot.
 
I tried to install the rasdaemon to read the mce error information and failed, it seems like I don't have several kernel options enabled for that, such as EDAS related stuff.
 
Hope rasdaemon could help for you to debug.

嗨azuresong，
感谢您提供的信息，我想我的Linux知识有点过时了，我会尝试rasdaemon但是我之前从未使用过它，我不知道它是否适合我。
另一方面，除了MCE错误信息是系统出现任何其他问题或问题？
我的系统仅用于测试，我并没有真正执行任何任务，所以我看到的一切都很正常。
问候，
罗尼G.



以下为原文

Hi azuresong,
 
Thanks for the information, I guess my Linux knowledge is a bit outdated, I will try rasdaemon however I have never used it before and I dont know if it is going to work out for me.
On the other hand, besides the MCE error message is the system exhibiting any other issue or problem? The system I have is for testing only and I am not really running any task on it so everything I see is normal.
 
Regards,

Ronny G

嗨rguevara，
说实话，除了dmesg日志中的mce错误之外，我还没有遇到任何明显的系统问题或崩溃。
我记得有人告诉我，一旦MCE错误可能导致系统随机重启或应用程序不稳定问题，这种情况是否属实？
我很乐意看到未来BIOS更新中的修复程序。
谢谢！



以下为原文

Hi rguevara,
 
To be honest, I haven't experienced any obvious system issues or crashes yet besides the mce error from the dmesg log.
 
I remember someone told me once that MCE error could cause random system reboot or application unstable issues, is that true for this case? I would love to see a fix in the future BIOS update.
 
Thanks!

我也有同样的问题！
我更换了mem，升级了BIOS，但未能解决



以下为原文

i have the same problem! i replaced mem,upgraded BIOS,but fail to solve

大家好，
我真的需要你的帮助来调试这个问题。
我安装了“rasdeamon”$ sudo apt install rasdaemon
我安装了它，但在运行时我收到一条错误消息，请参阅附件截图。
我得到一个“无法找到已安装的debugfs”错误消息，我相信我已经安装，请参阅屏幕截图上的先前命令。
如果可能的话，我需要你帮助我阅读日志并解释MCE消息，这是我想要做的以跟上对此报告的调查，其次，我需要了解这个错误消息是否连接到
您遇到的硬件问题。
请记住，我们为Linux相关问题提供的支持非常有限，因此您可以越多地帮助我。
问候，
罗尼G.     
截图2018-09-10 22-12-17.png 
107.8 K.



以下为原文

Hi everybody,
 
I am really going to need your help to debug this issue.
I installed "rasdeamon" $ sudo apt install rasdaemon
I have it installed but when running I am getting an error message, see screenshot attached. I am getting a "cant locate a mounted debugfs" error message which I believe I already mounted, see previous commands on screenshot.
I would need that if possible that you help me read the logs and interpret the MCE message which is what I am trying to do to keep up with the investigation on this report and secondly, I need to understand if this error messages is connected to the hardware issues you have had.
 
Please keep in mind that we provide very limited support for Linux related issues so the more you can help me the better.
 
Regards,
Ronny G

•   Screenshot from 2018-09-10 22-12-17.png 107.8 K
  
  

嗨rguevara，
感谢您回复进度报告。
你是如何启用rasdaemon服务的？
我假设Ubuntu现在正在使用systemd，也许您应该尝试使用systemctl enable命令启用rasdaemon服务。
请使用此参考https://wiki.archlinux.org/index.php/Machine-check_exception
另外，我发现rasdaemon github repo，README中的一个段落应该是有益的，这里是链接GitHub - sujithshankar / rasdaemon：克隆来自http://git.infradead.org/users/mchehab/rasdaemon.git/，基本上你
需要重新启动Ubuntu通用内核并启用以下选项，我不希望默认情况下启用这些选项。
然后mcelog应该记录在日记中。
希望这会有所帮助。
在/ contrib下提供了一个脚本，以便测试守护进程EDAC
处理程序。
守护程序正在运行时，只需运行：
＃contrib / edac-fake-inject
该脚本需要使用CONFIG_EDAC_DEBUG编译并运行的内核
EDAC驱动程序。
MCE错误处理可以使用MCE注入：
http://git.kernel.org/cgit/utils/cpu/mce/mce-inject.git
为了使它工作，应该编译和加载内核mce-inject模块。



以下为原文

Hi rguevara,
 
Thanks for report back the progress.
 
How did you enable the rasdaemon service? I assume Ubuntu is currently using systemd now, maybe you should try to enable the rasdaemon service with systemctl enable command. Please use this for reference https://wiki.archlinux.org/index.php/Machine-check_exception
 
Also, I found rasdaemon github repo, a paragraph in the README should be beneficial, here is the link GitHub - sujithshankar/rasdaemon: Cloning from http://git.infradead.org/users/mchehab/rasdaemon.git/ , basically you need to rebuild the Ubuntu generic kernel with following options enabled, which I don't have a hope those options are enabled by default. Then mcelog should be recorded in the journald. Hope this will help.
 
A script is provided under /contrib, in order to test the daemon EDAC
handler. While the daemon is running, just run:
# contrib/edac-fake-inject
 
The script requires a Kernel compiled with CONFIG_EDAC_DEBUG and a running
EDAC driver.
 
MCE error handling can use the MCE inject:
http://git.kernel.org/cgit/utils/cpu/mce/mce-inject.git
For it to work, Kernel mce-inject module should be compiled and loaded.

azuresong从未报告任何硬件问题，但MCE登录启动是有关/恼人的。
我有一个以前的NUC必须​​返回硬件错误，其他MCE日志非常混乱调试。
这是在所有BIOS> 037上启动时遇到相同mce错误的其他人的reddit线程
https://www.reddit.com/r/intelnuc/comments/8ufu1m/nuc7cjyh_gemini_lake_celeron_j4005_owners_please/
您应该能够根据https://www.mcelog.org/installation.html从源代码编译和安装mcelog并使其运行。
虽然我还没有看到它解码我在/ var / log / mcelog中看到的任何MCE错误。



以下为原文

azuresong never reported any hardware issues, but the MCE logs on boot is concerning/annoying. I had a previous NUC that had to be returned for hardware errors and the other MCE logs were very confusing to debug.
 
Here's a reddit thread of others who are experiencing the same mce errors on boot on all BIOS >037
https://www.reddit.com/r/intelnuc/comments/8ufu1m/nuc7cjyh_gemini_lake_celeron_j4005_owners_please/
 
You should be able to compile and install mcelog from source according to https://www.mcelog.org/installation.html  and get it running. I haven't been able to see it decode any of the MCE errors I'm seeing into /var/log/mcelog yet though.

此外，似乎mcelog在这种情况下无法提供详细的输出（虽然我已经看到它在我使用前一块板的真实硬件错误的情况下提供了正确的输出）NUC7PJYH（J5005） - mce：[硬件错误]·
问题＃70·andikleen / mcelog·GitHub
虽然我可以明确地说这个问题是在037之后的BIOS更新中引入的.rguevara，你提到BIOS不能在任何常规方法中降级，这是否意味着有一种非常规方法可用于降级BIOS
同时？



以下为原文

Also it seems like mcelog is having trouble giving detailed outputs in this case (though I've seen it give proper outputs in the case of real hardware errors I had with a previous board) NUC7PJYH (J5005) - mce: [Hardware Error] · Issue #70 · andikleen/mcelog · GitHub
 
Though I can definitively say this issue was introduced in the BIOS update immediately following 037. rguevara, you mentioned that the BIOS cannot be downgraded in any regular method, does that mean there is a non-regular method that can be used to downgrade the BIOS in the meantime?