From: Tormen <tormen@diplomail.ch>
To: linux-hotplug@vger.kernel.org
Subject: Re: possible bug regarding pciehp
Date: Fri, 18 Sep 2015 09:19:59 +0000 [thread overview]
Message-ID: <55FBD73F.2080305@diplomail.ch> (raw)
In-Reply-To: <55E70945.6060802@diplomail.ch>
On 09/05/2015 05:38 AM, Greg KH wrote:
> On Fri, Sep 04, 2015 at 09:54:18AM +0200, Tormen wrote:
>> On 09/02/2015 05:27 PM, Greg KH wrote:
>>> On Wed, Sep 02, 2015 at 04:35:49PM +0200, Tormen wrote:
>> When the network driver is loaded it seems to connect as a "PCI Express"
>> device:
>> tg3 0000:0a:00.0 eth0: Tigon3 [partno(BCM957762) rev 57766000] (PCI
>> Express)
>
> That's separate from the thunderbolt controller.
>
>> When I unplug the adapter the first thing appearing in dmesg is pciehp:
>> [ 210.992938] usb 1-2: USB disconnect, device number 4
>> [ 1557.453818] pciehp 0000:06:03.0:pcie24: slot(3-2): Link Down event
>> [ 1557.453870] pciehp 0000:06:03.0:pcie24: Cannot remove display device
>> 0000:08:00.0
>> [ 1557.509812] pciehp 0000:06:03.0:pcie24: Card not present on Slot(3-2)
>> [ 1558.721344] tg3 0000:0a:00.0: tg3_abort_hw timed out, TX_MODE_ENABLE
>> will not clear MAC_TX_MODEÿffffff
>> [ 1558.934601] pciehp 0000:09:00.0:pcie24: unloading service driver pciehp
>> [ 1558.935366] pciehp 0000:09:00.0:pcie24: Timeout on hotplug command
>> 0x1038 (issued 1557532 msec ago)
>> [ 1558.943460] pci_bus 0000:0a: busn_res: [bus 0a] is released
>> [ 1558.958426] pci_bus 0000:09: busn_res: [bus 09-0a] is released
>> [ 1558.958432] acpiphp: Slot [1] unregistered
>> [ 1558.958451] acpiphp: Slot [2-1] unregistered
>> [ 1558.958464] acpiphp: Slot [3-1] unregistered
>> [ 1558.958475] acpiphp: Slot [4-1] unregistered
>> [ 1558.958486] acpiphp: Slot [5-1] unregistered
>>
>> But I am not a kernel, pciehp, thunderbolt specialist :(
>>
>> How can I determine why the pciehp hotplug command 0x1038 timed out ?
>
> No idea, sorry, this is very odd hardware that doesn't follow any spec.
> Try emailing the author of the thunderbolt code, they should be able to
> help you out more.
>
> good luck,
>
> greg k-h
>
Thanks a lot! - I did and he was very kind in answering me right away -
thanks a lot Andreas - and his suggestion did lead to a working patch:
https://bugzilla.kernel.org/show_bug.cgi?id\x100191#c18
which makes the thunderbolt module load on boot and thus - like you
assumed Greg - provides the missing hotplug functionality!
Thanks again !
Tormen
prev parent reply other threads:[~2015-09-18 9:19 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
2015-09-04 7:54 ` Tormen
2015-09-05 3:38 ` Greg KH
2015-09-18 9:19 ` Tormen [this message]
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=55FBD73F.2080305@diplomail.ch \
--to=tormen@diplomail.ch \
--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 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.