linux-scsi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vasily Averin <vvs@sw.ru>
To: Vasily Averin <vvs@sw.ru>
Cc: "Ju, Seokmann" <Seokmann.Ju@lsil.com>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	linux-scsi@vger.kernel.org, "Kolli,
	Neela" <Neela.Kolli@engenio.com>,
	"Mukker, Atul" <Atul.Mukker@engenio.com>,
	"Bagalkote, Sreenivas" <Sreenivas.Bagalkote@engenio.com>,
	devel@openvz.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: megaraid_mbox: garbage in file
Date: Fri, 12 May 2006 08:18:32 +0400	[thread overview]
Message-ID: <44640C98.3070006@sw.ru> (raw)
In-Reply-To: <445BE14D.8000706@sw.ru>

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

  reply	other threads:[~2006-05-12  4:15 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-05 19:59 megaraid_mbox: garbage in file Ju, Seokmann
2006-05-05 23:35 ` Vasily Averin
2006-05-12  4:18   ` Vasily Averin [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-12 12:19 Ju, Seokmann
2006-05-04 18:48 Vasily Averin
2006-05-04 22:59 ` James Bottomley
2006-05-05  5:37   ` Vasily Averin
2006-05-05  9:21     ` Vasily Averin
2006-05-05 15:59     ` James Bottomley
2006-05-05 18:17       ` Vasily Averin
2006-05-05 20:05         ` James Bottomley
2006-05-05 23:43           ` Vasily Averin

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=44640C98.3070006@sw.ru \
    --to=vvs@sw.ru \
    --cc=Atul.Mukker@engenio.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=Neela.Kolli@engenio.com \
    --cc=Seokmann.Ju@lsil.com \
    --cc=Sreenivas.Bagalkote@engenio.com \
    --cc=devel@openvz.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).