From: Greg KH <greg@kroah.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: possible bug regarding pciehp
Date: Wed, 02 Sep 2015 15:27:25 +0000 [thread overview]
Message-ID: <20150902152725.GA16149@kroah.com> (raw)
In-Reply-To: <55E70945.6060802@diplomail.ch>
On Wed, Sep 02, 2015 at 04:35:49PM +0200, Tormen wrote:
> Hi,
>
> I am contacting you, hoping that either you can maybe help
> or you know someone who can help :)
>
> I opened a bug related to the tg3 driver when hot-plugging via pciehp:
> https://bugzilla.kernel.org/show_bug.cgi?id\x100191
>
> I am desperate because :
> (a) there is also a brcmfmac related driver.
> So both wireless and wired internet have problems:
> https://bugzilla.kernel.org/show_bug.cgi?id\x100201
> (b) there was no input by anybody so far. Maybe because I wrongly
> categorized the tg3 bug ?
>
> The bug is related to Broadcom tg3 driver and the pciehp hotplug framework.
> In order to sort out where the problem(s) lies, I wanted to kindly ask
> you if you could have a look at the bug :
> https://bugzilla.kernel.org/show_bug.cgi?id\x100191
> ?
> And/or if you could help me figuring out if pciehp is causing this
> problem and/or if tg3 is to blame.
Odds are neither are the issue, this is a thunderbolt problem. Make
sure you have enabled thunderbolt properly in your kernel if you want
hot-add of a device to work.
I think the code has only been tested on older macbooks, changes might
be needed for newer ones given that Apple's thunderbolt controller is
"special" (i.e. doesn't follow the specification.)
good luck!
greg k-h
next prev parent reply other threads:[~2015-09-02 15:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-02 14:35 possible bug regarding pciehp Tormen
2015-09-02 15:27 ` Greg KH [this message]
2015-09-04 7:54 ` Tormen
2015-09-05 3:38 ` Greg KH
2015-09-18 9:19 ` Tormen
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=20150902152725.GA16149@kroah.com \
--to=greg@kroah.com \
--cc=linux-hotplug@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).