[lkml]   [2014]   [Oct]   [15]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [systemd-devel] [RFC v2 3/6] kthread: warn on kill signal if not OOM
16.10.2014 01:41, Anatol Pomozov wrote:
> True. module name should be enough. In this case to debug the issue user needs:
> - disable failing udev rule (or blacklist module?)
> - reboot, it will let the user get into shell
> - modprobe the failing module
> - use sysrq-trigger to get more information about stuck process

Nitpick: this only works only if the "stuck modprobe" bug is 100%
reproducible. Which is not a given. So it is better to collect as much
information about the bug when it is noticed by systemd.

Alexander E. Patrakov

 \ /
  Last update: 2014-10-15 22:21    [W:0.091 / U:0.384 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site