linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Andrew Morton <akpm@zip.com.au>
Cc: "Nathan G. Grennan" <ngrennan@okcforum.org>,
	linux-kernel@vger.kernel.org
Subject: Re: Unresponiveness of 2.4.16 revisited
Date: Thu, 29 Nov 2001 13:12:12 -0800	[thread overview]
Message-ID: <20011129131212.C496@mikef-linux.matchmail.com> (raw)
In-Reply-To: <1006928344.2613.2.camel@cygnusx-1.okcforum.org> <3C05D608.6D06190D@zip.com.au>
In-Reply-To: <3C05D608.6D06190D@zip.com.au>

On Wed, Nov 28, 2001 at 10:30:32PM -0800, Andrew Morton wrote:
> "Nathan G. Grennan" wrote:
> > 
> > Well I tried your patch Andrew. It seemed to have absolutely no effect
> > on my problem. I used the am-response.patch someone posted the url to
> > eariler in the first thread, which was just a file of your patch. I
> > really suggest you try a mozilla source rpm. Not only does it do the
> > unarchiving, but also patches and rm -rf. I often see a second pause
> > during the patching after the unarchving. I use
> > 
> > rpm --rebuild mozilla-2001112602_trunk-0_rh7.src.rpm
> > 
> > I also tried Redhat's latest rawhide kernel, 2.4.16-0.1 and it had to
> > had time same problem. So it isn't fixed by one of their patchs. It is
> > most likely just a difference between Linus's 2.4.9 and 2.4.16.
> 
> Nathan,
> 
> I can reproduce the 30 second stall on ext3.  It is due to

Just recently I had to run badblocks -ws on a scsi hard drive.  It was on
its own scsi controller.  During the write portions, I was able to see
pauses of 1-5 seconds.  Mouse didn't move, nothing.  During the read
(compare) portion, there were no such pauses.

This was on vanilla 2.4.16. 2x366 celeron, and 256MB ram.  Only reading with
mutt, and irc.  gkrellm showed the pauses.

00:00.0 Host bridge: Intel Corp. 440LX/EX - 82443LX/EX Host bridge (rev 03)
00:01.0 PCI bridge: Intel Corp. 440LX/EX - 82443LX/EX AGP bridge (rev 03)
00:07.0 ISA bridge: Intel Corp. 82371AB PIIX4 ISA (rev 01)
00:07.1 IDE interface: Intel Corp. 82371AB PIIX4 IDE (rev 01)
00:07.2 USB Controller: Intel Corp. 82371AB PIIX4 USB (rev 01)
00:07.3 Bridge: Intel Corp. 82371AB PIIX4 ACPI (rev 01)
00:08.0 SCSI storage controller: Adaptec AIC-7881U (rev 01)
00:0a.0 Ethernet controller: Digital Equipment Corporation DECchip 21041 [Tulip Pass 3] (rev 21)
00:0b.0 Ethernet controller: Intel Corp. 82557 [Ethernet Pro 100] (rev 08)
01:00.0 VGA compatible controller: Matrox Graphics, Inc. MGA G100 [Productiva] AGP (rev 01)

mf

  reply	other threads:[~2001-11-29 21:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28  6:19 Unresponiveness of 2.4.16 revisited Nathan G. Grennan
2001-11-29  6:30 ` Andrew Morton
2001-11-29 21:12   ` Mike Fedyk [this message]
     [not found] ` <1007021221.1739.0.camel@cygnusx-1.okcforum.org>
2001-11-29  9:07   ` Nathan G. Grennan
2001-11-29  9:32     ` Oktay Akbal
2001-11-29 16:48       ` Nathan G. Grennan
2001-11-29 18:09         ` Oktay Akbal
2001-11-29 18:16           ` Nathan G. Grennan
2001-11-29 18:36             ` Andreas Dilger
2001-12-01 12:11             ` Bill Davidsen

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=20011129131212.C496@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=akpm@zip.com.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ngrennan@okcforum.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;
as well as URLs for NNTP newsgroup(s).