linux-kernel - Re: 3.12: kernel panic when resuming from suspend to RAM (x86

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:	Tue, 19 Nov 2013 11:15:21 +0100
From:	Borislav Petkov <bp@...en8.de>
To:	Francis Moreau <francis.moro@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>,
	Thomas Gleixner <tglx@...utronix.de>
Subject: Re: 3.12: kernel panic when resuming from suspend to RAM (x86_64)

On Tue, Nov 19, 2013 at 11:01:14AM +0100, Francis Moreau wrote:
> I think the easiest way to do it is to install a minimal system on a
> USB stick and try to reproduce first in order to preserve my system.

Yep, sounds simple enough.

> Then I'll try to see if this issue exists in a previous kernel version
> and if so, I'll do a git-bisect session.
>
> I can't find a quicker way to do that although using git-bisect (which
> implies several kernel builds) is a PITA.

You can start with a coarse bisect by testing the major kernel versions
first, i.e. 3.11, 3.10, 3.9 ... and once you find good and bad, then you
can do the git-bisect thing.

Also, you can check for BIOS updates for your machine and if there are,
check their changelogs whether they fix something suspend-related.

Good luck!

-- 
Regards/Gruss,
    Boris.

Sent from a fat crate under my desk. Formatting is fine.
--
--
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/