linux-kernel - Re: [REGRESSION] Errors at reboot after 722e5f2b1eec

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, 13 Sep 2018 17:21:27 +0200
From:   James Wang <jnwang@...e.com>
To:     "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        Pingfan Liu <kernelfans@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>
Cc:     tiwai@...e.de, bpetkov@...e.de, linux-kernel@...r.kernel.org
Subject: Re: [REGRESSION] Errors at reboot after 722e5f2b1eec



On 09/12/2018 11:56 AM, Rafael J. Wysocki wrote:
> 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?
>
Hi sir,
File a bug is no problem. but which product category should be used.

I attach logs here, first. and then file a bug.
>
>
>

-- 
SUSE Linux GmbH, GF: Felix Imendörffer, Jane Smithard, Graham Norton, HRB 21284 (AG Nürnberg)


View attachment "initcall_debug_with_driver_core.log" of type "text/x-log" (184392 bytes)

View attachment "initcall_debug_without_driver_core.log" of type "text/x-log" (181315 bytes)