Re: update-binfmts breaking suspend

2018-04-10 Thread Pavel Machek
Hi! > Ping? See the thread... akpm pointed out fix for autofs, and the problem is gone with newer -next kernels, so I assume the fix fixes it :-). Pavel -- (english)

Re: update-binfmts breaking suspend

2018-04-10 Thread Matthew Wilcox
Ping? On Fri, Apr 06, 2018 at 07:43:55AM -0700, Matthew Wilcox wrote: > Pavel Machek wrote: > > > Failure is not a hang, as they expect, but... machine locks up, but > > > does not suspend, and then continues running after a delay.. > > > > > > [ 35.038766] PM: Syncing filesystems ... done. >

Re: update-binfmts breaking suspend was Re: x32 suspend failuer in Re: linux-next: Tree for Apr 4

2018-04-05 Thread Rafael J. Wysocki
On Thursday, April 5, 2018 10:30:45 PM CEST Pavel Machek wrote: > Hi! > > > > Well, v4.16-rc4 is parent of v4.16-rc6, but next-20180304 is not > > > parent of next-20180307. > > > > > > But you are right that if I do bisect between -linus and -next, it > > > should work. > > > > > > Anyway, does

Re: update-binfmts breaking suspend was Re: x32 suspend failuer in Re: linux-next: Tree for Apr 4

2018-04-05 Thread Pavel Machek
Hi! > > Well, v4.16-rc4 is parent of v4.16-rc6, but next-20180304 is not > > parent of next-20180307. > > > > But you are right that if I do bisect between -linus and -next, it > > should work. > > > > Anyway, does s2ram work for you in -next? Are you testing 32bit? > > Hmm. I tested on T40p. T

update-binfmts breaking suspend was Re: x32 suspend failuer in Re: linux-next: Tree for Apr 4

2018-04-05 Thread Pavel Machek
On Wed 2018-04-04 10:49:05, Pavel Machek wrote: > On Wed 2018-04-04 09:58:17, Rafael J. Wysocki wrote: > > On Wed, Apr 4, 2018 at 9:50 AM, Pavel Machek wrote: > > > Hi! > > > > > >> Please do not add any v4.18 destined stuff to your linux-next included > > >> trees until after v4.17-rc1 has been r