From: David Riley <oscar@the-rileys.net>
To: Chris Wedgwood <cw@f00f.org>
Cc: Linus Torvalds <torvalds@transmeta.com>, linux-kernel@vger.kernel.org
Subject: Re: *massive* slowdowns on 2.4.1-pre1[1|2]
Date: Tue, 30 Jan 2001 17:21:36 -0500 [thread overview]
Message-ID: <3A773E70.804BEAB@the-rileys.net> (raw)
In-Reply-To: <3A761FEC.1C564FAE@the-rileys.net> <Pine.LNX.4.10.10101292102030.28124-100000@coffee.psychology.mcmaster.ca> <955pr6$afk$1@penguin.transmeta.com> <20010131001452.A6620@metastasis.f00f.org>
Chris Wedgwood wrote:
>
> On Mon, Jan 29, 2001 at 11:17:58PM -0800, Linus Torvalds wrote:
>
> You have to realize that stability takes precedence over
> EVERYTHING.
>
> Are you sure his desciption describes only disk-slow down? Seems to
> me something else is going on... why would speaker beeps take longer?
> Maybe some kind of PM weirdo?
My problem had nothing to do with disk access. Keyboard input isn't
slowed by disk access. I knew that... In any case, sub-486 speeds
aren't attained through using PIO instead of UDMA... my 486 uses PIO
disks anyway, so it's moot. The real culprit was ACPI, which is having
some temporary problems. I turned it off and everything's great
(thanks, Andrew).
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-30 22:20 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-30 1:59 *massive* slowdowns on 2.4.1-pre1[1|2] David Riley
2001-01-30 2:05 ` Mark Hahn
2001-01-30 7:17 ` Linus Torvalds
2001-01-30 8:27 ` Michael B. Trausch
2001-01-30 11:14 ` Chris Wedgwood
2001-01-30 22:21 ` David Riley [this message]
2001-01-30 13:18 ` Tobias Ringstrom
-- strict thread matches above, loose matches on Subject: below --
2001-01-30 2:06 Grover, Andrew
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=3A773E70.804BEAB@the-rileys.net \
--to=oscar@the-rileys.net \
--cc=cw@f00f.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.com \
/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.