All of lore.kernel.org
 help / color / mirror / Atom feed
From: Zatalian <zatalian@pandora.be>
To: linux-kernel@vger.kernel.org
Cc: DiegoCG@teleline.es
Subject: [Bug 1303] 2.6.0-test4, test5, test6, test7, test8, test9 very very slow with smp kernel
Date: Sun, 16 Nov 2003 17:30:00 +0100	[thread overview]
Message-ID: <1069000200.4225.11.camel@localhost> (raw)
In-Reply-To: <200311161500.hAGF0Hbh005350@fire-1.osdl.org>

http://bugme.osdl.org/show_bug.cgi?id=1303

Hi,

Diego suggested sending my bug to this email-adress so maybe some
kernel-developer can tell me what is happening with my computer and if
other people suffer the same problem.

This is what i get : 

Since kernel 2.6.0-test4 my system becomes very slow when using an
smp-kernel.

I have a DELL poweredge 2400 dual PIII 733 Mhz machine with 768 Mb sdram
and some SCSI disks 
I use ext3 for my boot partition and reiserfs for my root partition.

Right now I use kernel 2.6.0-test2 with smp without any problems.

This problem is not X related. Just booting without loading the nvidia
module, logging into the console and shutting down takes more than 10
minutes. With a normal kernel, this would take max. 2 minutes. Most
things become very slow (but other commands like "dmesg >
dmesg.2.6.0-test9" are as fast as always).

The only thing I found different between a normal working kernel and a
buggy kernel are the following lines in my dmesg : 


>> Losing too many ticks!
>> TSC cannot be used as a timesource. (Are you running with SpeedStep?)
>> Falling back to a sane timesource.

I don't have them when running a normal kernel.

I hope somebody can tell me what's going on here.

Thanks.

Zatalian.


           reply	other threads:[~2003-11-16 16:30 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <200311161500.hAGF0Hbh005350@fire-1.osdl.org>]

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=1069000200.4225.11.camel@localhost \
    --to=zatalian@pandora.be \
    --cc=DiegoCG@teleline.es \
    --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 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.