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 17:10:30 -0800 [thread overview]
Message-ID: <20060105171030.3a7beb19.randy_d_dunlap@linux.intel.com> (raw)
In-Reply-To: <87k6deyxrd.fsf@marrow.phys.tohoku.ac.jp>
On 06 Jan 2006 10:02:14 +0900
Jae-hyeon Park <jhpark@tuhep.phys.tohoku.ac.jp> wrote:
> Randy Dunlap <randy_d_dunlap@linux.intel.com> writes:
>
> > 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])
> >
>
> I couldn't find a line like that from a working kernel with AHCI
> option on. The only ahci-related lines look like
>
> ahci 0000:00:1f.2: version 1.2
> ahci: probe of 0000:00:1f.2 failed with error -12
>
> I selected AHCI because the lines in ata_piix.c
>
> { 0x8086, 0x2653, PCI_ANY_ID, PCI_ANY_ID, 0, 0, ich6_sata_rm },
>
> and
>
> /* ich6_sata_rm */
> {
> .sht = &piix_sht,
> .host_flags = ATA_FLAG_SATA | ATA_FLAG_SRST |
> PIIX_FLAG_COMBINED | PIIX_FLAG_CHECKINTR |
> ATA_FLAG_SLAVE_POSS | PIIX_FLAG_AHCI,
> .pio_mask = 0x1f, /* pio0-4 */
> .mwdma_mask = 0x07, /* mwdma0-2 */
> .udma_mask = 0x7f, /* udma0-6 */
> .port_ops = &piix_sata_ops,
> },
>
> seemed to indicate that my controller was ahci-capable.
> But according to
> http://marc.theaimsgroup.com/?l=linux-ide&m=111828214909335&w=2,
> my system does not support AHCI. I don't see Region 5 in the output
> of lspci -vv -s 00:1f.2.
Yes, I don't think that it's AHCI-capable, but I still must
keep the Oops from happening, so I'm going thru your kernel
message log output (still).
Thanks for your help.
---
~Randy
next prev parent reply other threads:[~2006-01-06 1:09 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
2006-01-06 1:02 ` Jae-hyeon Park
2006-01-06 1:10 ` Randy Dunlap [this message]
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=20060105171030.3a7beb19.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.