Date: Wed, 6 Apr 2005 15:19:43 -0700
From: Andrew Morton <akpm@osdl.org>
To: Neil Brown <neilb@cse.unsw.edu.au>
Cc: linux-kernel@vger.kernel.org, Dominik Brodowski <linux@brodo.de>
Subject: Re: 2.6.12-rc2-mm1
Message-Id: <20050406151943.37ff237b.akpm@osdl.org>
In-Reply-To: <16979.16146.433143.743902@cse.unsw.edu.au>
References: <20050405000524.592fc125.akpm@osdl.org>
	<16979.16146.433143.743902@cse.unsw.edu.au>
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1172
Lines: 29

Neil Brown <neilb@cse.unsw.edu.au> wrote:
>
> On Tuesday April 5, akpm@osdl.org wrote:
> > 
> > - Nobody said anything about the PM resume and DRI behaviour in
> >   2.6.12-rc1-mm4.  So it's all perfect now?
> 
> Well, Seeing you asked...
> 
> PM resume certainly seems to be improving.
> My main problem in rc1-mm3 is with PCMCIA.
> If I stop cardmgr before suspend-to-RAM, and then try to
> restart it after resume, I cannot.  Some message about the socket
> being in use, and am I sure there is no other cardmgr running (there
> isn't). 

I don't know whether the PCMCIA problem is due to PCMCIA changes or not. 
The only thing I see having changed between 2.6.12-rc1-mm3 and
2.6.12-rc2-mm1 is the addition of pcmcia-resource-handling-fixes.patch. 
Would you have time to revert that, retest?  

There have been a few problem in the area of device management in
bk-driver-core.  I think we're getting that settled down now.

-
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/