public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthias Schniedermeyer <ms@citd.de>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Clemens Ladisch <clemens@ladisch.de>,
	Greg KH <gregkh@linuxfoundation.org>,
	linux-kernel@vger.kernel.org,
	Andrew Morton <akpm@linux-foundation.org>
Subject: Re: Linux 3.2.5
Date: Tue, 7 Feb 2012 18:07:09 +0100	[thread overview]
Message-ID: <20120207170709.GA28108@citd.de> (raw)
In-Reply-To: <20120207165944.GA30442@srcf.ucam.org>

On 07.02.2012 16:59, Matthew Garrett wrote:
> Ok. Can you try this?
> 
> diff --git a/drivers/pci/pcie/aspm.c b/drivers/pci/pcie/aspm.c
> index 1cfbf22..24f049e 100644
> --- a/drivers/pci/pcie/aspm.c
> +++ b/drivers/pci/pcie/aspm.c
> @@ -500,6 +500,9 @@ static int pcie_aspm_sanity_check(struct pci_dev *pdev)
>  	int pos;
>  	u32 reg32;
>  
> +	if (aspm_disabled)
> +		return 0;
> +
>  	/*
>  	 * Some functions in a slot might not all be PCIe functions,
>  	 * very strange. Disable ASPM for the whole slot
> 

Works too. What is the difference (in my case)?

dmesg looks the same.

dmesg | grep -i aspm
[    0.761712] ACPI FADT declares the system doesn't support PCIe ASPM, so disable it
[    0.792916] ACPI _OSC control for PCIe not granted, disabling ASPM
[    1.626739] e1000e 0000:03:00.0: Disabling ASPM  L1






Bis denn

-- 
Real Programmers consider "what you see is what you get" to be just as 
bad a concept in Text Editors as it is in women. No, the Real Programmer
wants a "you asked for it, you got it" text editor -- complicated, 
cryptic, powerful, unforgiving, dangerous.


  reply	other threads:[~2012-02-07 17:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-06 18:16 Linux 3.2.5 Greg KH
2012-02-06 18:16 ` Greg KH
2012-02-07  8:40 ` Matthias Schniedermeyer
2012-02-07 10:19   ` Clemens Ladisch
2012-02-07 10:58     ` Matthias Schniedermeyer
2012-02-07 11:23       ` Matthias Schniedermeyer
2012-02-07 11:40       ` Clemens Ladisch
2012-02-07 11:48         ` Matthias Schniedermeyer
2012-02-07 12:28           ` Clemens Ladisch
2012-02-07 14:52             ` Matthias Schniedermeyer
2012-02-07 18:29               ` Matthias Schniedermeyer
2012-02-07 16:29             ` Linus Torvalds
2012-02-07 16:40               ` Matthew Garrett
2012-02-07 16:54               ` Matthias Schniedermeyer
2012-02-07 16:59                 ` Matthew Garrett
2012-02-07 17:07                   ` Matthias Schniedermeyer [this message]
2012-02-07 17:18                     ` Matthew Garrett
2012-02-28  0:13                   ` Greg KH
2012-02-28  0:19                     ` Matthew Garrett

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=20120207170709.GA28108@citd.de \
    --to=ms@citd.de \
    --cc=akpm@linux-foundation.org \
    --cc=clemens@ladisch.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=torvalds@linux-foundation.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