From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: James Wang <jnwang@suse.com>, Pingfan Liu <kernelfans@gmail.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: tiwai@suse.de, bpetkov@suse.de, linux-kernel@vger.kernel.org
Subject: Re: [REGRESSION] Errors at reboot after 722e5f2b1eec
Date: Wed, 12 Sep 2018 11:56:18 +0200 [thread overview]
Message-ID: <19d8cdd3-7f22-4066-e77f-8d17bf50bee7@intel.com> (raw)
In-Reply-To: <14f8bb1c-ef13-1329-b144-d487949615e5@suse.com>
On 9/12/2018 11:10 AM, James Wang wrote:
>
> On 09/12/2018 02:41 PM, Pingfan Liu wrote:
>> Cc James, could you try to enable initcall_debug, and paste the
>> shutdown seq with 722e5f2b1eec ("driver core: Partially revert "driver
>> core: correct device's shutdown order"") and without it?
> OK. And I will scheudule some testing orders, ahah, I'm in a business trip.
> All operations will be a little bit delay, but I will make it done.
>
> James
>
Can you please open a Bugzilla entry at bugzilla.kernel.org for the
tracking of this issue and attach the results to that one for future
reference?
next prev parent reply other threads:[~2018-09-12 9:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <s5hk1ns1m8n.wl-tiwai@suse.de>
2018-09-11 9:33 ` [REGRESSION] Errors at reboot after 722e5f2b1eec Greg Kroah-Hartman
2018-09-11 10:51 ` Rafael J. Wysocki
2018-09-11 11:01 ` Borislav Petkov
2018-09-11 11:55 ` Takashi Iwai
2018-09-11 12:26 ` James Wang
[not found] ` <441b2b19-1a73-4cde-913d-61a9f8072f08@suse.com>
2018-09-11 12:15 ` Takashi Iwai
2018-09-13 10:03 ` James Wang
2018-09-13 14:13 ` Rafael J. Wysocki
2018-09-14 2:29 ` Pingfan Liu
2018-09-14 6:26 ` Rafael J. Wysocki
2018-09-14 7:14 ` Borislav Petkov
2018-09-12 6:41 ` Pingfan Liu
2018-09-12 9:10 ` James Wang
2018-09-12 9:56 ` Rafael J. Wysocki [this message]
2018-09-13 15:21 ` James Wang
2018-09-13 20:50 ` Rafael J. Wysocki
2018-09-14 6:23 ` James 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=19d8cdd3-7f22-4066-e77f-8d17bf50bee7@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=bpetkov@suse.de \
--cc=gregkh@linuxfoundation.org \
--cc=jnwang@suse.com \
--cc=kernelfans@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tiwai@suse.de \
/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