Re: [systemd-devel] Problems with systemd master

2014-02-15 Thread Koen Kooi
Op 14 feb. 2014, om 19:16 heeft Greg KH gre...@linuxfoundation.org het volgende geschreven: On Fri, Feb 14, 2014 at 02:30:00PM -0300, Cristian Rodríguez wrote: El 14/02/14 13:32, Richard Purdie escribió: Both conditions are checked, can you find out why the second seems to fail too, it

[systemd-devel] Problems with systemd master

2014-02-14 Thread Richard Purdie
Hi, I work on the Yocto Project and we've been having some stability issues with systemd based images on our automated testing infrastructure. We default to the last released version but it appears there have been a lot of changes in master so I tried the latest git master in the hope that this

Re: [systemd-devel] Problems with systemd master

2014-02-14 Thread Kay Sievers
On Fri, Feb 14, 2014 at 4:23 PM, Richard Purdie richard.pur...@linuxfoundation.org wrote: systemd[1]: Expecting device dev-ttyS0.device... Expecting device dev-ttyS0.device... systemd[1]: job_get_timeout dev-ttyS0.device 1/96903843 0/18446744073709551615 - 1/96903843 [* ] A

Re: [systemd-devel] Problems with systemd master

2014-02-14 Thread Richard Purdie
On Fri, 2014-02-14 at 16:47 +0100, Kay Sievers wrote: On Fri, Feb 14, 2014 at 4:23 PM, Richard Purdie richard.pur...@linuxfoundation.org wrote: systemd[1]: Expecting device dev-ttyS0.device... Expecting device dev-ttyS0.device... systemd[1]: job_get_timeout dev-ttyS0.device

Re: [systemd-devel] Problems with systemd master

2014-02-14 Thread Cristian Rodríguez
El 14/02/14 13:32, Richard Purdie escribió: Both conditions are checked, can you find out why the second seems to fail too, it shouldn't? CONFIG_FHANDLE is in your kernel? No, it wasn't. I enabled that and that image started working better, thanks! I believe we should throw a big fat

Re: [systemd-devel] Problems with systemd master

2014-02-14 Thread Greg KH
On Fri, Feb 14, 2014 at 02:30:00PM -0300, Cristian Rodríguez wrote: El 14/02/14 13:32, Richard Purdie escribió: Both conditions are checked, can you find out why the second seems to fail too, it shouldn't? CONFIG_FHANDLE is in your kernel? No, it wasn't. I enabled that and that image