From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Anton Pyrogovskyi <asp@penguinishly.org.ua>
Cc: "mjg@redhat.com" <mjg@redhat.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Linux PM list <linux-pm@vger.kernel.org>
Subject: Re: PROBLEM: Re: [PATCH] pci: Rework ASPM disable code
Date: Mon, 23 Jul 2012 23:17:33 +0200 [thread overview]
Message-ID: <201207232317.33764.rjw@sisk.pl> (raw)
In-Reply-To: <2806511343077258@web6f.yandex.ru>
On Monday, July 23, 2012, Anton Pyrogovskyi wrote:
> Hello.
>
> This patch (aka commit 3c076351c, https://lkml.org/lkml/2011/11/10/467) makes my GPU (NVidia GT 240) become undetectable by the NVidia proprietary driver.
> The issue used to surface before, but I resolved it by disabling ASPM altogether (adding «pcie_aspm=off» to the kernel parameter line). This no more works since the commit is in order.
> The driver not being loaded causes me some obvious trouble, such as uvesafb and X not being able to start.
> This only happens during regular boot — if I thaw from hibernation or load the same kernel atop the currently running instance with kexec everything works fine.
> Upon reverting the patch and rebuilding the kernel, everything returns to normal permanently and I can live without kexec again.
> Tested on 3.4.4 and 3.5.0-rc7+, everything earlier than 3.3.x works as expected (due to not having its ASPM disable code reworked).
Well, without knowing what's inside the NVidia driver, we can't really say
what the problem may be.
Does nouveau detect your GPU with the Matthews commit?
Rafael
next prev parent reply other threads:[~2012-07-23 21:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-23 21:00 PROBLEM: Re: [PATCH] pci: Rework ASPM disable code Anton Pyrogovskyi
2012-07-23 21:17 ` Rafael J. Wysocki [this message]
[not found] ` <2809911343078330@web6f.yandex.ru>
2012-07-23 21:38 ` Matthew Garrett
2012-07-23 21:44 ` Rafael J. Wysocki
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=201207232317.33764.rjw@sisk.pl \
--to=rjw@sisk.pl \
--cc=asp@penguinishly.org.ua \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=mjg@redhat.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