Re: Stardom SATA HSM violation
Tejun Heo wrote:
Hello,
Mark Lord wrote:
I reported a very similar bug back a few releases ago.
Anyone who wants to try it themselves, can do this with hdparm-7.7 (from
sourceforge):
hdparm --drq-hsm-error /dev/sda
Whether or not it hangs the machine does depend upon exactly which SATA
LLD is used,
and what model/revision of drive is installed. But if it hangs for you
(eg. Tejun),
then you now have a way to reproduce a HSM error "on demand" for
testing. :)
Neat. Is this the FIFO-draining issue?
Yeah, that's the one. And I still patch my own kernels to
automatically drain up to 512 words from the FIFO when this happens.
Works like a charm. Patch below for demonstration purposes.
Signed-Off-By: Mark Lord <[EMAIL PROTECTED]>
---
--- linux/drivers/ata/libata-sff.c.orig 2007-04-26 12:02:46.0 -0400
+++ linux/drivers/ata/libata-sff.c 2007-04-29 08:29:27.0 -0400
@@ -413,6 +413,24 @@
ap->ops->irq_on(ap);
}
+static void ata_drain_fifo (struct ata_port *ap, struct ata_queued_cmd *qc)
+{
+ u8 stat = ata_chk_status(ap);
+ /*
+* Try to clear stuck DRQ if necessary.
+*/
+ if ((stat & ATA_DRQ) && (!qc || qc->dma_dir != DMA_TO_DEVICE)) {
+ unsigned int i, limit = 512;
+ printk("Draining up to %u words from data FIFO.\n", limit);
+ for (i = 0; i < limit ; ++i) {
+ ioread16(ap->ioaddr.data_addr);
+ if (!(ata_chk_status(ap) & ATA_DRQ))
+ break;
+ }
+ printk("Drained %u/%u words.\n", i, limit);
+ }
+}
+
/**
* ata_bmdma_drive_eh - Perform EH with given methods for BMDMA controller
* @ap: port to handle error for
@@ -469,7 +487,7 @@
}
ata_altstatus(ap);
- ata_chk_status(ap);
+ ata_drain_fifo(ap, qc);
ap->ops->irq_clear(ap);
spin_unlock_irqrestore(ap->lock, flags);
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: CF as IDE on ICH6M using libata
Tejun Heo wrote: Eddie Hung wrote: However, I think we can conclude that ICH6M (which on the X41, has a SATA-PATA bridge to connect a PATA drive) does not seem to support MWDMA It isn't clear whether the fault is at the driver or the CF device. It's probably the bridge chip --> we've run through that one before just recently (early summer?) on this list. A particular bridge that doesn't work at all with MWDMA. Cheers - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: pata_via cd/dvd timeout problems
On Thu, 2007-09-06 at 01:33 +0100, Alan Cox wrote: > > Unfortunately I don't have another machine to try these drives in. But > > they both worked OK under the old ide code -- the problems only started > > with the move to libata. > > > > I guess the commands timing out are udev probing to see if a disk has > > been inserted ? > > Probably. If you can file a bug in bugzilla and assign it to me I'll take > a look at this after the kernel summit. There are one or two reports with > pata_via and ATAPI (ie CD) that look similar. Hi Alan, I've created a bug for this http://bugzilla.kernel.org/show_bug.cgi?id=8986 but somehow I messed up and it didn't get assigned to you and now I can't change who it's assigned too. Can you take ownership or should I delete it and start again ? sorry Richard - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
drivers/ata/ahci.c driver questions / recommendations
Hello Mr Garzik or Linux IDE contributors: My name is Adrian B. Weissman. I am looking for open source AHCI / Sata II compliance test software. I read your name ( [EMAIL PROTECTED] ) at the top of the drivers/ata/ahci.c source file, and figured that you would be a good person to speak with. Basically, I was wondering what you or the linux-ide crew use to verify that your software is AHCI / Sata II Compliant? My initial guess if this type of software was not available was to purchase several of the various AHCI / Sata II controllers on PCI express card and build up a test suite. Any pointers or recommendations would be greatly appreciated. Regards, Adrian B. Weissman Building a website is a piece of cake. Yahoo! Small Business gives you all the tools to get online. http://smallbusiness.yahoo.com/webhosting - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai
Gaston, Jason D wrote:
-Original Message-
From: Gaston, Jason D
Sent: Friday, August 31, 2007 10:10 AM
To: 'Jeff Garzik'
Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED]
Subject: RE: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch
for
Intel Tolapai
This device has both AHCI and RAID modes that use the ahci driver.
Only
the RAID mode DID's are being added as the PCI class code support will
cover the AHCI mode. Looking at the Generic, PCI class code support
section, it uses "board_ahci". I assumed that they should be the same
as
the generic class code support is working on this platform.
Thanks,
Jason
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 12:47 AM
To: Gaston, Jason D
Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED]
Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch
for
Intel Tolapai
Jason Gaston wrote:
Resend trying to remove 8-bit characters in the email.
This patch adds the Intel Tolapai RAID controller DID's for SATA
support.
Signed-off-by: Jason Gaston <[EMAIL PROTECTED]>
--- linux-2.6.23-rc4/drivers/ata/ahci.c.orig2007-08-27
18:32:35.0 -0700
+++ linux-2.6.23-rc4/drivers/ata/ahci.c 2007-08-28
16:58:11.0 -
0700
@@ -411,6 +411,8 @@
{ PCI_VDEVICE(INTEL, 0x292f), board_ahci_pi }, /* ICH9M */
{ PCI_VDEVICE(INTEL, 0x294d), board_ahci_pi }, /* ICH9 */
{ PCI_VDEVICE(INTEL, 0x294e), board_ahci_pi }, /* ICH9M */
+ { PCI_VDEVICE(INTEL, 0x502a), board_ahci }, /* Tolapai */
+ { PCI_VDEVICE(INTEL, 0x502b), board_ahci }, /* Tolapai */
Why did you not use board_ahci_pi? Is the AHCI ports-implemented
register unreliable on this platform?
Jeff,
Do I need to change this to board_ahci_pi or is it ok to leave it at
board_ahci, which will be used by the AHCI class code devices?
You are the one who needs to answer this question ;-)
Most new Intel AHCI have a sane and reliable Ports-Implemented register
value even across reset, unlike earlier ones or some clones. For those,
we use board_ahci_pi.
If PI is not reliable across reset or if BIOS is absent (yes we care
about that case, when we do our own PCI resume for example), then you
should use board_ahci.
Jeff
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [RFT][PATCH v7] sata_mv: convert to new EH
dean gaudet wrote: On Fri, 13 Jul 2007, greg wrote: dean gaudet arctic.org> writes: if you've got any other workload you'd like me to throw at it, let me know. I've had a few problems with the driver in 2.6.20 (fc6xen x86_64). The machine tended to lock up after a random period of time (from a few minutes upwards), without any messages. Performing a smartctl on all the disks, or leaving smartd running, seemed to speed up the rate at which the crash occurred. What I found was that by moving the sata_mv device onto it's own bus (or a bus with two sata_mv devices), the crashes went away. Are you doing tests with the controller sharing a bus with other devices? Is there an merit to my observation that it might be an issue with devices sharing a PCI-X bus? Cards: Supermicro 5081 (SAT-MV8), Supermicro 6081 (SAT2-MV8), Highpoint 5081 (RocketRaid 1820A v1.1). Motherboards: Tyan S2882, AMD 8131 chipset; IBM x206, Intel 6300ESB. hmm! i don't seem to have replied to this. you know, i've seen this problem. the first time it happened was with a promise ultra tx/100 or tx/133 (on a dual k7 box, two controllers on the same bus certainly)... a 5 minute cronjob logging HD temperatures via smart would occasionally cause one of the disks to just disappear, return errors on every request, and required a reboot to rediscover it. eliminating the cronjob stopped the problem. Promise cards, in particular, snoop the ATA commands and occasionally update registers and do other internal magic based upon those commands. It is possible that SMART commands have the same requirements as SET FEATURES - XFER MODE: namely, all ports must be idle when the command is issued, not just the port in question. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH] libata: Add a drivers/ide style DMA disable
Tejun Heo wrote: Alan Cox wrote: This is useful when debugging, handling problem systems, or for distributions just to get the system installed so it can be sorted out later. This is a bit smarter than the old IDE one and lets you do libata.pata_dma=0 Disable all PATA DMA like old IDE libata.pata_dma=1 Disk DMA only libata.pata_dma=2 ATAPI DMA only libata.pata_dma=4 CF DMA only (or combinations thereof - 0,1,3 being the useful ones I suspect) (I've split CF as it seems to be a seperate case of pain and suffering different to the others and caused by assorted PIO wired adapters etc) SATA is not affected - for one its not clear it makes sense to disable DMA for SATA if even always possible, for two we've seen no failure evidence to justify needing to support this kind of hammer on SATA. Signed-off-by: Alan Cox <[EMAIL PROTECTED]> Acked-by: Tejun Heo <[EMAIL PROTECTED]> FWIW -- as I noted to Alan personally at KS, I would rather drop the "pata_" and have it apply to all, PATA or SATA. It is far less useful on SATA, but I can still see a possibility that somebody might want to avoid DMA for whatever reason, chiefly, possibly keeping failing hardware alive by slowing things down via PIO. And being able to avoid the DMA protocols can be useful for debugging or other things. As an aside, it would be nice to get the EH in shape where it can pause all ports, so we can finally allow userspace to submit SET FEATURES - XFER MODE and have it handled cleanly and properly. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: ICH Intel PATA short cable override...
Mark Lord wrote: Ditto for selecting transfer modes. Waiting on one thing AFAICS: ability to drain/idle all ports + issue a command on one port + resume normal parallel port operation SET FEATURES - XFER MODE is special in that it requires all sorts of additional controller handling and careful cross-port synchronization. Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai
>-Original Message-
>From: Jeff Garzik [mailto:[EMAIL PROTECTED]
>Sent: Friday, September 07, 2007 3:39 PM
>To: Gaston, Jason D
>Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED]
>Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch
for
>Intel Tolapai
>
>Gaston, Jason D wrote:
>>> -Original Message-
>>> From: Gaston, Jason D
>>> Sent: Friday, August 31, 2007 10:10 AM
>>> To: 'Jeff Garzik'
>>> Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED]
>>> Subject: RE: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch
>> for
>>> Intel Tolapai
>>>
>>> This device has both AHCI and RAID modes that use the ahci driver.
>> Only
>>> the RAID mode DID's are being added as the PCI class code support
will
>>> cover the AHCI mode. Looking at the Generic, PCI class code support
>>> section, it uses "board_ahci". I assumed that they should be the
same
>> as
>>> the generic class code support is working on this platform.
>>>
>>> Thanks,
>>>
>>> Jason
>>>
>>>
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 12:47 AM
To: Gaston, Jason D
Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED]
Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA
patch
>> for
Intel Tolapai
Jason Gaston wrote:
> Resend trying to remove 8-bit characters in the email.
>
> This patch adds the Intel Tolapai RAID controller DID's for SATA
>>> support.
> Signed-off-by: Jason Gaston <[EMAIL PROTECTED]>
>
> --- linux-2.6.23-rc4/drivers/ata/ahci.c.orig 2007-08-27
18:32:35.0 -0700
> +++ linux-2.6.23-rc4/drivers/ata/ahci.c 2007-08-28
>>> 16:58:11.0 -
0700
> @@ -411,6 +411,8 @@
> { PCI_VDEVICE(INTEL, 0x292f), board_ahci_pi }, /* ICH9M */
> { PCI_VDEVICE(INTEL, 0x294d), board_ahci_pi }, /* ICH9 */
> { PCI_VDEVICE(INTEL, 0x294e), board_ahci_pi }, /* ICH9M */
> + { PCI_VDEVICE(INTEL, 0x502a), board_ahci }, /* Tolapai */
> + { PCI_VDEVICE(INTEL, 0x502b), board_ahci }, /* Tolapai */
Why did you not use board_ahci_pi? Is the AHCI ports-implemented
register unreliable on this platform?
>>
>> Jeff,
>>
>> Do I need to change this to board_ahci_pi or is it ok to leave it at
>> board_ahci, which will be used by the AHCI class code devices?
>
>You are the one who needs to answer this question ;-)
>
>Most new Intel AHCI have a sane and reliable Ports-Implemented register
>value even across reset, unlike earlier ones or some clones. For
those,
>we use board_ahci_pi.
>
>If PI is not reliable across reset or if BIOS is absent (yes we care
>about that case, when we do our own PCI resume for example), then you
>should use board_ahci.
>
> Jeff
At this time, I don't have any way to test those particular DeviceID's
and I know that the AHCI mode DeviceID works by using the class code
support. So, I would like to just leave them at they are, if that is
ok.
Thanks,
Jason
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
RE: [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch for Intel Tolapai
>-Original Message-
>From: Jeff Garzik [mailto:[EMAIL PROTECTED]
>Sent: Friday, August 31, 2007 12:51 AM
>To: Gaston, Jason D
>Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED];
>[EMAIL PROTECTED]
>Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch
for
>Intel Tolapai
>
>Jason Gaston wrote:
>> Resend trying to remove 8-bit characters in the email.
>>
>> This patch adds the Intel Tolapai IDE mode SATA controller DID's.
>>
>> Signed-off-by: Jason Gaston <[EMAIL PROTECTED]>
>
>applied
Jeff,
I just noticed that the following section came through as spaces instead
of tabs. Do I need to resend a corrected version?
+static const struct piix_map_db tolapai_map_db = {
+.mask = 0x3,
+.port_enable = 0x3,
+.map = {
+/* PM PS SM SS MAP */
+{ P0, NA, P1, NA }, /* 00b */
+{ RV, RV, RV, RV }, /* 01b */
+{ RV, RV, RV, RV }, /* 10b */
+{ RV, RV, RV, RV },
+},
+};
+
Thanks,
Jason
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch for Intel Tolapai
Gaston, Jason D wrote:
-Original Message-
From: Jeff Garzik [mailto:[EMAIL PROTECTED]
Sent: Friday, August 31, 2007 12:51 AM
To: Gaston, Jason D
Cc: linux-ide@vger.kernel.org; [EMAIL PROTECTED];
[EMAIL PROTECTED]
Subject: Re: [PATCH 2.6.23-rc4][reRESEND] ata_piix: IDE mode SATA patch
for
Intel Tolapai
Jason Gaston wrote:
Resend trying to remove 8-bit characters in the email.
This patch adds the Intel Tolapai IDE mode SATA controller DID's.
Signed-off-by: Jason Gaston <[EMAIL PROTECTED]>
applied
Jeff,
I just noticed that the following section came through as spaces instead
of tabs. Do I need to resend a corrected version?
+static const struct piix_map_db tolapai_map_db = {
+.mask = 0x3,
+.port_enable = 0x3,
+.map = {
+/* PM PS SM SS MAP */
+{ P0, NA, P1, NA }, /* 00b */
+{ RV, RV, RV, RV }, /* 01b */
+{ RV, RV, RV, RV }, /* 10b */
+{ RV, RV, RV, RV },
+},
+};
that's always nice, yes :)
even better would be to run a script through #upstream, accomplishing
the same thing but for many drivers ;-)
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: [PATCH 2.6.23-rc4][reRESEND] ahci: RAID mode SATA patch for Intel Tolapai
Gaston, Jason D wrote: At this time, I don't have any way to test those particular DeviceID's and I know that the AHCI mode DeviceID works by using the class code support. So, I would like to just leave them at they are, if that is ok. Fine by me... Overall I'll follow "vendor's best advice" here :) Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
[PATCH 2.6.23-rc5] ata_piix: replace spaces with tabs
This patch removes some incorrect formatting spaces and replaces them with tabs.
Signed-off-by: Jason Gaston <[EMAIL PROTECTED]>
--- linux-2.6.23-rc5/drivers/ata/ata_piix.c.orig2007-09-07
17:11:55.0 -0700
+++ linux-2.6.23-rc5/drivers/ata/ata_piix.c 2007-09-07 17:13:24.0
-0700
@@ -445,15 +445,15 @@
};
static const struct piix_map_db tolapai_map_db = {
-.mask = 0x3,
-.port_enable = 0x3,
-.map = {
-/* PM PS SM SS MAP */
-{ P0, NA, P1, NA }, /* 00b */
-{ RV, RV, RV, RV }, /* 01b */
-{ RV, RV, RV, RV }, /* 10b */
-{ RV, RV, RV, RV },
-},
+ .mask = 0x3,
+ .port_enable = 0x3,
+ .map = {
+ /* PM PS SM SS MAP */
+ { P0, NA, P1, NA }, /* 00b */
+ { RV, RV, RV, RV }, /* 01b */
+ { RV, RV, RV, RV }, /* 10b */
+ { RV, RV, RV, RV },
+ },
};
static const struct piix_map_db *piix_map_db_table[] = {
-
To unsubscribe from this list: send the line "unsubscribe linux-ide" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
I decided to put the Norco 4618 card into the first PCI slot of my DS20. It and the PMP support seem to like that location much better - I'm successfully creating an array at the moment (with not much apparent slowdown to the system). I was able to move the graphics card to another slot (which for a period in the past was also limited to the first PCI slot). Maybe this will make sense to some folks out there - thanks! ...tom Jeff Garzik wrote: Tom Evans wrote: Have you heard of such and issue with the 3124-2/4276 combination? Is anyone else trying this driver on an Alpha? Alpha should not be operationally much different from other little endian 64-bit platforms. The PCI swizzle might be weird (what is your Alpha platform?), is the only Alpha-specific thing that comes to mind. I have similar such behavior before when using drivers that generate many unaligned accesses - I only have seen 2 places they occur in sata_sil24 and have fixed them myself, but that made no difference. We definitely want to fix all these you find. Please post more info... Also, if you are highly motivated, I would love to see if other SATA cards have similar problems on Alpha... Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
I decided to put the Norco 4618 card into the first PCI slot of my DS20. It and the PMP support seem to like that location much better - I'm successfully creating an array at the moment. The system still responds, but accessing currently running filesystems (another array and the local scsi boot disk) seems to "freeze" for 20-30 seconds. I was able to move the graphics card to another slot (which for a period in the past was also limited to the first PCI slot). Maybe this will make sense to some folks out there - thanks! ...tom Jeff Garzik wrote: Tom Evans wrote: Have you heard of such and issue with the 3124-2/4276 combination? Is anyone else trying this driver on an Alpha? Alpha should not be operationally much different from other little endian 64-bit platforms. The PCI swizzle might be weird (what is your Alpha platform?), is the only Alpha-specific thing that comes to mind. I have similar such behavior before when using drivers that generate many unaligned accesses - I only have seen 2 places they occur in sata_sil24 and have fixed them myself, but that made no difference. We definitely want to fix all these you find. Please post more info... Also, if you are highly motivated, I would love to see if other SATA cards have similar problems on Alpha... Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
I decided to put the Norco 4618 card into the first PCI slot of my DS20. It and the PMP support seem to like that location much better - I'm successfully creating an array at the moment. The system still responds, but accessing currently running filesystems (another array and the local scsi boot disk) seems to "freeze" for 20-30 seconds. I was able to move the graphics card to another slot (which for a period in the past was also limited to the first PCI slot). Maybe this will make sense to some folks out there - thanks! ...tom Jeff Garzik wrote: Tom Evans wrote: Have you heard of such and issue with the 3124-2/4276 combination? Is anyone else trying this driver on an Alpha? Alpha should not be operationally much different from other little endian 64-bit platforms. The PCI swizzle might be weird (what is your Alpha platform?), is the only Alpha-specific thing that comes to mind. I have similar such behavior before when using drivers that generate many unaligned accesses - I only have seen 2 places they occur in sata_sil24 and have fixed them myself, but that made no difference. We definitely want to fix all these you find. Please post more info... Also, if you are highly motivated, I would love to see if other SATA cards have similar problems on Alpha... Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
I decided to put the Norco 4618 card into the first PCI slot of my DS20. It and the PMP support seem to like that location much better - I'm successfully creating an array at the moment. The system still responds, but accessing currently running filesystems (another array and the local scsi boot disk) seems to "freeze" for 20-30 seconds. I was able to move the graphics card to another slot (which for a period in the past was also limited to the first PCI slot). Maybe this will make sense to some folks out there - thanks! ...tom Jeff Garzik wrote: Tom Evans wrote: Have you heard of such and issue with the 3124-2/4276 combination? Is anyone else trying this driver on an Alpha? Alpha should not be operationally much different from other little endian 64-bit platforms. The PCI swizzle might be weird (what is your Alpha platform?), is the only Alpha-specific thing that comes to mind. I have similar such behavior before when using drivers that generate many unaligned accesses - I only have seen 2 places they occur in sata_sil24 and have fixed them myself, but that made no difference. We definitely want to fix all these you find. Please post more info... Also, if you are highly motivated, I would love to see if other SATA cards have similar problems on Alpha... Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
I decided to put the Norco 4618 card into the first PCI slot of my DS20. It and the PMP support seem to like that location much better - I'm successfully creating an array at the moment. The system still responds, but accessing currently running filesystems (another array and the local scsi boot disk) seems to "freeze" for 20-30 seconds. I was able to move the graphics card to another slot (which for a period in the past was also limited to the first PCI slot). Maybe this will make sense to some folks out there - thanks! ...tom Jeff Garzik wrote: Tom Evans wrote: Have you heard of such and issue with the 3124-2/4276 combination? Is anyone else trying this driver on an Alpha? Alpha should not be operationally much different from other little endian 64-bit platforms. The PCI swizzle might be weird (what is your Alpha platform?), is the only Alpha-specific thing that comes to mind. I have similar such behavior before when using drivers that generate many unaligned accesses - I only have seen 2 places they occur in sata_sil24 and have fixed them myself, but that made no difference. We definitely want to fix all these you find. Please post more info... Also, if you are highly motivated, I would love to see if other SATA cards have similar problems on Alpha... Jeff - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
Re: Port Multiplier Patch 2.6.22.1 on Alpha
Sorry about the spam - said system is my mail server and the mail program, although I though had timed-out the sends still got the messages thru. ...tom - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
