Re: Kernel 5.4
Posted: Sat Oct 12, 2019 12:20 am
The memory issue with Dawicontrol DC 2976 UW is present also in Kernel 5.4 rc2.
Support Forum
https://forum.hyperion-entertainment.com/
https://forum.hyperion-entertainment.com/viewtopic.php?t=4349
xeno74 wrote:Hi Roland,Roland wrote:I noticed that Kernel 5.3 has created a problem which does not exist in 4.20 or earlier... If there is a Dawicontrol DC 2976 UW SCSI board (PCI) installed, the system does not boot unless the RAM is limited to 3500M. This happens now even when there is nothing connected to the controller!
Thanks a lot for reporting the issue with the Dawicontrol DC 2976 UW SCSI board (PCI).
Could you please test the RC2 of kernel 5.4 with this SCSI board? I would like to know if the problem still exists in the latest kernel.
Please post the results in the kernel 5.4 test thread.
Thanks in advance,
Christian
Hi Roland,Roland wrote:The memory issue with Dawicontrol DC 2976 UW is present also in Kernel 5.4 rc2.
4.21-alpha1 does not have that issue, I can use the full 8 Gb memory with it. I tested this with unitrd-4.19.3.
Thanks for testing the alpha1. Please test the alpha2 of kernel 4.21/5.0. I would like to know when the code changed.Roland wrote: 4.21-alpha1 does not have that issue, I can use the full 8 Gb memory with it.
Strange. Please test the alphas without any initial ramdisks. The initrds falsify the results.Roland wrote: I tested this with unitrd-4.19.3.
I tested also 5.1 (first stable version), and found out that if I use the uinitrd-4.19.3, I can use full RAM, but if unitrd-5.3, the issue is present.
4.20.17 seems to work ok both with unitrd-4.19.3 and unitrd-5.3.
Thanks for testing! Both have the patch because of this issue.Roland wrote: I tested now the alphas... 4.21-alpha2 is last which works - the issue is present starting from alpha3.
Code: Select all
diff -rupN a/arch/powerpc/sysdev/fsl_pci.c b/arch/powerpc/sysdev/fsl_pci.c
--- a/arch/powerpc/sysdev/fsl_pci.c 2018-12-28 08:20:11.651183458 +0100
+++ b/arch/powerpc/sysdev/fsl_pci.c 2018-12-28 08:17:54.971034055 +0100
@@ -127,9 +127,6 @@ static inline void setup_swiotlb_ops(str
static int fsl_pci_dma_set_mask(struct device *dev, u64 dma_mask)
{
- if (!dev->dma_mask || !dma_supported(dev, dma_mask))
- return -EIO;
-
/*
* Fix up PCI devices that are able to DMA to the large inbound
* mapping that allows addressing any RAM address from across PCI.
I think this problem with PCI boards should be solved in general level... It is stupid that some boards work, and others do not, without anyone really knowing why.xeno74 wrote: I tried to revert the changes in the file arch/powerpc/kernel/dma.c. The problem is, this file doesn’t exist in the latest kernels anymore. That means we can’t fix anything which doesn’t exist anymore. I think the issue was in these files but today it is somewhere in the other files.
That system seems to be for programmers etc., and you have to create an account.... Too complicated to my old, non-programmable brainsPlease create a bug report because the changes to the code are too long ago.
It’s very important to test the alphas and release candidates because the sooner we notice an error, the higher is the chance of a fast solution.