> On 23. Apr 2018, at 10:28, Kashyap Desai <kashyap.de...@broadcom.com> wrote >> >> Just did that on the “Dell R730xd, MegaRAID SAS-3 3108” and get the >> following output when the megacli works fine. >> >> ### >> Apr 23 09:31:37 xh643 kernel: [ 368.319092] GD IOV-len: 2048 Apr 23 >> 09:31:37 >> xh643 kernel: [ 368.319426] GD IOV-len: 32 Apr 23 09:31:37 xh643 kernel: >> [ >> 368.319563] GD IOV-len: 320 Apr 23 09:31:37 xh643 kernel: [ 368.319698] >> GD >> IOV-len: 616 Apr 23 09:31:37 xh643 kernel: [ 368.319887] GD IOV-len: 1664 >> Apr 23 09:31:37 xh643 kernel: [ 368.320040] GD IOV-len: 32 Apr 23 >> 09:31:37 >> xh643 kernel: [ 368.320174] GD IOV-len: 8 … ### >> >> Full output is attached in iov_len_megacli_works.txt, it also contains the >> output of /proc/buddyinfo which might be important based in my research so >> far. > > We need similar output whenever there is a dma_alloc_coherent() failure. > Did you added new prints in failure of dma_alloc_coherent() OR it is generic > print for all the case ?
Right now its generic for every iteration of the loop
###
6943 for (i = 0; i < ioc->sge_count; i++) {
6944 if (!ioc->sgl[i].iov_len)
6945 continue;
6946
6947 printk("GD IOV-len: %d\n", ioc->sgl[i].iov_len);
6948
6949 kbuff_arr[i] = dma_alloc_coherent(&instance->pdev->dev,
###
I will add the printk to dma_alloc_coherent() as well to see, which request
actually fails. But i have to be a bit patient since its a production system
and the customers aren’t to happy about reboots.
I have tried to build live-patch kernel to be more flexible with changes, but
the built failed with
###
...
/root/kpatch/kpatch-build/create-diff-object: unreconcilable difference
...
###
but thats out of focus for this list and just fyi :-)
signature.asc
Description: Message signed with OpenPGP
