[opensuse] HPET and SuSE 10.3

Clive Rogers

26 Jul 2008 26 Jul '08

18:08

Hi All, I have followed and implemented the postings of lockups on this distro and number 11 and still I suffer from some form of lockup. Running an AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ with 2 gig of memory. 2 IDE hard drives, 1 IDE DVD-RW and 1 SATA DVD-RW. All this is on an ASUS M2V-MX motherboard. Running the Default Kernel 2.6.22.18-0.2. After Googling and reading the post here and still getting the lockups I thought maybe its something to do with the HPET which my other PC has in the bios and Vista won't run properly without it. I read on Wikipedia http://en.wikipedia.org/wiki/HPET that the Kernel of 2.6 also requires the HPET to be turned on in the bios. This motherboard does not have HPET. So I can not turn it on. Is anyone on the list running 10.3 or 11.0 without HPET turned on in the bios ? Is anyone running any of the above distros without HPET in the bios ? If so how are you getting around rtc-cmos which again is mentioned in the wikipedia page ? Would I be better running an older kernel that does not require the HPET ? -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Show replies by date

Anders Johansson

26 Jul 26 Jul

18:24

On Saturday 26 July 2008 20:08:54 Clive Rogers wrote:

...

Hi All,

I have followed and implemented the postings of lockups on this distro and number 11 and still I suffer from some form of lockup. Running an AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ with 2 gig of memory. 2 IDE hard drives, 1 IDE DVD-RW and 1 SATA DVD-RW. All this is on an ASUS M2V-MX motherboard. Running the Default Kernel 2.6.22.18-0.2.

After Googling and reading the post here and still getting the lockups I thought maybe its something to do with the HPET which my other PC has in the bios and Vista won't run properly without it. I read on Wikipedia

http://en.wikipedia.org/wiki/HPET

that the Kernel of 2.6 also requires the HPET to be turned on in the bios.

No, it says it *can* use HPET, if present I don't think your lockups have anything to do with that. The last post from you about a lockup that I can see on this list ("Open SuSE 10.3 still locking up") said that the system wasn't in fact locking up. You just lost keyboard & mouse. Is that still the case? Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

18:44

Anders, On Saturday 26 July 2008 19:24:34 Anders Johansson wrote:

...

On Saturday 26 July 2008 20:08:54 Clive Rogers wrote:

...
Hi All,

I have followed and implemented the postings of lockups on this distro and number 11 and still I suffer from some form of lockup. Running an AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ with 2 gig of memory. 2 IDE hard drives, 1 IDE DVD-RW and 1 SATA DVD-RW. All this is on an ASUS M2V-MX motherboard. Running the Default Kernel 2.6.22.18-0.2.

After Googling and reading the post here and still getting the lockups I thought maybe its something to do with the HPET which my other PC has in the bios and Vista won't run properly without it. I read on Wikipedia

http://en.wikipedia.org/wiki/HPET

that the Kernel of 2.6 also requires the HPET to be turned on in the bios.

No, it says it *can* use HPET, if present

I don't think your lockups have anything to do with that.

The last post from you about a lockup that I can see on this list ("Open SuSE 10.3 still locking up") said that the system wasn't in fact locking up. You just lost keyboard & mouse.

Is that still the case?

Anders

Most times yes. I get the mouse movement for a while then the clock (bottom right) stops for around 3-5 mins or so. Then everything works fine for a while. Sometimes the system is locked up tight and I have to press reset. I can find nothing in the logs to point to anything. While the system "seems" locked mail is still downloaded and the hard drive will light up. I am not running compiz although I am running the Nvidia driver for my graphics card. Geforce 7300 LE. -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Patrick Shanahan

18:53

* Clive Rogers [07-26-08 14:40]:

...

I am not running compiz although I am running the Nvidia driver for my graphics card. Geforce 7300 LE.

I have the GeForce 7300 GS. You don't say which version of the nVidia driver, I use NVIDIA-Linux-x86_64-173.14.05-pkg2.run. I have had problems somewhat similar to yours, but have had non with this driver. While your graphics may become somewhat slower, you could test that the nVidia driver was the problem by using the nv driver for a period of time, from the cl: switch2nv (as root). -- Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

19:31

On Saturday 26 July 2008 19:53:47 Patrick Shanahan wrote:

...

NVIDIA-Linux-x86_64-173.14.05-pkg2.run

I am using NVIDIA-Linux-x86_64-173.14.09_2.6.22.18_0.2-0.1 from Nvidia repository. How do you install this NVIDIA-Linux-x86_64-173.14.05-pkg2.run ? From a Konsole as root ? -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Pete Connolly

19:45

Clive Rogers wrote:

...

On Saturday 26 July 2008 19:53:47 Patrick Shanahan wrote:

...
NVIDIA-Linux-x86_64-173.14.05-pkg2.run

I am using NVIDIA-Linux-x86_64-173.14.09_2.6.22.18_0.2-0.1 from Nvidia repository.

How do you install this NVIDIA-Linux-x86_64-173.14.05-pkg2.run ? From a Konsole as root ?

Hi Clive Nearly, just save your work in the GUI, switch to a console (CTRL-ALT-F1) and log in as root, then do an 'init 3' followed by 'sh NVIDIA-Linux-x86_64-173.14.05-pkg2.run' and follow the instructions. Afterwards, just 'init 5' again and you should be good to go. Cheers Pete -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

