linux-kernel - Re: Simple script that locks up my box with recent kernels

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20061124094648.GA5400@kernel.dk>
Date:	Fri, 24 Nov 2006 10:46:49 +0100
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Jesper Juhl <jesper.juhl@...il.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 Fri, Nov 24 2006, Jesper Juhl wrote:
> 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.

Since it triggers fairly quickly, any chance that you could try and
narrow it down to a specific version that breaks?

-- 
Jens Axboe

-
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/