From: Oliver Neukum <oneukum@suse.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Alan Stern <stern@rowland.harvard.edu>,
linux-pci@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: Thunderbolt adapter fails to instantiate USB and device enumeration if already connected at boot time
Date: Tue, 03 Jan 2017 10:28:57 +0100 [thread overview]
Message-ID: <1483435737.20054.6.camel@suse.com> (raw)
In-Reply-To: <CAJCQCtTGYUFCvwPzugJ4TUtFPGKTy7r+HJr_1o8s=cbASa4zUA@mail.gmail.com>
On Mon, 2017-01-02 at 14:45 -0700, Chris Murphy wrote:
> I see these lines in the problem case, which don't occur in the
> working case.
>
> [ 0.561046] pci_bus 0000:37: busn_res: [bus 37-ff] end is updated
> to 37
> [ 0.561047] pci_bus 0000:37: busn_res: can not insert [bus 37]
> under domain [bus 00-ff] (conflicts with (null) [bus 00-fe])
>
> [ 0.579446] pci 0000:37:00.0: can't claim BAR 0 [mem
> 0xb0000000-0xb000ffff]: address conflict with PCI Bus 0000:00 [mem
> 0x40000000-0xdfffffff window]
>
> [ 0.602277] pci 0000:37:00.0: can't derive routing for PCI INT A
> [ 0.602280] pci 0000:37:00.0: PCI INT A: not connected
> [ 0.612304] pci 0000:37:00.0: xHCI HW not ready after 5 sec (HC
> bug?) status = 0xffffffff
Have you tried "pci=realloc"?
Regards
Oliver
next prev parent reply other threads:[~2017-01-03 9:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-02 18:37 Thunderbolt adapter fails to instantiate USB and device enumeration if already connected at boot time Chris Murphy
2017-01-02 21:28 ` Alan Stern
2017-01-02 21:45 ` Chris Murphy
2017-01-03 9:28 ` Oliver Neukum [this message]
2017-01-03 15:19 ` Chris Murphy
2017-01-03 10:23 ` Lukas Wunner
2017-01-03 15:26 ` Chris Murphy
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=1483435737.20054.6.camel@suse.com \
--to=oneukum@suse.com \
--cc=linux-pci@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=stern@rowland.harvard.edu \
/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.