From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christian Borntraeger Date: Mon, 26 Jul 2004 06:19:36 +0000 Subject: Re: [PATCH] Limit number of concurrent hotplug processes Message-Id: <200407260819.36739.linux-kernel@borntraeger.net> List-Id: References: <40FD23A8.6090409@suse.de> <20040725182006.6c6a36df.akpm@osdl.org> In-Reply-To: <20040725182006.6c6a36df.akpm@osdl.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: linux-kernel@vger.kernel.org Cc: Andrew Morton , Hannes Reinecke , linux-hotplug-devel@lists.sourceforge.net Andrew Morton wrote: > Hannes Reinecke wrote: > > the attached patch limits the number of concurrent hotplug processes. > hm, it's a bit sad that this happens. Are you able to tell us more about > what is causing such an explosion of module probes? I dont know exactly which scenario Hannes has seen, but its quite simple to trigger this scenario with almost any s390/zSeries. Using the Hardware Management Console or z/VM you are able to hotplug (deactive/activate/attach/detach) almost every channel path. As a channel path can connect a big bunch of devices lots of machine checks are triggered, which causes lots of hotplugs. The same amount of machine checks could happen if a hardware failure happens. Some month ago I played around with a diet version of hotplug. This program was fast and small enough to make my scenario work properly. Nevertheless, as hannes already stated this will only delay the problem. cheers Christian ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_idG21&alloc_id040&op=click _______________________________________________ Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net Linux-hotplug-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel