linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Yijing Wang <wangyijing@huawei.com>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>,
	Yijing Wang <wangyijing0307@gmail.com>,
	LKML <linux-kernel@vger.kernel.org>, <linux-pci@vger.kernel.org>
Subject: Re: 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner
Date: Mon, 28 Jan 2013 19:15:12 +0800	[thread overview]
Message-ID: <51065DC0.5080609@huawei.com> (raw)
In-Reply-To: <51065AA4.6000700@googlemail.com>

On 2013/1/28 19:01, Chris Clayton wrote:
> [no one screamed, so linux-media ml dropped]
> 
> Hi Martin,
> 
> On 01/28/13 10:56, Martin Mokrejs wrote:
>>
>>
>> Chris Clayton wrote:
>>> Hi Yijing,
>>>
>>> On 01/28/13 02:40, Yijing Wang wrote:
>>>> Hi Chris,
>>>>      Sorry for the delay reply. It seems like my reply last night was missed.
>>>>
>>>>   From the sysinfo you provide, there are no pcie port devices under /sys/bus/pci_express/devices.
>>>> Maybe because there are some problems with _OSC in your laptop, so pcie port driver won't create pcie port device
>>>> for hotplug, aer and so on.
>>>>
>>>> Maybe you can add boot parameter "pcie_ports=native" and reboot your laptop.
>>>> Then use #modprobe pciehp pciehp_force=1 pciehp_debug=1 to load pciehp modules.
>>>> After above actions, enter /sys/bus/pci_express/devices/ directory and /sys/bus/pci/slots/
>>>> Some slots and pcie port devices should be there now.
>>>>
>>> Sorry, I've tried your suggestion, but the two directories are still empty.
>>>
>>> I verified the test environment as follows:
>>>
>>> [chris:~]$ uname -a
>>> Linux laptop 3.7.4 #15 SMP PREEMPT Mon Jan 28 09:43:57 GMT 2013 i686 GNU/Linux
>>> [chris:~]$ grep acpiphp /boot/System.map-3.7.4
>>> [chris:~]$ modinfo acpiphp
>>> modinfo: ERROR: Module acpiphp not found.
>>> [chris:~]$ modinfo pciehp
>>> filename:       /lib/modules/3.7.4/kernel/drivers/pci/hotplug/pciehp.ko
>>> license:        GPL
>>> description:    PCI Express Hot Plug Controller Driver
>>> author:         Dan Zink <dan.zink@compaq.com>, Greg Kroah-Hartman <greg@kroah.com>, Dely Sy <dely.l.sy@intel.com>
>>> depends:
>>> intree:         Y
>>> vermagic:       3.7.4 SMP preempt mod_unload CORE2
>>> parm:           pciehp_detect_mode:Slot detection mode: pcie, acpi, auto
>>>    pcie          - Use PCIe based slot detection
>>>    acpi          - Use ACPI for slot detection
>>>    auto(default) - Auto select mode. Use acpi option if duplicate
>>>                    slot ids are found. Otherwise, use pcie option
>>>   (charp)
>>> parm:           pciehp_debug:Debugging mode enabled or not (bool)
>>> parm:           pciehp_poll_mode:Using polling mechanism for hot-plug events or not (bool)
>>> parm:           pciehp_poll_time:Polling mechanism frequency, in seconds (int)
>>> parm:           pciehp_force:Force pciehp, even if OSHP is missing (bool)
>>> [chris:~]$ cat /proc/cmdline
>>> root=/dev/sda5 pciehp_ports=native ro resume=/dev/sda6

Oh, should "pcie_ports=native" not "pciehp_ports=native".


