From: mru@kth.se (Måns Rullgård)
To: Pavel Machek <pavel@ucw.cz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Dropping CONFIG_PM_DISK?
Date: Mon, 01 Mar 2004 11:08:01 +0100 [thread overview]
Message-ID: <yw1xhdx8ani6.fsf@kth.se> (raw)
In-Reply-To: <20040301094023.GF352@elf.ucw.cz> (Pavel Machek's message of "Mon, 1 Mar 2004 10:40:23 +0100")
Pavel Machek <pavel@ucw.cz> writes:
>> > Try current swsusp with minimal drivers, init=/bin/bash.
>>
>> Well, if I do that it works. Or at least some old version did, I
>> assume the later ones would too. However, that sort of removes the
>> whole point. Taking down the system enough to be able to unload
>> almost everything is as close as rebooting you'll get.
>
> Well, now do a search for "which module/application causes failure".
I know, it just takes an awful time.
>> BTW, is there some easier way to track the development than using the
>> patches from the web page? Unpatching after a couple of BK merges
>> isn't the easiest thing. Is there a BK tree somewhere I can pull
>> from?
>
> Are you using swsusp2?
Well, trying to. Isn't it supposed to be the latest and greatest?
> That's _not_ what I'm talking about. swsusp is in mainline.
It would still be the same module(s) that caused it to fail, right?
--
Måns Rullgård
mru@kth.se
next prev parent reply other threads:[~2004-03-01 10:08 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1ulUA-33w-3@gated-at.bofh.it>
2004-02-29 16:17 ` Dropping CONFIG_PM_DISK? Karol Kozimor
2004-02-29 16:23 ` Pavel Machek
2004-02-29 17:32 ` Måns Rullgård
2004-02-29 18:10 ` Michael Frank
2004-02-29 21:33 ` [Swsusp-devel] " Micha Feigin
2004-03-01 2:51 ` Michael Frank
2004-03-01 11:09 ` Benjamin Herrenschmidt
2004-03-01 11:35 ` Karol Kozimor
2004-03-01 11:28 ` Benjamin Herrenschmidt
2004-03-01 11:51 ` Karol Kozimor
2004-03-01 12:56 ` Martin Wickman
2004-03-01 13:22 ` Michael Frank
2004-03-01 12:34 ` Micha Feigin
2004-03-01 11:31 ` Benjamin Herrenschmidt
2004-03-01 11:57 ` Karol Kozimor
2004-03-01 22:08 ` Benjamin Herrenschmidt
2004-03-01 11:43 ` Michael Frank
2004-03-01 11:39 ` Benjamin Herrenschmidt
2004-03-01 12:48 ` Michael Frank
2004-03-01 13:47 ` Arjan van de Ven
2004-03-01 14:33 ` Michael Frank
2004-03-01 14:38 ` Arjan van de Ven
2004-03-01 22:10 ` Benjamin Herrenschmidt
2004-02-29 18:10 ` Pavel Machek
2004-02-29 18:29 ` Måns Rullgård
2004-03-01 9:40 ` Pavel Machek
2004-03-01 10:08 ` Måns Rullgård [this message]
2004-03-01 10:39 ` Pavel Machek
2004-03-01 9:58 ` Nigel Cunningham
2004-03-01 12:46 ` Pavel Machek
2004-03-01 18:16 ` Nigel Cunningham
2004-03-01 20:22 ` Pavel Machek
2004-03-01 10:45 ` Michael Frank
2004-02-28 23:00 Pavel Machek
2004-02-28 23:52 ` Benjamin Herrenschmidt
2004-02-29 7:30 ` Pavel Machek
2004-02-29 7:22 ` Benjamin Herrenschmidt
2004-02-29 12:40 ` Pavel Machek
2004-03-01 9:46 ` Nigel Cunningham
2004-03-01 12:40 ` Romano Giannetti
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=yw1xhdx8ani6.fsf@kth.se \
--to=mru@kth.se \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.