linux-kernel - Re: [PATCH 2/2] PCI,pciehp: avoid add a device already exist during pciehp

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: Windows password security audit tool. GUI, reports in PDF.

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

Date:	Thu, 11 Jul 2013 12:19:13 +0200
From:	Paul Bolle <pebolle@...cali.nl>
To:	Yijing Wang <wangyijing@...wei.com>
Cc:	Bjorn Helgaas <bhelgaas@...gle.com>, linux-kernel@...r.kernel.org,
	linux-pci@...r.kernel.org, Rafael <rjw@...k.pl>,
	Hanjun Guo <guohanjun@...wei.com>, jiang.liu@...wei.com,
	Oliver Neukum <oneukum@...e.de>,
	Gu Zheng <guz.fnst@...fujitsu.com>
Subject: Re: [PATCH 2/2] PCI,pciehp: avoid add a device already exist during
 pciehp_resume

Yijing,

On Thu, 2013-07-11 at 11:55 +0800, Yijing Wang wrote:
> Can you provide the lspci -vvv and lspci -xxxx info messages ?
> I want to confirm your hardware information which cause your resume error.
> You can get these messages in any kernel version, that's ok.

Would it be sufficient to send that information just for the two pcie
ports on my laptop, and the wireless card that is present in one of
those two ports?

And would it be OK to send that information off list?

> When you suspend and resume the system, the wireless card is always
> present in pcie slot, right?

Yes. I actually wouldn't even know how to remove it. I only discovered
my wireless card was in a pcie slot because of the error messages at
resume (which started a few releases ago, I think v3.7).


Paul Bolle

--
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/