Re: possible bug regarding pciehp

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



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=ffffffff
>> [ 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=100191#c18

which makes the thunderbolt module load on boot and thus - like you
assumed Greg - provides the missing hotplug functionality!

Thanks again !

Tormen

--
To unsubscribe from this list: send the line "unsubscribe linux-hotplug" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [Linux Kernel]     [Linux DVB]     [Asterisk Internet PBX]     [DCCP]     [Netdev]     [X.org]     [Util Linux NG]     [Fedora Women]     [ALSA Devel]     [Linux USB]

  Powered by Linux