From: Pavel Machek <pavel@ucw.cz>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: RFC: Self-snapshotting in Linux
Date: Thu, 17 Apr 2008 11:32:35 +0200 [thread overview]
Message-ID: <20080417093235.GB7314@elf.ucw.cz> (raw)
In-Reply-To: <48060436.6030707@tuffmail.co.uk>
On Wed 2008-04-16 14:50:46, Alan Jenkins wrote:
> Pavel Machek wrote:
>>> I guess there is the hardware / drivers issue. I would like to claim
>>> I've found hibernation to be reliable but unfortunately that's not
>>> 100% true.
>>>
>> So debug it, it is open source after all. Or at least file a bugs.
>>
> I definitely want to debug it; I love hibernating. It's a regression and
> it'll affect my distro kernel once I upgrade to Ubuntu Hardy.
>
> <http://bugzilla.kernel.org/show_bug.cgi?id=10196> "Backtraces during
> hibernate / resume".
>
> I posted the backtraces but nobody could tell me what they were - they
> don't actually say whether they're OOPs or BUGs etc. They might be
> softlockups - some times I got softlockup warnings, though thats not in the
> log I posted.
Not sure what that is, I never seen that before.
Can you try vanilla 2.6.25-rc9 or something?
> I'm confused about some details (exactly which versions / configs produced
> which symptoms). I don't have the machine right now, but I'll get back to
> it some time soon. I think I managed to get a pair of broken and
> non-broken kernels to work on, and it seems to be a regression going from
> 2.6.22 to 2.6.23.
If you can do a git bisect between those two, we could probably fix it
very quickly.
> Any help in clearing up my confusion would be appreciated. Is it worth
> trying to narrow down exactly where the hang happens between writing the
> hibernation image and shutting down? If so how? I suspect that's going to
> be easier than bisecting it.
Adding printks?
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2008-04-17 9:58 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ajbvb-3Ur-21@gated-at.bofh.it>
[not found] ` <ajcri-65w-13@gated-at.bofh.it>
2008-04-16 10:27 ` Alan Jenkins
2008-04-16 11:12 ` Pavel Machek
2008-04-16 13:50 ` Alan Jenkins
2008-04-17 9:32 ` Pavel Machek [this message]
2008-04-19 16:42 ` Alan Jenkins
2008-04-17 0:55 ` Nigel Cunningham
2008-04-17 7:48 ` Alan Jenkins
[not found] ` <ajd42-7Gt-49@gated-at.bofh.it>
2008-04-16 11:02 ` Alan Jenkins
2008-04-16 15:06 ` Peter Teoh
2008-04-16 16:21 ` Disconnect
2008-04-16 19:50 ` Vivek Goyal
[not found] ` <48065C64.7010808@gmail.com>
2008-04-16 20:10 ` Scott Lovenberg
2008-04-16 20:25 ` Vivek Goyal
2008-04-17 2:09 ` Scott Lovenberg
2008-04-17 6:23 ` Peter Teoh
2008-04-17 8:43 ` Alan Jenkins
2008-04-17 16:01 ` Scott Lovenberg
2008-04-16 8:44 Peter Teoh
2008-04-16 8:49 ` eric miao
2008-04-16 9:49 ` Ben Nizette
2008-04-16 10:33 ` Scott Lovenberg
2008-04-16 11:14 ` Pavel Machek
[not found] ` <804dabb00804160821n4872c65fh44f2c07ead67fc49@mail.gmail.com>
2008-04-17 9:33 ` Pavel Machek
2008-04-16 18:31 ` Greg Freemyer
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=20080417093235.GB7314@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=alan-jenkins@tuffmail.co.uk \
--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
all inboxes | Powered by JetHome®