Re: linux-next 20141216 BUG: sleeping function called from invalid context at mm/slab.c:2849

Valdis.Kletnieks
2014-12-18T19:21:13Z

[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]

On Thu, 18 Dec 2014 11:50:20 -0500, Eric Paris said:
> On Thu, 2014-12-18 at 11:45 -0500, Valdis.Kletnieks@vt.edu wrote:
> > On Tue, 16 Dec 2014 20:09:54 -0500, Valdis Kletnieks said:
> >
> > > Spotted these two while booting single-user on 20141216. 20141208
> > > doesn't throw these, so it's something in the last week or so..
> >
> > Gaah! Turns out that 20141208 *is* susceptible - it had been booting
> > just fine for several days, but it went around the bend, apparently due
> > to a userspace or initrd change.
>
> $5 says you updated systemd?

Actually, yeah. yum.log says:

Dec 12 14:08:09 Updated: systemd-218-1.fc22.x86_64

and things started going downhill that evening. Damned if I know what 218
was doing to cause the issues. (Other RPM update that looked vaguely
related was for selinux-policy, but again, damned if I know what a policy
file could contain that would change the behavior...)

Is it worth backing it to -217, or do we have a handle on the issue and
systemd is just the messenger?

[-- Attachment #2: Type: application/pgp-signature, Size: 848 bytes --]