| 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
| ||
|
Date: Sun, 17 Nov 2013 19:02:21 +0100 From: Francis Moreau <francis.moro@...il.com> To: Borislav Petkov <bp@...en8.de> Cc: LKML <linux-kernel@...r.kernel.org> Subject: Re: 3.12: kernel panic when resuming from suspend to RAM (x86_64) On Sun, Nov 17, 2013 at 5:01 PM, Borislav Petkov <bp@...en8.de> wrote: > On Sun, Nov 17, 2013 at 04:50:23PM +0100, Francis Moreau wrote: >> AFAIK, the kernel has 2 simple patches on top of the vanilla one. >> They're both are trivial and can't be related to this issue. >> >> You can have look to them here: >> https://wiki.archlinux.org/index.php/Kernels#Official_packages > > Ok. > >> Assuming that I'm running an upstream kernel, it's almost 100% >> reproductible. > > Is there any chance you can catch the whole oops, esp. keep the Code: > line complete? Sorry I haven't taken the original picture large enough, and getting this kernel panic is pretty hard since the kernel usually displays the black screen. > > Also, can you do: > > $ objdump -d vmlinux | less > > then search for 'call_timer_fn' and paste the whole function somewhere. I can't find any traces of this function in the dump... > > Also, can you catch a full dmesg and upload that somewhere too? http://paste.debian.net/66294/ Thanks. -- Francis -- 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