From: Rob Landley <rob@landley.net>
To: Patrick Mochel <mochel@osdl.org>
Cc: Pavel Machek <pavel@ucw.cz>, <linux-kernel@vger.kernel.org>
Subject: Re: Patrick's Test9 suspend code.
Date: Mon, 17 Nov 2003 15:11:32 -0600 [thread overview]
Message-ID: <200311171511.32908.rob@landley.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0311170844230.12994-100000@cherise>
You live!
Cool. :)
On Monday 17 November 2003 10:45, Patrick Mochel wrote:
> > Currently, patrick's code isn't working for me anymore either. I think
> > it's because I haven't figured out how I had ACPI set up last time
> > (performance covernor, probably. If I tell it to use the userspace
> > governor, there's still nothing in /sys/devices/system/cpu/cpu0, the
> > directory is empty. Maybe the documentation isn't up to date anymore, I
> > don't know...) When I tried to suspend with it, it sort of worked but
> > the writing to disk phase (which never caused a problem before) had a
> > visible pause between each sector written, and writing out the 3000
> > sectors took over 5 minutes, and the end result wasn't something it could
> > resume from anyway. Sigh...
>
> Are you using preempt? There was a similar problem reported a while back
> that was solved by disabling it. Though it's not a true fix, it should at
> least get you going again.
That might explain some stuff. I'm now getting messages from my orinoco card
during the writing phase about negotiating to talk with the access point,
which is interfering with the writing of the dots. That didn't happen
before.
Might it also be possible to just invent a new spinlock, grab it at the start
of suspend, and release it at the end of resume? (It's not like suspend
really needs to be preempted. I vaguely remember a "disable_preempt" call,
but haven't a clue what it or its semantics might actually be.)
I have an appointment in half an hour but I'll give it a shot this evening.
Thanks.
> Thanks,
>
>
> Pat
Rob
next prev parent reply other threads:[~2003-11-17 21:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-09 10:04 Patrick's Test9 suspend code Rob Landley
2003-11-13 13:08 ` Pavel Machek
2003-11-16 0:30 ` Rob Landley
2003-11-16 13:13 ` Pavel Machek
2003-11-17 2:38 ` Rob Landley
2003-11-17 8:42 ` Pavel Machek
2003-11-17 16:45 ` Patrick Mochel
2003-11-17 21:11 ` Rob Landley [this message]
2003-11-18 12:02 ` Rob Landley
2003-11-18 18:22 ` Pavel Machek
2003-11-18 22:12 ` Rob Landley
2003-11-18 23:21 ` Pavel Machek
2003-11-19 5:26 ` Rob Landley
2003-11-19 9:18 ` Pavel Machek
2003-11-19 9:41 ` Rob Landley
-- strict thread matches above, loose matches on Subject: below --
2003-11-19 13:15 Samium Gromoff
2003-11-19 19:06 ` Pavel Machek
2003-11-20 17:26 Shaheed
2003-11-20 19:39 ` Rob Landley
2003-11-20 22:33 ` Shaheed
2003-11-20 22:41 ` Nigel Cunningham
2003-11-20 23:02 ` Shaheed
2003-11-21 6:46 ` Rob Landley
2003-11-21 20:09 ` Nigel Cunningham
2003-11-21 0:06 ` 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=200311171511.32908.rob@landley.net \
--to=rob@landley.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=pavel@ucw.cz \
/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