public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Jack Howarth <howarth@bromo.msbb.uc.edu>
Cc: linux-kernel@vger.kernel.org, Shaohua Li <shaohua.li@intel.com>
Subject: Re: [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf
Date: Tue, 22 Jul 2008 18:32:20 -0700	[thread overview]
Message-ID: <200807221832.21167.jbarnes@virtuousgeek.org> (raw)
In-Reply-To: <20080723010058.GA12662@bromo.msbb.uc.edu>

On Tuesday, July 22, 2008 6:00 pm Jack Howarth wrote:
> Jesse,
>     I found that patch right after I sent the email. Applying the ASPM
> patch solves the boot hangs on under 2.6.26-git9 built with
> CONFIG_PCIEASPM=y. I am attaching the dmesg log for such a boot
> below. I am a little confused if the patch totally disables aspm on
> my machine or just inhibits the hang. Is there a proc entry I can check
> to monitor that aspm is in use?

It should disable ASPM on pre-1.1 PCIe devices, since apparently many of them 
get ASPM wrong, resulting in bus hangs.  There's a file in sysfs to control 
things:
/sys/module/pcie_aspm/parameters/policy
(see the description in 7d715a6c1ae5785d00fb9a876b5abdfc43abc44b for info).

With the patch applied hopefully it indicates that things are disabled.

Thanks for testing.

Jesse

  reply	other threads:[~2008-07-23  1:32 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-22 23:37 [PATCH] x86,pci: dmi check for mackpro 2.2 mmconf Jack Howarth
2008-07-23  0:23 ` Jesse Barnes
2008-07-23  1:00   ` Jack Howarth
2008-07-23  1:32     ` Jesse Barnes [this message]
2008-07-23  1:41       ` Jack Howarth
2008-07-23  1:54         ` Shaohua Li
  -- strict thread matches above, loose matches on Subject: below --
2008-07-18 16:41 Yinghai Lu
2008-07-18 16:50 ` Jack Howarth
2008-07-18 17:44 ` H. Peter Anvin
2008-07-18 17:47   ` Yinghai Lu
2008-07-18 17:49     ` H. Peter Anvin
2008-07-18 17:54       ` Yinghai Lu
2008-07-18 20:19         ` Ingo Molnar
2008-07-18 20:21           ` Yinghai Lu
2008-07-18 20:21 ` Ingo Molnar
2008-07-18 20:26   ` Yinghai Lu
2008-07-19  0:58     ` Jack Howarth
2008-07-19  1:22       ` Yinghai Lu
2008-07-19  3:28         ` Jack Howarth
2008-07-19  3:43           ` Justin Mattock
2008-07-19  4:45           ` Yinghai Lu
2008-07-19  5:12             ` Jack Howarth
2008-07-19  5:28               ` Yinghai Lu
2008-07-19 17:26                 ` Jesse Barnes
2008-07-19 18:19                   ` Jack Howarth
2008-07-19 18:40                   ` Jack Howarth
2008-07-19 19:04                     ` Jesse Barnes
2008-07-19 19:14                       ` Jack Howarth
2008-07-21  6:49                         ` Shaohua Li
2008-07-22 21:15                           ` Jesse Barnes

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=200807221832.21167.jbarnes@virtuousgeek.org \
    --to=jbarnes@virtuousgeek.org \
    --cc=howarth@bromo.msbb.uc.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=shaohua.li@intel.com \
    /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