From: Jens Axboe <jens.axboe@oracle.com>
To: Jesper Juhl <jesper.juhl@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>
Subject: Re: Simple script that locks up my box with recent kernels
Date: Fri, 24 Nov 2006 10:46:49 +0100 [thread overview]
Message-ID: <20061124094648.GA5400@kernel.dk> (raw)
In-Reply-To: <9a8748490611240141o4d285317h3c1e2110f515e141@mail.gmail.com>
On Fri, Nov 24 2006, Jesper Juhl wrote:
> On 24/11/06, Jens Axboe <jens.axboe@oracle.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
next prev parent reply other threads:[~2006-11-24 9:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-06 23:36 Simple script that locks up my box with recent kernels Jesper Juhl
2006-10-06 23:54 ` Andrew Morton
2006-10-07 0:06 ` Jesper Juhl
2006-10-07 0:21 ` Jesper Juhl
2006-10-07 3:11 ` Linus Torvalds
2006-10-07 21:02 ` Jesper Juhl
2006-10-07 21:25 ` Linus Torvalds
2006-10-08 23:33 ` Jesper Juhl
2006-10-16 22:45 ` Jesper Juhl
2006-10-16 23:04 ` Linus Torvalds
2006-10-16 23:13 ` Jesper Juhl
2006-10-23 20:30 ` Jesper Juhl
2006-11-22 0:46 ` Jesper Juhl
2006-11-22 2:36 ` Linus Torvalds
2006-11-22 3:25 ` Dave Jones
2006-11-22 3:44 ` Linus Torvalds
2006-11-22 3:49 ` Dave Jones
2006-11-22 10:32 ` Pádraig Brady
2006-11-22 17:58 ` Dave Jones
2006-11-22 8:03 ` Jens Axboe
2006-11-22 10:55 ` Jesper Juhl
2006-11-22 10:57 ` Jens Axboe
2006-11-22 11:04 ` Jesper Juhl
2006-11-22 11:07 ` Jens Axboe
2006-11-23 23:52 ` Jesper Juhl
2006-11-24 6:52 ` Jens Axboe
2006-11-24 9:41 ` Jesper Juhl
2006-11-24 9:46 ` Jens Axboe [this message]
2006-11-24 9:52 ` Jesper Juhl
2006-11-23 10:22 ` Jesper Juhl
2006-11-23 23:48 ` Jesper Juhl
2006-11-22 11:00 ` Jesper Juhl
2006-11-24 0:50 ` Jesper Juhl
2006-10-07 3:40 ` Grant Coady
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061124094648.GA5400@kernel.dk \
--to=jens.axboe@oracle.com \
--cc=akpm@osdl.org \
--cc=jesper.juhl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.