LinuxQuestions.org
View the Most Wanted LQ Wiki articles.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Newbie
User Name
Password
Linux - Newbie This Linux forum is for members that are new to Linux.
Just starting out and have a question? If it is not in the man pages or the how-to's this is the place!

Notices



Reply
 
Search this Thread
Old 06-26-2006, 01:36 AM   #1
bene223
LQ Newbie
 
Registered: Jan 2006
Posts: 19

Rep: Reputation: 0
Very sluggish performance *FIXED*


My computer:
AMD64 3000+ 939 pin
Abit AN8 939 pin nForce motherboard
1 gig of ram
Geforce 6800GT 256MB PCI-e

Linux Distribution:
Debian 3.1 (Sarge) using Gnome

Graphics Driver:
Linux IA32 1.0-8762
(downloaded from http://www.nvidia.com/object/unix.html)

uname -a
Linux debian 2.4.27-2-386 #1 ........ i686 GNU/Linux


I have a serious lag issue in Debian with any program that involves consuming bandwidth. This isn't limited to just telelag, I mean it's like the computer was just put on pause. It isn't just little jolts of lag here and there - my computer almost locks up completely for at least 10 seconds or so when it's trying to load a webpage in Firefox for example and it takes forever to load webpages. After the webpage has loaded though, I don't get any more freezeups & I can scroll up and down without any computer lag. It isn't just Firefox either, I've tried other web browsers included with Debian and it's the same issue. I also pinged the debian computer and it's latency is roughly 300 even every time, yet other computers on my network ping normal. Games, OpenOffice, etc. run just fine without any Computer lag what-so-ever which doesn't make sense to me. Any ideas?

Last edited by bene223; 06-27-2006 at 03:21 AM.
 
Old 06-26-2006, 02:20 AM   #2
cs-cam
Senior Member
 
Registered: May 2004
Location: Australia
Distribution: Gentoo
Posts: 3,544
Blog Entries: 4

Rep: Reputation: 56
Crack open a terminal and run top. That should show you which processes are using too much memory/CPU time.
 
Old 06-26-2006, 02:34 AM   #3
bene223
LQ Newbie
 
Registered: Jan 2006
Posts: 19

Original Poster
Rep: Reputation: 0
When I hit refresh on this page and monitor top, everything pretty much freezes but when it comes out of "the freeze" mozilla is using 25% of the processor. After the webpage has loaded though, it goes down to around 3%
 
Old 06-26-2006, 03:44 AM   #4
cs-cam
Senior Member
 
Registered: May 2004
Location: Australia
Distribution: Gentoo
Posts: 3,544
Blog Entries: 4

Rep: Reputation: 56
Weird. Is your hard disk going crazy at all?
 
Old 06-26-2006, 03:48 AM   #5
rickh
Senior Member
 
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250

Rep: Reputation: 60
What does your /etc/resolv.conf file look like?

Sounds like it could be a dns issue.
 
Old 06-26-2006, 10:17 AM   #6
bene223
LQ Newbie
 
Registered: Jan 2006
Posts: 19

Original Poster
Rep: Reputation: 0
cs-cam: I hit refresh on this page and look at my HDD LED and it doesn't flash or anything, so I guess the answer is no. Is that what you mean by the harddrive going crazy?

rickh:

cat resolv.conf
search
nameserver 192.168.0.1

I don't recall setting that as a nameserver. I don't even have a nameserver, it's just this computer and another computer on the network hooked up to a linksys router.
 
Old 06-26-2006, 10:43 AM   #7
rickh
Senior Member
 
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250

Rep: Reputation: 60
Quote:
nameserver 192.168.0.1
I think that's your problem, but I can't quite remember what the permanent fix is. If you have DSL, I think that may have something to do with it. For a temporary fix, try deleting both lines leaving an empty /etc/resolv.conf file.

Then connect to the net with firefox. I think that will rewrite the resolv.conf file correctly. After you connect, (if it works) look at the file again. You'll see what it should look like. I suspect however that the correct configuration won't survive a reboot.

Maybe searching these forums for "resolv.conf" will turn up a permanent solution.
 
Old 06-26-2006, 11:12 AM   #8
bene223
LQ Newbie
 
Registered: Jan 2006
Posts: 19

Original Poster
Rep: Reputation: 0
I deleted both lines and after I did, firefox wouldn't connect to the internet. So I rebooted, and resolv.conf changed the nameserver back to 192.168.0.1

I have DSL, a dynamic IP, using DHCP and I'm using a Linksys router. Maybe that will help. I'm still getting the very sluggish performance (computer lag and tele-lag) while browsing the web in Firefox. Anyone?

This is the output on my windows XP computer and everything connectionwise is working fine on it.
ipconfig /all
Quote:
Windows IP Configuration

Host Name . . . . . . . . . . . . : BEN
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Wireless Network Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros AR5005G Wireless Network Adapter
Physical Address. . . . . . . . . : 00-11-F5-C5-BE-6F
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.234.133
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.234.18
DHCP Server . . . . . . . . . . . : 192.168.234.18
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Monday, June 26, 2006 10:24:28 AM
Lease Expires . . . . . . . . . . : Tuesday, June 27, 2006 10:24:28 AM
This is the output on my Linux computer
ifconfig
Quote:
eth0 Link encap:Ethernet HWaddr 00:08:A1:47:69:47
inet addr:192.168.234.132 Bcast:192.168.234.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:721 errors:0 dropped:0 overruns:0 frame:0
TX packets:613 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:507800 (495.8 KiB) TX bytes:137973 (134.7 KiB)
Interrupt:5 Base address:0x9400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:106 errors:0 dropped:0 overruns:0 frame:0
TX packets:106 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0

Last edited by bene223; 06-26-2006 at 11:47 AM.
 
Old 06-26-2006, 11:35 AM   #9
sundialsvcs
Guru
 
Registered: Feb 2004
Location: SE Tennessee, USA
Distribution: Gentoo, LFS
Posts: 5,455

Rep: Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172Reputation: 1172
It definitely sounds like a timeout. If you are seeing a delay with no disk-drive activity, it could be that a particular application is frozen and isn't dealing with the GUI.

Check the usual suspects, like /var/log/messages (and other files in that directory).

Otherwise... "what changed?" When did this problem first appear?
 
Old 06-26-2006, 12:00 PM   #10
bene223
LQ Newbie
 
Registered: Jan 2006
Posts: 19

Original Poster
Rep: Reputation: 0
I don't know if this is what you mean by what changed but, resolv.conf changed the nameserver to 192.168.0.1 - This is what it was at before I deleted the entries in resolv.conf as requested in a few posts up.

This started yesterday when I installed Debian 3.1 (Sarge)

I copied a chunk of the log from /var/log/messages and /var/log/kernel

/var/log/messages
Quote:
Jun 26 02:35:48 localhost gconfd (root-1518): starting (version 2.8.1), pid 1518 user 'root'
Jun 26 02:35:48 localhost gconfd (root-1518): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jun 26 02:35:48 localhost gconfd (root-1518): Resolved address "xml:readwrite:/root/.gconf" to a writable configuration source at position 1
Jun 26 02:35:48 localhost gconfd (root-1518): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jun 26 02:36:41 localhost shutdown[1555]: shutting down for system halt
Jun 26 02:36:43 localhost gconfd (ben-1377): Received signal 15, shutting down cleanly
Jun 26 02:36:43 localhost gconfd (ben-1377): Exiting
Jun 26 02:36:44 localhost kernel: Kernel logging (proc) stopped.
Jun 26 02:36:44 localhost kernel: Kernel log daemon terminating.
Jun 26 02:36:44 localhost exiting on signal 15
Jun 26 02:37:59 localhost syslogd 1.4.1#17: restart.
Jun 26 02:37:59 localhost kernel: klogd 1.4.1#17, log source = /proc/kmsg started.
Jun 26 02:37:59 localhost kernel: Inspecting /boot/System.map-2.4.27-2-386
Jun 26 02:37:59 localhost kernel: Loaded 18328 symbols from /boot/System.map-2.4.27-2-386.
Jun 26 02:37:59 localhost kernel: Symbols match kernel version 2.4.27.
Jun 26 02:37:59 localhost kernel: Loaded 656 symbols from 28 modules.
Jun 26 02:37:59 localhost kernel: trl[ffffffff] cmdptr[ffffffff]
Jun 26 02:38:01 localhost lpd[1325]: restarted
Jun 26 02:38:04 localhost kernel: apm: BIOS version 1.2 Flags 0x07 (Driver version 1.16)
Jun 26 02:38:06 localhost kernel: NVRM: loading NVIDIA Linux x86 Kernel Module 1.0-8762 Mon May 15 13:06:38 PDT 2006Jun 26 02:38:06 localhost kernel: i2c-core.o: i2c core module version 2.6.1 (20010830)
Jun 26 02:38:06 localhost kernel: NVRM: Your Linux 2.4 kernel was configured to include modular
Jun 26 02:38:06 localhost kernel: NVRM: support for the Linux/i2c infrastructure, but the NVIDIA
Jun 26 02:38:06 localhost kernel: NVRM: Linux graphics driver was unable to locate and load the
Jun 26 02:38:06 localhost kernel: NVRM: i2c-core.o kernel module.
Jun 26 02:38:06 localhost kernel: NVRM:
Jun 26 02:38:06 localhost kernel: NVRM: If you wish to take advantage of the NVIDIA driver's i2c
Jun 26 02:38:06 localhost kernel: NVRM: support feature, please make sure the Linux/i2c kernel
Jun 26 02:38:06 localhost kernel: NVRM: modules are installed correctly.
Jun 26 02:38:07 localhost kernel: NVRM: bad caching on address 0xf294a000: actual 0x163 != expected 0x173
Jun 26 02:38:07 localhost kernel: NVRM: please see the README section on Cache Aliasing for more information
Jun 26 02:38:24 localhost gconfd (ben-1422): starting (version 2.8.1), pid 1422 user 'ben'
Jun 26 02:38:24 localhost gconfd (ben-1422): Resolved address "xml:readonly:/etc/gconf/gconf.xml.mandatory" to a read-only configuration source at position 0
Jun 26 02:38:24 localhost gconfd (ben-1422): Resolved address "xml:readwrite:/home/ben/.gconf" to a writable configuration source at position 1
Jun 26 02:38:24 localhost gconfd (ben-1422): Resolved address "xml:readonly:/etc/gconf/gconf.xml.defaults" to a read-only configuration source at position 2
Jun 26 02:38:40 localhost gconfd (ben-1422): Resolved address "xml:readwrite:/home/ben/.gconf" to a writable configuration source at position 0
Jun 26 02:38:54 localhost kernel: ffffffff]
Jun 26 02:43:05 localhost kernel: ffffffff]
Jun 26 02:44:07 localhost last message repeated 3 times
Jun 26 02:45:26 localhost kernel: ffffffff]
Jun 26 02:46:05 localhost last message repeated 2 times
Jun 26 02:47:25 localhost kernel: ffffffff]
Jun 26 02:49:49 localhost kernel: ffffffff]
Jun 26 02:50:31 localhost last message repeated 3 times
Jun 26 03:02:00 localhost kernel: ffffffff]
Jun 26 03:02:01 localhost kernel: ffffffff]
Jun 26 03:10:23 localhost kernel: ffffffff]
Jun 26 03:10:28 localhost kernel: ffffffff]
Jun 26 03:16:51 localhost kernel: ffffffff]
Jun 26 03:16:52 localhost kernel: <ffffffff]
Jun 26 03:16:52 localhost kernel: ffffffff]
Jun 26 03:16:53 localhost kernel: ffffffff]
Jun 26 03:20:44 localhost kernel: ffffffff]
I used cat /var/log/kernel and it scrolled forever, I waited 2 minutes and it was still scrolling from yesterday with errors all looking somewhat like this:

