| 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: <874pizwqi6.fsf@oxford.xeocode.com> Date: Thu, 16 Aug 2007 14:36:17 +0100 From: Gregory Stark <stark@...erprisedb.com> To: "Peter Zijlstra" <peterz@...radead.org> Cc: <linux-kernel@...r.kernel.org> Subject: Re: soft lockup detected "Peter Zijlstra" <peterz@...radead.org> writes: > On Thu, 2007-08-16 at 09:54 +0100, Gregory Stark wrote: > >> This is on 2.6.21-1.3194.fc7. I've been trying different kernels but this is >> the first point where I've narrowed down the symptoms to something >> reproducible. > > That is a very old kernel, and a vendor kernel at that. I'm sorry? The original kernel to exhibit the problem was 2.6.5 -- *that* was a very old kernel and I insisted we upgrade before trying to report any problems. However 2.6.21 is only one version out of date and it's about 3 months old. None of the changelog entries since then have mentioned any semop or ipc related changes (aside from a hugetlb change but we're not using hugetlb). It's more recent than most distributions have as their current release. I do share your feelings about vendor kernels. We've seen these problems with SUSE 2.6.5 and 2.6.16 kernels though. This was the most recently released kernel we've tried. > Did any of the different kernels you tried include a recent upstream > one? Still working on it. -- Gregory Stark EnterpriseDB http://www.enterprisedb.com - 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