Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755049AbaJJWpl (ORCPT ); Fri, 10 Oct 2014 18:45:41 -0400 Received: from mail-yk0-f172.google.com ([209.85.160.172]:54341 "EHLO mail-yk0-f172.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751514AbaJJWpi (ORCPT ); Fri, 10 Oct 2014 18:45:38 -0400 MIME-Version: 1.0 X-Originating-IP: [84.208.172.182] In-Reply-To: References: <1409899047-13045-1-git-send-email-mcgrof@do-not-panic.com> <20140905141241.GC10455@mtj.dyndns.org> <20140905164405.GA28964@core.coreip.homeip.net> <20140905174925.GA12991@mtj.dyndns.org> <20140905224047.GC15723@mtj.dyndns.org> <20140909011059.GB11706@mtj.dyndns.org> <1410241109.2028.22.camel@jarvis.lan> <1410291346.13298.16.camel@jarvis.lan> From: Tom Gundersen Date: Sat, 11 Oct 2014 00:45:17 +0200 Message-ID: Subject: Re: [systemd-devel] [RFC v2 3/6] kthread: warn on kill signal if not OOM To: Anatol Pomozov Cc: "Luis R. Rodriguez" , Tejun Heo , One Thousand Gnomes , Takashi Iwai , Kay Sievers , Sreekanth Reddy , James Bottomley , Praveen Krishnamoorthy , hare , Nagalakshmi Nandigama , Wu Zhangjin , Tetsuo Handa , "mpt-fusionlinux.pdl" , Tim Gardner , Benjamin Poirier , Santosh Rastapur , Casey Leedom , Hariprasad S , Pierre Fersing , Arjan van de Ven , Abhijit Mahajan , systemd Mailing List , Linux SCSI List , "netdev@vger.kernel.org" , Dmitry Torokhov , Oleg Nesterov , "linux-kernel@vger.kernel.org" , Andrew Morton , Joseph Salisbury Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, Oct 10, 2014 at 11:54 PM, Anatol Pomozov wrote: > 1) Why not to make the timeout configurable through config file? There > is already udev.conf you can put config option there. Thus people with > modprobe issues can easily "fix" the problem. And then decrease > default timeout back to 30 seconds. I agree that long module loading > (more than 30 secs) is abnormal and should be investigated by driver > authors. We can already configure this either on the udev or kernel commandline, is that not sufficient (I don't object to also adding it to the config file, just asking)? > 2) Could you add 'echo w > /proc/sysrq-trigger' to udev code right > before killing the "modprobe" thread? sysrq will print information > about stuck threads (including modprobe itself) this will make > debugging easier. e.g. dmesg here > https://bugs.archlinux.org/task/40454 says nothing where the threads > were stuck. Are the current warnings (in udev git) sufficient (should tell you which module is taking long, but still won't tell you which kernel thread of course)? Cheers, Tom -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/