20:08

On Saturday 26 July 2008 21:45:42 Pete Connolly wrote:

...

Clive Rogers wrote:

...
On Saturday 26 July 2008 19:53:47 Patrick Shanahan wrote:

...
NVIDIA-Linux-x86_64-173.14.05-pkg2.run

I am using NVIDIA-Linux-x86_64-173.14.09_2.6.22.18_0.2-0.1 from Nvidia repository.

How do you install this NVIDIA-Linux-x86_64-173.14.05-pkg2.run ? From a Konsole as root ?

Hi Clive

Nearly, just save your work in the GUI, switch to a console (CTRL-ALT-F1) and log in as root, then do an 'init 3' followed by 'sh

NVIDIA-Linux-x86_64-173.14.05-pkg2.run' and follow the instructions. Afterwards, just 'init 5' again and you should be good to go.

Yes, but please don't. First of all, overwriting the rpm by the .sh installer is not a good idea in general without first uninstalling the rpm And secondly, the .09 driver is an improvement over the .05 Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

22:11

Thank you for all the input people. I still have not had a "lockup" or screen hangup. Going to leave the PC on over night and see what happens in the morning. -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

19:40

On Saturday 26 July 2008 20:44:22 Clive Rogers wrote:

...

Anders,

On Saturday 26 July 2008 19:24:34 Anders Johansson wrote:

...
On Saturday 26 July 2008 20:08:54 Clive Rogers wrote:

...
Hi All,

I have followed and implemented the postings of lockups on this distro and number 11 and still I suffer from some form of lockup. Running an AMD Athlon(tm) 64 X2 Dual Core Processor 4800+ with 2 gig of memory. 2 IDE hard drives, 1 IDE DVD-RW and 1 SATA DVD-RW. All this is on an ASUS M2V-MX motherboard. Running the Default Kernel 2.6.22.18-0.2.

After Googling and reading the post here and still getting the lockups I thought maybe its something to do with the HPET which my other PC has in the bios and Vista won't run properly without it. I read on Wikipedia

http://en.wikipedia.org/wiki/HPET

that the Kernel of 2.6 also requires the HPET to be turned on in the bios.

No, it says it *can* use HPET, if present

I don't think your lockups have anything to do with that.

The last post from you about a lockup that I can see on this list ("Open SuSE 10.3 still locking up") said that the system wasn't in fact locking up. You just lost keyboard & mouse.

Is that still the case?

Anders

Most times yes. I get the mouse movement for a while then the clock (bottom right) stops for around 3-5 mins or so. Then everything works fine for a while.

Sometimes the system is locked up tight and I have to press reset. I can find nothing in the logs to point to anything. While the system "seems" locked mail is still downloaded and the hard drive will light up.

OK, so it seems your system is busy working on something. Do you by any chance have a second system you could use, to ssh into this one, to see what exactly is going on? Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

20:32

Anders,

...

...
...
Anders

Most times yes. I get the mouse movement for a while then the clock (bottom right) stops for around 3-5 mins or so. Then everything works fine for a while.

Sometimes the system is locked up tight and I have to press reset. I can find nothing in the logs to point to anything. While the system "seems" locked mail is still downloaded and the hard drive will light up.

OK, so it seems your system is busy working on something.

Do you by any chance have a second system you could use, to ssh into this one, to see what exactly is going on?

Anders

I have a second system with Vista installed. I would not have a clue as to how to use the ssh. I did come across a couple of web pages that also said with instability problem use CPUFREQ=no bios=nomsi in the boot loader (lilo in my case) I have installed these two and so far no lockups. I also tried to install the NVIDIA-Linux-x86_64-173.14.05-pkg2.run but I got my system is running the 32 bit version and the scrip exited. If this is the case then why did Yast2 install the NVIDIA-Linux-x86_64-173.14.09_2.6.22.18_0.2-0.1 from the Nvidia repository ? -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

20:44

On Saturday 26 July 2008 22:32:18 Clive Rogers wrote:

...

I have a second system with Vista installed. I would not have a clue as to how to use the ssh.

