public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dtor_core@ameritech.net>
To: romano@dea.icai.upco.es
Cc: Pavel Machek <pavel@ucw.cz>,
	linux-kernel@vger.kernel.org, Andrew Morton <akpm@osdl.org>
Subject: Re: 2.6.12-rc1 swsusp broken [Was Re: swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel]
Date: Thu, 31 Mar 2005 13:09:49 -0500	[thread overview]
Message-ID: <200503311309.50165.dtor_core@ameritech.net> (raw)
In-Reply-To: <20050331165007.GA29674@pern.dea.icai.upco.es>

On Thursday 31 March 2005 11:50, Romano Giannetti wrote:
> On Thu, Mar 31, 2005 at 10:15:26AM -0500, Dmitry Torokhov wrote:
> > On Thu, 31 Mar 2005 16:47:29 +0200, Romano Giannetti <romanol@upco.es> wrote:
> > > 
> > > The bad news is that with 2.6.12-rc1 (no preempt) swsusp fails to go.
> > 
> > Ok, I see you have an ALPS touchpad. I think this patch will help you
> > with swsusp:
> > 
> > http://marc.theaimsgroup.com/?l=linux-kernel&m=111212532524998&q=raw
> 
> Yes! With this it works ok.
> 
> > Also, could you please try sticking psmouse_reset(psmouse) call at the
> > beginning of drivers/input/mouse/alps.c::alps_reconnect() and see if
> > it can suspend _without_ the patch above.
> 
> It works, too. Which one is the best one? 
>

Both of them are needed as they address two different problems.

-- 
Dmitry

  reply	other threads:[~2005-03-31 19:41 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-29 11:03 swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel Romano Giannetti
2005-03-29 13:20 ` Romano Giannetti
2005-03-29 17:02   ` Romano Giannetti
2005-03-29 18:15     ` Pavel Machek
2005-03-31 14:47       ` 2.6.12-rc1 swsusp broken [Was Re: swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel] Romano Giannetti
2005-03-31 15:15         ` Dmitry Torokhov
2005-03-31 15:41           ` Romano Giannetti
2005-03-31 16:50           ` Romano Giannetti
2005-03-31 18:09             ` Dmitry Torokhov [this message]
2005-04-01 16:14               ` Benoit Boissinot
2005-04-01 16:28                 ` Dmitry Torokhov
2005-04-01 16:43                   ` Touchpad does not work anymore Benoit Boissinot
2005-04-01 17:00                     ` Dmitry Torokhov
2005-04-01 17:29                       ` Benoit Boissinot
2005-04-05  2:21                         ` Benoit Boissinot
2005-03-31 18:29             ` 2.6.12-rc1 swsusp broken [Was Re: swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel] Benoit Boissinot
2005-03-31 22:25               ` noresume breaks next suspend [was Re: 2.6.12-rc1 swsusp broken] Pavel Machek
2005-04-01  0:50                 ` Nigel Cunningham
2005-04-01  3:04                   ` Nigel Cunningham
2005-04-01  9:45                   ` Pavel Machek
     [not found] ` <20050525212520.419ee442.akpm@osdl.org>
     [not found]   ` <20050603094448.GA3218@pern.dea.icai.upco.es>
     [not found]     ` <20050603105010.GA7300@pern.dea.icai.upco.es>
2005-06-03 12:35       ` swsusp, preempt, input and 2.6.12-rc5-mm2 Re: swsusp not working for me on a PREEMPT 2.6.12-rc1 and 2.6.12-rc1-mm3 kernel Romano Giannetti

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200503311309.50165.dtor_core@ameritech.net \
    --to=dtor_core@ameritech.net \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=romano@dea.icai.upco.es \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox