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