| 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: <47B5FE1E.5080804@gmail.com> Date: Fri, 15 Feb 2008 22:03:26 +0100 From: Jarek Poplawski <jarkao2@...il.com> To: unlisted-recipients:; (no To-header on input) CC: Denys Fedoryshchenko <denys@...p.net.lb>, Bart Van Assche <bart.vanassche@...il.com>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: BUG/ spinlock lockup, 2.6.24 Jarek Poplawski wrote, On 02/15/2008 09:21 PM: > Denys Fedoryshchenko wrote, On 02/15/2008 08:42 PM: > ... > >> I have similar crashes on completely different hardware with same job (QOS), >> so i think it is actually some nasty bug in networking. > > Maybe you could try with some other debugging options? E.g. since lockdep > doesn't help - turn this off. Instead try some others, like these: ...On the other hand this: > Feb 15 15:50:17 217.151.X.X [1521315.068984] BUG: spinlock lockup on CPU#1, > ksoftirqd/1/7, f0551180 seems to point just at spinlock lockup, so it's more about the full report. I wonder if this patch to prink could help here: author Ingo Molnar <mingo at elte.hu> Fri, 25 Jan 2008 20:07:58 +0000 (21:07 +0100) printk: make printk more robust by not allowing recursion http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=32a76006683f7b28ae3cc491da37716e002f198e Jarek P. -- 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