| 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: Wed, 4 Oct 2006 22:27:18 -0700 From: "Steve Hindle" <mech422@...il.com> To: "David Chinner" <dgc@....com> Cc: linux-kernel@...r.kernel.org, jgarzik@...ox.com, linux-ide@...r.kernel.org Subject: Re: PROBLEM: Hardlock with 2.6.1[678] on Abit AI7, ICH5 + XFS, SATA under heavy I/O load On 10/4/06, David Chinner <dgc@....com> wrote: > On Wed, Oct 04, 2006 at 06:28:35PM -0700, Steve Hindle wrote: > > Hello, > > > > My machine is hardlocking with recent kernels (including 2.6.18-mm3) > > under heavy I/O load (for instance, just compiling the kernel is > > enough to lock the machine). No bug,oops,or panic and nothing in the > > system logs. > > Does it happen on any other filesystems? Is this your root filesystem > that is hanging? > no, its not my root - but my other partitions are also XFS and are on the same drive... so not really any way to check ATM. > Journalling filesystems shouldn't get corrupted by hangs or > crashes... I understood this in theory - but was rather pleased theory == practice. However, I didn't even notice a 'not unmounted cleanly' message during subsequent boots? I might just have missed it though - Debian's boot has gotten much 'chattier' over the years... Steve - 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