linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mark Lord <liml@rtr.ca>
To: Hannes Reinecke <hare@suse.de>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>, linux-ide@vger.kernel.org
Subject: Re: [PATCH] Fixup ahci suspend / resume
Date: Tue, 28 Feb 2006 09:45:54 -0500	[thread overview]
Message-ID: <44046222.4090008@rtr.ca> (raw)
In-Reply-To: <44045FB1.5040408@suse.de>

Hannes Reinecke wrote:
> Hi all,
> 
> the current ahci doesn't handle suspend / resume cycles too well.
> On certain machines the disk just locks up and refuses to work after a
> resume.
> 
> This is due to a initialisation error after resume; ahci has fo[u]r
> registers containing DMA addresses (which are obviously allocated by the
> kernel). Of course there is no guarantee that these addresses are
> unchanged across reboots. So ahci loads the suspended image, and after
> the suspended image is started the driver is presented with different
> DMA addresses, whereas the chip still uses the original ones.
> 
> This patch rearranges the suspend / resume code to properly initialise
> those registers after a resume. It also contains some initialisation
> fixes to make the driver behave more spec-compliant.
..

Is ahci the *only* interface afflicted with this problem?

  reply	other threads:[~2006-02-28 14:46 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-28 14:35 [PATCH] Fixup ahci suspend / resume Hannes Reinecke
2006-02-28 14:45 ` Mark Lord [this message]
2006-02-28 14:59   ` Hannes Reinecke
2006-02-28 15:14 ` Jeff Garzik
2006-02-28 15:19   ` Jens Axboe
2006-02-28 15:22     ` Jeff Garzik
2006-02-28 15:28       ` Jens Axboe
2006-02-28 15:35         ` Jeff Garzik
2006-02-28 15:57           ` Hannes Reinecke
2006-02-28 17:25             ` Jens Axboe
2006-03-04  7:37               ` Randy.Dunlap
2006-03-06  8:36                 ` Hannes Reinecke

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=44046222.4090008@rtr.ca \
    --to=liml@rtr.ca \
    --cc=hare@suse.de \
    --cc=linux-ide@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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).