Page 1 of 3 123 LastLast
Results 1 to 10 of 24

Thread: Pointer device locks up

  1. #1

    Question Pointer device locks up

    Hello again.

    Let's see -- I'm running Tumbleweed on an older (32-bit) dual cpu (2 x Intel Pentium 4, 2.40 GHz) processor. OpenSuse Tumbleweed 20171218, KDE Plasma 5.11.4, KDE Frameworks 5.40.0, Qt 5.9.3, Kernel 4.14.6-1-default. This problem arose about two or three days ago (shortly after the latest automatic update). Oh, yeah -- my mouse is a standard PS/2 2-button dealie, connected to the 6-pin PS/2 port. The keyboard uses a similar connection.

    Anyway, every once in a while my pointer device / mouse gets "stuck" -- the cursor stops at a particular point on the screen, and no amount of moving the mouse around will get it free. Sometimes I'm able to use keyboard navigation to shut down a few application programs (like Alt-f, then Quit). Sometimes that also fails. The only way I can get around this is to reboot. Most of the time I can use Alt-Ctrl-F1 to get to the terminal interface, log in as root, and do an orderly shutdown. Other times I have to use the reset button (this is messy, and often means I have to boot up three times before everything works right: once to get past an error message about "Invalid PTCI data", once to get the system up with the mouse still frozen but with the keyboard operational, and the third time I can do a clean boot after a clean shutdown).

    This problem arises in any one of several applications, so I suspect a bug in the OS (it's as if an interrupt service routine stops working). I'm not certain this is the appropriate forum, but couldn't find a better one.

    Any advice will be appreciated. It's annoying to be forced to reboot the system four or five times per day.

  2. #2
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    17,555
    Blog Entries
    1

    Default Re: Pointer device locks up

    This reads like a possible kernel regression IMO. Not many using PS/2 connected devices these days. Examine the journal log from a previous boot where lock up occurred (eg -1 pertains to last boot before current)
    Code:
    sudo journalctl -b -1
    and look for any obvious errors relating to the PS/2 devices at a given time. (Some filtering with grep may be needed to help here.)

    You could also try substituting/adding a USB pointing device as a backup and using that instead. Does it stay working when the PS2 device is locked up?
    Last edited by deano_ferrari; 22-Dec-2017 at 19:17.

  3. #3
    Join Date
    Sep 2008
    Posts
    2,658

    Default Re: Pointer device locks up

    sounds like a graphic card issue to me
    what kind of a graphic card and driver do you have
    Code:
    sudo lspci | grep VGA
    are you sure that's a 32bit cpu afaik intel only had 32bit single core cpu's they did include hyper threading in some of them so they had a cpu with 2 virtual cores but those weren't dual core afaik all dualcore are x64
    Code:
    sudo lscpu
    or
    Code:
    cat /proc/cpuinfo
    anyways if you have an old graphic card without hardware acceleration plasma 5 is too intensive for you, you're better off with a lighter desktop like lxqt or lxde or mate
    plasma 5 is also known to have issues with some on-board intel graphic cards (the fix for some of them is to use uxa acceleration) and does not work well with the noveau driver you'd need the propitiatory nvidia driver which afaik only officially supports GeForce 4xx or never you might be able to get the older G03 driver working (GeForce 8xx and above) but that needs to be installed the hard way

  4. #4

    Question Re: Pointer device locks up

    Code:
     sudo journalctl -b -1
    This doesn't work well for me. It did work without the operands.

    Code:
     david@localhost:~> sudo journalctl -b -1
    [sudo] password for root: 
    Specifying boot ID or boot offset has no effect, no persistent journal was found.
    david@localhost:~>
    Code:
    david@localhost:~> sudo journalctl
    [sudo] password for root: 
    
    ... a lot of stuff
    
    Dec 22 14:50:13 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    
    ... a lot more stuff
    
    Dec 22 15:03:09 localhost kernel: psmouse serio1: bad data from KBC - timeout
    Dec 22 15:03:11 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    Dec 22 15:03:23 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    Dec 22 15:04:41 localhost kernel: psmouse serio1: bad data from KBC - timeout
    Dec 22 15:04:41 localhost kernel: psmouse serio1: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
    Dec 22 15:04:46 localhost kernel: psmouse serio1: hgpk: ID: 10 02 64
    Dec 22 15:05:49 localhost systemd[1]: Starting Cleanup of Temporary Directories...
    Dec 22 15:05:49 localhost systemd-tmpfiles[2430]: [/usr/lib/tmpfiles.d/tmp.conf:13] Duplicate line for path "/var/tmp", ignoring.
    Dec 22 15:05:49 localhost systemd-tmpfiles[2430]: [/usr/lib/tmpfiles.d/var.conf:14] Duplicate line for path "/var/log", ignoring.
    Dec 22 15:05:49 localhost systemd-tmpfiles[2430]: [/usr/lib/tmpfiles.d/var.conf:19] Duplicate line for path "/var/cache", ignoring.
    Dec 22 15:05:49 localhost systemd-tmpfiles[2430]: [/usr/lib/tmpfiles.d/var.conf:21] Duplicate line for path "/var/lib", ignoring.
    Dec 22 15:05:49 localhost systemd-tmpfiles[2430]: [/usr/lib/tmpfiles.d/var.conf:23] Duplicate line for path "/var/spool", ignoring.
    Dec 22 15:05:50 localhost systemd[1]: Started Cleanup of Temporary Directories.
    Dec 22 15:06:07 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    Dec 22 15:07:16 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    No more messages about "psmouse" that I can find. Thanks! dcb

  5. #5
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    17,555
    Blog Entries
    1

    Default Re: Pointer device locks up

    Quote Originally Posted by davidcbryant1951 View Post
    Code:
     sudo journalctl -b -1
    This doesn't work well for me. It did work without the operands.
    That's because /var/log/journal/ is missing.


    See here:
    https://www.freedesktop.org/software...d.service.html

    On systems where /var/log/journal/ does not exist yet but where persistent logging is desired (and the default journald.conf is used), it is sufficient to create the directory, and ensure it has the correct access modes and ownership:
    mkdir -p /var/log/journal
    systemd-tmpfiles --create --prefix /var/log/journal
    Last edited by deano_ferrari; 22-Dec-2017 at 19:04.

  6. #6
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    17,555
    Blog Entries
    1

    Default Re: Pointer device locks up

    Code:
    Dec 22 15:03:09 localhost kernel: psmouse serio1: bad data from KBC - timeout
    Dec 22 15:03:11 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    Dec 22 15:03:23 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    Dec 22 15:04:41 localhost kernel: psmouse serio1: bad data from KBC - timeout
    Dec 22 15:04:41 localhost kernel: psmouse serio1: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
    Dec 22 15:04:46 localhost kernel: psmouse serio1: hgpk: ID: 10 02 64
    Is the posted output from an event where the PS/2 hardware locked up?

  7. #7

    Default Re: Pointer device locks up

    Quote Originally Posted by deano_ferrari View Post
    Code:
    Dec 22 15:03:09 localhost kernel: psmouse serio1: bad data from KBC - timeout
    Dec 22 15:03:11 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    Dec 22 15:03:23 localhost kernel: psmouse serio1: hgpk: ID: 10 00 64
    Dec 22 15:04:41 localhost kernel: psmouse serio1: bad data from KBC - timeout
    Dec 22 15:04:41 localhost kernel: psmouse serio1: Mouse at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
    Dec 22 15:04:46 localhost kernel: psmouse serio1: hgpk: ID: 10 02 64
    Is the posted output from an event where the PS/2 hardware locked up?
    No. I had just rebooted the system, and it was still working OK.

  8. #8

    Default Re: Pointer device locks up

    Quote Originally Posted by deano_ferrari View Post
    That's because /var/log/journal/ is missing.


    See here:
    https://www.freedesktop.org/software...d.service.html
    OK, Thanks. I'm saving the journal now ... Maybe I'll capture some useful data in a day or two.

  9. #9
    Join Date
    Sep 2008
    Posts
    2,658

    Default Re: Pointer device locks up

    seeing how it's a known issue I still think it's your graphic card as Mesa-dri-nouveau taints the kernel and there is a serious bug in intel's driver stack (old ati cards have been abandoned by amd)
    telling us your graphic card and cpu would have been of more help, seeing it's an old PC most likely has an nvidia graphic card running TW you are using noveau if you installed Mesa-dri-nouveau your system is broken and will have the symptoms you described, if it's a supported card install the propitiatory driver if it's not remove Mesa-dri-nouveau and use openbox instead of kwin5 as a window manager by installing openbox-kde and selecting plasma5-openbox at the login screen
    seriosly how dificult is it to post
    Code:
    sudo lspci | grep VGA
    sudo lscpu

  10. #10
    Join Date
    Sep 2013
    Location
    Norfolk, UK
    Posts
    847

    Default Re: Pointer device locks up

    Quote Originally Posted by I_A View Post
    seeing it's an old PC most likely has an nvidia graphic card running TW you are using noveau if you installed Mesa-dri-nouveau your system is broken and will have the symptoms you described,
    That's a rather sweeping generalisation

    I've an old AMD 64 X2 5600+ based PC (currently using it to reply here incidentally), with a GeForce 8600GTS using the OSS nouveau driver and Mesa-dri-nouveau. Machine also has a PS/2 keyboard and PS/2 mouse.... No problems at all running TW 20171220 with KDE Plasma 5 (albeit a little sluggish, but perfectly usable).
    Regards, Paul

    Tumbleweed (Snapshot: 20180416) KDE Plasma 5
    Leap 42.3 KDE Plasma 5
    [Non-Tumbling Tumblweed (20150508) KDE 4 - Resurrected just for fun]


Page 1 of 3 123 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •