From: Shawn Starr <shawn.starr@rogers.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: Kernel development list <linux-kernel@vger.kernel.org>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>
Subject: Re: [3.16-rcX][pciehp][radeon] PCIe HotPlug conflicts with radeon GPU
Date: Tue, 23 Sep 2014 14:53:35 -0400 [thread overview]
Message-ID: <1722798.naFc0gpZgU@segfault> (raw)
In-Reply-To: <CAErSpo6zLY8RVAHnLe81jjOE8cxGzskjPq3HL7eZVOtC-WF6=w@mail.gmail.com>
On September 11, 2014 04:26:21 PM Bjorn Helgaas wrote:
> [+cc linux-pci]
>
> On Sat, Aug 2, 2014 at 10:02 AM, Shawn Starr <shawn.starr@rogers.com> wrote:
> > Hello devs,
> >
> > There are two issues I am encountering with the PCIe Hotplug driver on my
> > Lenovo Laptop (W500). I note this goes back further than 3.15.
> >
> > It is noted here:
> > http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=
> > f244d8b623dae7a7bc695b0336f67729b95a9736
> > https://bugzilla.kernel.org/show_bug.cgi?id=79701
> >
> > And my open bug here:
> > https://bugzilla.kernel.org/show_bug.cgi?id=77261
> >
> > 1) If I enable the device to use both the integrated and discrete GPU,
> > pciehp will decide to force unload radeon because it puts itself into a
> > power saving state, fails back to the Intel integrated GPU in this case
> > unless I tell radeon.ko to runpm=0 (no power management, then pciehp wont
> > touch it).
> >
> > 2) If the Radeon GPU resets and you use pci_reset=1 for kernel module
> > option, pciehp decides to force unload radeon even though the GPU is
> > trying to setup after failing.
> >
> > Kernel I am using right now: 3.16.0-0.rc7.git3.1.fc21.x86_64 (about to
> > boot into snapshot kernel-core-3.16.0-0.rc7.git4.1.fc21.x86_64)
> Hi Shawn,
>
> Thanks for the report and sorry that it got dropped. But I see you're
> cc'd on https://bugzilla.kernel.org/show_bug.cgi?id=79701, so you've
> probably seen the work there. If you can try out the patches I just
> posted, that would be great.
>
> Bjorn
Hi Bjorn,
I will be testing this in 3.17-rcX if it hits 3.17, otherwise manually patch
it in.
Thanks,
Shawn
next prev parent reply other threads:[~2014-09-23 19:00 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-02 16:02 [3.16-rcX][pciehp][radeon] PCIe HotPlug conflicts with radeon GPU Shawn Starr
2014-09-11 22:26 ` Bjorn Helgaas
2014-09-23 18:53 ` Shawn Starr [this message]
2014-10-11 19:37 ` [Bulk] " Shawn Starr
2014-10-13 16:11 ` Bjorn Helgaas
2014-10-26 17:31 ` Alex Deucher
2014-10-26 17:31 ` Alex Deucher
2014-10-27 16:44 ` Bjorn Helgaas
2014-10-27 16:44 ` Bjorn Helgaas
2014-10-28 15:45 ` Alex Deucher
2014-10-28 15:45 ` Alex Deucher
2014-10-28 16:20 ` Bjorn Helgaas
2014-10-28 16:20 ` Bjorn Helgaas
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=1722798.naFc0gpZgU@segfault \
--to=shawn.starr@rogers.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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.