All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 70687] vgaswitcheroo issues on Linux 3.12
Date: Tue, 24 Dec 2013 18:53:12 +0000	[thread overview]
Message-ID: <bug-70687-502-ZbJUW6sXqz@http.bugs.freedesktop.org/> (raw)
In-Reply-To: <bug-70687-502@http.bugs.freedesktop.org/>


[-- Attachment #1.1: Type: text/plain, Size: 1293 bytes --]

https://bugs.freedesktop.org/show_bug.cgi?id=70687

--- Comment #13 from Armin K <krejzi@email.com> ---
I seem to have discovered the root of the issue.

I've just built 3.13-rc5 kernel which has the dynamic powering of the discrete
gpu and all hell broke loose.

I've narrowed the error down to the pci hotplug driver. My machine loads shpchp
pci hotplug driver from what I can see in lsmod output. But the trick is, that
there is another pci hotplug driver, acpi pci hotplug one, which seems to break
all hell loose here. Disabling it seems to fix everything for me, at least on
kernel 3.13.

# CONFIG_HOTPLUG_PCI_ACPI is not set

This kernel config option is the culprit for this, and that also can be seen
from my backtrace:

[   22.731998]  [<ffffffff81343cb1>] ? acpiphp_check_bridge+0x72/0x88

So the trick behind this is that acpi pci hotplug driver conflicts with shpchp
one that my machine uses. And since it is a builtin driver, and can't be built
as module it is always loaded. The other possibility is that this machine
doesn't support acpi hotplug, but does support shpc pci hotplug. We need a
kernel workarround so that acpi pci hotplug is disabled and out of the way when
shpc pci hotplug is enabled.

-- 
You are receiving this mail because:
You are the assignee for the bug.

[-- Attachment #1.2: Type: text/html, Size: 2035 bytes --]

[-- Attachment #2: Type: text/plain, Size: 159 bytes --]

_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2013-12-24 18:53 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-20 19:02 [Bug 70687] New: vgaswitcheroo issues on Linux 3.12 bugzilla-daemon
2013-10-20 19:03 ` [Bug 70687] " bugzilla-daemon
2013-10-21 17:24 ` bugzilla-daemon
2013-10-22 20:44 ` bugzilla-daemon
2013-12-01 21:33 ` bugzilla-daemon
2013-12-02  7:13 ` bugzilla-daemon
2013-12-04 23:55 ` bugzilla-daemon
2013-12-06  1:20 ` bugzilla-daemon
2013-12-08 15:52 ` bugzilla-daemon
2013-12-08 15:52 ` bugzilla-daemon
2013-12-10 23:43 ` bugzilla-daemon
2013-12-13 19:08 ` bugzilla-daemon
2013-12-23 19:54 ` bugzilla-daemon
2013-12-24 18:53 ` bugzilla-daemon [this message]
2014-01-05 22:05 ` bugzilla-daemon
2014-01-06 13:58 ` bugzilla-daemon
2014-01-07 22:43 ` bugzilla-daemon
2014-01-10  4:46 ` bugzilla-daemon
2014-01-10 14:23 ` bugzilla-daemon
2014-01-19  8:29 ` bugzilla-daemon

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=bug-70687-502-ZbJUW6sXqz@http.bugs.freedesktop.org/ \
    --to=bugzilla-daemon@freedesktop.org \
    --cc=dri-devel@lists.freedesktop.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.