public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lost Logic <lostlogic@lostlogicx.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Unresponiveness of 2.4.16
Date: Mon, 26 Nov 2001 18:57:40 -0600	[thread overview]
Message-ID: <3C02E504.4090501@lostlogicx.com> (raw)
In-Reply-To: <1006812135.1420.0.camel@cygnusx-1.okcforum.org> <3C02E1F8.8090407@lostlogicx.com>

Lost Logic wrote:

> I'm running 2.4.16 with 2 IDE UDMA mode 4 drives, and I have 
> experienced no such pausing no matter what I do.  (which usually 
> includes patching, extracting, and generally messing with kernels from 
> Eterm with XMMS playing, and a couple mozillas open)

Ignore that, I know why I have no problems, I can extract kernels, make 
kernels, etc w/o paging...

>
> Nathan G. Grennan wrote:
>
>> 2.4.16 becomes very unresponsive for 30 seconds or so at a time during
>> large unarchiving of tarballs, like tar -zxf mozilla-src.tar.gz. The
>> file is about 36mb. I run top in one window, run free repeatedly in
>> another window and run the tar -zxf in a third window. I had many
>> suspects, but still not sure what it is. I have tried
>>
>> ext2 vs ext3
>> preemptive vs non-preemptive
>> tainted vs non-tainted
>>
>> Nothing seems to help 2.4.16.
>>
>> I tried switching to Redhat's 2.4.9-13 kernel and it acts Alot better.
>> Not only does 2.4.9-13 not get the 30 second delay, but it also seems to
>> take advantage of caching. 2.4.16 takes the same moment of time each
>> time, even tho it should have cached it all into memory the first time.
>> 2.4.9-13 takes a while the first time(without the 30 second new process
>> freezing), but then takes almost no time the times after that. One
>> interesting thing I noticed is that with and without preemptive a
>> already started mp3 playing had no disruption even during the 30 second
>> windows where any new commands would get stuck with 2.4.16. I am not
>> using custom
>>
>> I plan to do more testing to see how say 2.4.9, 2.4.13ac7, etc.
>> Any ideas of how to fix this for 2.4.16?
>>
>> I have attached my .config.
>>
>> My system:
>>
>> Redhat 7.2 with all updates
>>
>> Athlon Thunderbird 1.33ghz
>> 768mb(512mb, 256mb) PC133 SDRAM
>> Abit KT7A-RAID v1.0(KT133A chipset)
>> Bios 64
>> HPT370(bios v1.2.0604)
>>   Primary Master   Quantum Fireball AS40.0
>>   Secondary Master IBM-DTLA-307045
>> VIA686B   Primary Master   CREATIVE DVD-ROM DVD6240E
>>   Secondary Master CR-2801TE
>>
>
>
> -
> 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/
>
>




  reply	other threads:[~2001-11-27  0:58 UTC|newest]

Thread overview: 53+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-26 22:02 Unresponiveness of 2.4.16 Nathan G. Grennan
2001-11-26 22:17 ` Alan Cox
2001-11-26 23:34   ` Nicolas Pitre
2001-11-27  0:05     ` Steve Lion
2001-11-27  9:12     ` Ahmed Masud
2001-11-27 17:12       ` Andrew Morton
2001-11-27 20:31         ` Mike Fedyk
2001-11-27 20:57           ` Andrew Morton
2001-11-27 21:19             ` Martin Eriksson
2001-11-27 21:24             ` Mike Fedyk
2001-11-28 18:24             ` Marcelo Tosatti
2001-11-28 18:57               ` Marcelo Tosatti
2001-11-28 20:31               ` Andrew Morton
2001-11-28 20:56                 ` Andreas Dilger
2001-11-28 21:12                   ` Andrew Morton
2001-11-28 20:04                     ` Marcelo Tosatti
2001-11-28 21:26                       ` Andrew Morton
2001-11-26 23:59   ` Rik van Riel
2001-11-27  0:36     ` Andrew Morton
2001-11-27  0:46       ` Rik van Riel
2001-11-27  4:38       ` Mike Fedyk
2001-11-27  4:45         ` Andrew Morton
2001-11-27  1:45   ` Andrea Arcangeli
2001-11-26 22:21 ` Andrew Morton
2001-11-27  7:42   ` Jens Axboe
2001-11-27  7:58     ` Mike Fedyk
2001-11-27  8:01       ` Jens Axboe
2001-11-27  8:31     ` Andrew Morton
2001-11-27  8:38       ` Jens Axboe
2001-11-26 22:44 ` Lincoln Dale
2001-11-27  4:34   ` GOTO Masanori
2001-11-27  0:44 ` Lost Logic
2001-11-27  0:57   ` Lost Logic [this message]
2001-11-27  3:49 ` Sean Elble
2001-11-27  3:56   ` Doug Ledford
2001-11-27  4:00     ` Sean Elble
  -- strict thread matches above, loose matches on Subject: below --
2001-11-27  9:56 willy tarreau
2001-11-27 10:57 ` Heinz Diehl
2001-11-28  0:33 Torrey Hoffman
2001-11-28  0:48 ` Andrew Morton
2001-11-28 18:09   ` Marcelo Tosatti
2001-11-28 19:38     ` Andrew Morton
2001-11-28  1:31 Dieter Nützel
2001-11-28  2:13 ` Andrew Morton
2001-11-28  2:34   ` Mike Fedyk
2001-11-28  2:48     ` Andrew Morton
2001-11-28 20:21       ` Roger Larsson
2001-11-28  3:53     ` Dieter Nützel
     [not found]     ` <200111280353.fAS3rEB05638@zero.tech9.net>
2001-11-28  4:14       ` Robert Love
2001-11-28 18:56 Torrey Hoffman
2001-11-28 19:31 ` Andrew Morton
2001-11-28 19:42 Torrey Hoffman
2001-11-28 20:51 ` Dieter Nützel

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=3C02E504.4090501@lostlogicx.com \
    --to=lostlogic@lostlogicx.com \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox