public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Jeff Garzik <jeff@garzik.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: State of resume for AHCI?
Date: Thu, 01 Jun 2006 10:28:34 -0700	[thread overview]
Message-ID: <447F23C2.8030802@goop.org> (raw)

Hi Jeff,

I'm trying to get a Thinkpad X60 working properly.  My biggest remaining 
problem is the failure of AHCI to resume properly after suspend-to-ram.  
I know the problem is known about and there are patches floating about 
to address it, but I don't really understand the larger picture.  There 
were some discussions about it a couple of months ago, but I haven't 
seen anything much since.

Is there a git tree which should work properly on this hardware, or a 
current patch to do it?  Does somebody need to bring the existing patch 
up to date?  Does fixing this require more infrastructure changes which 
are still brewing?

I'm running 2.6.17-rc2-mm1 (soon mm2).  I've tried porting Hannes 
Reinecke's patch to this tree, but there have been some code changes 
which cause significant conflicts, and I don't really know enough about 
the driver/hardware to be confident in my changes.  That said, I have 
got something compiling, but it crashes somewhere in the kobject stuff 
when it encounters the first port with no drive on it; this looks like a 
more general scsi/libata bug; I'll track it down if its interesting.

Anyway, I'd appreciate it if you could give me some hints about how to 
get a fix with some current kernel.

Thanks,
    J

             reply	other threads:[~2006-06-01 17:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-01 17:28 Jeremy Fitzhardinge [this message]
2006-06-01 18:30 ` State of resume for AHCI? Mark Lord
2006-06-01 18:39   ` Jens Axboe
2006-06-01 20:19     ` Jeremy Fitzhardinge
2006-06-02  1:02       ` zhao, forrest
2006-06-02  3:39         ` Jeremy Fitzhardinge
2006-06-02  6:39         ` Hannes Reinecke
2006-06-02  6:03       ` Jens Axboe
2006-06-02  6:03         ` zhao, forrest
2006-06-02  6:41           ` Jens Axboe
2006-06-02  6:43             ` Hannes Reinecke
2006-06-02  6:49               ` zhao, forrest
2006-06-02  7:06                 ` Jens Axboe
2006-06-02  6:52               ` Jens Axboe
2006-06-01 18:48   ` Mark Lord
2006-06-06  2:16     ` Tejun Heo

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=447F23C2.8030802@goop.org \
    --to=jeremy@goop.org \
    --cc=jeff@garzik.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