From: Nick Piggin <piggin@cyberone.com.au>
To: "Sergey S. Kostyliov" <rathamahata@php4.ru>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 898] New: Very HIGH File & VM system latencies and system stop responding while extracting big tar archive file.
Date: Fri, 11 Jul 2003 19:57:54 +1000 [thread overview]
Message-ID: <3F0E8A22.6020700@cyberone.com.au> (raw)
In-Reply-To: <200307111346.39731.rathamahata@php4.ru>
Sergey S. Kostyliov wrote:
>Hello all,
>
>On Friday 11 July 2003 10:14, Martin J. Bligh wrote:
>
>>http://bugme.osdl.org/show_bug.cgi?id=898
>>
>> Summary: Very HIGH File & VM system latencies and system stop
>> responding while extracting big tar archive file.
>> Kernel Version: 2.5.75
>> Status: NEW
>> Severity: high
>> Owner: bugme-janitors@lists.osdl.org
>> Submitter: bakhtiar@softhome.net
>>
>>
>>Distribution:Slackware v7.1 : glibc v2.1.3
>>Hardware Environment: P!!! 550 MHz, 256 MB RAM. HP Brio BA600
>>
>
>The same issues here with 2.5.7{4,5}. IO-intencive task got stuck in 'D'
>state (bk,rsync,tar - it really doesn't matter). I think a have to get decoded
>Alt-SysRq-T for this tasks next time.
>
You're sure 2.5.74 got processes stuck in D? That means its possibly
a driver bug. If you can get 2.5.75 to hang, please also try with
elevator=deadline. Thank you.
Nick
next prev parent reply other threads:[~2003-07-11 9:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-11 6:14 [Bug 898] New: Very HIGH File & VM system latencies and system stop responding while extracting big tar archive file Martin J. Bligh
2003-07-11 9:46 ` Sergey S. Kostyliov
2003-07-11 9:57 ` Nick Piggin [this message]
2003-07-11 10:45 ` Andrew Morton
2003-07-11 18:39 ` Mike Fedyk
2003-07-11 19:00 ` Andrew Morton
2003-07-11 20:24 ` Shawn
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=3F0E8A22.6020700@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=rathamahata@php4.ru \
/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;
as well as URLs for NNTP newsgroup(s).