Siduction Forum
Siduction Forum => Installation - Support => Topic started by: id027102 on 2020/03/29, 10:33:16
-
Next problem appears with kernel 5.5.* , never seen before :
Mar 29 09:56:39 medion-pc kernel: EDAC amd64: Error: F1 not found: device 0x1601 (broken BIOS?)
Mar 29 09:56:39 medion-pc kernel: EDAC amd64: Error: F1 not found: device 0x1601 (broken BIOS?)
Mar 29 09:56:39 medion-pc kernel: EDAC amd64: Error: F1 not found: device 0x1601 (broken BIOS?)
Mar 29 09:56:39 medion-pc kernel: EDAC amd64: Error: F1 not found: device 0x1601 (broken BIOS?)
Is it possible somethings to set in kernel ?
Similar problem solved with upgrade kernel with suse here :
https://www.suse.com/support/kb/doc/?id=000019537
Can somebody help ?
-
You did not show your hardware "inxi -Fz" which might have helped. Also, how long have you had siduction installed on that system? I noticed you chose the "Installation" forum to post the problem -- is this a new hardware platform? I ask this because linux 5.5-x is not new in siduction.
I believe your issue is described in the second part of this article (https://ndimcomputing.io/fs-fp5v_ecc_linux.html).
-
kernel: EDAC amd64: Error: F1 not found: device 0x1601
0x1601 (not 0x1460 as in your link) has been in the kernel for ages (one proof (https://lkml.org/lkml/2013/9/24/713)). towo?
You has flashed the latest available BIOS/UEFI? If the indescribable Medion support provides one...
Btw., EDAC (https://en.wikipedia.org/wiki/Forward_error_correction), you do not have a server mainboard with ECC - do you? Medion... ;-)
-
I would have tested 5.6.0-rc7-siduction-amd64 too. The night is expected to come the final anyway.
Update: 5.6 vanilla final is out.
-
In attach the rsult of inxi -Fz
And :
I had no problem before 5.5 , I reinstalled 5.4.18 and no problem anymore
Also reinstalled other 5.5.* and each had the same problem
Now I installed kernel from debian , and also no problem
No this is no new hardware , but I was for 3 month in Indonesia (without the desktop)
And NO I does not check everyday for error
Also medion-pc , is the name of the pc from the beginning , but in 2018 aug , the motherboard,CPU and memory have been replaced , so nothing to do with medion support
And Yes the latest bios/uefi stable available on msi.com is flashed
-
Checked config for differencs to day , and I find :
CONFIG_EDAC_GHES is not set for 5.4 and CONFIG_EDAC_GHES=y for 5.5
CONFIG_EDAC_I10NM is not set for 5.4 and CONFIG_EDAZC_I10NM=m for 5.5
Can it be the origin of the problem ?
-
If you think CONFIG_EDAC_GHES is your problem, boot your system with ghes.disable=1 as kernel bootparameter.
-
ghes.disable=1 did not solve the problem
Must be a diff between 5.4 and 5.5 but what ? (debian kernels = same problem as siduction kernels 5.4 OK , 5.5 NOK)
-
It seems of problem is solved by blacklisting amd64_edac_mod