| 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
| ||
|
Message-ID: <q2p19f34abd1004240509r63449b41l379bc14f5c6eaeae@mail.gmail.com> Date: Sat, 24 Apr 2010 14:09:20 +0200 From: Vegard Nossum <vegard.nossum@...il.com> To: Pedro Francisco <pedrogfrancisco@...il.com> Cc: me@...copeland.com, "John W. Linville" <linville@...driver.com>, linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org, mickflemm@...il.com Subject: Re: ath5k misbehaving affecting other kernel parts unrelated? On 24 April 2010 10:56, Pedro Francisco <pedrogfrancisco@...il.com> wrote: > For some reason I am unable to get a kernel I compiled to boot. Since I was > unable to compile the kernel with those debugging options, I just turned on > slub_debug on GRUB. > > I got a few messages which I pasting here only partially to check for their > significance. If significant I'll post them fully: Please post all the info you have. Full crash log and full slub-debug report are both very interesting. Not sure what exactly linux-backports-modules-wireless-lucid-generic is, but one way to narrow it down is to NOT use that and see if it still crashes. You might find your distro config in /boot/config-*; you could copy that to .config in your kernel directory and try to compile (and boot) a more recent kernel with that. Good luck, Vegard -- 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