Hi Mark,
I was looking at the features on a new 320GB 2.5 SATA2 disk and
finding the current hdparm 7.7 doesn't recognise a couple of features
[1]. I dumped the raw identify data [2], if it is of use.
Also, do you know what tools to use to set a drive password and unlock
the drive at boot-time,
Here is the updated patch according your comments:
From af124a0fd4984db4fbc8638e0af4e6a41561588d Mon Sep 17 00:00:00 2001
From: Saeed Bishara [EMAIL PROTECTED]
Date: Sun, 2 Dec 2007 10:43:10 +0200
Subject: [PATCH] sata_mv: Remove PCI dependency
The integrated SATA controller is connected
On Wed, 2008-01-09 at 14:13 +0900, Tejun Heo wrote:
James Bottomley wrote:
Also, DMA alignment at
block layer isn't enough for ATA. ATA needs drain buffers for ATAPI
commands with variable length response. :-(
OK, where is this in the libata code? The dma_pad size is only 4 bytes,
Daniel J Blueman wrote:
Hi Mark,
I was looking at the features on a new 320GB 2.5 SATA2 disk and
finding the current hdparm 7.7 doesn't recognise a couple of features
[1]. I dumped the raw identify data [2], if it is of use.
Also, do you know what tools to use to set a drive password and
Hello, all.
Broken MWDMA on pata_ali has caused a number of bug reports. I've been
trying to fix it for some time now finally got a machine with
pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago.
Testing confirms what users have been reporting - MWDMA2 works fine
with the
Oh... I forgot to mention something.
I traced DMA command execution and the following is what happens.
1. host setups DMA engine (programs BMDMA controller)
2. host issues PACKET
3. device sets BSY
4. host transfers CDB when BSY clears and DRQ sets (Status turns to 0xd0)
5. host activates BMDMA
trying to fix it for some time now finally got a machine with
pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago.
Oh good. I've been through a pile of ones that just work.
Which North and south does it have and what revision ?
I walked through IDE and libata codes and
Are you really sure that the old IDE is actually issuing DMA commands,
rather than falling back to PIO ?
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
Tejun Heo wrote:
Hello, all.
Broken MWDMA on pata_ali has caused a number of bug reports. I've been
trying to fix it for some time now finally got a machine with
pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago.
Testing confirms what users have been reporting - MWDMA2
On Wed, 9 Jan 2008 17:16:35 +
Alan Cox [EMAIL PROTECTED] wrote:
trying to fix it for some time now finally got a machine with
pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago.
Oh good. I've been through a pile of ones that just work.
Which North and south
HNY. :-)
Bartlomiej Zolnierkiewicz wrote:
* Move wait_hwif_ready() documentation before this function.
* Fix trailing whitespaces.
* s/wait-for-busy/wait-for-non-busy/
* Remove no longer valid comment about the current code behavior.
* Docbook-ize it.
* Rename wait_hwif_ready()
Hi, I wrote:
* Move wait_hwif_ready() documentation before this function.
* Fix trailing whitespaces.
* s/wait-for-busy/wait-for-non-busy/
* Remove no longer valid comment about the current code behavior.
* Docbook-ize it.
* Rename wait_hwif_ready() to ide_port_wait_ready().
On Wednesday 09 January 2008 03:41:16 Tejun Heo wrote:
Ondrej Zary wrote:
Hello,
I switched to libata drivers for my onboard PATA controller (PIIX4)
recently. Everything works fine except that kernel tries to start not
only my hard drive (sda) but also LS-120 floppy drive (sdb) which does
Hi all,
Here is the resend (aka v4) version of the OF-platform PATA
driver and related patches.
Changes since v3:
- Acked-by: Paul Mundt [EMAIL PROTECTED]
- In the powerpc specific patch: update defconfig and use
machine_device_initcall -- this is new call found in the
galak/powerpc.git.
This patch adds ATAPI DMA support for HT1000 (aka BCM5785) HT1100 (aka
BCM11000) SATA Controller.
Signed-off-by: Anantha Subramanyam [EMAIL PROTECTED]
---
--- linux-2.6.23.11/drivers/ata/sata_svw.c.orig 2008-01-07
05:22:29.0 -0800
+++ linux-2.6.23.11/drivers/ata/sata_svw.c
This patch adds localbus and pata nodes to use CF IDE interface
on MPC8349E-mITX boards.
Patch also updates defconfig and adds some code to probe localbus.
Signed-off-by: Anton Vorontsov [EMAIL PROTECTED]
Acked-by: Olof Johansson [EMAIL PROTECTED]
---
arch/powerpc/boot/dts/mpc8349emitx.dts
Split pata_platform_{probe,remove} into two pieces:
1. pata_platform_{probe,remove} -- platform_device-dependant bits;
2. __ptata_platform_{probe,remove} -- device type neutral bits.
This is done to not duplicate code for the OF-platform driver.
Signed-off-by: Anton Vorontsov [EMAIL PROTECTED]
-Original Message-
From: Tejun Heo [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 08, 2008 9:34 PM
To: Gaston, Jason D
Cc: Tom Evans; linux-ide@vger.kernel.org
Subject: Re: SATA PMP support in 2.6.24-rc3?
Gaston, Jason D wrote:
For reference, here is the dmesg output from the
On Tue, 2008-01-08 at 11:39 +1100, Rusty Russell wrote:
On Tuesday 08 January 2008 02:48:23 James Bottomley wrote:
We're always open to new APIs (or more powerful and expanded old ones).
The way we've been doing the sg_chain conversion is to slide API layers
into the drivers so sg_chain
Hi Tejun,
On Wednesday 09 January 2008, Tejun Heo wrote:
Hello, all.
Broken MWDMA on pata_ali has caused a number of bug reports. I've been
trying to fix it for some time now finally got a machine with
pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago.
Testing
It works.
Boot log is attached.
I ran mke2fs on all 4 drives simultaneously and all is . I did notice
that DMA was disabled on the hardware? Do you need any info from my side
for this?
Should device node sdf on the 5th port exist even though no drive is
installed on the 5th port?
Thanks
cat
Hi,
On Sunday 06 January 2008, George Kibardin wrote:
Signed-off-by: George Kibardin [EMAIL PROTECTED]
--- drivers/ide/ide-iops.c.orig 2008-01-03 18:35:23.0 +0300
+++ drivers/ide/ide-iops.c 2008-01-03 18:12:29.0 +0300
@@ -612,12 +612,12 @@
Signed-off-by: Bartlomiej Zolnierkiewicz [EMAIL PROTECTED]
---
drivers/ide/pci/aec62xx.c |1 -
drivers/ide/pci/alim15x3.c |1 -
drivers/ide/pci/amd74xx.c |3 ---
drivers/ide/pci/atiixp.c |4
drivers/ide/pci/cmd640.c |4
Hi Anton,
Juts one small trivial comment (could be fixed later).
On Wed, 9 Jan 2008 22:10:41 +0300 Anton Vorontsov [EMAIL PROTECTED] wrote:
+static struct of_device_id pata_of_platform_match[] = {
This could be declared const.
--
Cheers,
Stephen Rothwell[EMAIL PROTECTED]
From: Ondrej Zary [EMAIL PROTECTED]
Prevent libata from starting/stopping non-ATA devices (like ATAPI floppy
drives) as they don't seem to like it:
sd 1:0:1:0: [sdb] Starting disk
ata2.01: configured for PIO2
sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
sd 1:0:1:0: [sdb] Sense Key :
I stopped seeing this message when I started using rc4.
I upgraded to rc7 with your patch - the dmesg is attached.
The link speed seems limited to 1.5Gbps now though, which hasn't been
the case in rc3-rc6.
...tom
-Original Message-
From: Tejun Heo [mailto:[EMAIL PROTECTED]
Sent:
On Thu, Jan 10, 2008 at 10:40:48AM +1100, Stephen Rothwell wrote:
Hi Anton,
Juts one small trivial comment (could be fixed later).
On Wed, 9 Jan 2008 22:10:41 +0300 Anton Vorontsov [EMAIL PROTECTED] wrote:
+static struct of_device_id pata_of_platform_match[] = {
This could be
Tejun Heo wrote:
How about putting a bunch of printks inside the interrupt handler? That
would tell us if it's even reaching the interrupt handler..
If you give me a patch, I'll apply it and cause lock up and report the
result. Just shoot the patches my way. But maybe reproducing the lock
up
Thomas Evans wrote:
I stopped seeing this message when I started using rc4.
I upgraded to rc7 with your patch - the dmesg is attached.
The link speed seems limited to 1.5Gbps now though, which hasn't been
the case in rc3-rc6.
So, yours works fine w/o the patch, right?
--
tejun
-
To
Gaston, Jason D wrote:
I am using a Sans Digital PMP, which has a Sil3726CBHU controller in it.
I also have an Addonics PMP and it has the same controller in it.
Hmmm... I wonder why all SIMG PMPs I have work just fine. :-(
Anyways, can you please test the patch I posted on the other thread
Hello, Andrew.
Andrew Ryder wrote:
It works.
Boot log is attached.
Great!
I ran mke2fs on all 4 drives simultaneously and all is . I did notice
that DMA was disabled on the hardware? Do you need any info from my side
for this?
Should device node sdf on the 5th port exist even though
Tejun Heo wrote:
From: Ondrej Zary [EMAIL PROTECTED]
Prevent libata from starting/stopping non-ATA devices (like ATAPI floppy
drives) as they don't seem to like it:
sd 1:0:1:0: [sdb] Starting disk
ata2.01: configured for PIO2
sd 1:0:1:0: [sdb] Result: hostbyte=0x00 driverbyte=0x08
sd
http://bugzilla.kernel.org/show_bug.cgi?id=9673
ACPI _PS3 cause S4 breaks in the second attempt. The system has a _PS3
method for IDE, which will call into SMM mode. Currently we haven't clue
why just the second attempt fails, as it's totally in BIOS code, so
blacklist the system so far for
Hello,
Bartlomiej Zolnierkiewicz wrote:
I wondered whether the device was configured differently, so compared
hdparm --Istdout results. They were identical too. (attached)
ATA device, with non-removable media
Model Number: IC25N040ATMR04-0
Serial Number:
Alan Cox wrote:
trying to fix it for some time now finally got a machine with
pata_ali and non-working MWDMA2 ATAPI device on my desk a few weeks ago.
Oh good. I've been through a pile of ones that just work.
Which North and south does it have and what revision ?
Attached full output of
Mark Lord wrote:
Are you really sure that the old IDE is actually issuing DMA commands,
rather than falling back to PIO ?
Yeap, pretty sure. Here is debug dump of IDE transferring sector zero.
[ 114.377898] XXX writing 0x8 to dma_cmd
[ 114.381718] XXX read dma_stat 0x24 and writing 0x26
[
On Thursday 10 January 2008 09:10:37 James Bottomley wrote:
On Tue, 2008-01-08 at 11:39 +1100, Rusty Russell wrote:
On Tuesday 08 January 2008 02:48:23 James Bottomley wrote:
We're always open to new APIs (or more powerful and expanded old ones).
The way we've been doing the sg_chain
Hello, Sergei.
Sergei Shtylyov wrote:
Heh, it works by accident: PIO4 timings correspond to MWDMA ones. The
driver does *not* support MWDMA modes -- there's FIXME in
ali_set_dma_mode().
Yeap, I saw that and lifted MWDMA programming from pata_ali. That's how
I got the identical PCI
On Wed, 9 Jan 2008 18:36:34 -0600 Olof Johansson [EMAIL PROTECTED] wrote:
On Thu, Jan 10, 2008 at 10:40:48AM +1100, Stephen Rothwell wrote:
Hi Anton,
Juts one small trivial comment (could be fixed later).
On Wed, 9 Jan 2008 22:10:41 +0300 Anton Vorontsov [EMAIL PROTECTED] wrote:
Gaston, Jason D wrote:
Attached are two dmesg outputs from 2.6.24-rc7 with only this simg quirk
patch applied.
The first (dmesg_wSipatch) was generated with the PMP turned off during
boot and then powered on, while connected to eSATA.
The second (dmesg_poweronoff) was generated with the
Tejun Heo wrote:
Please apply the attached patch on top of 2.6.24-rc7 and report the
result. Thanks.
Andrew, with the patch applied, please try to turn off and on the PMP
array while the system is running and verify that each time the array
gets detected correctly and disks are accessible.
On Thu, Jan 10, 2008 at 02:47:33AM +, Matthew Hall wrote:
I am using the Supermicro H8DCE motherboard. Some (not all) of the SATA
channels quit working due to some kind of resource conflict when I
upgrade to any kernel above 2.6.20.xx series, in my case I am running
2.6.20.21 SMP x86_64
Tejun,
I rebooted with the 4726 online during bootup, verified everything was
there by re-formatting the fs on each drive. I powered off the 4726 for
approx 15 seconds, turned it back on, and repeated the power on/off
again about 1 minute later.
The first 3 drives are accessible, but the 4th
Hello,
Kasimir Müller wrote:
thanks very much again for your time and readiness to help.
I applied the patch as you proposed without problem.
I attach the kernel logs of the past few days. As far as I can see, with
the patched kernel errors appear only under heavy load .
If you want, I
Andrew Ryder wrote:
Tejun,
I rebooted with the 4726 online during bootup, verified everything was
there by re-formatting the fs on each drive. I powered off the 4726 for
approx 15 seconds, turned it back on, and repeated the power on/off
again about 1 minute later.
The first 3 drives are
saeed bishara wrote:
Here is the updated patch according your comments:
From af124a0fd4984db4fbc8638e0af4e6a41561588d Mon Sep 17 00:00:00 2001
From: Saeed Bishara [EMAIL PROTECTED]
Date: Sun, 2 Dec 2007 10:43:10 +0200
Subject: [PATCH] sata_mv: Remove PCI dependency
The integrated SATA
Matthew,
On Wed, Jan 09, 2008 at 08:39:45PM -0700, Matthew Wilcox wrote:
On Thu, Jan 10, 2008 at 02:47:33AM +, Matthew Hall wrote:
I am using the Supermicro H8DCE motherboard. Some (not all) of the SATA
channels quit working due to some kind of resource conflict when I
upgrade to any
4726 hates SRST even on non-config ports. Don't use it.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
drivers/ata/libata-pmp.c | 12 +---
1 file changed, 5 insertions(+), 7 deletions(-)
diff --git a/drivers/ata/libata-pmp.c b/drivers/ata/libata-pmp.c
index c0c4dbc..caef2bb 100644
Matthew Hall wrote:
ACPI: PCI Interrupt Link [LT3D] enabled at IRQ 46
ACPI: PCI Interrupt :80:07.0[A] - Link [LT3D] - GSI 46 (level,
low) - IRQ 46
sata_nv :80:07.0: Using ADMA mode
PCI: Unable to reserve mem region #6:[EMAIL PROTECTED] for device
:80:07.0
ACPI: PCI interrupt for
Timeout on downstream command may indicate transmission problem on
host link. Propagate timeouts to host link.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
drivers/ata/libata-eh.c | 20 +++-
1 file changed, 15 insertions(+), 5 deletions(-)
diff --git
Tejun Heo wrote:
Gwendal Grignou wrote:
Fix commands timeout with Sil3124/3132 based HBA when pass-through ATA
commands [where ATA_QCFLAG_RESULT_TF is set] are used while other
commands are active on other devices
connected to the same port with a Port Multiplier.
Due to a hardware bug, these
On Wed, Jan 09, 2008 at 11:40:47PM -0500, Jeff Garzik wrote:
Error -16 is EBUSY, which causes the driver load to fail due to the Unable
to reserve mem region message.
This means that the sata_nv driver needed to use PCI BAR 6, but was unable
to for some reason. Given that sata_nv uses
Matthew Hall wrote:
On Wed, Jan 09, 2008 at 11:40:47PM -0500, Jeff Garzik wrote:
Error -16 is EBUSY, which causes the driver load to fail due to the Unable
to reserve mem region message.
This means that the sata_nv driver needed to use PCI BAR 6, but was unable
to for some reason. Given
Tejun Heo wrote:
There still are remaining issues with ADMA support. Disable it by
default and warn when enabling.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
Jeff, please hold off till Robert acks. Robert, what do you think?
drivers/ata/sata_nv.c |5 -
1 file changed, 4
Hello, haven't fell asleep yet?
Jeff Garzik wrote:
Tejun Heo wrote:
There still are remaining issues with ADMA support. Disable it by
default and warn when enabling.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
Jeff, please hold off till Robert acks. Robert, what do you think?
Hello,
Andrew Ryder wrote:
This might be of interest.. I had turned the drive off for about 20
minutes, then turned it back on. ata1.03 is now partially there, it is
recognized as a device, but of 0MB in size.
All of this is done with the 4726 turned on..
Bootlog11.txt - I unplugged the
From: Gwendal Grignou [EMAIL PROTECTED]
Fix commands timeout with Sil3124/3132 based HBA when pass-through ATA
commands [where ATA_QCFLAG_RESULT_TF is set] are used while other
commands are active on other devices connected to the same port with a
Port Multiplier. Due to a hardware bug, these
Robert Hancock wrote:
However, how about putting in a printk in nv_adma_interrupt handler here:
/* freeze if hotplugged or controller error */
if (unlikely(status (NV_ADMA_STAT_HOTPLUG |
NV_ADMA_STAT_HOTUNPLUG |
NV_ADMA_STAT_TIMEOUT |
Ke Wei wrote:
The 88SE6440 driver :
The driver is based on bare code from Jeff Garzik. And it can work
under linux kernel 2.6.23.
By far, Can discover and find SAS HDD, but SATA is currently
unsupported. Command queue depth can be above 1.
Most error handling, and some phy handling code is
Jeff Garzik wrote:
1) To make it easier for people to review and test the driver, I would
suggest posting a diff against 2.6.24-rc7 (or 2.6.23), ignoring my
original code. Thus, it would result in a patch
Er, that sentence was incomplete. Continuing...
Thus it would result in a patch that
I'm sorry, I should have guessed !!
(I applied those little change to my code manually and then to the patch :)
Thanks,
George
-Original Message-
From: Bartlomiej Zolnierkiewicz [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 10, 2008 2:26 AM
To: George Kibardin
Cc:
61 matches
Mail list logo
