From: Robert Hancock <hancockr@shaw.ca>
To: Jan Kasprzak <kas@fi.muni.cz>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3ware 7500 not working in 2.6.16.18, 2.6.17-rc5
Date: Thu, 25 May 2006 20:03:14 -0600 [thread overview]
Message-ID: <447661E2.5020103@shaw.ca> (raw)
In-Reply-To: <6gn8D-4AV-13@gated-at.bofh.it>
Jan Kasprzak wrote:
> Hi all,
>
> I have a 3ware 75xx P-ATA controller, which has been working in 2.6.15-rc2.
> Today I have tried to upgrade to 2.6.16.18, and it cannot boot - the
> controller cannot access the drives, with the attached messages.
> I have also tried 2.6.17-rc5 with the same results.
...
> 3w-xxxx: tw_map_scsi_sg_data(): pci_map_sg() failed.
> nommu_map_sg: overflow 2053d9000+4096 of device mask ffffffff
> sd 0:0:0:0: SCSI error: return code = 0x70000
> end_request: I/O error, dev sda, sector 0
> Buffer I/O error on device sda, logical block 0
> nommu_map_sg: overflow 2053d9000+4096 of device mask ffffffff
> 3w-xxxx: tw_map_scsi_sg_data(): pci_map_sg() failed.
> [... and so on, the same for all eight drives sda to sdh ...]
It looks like this controller only supports 32-bit DMA addresses. For
some reason it's trying to feed in an SG list with addresses over 4GB,
which fails. I'd think this configuration should work, but maybe not?
It looks like you have IOMMU turned off - I think you'll really want to
turn that on with that much RAM (12GB). Even if this case did work as
well as it could, without IOMMU the kernel would have to bounce-buffer
the data below 4GB which will kill performance.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2006-05-26 2:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6gn8D-4AV-13@gated-at.bofh.it>
2006-05-26 2:03 ` Robert Hancock [this message]
2006-05-26 10:08 ` 3ware 7500 not working in 2.6.16.18, 2.6.17-rc5 Jan Kasprzak
2006-05-25 12:22 Jan Kasprzak
2006-05-25 12:35 ` Jan Kasprzak
2006-05-25 13:25 ` Jeff Garzik
2006-05-25 13:39 ` Jan Kasprzak
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=447661E2.5020103@shaw.ca \
--to=hancockr@shaw.ca \
--cc=kas@fi.muni.cz \
--cc=linux-kernel@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