linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
To: Jens Axboe <axboe@suse.de>
Cc: jhpark@tuhep.phys.tohoku.ac.jp, linux-ide@vger.kernel.org,
	jgarzik@pobox.com, chris@powerblogs.com
Subject: Re: [PATCH 0/5] SATA/ACPI suspend/resume support
Date: Tue, 3 Jan 2006 13:00:27 -0800	[thread overview]
Message-ID: <20060103130027.44bb8897.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <20060103201312.GB3472@suse.de>

On Tue, 3 Jan 2006 21:13:12 +0100
Jens Axboe <axboe@suse.de> wrote:

> On Tue, Jan 03 2006, Jens Axboe wrote:
> > On Tue, Jan 03 2006, Randy Dunlap wrote:
> > > 
> > > Ugh.  So the ACPI taskfile data looks like crap??
> > > I guess that I'll just invalidate gtf_address (set to NULL)
> > > if gtf_length looks invalid.  Is there something better to do?
> > 
> > Bugger me, I'm totally acpi ignorant. But did you see my note that if I
> > clear gtf_address before calling into the function (where you pass it by
> > reference), the problem goes away? That smells more like return-on-error
> > without setting it at all, hence kfree() blows up when passed a bogus
> > stack filled variable.

Yes, I'll just init gtf_length and gtf_address to 0
in do_drive_get_GTF().

> > > Jae-hyeon,
> > > 
> > > Please send me a dump of your ACPI tables (acpidump).
> > > 'acpidump' is at
> > > http://www.kernel.org/pub/linux/kernel/people/lenb/acpi/utils/ .
> > > Use the latest pmtools tarball.
> > 
> > I've attached mine as well, in case they are useful.

At least it shows that there is no _GTF at all for SATA devices,
only for PATA (which my patch does not address).

> > > Jens, could you see that <gtf_address> your system is
> > > getting that is invalid?
> > 
> > Sure, will reboot it after posting this message.
> 
> It's just 0 (because I fill it as such). do_drive_get_GTF() looks
> suspicious, at least with noacpi != 0 it will return success without
> filling gtf_address. Perhaps you want to treat that as an error, or
> check for it earlier?
> 
> Anyways, I'm pretty sure do_drive_get_GTF() needs some fixing. I'll
> leave that to you, let me know if you want me to test anything.

Yes, basic error on my part.  I've updated the patch series
and rediffed it against 2.6.15.  If one of you could test it,
that would be great (Jae-hyeon or Jens).

New patch series is at
  http://www.xenotime.net/linux/SATA/2.6.15/
with a combined patch at
  http://www.xenotime.net/linux/SATA/2.6.15/libata-combine-2615.patch

If you don't want to revert the old patchset and apply the new
one, you can just do this:

	*gtf_length = 0;
	*gtf_address = 0UL;
at the top of do_drive_get_GTF().


Thanks for your help.
---
~Randy

  reply	other threads:[~2006-01-03 20:59 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-27 23:34 [PATCH 0/5] SATA/ACPI suspend/resume support Randy Dunlap
2005-12-30  8:36 ` Jae-hyeon Park
2006-01-03 17:08   ` Randy Dunlap
2006-01-03 17:26     ` Jens Axboe
2006-01-03 19:03       ` Jens Axboe
2006-01-03 19:06         ` Randy Dunlap
2006-01-03 19:57         ` Randy Dunlap
2006-01-03 20:06           ` Jens Axboe
2006-01-03 20:11             ` Randy Dunlap
2006-01-03 20:13             ` Jens Axboe
2006-01-03 21:00               ` Randy Dunlap [this message]
2006-01-03 21:16                 ` Jens Axboe
2006-01-03 22:02                   ` Randy Dunlap
2006-01-04  7:36                     ` Jens Axboe
2006-01-03 22:40           ` Jae-hyeon Park
2006-01-04  0:40             ` Randy Dunlap
2006-01-04  1:31               ` Jae-hyeon Park
2006-01-04 18:13                 ` Randy Dunlap
2006-01-04 18:57                 ` Randy Dunlap
2006-01-04 19:42                 ` Randy Dunlap
2006-01-05 14:08                   ` Jae-hyeon Park
2006-01-05 18:36                     ` Randy Dunlap
2006-01-06  1:02                       ` Jae-hyeon Park
2006-01-06  1:10                         ` Randy Dunlap
2006-01-06 20:43                     ` Randy Dunlap
2006-01-07 13:11                       ` Jae-hyeon Park
2006-01-07 16:55                         ` Randy.Dunlap

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=20060103130027.44bb8897.randy_d_dunlap@linux.intel.com \
    --to=randy_d_dunlap@linux.intel.com \
    --cc=axboe@suse.de \
    --cc=chris@powerblogs.com \
    --cc=jgarzik@pobox.com \
    --cc=jhpark@tuhep.phys.tohoku.ac.jp \
    --cc=linux-ide@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).