From: John David Anglin <dave.anglin@bell.net>
To: Carlo Pisani <carlojpisani@gmail.com>
Cc: Parisc List <linux-parisc@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: C3600, sata controller
Date: Sun, 12 May 2019 17:10:05 -0400 [thread overview]
Message-ID: <f52cf203-c48a-fd04-5827-19903c3a192f@bell.net> (raw)
In-Reply-To: <CA+QBN9A4PhPZ36otsk0TRaO9KKnKL=hfnskfFJGQJEbtb3=i=Q@mail.gmail.com>
The c3600 doesn't have any PCI-X slots (only PCI) as far as I can tell from user manuals.
The SY-PCX40009 PCI-X card that I have says it supports two models: 32-bit at 66 MHz and 64-bit
at 133 MHz. The 32-bit slots in c3600 are 33 MHz. Whether the card will work at 33 MHz is not
clear. The card says it's backward compatible to PCI 2.3.
On 2019-05-12 4:44 p.m., Carlo Pisani wrote:
> guys,
> I asked a friend to lend us his card, which is the card2 listed below
> and not things are becoming really weird
>
> card1, Silicon Image, Inc. Adaptec AAR-1210SA
> card2, Silicon Image, Inc. SiI 3124 PCI-X Serial ATA
>
> the card1 is a PCI32 bit card, and uses the "sata_sil" driver
> the card2 is a PCI64 bit card, and uses the "sata_sil24" driver
>
> card1 is installed in a PCI32 slot, and it's moving 32Gbyte in a loop
> without any issue
>
> I have just tested card2 in each of the PCI-X slot (including the 3.3V
> one) and ... it has always triggered the HPMC unit, crashing the
> machine
>
> the hardware is different, and drivers are also different, but ....
> maybe the problem is related to 32 vs 64bit?
>
> I am going to repeat the test with card2 installed in a PCI32 slot.
> This should force it to 32bit: will it work correctly?
> (hope this makes sense)
>
> ---
>
> we have also checked if the kernel is correctly handling the ram
> we have a C3600 with 8Gbyte of ram
>
> mount -t tmpfs -o size=7G tmpfs /mnt/ramdrive/
> dd if=/dev/zero of=/mnt/ramdrive/test.bin
> badblocks -swv /mnt/ramdrive/test.bin
>
> checking for bad blocks in read-write mode
> >From block 0 to 7340031
> Testing with pattern 0xaa: done
> Reading and comparing: done
> Testing with pattern 0x55: done
> Reading and comparing: done
> Testing with pattern 0xff: done
> Reading and comparing: done
> Testing with pattern 0x00: done
> Reading and comparing: done
> Pass completed, 0 bad blocks found.
>
> no problems found
>
--
John David Anglin dave.anglin@bell.net
next prev parent reply other threads:[~2019-05-12 21:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-01 21:45 linux-next: Signed-off-by missing for commit in the parisc-hd tree Stephen Rothwell
2019-05-02 5:48 ` Helge Deller
2019-05-12 20:44 ` C3600, sata controller Carlo Pisani
2019-05-12 20:49 ` Carlo Pisani
2019-05-12 21:10 ` John David Anglin [this message]
2019-05-12 21:15 ` Carlo Pisani
2019-05-13 23:14 ` John David Anglin
2019-05-13 23:24 ` Carlo Pisani
2019-05-13 23:47 ` Carlo Pisani
2019-05-14 1:50 ` John David Anglin
2019-05-14 8:22 ` Carlo Pisani
[not found] ` <CA+QBN9CgMRFmv+isvH-Y=FCCFwKhmD5_5s5u32xg+wk-gTLK5A@mail.gmail.com>
2019-05-14 12:10 ` John David Anglin
2019-05-14 12:29 ` Carlo Pisani
2019-05-14 12:57 ` C3600, optical Fibre Channel, any card? Carlo Pisani
2019-05-14 13:01 ` C3600, sata controller Sven Schnelle
2019-05-14 14:23 ` John David Anglin
2019-05-17 15:43 ` Carlo Pisani
2019-05-17 17:21 ` Helge Deller
2019-05-17 18:05 ` John David Anglin
2019-05-17 18:25 ` Carlo Pisani
2019-05-13 15:10 ` Carlo Pisani
2019-05-13 21:58 ` Carlo Pisani
2019-05-17 17:31 ` Carlo Pisani
2019-05-25 8:59 ` Carlo Pisani
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=f52cf203-c48a-fd04-5827-19903c3a192f@bell.net \
--to=dave.anglin@bell.net \
--cc=carlojpisani@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-parisc@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).