lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Wed, 16 Apr 2008 14:50:46 +0100
From:	Alan Jenkins <alan-jenkins@...fmail.co.uk>
To:	Pavel Machek <pavel@....cz>
CC:	linux-kernel@...r.kernel.org
Subject: Re: RFC: Self-snapshotting in Linux

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.

The backtraces have been harder to reproduce across different versions / 
configs, but there's definitely an issue where it hangs every time after 
it successfully suspends. It then tends to lock up about a minute after 
resuming.

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.

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.

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