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

Recursion

(56,582 posts)
3. There was an assertion failure in systemd
Thu May 8, 2014, 11:36 PM
May 2014

In principle there's no reason an init shouldn't look at the kernel command line and be more verbose if debug is specified; the problem here was that systemd had two failed assertions that spammed kmsg.

The context here is that udev has been more or less broken since Sievers took it over a few years ago, and Linus has grown progressively more frustrated with

1. its firmware loading not checking for race conditions that lead to a lockup, and
2. Siever's insistence that loading firmware shouldn't be udev's job and the kernel should do it (putting the loading of firmware into userspace was the specific purpose for leaving devfs for udev in the first place)

Recommendations

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

Latest Discussions»Culture Forums»Open Source and Free Software»Linus Torvalds suspends k...»Reply #3