All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 141741] drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM
Date: Mon, 14 Nov 2016 15:28:17 +0000	[thread overview]
Message-ID: <bug-141741-2300-n4XXqfLlgX@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-141741-2300@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=141741

--- Comment #21 from Tero Roponen <tero.roponen@gmail.com> ---
(In reply to Lukas P from comment #19)
> I did a bisect and it reported the following commit as the first bad one:
> 30b5b8808c12bcd947dd474980482561b69c1bcb
> 
> diff --git a/drivers/pci/Kconfig b/drivers/pci/Kconfig
> index a1f37db..209292e 100644
> --- a/drivers/pci/Kconfig
> +++ b/drivers/pci/Kconfig
> @@ -128,4 +128,5 @@ config PCI_HYPERV
>            The PCI device frontend driver allows the kernel to import
> arbitrary
>            PCI devices from a PCI backend to support PCI driver domains.
>  
> +source "drivers/pci/hotplug/Kconfig"
>  source "drivers/pci/host/Kconfig"
> 
> If I remove the changed line in the source of v4.6 everything works normally.

I'm not an expert, but removing the inclusion of drivers/pci/hotplug/Kconfig
equals to disabling all the HOTPLUG_PCI_* options in the config ("Support for
PCI Hotplug" in menuconfig). You could try disabling those one by one to see
which one causes the problem.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are watching the assignee of the bug.
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel

  parent reply	other threads:[~2016-11-14 15:28 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-24 10:03 [Bug 141741] New: drm:radeon_get_bios [radeon]] *ERROR* Unable to locate a BIOS ROM bugzilla-daemon
2016-07-24 10:04 ` [Bug 141741] " bugzilla-daemon
2016-07-24 10:05 ` bugzilla-daemon
2016-07-24 10:05 ` bugzilla-daemon
2016-07-24 10:05 ` bugzilla-daemon
2016-07-24 10:06 ` bugzilla-daemon
2016-07-24 10:06 ` bugzilla-daemon
2016-07-24 10:07 ` bugzilla-daemon
2016-07-25  3:42 ` bugzilla-daemon
2016-07-25 16:49 ` bugzilla-daemon
2016-07-25 17:26 ` bugzilla-daemon
2016-07-26  6:07 ` bugzilla-daemon
2016-07-26 15:52 ` bugzilla-daemon
2016-07-27  6:17 ` bugzilla-daemon
2016-08-02  6:44 ` bugzilla-daemon
2016-09-20 21:47 ` bugzilla-daemon
2016-09-21 13:14 ` bugzilla-daemon
2016-09-27 21:35 ` bugzilla-daemon
2016-09-27 22:06 ` bugzilla-daemon
2016-09-28 22:26 ` bugzilla-daemon
2016-09-29 13:50 ` bugzilla-daemon
2016-10-20 20:18 ` bugzilla-daemon
2016-11-12 22:39 ` bugzilla-daemon
2016-11-14 15:28 ` bugzilla-daemon [this message]
2016-11-24 10:08 ` bugzilla-daemon
2016-12-27 17:38 ` bugzilla-daemon
2017-03-03  2:44 ` 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-141741-2300-n4XXqfLlgX@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.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.