From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner+willy=40w.ods.org-S266345AbUHBHzl@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S266345AbUHBHzl (ORCPT <rfc822;willy@w.ods.org>);
	Mon, 2 Aug 2004 03:55:41 -0400
Received: (majordomo@vger.kernel.org) by vger.kernel.org id S266347AbUHBHzl
	(ORCPT <rfc822;linux-kernel-outgoing>);
	Mon, 2 Aug 2004 03:55:41 -0400
Received: from traminer.chepelov.org ([62.212.101.212]:46086 "EHLO
	traminer.chepelov.org") by vger.kernel.org with ESMTP
	id S266345AbUHBHzh (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Mon, 2 Aug 2004 03:55:37 -0400
Date: Mon, 2 Aug 2004 09:55:34 +0200
To: Patrick Mochel <mochel@digitalimplant.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: swsusp in 2.6.8-rc2-mm1
Message-ID: <20040802075534.GA22537@chepelov.org>
References: <20040729232204.GA8020@chepelov.org> <Pine.LNX.4.50.0408012320500.4359-100000@monsoon.he.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=iso-8859-15
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <Pine.LNX.4.50.0408012320500.4359-100000@monsoon.he.net>
X-Face: "99`N"mZV/:<T->OLp[>#d3R;u.!ivtwAEpIQDL8rD#;L3Wm)~^)Uv=#;S!LZf1y8oRY7J#JR\Lr{*4Cn*32C89ln>0~5~tm--}j%hvhj+vtW><xbwA=@G8M||zPV0-r`:6zhMqq+_OC_0W*-:Wxzm3%|A5EE}VFnIgRU=+,L-hGdM"j&l'_^zK+%MBOsdmi#e3(3fGg^SGM
Accept-Languages: fr, en, ru 
User-Agent: Mutt/1.5.6i
From: Cyrille Chepelov <cyrille@chepelov.org>
Sender: linux-kernel-owner@vger.kernel.org
X-Mailing-List: linux-kernel@vger.kernel.org

Le Sun, Aug 01, 2004, à 11:22:04PM -0700, Patrick Mochel a écrit:

> On Fri, 30 Jul 2004, Cyrille Chepelov wrote:

> > Long story made short, it seems that the new swsusp code felt like
> > dereferencing a NULL, and I thought you'd might want to know about that.
> > I know it's pretty bad form to send an oops in a photographic way, but
> > that's better than nothing and I hope you'll be able to exploit this.
> >
> > I've put the stuff at http://www.chepelov.org/cyrille/swsusp
> 
> It's better than nothing, but would please post to the list next time.
> That way other people with similar problems may be able to help, too.
> 
> Hrm, I can't seem to connect..will look into it later..

OK, sorry about that. My 486 router/web server is dying, and I've got
some heavy reformatting/replacement action pending next week. Here's an
alternative address for now:
	http://perso.crans.org/~chepelov/swsusp/

I've put the list on CC: too (I can't subscribe, otherwise I'll really
kill the 486 [die spammers die!] before its time has come, but I'll try
to follow through the archives).

Thanks in advance!

	-- Cyrille

--