<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Joseph,<br>
<br>
please provide the output of lspci -vvvv when the driver is not
loaded as an attachment.<br>
<br>
Additional to that a full dmesg as a text file attachment with the
crash would be helpful, you should still be able to ssh into the
system even when the driver crashed.<br>
<br>
That looks strongly like the BIOS didn't assigned a PCI BAR to the
GPUs. The drivers crashes because we assume that the BIOS is
working correctly and assigned PCI BARs to all GPUs.<br>
<br>
Another possibility is that something went wrong while resizing
the BARs. In this case it would be a driver/PCI subsystem problem.<br>
<br>
Regards,<br>
Christian.<br>
<br>
Am 15.02.2018 um 23:26 schrieb Joseph Wang:<br>
</div>
<blockquote type="cite"
cite="mid:CAPoeEY80EyzCrRfTFp7E9VreZAzEUC4SQ6Kuqynn2Q3oL9CB5A@mail.gmail.com">
<div dir="ltr">
<div>I'm attempting to use amdgpu with the B250 mining expert
motherboard for GPU mining of ethereum. The MB can handle 19
cards. When I have more than six cards, X11 stops working but
I can still handle text console. At nine cards, I get the
attached kernel oops on boot.</div>
<div><br>
</div>
<div>This is running with the drm-next-4.17-wip branch.</div>
<div><br>
</div>
<div>Also would love to get this working with rocm<br>
</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
amd-gfx mailing list
<a class="moz-txt-link-abbreviated" href="mailto:amd-gfx@lists.freedesktop.org">amd-gfx@lists.freedesktop.org</a>
<a class="moz-txt-link-freetext" href="https://lists.freedesktop.org/mailman/listinfo/amd-gfx">https://lists.freedesktop.org/mailman/listinfo/amd-gfx</a>
</pre>
</blockquote>
<br>
</body>
</html>