From: Jeff Garzik <jgarzik@pobox.com>
To: "Oliver M. Bolzer" <oliver@gol.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-t9 libata: Promise FastTrak S150 TX4 not working
Date: Mon, 27 Oct 2003 11:57:30 -0500 [thread overview]
Message-ID: <20031027165730.GC19711@gtf.org> (raw)
In-Reply-To: <20031027151505.GB10432@magi.fakeroot.net>
On Mon, Oct 27, 2003 at 04:15:05PM +0100, Oliver M. Bolzer wrote:
> Several weeks ago, I tested without success the 2.4.22-bk32-libata1
> patch with my Promise FastTrak S150 TX4 controller. Seeing that
> 2.6.0-test9 merged libata, I tryed again, without success.
>
> 4 drives are connected to the controller and are configured as 4
> seperate arrays (the thing doesn't have a non-RAID-mode) that are
> working with Promise's partially-binary-only ft3xx driver on 2.4.22.
>
> Below are the contents of /proc/pci on the machine and dmesg output
> with ATA_DEBUG and ATA_VERBOSE_DEBUG enabled. As it seemed that it
> could not soft-reset the ports, I also compiled the driver without
> the ATA_FLAG_SRST flag for my controller. It looks like the driver
> can recognize the arrays this way but then the kernel enters some
> kind of endless-loop after DMA timeouts. The dmesg output without
> ATA_FLAG_SRST ist also included below.
>
> In both cases, the actual error seems to be
> ATA: abnormal status 0x80 on port 0xF881321C
>
> As I got 8 identical machines with only 3 currenly in beta-use, I'm
> ready to test any kind of patches to help improve the driver.
Wow, this is an excellent bug report.
Yes, it looks like I will need to use a Promise-specific reset
mechanism, rather than one of the three generic mechanisms:
EXECUTE DEVICE DIAGNOSTIC (no flags), ATA software reset
(ATA_FLAG_SRST), and Serial ATA COMRESET (ATA_FLAG_SATA_RESET).
I would prefer to switch both VIA and Promise drivers over to
ATA_FLAG_SATA_RESET.
Jeff
prev parent reply other threads:[~2003-10-27 16:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 15:15 2.6.0-t9 libata: Promise FastTrak S150 TX4 not working Oliver M. Bolzer
2003-10-27 16:57 ` Jeff Garzik [this message]
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=20031027165730.GC19711@gtf.org \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oliver@gol.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.