Hyperion Entertainment Message Boards

xeno74 wrote:Hi All,

Here is the RC2 of kernel 5.0 for testing.

New:

• Many DRM fixes:
  drm-fixes-2019-01-11-1
  drm-fixes-2019-01-11
  drm-intel-fixes-2019-01-11
  drm-misc-fixes-2019-01-10-1
  drm-fixes-5.0
  drm-misc-fixes-2019-01-10
• Linux 5.0-RC2 Kernel Released -- phoronix.com
• The Many New Features & Improvements Of The Linux 5.0 Kernel -- phoronix.com
• Linus Torvalds' RC2 message
• Linux Git log
• Phoronix articles, reviews and news stories covering Linux 5.0

Please note: I tried to compile the RC2 without the latest DRM updates for the ATI FireMV 2250 and ATI FirePro 2260 from the latest Git kernel today.
Unfortunately there are so many new dependencies because of many new small and big DRM fixes so I wasn't able to remove the first DRM updates today.
The ATI FireMV 2250 and ATI FirePro 2260 work alone without any problems in a X5000 but they don't work with a HD7xxx together anymore.
Ace doesn't have any error messages for us so it is difficult for us to report it to the developers.

Download: vmlinux-5.0-rc2-AmigaOne_X1000_X5000.tar.gz

Screenshot of Fienix with the RC2 of kernel 5.0 connected to a Leopard server:



Please test it.

Thanks,
Christian

Skateman wrote:Kernel 5.0 RC2 is running with no issues on the AmigaOne X5000

Keep up the good work Christian

acefnq wrote:Christian
With both cards in RC2 boots to Radeon SI card and works fine. Don't worry if you can't remove the DRM from here on in I will generally use my SI and only reverts to the earlier RCs if I want specific 3d support as I am very apprehensive about continually removing my cards (I killed my XE doing that)

Cheers

ace

Christoph Hellwig wrote: Hi Christian,

can you check if the debug printks in this patch trigger?

diff --git a/kernel/dma/direct.c b/kernel/dma/direct.c
index 355d16acee6d..e46c9b64ec0d 100644
--- a/kernel/dma/direct.c
+++ b/kernel/dma/direct.c
@@ -118,8 +118,11 @@ struct page *__dma_direct_alloc_pages(struct device *dev, size_t size,
 			page = NULL;
 		}
 	}
-	if (!page)
+	if (!page) {
 		page = alloc_pages_node(dev_to_node(dev), gfp, page_order);
+		if (!page)
+			pr_warn("failed to allocate memory with gfp 0x%x\n", gfp);
+	}
 
 	if (page && !dma_coherent_ok(dev, page_to_phys(page), size)) {
 		__free_pages(page, page_order);
@@ -139,6 +142,10 @@ struct page *__dma_direct_alloc_pages(struct device *dev, size_t size,
 		}
 	}
 
+	if (!page) {
+		pr_warn("failed to allocate DMA memory!\n");
+		dump_stack();
+	}
 	return page;
 }

Christoph Hellwig wrote: On top of 257002094bc5935dd63207a380d9698ab81f0775, that is the first
one you identified as breaking the detection of the SATA disks.