mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Jean-Marc Valin <Jean-Marc.Valin@USherbrooke.ca>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Suspend to RAM broken with 2.6.13
Date: Fri, 7 Oct 2005 09:28:35 +0200	[thread overview]
Message-ID: <20051007072835.GG27711@elf.ucw.cz> (raw)
In-Reply-To: <1128663145.14284.85.camel@localhost.localdomain>

On Pá 07-10-05 15:32:25, Jean-Marc Valin wrote:
> Hi,
> 
> I've done some further testing on suspend to RAM and it seems like it
> got broken for me between 2.6.11 and 2.6.12. Does that help narrowing
> down the problem?

Well, you'd have to track it down in a bit more specific way. If you
can narrow it down to specific day, or even better with binary search,
it will help.
								Pavel

> Le vendredi 23 septembre 2005 ? 18:32 +0200, Pavel Machek a écrit :
> > Hi!
> > 
> > > I'm experiencing problems with suspend to RAM on my Dell D600 laptop.
> > > When I run Ubuntu's 2.6.10 kernel I have no problem with suspend to RAM.
> > > However, when I run 2.6.13, my laptop sometimes doesn't wake up. It
> > > seems like the longer my uptime, the more likely the problem is to occur
> > > (which makes it hard to reproduce sometimes). This happens even with a
> > > non-preempt kernel.
> > 
> > Check if it works with minimal drivers and non-preemptible kernel...



-- 
if you have sharp zaurus hardware you don't need... you know my address

  reply	other threads:[~2005-10-07  7:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-22  0:07 Jean-Marc Valin
2005-09-23 16:32 ` Pavel Machek
2005-09-24 11:12   ` Jean-Marc Valin
2005-09-26  6:59   ` Jean-Marc Valin
2005-10-07  5:32   ` Jean-Marc Valin
2005-10-07  7:28     ` Pavel Machek [this message]
2005-10-07  9:50       ` Jean-Marc Valin
2005-10-10  8:54         ` Pavel Machek

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=20051007072835.GG27711@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=Jean-Marc.Valin@USherbrooke.ca \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®