/var/log/kernel
Quote:
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 29 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 30 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 31 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Runaway loop while stopping context: ...
Jun 25 18:03:12 localhost kernel: ohci1394_1: Runaway loop while stopping context: ...
Jun 25 18:03:12 localhost kernel: ohci1394_1: Runaway loop while stopping context: reqTxComplete...
Jun 25 18:03:12 localhost kernel: ohci1394_1: Runaway loop while stopping context: respTxComplete...
Jun 25 18:03:12 localhost kernel: ohci1394_1: Runaway loop while stopping context: RQPkt...
Jun 25 18:03:12 localhost kernel: ohci1394_1: Runaway loop while stopping context: RSPkt...
Jun 25 18:03:12 localhost kernel: ohci1394_1: Error in reception of SelfID packets [0xffffffff/0x00000000] (count: 16)Jun 25 18:03:12 localhost kernel: ohci1394_1: Too many errors on SelfID error reception, giving up!
Jun 25 18:03:12 localhost kernel: ohci1394_1: Unhandled interrupt(s) 0xfe7cff0c
Jun 25 18:03:12 localhost kernel: ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 21 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 22 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 23 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 24 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 25 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 26 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 27 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 28 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 29 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 30 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Xmit 31 Context died: ctrl[ffffffff] cmdptr[ffffffff]
Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 0 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 1 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 2 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 3 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 4 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 5 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 6 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 7 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 8 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 9 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]Jun 25 18:03:12 localhost kernel: ohci1394_1: Iso Recv 10 Context died: ctrl[ffffffff] cmdptr[ffffffff] match[ffffffff]

