From: Markus Lidel <Markus.Lidel@shadowconnect.com>
To: Vasily Averin <vvs@sw.ru>
Cc: linux-scsi@vger.kernel.org, devel@openvz.org
Subject: Re: 64bit DMA in i2o_block
Date: Fri, 22 Sep 2006 12:14:27 +0200 [thread overview]
Message-ID: <4513B783.70008@shadowconnect.com> (raw)
In-Reply-To: <4513A87F.8040809@sw.ru>
[-- Attachment #1: Type: text/plain, Size: 2152 bytes --]
Hello,
Vasily Averin wrote:
> I've found that your driver does not work correctly with following options:
> CONFIG_I2O_EXT_ADAPTEC=y
> # CONFIG_I2O_EXT_ADAPTEC_DMA64 is not set
> I've checked it on 2.6.18 kernel on x86_64 node with 4Gb memory.
That could be the reason for the problems. I've only tried it on x86_64
machines with < 4 GB memory...
> I would note that I've not noticed any bugs on x86 kernels, but x86_64 does not
> work at all.
> The behaviors of x86_64 kernels can differ:
> sometimes driver can not find partition table:
> i2o/hda: unknown partition table
> sometimes it find not all partition:
> i2o/hda: i2o/hda1 i2o/hda2 i2o/hda3 i2o/hda4 < >
> in other cases it detects devices well but corrupt the memory and filesystem:
> Sep 21 16:46:09 ts10 block-osm: registered device at major 80
> Sep 21 16:46:09 ts10 i2o/hda: i2o/hda1 i2o/hda2 i2o/hda3 i2o/hda4 < i2o/hda5 >
> Sep 21 16:46:09 ts10 block-osm: device added (TID: 207): i2o/hda
> Sep 21 16:46:09 ts10 kjournald starting. Commit interval 5 seconds
> Sep 21 16:46:09 ts10 EXT3-fs: mounted filesystem with ordered data mode.
> Sep 21 16:46:10 ts10 Freeing unused kernel memory: 236k freed
> Sep 21 16:46:10 ts10 hotplug[961]: segfault at 0000000000000008 rip
> 00000032411088cf rsp 00007fff5b189050 error 4
> When I enabled CONFIG_I2O_EXT_ADAPTEC_DMA64 -- all the troubles went away.
> I've tried to investigate this issue, but I've not found and documentation
> described format of Adaptec's private messages.
> I would like to ask you, is this behavior specific for my hardware (Adaptec
> ASR-2010S I2O Zero Channel)? If not, I believe it makes sense to enable
> CONFIG_I2O_EXT_ADAPTEC_DMA64 in Kconfig by default for 64-bit kernels.
I believe it's a driver issue. Do you have a testing-system where you
could try out the appended patch?
Thank you very much.
Best regards,
Markus Lidel
------------------------------------------
Markus Lidel (Senior IT Consultant)
Shadow Connect GmbH
Carl-Reisch-Weg 12
D-86381 Krumbach
Germany
Phone: +49 82 82/99 51-0
Fax: +49 82 82/99 51-11
E-Mail: Markus.Lidel@shadowconnect.com
URL: http://www.shadowconnect.com
[-- Attachment #2: i2o-test-32bit-dma.patch --]
[-- Type: text/x-patch, Size: 606 bytes --]
--- include/linux/i2o.h 2006-09-22 12:07:29.286557446 +0200
+++ include/linux/i2o.h 2006-09-22 12:08:01.904303452 +0200
@@ -776,6 +776,8 @@
#ifdef CONFIG_I2O_EXT_ADAPTEC_DMA64
if ((sizeof(dma_addr_t) > 4) && c->pae_support)
*mptr++ = cpu_to_le32(i2o_dma_high(dma_addr));
+#else
+ BUG_ON((u32) ((u64) dma_addr >> 32));
#endif
*sg_ptr = mptr;
}
@@ -835,6 +837,8 @@
#ifdef CONFIG_I2O_EXT_ADAPTEC_DMA64
if ((sizeof(dma_addr_t) > 4) && c->pae_support)
*mptr++ = cpu_to_le32(i2o_dma_high(sg_dma_address(sg)));
+#else
+ BUG_ON((u32) ((u64) sg_dma_address(sg) >> 32));
#endif
sg++;
}
next prev parent reply other threads:[~2006-09-22 10:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-22 9:10 64bit DMA in i2o_block Vasily Averin
2006-09-22 10:14 ` Markus Lidel [this message]
2006-09-22 10:54 ` Andi Kleen
2006-09-22 11:47 ` Markus Lidel
2006-09-22 11:39 ` 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=4513B783.70008@shadowconnect.com \
--to=markus.lidel@shadowconnect.com \
--cc=devel@openvz.org \
--cc=linux-scsi@vger.kernel.org \
--cc=vvs@sw.ru \
/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