From: Vasily Averin <vvs@sw.ru>
To: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
Cc: 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: Sat, 06 May 2006 03:35:41 +0400 [thread overview]
Message-ID: <445BE14D.8000706@sw.ru> (raw)
In-Reply-To: <890BF3111FB9484E9526987D912B261901BD42@NAMAIL3.ad.lsil.com>
Ju, Seokmann wrote:
> 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:
megaraid mailbox: status:0x0 cmd:0xa7 id:0x1f sec:0x1a lba:0x33f624ac
addr:0xffffffff ld:128 sg:4
scsi cmnd: 0x28 0x00 0x33 0xf6 0x24 0xac 0x00 0x00 0x1a 0x00
mbox request_buffer ebeb9380 use_sg 4
mbox sg0: page 050c5d88 off 0 addr e90d2000 len 4096 virt eb0d2000
first 732e646c page->flags 20000000
mbox sg1: page 050c5710 off 0 addr e90a4000 len 4096 virt eb0a4000
first 00000003 page->flags 20000000
mbox sg2: page 050c4438 off 0 addr e901e000 len 4096 virt eb01e000
first 00000000 page->flags 20000000
mbox sg3: page 030d64dc off 1024 addr 5f3f400 len 1024 virt 07f3f400
first 19398a0e page->flags 20001004
Errors go away, file content is correct.
> 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.
How do you this, can it be the cause of
http://bugzilla.kernel.org/show_bug.cgi?id=6052
If so, you have a good chance to resolve this bug too :)
Thank you,
Vasily Averin
SWsoft Virtuozzo/OpenVZ Linux kernel team
next prev parent reply other threads:[~2006-05-05 23:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-05 19:59 megaraid_mbox: garbage in file Ju, Seokmann
2006-05-05 19:59 ` Ju, Seokmann
2006-05-05 23:35 ` Vasily Averin [this message]
2006-05-12 4:18 ` Vasily Averin
-- strict thread matches above, loose matches on Subject: below --
2006-05-12 12:19 Ju, Seokmann
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
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=445BE14D.8000706@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.