Last edited by bene223; 06-26-2006 at 12:03 PM.
 
Old 06-26-2006, 12:01 PM   #11
rickh
Senior Member
 
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250

Rep: Reputation: 60
You're on the right track with the resolv.conf issue. That file needs to contain a real dns server, not 192.168.0.1

Is this a new dsl setup, at least new to Linux? Your dsl modem obviously has a built in firewall which is not playing nice with Linux. I have seen that several times lately with dsl ISPs. If you look in your router via the browser interface, you should see the correct ip information for dns servers.
 
Old 06-26-2006, 12:28 PM   #12
bene223
LQ Newbie
 
Registered: Jan 2006
Posts: 19

Original Poster
Rep: Reputation: 0
I've had this DSL modem for about 2 years. It's a Speedstream 5100 - I hope that is what you mean by asking if it's a new DSL setup to Linux. I used mozilla to log into my modem. I looked everywhere and didn't see anything that even remotely looked like there was a Firewall; it was all just connection related information such as Upsptream, Downstream, Connection Status, DNS Servers, etc.

Alright this what I just tried doing: I unplugged my router and I'm plugged straight into the DSL modem just to rule out a possible problem factor. My DSL modem's IP is 192.168.0.1 This is my guess why it is wanting to use the DSL Modem (192.168.0.1) as a nameserver. I still had the same lag issue. I then tried changing the DNS Server IP to the the one my modem had listed; I am still having the lag issue. Any ideas as to why I'm still getting this serious computer + tele lag when I'm browsing the Internet but not get lag what-so-ever using programs such as OpenOffice, various built-in games, etc.? Even when I just ping different websites (such as www.google.com) the ping is 300ms

