From: Yijing Wang <wangyijing@huawei.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Bjorn Helgaas <bhelgaas@google.com>, <linux-pci@vger.kernel.org>,
Hanjun Guo <guohanjun@huawei.com>, <jiang.liu@huawei.com>,
"Rafael J. Wysocki" <rjw@sisk.pl>,
Oliver Neukum <oneukum@suse.de>,
Gu Zheng <guz.fnst@cn.fujitsu.com>
Subject: Re: [PATCH -v4 1/6] PCI,pciehp: avoid add a device already exist before suspend during resume
Date: Mon, 5 Aug 2013 11:12:03 +0800 [thread overview]
Message-ID: <51FF1803.5090202@huawei.com> (raw)
In-Reply-To: <1375469567.1460.15.camel@x61.thuisdomein>
>
> 0) There's no 0/6 in my mailbox, so I reply to this message.
>
Sorry, I forgot adding your cc into patch 0.
> 1) This series applies cleanly on top of v3.10.5-rc1 (except for some
> odd problem in 6/6, which I mentioned in my reply to 6/6).
>
> 2) However, this series doesn't appear to work on v3.10.5-rc1. After the
> first resume the wireless connection appears to be gone (in Gnome 3).
> iwl4965 is still loaded, but I can't reconnect. That should happen
> automagically.
I found some mistakes in my patch 6/6, I'm very sorry about that.
Will be more careful next time, I will refresh this patch, can your help
to test it again? I will update this patch and resend it soon.
>
> 3) And the second resume apparently hangs the system. Not sure how it
> hangs exactly, but I have to manually shutdown the laptop by pressing
> the power button for a few seconds.
>
> 4) I guess I'll have to respin v3.10.5-rc1 without this series to
> determine if v3.10.5-rc1 or this series causes these issues. But feel
> free to prod me for further tests.
Thanks!
Yijing.
--
Thanks!
Yijing
next prev parent reply other threads:[~2013-08-05 3:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-01 13:06 [PATCH -v4 0/6] Use PCI Serial Number to identify device change Yijing Wang
2013-08-01 13:06 ` [PATCH -v4 1/6] PCI,pciehp: avoid add a device already exist before suspend during resume Yijing Wang
2013-08-02 18:52 ` Paul Bolle
2013-08-02 21:43 ` Paul Bolle
2013-08-05 3:12 ` Yijing Wang [this message]
2013-08-01 13:06 ` [PATCH -v4 2/6] PCI: introduce PCIe Device Serial Number Capability support Yijing Wang
2013-08-01 13:06 ` [PATCH -v4 3/6] PCI: Introduce Vital Product Data Serial Number capability support Yijing Wang
2013-08-01 13:06 ` [PATCH -v4 4/6] PCI: add pci_serial_number_changed() for device change identification Yijing Wang
2013-08-01 13:06 ` [PATCH -v4 5/6] PCI: add inspection of device change in pci_scan_single_device Yijing Wang
2013-08-01 13:06 ` [PATCH -v4 6/6] PCI,pciehp: identify device change during suspend Yijing Wang
2013-08-01 13:12 ` Yijing Wang
2013-08-02 18:42 ` Paul Bolle
2013-08-05 3:05 ` Yijing Wang
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=51FF1803.5090202@huawei.com \
--to=wangyijing@huawei.com \
--cc=bhelgaas@google.com \
--cc=guohanjun@huawei.com \
--cc=guz.fnst@cn.fujitsu.com \
--cc=jiang.liu@huawei.com \
--cc=linux-pci@vger.kernel.org \
--cc=oneukum@suse.de \
--cc=pebolle@tiscali.nl \
--cc=rjw@sisk.pl \
/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).