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: Thu, 19 Jun 2008 19:00:48 -0700 (PDT) From: David Miller <davem@...emloft.net> To: a.beregalov@...il.com Cc: kernel-testers@...r.kernel.org, sparclinux@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: 2.6.26-rc: SPARC: Sun Ultra 10 can not boot From: "Alexander Beregalov" <a.beregalov@...il.com> Date: Thu, 19 Jun 2008 20:02:44 +0400 > I have reverted this commit and > 2.6.26-rc6-00233-g99d3b2d works fine. It can boot. I know what the problem is. It's hanging because lockdep is starting to actually be used. :-) Beforehand various bugs caused lockdep to disable itself almost immediately. So it was never actually enabled on sparc64. When you revert that changeset, there is a loop in the backtrace of all kernel threads, and therefore lockdep turns itself off when all of the stack backtrace slots get consumed by that loop in the backtraces. After the revert you should see a set of kernel messages like: BUG: MAX_STACK_TRACE_ENTRIES too low! turning off the locking correctness validator. and that would confirm my theory. Lockdep really isn't usable on sparc64 at this time and it's one of the ongoing things I'm trying to get fully fixed. The changeset in question fixes a real bug in stack backtrace output, so it should stay in the tree. FWIW, I just verified the above on my ultra5 box. -- 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