From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: Re: swsusp 'disk' fails in bk-current - intel_agp at fault? Date: Wed, 30 Mar 2005 01:52:13 -0800 Message-ID: <20050330095213.GA12632@kroah.com> References: <4243252D.6090206@suse.de> <20050324235439.GA27902@hexapodia.org> <4243D854.2010506@suse.de> <20050329181831.GB8125@elf.ucw.cz> <20050329192339.GE8125@elf.ucw.cz> <20050329205225.GF8125@elf.ucw.cz> Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============068671297222429928==" Return-path: In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: linux-pm-bounces-qjLDD68F18O7TbgM5vRIOg@public.gmane.org Errors-To: linux-pm-bounces-qjLDD68F18O7TbgM5vRIOg@public.gmane.org To: Patrick Mochel Cc: Vojtech Pavlik , Andy Isaacson , Linux-pm mailing list , Stefan Seyfried , kernel list List-Id: linux-pm@vger.kernel.org --===============068671297222429928== Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Tue, Mar 29, 2005 at 01:23:35PM -0800, Patrick Mochel wrote: > > On Tue, 29 Mar 2005, Pavel Machek wrote: > > > I don't really want us to try execve during resume... Could we simply > > artifically fail that execve with something if (in_suspend()) return > > -EINVAL; [except that in_suspend() just is not there, but there were > > some proposals to add it]. > > > > Or just avoid calling hotplug at all in resume case? And then do > > coldplug-like scan when userspace is ready... > > I thought that cold-plugging only worked for devices, not all objects. We can walk the whole sysfs tree and create "cold" hotplug events. udevstart does that for devices that udev cares about (as an example.) > Can we just queue up hotplug events? That way we wouldn't lose any across > the transition, and could be used to send resume events to userspace for > various devices that need help.. Ick, I really hate this idea, but there is a patch in the SuSE kernel to do this at boot time. Hopefully the author of that patch resubmitts it again and maybe it will make it eventually into mainline... thanks, greg k-h --===============068671297222429928== Content-Type: text/plain; charset="iso-8859-1" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline --===============068671297222429928==--