@Holger, that's my symptoms to tee... :-) Strangely it doesn't effect Arch Linux - running on the same box - with a newer 3.19.2 kernel. So they must have a patch for the issue (but I can't figure out what). Perhaps I'll check through the (stock) kernel configuration as well - to check it matches mine.
Thanks On 31 March 2015 at 01:29, Holger Hoffstätte < holger.hoffstae...@googlemail.com> wrote: > On Mon, 30 Mar 2015 23:22:58 +0100, Bob Wya wrote: > > > I'm getting a bit bogged down trying to build an early release of the > 3.18 > > kernel. Since I can't automatically go back before 3.18.9 now (using > > portage anyway)... > > > > Basically I trying to check if a suspend/resume issue I've got was > > introduced after the 3.18 kernel was released (or was in the base > release). > > I've got a reproduce-able failure to suspend-to-ram with >=3.18.x gentoo > > kernel sources. However this issue is not present with the gentoo kernel > > sources <=3.17.x. (A systemd nfs client mount problem - which blocks the > > suspend-to-ram process.) > > You are probably looking at this bug: > http://thread.gmane.org/gmane.linux.nfs/69717 > > This was introduced in 3.18.9 (as you found out), so simply using vanilla > 3.18.8 should fix it; I don't remember seeing it before. > I never bothered to try and now just stop NFS before suspend. 3.19.x gained > the same problem. > > -h > > >