Install PuTTY (http://www.chiark.greenend.org.uk/~sgtatham/putty/) Test it, to make sure it works, then - the next time your linux box hangs - log in and run "top" to see what is consuming CPU

...

I did come across a couple of web pages that also said with instability problem use CPUFREQ=no bios=nomsi in the boot loader (lilo in my case) I have installed these two and so far no lockups.

I also tried to install the NVIDIA-Linux-x86_64-173.14.05-pkg2.run but I got my system is running the 32 bit version and the scrip exited. If this is the case then why did Yast2 install the NVIDIA-Linux-x86_64-173.14.09_2.6.22.18_0.2-0.1 from the Nvidia repository ?

I don't know, but please don't downgrade your driver with the shell script. Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

20:55

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-07-26 at 21:32 +0100, Clive Rogers wrote:

...

I have a second system with Vista installed. I would not have a clue as to how to use the ssh.

Install putty. It used to come with the suse DVD (pay version). Or download it from somewhere, it is easy to find. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIi48utTMYHG2NR9URArBDAJ4jaiNTG4xYyNvd7ALGnr1Qy0DQcgCgknz4 Z0/kLGQqq+RWXndLNjvfJ/w= =+JXS -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

20:51

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Saturday 2008-07-26 at 19:44 +0100, Clive Rogers wrote: ...

...

I can find nothing in the logs to point to anything. While the system "seems" locked mail is still downloaded and the hard drive will light up.

Thus your system is not locked: it is only the graphic session that is locked, or perhaps the keyboard/mouse. If that's the case, probably nothing you try tuning the kernel will help. Your best bet is the nvidia commercial driver, and the best thing is NOT using the commercial driver at all - at least in order to find out if it is the culprit. Install instead the "nv" open driver. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIi45vtTMYHG2NR9URAnYoAJ97bit7TXHTYSJIVj3RvePqM3OmXACfQDaJ U1BEc+9cZCfmLBdKzQW59c0= =KO// -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John Andersen

27 Jul 27 Jul

02:02

On Sat, Jul 26, 2008 at 11:44 AM, Clive Rogers wrote:

...

...
No, it says it *can* use HPET, if present

I don't think your lockups have anything to do with that.

The last post from you about a lockup that I can see on this list ("Open SuSE 10.3 still locking up") said that the system wasn't in fact locking up. You just lost keyboard & mouse.

Is that still the case?

Anders

Most times yes. I get the mouse movement for a while then the clock (bottom right) stops for around 3-5 mins or so. Then everything works fine for a while.

There is always the nohpet boot parameter you can try if you think it is related... -- ----------JSA--------- There are 10 kinds of people in this world, those that can read binary and those that can't. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

10:05

New subject: [opensuse] HPET and SuSE 10.3 Update

I left the computer on over night and I have not had a "lockup" This morning I was going through the motherboard booklet and could find nothing about installing Vista or being Vista ready. I installed Vista and it installed OK, although it does write all over the mbr where the grub/lilo loaders are installed to. This was easily fixed so that I have a dual boot system. This proves I think that this motherboard is hpet ready so Anders and a couple of others were correct in there thinking that hpet is not at fault. On 5 other computers that my friends own they could not install Vista without it playing up as their motherboards were too old and don't have hpet which from what I have read Vista needs for some internal workings. That brings me back to whether its the Nvidia drivers. When I first installed SuSE 10.3 I didn't have the PCIE GeForce NVidia card but had onboard graphics. This was the DeltaChrome 9 which did not have any real drivers to start with and SuSE installed some drivers and the lockups started. So I bought the GeForce NVidia 7300 LE. SuSE correctly saw the card and installed the nv card drivers. This is where the so called lockups were not so fierce or so often. But even so 10 lockups a day is not right. I may have to backdown to one of the 173.14.05 drivers just to stop this from happening. I can't get any work done at this rate. Just had a 2 minute lockup. Top showed nothing as it stopped working during the lockup. Just checked the /var/log/messages and nothing is there during the "lockup" time I noted from my digital clock. -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

10:17

New subject: [opensuse] HPET and SuSE 10.3 Update

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-07-27 at 11:05 +0100, Clive Rogers wrote:

...

Just had a 2 minute lockup. Top showed nothing as it stopped working during the lockup. Just checked the /var/log/messages and nothing is there during the "lockup" time I noted from my digital clock.

Try sshing from another computer. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIjEtJtTMYHG2NR9URAk4sAJ0cDWeyaBUoHrHRIgKMV5Df9FjioQCcDfxU AUCXPLEIevJpg3xl+l0cdio= =5XKK -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Anders Johansson

11:37

New subject: [opensuse] HPET and SuSE 10.3 Update

On Sunday 27 July 2008 12:05:05 Clive Rogers wrote:

...

I may have to backdown to one of the 173.14.05 drivers

Please don't do that. There is absolutely no reason to.

...

Just had a 2 minute lockup. Top showed nothing as it stopped working during the lockup.

Did you try ssh using PuTTY from your vista machine? Anders -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

11:59

New subject: [opensuse] HPET and SuSE 10.3 Update

Hello Anders, On Sunday 27 July 2008 12:37:04 Anders Johansson wrote:

...

On Sunday 27 July 2008 12:05:05 Clive Rogers wrote:

...
I may have to backdown to one of the 173.14.05 drivers

Please don't do that. There is absolutely no reason to.

...
Just had a 2 minute lockup. Top showed nothing as it stopped working during the lockup.

Did you try ssh using PuTTY from your vista machine?

Anders

Yes I got PuTTY on the Vista machine. I have ssh'd (is that the correct term ?) into the SuSE machine and now am waiting for a lockup to occur with top running under a root login. Is that the correct utility to run for this purpose ? So far the SuSE machine has behaved itself. I have even removed the CPUFREQ=no bios=nomsi from /etc/lilo.conf and rebooted the pc to see if I can force a "lockup" I will let you know if and when something happens. -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

12:04

New subject: [opensuse] HPET and SuSE 10.3 Update

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Sunday 2008-07-27 at 12:59 +0100, Clive Rogers wrote:

...

Yes I got PuTTY on the Vista machine. I have ssh'd (is that the correct term ?) into the SuSE machine and now am waiting for a lockup to occur with top running under a root login.

Is that the correct utility to run for this purpose ?

Yes. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIjGRetTMYHG2NR9URAofzAJ4y+H1/jSLl7JL4vPkBcipzjpnXVwCfemTl QzD1Z1U5HH8gdrSDxlJcqFc= =odOJ -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

28 Jul 28 Jul

10:01

New subject: [opensuse] HPET and SuSE 10.3 Update

On Sunday 27 July 2008 13:04:27 Carlos E. R. wrote:

...

The Sunday 2008-07-27 at 12:59 +0100, Clive Rogers wrote:

...
Yes I got PuTTY on the Vista machine. I have ssh'd (is that the correct term ?) into the SuSE machine and now am waiting for a lockup to occur with top running under a root login.

Is that the correct utility to run for this purpose ?

Yes.

-- Cheers, Carlos E. R.

Computer was again left on over night and no "lockup" Then at 10.23 am and 10.24 am I had a lockup. This is the last two lines in /var/log/messages. There was nothing before this from 01.10 on the 28th. Then nothing again until 10.32 when I issued the reboot from the ssh from my other pc. Jul 28 10:05:15 cos1 smartd[4017]: Device: /dev/sda, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 249 to 250 Jul 28 10:05:15 cos1 smartd[4017]: Device: /dev/sdb, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 244 to 245 Here I have put 2 screen captures from Vista of Top during the "lockup" http://homepage.ntlworld.com/c.rogers/lts/ I can not make head nor tail of this so if any one can please enlighten me. During this time I had no keyboard or mouse but I could issue sax2 over the ssh and my screen changed to the test screen for resizing etc. From this I assume its not my graphics card or hpet but something to do with loosing mouse and keyboard input ? -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

11:22

New subject: [opensuse] HPET and SuSE 10.3 Update

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-07-28 at 11:01 +0100, Clive Rogers wrote:

...

Then at 10.23 am and 10.24 am I had a lockup.

This is the last two lines in /var/log/messages. There was nothing before this from 01.10 on the 28th. Then nothing again until 10.32 when I issued the reboot from the ssh from my other pc.

Jul 28 10:05:15 cos1 smartd[4017]: Device: /dev/sda, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 249 to 250 Jul 28 10:05:15 cos1 smartd[4017]: Device: /dev/sdb, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 244 to 245

Not related.

...

Here I have put 2 screen captures from Vista of Top during the "lockup" http://homepage.ntlworld.com/c.rogers/lts/

Nothing there, except that it is not busy.

...

I can not make head nor tail of this so if any one can please enlighten me. During this time I had no keyboard or mouse but I could issue sax2 over the ssh and my screen changed to the test screen for resizing etc.

You could simply have killed the session from remote.

...

From this I assume its not my graphics card or hpet but something to do with loosing mouse and keyboard input ?

Maybe. Could be. You could look at the X session log. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIjavitTMYHG2NR9URAvfvAJ4lOFM+Mtfcp/ogo7LZxyDSKba0sACdG0E4 LYMzkZasR911jlMcndTB4Y0= =8hjX -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

11:53

New subject: [opensuse] HPET and SuSE 10.3 Update

Thanks Carlos, On Monday 28 July 2008 12:22:07 Carlos E. R. wrote:

...

The Monday 2008-07-28 at 11:01 +0100, Clive Rogers wrote:

...
Then at 10.23 am and 10.24 am I had a lockup.

This is the last two lines in /var/log/messages. There was nothing before this from 01.10 on the 28th. Then nothing again until 10.32 when I issued the reboot from the ssh from my other pc.

Jul 28 10:05:15 cos1 smartd[4017]: Device: /dev/sda, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 249 to 250 Jul 28 10:05:15 cos1 smartd[4017]: Device: /dev/sdb, SMART Prefailure Attribute: 8 Seek_Time_Performance changed from 244 to 245

Not related.

...
Here I have put 2 screen captures from Vista of Top during the "lockup" http://homepage.ntlworld.com/c.rogers/lts/

Nothing there, except that it is not busy.

...
I can not make head nor tail of this so if any one can please enlighten me. During this time I had no keyboard or mouse but I could issue sax2 over the ssh and my screen changed to the test screen for resizing etc.

You could simply have killed the session from remote.

...
From this I assume its not my graphics card or hpet but something to do with loosing mouse and keyboard input ?

Maybe. Could be.

You could look at the X session log.

-- Cheers, Carlos E. R.

Here is my .xsession-errors from my home directory. /etc/X11/xim: Checking whether an input method should be started. /etc/X11/xim: user environment variable LANG=en_GB.UTF-8 sourcing /etc/sysconfig/language to get the value of INPUT_METHOD INPUT_METHOD is not set or empty (no user selected input method). Trying to start a default input method for the locale en_GB.UTF-8 ... There is no default input method for the current locale. startkde: Starting up... kbuildsycoca running... DCOP Cleaning up dead connections. QObject::connect: No such signal Kicker::settingsChanged(SettingsCategory) QObject::connect: (sender name: 'kicker') QObject::connect: (receiver name: 'animtt') sh: jackd: command not found akode: Guessed format: xiph KNotify::playTimeout kbuildsycoca running... Reusing existing ksycoca KNotify::playTimeout KNotify::playTimeout KNotify::playTimeout KNotify::playTimeout KNotify::playTimeout KNotify::playTimeout gpgmeplug checkMessageSignature status flags: 80 QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x260007f QPainter::begin: Cannot paint null pixmap QLayout "unnamed" added to QWidget "unnamed", which already has a layout sh: jackd: command not found akode: Guessed format: xiph KNotify::playTimeout X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3001e75 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3001e75 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3001e75 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3001e75 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3001e75 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3001e75 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3000014 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3000014 Loading image... Loading image... Loading image... Loading image... Loading image... KNotify::playTimeout X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c03a82 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c00132 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c000c0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c003ee X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2c00463 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2c00463 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c00463 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30005bd X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30008ba X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x300099d X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c000c0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c00132 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c0027b QGDict::hashKeyString: Invalid null key QGDict::hashKeyString: Invalid null key X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x260014e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x260014e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x260014e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x260014e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x260014e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3800037 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3800037 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3800037 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3800037 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3800037 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3800037 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x380001e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x380001e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x380001e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x380001e X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x380001e Launched ok, pid = 5900 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3200006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3200006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3200006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3200006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3200006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c00003 gpgmeplug checkMessageSignature status flags: 80 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3000003 4307:error:0B07C065:lib(11):func(124):reason(101):x509_lu.c:348: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2a00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2a00006 4307:error:0B07C065:lib(11):func(124):reason(101):x509_lu.c:348: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3000006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3000006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3000006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3000006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3000006 Does this make any kind of sense ? Below is a paste of the imput section from my /etc/X11/xorg.conf Section "ServerFlags" Option "AllowMouseOpenFail" "on" EndSection Section "InputDevice" Driver "kbd" Identifier "Keyboard[0]" Option "Protocol" "Standard" Option "XkbLayout" "gb" Option "XkbModel" "microsoftpro" Option "XkbRules" "xfree86" EndSection Section "InputDevice" Driver "mouse" Identifier "Mouse[1]" Option "Buttons" "9" Option "Device" "/dev/input/mice" Option "Name" "ImExPS/2 Generic Explorer Mouse" Option "Protocol" "explorerps/2" Option "Vendor" "Sysp" Option "ZAxisMapping" "4 5" EndSection Section "Monitor" Option "CalcAlgorithm" "XServerPool" DisplaySize 310 230 HorizSync 30-72 Identifier "Monitor[0]" ModelName "AOC SPECTRUM 7F" Option "DPMS" VendorName "AOC" VertRefresh 43-160 UseModes "Modes[0]" EndSection Can anyone see if anything is wrong here ? -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

12:27

New subject: [opensuse] HPET and SuSE 10.3 Update

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Monday 2008-07-28 at 12:53 +0100, Clive Rogers wrote:

...

...
You could look at the X session log.

Here is my .xsession-errors from my home directory.

The one while locked? The log is overwritten when you start another session.

...

startkde: Starting up... kbuildsycoca running... ...

...

Resource id: 0x3000006

Does this make any kind of sense ?

No... Try using another desktop. You are using kde, try gnome or any other you have; if it doesn't lock, then it is kde related. You could try another user, a newly created one. Or perhaps you can try swapping the keyboard/mice. I think this is getting too weird... Perhaps you should open a bugzilla. The system itself is not locking, you can ssh-in from outside and execute programs, so it does not seems hardware, it is software. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIjbtFtTMYHG2NR9URAg4aAJ9JlX4YxgmUksBstKeGV9StJOYISACfePgg +Bqho/uVF0MCao2oxPZjS1k= =yzvR -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

29 Jul 29 Jul

19:25

New subject: [opensuse] SuSE10.3 mouse and keyboard still locking up

I managed to ssh into the SuSE box and get the .xsession-errors from my home directory. The so called lockup started at 20.03 and finished at 20.14. This file is from the 20.14 after I got the keyboard and mouse back. Can anyone see in this file what is causing these holds on the mouse and keyboard. This mouse and keyboard are wireless and the wireless receiver is plugged into the PS2 ports. /etc/X11/xim: Checking whether an input method should be started. /etc/X11/xim: user environment variable LANG=en_GB.UTF-8 sourcing /etc/sysconfig/language to get the value of INPUT_METHOD INPUT_METHOD is not set or empty (no user selected input method). Trying to start a default input method for the locale en_GB.UTF-8 ... There is no default input method for the current locale. startkde: Starting up... kbuildsycoca running... QObject::connect: No such signal Kicker::settingsChanged(SettingsCategory) QObject::connect: (sender name: 'kicker') QObject::connect: (receiver name: 'animtt') sh: jackd: command not found akode: Guessed format: xiph KNotify::playTimeout kbuildsycoca running... Reusing existing ksycoca KNotify::playTimeout KNotify::playTimeout KNotify::playTimeout KNotify::playTimeout Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Adobe Flash Player: gtk_clipboard_get(GDK_SELECTION_PRIMARY); failed. Trying to call gtk_init(0,0); Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 KNotify::playTimeout KNotify::playTimeout KNotify::playTimeout Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 (<unknown>:4329): GLib-GObject-WARNING **: IA__g_object_newv: construct property "bits-per-sample" for object `GdkPixbuf' can't be set twice (<unknown>:4329): GLib-GObject-WARNING **: IA__g_object_newv: object class `GdkPixbuf' has no property named `pixels' (<unknown>:4329): GLib-GObject-WARNING **: gtype.c:3339: type id `0' is invalid (<unknown>:4329): GLib-GObject-WARNING **: can't peek value table for type `<invalid>' which is not currently referenced (<unknown>:4329): GLib-GObject-WARNING **: gvalue.c:96: cannot initialize GValue with type `(null)', this type has no GTypeValueTable implementation KCrash: Application 'nspluginviewer' crashing... X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2a00006 gpgmeplug checkMessageSignature status flags: 80 gpgmeplug checkMessageSignature status flags: 80 Load smb config files from /dev/null Loaded services file OK. Server role: ROLE_STANDALONE QInputContext: cannot create input context for non-toplevel widgets QInputContext: cannot create input context for non-toplevel widgets X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2200615 Load smb config files from /dev/null Loaded services file OK. Server role: ROLE_STANDALONE QInputContext: cannot create input context for non-toplevel widgets QInputContext: cannot create input context for non-toplevel widgets Load smb config files from /dev/null Loaded services file OK. Server role: ROLE_STANDALONE X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c00006 QInputContext: cannot create input context for non-toplevel widgets QInputContext: cannot create input context for non-toplevel widgets X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2c00009 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2c00009 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2c00009 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c00009 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3000001 4405:error:0B07C065:lib(11):func(124):reason(101):x509_lu.c:348: X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2201186 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2201186 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2201186 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2201186 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2201186 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2201186 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3200002 QLayout "unnamed" added to QWidget "unnamed", which already has a layout QLayout "unnamed" added to QWidget "unnamed", which already has a layout QLayout "unnamed" added to QWidget "unnamed", which already has a layout QLayout "unnamed" added to QWidget "unnamed", which already has a layout QLayout "unnamed" added to QWidget "unnamed", which already has a layout Grabbing the mouse failed with "GrabNotViewable" Grabbing the mouse failed with "GrabNotViewable" Grabbing the mouse failed with "GrabNotViewable" Grabbing the mouse failed with "GrabNotViewable" Grabbing the mouse failed with "GrabNotViewable" Grabbing the mouse failed with "GrabNotViewable" QLayout "unnamed" added to QWidget "unnamed", which already has a layout X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3002e37 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3002e37 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3002e37 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3002e37 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3002e37 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3002e37 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3002f0a X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3002f25 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003174 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003174 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003174 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003174 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003174 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003174 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x300322b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x300322b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x300322b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x300322b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30033f9 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30034d0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30034d0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30034d0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30034d0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30034d0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30034d0 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30036f3 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003988 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30039a7 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003a5f X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003b75 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003c31 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003ce7 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003dba X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003dba X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003dba X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003dba X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003dba X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003dba X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003e89 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003e89 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003e89 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003e89 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3003e89 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003e89 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3003fec X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x300421b X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30042f6 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30042f6 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30042f6 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30042f6 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30042f6 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30042f6 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30043be X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30043be X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30043be X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30043be X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x30043be X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30043be X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004486 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004486 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004486 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004486 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004486 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3004486 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004572 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004572 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004572 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3004572 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3004572 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3004648 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x30049ae X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3004a8c X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3004c47 QLayout "unnamed" added to QWidget "unnamed", which already has a layout QLayout "unnamed" added to QWidget "unnamed", which already has a layout Grabbing the mouse failed with "GrabNotViewable" Grabbing the mouse failed with "GrabNotViewable" QLayout "unnamed" added to QWidget "unnamed", which already has a layout X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006752 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006752 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006752 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006752 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006aa5 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006adb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006adb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006adb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006adb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006adb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006adb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006bad X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006c5d X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006c5d X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006c5d X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006c5d X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006c5d X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006c5d X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006d15 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006d15 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006d15 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006d15 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006d15 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006d15 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006dcb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006dcb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006dcb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006dcb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006dcb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x3006dcb X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006e88 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006f40 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3006ffa X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x1e00068 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Flash Player: Warning: environment variable G_FILENAME_ENCODING is set and is not UTF-8 Launched ok, pid = 6677 Launched ok, pid = 6792 /usr/share/gimp/2.0/themes/Default/gtkrc:24: Unable to locate image file in pixmap_path: "images/stock-error-64.png" /usr/share/gimp/2.0/themes/Default/gtkrc:28: Unable to locate image file in pixmap_path: "images/stock-info-64.png" /usr/share/gimp/2.0/themes/Default/gtkrc:32: Unable to locate image file in pixmap_path: "images/stock-question-64.png" /usr/share/gimp/2.0/themes/Default/gtkrc:36: Unable to locate image file in pixmap_path: "images/stock-warning-64.png" /usr/share/gimp/2.0/themes/Default/gtkrc:24: Unable to locate image file in pixmap_path: "images/stock-error-64.png" /usr/share/gimp/2.0/themes/Default/gtkrc:28: Unable to locate image file in pixmap_path: "images/stock-info-64.png" /usr/share/gimp/2.0/themes/Default/gtkrc:32: Unable to locate image file in pixmap_path: "images/stock-question-64.png" /usr/share/gimp/2.0/themes/Default/gtkrc:36: Unable to locate image file in pixmap_path: "images/stock-warning-64.png" X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3800863 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x38006be X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x380072a Found dcraw version: 8.60 QFile::open: No file name specified QFile::open: No file name specified QDate::setYMD: Invalid date 0000-00-00 QDate::setYMD: Invalid date 0000-00-00 QDate::setYMD: Invalid date 0000-00-00 QDate::setYMD: Invalid date 0000-00-00 QDate::setYMD: Invalid date 0000-00-00 QDate::setYMD: Invalid date 0000-00-00 QClipboard::setData: Cannot set X11 selection owner for PRIMARY Launched ok, pid = 16636 sh: jackd: command not found akode: Guessed format: xiph KNotify::playTimeout QObject::connect: Cannot connect (null)::destroyed( QObject* ) to KMReaderMainWin::slotFolderRemoved( QObject* ) KNotify::playTimeout sh: jackd: command not found akode: Guessed format: xiph KNotify::playTimeout KNotify::playTimeout QComboBox::text: (KFileDialog::filterwidget) Index 0 out of range QComboBox::text: (KFileDialog::filterwidget) Index 0 out of range X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x1a0e614 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2c00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2c00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 20 Minor opcode: 0 Resource id: 0x2c00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x2c00006 X Error: BadWindow (invalid Window parameter) 3 Major opcode: 19 Minor opcode: 0 Resource id: 0x3600006 -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

23:51

New subject: [opensuse] SuSE10.3 mouse and keyboard still locking up

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Tuesday 2008-07-29 at 20:25 +0100, Clive Rogers wrote:

...

I managed to ssh into the SuSE box and get the .xsession-errors from my home directory. The so called lockup started at 20.03 and finished at 20.14. This file is from the 20.14 after I got the keyboard and mouse back.

Can anyone see in this file what is causing these holds on the mouse and keyboard. This mouse and keyboard are wireless and the wireless receiver is plugged into the PS2 ports.

Wireless? It could be radio interference... I don't know if that thing can log anything somewhere else Perhaps the kernel log, increasing verbosity. I would try another keyboard, preferable by wire. No, I don't see anything in the log... - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIj60ZtTMYHG2NR9URAp0lAKCTlWzK/kETN8g54RR4edGewn4BJwCfcJ1C W9eSVxTpfxNkzfTguAvGd94= =BgDb -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

31 Jul 31 Jul

08:39

New subject: [opensuse] SuSE10.3 mouse and keyboard still locking up

On Wednesday 30 July 2008 00:51:50 Carlos E. R. wrote:

...

The Tuesday 2008-07-29 at 20:25 +0100, Clive Rogers wrote:

...
I managed to ssh into the SuSE box and get the .xsession-errors from my home directory. The so called lockup started at 20.03 and finished at 20.14. This file is from the 20.14 after I got the keyboard and mouse back.

Can anyone see in this file what is causing these holds on the mouse and keyboard. This mouse and keyboard are wireless and the wireless receiver is plugged into the PS2 ports.

Wireless? It could be radio interference... I don't know if that thing can log anything somewhere else Perhaps the kernel log, increasing verbosity.

I would try another keyboard, preferable by wire.

No, I don't see anything in the log...

-- Cheers, Carlos E. R.

I turned off the wireless router last night and have not had a "lockup" since. I don't know if older wireless mouse and keyboard (some 8 years old) get any kind of interference from the newer wireless gear. I also have bluetooth on my other PC but again I am unsure if this would interfear with wireless mouse and keyboard from 7 or 8 years ago. Anyone got any experience of this kind of playing up of wireless technology ? I have also now remembered that on my laptop running XP Home/Kubuntu dual boot system my mouse pointer would jump to one of the corners every now and then. This would happen when you least expect it. With my wired mouse it would not happen. So this is 2 PC's that have a weird problem. Is this some type of RF interference again ? -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

John Andersen

09:03

New subject: [opensuse] SuSE10.3 mouse and keyboard still locking up

On Thu, Jul 31, 2008 at 1:39 AM, Clive Rogers wrote:

...

I have also now remembered that on my laptop running XP Home/Kubuntu dual boot system my mouse pointer would jump to one of the corners every now and then. This would happen when you least expect it. With my wired mouse it would not happen. So this is 2 PC's that have a weird problem.

The jumping is something I have seen before with early optical mice. But it was mostly an optical problem, not a radio one. Wood grain desktops seem to induce it a lot, printed pages too. A blank sheet of white paper seems to be the best for these older mice. I also remember some interrupt problems which occasionally hurt all USB mice, but that was back in the Suse 8.0 days IIRC. As to the router, yes, I think it could be a problem for your wireless mouse, as could your wireless telephone (not cell phone) and anything else that shares that bandwidth. You can try setting the router to a different channel or lie to it and tell it you are in India or Japan or somewhere that has different band allocations. In the end, you wanted a new keyboard anyway... -- ----------JSA--------- There are 10 kinds of people in this world, those that can read binary and those that can't. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

17:57

New subject: [opensuse] SuSE10.3 mouse and keyboard still locking up

John, On Thursday 31 July 2008 10:03:25 John Andersen wrote:

...

On Thu, Jul 31, 2008 at 1:39 AM, Clive Rogers wrote:

...
I have also now remembered that on my laptop running XP Home/Kubuntu dual boot system my mouse pointer would jump to one of the corners every now and then. This would happen when you least expect it. With my wired mouse it would not happen. So this is 2 PC's that have a weird problem.

The jumping is something I have seen before with early optical mice. But it was mostly an optical problem, not a radio one. Wood grain desktops seem to induce it a lot, printed pages too. A blank sheet of white paper seems to be the best for these older mice.

Yes I use a blank mouse mat now and have done for a while on my SuSE PC. The laptop I did not think to get a blank mouse mat for it but will asap.

...

I also remember some interrupt problems which occasionally hurt all USB mice, but that was back in the Suse 8.0 days IIRC.

As to the router, yes, I think it could be a problem for your wireless mouse, as could your wireless telephone (not cell phone) and anything else that shares that bandwidth. You can try setting the router to a different channel or lie to it and tell it you are in India or Japan or somewhere that has different band allocations.

Thanks for that idea. I will try changing the country and see if that stops the interference.

...

In the end, you wanted a new keyboard anyway...

My old keyboard is like your favourite pillow. Got to have that comfort zone so to speak. I have tried a new keyboard and its not the same feel or touch. Now back on my old keyboard having found for the time being some form of solution to the so called lockups. -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

10:23

New subject: [opensuse] SuSE10.3 mouse and keyboard still locking up

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-ID: The Thursday 2008-07-31 at 09:39 +0100, Clive Rogers wrote:

...

I turned off the wireless router last night and have not had a "lockup" since.

Ha! Funny.

...

I don't know if older wireless mouse and keyboard (some 8 years old) get any kind of interference from the newer wireless gear.

Could be...

...

I also have bluetooth on my other PC but again I am unsure if this would interfear with wireless mouse and keyboard from 7 or 8 years ago.

The only way to guess is to get the the frequency used from the data sheets. If they are close, or perhaps one double of the other, then there are chances. If one of them acts up when the other one is activated, then yes, you have got interferences. That's the proof. Real proof would require some expensive equipment.

...

Anyone got any experience of this kind of playing up of wireless technology ?

I'm supposedly a telecommunications chap, but I have always distrusted wireless technology and never use it, unless there is no alternative. Haven't you read a sticker on equipment saying something like the device will not produce harmful interference and must accept interference from others, or something of the sort? Well, you have it...

...

I have also now remembered that on my laptop running XP Home/Kubuntu dual boot system my mouse pointer would jump to one of the corners every now and then. This would happen when you least expect it. With my wired mouse it would not happen. So this is 2 PC's that have a weird problem.

Is this some type of RF interference again ?

Can be that, or can be the optical problem John mentions. - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIkZKWtTMYHG2NR9URAurOAJ9k2mbNdJHJjnDMOGxUks/YBmwqqQCeLd+r lWJrMKUyvkD8mZzwZtdez5o= =8kU3 -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Clive Rogers

17:49

New subject: [opensuse] SuSE10.3 mouse and keyboard still locking up

On Thursday 31 July 2008 11:23:17 Carlos E. R. wrote:

...

Content-ID: <snip> I'm supposedly a telecommunications chap, but I have always distrusted wireless technology and never use it, unless there is no alternative.

Haven't you read a sticker on equipment saying something like the device will not produce harmful interference and must accept interference from others, or something of the sort? Well, you have it...

I have read this on many occasions and I must admit I would not know if radio frequence's interfere or not. They are not supposed to as they all have passed the tests.

...

...
I have also now remembered that on my laptop running XP Home/Kubuntu dual boot system my mouse pointer would jump to one of the corners every now and then. This would happen when you least expect it. With my wired mouse it would not happen. So this is 2 PC's that have a weird problem.

Is this some type of RF interference again ?

Can be that, or can be the optical problem John mentions.

-- Cheers, Carlos E. R.

Thanks for your input Carlos. I will have to keep a close eye on things and do some research now that I am getting close to solving (or should I say hopefully getting close) this issue. Will let you know how things go over the next few days. -- Clive. http://homepage.ntlworld.com/c.rogers/ Fighting for darker skies. From 52:26:29ºN 01:27:46ºW (Coventry, UK) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

Carlos E. R.

19:08

New subject: [opensuse] SuSE10.3 mouse and keyboard still locking up

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The Thursday 2008-07-31 at 18:49 +0100, Clive Rogers wrote:

...

...
Haven't you read a sticker on equipment saying something like the device will not produce harmful interference and must accept interference from others, or something of the sort? Well, you have it...

I have read this on many occasions and I must admit I would not know if radio frequence's interfere or not. They are not supposed to as they all have passed the tests.

It doesn't really mean that the equipment will never interfere. It is impossible to guarantee that for ever. If your router is suspect, before changing the country simple change the channel. It might also be possible to change the channel used by the keyboard/mouse. If you change the country and you happen to transmit in a frequency that is reserved for something else and you interfere with somebody else's equipment, then the may fine you.

...

Thanks for your input Carlos. I will have to keep a close eye on things and do some research now that I am getting close to solving (or should I say hopefully getting close) this issue.

Will let you know how things go over the next few days.

Ok. This is one to save for the record - who would have guessed the culprit at the beginning? :-) - -- Cheers, Carlos E. R. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.4-svn0 (GNU/Linux) iD8DBQFIkg22tTMYHG2NR9URAobeAJ9vwAV8j6+pxCIQBeeqZaXyX1aNfwCeIGA9 ENfXqD4YwjnbCVRF2QW8l0E= =T0db -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org

5748

Age (days ago)

5753

Last active (days ago)

List overview

Download

30 comments

6 participants

participants (6)

Anders Johansson
Carlos E. R.
Clive Rogers
John Andersen
Patrick Shanahan
Pete Connolly