Last edited by bene223; 06-26-2006 at 12:40 PM.
 
Old 06-26-2006, 10:46 PM   #13
chrism01
Guru
 
Registered: Aug 2004
Location: Sydney
Distribution: Centos 6.6, Centos 5.10
Posts: 16,324

Rep: Reputation: 2041Reputation: 2041Reputation: 2041Reputation: 2041Reputation: 2041Reputation: 2041Reputation: 2041Reputation: 2041Reputation: 2041Reputation: 2041Reputation: 2041
As said, it's a network issue ie resolv.conf.
Initially connect PC to DSL modem and manually enter ISP search domain and nameservers (should be 2 of them).
I think you need to reboot to make it take effect (ie it's not dynamically updated).
Alternatively, do
sevice network restart
or equiv on your system.
 
Old 06-26-2006, 11:08 PM   #14
bene223
LQ Newbie
 
Registered: Jan 2006
Posts: 19

Original Poster
Rep: Reputation: 0
How do I make resolv.conf not go back to 192.168.0.1 when I reboot? It resets itself when I reboot despite entering the dns server
 
Old 06-27-2006, 12:08 AM   #15
rickh
Senior Member
 
Registered: May 2004
Location: Albuquerque, NM USA
Distribution: Debian-Lenny/Sid 32/64 Desktop: Generic AMD64-EVGA 680i Laptop: Generic Intel SIS-AC97
Posts: 4,250

Rep: Reputation: 60
I don't have a specific answer, but if you do a "Search Titles Only" (Advanced Search), from the Search button at the top of this page, You'll get a lot of hits with various suggestions about resolving this issue.
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
sluggish Mandrake 10 joshy Mandriva 6 08-19-2004 06:06 PM
Sluggish linuxnubx Slackware 18 07-28-2004 04:27 AM
Should Fedora 1 be this sluggish? lrt2003 Fedora 1 05-22-2004 02:00 AM
Sluggish performance w/ RH 7.3 theonlylivinggo Linux - Newbie 0 02-15-2004 09:13 PM
Linux sluggish !!! juby Linux - General 9 05-14-2003 01:44 AM


All times are GMT -5. The time now is 03:45 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration