mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Luming Yu" <luming.yu@gmail.com>
To: "Adrian Bunk" <bunk@stusta.de>,
	"Lee Revell" <rlrevell@joe-job.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.6.20-rc3 regression: suspend to RAM broken on Mac mini Core Duo
Date: Tue, 9 Jan 2007 22:51:04 +0800	[thread overview]
Message-ID: <3877989d0701090651m84d7f41v5d06e1638a7eb31d@mail.gmail.com> (raw)
In-Reply-To: <20070108210428.GA7199@dose.home.local>

> > > It didn't. It looks like it is unusable, becuase it isn't reliable in
> > > 2.6.20-rc3.
> >
> > Is this issue still present in -rc4?
>
> I used 2.6.20-rc4 in single user mode, and applied 2 patches from
> netdev to get wake on LAN support. This way I was able to set up an
> automatic suspend/resume loop. It looked good, but after e.g. 20
> minutes, the resume hang. So it is reproduceable with 2.6.20-rc4.
> Unfortunately, I can not test the same with 2.6.18, as the wake on LAN
> patches need 2.6.20-rc.

Hmm, do you mean this is the first time of this kind of testing?
Is this issue related to LAN driver?
I guess you should be able to set up an automatic suspend/resume loop
with /proc/acpi/alarm, and test similar with 2.6.18.

--Luming

  reply	other threads:[~2007-01-09 14:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-07 15:17 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 [this message]
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
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=3877989d0701090651m84d7f41v5d06e1638a7eb31d@mail.gmail.com \
    --to=luming.yu@gmail.com \
    --cc=bunk@stusta.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rlrevell@joe-job.com \
    /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®