On Mon, Nov 07, 2022 at 04:14:54PM -0500, James Puthukattukaran wrote: > > There is a path to disable the controller and that code ran but did > not help. I checked wit the nvme folks and Keith mentioned that there > might be an issue with the nvme queue management. Unfortunately, we > can't try newer kernels in the field. So, looking for a way to just > "shut off the device" when we have scenarios like this where we can't > untangle the mess. Well, I didn't request you try new kernels in the field. I asked if you could experiment with a newer one on a development machine to confirm if the bug was fixed by some of the significant changes in this path so that we could confirm a reason to port to stable. You're going to have to change your kernel to fix this observation, so it would be worth the effort to know if the changes being considered actually address the problem. If you're just looking for a work-around for this specific scenario, sorry, I don't think we'll find one. You should just avoid this scenario if you can't change your kernel.
