| 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, 11 Oct 2007 19:56:44 -0500 From: Berkley Shands <berkley@....wustl.edu> To: Nick Piggin <nickpiggin@...oo.com.au> CC: linux-kernel@...r.kernel.org Subject: Re: 2.6.23 spinlock hang in kswapd under heavy disk write loads 100% reproducible on the two motherboards in question. Does not happen on any other motherboard I have in my possession (not tyan, not uniwide, not socket 940...) No errors, no dmesg, nothing with debug_spinlock set. <sysrq> shows lots (when it works), but by then too many things are locked up to be of much use. I can get into KDB and look around (2.6.22 for kdb - it hangs there too). Even access to the local disk is blocked. Processes in core and running remain there (iostat, top, ...). I personally think the bios are suspect on the PCIe, as symptoms change with the bios rev. I did a major paper on SAS performance with one H8DMi, but it got a bios rev, and now crashes. Missed interrupt? APIC sending an interrupt to multiple cpus? I don't know. Tell me what to look at, and I can get you the info. It usually takes 20 seconds to go bang, using either the LSI8888ELP or the rocket raid 2340. Other controllers are too slow. 2.6.20 does not lock up. It is also 200MB/Sec slower in writing :-) thanks for the response. berkley - 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