From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jiri Slaby Subject: Re: swsusp regression (s2dsk) [Was: 2.6.18-rc2-mm1] Date: Sun, 30 Jul 2006 01:57:41 +0159 Message-ID: <44CBF60C.3090508@gmail.com> References: <20060727015639.9c89db57.akpm@osdl.org> <44CBA1AD.4060602@gmail.com> <200607292059.59106.rjw@sisk.pl> <44CBE9D5.9030707@gmail.com> <20060729232216.GB1983@elf.ucw.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20060729232216.GB1983@elf.ucw.cz> Sender: linux-kernel-owner@vger.kernel.org To: Pavel Machek Cc: Jiri Slaby , "Rafael J. Wysocki" , Andrew Morton , linux-kernel@vger.kernel.org, linux-pm@osdl.org, linux-mm@kvack.org List-Id: linux-pm@vger.kernel.org Pavel Machek napsal(a): > Hi! > >>>> I have problems with swsusp again. While suspending, the very last thing kernel >>>> writes is 'restoring higmem' and then hangs, hardly. No sysrq response at all. >>>> Here is a snapshot of the screen: >>>> http://www.fi.muni.cz/~xslaby/sklad/swsusp_higmem.gif >>>> >>>> It's SMP system (HT), higmem enabled (1 gig of ram). >>> Most probably it hangs in device_power_up(), so the problem seems to be >>> with one of the devices that are resumed with IRQs off. >>> >>> Does vanila .18-rc2 work? >> Yup, it does. > > Can you try up kernel, no highmem? (mem=512M)? It writes then: p16v: status 0xffffffff, mask 0x00001000, pvoice f7c04a20, use 0 in endless loop when resuming -- after reading from swap. regards, -- Jiri Slaby faculty of informatics, masaryk university, brno, cz e-mail: jirislaby gmail com, gpg pubkey fingerprint: B674 9967 0407 CE62 ACC8 22A0 32CC 55C3 39D4 7A7E