Hi,
I'd like to bring to your attention an article that claims the Pioneer
DVR-111 drive doesn't work with libata because the drive needs the
nodma option:
http://apcmag.com/6415/first_look_at_fedora_core_7
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=242956
The drive was released
If PORTS_IMPL register is zero, ahci initialize it to full mask
corresponding to nr_ports in the CAP register. hpriv-cap, which is
initialized at the end of the function, is incorrectly used as value
of CAP causing ahci to always override PORTS_IMPL to 0x1 if it's zero.
Fix it.
This fixes a bug
On Tue, 19 Jun 2007 01:55:38 -0700 (PDT)
Vlad [EMAIL PROTECTED] wrote:
I'd like to bring to your attention an article that claims the Pioneer
DVR-111 drive doesn't work with libata because the drive needs the
nodma option:
http://apcmag.com/6415/first_look_at_fedora_core_7
Hello.
[EMAIL PROTECTED] wrote:
I think reading the IDE status register clears the interrupt in the IDE
device, which might be causing the drive to think it's OK to generate
another interrupt.
This is not how IDE drives are supposed to act -- they won't proceed any
further until interrupt
Hello.
Alan Cox wrote:
I can prepare a patch, but only with a lot of guidance. I can test
debug, I'm highly motivated just right now ...
If you've got a nice repeatable problem please try using the libata
driver. That handles the error paths differently and doesn't try a FIFO
drain which
On Tue, 19 Jun 2007 18:10:04 +0400
Sergei Shtylyov [EMAIL PROTECTED] wrote:
Hello.
Alan Cox wrote:
I can prepare a patch, but only with a lot of guidance. I can test
debug, I'm highly motivated just right now ...
If you've got a nice repeatable problem please try using the libata
Alan Cox wrote:
I can prepare a patch, but only with a lot of guidance. I can test
debug, I'm highly motivated just right now ...
If you've got a nice repeatable problem please try using the libata
driver. That handles the error paths differently and doesn't try a FIFO
drain which might
On Mon, Jun 18, 2007 at 04:22:38PM -0500, linas wrote:
On Mon, Jun 18, 2007 at 10:04:41PM +0100, Alan Cox wrote:
please try using the libata
driver.
Its worse. I get a hard hang (sysrq doesn't work) during boot,
just when the system goes to read the partition table.
Recap: this is an
Hi Sergei,
On Tue, Jun 19, 2007 at 06:07:07PM +0400, Sergei Shtylyov wrote:
[EMAIL PROTECTED] wrote:
I think reading the IDE status register clears the interrupt in the IDE
device, which might be causing the drive to think it's OK to generate
another interrupt.
This is not how IDE
Sergei Shtylyov wrote:
Alan Cox wrote:
I can prepare a patch, but only with a lot of guidance. I can test
debug, I'm highly motivated just right now ...
If you've got a nice repeatable problem please try using the libata
driver. That handles the error paths differently and doesn't try a
Mark Lord wrote:
I can prepare a patch, but only with a lot of guidance. I can test
debug, I'm highly motivated just right now ...
If you've got a nice repeatable problem please try using the libata
driver. That handles the error paths differently and doesn't try a
FIFO
drain which might
Hello.
Linas Vepstas wrote:
[EMAIL PROTECTED] wrote:
I think reading the IDE status register clears the interrupt in the IDE
device, which might be causing the drive to think it's OK to generate
another interrupt.
This is not how IDE drives are supposed to act -- they won't proceed any
Alan Cox wrote:
Indeed... but the thing is we don't know what's asserted in this case
-- remember, it's reading the status register that locks everything up...
Exactly. And IORDY shouldn't really apply there,
unless some nitwit standards person wrote it into a spec..
Could it be we need
On Tue, Jun 19, 2007 at 08:10:25PM +0400, Sergei Shtylyov wrote:
I'm thinking that trying to debug libata is a better idea, rather than
investing time in ide, right? Although at the moment, libata works even
less; see other email.
Which makes me think this really is some *hardware*
Hello
I'm making a backup of some disks with dd (disk image) and sata_promise
reported these errors:
--
ata8.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
ata8.00: cmd
Vlad wrote:
Hi,
I'd like to bring to your attention an article that claims the Pioneer
DVR-111 drive doesn't work with libata because the drive needs the
nodma option:
Not on my systems -- works fine.
-
To unsubscribe from this list: send the line unsubscribe linux-ide in
the body of a
Hi,
On Tuesday 19 June 2007, Linas Vepstas wrote:
On Tue, Jun 19, 2007 at 08:10:25PM +0400, Sergei Shtylyov wrote:
I'm thinking that trying to debug libata is a better idea, rather than
investing time in ide, right? Although at the moment, libata works even
less; see other email.
This patch applies some trivial cleanups to sata_promise:
- repair whitespace damage
- correct comment at board_2057x_pata definition
- pull SATAII TX4 support code out to separate functions
- rename ata_nr to ata_no for consistency with libata's port_no
- remove some init-time debug printks
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 hotplugging (insertion)
on the
Bartlomiej Zolnierkiewicz wrote:
There are two distinct issues.
-- libata locks up in partition table read on an hpt366+old maxtor disk
that has ben working fine for many years with old ide driver. (It
still works fine when I boot to the alternate ide-based kernel).
-- ide driver locks up
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 external drive bay that
21 matches
Mail list logo
