![]() | |||||||||||||
Messages in this thread |
On 24/11/06, Jens Axboe <jens.axboe@oracle.com> wrote: > 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? > I already tried doing a git bisect, but I somehow messed it up (probably by concluding that a bad kernel was good). The problem is that *usually* triggers fairly quickly (within 1hr), but sometimes it takes much longer to trigger, so it's hard to be 100% sure that a kernel is actually good - except if I leave it running for something like 24hrs for each step in the bisect. That is actually something I plan to do, but finding the time for that is not easy. -- Jesper Juhl <jesper.juhl@gmail.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@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-11-24 09:55 [from the cache] ©2003-2008 | |||||||||||||