On 6/8/18 2:07 PM, valdis.kletni...@vt.edu wrote:
> On Thu, 07 Jun 2018 18:41:35 -0400, valdis.kletni...@vt.edu said:
>> On Thu, 07 Jun 2018 17:14:01 -0400, Mike Snitzer said:
>>> Can you please share what you test is? We've gotten lots of reports
>>> with failure following wake_up but I don't hav
On Thu, 07 Jun 2018 18:41:35 -0400, valdis.kletni...@vt.edu said:
> On Thu, 07 Jun 2018 17:14:01 -0400, Mike Snitzer said:
> > Can you please share what you test is? We've gotten lots of reports
> > with failure following wake_up but I don't have a canned test to trigger
>
> Just a laptop with 16G
On Thu, 07 Jun 2018 17:14:01 -0400, Mike Snitzer said:
> Can you please share what you test is? We've gotten lots of reports
> with failure following wake_up but I don't have a canned test to trigger
Just a laptop with 16G of RAM, no clear reproducer - Chrome with a lot of
tabs, a mail reader, a
On Thu, Jun 07 2018 at 4:40pm -0400,
valdis.kletni...@vt.edu wrote:
> I've hit this one twice today with pretty much the same traceback.
> The disk has 3 partitions - one for EFI, one for /boot, and then the rest of
> the disk is a cryptluks partition that contains a dozen or so LVM logical
> vo
I've hit this one twice today with pretty much the same traceback.
The disk has 3 partitions - one for EFI, one for /boot, and then the rest of
the disk is a cryptluks partition that contains a dozen or so LVM logical
volumes.
'git log -- drivers/md' didn't show any obvious suspects since next-201
