public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Riley <oscar@the-rileys.net>
To: linux-kernel@vger.kernel.org
Subject: *massive* slowdowns on 2.4.1-pre1[1|2]
Date: Mon, 29 Jan 2001 20:59:08 -0500	[thread overview]
Message-ID: <3A761FEC.1C564FAE@the-rileys.net> (raw)

Sorry if this is a redundant post, but I didn't see any related posts
(at least from the subject lines)...

Kernel 2.4.1-pre11 and pre12 are both massively slower than 2.4.0 on the
same machine, compiled with the same options.  The machine is a Athlon
900 on a KT133 chipset.  The slowdown is noticealbe in all areas...
booting takes over five minutes, keyboard input is noticeably delayed,
and the PC speaker makes much longer beeps when beeping the console.  I
just wanted to post this since 2.4.1 is soon for release (at least
according to Linus' post on -pre11) and we wouldn't want to release this
if it affects more than just me.  I've tried a number of different
options to make this work, but none have seemed to work.  BTW, my
problems are nothing similar to the current discussion of KT133
misbehaviour, especially since this machine works perfectly on 2.4.0.
-
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/

             reply	other threads:[~2001-01-30  1:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-30  1:59 David Riley [this message]
2001-01-30  2:05 ` *massive* slowdowns on 2.4.1-pre1[1|2] 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
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=3A761FEC.1C564FAE@the-rileys.net \
    --to=oscar@the-rileys.net \
    --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