[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <nycvar.YFH.7.76.1905271126480.1962@cbobk.fhfr.pm>
Date: Mon, 27 May 2019 11:29:19 +0200 (CEST)
From: Jiri Kosina <jikos@...nel.org>
To: Dongli Zhang <dongli.zhang@...cle.com>
cc: Keith Busch <kbusch@...nel.org>, Jens Axboe <axboe@...nel.dk>,
Sagi Grimberg <sagi@...mberg.me>, linux-kernel@...r.kernel.org,
linux-nvme@...ts.infradead.org,
Keith Busch <keith.busch@...el.com>,
Hannes Reinecke <hare@...e.de>, Christoph Hellwig <hch@....de>
Subject: Re: [5.2-rc1 regression]: nvme vs. hibernation
On Sat, 25 May 2019, Dongli Zhang wrote:
> Looks this has been discussed in the past.
>
> http://lists.infradead.org/pipermail/linux-nvme/2019-April/023234.html
>
> I created a fix for a case but not good enough.
>
> http://lists.infradead.org/pipermail/linux-nvme/2019-April/023277.html
That removes the warning, but I still seem to have ~1:1 chance of reboot
(triple fault?) immediately after hibernation image is read from disk.
Seems like that has been going all the way down to 4.19, which seems to be
rock stable. It's a bit hard to bisect, as I am not really 100% sure
whether this is one issue or two intermixed ones, and it doesn't reproduce
completely reliably.
--
Jiri Kosina
SUSE Labs
Powered by blists - more mailing lists