>>> [chris:~]$ sudo modprobe pciehp pciehp_force=1 pciehp_debug=1
>>> [chris:~]$ lsmod
>>> Module                  Size  Used by
>>> pciehp                 19907  0
>>> [...]
>>>
>>> You will notice that the kernel I have used is 3.7.4. I hope that's a suitable kernel for your tests. I've moved away from the 3.8 development kernel onto one that's stable and on which Martin has identified a solution. I see Greg KH released 3.7.5 yesterday and it includes a pciehp change. I'll upgrade to that, run the tests again and report back.
>>>
>>> One question - should I include the (acpi) pci_slot driver in the kernel build or does pciehp populate the directories without pci_slot?
>>
>> Hi Chris,
>>    I am not a kernel developer but from the other threads at linux-pci I gathered there are in some
>> scenarios problems with improper loading of the hotplug modules. Therefore, the patches floating
>> now around are to disable hotplug module availability. Therefore, I suggested you to try only
>> only static kernel support for hotplug. That way you don't hit the issue. That is for sure not
>> addressed in 3.7.5, seems that it is probably in -next.
>> Martin
>>
> In a few minutes I'll be sending out another reply to Yijing's suggestions because I noticed a typo in the parameter I added to the kernel command line. I'm now going back through email to remember why we were trying to get those /sys/bus/pci... directories populated.
> 
> Watch this space! :-)
> Chris
> 
> 
> .
> 


-- 
Thanks!
Yijing


  reply	other threads:[~2013-01-28 11:20 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <51016937.1020202@googlemail.com>
     [not found] ` <510189B1.606@fold.natur.cuni.cz>
2013-01-26 20:54   ` 3.8.0-rc4+ - Oops on removing WinTV-HVR-1400 expresscard TV Tuner Chris Clayton
2013-01-26 21:14     ` Martin Mokrejs
2013-01-27  9:57       ` Chris Clayton
2013-01-27  2:45     ` Yijing Wang
2013-01-27 11:19       ` Chris Clayton
2013-01-27 12:18         ` Yijing Wang
2013-01-27 13:37           ` Chris Clayton
2013-01-27 14:26             ` Martin Mokrejs
2013-01-27 15:34               ` Chris Clayton
2013-01-27 16:41                 ` Martin Mokrejs
2013-01-27 22:53                   ` Chris Clayton
2013-01-27 23:21                     ` Martin Mokrejs
2013-01-28  2:40                     ` Yijing Wang
2013-01-28 10:12                       ` Chris Clayton
2013-01-28 10:56                         ` Martin Mokrejs
2013-01-28 11:01                           ` Chris Clayton
2013-01-28 11:15                             ` Yijing Wang [this message]
2013-01-28 10:58                         ` Yijing Wang
2013-01-28 11:23                         ` Chris Clayton
2013-01-28 12:12                           ` Martin Mokrejs
2013-01-28 12:26                             ` Yijing Wang
2013-01-28 19:11                             ` Chris Clayton
2013-01-28 21:02                               ` Martin Mokrejs
2013-01-31 12:09                                 ` Chris Clayton
2013-01-31 13:05                                   ` Martin Mokrejs
2013-03-06 23:45                                   ` Bjorn Helgaas
2013-03-07 16:28                                     ` Chris Clayton
2013-03-07 17:30                                       ` Bjorn Helgaas
2013-03-07 20:21                                         ` Chris Clayton
2013-03-08  0:39                                           ` Bjorn Helgaas
2013-03-08 10:44                                             ` Chris Clayton
2013-03-08 22:57                                               ` Bjorn Helgaas
2013-03-09  9:20                                                 ` Chris Clayton
2013-03-12 22:20                                                   ` Bjorn Helgaas
2013-03-15 22:48                                                     ` Bjorn Helgaas
2013-03-19 15:46                                                       ` Chris Clayton
2013-04-01 17:28                                                         ` Bjorn Helgaas
2013-07-09  9:35                                                           ` Chris Clayton
2013-07-09 20:19                                                             ` Bjorn Helgaas

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=51065DC0.5080609@huawei.com \
    --to=wangyijing@huawei.com \
    --cc=chris2553@googlemail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mmokrejs@fold.natur.cuni.cz \
    --cc=wangyijing0307@gmail.com \
    /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).