Welcome to DU! The truly grassroots left-of-center political community where regular people, not algorithms, drive the discussions and set the standards. Join the community: Create a free account Support DU (and get rid of ads!): Become a Star Member Latest Breaking News Editorials & Other Articles General Discussion The DU Lounge All Forums Issue Forums Culture Forums Alliance Forums Region Forums Support Forums Help & Search

Open Source and Free Software

Recursion

(56,582 posts)

7. That will hit any kernel whatsoever; it's a bug in systemd

Reply to defacto7 (Reply #5)

Fri May 9, 2014, 03:44 AM

May 2014

There are invalid assert() calls in systemd that fill up kmsg (because PID 1 has to write to kmsg before the regular dmesg ring is brought up) to such an extent that getty or logind or whatever can't spawn a new login shell.

On the plus side, Sievers is the one responsible for the wrongheaded and potentially disastrous push to move all of dbus into the kernel, so this delays that for a while, thankfully.

Edit history

Please sign in to view edit histories.

Recommendations

0 members have recommended this reply (displayed in chronological order):

8 replies

= new reply since forum marked as read

Highlight:

Linus Torvalds suspends key Linux developer [View all] Recursion May 2014 OP

wtf bananas May 2014 #1

Although I see Andrea's point in principle defacto7 May 2014 #2

The real problem is there should not be a "wandering init proc" Recursion May 2014 #4

"PID 1 shouldn't be doing anything else" defacto7 May 2014 #6

Oh, now I see what you're talking about. Andrea's thing is a different thread Recursion May 2014 #8

There was an assertion failure in systemd Recursion May 2014 #3

On what kernels are these problems centering now? defacto7 May 2014 #5

That will hit any kernel whatsoever; it's a bug in systemd Recursion May 2014 #7