From: Tino Keitel <tino.keitel@tikei.de>
To: linux-kernel@vger.kernel.org
Subject: Re: 2.6.20-rc3 regression: suspend to RAM broken on Mac mini Core Duo
Date: Mon, 8 Jan 2007 23:02:38 +0100 [thread overview]
Message-ID: <20070108220238.GA16799@dose.home.local> (raw)
In-Reply-To: <20070108161718.GB2208@elf.ucw.cz>
On Mon, Jan 08, 2007 at 17:17:19 +0100, Pavel Machek wrote:
> On Sun 2007-01-07 23:27:06, Tino Keitel wrote:
> > On Sun, Jan 07, 2007 at 21:04:53 +0100, Tino Keitel wrote:
> > > On Sun, Jan 07, 2007 at 13:23:13 -0500, Lee Revell wrote:
> > > > On Sun, 2007-01-07 at 16:17 +0100, Tino Keitel wrote:
> > > > > No information about the device/driver that refuses to resume.
> > > >
> > > > You should be able to identify the problematic driver by removing each
> > > > driver manually before suspending.
> > >
> > > I can not reproduce it anymore, resume now works. I really hope that it
> > > will stay so.
> >
> > It didn't. It looks like it is unusable, becuase it isn't reliable in
> > 2.6.20-rc3.
>
> What was last working version? Can you pinpoint driver breaking it?
I just used 2.6.18.2 with a manual driven suspend/resume loop and fully
loaded userspace for ca. 40 minutes, without a failure.
I tried to pinpoint the driver with pm_trace, without success (see my
original posting).
Regards,
Tino
next prev parent reply other threads:[~2007-01-08 22:02 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-07 15:17 2.6.20-rc3 regression: suspend to RAM broken on Mac mini Core Duo Tino Keitel
2007-01-07 18:23 ` Lee Revell
2007-01-07 20:04 ` Tino Keitel
2007-01-07 22:27 ` Tino Keitel
2007-01-07 23:44 ` Adrian Bunk
2007-01-08 21:04 ` Tino Keitel
2007-01-09 14:51 ` Luming Yu
2007-01-09 23:16 ` Tino Keitel
2007-01-12 14:50 ` Pavel Machek
2007-01-13 3:05 ` Tino Keitel
2007-01-13 3:45 ` Tino Keitel
2000-01-17 4:43 ` Tino Keitel
2007-01-13 10:18 ` Pavel Machek
2007-01-08 16:17 ` Pavel Machek
2007-01-08 22:02 ` Tino Keitel [this message]
2007-01-08 23:29 ` Rafael J. Wysocki
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=20070108220238.GA16799@dose.home.local \
--to=tino.keitel@tikei.de \
--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