Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754888AbZKBKvo (ORCPT ); Mon, 2 Nov 2009 05:51:44 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1754858AbZKBKvn (ORCPT ); Mon, 2 Nov 2009 05:51:43 -0500 Received: from atrey.karlin.mff.cuni.cz ([195.113.26.193]:37545 "EHLO atrey.karlin.mff.cuni.cz" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754774AbZKBKvn (ORCPT ); Mon, 2 Nov 2009 05:51:43 -0500 Date: Mon, 2 Nov 2009 11:51:41 +0100 From: Pavel Machek To: Haojian Zhuang Cc: dsaxena@laptop.org, alan@linux.intel.com, gregkh@suse.de, Daniel Mack , linux-arm-kernel@lists.infradead.org, Eric , Haojian Zhuang , rpurdie@rpsys.net, lenz@cs.wisc.edu, kernel list , Dirk@opfer-online.de, arminlitzel@web.de, Cyril Hrubis , thommycheck@gmail.com, dbaryshkov@gmail.com, omegamoon@gmail.com, utx@penguin.cz, "Rafael J. Wysocki" Subject: Re: Possible suspend/resume regression in .32-rc? Message-ID: <20091102105141.GB11426@elf.ucw.cz> References: <20091031013427.GL14091@buzzloop.caiaq.de> <20091101205449.GT14091@buzzloop.caiaq.de> <20091101213343.GA31345@elf.ucw.cz> <20091101220341.GA16698@elf.ucw.cz> <771cded00911020122o3bb5cc96q957c8be1ce7cae46@mail.gmail.com> <20091102093840.GA11426@elf.ucw.cz> <771cded00911020248s2b2b6577o5ec2f3772a09e7b9@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <771cded00911020248s2b2b6577o5ec2f3772a09e7b9@mail.gmail.com> X-Warning: Reading this can be dangerous to your mental health. User-Agent: Mutt/1.5.20 (2009-06-14) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 2253 Lines: 51 On Mon 2009-11-02 06:48:28, Haojian Zhuang wrote: > On Mon, Nov 2, 2009 at 5:38 AM, Pavel Machek wrote: > > On Mon 2009-11-02 05:22:30, Haojian Zhuang wrote: > >> On Sun, Nov 1, 2009 at 6:03 PM, Pavel Machek wrote: > >> > >> Em, it's not caused by the IRQ patch. > >> > >> The kernel is blocked in resume path. When console is resumed, IRQ is > >> already disabled and system is blocked. Actually, IRQ shouldn't be > >> disabled at here. Up to now, I only find which patch will cause this > >> issue. But I can't find the best solution on it. The patch with issue > >> is pasted in below. > >> > >> So this issue is only occused when console suspend is enabled. If you > >> enable no_console_suspend in command, you won't meet this issue. It > >> seems that it's caused by removing termios setting in > >> uart_resume_port() in the below patch. If I add these code back, the > >> issue doesn't occur any more. > > > > Given that it hangs very early, in arch_suspend_enable_irqs() (see my > > other mail), I don't trust your analysis. > > > > I'm not using serial console on spitz, and I have never had successful > > resume with the patch applied. > > It seems that we're talking on different issue with similar symptom. > Please check my test method. While I'm testing suspend with devices > level, kernel is blocked in console resume. In this level, it won't > call arch_suspend_enable_irqs(). This function call is only invoked in > processor level or below. For me, everything but real suspend works. I do _not_ have serial console for spitz. > Up to now, I can't reproduce the issue you're talking on my platform > yet. I'll check this issue continuously. I also want to know your > hardware information. Spitz, aka Sharp Zaurus c3000. Can we get the patch reverted till its fixed, so other development can continue? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html -- 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/