Date: Fri, 7 Jan 2005 00:48:29 +0100
From: Pavel Machek <pavel@ucw.cz>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-mm2: swsusp regression
Message-ID: <20050106234829.GF28777@elf.ucw.cz>
References: <20050106002240.00ac4611.akpm@osdl.org> <200501061848.11719.rjw@sisk.pl> <20050106225233.GD2766@elf.ucw.cz> <200501070041.43023.rjw@sisk.pl>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200501070041.43023.rjw@sisk.pl>
User-Agent: Mutt/1.5.6+20040907i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1316
Lines: 37

Hi!

> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.10/2.6.10-mm2/
> > > > 
> > > > - Various minorish updates and fixes
> > > 
> > > There's an swsusp regression on my box (AMD64) wrt -mm1.  Namely, 
> 2.6.10-mm2 
> > > does not suspend, but hangs solid right after the critical section, 100% 
> of 
> > > the time.
> > 
> > can you comment out device_power_{down,up} from
> > swsusp_{suspend,resume} and see what happens?
> 
> It works just fine.

Ok, problem is that device_power_{down,up} is right thing, and
neccessary for many machines to work...

...so... could you go through sysdev_register()s, one by one,
commenting them to see which one causes the regression? That driver
then needs to be fixed.

Go after mtrr and time in first places.
								Pavel
PS: Probably drop andrew from reply; he probably gets enough mail
anyway. I want this one to go to him so that he does not back up the
patch, through.
-- 
People were complaining that M$ turns users into beta-testers...
...jr ghea gurz vagb qrirybcref, naq gurl frrz gb yvxr vg gung jnl!
-
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/