From: ghugh Song <ghugh@bellini.mit.edu>
To: linux-kernel@vger.kernel.org
Subject: Something wrong with recent 2.4.21-rc* kernels?
Date: Sat, 31 May 2003 14:15:16 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.53.0305311354230.2743@bellini.mit.edu> (raw)
I am comparing
2.4.21-pre3-ac4
2.4.21-rc5-ac1
2.4.21-rc6-ac1
In the last two kernels, something is definitely not right.
LaTeXing a big file takes about twice the time compared to
the same job under 2.4.21-pre3-ac4.
However, I am not totally satisfied with the 2.4.21-pre3-ac4, either.
In the beginning just after a reboot, the condition is really nice.
However, after a while, "time"ing a job reveals that something bad is
happening in the first column of "real" time, which means the wall-clock
timing. One might say that it is still better with 2.4.21-pre3-ac4
than the situation with 2.4.21-rc5-ac1 or with 2.4.21-rc6-ac1, because
it still does not contaminate "user" time in the middle column.
With 2.4.21-pre3-ac4, as everyone comlained, there seems to be a
problem with the cursor movement while kernel-compilation in the back.
The mouse movement seemed to have improved in 2.4.21-rc6-ac1. But
overall performance hit is just not acceptable.
BTW, the .config file for 2.4.21-rc6-ac1 has been taken from
2.4.21-pre3-ac4 during compilation.
The motherboard is an Asus with the Nvidia2 chipset.
Main system is running off SCSI hard disks under Adaptec U2-SCSI PCI
controller. No ATAPI hard disk is running at the moment.
I never used the installed ATAPI CDrom during the test.
In the emaillist, I have been reading about random halts in recent
kernels, i.e., 2.4.21-rc*. Well. I did not experience such a
drastic things. maybe because I did not wait long enough.
Regards,
G. Hugh Song
next reply other threads:[~2003-05-31 18:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-31 18:15 ghugh Song [this message]
2003-05-31 18:56 ` More on Blade 100/AC97 codec detection failure J.C. Wren
2003-05-31 20:00 Something wrong with recent 2.4.21-rc* kernels? ghugh Song
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=Pine.LNX.4.53.0305311354230.2743@bellini.mit.edu \
--to=ghugh@bellini.mit.edu \
--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
all inboxes | Powered by JetHome®