From: Pavel Machek <pavel@ucw.cz>
To: Sanjoy Mahajan <sanjoy@mrao.cam.ac.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.13-rc3: swsusp works (TP 600X)
Date: Sat, 23 Jul 2005 02:35:44 +0200 [thread overview]
Message-ID: <20050723003544.GC1988@elf.ucw.cz> (raw)
In-Reply-To: <E1Dw7ja-0002Ge-EF@approximate.corpus.cam.ac.uk>
Hi!
> swsusp now mostly works on my TP 600X. If I don't eject the pcmcia card
> (usually a prism54 wireless card), swsusp begins the process of
> hibernation, but never gets to the writing pages part. The eth0 somehow
> tries to reload the firmware (as if it's been woken up), and then
> everything hangs. If I eject the card and (for safety) stop
> /etc/init.d/pcmcia, then swsusp writes out the memory to swap, and
> waking up works fine. Thanks for all the improvements!
>
> Is there debugging I can do in order to help get the pcmcia system
> hibernating automagically?
Well, it really may be the firmware loading. Add some printks to
confirm it, then fix it.
> One other glitch is that pdnsd (a nameserver caching daemon) has crashed
> when the system wakes up from swsusp. It also happens when waking up
> from S3, which was working with 2.6.11.4 although not with 2.6.13-rc3.
> Many people have said mysql also does not suspend well. Is their use of
> a named pipe or socket causing the problem?
No idea, strace?
Pavel
--
teflon -- maybe it is a trademark, but it should not be.
next prev parent reply other threads:[~2005-07-23 0:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-23 0:19 2.6.13-rc3: swsusp works (TP 600X) Sanjoy Mahajan
2005-07-23 0:35 ` Pavel Machek [this message]
2005-07-28 20:17 ` Sanjoy Mahajan
2005-07-28 21:36 ` Pavel Machek
2005-07-28 21:55 ` Rafael J. Wysocki
2005-07-29 3:48 ` Sanjoy Mahajan
2005-07-29 4:33 ` Sanjoy Mahajan
2005-07-30 0:50 ` S3 and sigwait (was Re: 2.6.13-rc3: swsusp works (TP 600X)) Sanjoy Mahajan
2005-07-30 10:30 ` [ACPI] " Pavel Machek
2005-08-01 6:51 ` Shaohua Li
2005-08-01 7:09 ` Pavel Machek
2005-08-02 5:16 ` Shaohua Li
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=20050723003544.GC1988@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=sanjoy@mrao.cam.ac.uk \
/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