Hi,
I notice a regression report on Bugzilla [1]. Quoting from it:
> Issue description:
> root:~# lsb_release -a
> No LSB modules are available.
> Distributor ID: Ubuntu
> Description: Ubuntu 22.04 LTS
> Release: 22.04
> Codename: jammy
>
> root:~# uname -a
> Linux dapu-Star-Lake 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
>
> root:~#nvme subsystem-reset /dev/nvme0
>
> root:~#nvme list //This command will hang about 60 seconds.
>
> Issue analysis:
> Maybe it hangs in function nvme_wait_reset. When we revert the following commit, this issue will disappear.
> if (!nvme_wait_reset(ctrl))
> https://github.com/torvalds/linux/commit/1e866afd4bcdd01a70a5eddb4371158d3035ce03?diff=split
See Bugzilla for the full thread.
Anyway, I'm adding this regression to be tracked by regzbot:
#regzbot introduced: 1e866afd4bcdd0 https://bugzilla.kernel.org/show_bug.cgi?id=217745
#regzbot title: listing nvme devices hangs after subsystem reset
Thanks.
[1]: https://bugzilla.kernel.org/show_bug.cgi?id=217745
--
An old man doll... just what I always wanted! - Clara
On 02.08.23 13:41, Bagas Sanjaya wrote:
>
> I notice a regression report on Bugzilla [1]. Quoting from it:
>
>> Issue description:
>> root:~# lsb_release -a
>> No LSB modules are available.
>> Distributor ID: Ubuntu
>> Description: Ubuntu 22.04 LTS
>> Release: 22.04
>> Codename: jammy
>>
>> root:~# uname -a
>> Linux dapu-Star-Lake 5.19.0-46-generic #47~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Jun 21 15:35:31 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
Bagas, please don't forward reports to the developers (and also don't
add them to the regression tracking) if the report is about a problem
with a vendor kernel that is known or likely to be patched[1].
Developers otherwise will just start to ignore your mails, as you are
wasting their time.
Ciao, Thorsten
[1] unless of course the reporter confirmed that the issue also happens
with a fresh vanilla kernel; but that afaics still hasn't happened in
this case yet; and even if that's the case it must be really obvious
when forwarding a report.
>> root:~#nvme subsystem-reset /dev/nvme0
>>
>> root:~#nvme list //This command will hang about 60 seconds.
>>
>> Issue analysis:
>> Maybe it hangs in function nvme_wait_reset. When we revert the following commit, this issue will disappear.
>> if (!nvme_wait_reset(ctrl))
>> https://github.com/torvalds/linux/commit/1e866afd4bcdd01a70a5eddb4371158d3035ce03?diff=split
>
> See Bugzilla for the full thread.
>
> Anyway, I'm adding this regression to be tracked by regzbot:
>
> #regzbot introduced: 1e866afd4bcdd0 https://bugzilla.kernel.org/show_bug.cgi?id=217745
> #regzbot title: listing nvme devices hangs after subsystem reset
>
> Thanks.
>
> [1]: https://bugzilla.kernel.org/show_bug.cgi?id=217745
>