Hi,
Friday, May 12, 2006 12:19 AM, Vasily Averin wrote:
> Could you please tell me any updates? Could you confirm that
> this issue was
> reproduced on your nodes?
Yes, it has confirmed by F/W team that the controller doesn't support 64-bit DMA.
A patch addresses the issue will followed by soon.
Thank you,
> -----Original Message-----
> From: Vasily Averin [mailto:[email protected]]
> Sent: Friday, May 12, 2006 12:19 AM
> To: Vasily Averin
> Cc: Ju, Seokmann; James Bottomley;
> [email protected]; Kolli, Neela; Mukker, Atul;
> Bagalkote, Sreenivas; [email protected]; Linux Kernel Mailing List
> Subject: Re: megaraid_mbox: garbage in file
>
> Vasily Averin wrote:
> > Ju, Seokmann wrote:
> >>I'm waiting for feedback from F/W team for MegaRAID 150-4
> controller if it supports 64-bit DMA.
> >>
> >>I'll update here as I get.
>
> Could you please tell me any updates? Could you confirm that
> this issue was
> reproduced on your nodes?
>
> >>Can you do one quick change in the driver?
> >>Search for 'pci_set_dma_mask()' API calls in the driver and
> mask out one of them with DMA_64BIT_MASK as follow.
> >>---
> >> // if (pci_set_dma_mask(adapter->pdev, DMA_64BIT_MASK) != 0) {
> >>
> >> // conlog(CL_ANN, (KERN_WARNING
> >> // "megaraid: could not set DMA mask for
> 64-bit.\n"));
> >>
> >> // goto out_free_sysfs_res;
> >> // }
> >>---
> >>
> >>I found that the driver is NOT checking 64-bit DMA
> capability of the controllers accordingly and this could be a reason.
> >
> > This change help me:
> > Errors go away, file content is correct.
>
> I'm going to use this change in production, at least as
> temporal workaround.
> Could you please confirm that it is safe for all controllers
> supported by this
> driver?
>
> Thank you,
> Vasily Averin
>
> SWsoft Virtuozzo/OpenVZ Linux kernel team
>