linux-kernel - Re: Linux Support for Thunderbolt using Apple Monitor

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Sat, 05 May 2012 14:19:10 +1000
From:	Francois Rigaut <frigaut@...il.com>
To:	Yinghai Lu <yinghai@...nel.org>
CC:	Greg KH <gregkh@...uxfoundation.org>, linux-pci@...r.kernel.org,
	Nico Schottelius <nico-linux-20120419@...ottelius.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Linux Support for Thunderbolt using Apple Monitor


On 05/05/12 05:38, Yinghai Lu wrote:
> On Fri, May 4, 2012 at 12:37 PM, Yinghai Lu<yinghai@...nel.org>  wrote:
>> On Fri, May 4, 2012 at 11:48 AM, Greg KH<gregkh@...uxfoundation.org>  wrote:
>>> Ok, it looks like these are the devices that we are missing while
>>> "hotplugging":
>>> 37:00.0 PCI bridge: Intel Corporation Device 1513
>>> 38:00.0 PCI bridge: Intel Corporation Device 1513
>>> 38:01.0 PCI bridge: Intel Corporation Device 1513
>>> 38:02.0 PCI bridge: Intel Corporation Device 1513
>>> 38:03.0 PCI bridge: Intel Corporation Device 1513
>>> 38:04.0 PCI bridge: Intel Corporation Device 1513
>>> 38:05.0 PCI bridge: Intel Corporation Device 1513
>>> 39:00.0 PCI bridge: Pericom Semiconductor Device 400c (rev 02)
>>> 3a:03.0 PCI bridge: Pericom Semiconductor Device 400c (rev 02)
>>> 3b:00.0 USB controller: Pericom Semiconductor Device 400e (rev 01)
>>> 3b:00.1 USB controller: Pericom Semiconductor Device 400e (rev 01)
>>> 3b:00.2 USB controller: Pericom Semiconductor Device 400f (rev 01)
>>> 3c:00.0 Ethernet controller: Broadcom Corporation NetXtreme BCM57761 Gigabit Ethernet PCIe (rev 10)
>>> 3d:00.0 FireWire (IEEE 1394): nee Agere Systems nee Lucent
>>> Microelectronics FW643 PCI Express 1394b Controller (PHY/Link) (rev 08)
>>>
>>> Which is good, I was worried that there was a video controller out there
>>> on the end of the thunderbolt link.
>>>
>>> So, the problem really is two here:
>>>   - your video card doesn't detect the new display
>>>   - your pci devices do not show up
>>>
>>> The first one probably needs to be reported to the Intel video driver
>>> people, they can help you out the best.
no it's definitely not the first one. As you saw, there'sa whole bunch 
of other devices (3 USB, firewire, network) that do not show up either.

The new info from Yinghai (thanks Yinghai) explains why hotpluging with 
pciehp did not work/detect the PCIE hotplug and did not result in *any* 
kernel messages.

So the whole thing I guess boils down to making acpiphp work. And why it 
outputs the "no such device" error message and does not load:

I tried with debug=1 and got a bit more info in the log files:

[root@...iahu frigaut]# lsmod | grep -e acpi -e pci
acpi_cpufreq            5941  0
mperf                   1275  1 acpi_cpufreq
processor              26144  1 acpi_cpufreq
[root@...iahu frigaut]# modprobe acpiphp debug=1
ERROR: could not insert 'acpiphp': No such device

at this point this message showed up in everything.log:
May  5 14:09:55 localhost kernel: [28329.700022] pci_hotplug: PCI Hot 
Plug PCI Core version: 0.5
May  5 14:09:55 localhost kernel: [28329.702041] acpiphp: ACPI Hot Plug 
PCI Controller Driver version: 0.5
May  5 14:09:55 localhost kernel: [28329.702484] acpiphp_glue: found 
PCI-to-PCI bridge at PCI 0000:04:00.0
May  5 14:09:55 localhost kernel: [28329.702715] acpiphp_glue: Bus 
0000:05 has 0 slots
May  5 14:09:55 localhost kernel: [28329.702720] acpiphp_glue: Total 0 slots

then:
[root@...iahu frigaut]# lsmod | grep -e acpi -e pci
pci_hotplug            25324  0
acpi_cpufreq            5941  0
mperf                   1275  1 acpi_cpufreq
processor              26144  1 acpi_cpufreq
[root@...iahu frigaut]#

shows that acpiphp was indeed not loaded (I assume the error occurs 
after it has written out the above messages in the log file), but 
pci_hotplug was as a dep of acpiphp I assume (thus, correct behavior).

So we're back to the issue of the acpiphp load error.

Greg, I see you're one of the authors of acpiphp:
#define DRIVER_VERSION    "0.5"
#define DRIVER_AUTHOR    "Greg Kroah-Hartman <gregkh@...ibm.com>, 
Takayoshi Kochi <t-kochi@...jp.nec.com>, Matthew Wilcox <willy@...com>"
#define DRIVER_DESC    "ACPI Hot Plug PCI Controller Driver"

but that might have been a while back?

Cheers, and thanks,
Francois



>>>
>>> The second one means that something is up with the pci hotplug
>>> controller.  I've cced the linux-pci list, the people there should be
>>> able to help out better than I, as I no longer have any PCI hotplug
>>> hardware to work with anymore.
>>>
>> those devices are under 04:04.0, but that does not have slot cap
>> enabled by BIOS. So pciehp is going to to help.
> should be: pciehp is not going to help.
>
> so acpiphp are involved?
>
> Yinghai
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/