From: David Henningsson <david.henningsson@canonical.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
Andreas Noever <andreas.noever@gmail.com>
Subject: Re: [PATCH] Add pci=assign-busses quirk to Dell Latitude D505
Date: Thu, 11 Sep 2014 10:13:09 +0200 [thread overview]
Message-ID: <54115995.5020107@canonical.com> (raw)
In-Reply-To: <CAErSpo6DDCkrew8rwkNX8=gzc19vErY5iafPBN4oKw_Ww792=g@mail.gmail.com>
On 2014-09-10 20:08, Bjorn Helgaas wrote:
> [+cc Andreas]
> v3.16 fails with:
>
> pci 0000:01:01.0: can't allocate child bus 01 from [bus 01]
>
> which Andreas added with fc1b253141b3 ("PCI: Don't scan random busses
> in pci_scan_bridge()"). But I don't understand that code well enough
> to know whether this commit is actually the cause of the problem.
>
> And I also haven't figured out how "pci=assign-busses" makes a difference.
>
> David, would you mind turning on CONFIG_DYNAMIC_DEBUG=y in your v3.16
> kernel, adding 'dyndbg="file probe.c +p"' to your boot arguments, and
> collecting another dmesg log?
Thanks for looking at this (and sorry for not having done a bisect yet).
Anyhow, a new dmesg log has now been posted at kernel bugzilla #83441.
It has a few more lines starting with "pci_bus" but nothing that really
stands out AFAICT.
--
David Henningsson, Canonical Ltd.
https://launchpad.net/~diwic
next prev parent reply other threads:[~2014-09-11 8:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 9:10 [PATCH] Add pci=assign-busses quirk to Dell Latitude D505 David Henningsson
2014-08-29 14:22 ` Bjorn Helgaas
2014-08-29 14:44 ` David Henningsson
2014-08-29 17:36 ` Bjorn Helgaas
2014-09-10 18:08 ` Bjorn Helgaas
2014-09-10 19:50 ` Andreas Noever
2014-09-10 20:37 ` Bjorn Helgaas
2014-09-11 8:13 ` David Henningsson [this message]
2014-09-13 3:18 ` Bjorn Helgaas
2014-09-14 22:10 ` Andreas Noever
2014-09-15 9:53 ` Wei Yang
2014-09-15 10:04 ` Andreas Noever
2014-09-16 1:37 ` Wei Yang
2014-09-16 3:00 ` Gavin Shan
2014-09-15 19:03 ` Bjorn Helgaas
2014-09-16 8:49 ` Wei Yang
2014-09-19 17:04 ` 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=54115995.5020107@canonical.com \
--to=david.henningsson@canonical.com \
--cc=andreas.noever@gmail.com \
--cc=bhelgaas@google.com \
--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.