Monitor problem after system left overnight.
I have an older pc with an old slot II Celeron processer. It all seems ok. During the day when it goes into screen saver a small mouse movement brings it right back OK. But when it is left over night and I give it a mouse movement it comes back after a few min. with the screen seeming to vibrate and the mouse no longer will move. I can't do anything with it so I have to power down and restart it. It has an Nvidia MX-200 video card. Has anyone else run into this? Does anyone have any suggestions? Thanks Bob
On 10:11 Thu 21 Oct , Robert A. Rawlinson wrote:
I have an older pc with an old slot II Celeron processer. It all seems ok. During the day when it goes into screen saver a small mouse movement brings it right back OK. But when it is left over night and I give it a mouse movement it comes back after a few min. with the screen seeming to vibrate and the mouse no longer will move. I can't do anything with it so I have to power down and restart it. It has an Nvidia MX-200 video card. Has anyone else run into this? Does anyone have any suggestions? Thanks Bob
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Mind you, I'm no guru. It does sound, however, as if the overnight thing --and particularly the broken mouse-- point more to a problem recovering from suspension or hibernation. What kernel version are you using...? Errors in the log...? -- "Yogi" CH Namasté Yoga Studio
C Hamel wrote:
On 10:11 Thu 21 Oct , Robert A. Rawlinson wrote:
I have an older pc with an old slot II Celeron processer. It all seems ok. During the day when it goes into screen saver a small mouse movement brings it right back OK. But when it is left over night and I give it a mouse movement it comes back after a few min. with the screen seeming to vibrate and the mouse no longer will move. I can't do anything with it so I have to power down and restart it. It has an Nvidia MX-200 video card. Has anyone else run into this? Does anyone have any suggestions? Thanks Bob
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Mind you, I'm no guru. It does sound, however, as if the overnight thing --and particularly the broken mouse-- point more to a problem recovering from suspension or hibernation. What kernel version are you using...? Errors in the log...? -- "Yogi" CH Namasté Yoga Studio
Sorry I have been trying to get the log over on this pc to send. I am on Suse 9.1. I did find some kind of errors having to do with "kernal : badness in pci_find_subsys at drivers/pci/search:c167". There is a whole section of messaged associated with it. The messages repeat every few minutes until I rebooted. I am not yet able to get the log over here to send. I will do so as soon as I can figure out how to do so. Bob
On Thursday 21 Oct 2004 18:40, C Hamel wrote:
On 10:11 Thu 21 Oct , Robert A. Rawlinson wrote:
I have an older pc with an old slot II Celeron processer. It all seems ok. During the day when it goes into screen saver a small mouse movement brings it right back OK. But when it is left over night and I give it a mouse movement it comes back after a few min. with the screen seeming to vibrate and the mouse no longer will move. I can't do anything with it so I have to power down and restart it. It has an Nvidia MX-200 video card. Has anyone else run into this? Does anyone have any suggestions? Thanks Bob
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Mind you, I'm no guru. It does sound, however, as if the overnight thing --and particularly the broken mouse-- point more to a problem recovering from suspension or hibernation. What kernel version are you using...? Errors in the log...? -- "Yogi" CH Namast� Yoga Studio
Make shure you have the sleep/suspend function on your Hard drives turned OFF this caused me no end of problems on older hardware a few years ago .. hdparm -S0 /dev/hd? .. pete. -- Linux user No: 256242 Machine No: 139931 G6NJR Pete also MSA registered "Quinton 11" A Linux Only area Happy bug hunting M$ clan, The time is here to FORGET that M$ Corp ever existed the world does not NEED M$ Corp the world has NO USE for M$ Corp it is time to END M$ Corp , Play time is over folks time for action approaches at an alarming pace the death knell for M$ Copr has been sounded . Termination time is around the corner ..
peter Nikolic wrote:
On Thursday 21 Oct 2004 18:40, C Hamel wrote:
On 10:11 Thu 21 Oct , Robert A. Rawlinson wrote:
I have an older pc with an old slot II Celeron processer. It all seems ok. During the day when it goes into screen saver a small mouse movement brings it right back OK. But when it is left over night and I give it a mouse movement it comes back after a few min. with the screen seeming to vibrate and the mouse no longer will move. I can't do anything with it so I have to power down and restart it. It has an Nvidia MX-200 video card. Has anyone else run into this? Does anyone have any suggestions? Thanks Bob
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Mind you, I'm no guru. It does sound, however, as if the overnight thing --and particularly the broken mouse-- point more to a problem recovering from suspension or hibernation. What kernel version are you using...? Errors in the log...? -- "Yogi" CH Namast� Yoga Studio
Make shure you have the sleep/suspend function on your Hard drives turned OFF this caused me no end of problems on older hardware a few years ago ..
hdparm -S0 /dev/hd? ..
pete.
Thanks! I am trying it now. I will let you know tomorrow if it works. I also updated the Nvidia drivers. Bob
Robert A. Rawlinson wrote:
peter Nikolic wrote:
On Thursday 21 Oct 2004 18:40, C Hamel wrote:
On 10:11 Thu 21 Oct , Robert A. Rawlinson wrote:
I have an older pc with an old slot II Celeron processer. It all seems ok. During the day when it goes into screen saver a small mouse movement brings it right back OK. But when it is left over night and I give it a mouse movement it comes back after a few min. with the screen seeming to vibrate and the mouse no longer will move. I can't do anything with it so I have to power down and restart it. It has an Nvidia MX-200 video card. Has anyone else run into this? Does anyone have any suggestions? Thanks Bob
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Mind you, I'm no guru. It does sound, however, as if the overnight thing --and particularly the broken mouse-- point more to a problem recovering from suspension or hibernation. What kernel version are you using...? Errors in the log...? -- "Yogi" CH Namast� Yoga Studio
Make shure you have the sleep/suspend function on your Hard drives turned OFF this caused me no end of problems on older hardware a few years ago ..
hdparm -S0 /dev/hd? ..
pete.
Thanks! I am trying it now. I will let you know tomorrow if it works. I also updated the Nvidia drivers. Bob
Well those did not work. Still looking for the solution. The only things I can find in the log were about the hd and the nvidia card. The log goes on for several hours and then suddenly no new entries until I restart. Bob
Make shure you have the sleep/suspend function on your Hard drives turned OFF this caused me no end of problems on older hardware a few years ago ..
hdparm -S0 /dev/hd? ..
pete.
Thanks! I am trying it now. I will let you know tomorrow if it works. I also updated the Nvidia drivers. Bob
Well those did not work. Still looking for the solution. The only things I can find in the log were about the hd and the nvidia card. The log goes on for several hours and then suddenly no new entries until I restart. Bob
I don't have the whole thread in front of me so I'm sorry if you've already given this... Do the logs end at the same time each night? Have you ruled out a cron job or other scheduled routine such as online update? You mention hd and video card entries. Were these one time only entries or do they occur each night? Jeff
Robert A. Rawlinson wrote:
Well those did not work. Still looking for the solution. The only things I can find in the log were about the hd and the nvidia card. The log goes on for several hours and then suddenly no new entries until I restart. Bob
Perhaps it is related with some power save DPMS feature? If you use KDE, there's a place in the control center to change the minutes to standby and to suspend/off. Another option is to leave your computer in a text console and see if the same happens. e.g.: just before leaving, ctrl+alt+f2 and turn you monitor off (I don't think there is energy saving features in the text console, just blank screen) - you may argue that this could interfere with the tests; right, so try again later leaving the monitor on. -- Marcos Lazarini
C Hamel wrote:
On 10:11 Thu 21 Oct , Robert A. Rawlinson wrote:
I have an older pc with an old slot II Celeron processer. It all seems ok. During the day when it goes into screen saver a small mouse movement brings it right back OK. But when it is left over night and I give it a mouse movement it comes back after a few min. with the screen seeming to vibrate and the mouse no longer will move. I can't do anything with it so I have to power down and restart it. It has an Nvidia MX-200 video card. Has anyone else run into this? Does anyone have any suggestions? Thanks Bob
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
Mind you, I'm no guru. It does sound, however, as if the overnight thing --and particularly the broken mouse-- point more to a problem recovering from suspension or hibernation. What kernel version are you using...? Errors in the log...? -- "Yogi" CH Namasté Yoga Studio
Well I was finally able to get the log over to a win pc and had to edit to change the linefeeds to CRLF so I could send it. Here is what looks like the problem area: Oct 20 02:50:15 rawlinson kernel: Badness in pci_find_subsys at drivers/pci/search.c:167 Oct 20 02:50:15 rawlinson kernel: Call Trace: Oct 20 02:50:15 rawlinson kernel: [pci_find_subsys+202/224] pci_find_subsys+0xca/0xe0 Oct 20 02:50:15 rawlinson kernel: [<c01e016a>] pci_find_subsys+0xca/0xe0 Oct 20 02:50:15 rawlinson kernel: [pci_find_device+11/16] pci_find_device+0xb/0x10 Oct 20 02:50:15 rawlinson kernel: [<c01e018b>] pci_find_device+0xb/0x10 Oct 20 02:50:15 rawlinson kernel: [pci_find_slot+19/80] pci_find_slot+0x13/0x50 Oct 20 02:50:15 rawlinson kernel: [<c01e01a3>] pci_find_slot+0x13/0x50 Oct 20 02:50:15 rawlinson kernel: [__crc_pnp_add_card_device+69293/784293] os_pci_init_handle+0x35/0x5b [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6e37f97>] os_pci_init_handle+0x35/0x5b [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_pnp_add_card_device+175781/784293] _nv001243rm+0x1f/0x24 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6e51f8f>] _nv001243rm+0x1f/0x24 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_ethtool_op_get_tx_csum+463785/4662689] _nv000816rm+0x2f5/0x384 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6f98845>] _nv000816rm+0x2f5/0x384 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_vmalloc+108493/265229] _nv003801rm+0xd8/0x100 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6f0105c>] _nv003801rm+0xd8/0x100 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_ethtool_op_get_tx_csum+462563/4662689] _nv000809rm+0x2f/0x34 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6f9837f>] _nv000809rm+0x2f/0x34 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_ethtool_op_get_tx_csum+36316/4662689] _nv003606rm+0xe4/0x114 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6f30278>] _nv003606rm+0xe4/0x114 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_ethtool_op_get_tx_csum+35469/4662689] _nv003564rm+0x7c9/0x908 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6f2ff29>] _nv003564rm+0x7c9/0x908 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_pnp_add_card_device+276653/784293] _nv004046rm+0x3a3/0x3b0 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6e6a997>] _nv004046rm+0x3a3/0x3b0 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_ethtool_op_get_tx_csum+282007/4662689] _nv001476rm+0x1d3/0x45c [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6f6c233>] _nv001476rm+0x1d3/0x45c [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_pnp_add_card_device+186848/784293] _nv000896rm+0x4a/0x64 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6e54aca>] _nv000896rm+0x4a/0x64 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_pnp_add_card_device+193018/784293] rm_isr_bh+0xc/0x10 [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6e562e4>] rm_isr_bh+0xc/0x10 [nvidia] Oct 20 02:50:15 rawlinson kernel: [__crc_pnp_add_card_device+63603/784293] nv_kern_isr_bh+0x6/0xa [nvidia] Oct 20 02:50:15 rawlinson kernel: [<d6e3695d>] nv_kern_isr_bh+0x6/0xa [nvidia] Oct 20 02:50:15 rawlinson kernel: [tasklet_action+56/112] tasklet_action+0x38/0x70 Oct 20 02:50:15 rawlinson kernel: [<c0122f18>] tasklet_action+0x38/0x70 Oct 20 02:50:15 rawlinson kernel: [__do_softirq+67/144] __do_softirq+0x43/0x90 Oct 20 02:50:15 rawlinson kernel: [<c01231e3>] __do_softirq+0x43/0x90 Oct 20 02:50:15 rawlinson kernel: [do_softirq+38/48] do_softirq+0x26/0x30 Oct 20 02:50:15 rawlinson kernel: [<c0123256>] do_softirq+0x26/0x30 Oct 20 02:50:15 rawlinson kernel: [do_IRQ+293/416] do_IRQ+0x125/0x1a0 Oct 20 02:50:15 rawlinson kernel: [<c010a8f5>] do_IRQ+0x125/0x1a0 Oct 20 02:50:15 rawlinson kernel: [common_interrupt+24/32] common_interrupt+0x18/0x20 Oct 20 02:50:15 rawlinson kernel: [<c0108d48>] common_interrupt+0x18/0x20 This repeats from on to 30 times on a night. No particular time, in fact it has done it when I was working on it. Screen gets vertical lines it starts to shiver and the mouse freezes. The only way out is to reboot. I set to level 3 and it still does it. I tried running it in win me for a couple days and no problems. So I assume it is some driver in Suse 9.1. Thanks for any help you can offer. Bob
The Sunday 2004-10-31 at 15:09 -0700, Robert A. Rawlinson wrote:
Well I was finally able to get the log over to a win pc and had to edit to change the linefeeds to CRLF so I could send it. Here is what looks like the problem area:
Oct 20 02:50:15 rawlinson kernel: Badness in pci_find_subsys at drivers/pci/search.c:167 Oct 20 02:50:15 rawlinson kernel: Call Trace:
I think that is something for a developper to handle. -- Cheers, Carlos Robinson
Carlos E. R. wrote:
The Sunday 2004-10-31 at 15:09 -0700, Robert A. Rawlinson wrote:
Well I was finally able to get the log over to a win pc and had to edit to change the linefeeds to CRLF so I could send it. Here is what looks like the problem area:
Oct 20 02:50:15 rawlinson kernel: Badness in pci_find_subsys at drivers/pci/search.c:167 Oct 20 02:50:15 rawlinson kernel: Call Trace:
I think that is something for a developper to handle.
Well I finally gave up on the video card I had and replaced it. It seems to have fixed the problem as it has gone two nights now without a problem. Thanks for all the help I got from this list. I hope to return the favor when I have gained more knowledge. Bob
On 21-Oct-04 Robert A. Rawlinson wrote:
I have an older pc with an old slot II Celeron processer. It all seems ok. During the day when it goes into screen saver a small mouse movement brings it right back OK. But when it is left over night and I give it a mouse movement it comes back after a few min. with the screen seeming to vibrate and the mouse no longer will move. I can't do anything with it so I have to power down and restart it. It has an Nvidia MX-200 video card. Has anyone else run into this? Does anyone have any suggestions? Thanks Bob
While the sticky mouse suggests a system problem, there may
also be a monitor problem: the "vibration" suggests that it
may be worth trying a "degauss". Some monitors have a physical
"degauss" button, on others it is part of the monitor's
built-in utilities which you can access by means of some button
on the monitor casing.
If that cures the vibration then Mike Roy's suggestion of
turning the monitor off when not in use should cure that side
of it (and it's a good idea anyway).
Good luck!
Ted.
--------------------------------------------------------------------
E-Mail: (Ted Harding)
participants (7)
-
C Hamel -
Carlos E. R. -
Jeffrey Laramie -
Marcos Vinicius Lazarini -
peter Nikolic -
Robert A. Rawlinson -
Ted.Harding＠nessie.mcc.ac.uk