Messages in this thread |  | | Date | Thu, 16 Oct 2014 01:46:44 +0600 | From | "Alexander E. Patrakov" <> | Subject | Re: [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
|  |