From: AndrewL733 <AndrewL733@aol.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Macbook Pro SATA Drives not seen in 2.6.25
Date: Wed, 14 May 2008 07:36:02 -0400 [thread overview]
Message-ID: <482ACEA2.7080300@aol.com> (raw)
In-Reply-To: <20080514010618.2e1e510a.akpm@linux-foundation.org>
Thanks, Andrew. Another question below.
Andrew Morton wrote:
> On Tue, 13 May 2008 23:27:21 -0400 AndrewL733 <AndrewL733@aol.com> wrote:
>
>
>> I have a couple of Macbook Pros. The newest one -- based on the Penryn
>> Core 2 Duo with ICH8 -- will not boot with any 2.6.25 kernel (I have
>> tried 2.6.25 and 2.6.25.3).
>>
>
> Let's cc linux-ide.
>
>
>> It boots fine with 2.6.24.7 as well as with
>> 2.6.26-rc2. It also boots fine with 2.6.22. I have specific reasons why
>> I need to run 2.6.25 so I would appreciate any help here. It seems the
>> SATA drives are detected, but then for each partition during bootup I see:
>>
>> ata3: SATA link down (SStatus 0 SControl 0)
>>
>> The same 2.6.25 kernels boot fine on my older Macbook Pro with ICH7 and
>> I do not see this error.
>>
>> I would be happy to run a git bisect to help identify the issue, but if
>> this problem is already well understood (hey, it's fixed in 2.6.26), I
>> can think of better ways to spend my time.
>>
>
> The below went into 2.6.25.1 (or will do so). It looks hopful. Can
> you test it please?
>
Do you mean 2.6.25.4 ? As I said above, I already tried 2.6.25.3
yesterday and it doesn't boot.
>
>
> From: Tejun Heo <htejun@gmail.com>
>
> commit cb6716c879ecf49e2af344926c6a476821812061 upstream
>
> On certain configurations (certain macbooks), even though all the
> conditions for SIDPR access described in the datasheet are met,
> actually reading those registers just returns 0 and have no effect on
> write. Verify SIDPR is actually working before enabling it.
>
> This is reported by Ryan Roth in bz#10512.
>
> Signed-off-by: Tejun Heo <htejun@gmail.com>
> Cc: Ryan Roth <ryan.roth@ch2m.com>
> Signed-off-by: Jeff Garzik <jgarzik@redhat.com>
> Signed-off-by: Greg Kroah-Hartman <gregkh@suse.de>
>
> ---
> drivers/ata/ata_piix.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
>
> --- a/drivers/ata/ata_piix.c
> +++ b/drivers/ata/ata_piix.c
> @@ -1531,6 +1531,8 @@ static void __devinit piix_init_sidpr(st
> {
> struct pci_dev *pdev = to_pci_dev(host->dev);
> struct piix_host_priv *hpriv = host->private_data;
> + struct ata_device *dev0 = &host->ports[0]->link.device[0];
> + u32 scontrol;
> int i;
>
> /* check for availability */
> @@ -1549,6 +1551,29 @@ static void __devinit piix_init_sidpr(st
> return;
>
> hpriv->sidpr = pcim_iomap_table(pdev)[PIIX_SIDPR_BAR];
> +
> + /* SCR access via SIDPR doesn't work on some configurations.
> + * Give it a test drive by inhibiting power save modes which
> + * we'll do anyway.
> + */
> + scontrol = piix_sidpr_read(dev0, SCR_CONTROL);
> +
> + /* if IPM is already 3, SCR access is probably working. Don't
> + * un-inhibit power save modes as BIOS might have inhibited
> + * them for a reason.
> + */
> + if ((scontrol & 0xf00) != 0x300) {
> + scontrol |= 0x300;
> + piix_sidpr_write(dev0, SCR_CONTROL, scontrol);
> + scontrol = piix_sidpr_read(dev0, SCR_CONTROL);
> +
> + if ((scontrol & 0xf00) != 0x300) {
> + dev_printk(KERN_INFO, host->dev, "SCR access via "
> + "SIDPR is available but doesn't work\n");
> + return;
> + }
> + }
> +
> host->ports[0]->ops = &piix_sidpr_sata_ops;
> host->ports[1]->ops = &piix_sidpr_sata_ops;
> }
>
>
next prev parent reply other threads:[~2008-05-14 11:36 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <482A5C19.6090503@aol.com>
2008-05-14 8:06 ` Macbook Pro SATA Drives not seen in 2.6.25 Andrew Morton
2008-05-14 11:36 ` AndrewL733 [this message]
2008-05-14 17:44 ` Andrew Morton
2008-05-14 12:59 ` SOLVED: " AndrewL733
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=482ACEA2.7080300@aol.com \
--to=andrewl733@aol.com \
--cc=akpm@linux-foundation.org \
--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).