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: Fri, 24 Nov 2006 10:41:08 +0100 From: "Jesper Juhl" <jesper.juhl@...il.com> To: "Jens Axboe" <jens.axboe@...cle.com> Cc: "Linus Torvalds" <torvalds@...l.org>, "Linux Kernel Mailing List" <linux-kernel@...r.kernel.org>, "Andrew Morton" <akpm@...l.org> Subject: Re: Simple script that locks up my box with recent kernels On 24/11/06, Jens Axboe <jens.axboe@...cle.com> wrote: > On Fri, Nov 24 2006, Jesper Juhl wrote: > > > Does the box survive io intensive workloads? > > > > It seems to. It does get sluggish as hell when there is lots of disk I/O but > > it seems to be able to survive. > > I'll try some more, with some IO benchmarks + various other stuff to see > > if I can get it to die that way. > > Just wondering if you have a marginal powersupply, perhaps. > It is a possibility, but I doubt it, since if I use a 2.6.17.x kernel then things are rock solid and I can't cause a lockup even if I leave my box building kernels in the background for days. > > > Have you tried using net or > > > serial console to see if it spits out any info before it crashes? > > > > Lacking a second box at the moment, so that's not an option currently :( > > It's likely a requirement to get any further with this issue, I'm > afraid. Nobody can debug this thing blind folded. > I'll see if I can get my hands on a second box. -- Jesper Juhl <jesper.juhl@...il.com> Don't top-post http://www.catb.org/~esr/jargon/html/T/top-post.html Plain text mails only, please http://www.expita.com/nomime.html - 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