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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20131118024315.GA26395@chicago.guarana.org>
Date:	Mon, 18 Nov 2013 13:43:15 +1100
From:	Kevin Easton <kevin@...rana.org>
To:	Borislav Petkov <bp@...en8.de>
Cc:	Francis Moreau <francis.moro@...il.com>,
	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 Mon, Nov 18, 2013 at 02:04:28AM +0100, Borislav Petkov wrote:
> On Mon, Nov 18, 2013 at 11:33:25AM +1100, Kevin Easton wrote:
> > That's part of an ASCII string, "DEP=2\0SE", so if that looks familiar
> > to anyone (part of a kernel command line?) it might give a clue to
> > where the timer callback pointer is being overwritten.
> 
> Yeah, it could be anything, maybe even part of dmesg although nothing
> matches "DEP" in there.

We actually have the following long as well, from the .data member.
Pasting them together gives "DEP=2\0SEQNUM=223" which looks like udev.

    - Kevin 
--
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/