From: Martin Mokrejs <mmokrejs@fold.natur.cuni.cz>
To: Yinghai Lu <yinghai@kernel.org>
Cc: Thomas Gleixner <tglx@linutronix.de>,
linux-pci@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: 3.2.11: PCI Express card cannot be re-detected withing cca 60sec timeframe
Date: Tue, 17 Apr 2012 11:34:07 +0200 [thread overview]
Message-ID: <4F8D390F.9050408@fold.natur.cuni.cz> (raw)
In-Reply-To: <CAE9FiQWSw1h772ijZ6YL4EujwjgvZ84bbDx9VbF_cdE63D-41w@mail.gmail.com>
Yinghai Lu wrote:
> On Tue, Apr 17, 2012 at 1:46 AM, Yinghai Lu <yinghai@kernel.org> wrote:
>> On Tue, Apr 17, 2012 at 12:27 AM, Martin Mokrejs
>> <mmokrejs@fold.natur.cuni.cz> wrote:
>>>>
>>>> can you send out lspci -vvxxxx -s 00:1c.7 after removing USB 3.0 express card?
>>>
>>> No, that did not help (tried on 3.4-rc3). First I plugged in the NEC uPD720200 USB3.0 card
>>> and unplugged it (card removal not reported :(), saved the lspci output.
>>> Then I inserted the FireWire card, unplugged, again saved the lspci output.
>>> Finally, saved the dmesg. All three files are attached.
>>
>> for USB 3.0:
>> SltSta: Status: AttnBtn- PowerFlt- MRL- CmdCplt- PresDet+ Interlock-
>> Changed: MRL- PresDet- LinkState+
>
> LnkSta: Speed 2.5GT/s, Width x1, TrErr- Train- SlotClk+ DLActive+
> BWMgmt+ ABWMgmt-
>
> link still active even that card get removed, that looks like chipset
> have problem.
Yinghai,
so what should I ask Dell for? To fix BIOS of the laptop? What exactly? Or do you think
this is a hardware issue with the chipset?
# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor Family DRAM Controller (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #2 (rev 05)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset Family High Definition Audio Controller (rev 05)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 1 (rev b5)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 2 (rev b5)
00:1c.3 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 4 (rev b5)
00:1c.4 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 5 (rev b5)
00:1c.7 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset Family PCI Express Root Port 8 (rev b5)
00:1d.0 USB controller: Intel Corporation 6 Series/C200 Series Chipset Family USB Enhanced Host Controller #1 (rev 05)
00:1f.0 ISA bridge: Intel Corporation HM67 Express Chipset Family LPC Controller (rev 05)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series Chipset Family 6 port SATA AHCI Controller (rev 05)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family SMBus Controller (rev 05)
05:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168B PCI Express Gigabit Ethernet controller (rev 06)
09:00.0 Network controller: Intel Corporation Centrino Wireless-N 1030 (rev 34)
0b:00.0 USB controller: Texas Instruments Device 8241 (rev 02)
#
Martin
next prev parent reply other threads:[~2012-04-17 9:34 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4F6A483D.50702@fold.natur.cuni.cz>
[not found] ` <CAE9FiQVnErU-cska4gpinyj-LOup-U+3vsEG2z_-7h6kyREYtw@mail.gmail.com>
[not found] ` <4F6A5A53.305@fold.natur.cuni.cz>
[not found] ` <CAE9FiQXP7fO9OGN557jdofFFiFj96wL--ZA8X3UPEJ6o9JLvBw@mail.gmail.com>
[not found] ` <4F8BEB1D.9080903@fold.natur.cuni.cz>
[not found] ` <CAE9FiQXoX3J6P_9Tun_XbkK3egvSeBZxAtC13HacFDO0fwmZaA@mail.gmail.com>
[not found] ` <4F8C6E4E.1000205@fold.natur.cuni.cz>
2012-04-16 20:53 ` Yinghai Lu
2012-04-17 1:42 ` Yinghai Lu
2012-04-17 2:48 ` Yinghai Lu
2012-04-17 7:27 ` Martin Mokrejs
2012-04-17 8:46 ` Yinghai Lu
2012-04-17 8:58 ` Yinghai Lu
2012-04-17 9:34 ` Martin Mokrejs [this message]
2012-04-17 17:07 ` Yinghai Lu
2012-04-17 19:02 ` Yinghai Lu
2012-04-18 17:53 ` Martin Mokrejs
2012-04-18 19:48 ` Yinghai Lu
2012-04-18 20:29 ` Martin Mokrejs
2012-04-18 20:58 ` Yinghai Lu
2012-04-18 22:55 ` Martin Mokrejs
2012-04-19 1:57 ` Yinghai Lu
2012-04-19 3:16 ` Mark Lord
2012-04-19 23:16 ` Martin Mokrejs
2012-04-19 21:48 ` Yinghai Lu
2012-04-20 2:06 ` Yinghai Lu
2012-04-20 11:23 ` Martin Mokrejs
2012-04-20 16:01 ` Yinghai Lu
2012-04-20 17:25 ` Martin Mokrejs
2012-04-20 17:28 ` Martin Mokrejs
2012-04-20 18:47 ` Yinghai Lu
2012-04-20 23:17 ` Sarah Sharp
2012-04-21 0:09 ` Yinghai Lu
2012-04-21 4:46 ` Yinghai Lu
2012-04-21 9:01 ` Martin Mokrejs
2012-04-21 9:12 ` Martin Mokrejs
2012-04-21 13:25 ` Sarah Sharp
2012-04-21 18:46 ` Yinghai Lu
2012-04-24 20:47 ` Martin Mokrejs
2012-04-24 20:48 ` Martin Mokrejs
2012-04-26 16:08 ` Yinghai Lu
2012-04-26 22:08 ` Martin Mokrejs
2012-04-26 22:44 ` Yinghai Lu
2012-04-26 23:26 ` Martin Mokrejs
2012-04-27 3:51 ` Yinghai Lu
2012-04-20 23:50 ` Martin Mokrejs
2012-04-21 0:04 ` Yinghai Lu
2012-05-04 16:16 ` Martin Mokrejs
2012-04-19 17:32 ` Martin Mokrejs
2012-04-19 18:13 ` Yinghai Lu
2012-05-04 15:58 ` Martin Mokrejs
2012-05-04 20:43 ` Martin Mokrejs
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=4F8D390F.9050408@fold.natur.cuni.cz \
--to=mmokrejs@fold.natur.cuni.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=tglx@linutronix.de \
--cc=yinghai@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
all inboxes | Powered by JetHome®