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

Comments

Popular posts from this blog

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process.  I had a specific need and found a specific solution that worked. Situation:  I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...)  The image was great, but I needed more flexibility on my bare metal.  So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances.  I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals.  In this case, the rigor is justified.  They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system.  They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE:  This is NOT a good implementation strategy in the "real world"  it will simply allow you to test the functionality.  There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...