Skip to main content

desktop lock up on RHEL

Issue: my desktop would lock up and become unresponsive while the machine still had a normally functioning  OS.

Resolution:
attempt #1:  disable the Lenovo fingerprint reader.  This didn't fix it.
attempt #2:  stop using Google Chrome.  Wasn't Google Chrome...
attempt #3:  stay away from flash...  perhaps I'll try uninstalling flash.
attempt #4:  this seems to have fixed it... update the boot string with i8042.noloop

SOLVED:
--FOR RHEL update your /boot/grub/grub.conf
title Red Hat Enterprise Linux Workstation (2.6.32-279.2.1.el6.x86_64)
        root (hd0,2)
        kernel /vmlinuz-2.6.32-279.2.1.el6.x86_64 ro root=/dev/mapper/vg_neo-lv_root rd_NO_LUKS LANG=en_US.UTF-8 rd_NO_MD quiet SYSFONT=latarcyrheb-sun16 rhgb crashkernel=auto rd_LVM_LV=vg_neo/lv_swap  KEYBOARDTYPE=pc KEYTABLE=us rd_LVM_LV=vg_neo/lv_root rd_NO_DM i8042.noloop
        initrd /initramfs-2.6.32-279.2.1.el6.x86_64.img

-- Fedora 17 (fc16 and greater, actually)
root@neo ~ # cat /etc/default/grub

#grub2-mkconfig -o /boot/grub2/grub.cfg
#grub2-mkfont --output=/boot/grub2/unicode.pf2 /usr/share/fonts/dejavu/DejaVuSansMono.ttf
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR="Fedora"
GRUB_DEFAULT=saved
GRUB_CMDLINE_LINUX="rd.lvm.lv=vg_neo/lv_swap rd.md=0 rd.dm=0 SYSFONT=True  KEYTABLE=us rd.luks=0 rd.lvm.lv=vg_neo/lv_root LANG=en_US.UTF-8 rhgb quiet i8042.noloop"
#GRUB_THEME="/boot/grub2/themes/system/theme.txt"# Custom stuff
GRUB_DISABLE_RECOVERY="true"
GRUB_SAVEDEFAULT="true"
GRUB_GFXMODE=1600x900x16
GRUB_GFXPAYLOAD_LINUX=keep
GRUB_BACKGROUND=/boot/grub/splash-tree.tga
root@neo ~ # grub2-mkconfig -o /boot/grub2/grub.cfg



Errata:  Looks like I may have been way off base.  It is odd that this problem just randomly appeared.

History:
I occasionally boot my laptop to Windows 7 to allow updates and such.  Unfortunately the fingerprint reader software grabbed my attention and I decided I would give it a try.

One odd result of configuring the fingerprint reader within Windows is there is a small green light on the reader after I shut the machine down.  I can scan my finger when the machine is off and it will start the machine (again, from the power-off state).

I am not certain that my desktop lockup in Linux is caused by the fingerprint reader - but there is a coincidence of enabling the reader and my lockups.

When the desktop locks up, the mouse remains frozen and the keyboard is essentially unresponsive (there is a significantly delayed response).  I had noticed that when the machine would go to the screensaver and I woke it up, the password entry area would fill as though I was holding down a key on the keyboard.

I'll update this post if my resolution did not solve the issue.  (posted: 20120726)

NOTES:
http://www.thinkwiki.org/wiki/Synaptics_TouchPad_driver_for_X#Configuration_using_Gnome

Seem somewhat related to the lockups...

messages:Jul 26 23:33:59 neo kernel: psmouse.c: TouchPad at isa0060/serio1/input0 lost synchronization, throwing 2 bytes away.
messages:Jul 26 23:34:01 neo kernel: psmouse.c: failed to re-enable mouse on isa0060/serio1
messages:Jul 26 23:34:01 neo kernel: psmouse.c: resync failed, issuing reconnect request
messages:Jul 26 23:34:07 neo kernel: psmouse.c: Failed to deactivate mouse on isa0060/serio1
messages:Jul 26 23:34:08 neo kernel: psmouse.c: Failed to enable mouse on isa0060/serio1

Labels:

Comments

Post a Comment

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...
2 comments
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un...
1 comment
Read more