linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Peter Favrholdt <linux-ide@how.dk>
To: Mikael Pettersson <mikpe@it.uu.se>
Cc: linux-ide@vger.kernel.org
Subject: Re: Bug is fixed in 2.6.23.1: sata_promise: port is slow to respond, reset failed
Date: Mon, 15 Oct 2007 19:55:29 +0200	[thread overview]
Message-ID: <4713A991.3030308@how.dk> (raw)
In-Reply-To: <200710150821.l9F8LHdS025458@harpo.it.uu.se>

Hi

Mikael Pettersson wrote:
> However, I don't see how the sata_promise changes from 2.6.22 to 2.6.23
> can explain this. The only functional changes there are a critical fix
> for FastTrack TX4200 (not your card), and support for SATA hotplugging
> (not happening here).
> 
> So I'm suspecting something in libata core might have changed to fix this.
> 
> Just to make sure, what's the numerical PCI IDs for your card?

01:08.0 0180: 105a:3d17 (rev 02)
         Subsystem: 105a:3d17
         Flags: bus master, 66MHz, medium devsel, latency 72, IRQ 19
         I/O ports at a400 [size=128]
         I/O ports at a800 [size=256]
         Memory at e9024000 (32-bit, non-prefetchable) [size=4K]
         Memory at e9000000 (32-bit, non-prefetchable) [size=128K]
         [virtual] Expansion ROM at 300a0000 [disabled] [size=32K]
         Capabilities: [60] Power Management version 2


Best regards,

Peter

  reply	other threads:[~2007-10-15 17:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-15  8:21 Bug is fixed in 2.6.23.1: sata_promise: port is slow to respond, reset failed Mikael Pettersson
2007-10-15 17:55 ` Peter Favrholdt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-02 11:12 Peter Favrholdt
2007-10-14  9:21 ` Bug is fixed in 2.6.23.1: " Peter Favrholdt

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=4713A991.3030308@how.dk \
    --to=linux-ide@how.dk \
    --cc=linux-ide@vger.kernel.org \
    --cc=mikpe@it.uu.se \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).