I wonder if anybody can shed some light on this....... I am running 6.1 and have successfully replaced all that I used to have on M$ so can effectively bin it.... however something is beginning to play up......................................... Every now and again, at different times of the day, I start Kwintv (I cannot get sound with xawtv) and my system freezes. When I say freeze, it freezes solid, the Hard Disk comes on, the cursor sticks, no combination of any keys will make the slightest difference - nothing..... Spookily, Seti is still chugging on in the background as is the sound element of the Kwintv. I have to resort to the reset button to release this circle and on the forced check, normally I get :- Deleted inode 940132 has zero dtime..fixed and then back to normal, sometimes I have to repeat this cycle 4-5 times before peace and tranquility is restored. Tonight, it happened again, this time fsck had to be run manually and reported block bit map diffrences, unattached inodes etc (not entirely sure what it all means really) Restored the situation anyway and checked /var/log/messages - ".........Kernel bttv0 PLL 28636363 => 35468950 ok" ".........Kernel hdb: lost interrupt" Anybody got a clue what all this is about ? I don't particularly like having to keep resetting the system ! Many thanks Pete -- -------------------------------------------------------------------- Still thinking of something witty to put in my signature file ! -------------------------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
I've had somewhat of the same problem before. But mine was because I ran killall5 it sounds like your ram is being over-used. Try killing some processes and see if that helps at all ryan --signatures are overrated--
-----Original Message----- From: Pete Atkinson [mailto:Superseagulls@netscapeonline.co.uk] Sent: Wednesday, March 01, 2000 2:50 PM To: suse-linux-e@suse.com Subject: [SLE] Complete system lock up
I wonder if anybody can shed some light on this.......
I am running 6.1 and have successfully replaced all that I used to have on M$ so can effectively bin it.... however something is beginning to play up.........................................
Every now and again, at different times of the day, I start Kwintv (I cannot get sound with xawtv) and my system freezes. When I say freeze, it freezes solid, the Hard Disk comes on, the cursor sticks, no combination of any keys will make the slightest difference - nothing..... Spookily, Seti is still chugging on in the background as is the sound element of the Kwintv. I have to resort to the reset button to release this circle and on the forced check, normally I get :- Deleted inode 940132 has zero dtime..fixed and then back to normal, sometimes I have to repeat this cycle 4-5 times before peace and tranquility is restored. Tonight, it happened again, this time fsck had to be run manually and reported block bit map diffrences, unattached inodes etc (not entirely sure what it all means really) Restored the situation anyway and checked /var/log/messages -
".........Kernel bttv0 PLL 28636363 => 35468950 ok" ".........Kernel hdb: lost interrupt"
Anybody got a clue what all this is about ?
I don't particularly like having to keep resetting the system !
Many thanks
Pete -- --------------------------------------------------------------------
Still thinking of something witty to put in my signature file !
--------------------------------------------------------------------
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Ryan Yagatich wrote:
I've had somewhat of the same problem before. But mine was because I ran killall5
it sounds like your ram is being over-used. Try killing some processes and see if that helps at all
ryan
Or, if you're on a network, try to telnet (rlogin, ssh, ...) into your machine, and see what's going on. Iwan. -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Thanks to all that have replied.. I have tried to telnet in, but unfortunately even though seti etc is still running, the "system" is dead - I can't even ping my machine.. I have also offloaded squid and wwwrun which seemed to be hogging a fair amount of ram - I have "niced" seti as this was quite intensive but it still does it (occassionally) So.. from a ram point of view, this is free total used free shared buffers cached Mem: 59690 56512 3168 33540 1980 19112 -/+ buffers/cache 35420 24260 Swap: 128516 3028 125488 Considering that Seti and the Tv are currently running, the swap use seems low ? This is extracts from top PID PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM COMMAND 2162 16 11 13628 13M 600 R N 0 98.6 21.9 seti 2043 0 0 12112 11M 1224 S 0 0.3 20.2 X 2156 0 0 8252 8252 3412 S 0 0 13.8 kwintv finally, my fstab /dev/hdb4 swap swap defaults 0 0 (128M) /dev/hdb3 / ext2 defaults 1 1 (6GB) 66%cap /dev/hdb2 /boot ext2 defaults 1 2 (8MB) 26% /dev/hda1 /dos1 vfat defaults 0 0 (850M) 79% /dev/hdb1 /dos1 vfat defaults 0 0 (1.6GB) 38% I sippose with the benefit of hindsight that my disk set up is all wrong - especially now that windross is effectively redundant - it seemed to evolve that way I am using a 400Mhz Celeron - 64M Ram on a 66Mhz LX board any ideas - Pete On Wed, 01 Mar 2000, Iwan Mouwen wrote: > Ryan Yagatich wrote:
I've had somewhat of the same problem before. But mine was because I ran killall5
it sounds like your ram is being over-used. Try killing some processes and see if that helps at all
ryan
Or, if you're on a network, try to telnet (rlogin, ssh, ...) into your machine, and see what's going on.
Iwan.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Pete Atkinson wrote:
Thanks to all that have replied..
I have tried to telnet in, but unfortunately even though seti etc is still running, the "system" is dead - I can't even ping my machine..
I have also offloaded squid and wwwrun which seemed to be hogging a fair amount of ram - I have "niced" seti as this was quite intensive but it still does it (occassionally)
So..
from a ram point of view, this is free
total used free shared buffers cached Mem: 59690 56512 3168 33540 1980 19112 -/+ buffers/cache 35420 24260 Swap: 128516 3028 125488
Considering that Seti and the Tv are currently running, the swap use seems low ?
This is extracts from top
PID PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM COMMAND 2162 16 11 13628 13M 600 R N 0 98.6 21.9 seti 2043 0 0 12112 11M 1224 S 0 0.3 20.2 X 2156 0 0 8252 8252 3412 S 0 0 13.8 kwintv
finally, my fstab
/dev/hdb4 swap swap defaults 0 0 (128M) /dev/hdb3 / ext2 defaults 1 1 (6GB) 66%cap /dev/hdb2 /boot ext2 defaults 1 2 (8MB) 26% /dev/hda1 /dos1 vfat defaults 0 0 (850M) 79% /dev/hdb1 /dos1 vfat defaults 0 0 (1.6GB) 38%
I sippose with the benefit of hindsight that my disk set up is all wrong - especially now that windross is effectively redundant - it seemed to evolve that way I am using a 400Mhz Celeron - 64M Ram on a 66Mhz LX board
any ideas -
Pete
On Wed, 01 Mar 2000, Iwan Mouwen wrote: > Ryan Yagatich wrote:
I've had somewhat of the same problem before. But mine was because I ran killall5
it sounds like your ram is being over-used. Try killing some processes and see if that helps at all
ryan
Or, if you're on a network, try to telnet (rlogin, ssh, ...) into your machine, and see what's going on.
Iwan.
Two thoughts: 1) I have 64MB of RAM and my free shows: total used free shared buffers cached Mem: 62640 61068 1572 59580 924 24052 -/+ buffers/cache: 36092 26548 Swap: 82652 528 82124 yours shows only 59690. Where is the rest? 2) If you are able to do free and top, why don't you 'kill -9 2162' to stop seti? JLK -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Its getting stranger ..... if I don't have kwintv running, I have 62880 ram, if I start Kwintv it drops to 59680, I thought 'free' would have reported ram regardless of what is running - anybody else like to try with this ? I suppose at the end of the day, I should get into the habit of killing seti before I try and run anything - not exactly ideal though..... Pete...... aying that, i have now got kmail, kwintv, seti and a kvt window open and it still shows 59680 with 1780 free - no sign of anything freezing ;-)
Two thoughts: 1) I have 64MB of RAM and my free shows: total used free shared buffers cached Mem: 62640 61068 1572 59580 924 24052 -/+ buffers/cache: 36092 26548 Swap: 82652 528 82124
yours shows only 59690. Where is the rest?
2) If you are able to do free and top, why don't you 'kill -9 2162' to stop seti?
JLK
On Sat, 04 Mar 2000, Jerry L Kreps wrote:
Pete Atkinson wrote:
Thanks to all that have replied..
I have tried to telnet in, but unfortunately even though seti etc is still running, the "system" is dead - I can't even ping my machine..
I have also offloaded squid and wwwrun which seemed to be hogging a fair amount of ram - I have "niced" seti as this was quite intensive but it still does it (occassionally)
So..
from a ram point of view, this is free
total used free shared buffers cached Mem: 59690 56512 3168 33540 1980 19112 -/+ buffers/cache 35420 24260 Swap: 128516 3028 125488
Considering that Seti and the Tv are currently running, the swap use seems low ?
This is extracts from top
PID PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM COMMAND 2162 16 11 13628 13M 600 R N 0 98.6 21.9 seti 2043 0 0 12112 11M 1224 S 0 0.3 20.2 X 2156 0 0 8252 8252 3412 S 0 0 13.8 kwintv
finally, my fstab
/dev/hdb4 swap swap defaults 0 0 (128M) /dev/hdb3 / ext2 defaults 1 1 (6GB) 66%cap /dev/hdb2 /boot ext2 defaults 1 2 (8MB) 26% /dev/hda1 /dos1 vfat defaults 0 0 (850M) 79% /dev/hdb1 /dos1 vfat defaults 0 0 (1.6GB) 38%
I sippose with the benefit of hindsight that my disk set up is all wrong - especially now that windross is effectively redundant - it seemed to evolve that way I am using a 400Mhz Celeron - 64M Ram on a 66Mhz LX board
any ideas -
Pete
On Wed, 01 Mar 2000, Iwan Mouwen wrote: > Ryan Yagatich wrote:
I've had somewhat of the same problem before. But mine was because I ran killall5
it sounds like your ram is being over-used. Try killing some processes and see if that helps at all
ryan
Or, if you're on a network, try to telnet (rlogin, ssh, ...) into your machine, and see what's going on.
Iwan.
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
Pete Atkinson wrote:
Thanks to all that have replied..
I have tried to telnet in, but unfortunately even though seti etc is still running, the "system" is dead - I can't even ping my machine..
This is extracts from top
PID PRI NI SIZE RSS SHARE STAT LIB %CPU %MEM COMMAND 2162 16 11 13628 13M 600 R N 0 98.6 21.9 seti 2043 0 0 12112 11M 1224 S 0 0.3 20.2 X 2156 0 0 8252 8252 3412 S 0 0 13.8 kwintv
Considering seti looks to have almost 99% of your cpu I wonder if it's not dead but just doesn't have time to listen to you. Nick -- -------------------------------------------------- Nick Zentena "Microsoft has unjustifiably jeopardized the stability and security of the operating system." U.S. District Judge Thomas Penfield Jackson Nov 5/1999 -------------------------------------------------- -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/
participants (5)
-
iwan＠vvier.tudelft.nl -
JerryKreps＠alltel.net -
ryagatich＠csn1.com -
Superseagulls＠netscapeonline.co.uk -
zentena＠hophead.dyndns.org