From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2992480AbXCBOZx (ORCPT ); Fri, 2 Mar 2007 09:25:53 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S2992484AbXCBOZw (ORCPT ); Fri, 2 Mar 2007 09:25:52 -0500 Received: from mail.tpi.com ([198.107.51.143]:1804 "EHLO mail.tpi.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2992480AbXCBOZv (ORCPT ); Fri, 2 Mar 2007 09:25:51 -0500 Message-ID: <45E833ED.2070402@tpi.com> Date: Fri, 02 Mar 2007 07:25:49 -0700 From: Tim Gardner User-Agent: Thunderbird 1.5.0.9 (X11/20060911) MIME-Version: 1.0 To: Pavel Machek CC: nigel@nigel.suspend2.net, linux-kernel@vger.kernel.org, Ben Collins Subject: Re: Resume from S2R fails after dpm_resume() References: <45E5E799.1000502@tpi.com> <20070302141259.GJ2156@elf.ucw.cz> In-Reply-To: <20070302141259.GJ2156@elf.ucw.cz> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Pavel Machek wrote: > Hi! > >> I instrumented 2.6.21-rc1 base/power/resume.c device_resume() with >> TRACE_RESUME(0) as the last statement in the function. Sure enough it >> was the last hash value in the RTC after a hard reboot when resume failed: >> >> [ 12.028820] hash matches drivers/base/power/resume.c:104 >> >> The machine appears to be absolutely wedged after initiating resume by >> pressing the power button. The disk flashes for a half second or so, >> then thats it. >> >> It is a Dell XPS, BIOS rev A04. I'm using 'echo 1 > /sys/power/pm_trace; >> echo mem > /sys/power/state' to initiate the S2R sequence. >> >> Any suggestions on where to go from here? > > Did it work ok in 2.6.20? Can you try to get video working/get serial > console/something? > Pavel Pavel, The last version that worked well was Ubuntu Edgy (2.6.17). It was broken by 2.6.18. I have not started the 'git bisect' process, instead I've been trying to figure out why it doesn't work in 2.6.21-rc2. Using the TRACE_RESUME macro I've drilled down to kernel/printk.c:__call_console_drivers. So far the last trace info that I have is just before the call to con->write(). I'm trying to figure out what driver has registered as the console (intel_agp or agpgart?). Am I banging my head on a known problem? rtg -- Tim Gardner timg@tpi.com www.tpi.com OR 503-601-0234 x102 MT 406-443-5357