linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Randy Dunlap <randy_d_dunlap@linux.intel.com>
To: Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp>
Cc: axboe@suse.de, linux-ide@vger.kernel.org, jgarzik@pobox.com,
	chris@powerblogs.com
Subject: Re: [PATCH 0/5] SATA/ACPI suspend/resume support
Date: Thu, 5 Jan 2006 10:36:04 -0800	[thread overview]
Message-ID: <20060105103604.4b785239.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <87aceag437.fsf@marrow.phys.tohoku.ac.jp>

On 05 Jan 2006 23:08:12 +0900
Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> wrote:

> Randy Dunlap <randy_d_dunlap@linux.intel.com> writes:
> >
> > Does your system work without using the AHCI driver?
> > or is it required?
> 
> I tested turning off AHCI with 2.6.15-rc7 + git-libata-all.patch +
> libata_resume_fix.patch + libata_suspend-fix.patch +
> libata_suspend.patch.  The system runs okay, and ACPI suspend/resume
> and suspend2 work, without AHCI.
> 
> > Of course, even if the AHCI driver is not needed,
> > it shouldn't be oopsing like this.
> > 
> > It looks like the ata_piix driver is the one that is
> > actually being used, from what I can see here.
> > 
> > Please send your /proc/interrupts, /proc/iomem, /proc/ioports,
> > and 'lspci -v'.
> 
> They are enclosed below.

Hi,
While I'm looking over this, do you have a mode in which
the AHCI driver loads successfully?  If so, look for a
kernel message similar to this one:

ahci 0000:00:1f.2: AHCI 0001.0100 32 slots 4 ports 1.5 Gbps 0x5 impl SATA mode

and post it, please.  (I think that it won't say "SATA mode".)
The "prog-if" value of 80 from your lspci output is interesting to me:
0000:00:1f.2 IDE interface: Intel Corporation 82801FBM (ICH6M) SATA Controller (rev 03) (prog-if 80 [Master])

Thanks,
---
~Randy

  reply	other threads:[~2006-01-05 18:35 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
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 [this message]
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=20060105103604.4b785239.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).