Alan Cox wrote:
On Fri, Jun 29, 2007 at 05:34:36PM +1000, Andrew Hall wrote:
Further to this the PATA to SATA bridge being used in this case is:
http://www.jmicron.com/JM20330.html
..as you will see only PIO and UDMA modes are supported.
In which case their microcontroller in the middle
Theo Baumgartner wrote:
Hello
I've got a sil3124 card which doesn't seem to use the full speed of my drives.
---
ata1: SATA max UDMA/100 cmd 0xe085 ctl 0x bmdma
Soeren Sonnenburg wrote:
Dear List,
since the switch to
CONFIG_ATA=y
CONFIG_ATA_ACPI=y
CONFIG_ATA_PIIX=y,
the ATA_PIIX driver manages both, internal sata disk aswell as cd/dvd
rom. However I am being flooded with the error messages below (well they
appear from time to time,
Mark wrote:
Can I ignore them (EH handled them) or do i have to worry that the dd images
are corrupted
(don't wanna make an md5sum of a 250gb disk and image)?
Yeah, data should be okay. All failed commands are retried.
I get the same errors with my Promise SATA300 TX4 with 3 Samsung SATA
Greetings,
I have been troubleshooting a problem for over a year now, and to make a
long story short, I think the sata_sil driver has a bug during writing when
there are multiple cards that are using different models of SiI chips in the
system.
I will be watching the list, although cc'ing me
Mikael Pettersson wrote:
This patch enables hotplugging of SATA devices in the
sata_promise driver. It's been tested successfully on
both first- and second-generation Promise SATA chips:
SATA150 TX2plus, SATAII150 TX2plus, SATA300 TX2plus,
and SATA300 TX4.
The only quirk I've seen is that
Jeff Gustafson wrote:
Hi all,
I found issue similar to the one I am having in the archive on this
list. I never found a resolution to the problem in the archive.
I have a 4-port Sil 3124 64-bit PCI-X card in a Dell PowerEdge 750. It
is connected to four SATA hard drives in an
Patrick Nagel wrote:
If I can be of help with more information, please tell me what you need.
Full dmesg including boot log would be a nice place to start. Did the
kernel say anything during or after such freezes?
--
tejun
-
To unsubscribe from this list: send the line unsubscribe linux-ide
Sergei Shtylyov wrote:
scsi 0:0:0:0: Direct-Access ATA ST3250620NS 3.AE PQ: 0
ANSI: 5
SCSI device sda: 488397168 512-byte hdwr sectors (250059 MB)
SCSI device sda: write cache: enabled, read cache: enabled, doesn't
support DPO or FUA
for SATA disk drives. And I wonder -- are
William Thompson wrote:
I'm not on either list, keep me in CC.
I noticed the following error on a cdrom device:
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: cmd a0/00:00:00:00:20/00:00:00:00:00/a0 tag 0 cdb 0x0 data 0
res
Matt Sealey wrote:
I'm a litle confused here.
Page 10 (4.2.1) so I just mask off bit 0 and bit 2 of the class prog-if byte
and set
it to compatible mode which will basically mean PCI mapped registers and
two IRQs? This corresponds with the table on Page 7 (4.2.1.1)..
Checked the Pegasos
Mikael Pettersson wrote:
ata2.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x2 frozen
ata2.00: cmd a0/01:00:00:00:00/00:00:00:00:00/a0 tag 0 cdb 0x12 data 36 in
res 40/00:00:00:00:00/00:00:00:00:00/00 Emask 0x4 (timeout)
This is hopefully fixed by using PIO for ATAPI data
Tejun Heo wrote:
Hello, all.
his is the fourth take of libata-pmp patchset. This patchset contains
15 patches and implements PMP support.
Hi Tejun,
Thanks once again. 2.6.22-rc6 + libata-tj-2.6.22-rc6-20070702 seems
to be working fine on my system (SiI3124 PCI-X + two SiI4726, plus
other
Chuck Ebbert wrote:
From:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245512
The following error consistently appears at apparently random intervals in
syslog:
kernel: ata1.00: exception Emask 0x2 SAct 0x1001 SErr 0x0 action 0x2 frozen
kernel: ata1.00: (spurious completions
Tejun Heo wrote:
Matt Sealey wrote:
I'm a litle confused here.
Page 10 (4.2.1) so I just mask off bit 0 and bit 2 of the class prog-if byte
and set
it to compatible mode which will basically mean PCI mapped registers and
two IRQs? This corresponds with the table on Page 7 (4.2.1.1)..
[EMAIL PROTECTED] wrote:
Greetings,
I have been troubleshooting a problem for over a year now, and to make a
long story short, I think the sata_sil driver has a bug during writing when
there are multiple cards that are using different models of SiI chips in
the
system.
I will be watching
We can't make the controller TRULY legacy since there is not any good way
of mapping the IDE/BMDMA registers into the lower kilobyte or so of
memory - obviously PPC has no io address space, it's all memory mapped,
so the lower kilobyte of IO ports is really the CPU zero page. It's not
a good
Well, let's put the class code as native since the chip is made native,
in a platform file somewhere. Then, we can have a configuration option in
the platform code which allows users to choose whether the IDE configuration
is reworked to steer to a single IRQ or two IRQs. That way they can choose
Yes but the libata driver doesn't check the config register, it checks
the class code, no?
--
Matt Sealey [EMAIL PROTECTED]
Genesi, Manager, Developer Relations
Jeff Garzik wrote:
Matt Sealey wrote:
The old Via driver checked the host controller configuration space,
rather
than trust the
Tejun Heo wrote:
host-irq and host-irq2 should be set before ata_host_register() for
IRQ reporting to work. Move up host-irq assignment in
ata_host_activate() and add it to ata_pci_init_one() native path and
pata_cs5520.
The port info printing in ata_host_register() doesn't fit all the
Florian Attenberger wrote:
Signed-off-by: Florian Attenberger [EMAIL PROTECTED]
--- 2.6.22-rc6/drivers/ata/sata_mv.c2007-06-30 16:21:47.462020256 +0200
+++ 2.6.22-rc6.mine/drivers/ata/sata_mv.c 2007-06-30 16:25:25.999165444
+0200
@@ -582,6 +582,9 @@ static const struct
Hello.
Bartlomiej Zolnierkiewicz wrote:
SWDMA modes are unsupported by it821x. Attempts to tune SWDMA modes always
fail (due to sanity check in -speedproc) and result in PIO being tuned.
* Fix incorrect SWDMA mask so core code won't try these modes and will just
tune PIO if no other DMA
Chuck Ebbert wrote:
This patch was found to fix some of the problems with the
pata_ali driver. Is it going to be merged in 2.6.22?
[https://bugzilla.redhat.com/bugzilla/attachment.cgi?id=156482]
applied
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a
Jose Alberto Reguero wrote:
This patch add support to Marvell 6121.
Looking at the code I think that AHCI_FLAG_MV_PATA flag must be assigned to
the PATA port.
Signed-off-by: Jose Alberto Reguero [EMAIL PROTECTED]
applied, thanks
-
To unsubscribe from this list: send the line unsubscribe
Olof Johansson wrote:
CONFIG_PM=n compile fix.
Signed-off-by: Olof Johansson [EMAIL PROTECTED]
---
Hi,
On Sat, May 26, 2007 at 11:09:54PM -0400, Jeff Garzik wrote:
This is checked into the 'mv-ahci-pata' branch of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
Mikael Pettersson wrote:
sil24_interrupt() loads host-ports[i] into a local variable,
validates it, and then loads the value again in the call to
sil24_host_intr(). This patch replaces the second load by a
reference to the local variable.
This is safe since no side-effects have occurred since
Chr wrote:
Hi,
I got a new laptop and I had a little problem that the DVD drive wasn't
recognized by
libata's piix driver (but the old IDE Subsystem found it!!).
So, after adding the new pciid 8086:2850 it works!
But, I don't know if it's ich_pata_100 or ich_pata_133 since the
dvd/cd drives
Tejun Heo wrote:
Update formatting for LLD provided error descriptions such that...
* No default () around it
* Each element is separated by not ,
This change makes each element responsible for putting a space after
itself instead of before - e.g. elem not , elem. This is more
conventional
Tejun Heo wrote:
+++ b/include/linux/libata.h
@@ -322,7 +322,8 @@ enum ata_completion_errors {
AC_ERR_SYSTEM = (1 6), /* system error */
AC_ERR_INVALID = (1 7), /* invalid argument */
AC_ERR_OTHER= (1 8), /* unknown */
-
Tejun Heo wrote:
Convert -scr_read/write callbacks to return error code to better
indicate failure. This will help handling of SCR_NOTIFICATION.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
ACK
but I do not look forward to merging this with #mv-eh :)
[my problem, not yours]
-
To unsubscribe
Tejun Heo wrote:
ahci_save_initial_config() is responsible for reading, screening the
host CAP register and storing the modified result into hpriv-cap for
the rest of the driver. Move ATA_FLAG_NO_NCQ handling into
ahci_save_initial_config(). It's more consistent this way and the
rest of the
Tejun Heo wrote:
ATA_EHI_HOTPLUGGED is a hint for reset functions indicating the the
port might have gone through hotplug/unplug just before entering EH.
Reset functions modify their behaviors a bit to handle the situation
better - e.g. using longer debouncing delay.
Currently, once HOTPLUG is
Tejun Heo wrote:
If SError isn't accessible, EH can't tell whether hotplug has happened
or not. Report SError read failure with AC_ERR_OTHER and schedule
probing with hardreset. This will be mainly useful for PMPs.
Signed-off-by: Tejun Heo [EMAIL PROTECTED]
---
drivers/ata/libata-eh.c |6
Jeff Garzik wrote:
Tejun Heo wrote:
+++ b/include/linux/libata.h
@@ -322,7 +322,8 @@ enum ata_completion_errors {
AC_ERR_SYSTEM= (1 6), /* system error */
AC_ERR_INVALID= (1 7), /* invalid argument */
AC_ERR_OTHER= (1 8), /* unknown */
-
Jeff Garzik wrote:
Tejun Heo wrote:
@@ -1698,12 +1705,13 @@ static void ahci_print_info(struct ata_host
*host)
dev_printk(KERN_INFO, pdev-dev,
flags:
- %s%s%s%s%s%s
- %s%s%s%s%s%s%s\n
+%s%s%s%s%s%s%s
+%s%s%s%s%s%s%s\n
Jeff Garzik wrote:
Tejun Heo wrote:
Update formatting for LLD provided error descriptions such that...
* No default () around it
* Each element is separated by not ,
This change makes each element responsible for putting a space after
itself instead of before - e.g. elem not , elem.
The HPT343/345 (aka 363) is a bit of a warped device. For many setups you
need to access the other registers via BAR4 offsets. PIO is now rock
solid, DMA isn't. Unfortunately the drivers/ide hpt34x driver is
completely broken so doesn't help further debug.
Signed-off-by: Alan Cox [EMAIL
Matt Sealey wrote:
Yes but the libata driver doesn't check the config register, it checks
the class code, no?
Talking about the end result...
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Jeff Garzik wrote:
Tejun Heo wrote:
In most cases, when EH is scheduled, all in-flight commands are
aborted causing EH to kick in immediately. However, in some cases
(especially with PMP), it's unclear which commands are affected by the
error condition and although aborting all in-flight
On Tue, 3 Jul 2007, Alan Cox wrote:
Chuck Ebbert (1):
pata_ali: fix UDMA settings
Could you please fix your git tree to have the proper credits for patches
you pull from bugzilla.
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242472
I don't think it is Jeff who needs
Hi,
On Sat, Jun 30, 2007 at 12:04:22AM +0400, Sergei Shtylyov wrote:
The HPT36x chips finally turned out to have the channel enable bits --
however,
badly implemented. Make use of them despite it's probably only going to
burden
the driver's code -- assuming both channels are always
On Fri, Jun 29, 2007 at 11:57:17PM +0400, Sergei Shtylyov wrote:
Add the MAXTOR STM3320620A drive into the UltraDMA/66 mode blacklist
for the HPT36x chips.
Signed-off-by: Sergei Shtylyov [EMAIL PROTECTED]
Acked-by: Linas Vepstas [EMAIL PROTECTED]
Applied tested it worked for me.
--linas
attribution. Probably because of some insane system he uses (he has a
comment in that bugzilla about patch from comment #14 is in CVS now..
CVS? What kind if insane setup do you have there at Red Hat?
CVS is used for tracking patch sets for RPMS rather than source trees.
Its quite good at
Hello.
Bartlomiej Zolnierkiewicz wrote:
* Add ATA_PIO[0-6] defines to linux/ata.h.
* Add -pio_mask field to ide_pci_device_t and ide_hwif_t.
* Add PIO masks to host drivers.
Hm, the next logical step would be to use the mask constants in
linux/ata.h for the drivers' DMA caps too...
Libata General with respect to PATA
Wrong port and IRQ reporting - IRQ now fixed by Tejun, port reporting
fixes sent to Andrew. All these are cosmetic and don't harm debug.
Still can't user set drive speed or user issue commands at a given speed.
Needed to
The new improved driver is not really better than the old one because
the old one is broken. :)
Old driver does identical configuration when it comes to PIO modes.
No the old driver doesn't even do that. It starts up. It spuriously
adjusts some non writable PCI BAR registers, prints a
Tejun Heo wrote:
Jim Paris wrote:
Tejun Heo wrote:
* Sil4726 is a bit too quirky. Without the first fan-out port
occupied, the thing acts really weirdly. As long as the first port
is occupied, it works okay.
I'll test the 4726 behavior with pulling disks etc including the
Bartlomiej Zolnierkiewicz wrote:
* Add IDE_HFLAG_ABUSE_{PREFETCH,FAST_DEVSEL,DMA_MODES} flags
and set them in ht6560, cmd640, cmd64x and sc1200 host drivers.
* Add set_pio_mode_abuse() for checking if host driver has a non-standard
-tuneproc() implementation and use it in do_special().
Bartlomiej Zolnierkiewicz wrote:
* Add -host_flags to ide_hwif_t to store ide_pci_device_t.host_flags,
assign it in setup-pci.c:ide_pci_setup_ports().
* Add IDE_HFLAG_PIO_NO_{BLACKLIST,DOWNGRADE} to ide_pci_device_t.host_flags
and teach ide_get_best_pio_mode() about them. Also remove
On Tuesday 03 July 2007, Albert Lee wrote:
Recently the PLL input clock of Promise 2027x is sometimes detected
higer than expected (e.g. 20.027 MHz compared to 16.714 MHz).
It seems sometimes the mdelay() function is not as precise as it
used to be. Per Alan's advice, HT or power management
On Tuesday 03 July 2007, Sergei Shtylyov wrote:
Hello.
Albert Lee wrote:
Recently the PLL input clock of Promise 2027x is sometimes detected
higer than expected (e.g. 20.027 MHz compared to 16.714 MHz).
^ h
It seems sometimes the mdelay() function is not as precise as it
used
On Tuesday 03 July 2007, Linas Vepstas wrote:
On Fri, Jun 29, 2007 at 11:57:17PM +0400, Sergei Shtylyov wrote:
Add the MAXTOR STM3320620A drive into the UltraDMA/66 mode blacklist
for the HPT36x chips.
Signed-off-by: Sergei Shtylyov [EMAIL PROTECTED]
Acked-by: Linas Vepstas [EMAIL
On Tuesday 03 July 2007, Linas Vepstas wrote:
Hi,
On Sat, Jun 30, 2007 at 12:04:22AM +0400, Sergei Shtylyov wrote:
The HPT36x chips finally turned out to have the channel enable bits --
however,
badly implemented. Make use of them despite it's probably only going to
burden
the
On Tuesday 03 July 2007, Sergei Shtylyov wrote:
Hello.
Bartlomiej Zolnierkiewicz wrote:
* Add ATA_PIO[0-6] defines to linux/ata.h.
* Add -pio_mask field to ide_pci_device_t and ide_hwif_t.
* Add PIO masks to host drivers.
Hm, the next logical step would be to use the mask
Please pull from:
master.kernel.org:/pub/scm/linux/kernel/git/bart/ide-2.6.git/
to receive the following updates:
drivers/ide/ide-probe.c|4 ++--
drivers/ide/ide-taskfile.c | 12
drivers/ide/pci/amd74xx.c |8 +++-
drivers/ide/pci/hpt366.c |
Tejun Heo wrote:
Michael Tokarev wrote:
[]
A test drive is Seagate Barracuda ST3250620AS desktop drive,
250Gb, cache size is 16Mb, 7200RPM.
[test shows that NCQ makes no difference whatsoever]
And which elevator?
Well. It looks like the results does not depend on the
elevator. Originally I
From: Christian Lamparter [EMAIL PROTECTED]
ATA: add a PCI ID for Intel Santa Rosa (ICH8M) PATA controller.
Signed-off-by: Christian Lamparter [EMAIL PROTECTED]
---
drivers/ata/ata_piix.c |2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/ata/ata_piix.c b/drivers/ata/ata_piix.c
On Tuesday 03 July 2007, Sergei Shtylyov wrote:
Bartlomiej Zolnierkiewicz wrote:
* Add -host_flags to ide_hwif_t to store ide_pci_device_t.host_flags,
assign it in setup-pci.c:ide_pci_setup_ports().
* Add IDE_HFLAG_PIO_NO_{BLACKLIST,DOWNGRADE} to ide_pci_device_t.host_flags
and
.bootable = ON_BOARD, \
.enablebits = { {0x40, 1, 1}, {0x40, 0x10, 0x10} }, \
+ .pio_mask = ATA_PIO5, \
}
Just noticed that this driver does nothing in its tuneproc() method. So,
this mask is
Tejun Heo [EMAIL PROTECTED] :
Francois Romieu wrote:
Tejun Heo [EMAIL PROTECTED] :
[...@
The port info printing in ata_host_register() doesn't fit all the
different controllers. It should probably be moved out to LLDs with
some helpers in the future.
Signed-off-by: Tejun Heo [EMAIL
On Tuesday 03 July 2007, Sergei Shtylyov wrote:
Hello.
Bartlomiej Zolnierkiewicz wrote:
http://www.linuxhq.com/kernel/v2.3/10/drivers/block/hpt343.c
Does anybody have DOS driver for HPT343? Google doesn't have it...
I have the drivers for HPT34[35] -- tried dissassembling them
Johny Mail list wrote:
This patch don't work in my case.
Please elaborate on don't work.
Especially with a 2.6.18.8 kernel.
Sorry but i don't understand when you say : you may need to patch the
patch to contain the correct PCI IDs (from lspci -n).
Where is the correct line in the patch to
Johny Mail list wrote:
2007/7/3, Tejun Heo [EMAIL PROTECTED]:
Brad Campbell wrote:
Johny Mail list wrote:
Hello list,
I have a little question about software RAID on Linux.
I have installed Software Raid on all my SC1425 servers DELL by
believing that the md raid was a strong driver.
And
On Tue, Jul 03, 2007 at 07:50:26PM +0200, Bartlomiej Zolnierkiewicz wrote:
Hi,
On Tuesday 03 July 2007, Michal Piotrowski wrote:
IDE
Subject: 2.6.22-rcX: hda: lost interrupt
References : http://lkml.org/lkml/2007/6/29/121
Submitter : David Chinner [EMAIL PROTECTED]
Status
On Wed, 4 Jul 2007, Hadmut Danisch wrote:
Hi,
just a question:
I have an older computer with a ASRock K7VT4A Pro mainboard and a VIA sata
controller.
A 320GB Seagate SATA disk worked pretty well with that board, but now I replaced
it with a 500GB Western Digital SATA, and the BIOS does not
Hello,
Michael Tokarev wrote:
Well. It looks like the results does not depend on the
elevator. Originally I tried with deadline, and just
re-ran the test with noop (hence the long delay with
the answer) - changing linux elevator changes almost
nothing in the results - modulo some random
Mark Lord wrote:
I believe he said it was ICH5 (different post/thread).
My observation on ICH5 is that if one unplugs a drive,
then the chipset/cpu locks up hard when toggling SRST
in the EH code.
Specifically, it locks up at the instruction
which restores SRST back to the non-asserted
Hadmut Danisch wrote:
Hi,
just a question:
I have an older computer with a ASRock K7VT4A Pro mainboard and a VIA sata
controller.
A 320GB Seagate SATA disk worked pretty well with that board, but now I
replaced
it with a 500GB Western Digital SATA, and the BIOS does not recognize
Tejun Heo writes:
Sounds awfully similar to the recent nvidia data corruption issue. It
was involving the IOMMU and one of the workarounds was not using IOMMU,
IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU
off by passing iommu=off as kernel parameter.
--
tejun
[EMAIL PROTECTED] wrote:
That indeed seems to have fixed the problem - I've been pulling my hair
out forever about this!
Is this something I'll need to leave in forever, is it supposed to get
fixed, etc.?
I'm going to continue doing testing and really try to thrash it tonight
(I just did the
Tejun Heo writes:
Sounds awfully similar to the recent nvidia data corruption issue. It
was involving the IOMMU and one of the workarounds was not using IOMMU,
IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU
off by passing iommu=off as kernel parameter.
--
tejun
On Jul 03, 2007, at 13:51:16, Alan Cox wrote:
Libata General with respect to PATA
[...snip...]
Chipsets
[...snip...]
I'd love to try to poke holes in the libata PATA support, but sadly
it doesn't look like any of my systems built-in ATA
[EMAIL PROTECTED] writes:
Tejun Heo writes:
Sounds awfully similar to the recent nvidia data corruption issue. It
was involving the IOMMU and one of the workarounds was not using IOMMU,
IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU
off by passing iommu=off as kernel
[EMAIL PROTECTED] wrote:
Tejun Heo writes:
Sounds awfully similar to the recent nvidia data corruption issue. It
was involving the IOMMU and one of the workarounds was not using IOMMU,
IIRC. Please turn off IOMMU and see what happens. You can turn IOMMU
off by passing iommu=off as kernel
Apologies for the chain-replying to myself, just replying as I think of
things to try.
[EMAIL PROTECTED] writes:
Here's an odd data point.
I just broke that array, formatted all three of those partitions
seperately, mounted and did my ISO copy test.
All three drives, run one at a
Alan Cox wrote:
Lots of BIOSen simply return the BIOS set modes via the ACPI methods and
pass back the values you give it across suspend/resume. Thus instead of
trying to do clever stuff with this data we instead use it as a way to
take a sneak peak at cable type information when viable. This
[EMAIL PROTECTED] wrote:
Apologies for the chain-replying to myself, just replying as I think of
things to try.
[EMAIL PROTECTED] writes:
Here's an odd data point.
I just broke that array, formatted all three of those partitions
seperately, mounted and did my ISO copy test.
All three
Krzysztof Oledzki wrote:
On 2007-07-03 09:42, Tejun Heo wrote:
Chuck Ebbert wrote:
From:
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=245512
The following error consistently appears at apparently random
intervals in syslog:
kernel: ata1.00: exception Emask 0x2 SAct 0x1001 SErr
Francois Romieu wrote:
I have rebuilt on top of 872aad45d6174570dd2e1defc3efee50f2cfcc72 and it
still seems bizarre:
[0.00] Linux version 2.6.22-rc7 ([EMAIL PROTECTED]) (gcc version
4.1.1 20070105 (Red Hat 4.1.1-51)) #13 Tue Jul 3 20:42:14 CEST 2007
[...]
[ 30.140053] input: AT
Tejun Heo wrote:
Francois Romieu wrote:
I have rebuilt on top of 872aad45d6174570dd2e1defc3efee50f2cfcc72 and it
still seems bizarre:
Okay, 872aad45 doesn't have the patch yet. Either apply the patch
manually or you need to wait a bit more.
--
tejun
-
To unsubscribe from this list: send the
80 matches
Mail list logo
