From mboxrd@z Thu Jan 1 00:00:00 1970 From: Pavel Machek Subject: Re: Hotplug events during sleep transition Date: Thu, 22 Dec 2005 15:34:49 +0100 Message-ID: <20051222143448.GB9800@elf.ucw.cz> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============71700109300311254==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces@lists.osdl.org Errors-To: linux-pm-bounces@lists.osdl.org To: Alan Stern Cc: Linux-pm mailing list List-Id: linux-pm@vger.kernel.org --===============71700109300311254== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Hi! > I recently worked on a patch to unbind USB drivers that don't have > suspend/resume methods, and then rebind them when the system comes back > up. There was an unexpected effect: In some cases the unbind or rebind > operations caused hotplug events, which started up new user processes at a > time when everything was supposed to be frozen. Obviously this is not a > good thing. > > Is there some other way these sorts of events can be handled? For > instance, can the hotplug system be smart enough to delay creating the new > processes? Or can they be created already in a frozen state? There were some problems with this already... but I do not recall what the solution was. lkml thread, IIRC. Were it PCMCIA cards or something like that? Pavel -- Thanks, Sharp! --===============71700109300311254== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============71700109300311254==--