| View previous topic :: View next topic |
| Author |
Message |
net_keeper
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 108
Location: Earth
|
 Posted: Tue Jul 29, 2003 1:28 pm Post subject: Running program cause mouse lag's, and slow my pc. |
 |
|
Hy,
I have problem.
While im doing any proccess, dosnt matter which,
My computer getting slow.
The mouse is bumping and starting to bump everywhere...
That's happend if for eample i'm doing emerge sync.
In my mandrake (with multimedia kernel-preemptible), that's dosent happend.
I've tried Kernel 2.4 and 2.6 (test1) on my gentoo, with no use.
An idea?
There isnt any proccess running in background except my KDE and emerge sync.
I have Pentium 3, 800MHZ and 40GB Hard disk (7200RPM) and 256 SDRAM
Thank for your time |
|
| Back to top |
|
 |
ozukir@
Apprentice
Joined: 14 Oct 2002
Posts: 209
Location: USA
|
| Posted: Tue Jul 29, 2003 2:02 pm Post subject: |
|
|
| Determine that your system is not under some significant load using top. man top for more info. |
|
| Back to top |
|
|
net_keeper
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 108
Location: Earth
|
| Posted: Tue Jul 29, 2003 2:16 pm Post subject: |
|
|
ive try top,
Every proccess im running is taking almost everything from my CPU.
If im running emerge sync so python get more than 50% from my CPU.
Nothing else is overloading.
Ive try to disable the preemtible but with no use. |
|
| Back to top |
|
|
ozukir@
Apprentice
Joined: 14 Oct 2002
Posts: 209
Location: USA
|
| Posted: Wed Jul 30, 2003 6:14 am Post subject: |
|
|
I'm sorry, I don't understand. Every process is using an equal percentage of your CPU such that 10 processes are using 10% each? What is going on when the system is idle, what is the load average?
Disable X and run top from the console. Run some programs and monitor top. Is the load average still high? |
|
| Back to top |
|
|
net_keeper
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 108
Location: Earth
|
| Posted: Wed Jul 30, 2003 6:51 am Post subject: |
|
|
Yes,
I dont have any process who eats my CPU when the computer is idle.
But every proccess I am trying to run eat's the whole CPU (at the loading) and my mouse start jumping and bumping. |
|
| Back to top |
|
|
ozukir@
Apprentice
Joined: 14 Oct 2002
Posts: 209
Location: USA
|
| Posted: Wed Jul 30, 2003 7:21 am Post subject: |
|
|
You should really exit your Window manager and disable the X server, then run top in one console and a process (such as emerge sync) in another. Still the same problem?
How:
1. Ctl + Alt + F1 : Exits X taking you to a console
2. Log in as root and disable your window manager (and through association the X server)
| Code: | | # /etc/init.d/xdm stop |
3. Log into another console (Ctl + F2) and run a process.
4. Go back to first console (Ctl + F1) and run top.
What kernel optimizations are you using? What flags? Can you reduce these to more sane values? What services are running in the background (DNS, sshd, apache, etc.)? What file system are you using (reiserfs, ext3)? What hard drive parameters are you using (man hdparm)?
Maybe one of these questions will begin to lead you in the right direction. Let me know what you find. |
|
| Back to top |
|
|
net_keeper
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 108
Location: Earth
|
| Posted: Wed Jul 30, 2003 7:30 am Post subject: |
|
|
Ive quit X, and emerge sync taking 38% from my CPU.
Nothing running backgorund, only: PPTP dialer, and DHCP server.
Im using reiserfs, and i dont know my harddisk parameters.
Is there any funtion to show the parameter? |
|
| Back to top |
|
|
net_keeper
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 108
Location: Earth
|
| Posted: Wed Jul 30, 2003 7:31 am Post subject: |
|
|
| Code: | bash-2.05b# hdparm -I /dev/hda7
/dev/hda7:
ATA device, with non-removable media
Model Number: ST340016A
Serial Number: 3HSA5TJY
Firmware Revision: 3.19
Standards:
Supported: 5 4 3 2
Likely used: 6
Configuration:
Logical max current
cylinders 16383 16383
heads 16 16
sectors/track 63 63
--
CHS current addressable sectors: 16514064
LBA user addressable sectors: 78165360
device size with M = 1024*1024: 38166 MBytes
device size with M = 1000*1000: 40020 MBytes (40 GB)
Capabilities:
LBA, IORDY(can be disabled)
bytes avail on r/w long: 4 Queue depth: 1
Standby timer values: spec'd by Standard
R/W multiple sector transfer: Max = 16 Current = ?
Recommended acoustic management value: 128, current value: 128
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow control=120ns
Commands/features:
Enabled Supported:
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* Look-ahead
* Write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
Device Configuration Overlay feature set
* Automatic Acoustic Management feature set
SET MAX security extension
* DOWNLOAD MICROCODE cmd
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
HW reset results:
CBLID- above Vih
Device num = 1
Checksum: correct
|
|
|
| Back to top |
|
|
ozukir@
Apprentice
Joined: 14 Oct 2002
Posts: 209
Location: USA
|
| Posted: Wed Jul 30, 2003 8:55 am Post subject: |
|
|
OK, so you've tried two different kernel versions (2.4 & 2.6) with the same results. I assume that you have a fairly standard kernel configuration in both instances. You could try running a precompiled kernel from the Gentoo Live CD with your binaries and normal working environment to determine for sure that the culprit is not the kernel. For now I have to assume that your kernels are fine. You never mentioned your make.conf flags and optimizations. I have to assume that those are pretty standard as well. You don't mention any unusual error messages. I have to assume that all is well here.
It's difficult for me to understand what is exactly going on here without having my hands on your system. You say that when running Mandrake you have no such problems, so we can assume that this is not directly hardware related. That really leaves only your optimizations or your configuration, and I'm leaning more towards your kernel and optimizations. Is this your only gentoo system? I wish I could help more. |
|
| Back to top |
|
|
net_keeper
Tux's lil' helper
Joined: 06 Jul 2003
Posts: 108
Location: Earth
|
| Posted: Wed Jul 30, 2003 9:16 am Post subject: |
|
|
This is my first and my only gentoo system.
My make.conf:
| Code: |
# Copyright 2000-2003 Daniel Robbins, Gentoo Technologies, Inc.
# Contains local system settings for Portage system
# $Header: /home/cvsroot/gentoo-src/portage/cnf/make.conf,v 1.58 2003/03/22 15:26:27 carpaski Exp $
# Please review 'man make.conf' for more information.
# Build-time functionality
# ========================
#
# The USE variable is used to enable optional build-time functionality. For
# example, quite a few packages have optional X, gtk or GNOME functionality
# that can only be enabled or disabled at compile-time. Gentoo Linux has a
# very extensive set of USE variables described in our USE variable HOWTO at
# http://www.gentoo.org/doc/use-howto.html
#
# The available list of use flags with descriptions is in your portage tree.
# Use 'less' to view them: --> less /usr/portage/profiles/use.desc <--
#
# 'ufed' is an ncurses/dialog interface available in portage to make handling
# useflags for you. 'emerge app-admin/ufed'
#
# Example:
USE="acpi alsa apm arts avi cdr cups gif gnome gpm gtk gtk2 jpeg mmx mozilla mpeg mysql oggvorbis -oss png python qt samba spell usb wmf X xml xml2 xmms"
# Host Setting
# ============
#
# If you are using a Pentium Pro or greater processor, leave this line as-is;
# otherwise, change to i586, i486 or i386 as appropriate. All modern systems
# (even Athlons) should use "i686-pc-linux-gnu"
#
CHOST="i686-pc-linux-gnu"
# Host and optimization settings
# ==============================
#
# For optimal performance, enable a CFLAGS setting appropriate for your CPU.
#
# Please note that if you experience strange issues with a package, it may be
# due to gcc's optimizations interacting in a strange way. Please test the
# package (and in some cases the libraries it uses) at default optimizations
# before reporting errors to developers.
#
# -mcpu=<cpu-type> means optimize code for the particular type of CPU without
# breaking compatibility with other CPUs.
#
# -march=<cpu-type> means to take full advantage of the ABI and instructions
# for the particular CPU; this will break compatibility with older CPUs (for
# example, -march=athlon-xp code will not run on a regular Athlon, and
# -march=i686 code will not run on a Pentium Classic.
#
# CPU types supported in gcc-3.2 and higher: athlon-xp, athlon-mp,
# athlon-tbird, athlon, k6, k6-2, k6-3, i386, i486, i586 (Pentium), i686
# (PentiumPro), pentium, pentium-mmx, pentiumpro, pentium2 (Celeron), pentium3.
# Note that Gentoo Linux 1.4 and higher include at least gcc-3.2.
# ATHLON-4 will generate invalid SSE instructions; use 'athlon' instead.
# PENTIUM4 will generate invalid instructions; use 'pentium3' instead.
#
# CPU types supported in gcc-2.95*: k6, i386, i486, i586 (Pentium), i686
# (Pentium Pro), pentium, pentiumpro Gentoo Linux 1.2 and below use gcc-2.95*
#
# Decent examples:
#
#CFLAGS="-mcpu=athlon-xp -O3 -pipe"
CFLAGS="-march=pentium3 -O3 -pipe"
# If you set a CFLAGS above, then this line will set your default C++ flags to
# the same settings.
CXXFLAGS="${CFLAGS}"
# Advanced Masking
# ================
#
# Gentoo is using a new masking system to allow for easier stability testing
# on packages. KEYWORDS are used in ebuilds to mask and unmask packages based
# on the platform they are set for. A special form has been added that
# indicates packages and revisions that are expected to work, but have not yet
# been approved for the stable set. '~arch' is a superset of 'arch' which
# includes the unstable, in testing, packages. Users of the 'x86' architecture
# would add '~x86' to ACCEPT_KEYWORDS to enable unstable/testing packages.
# '~ppc', '~sparc', '~sparc64' are the unstable KEYWORDS for their respective
# platforms. DO NOT PUT ANYTHING BUT YOUR SPECIFIC ~ARCHITECTURE IN THE LIST.
# IF YOU ARE UNSURE OF YOUR ARCH, OR THE IMPLICATIONS, DO NOT MODIFY THIS.
#
#ACCEPT_KEYWORDS="~arch"
# Portage Directories
# ===================
#
# Each of these settings controls an aspect of portage's storage and file
# system usage. If you change any of these, be sure it is available when
# you try to use portage. *** DO NOT INCLUDE A TRAILING "/" ***
#
# PORTAGE_TMPDIR is the location portage will use for compilations and
# temporary storage of data. This can get VERY large depending upon
# the application being installed.
#PORTAGE_TMPDIR=/var/tmp
#
# PORTDIR is the location of the portage tree. This is the repository
# for all profile information as well as all ebuilds. This directory
# itself can reach 200M. WE DO NOT RECOMMEND that you change this.
#PORTDIR=/usr/portage
#
# DISTDIR is where all of the source code tarballs will be placed for
# emerges. The source code is maintained here unless you delete
# it. The entire repository of tarballs for gentoo is 9G. This is
# considerably more than any user will ever download. 2-3G is
# a large DISTDIR.
#DISTDIR=${PORTDIR}/distfiles
#
# PKGDIR is the location of binary packages that you can have created
# with '--buildpkg' or '-b' while emerging a package. This can get
# upto several hundred megs, or even a few gigs.
#PKGDIR=${PORTDIR}/packages
#
# PORT_LOGDIR is the location where portage will store all the logs it
# creates from each individual merge. They are stored as YYMMDD-$PF.log
# in the directory specified. This is disabled until you enable it by
# providing a directory. Permissions will be modified as needed IF the
# directory exists, otherwise logging will be disabled.
#PORT_LOGDIR=/var/log/portage
#
# PORTDIR_OVERLAY is a directory where local ebuilds may be stored without
# concern that they will be deleted by rsync updates. Default is not
# defined.
#PORTDIR_OVERLAY=/usr/local/portage
# Fetching files
# ==============
#
# If you need to set a proxy for wget or lukemftp, add the appropriate "export
# ftp_proxy=<proxy>" and "export http_proxy=<proxy>" lines to /etc/profile if
# all users on your system should use them.
#
# Portage uses wget by default. Here are some settings for some alternate
# downloaders -- note that you need to merge these programs first before they
# will be available.
#
# Default fetch command (5 tries, passive ftp for firewall compatibility)
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp \${URI} -P \${DISTDIR}"
#
# Using wget, ratelimiting downloads
#FETCHCOMMAND="/usr/bin/wget -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#RESUMECOMMAND="/usr/bin/wget -c -t 5 --passive-ftp --limit-rate=200k \${URI} -P \${DISTDIR}"
#
# Lukemftp (BSD ftp):
#FETCHCOMMAND="/usr/bin/lukemftp -s -a -o \${DISTDIR}/\${FILE} \${URI}"
#RESUMECOMMAND="/usr/bin/lukemftp -s -a -R -o \${DISTDIR}/\${FILE} \${URI}"
#
# Prozilla (turbo downloader)
#FETCHCOMMAND='/usr/bin/proz --no-getch -s ${URI} -P ${DISTDIR}'
#
# Portage uses GENTOO_MIRRORS to specify mirrors to use for source retrieval.
# The list is a space seperated list which is read left to right. If you use
# another mirror we highly recommend leaving the default mirror at the end of
# the list so that portage will fall back to it if the files cannot be found
# on your specified mirror. We _HIGHLY_ recommend that you change this setting
# to a nearby mirror by merging and using the 'mirrorselect' tool.
#GENTOO_MIRRORS="<your_mirror_here> http://gentoo.oregonstate.edu/ http://www.ibiblio.org/pub/Linux/distributions/gentoo"
# Advanced Features
# =================
#
# MAKEOPTS provides extra options that may be passed to 'make' when a
# program is compiled. Presently the only use is for specifying
# the number of parallel makes (-j) to perform. The suggested number
# for parallel makes is CPUs+1.
#MAKEOPTS="-j2"
#
# AUTOCLEAN enables portage to automatically clean out older or overlapping
# packages from the system after every successful merge. This is the
# same as running 'emerge -c' after every merge. Set with: "yes" or "no".
# This does not affect the unpacked source. See 'noclean' below.
#AUTOCLEAN="yes"
#
# FEATURES are settings that affect the functionality of portage. Most of
# these settings are for developer use, but some are available to non-
# developers as well. 'buildpkg' is an always-on setting for the emerge
# flag of the same name. It causes binary packages to be created of all
# packages that are merged. 'distcc' enables distcc support for via CC.
# 'userpriv' allows portage to drop root privleges while it is compiling
# as a security measure, and as a side effect this can remove sandbox
# access violations for users. 'usersandbox' enables sandboxing while
# portage is running under userpriv. 'notitles' disables xterm titlebar
# updates (which contain status info). 'noclean' prevents portage from
# removing the source and temporary files after a merge -- for debugging
# purposes only. 'noauto' is a feature which causes ebuild to perform
# the action requested and not any other required actions like clean or
# unpack -- for debugging purposes only. 'cvs' is a feature for developers
# that causes portage to enable full settings and USE flags in SRC_URI and
# has wide effects -- don't set this unless you're ready for it. 'keeptemp'
# prevents the clean phase from deleting the temp files ($T) from a merge.
# 'keepwork' prevents the clean phase from deleting the $WORKDIR.
#FEATURES="sandbox buildpkg ccache distcc userpriv usersandbox notitles noclean noauto cvs keeptemp keepwork"
#
# CCACHE_SIZE sets the space use limitations for ccache. The default size is
# 2G, and will be set if not defined otherwise and ccache is in features.
# Portage will set the default ccache dir if it is not present in the
# user's environment: ${PORTAGE_TMPDIR}/ccache (/var/tmp/ccache).
# Sizes are specified with 'G' 'M' or 'K'.
# '4G' for 4 gigabytes, '4096M' for 4 gigabytes, etc... Default is 2G
#CCACHE_SIZE="2G"
#
# RSYNC_RETRIES sets the number of times portage will attempt to retrieve
# a current portage tree before it exits with an error. This allows
# for a more successful retrieval without user intervention most times.
#RSYNC_RETRIES="3"
#
# RSYNC_TIMEOUT sets the length of time rsync will wait before it times out
# on a connection. Most users will benefit from this setting as it will
# reduce the amount of 'dead air' they experience when they run across
# the occasional, unreachable mirror. Dialup users might want to set this
# value up around the 300 second mark.
#RSYNC_TIMEOUT=180
#
# RSYNC_EXCLUDEFROM is a file that portage will pass to rsync when it updates
# the portage tree. Specific chucks of the tree may be excluded from
# consideration. This may cause dependency failures if you are not careful.
# The file format is one pattern per line, blanks and ';' or '#' lines are
# comments. See 'man rsync' for more details on the exclude-from format.
#RSYNC_EXCLUDEFROM=/etc/portage/rsync_excludes
|
|
|
| Back to top |
|
|
Assgier
Tux's lil' helper
Joined: 28 May 2003
Posts: 127
Location: Europe -> Netherlands -> Utrecht -> Amersfoort
|
| Posted: Fri Aug 01, 2003 7:50 pm Post subject: |
|
|
you might want to try enabling DMA on your harddrive (shouldn't the drive be named /dev/hda instead of /dev/hda7 ?)...
to see whether DMA is currently enabled, type as root:
hdparm -d /dev/hda7 (/dev/hda if hda7 doesn't work)
if it's disabled (0), type following (as root):
hdparm -d1 /dev/hda7 (/dev/hda if hda7 doesn't work)
after that retry to do an emerge (r)sync and reply here with your info [img:39ce9bf6e1]http://gathering.tweakers.net/global/smileys/smile.gif[/img:39ce9bf6e1]
_________________
 |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Kernel & Hardware
