[hardy] computer hard locks with flashing keyboard lights

[Mark Grandi]

I'm using the latest version of hardy, and at seemingly random times, my computer has hard locked twice (once while i was watching youtube, the other while i was away at school and i come back to find it frozen)

I tried to ctrl+alt+backspace to restart the GUI but that didnt do anything

I even tried alt+sysrq+REISUB and that did nothing either

However,i did notice each time the computer hard locked like this, the keyboard LEDs for Caps lock and Scroll lock were flashing. Does this mean something?

I can try and provide any logs that may pin this down but i don't know which ones......

[Lupick (lupick)]

Same issue here.....

it happen in a completly random way.

L.

[jason (marshmel)]

I've got the same bug happening here. But only when X first starts and its random too.

[Dotan Mazor (dotanmazor)]

This issue affect Gutsy (7.10) as well.

Toshiba Satellite L40-17U, only a USB mouse is connected.

Other symptoms:

- There were times when the Alt key was seemed as constantly pressed, just before the freeze.

- Compiz was turned off and XGL disabled, but there are still hang-ups.

- Network "confusion"? These hang-ups started after starting to use aMule and Azureus (not at the same time).

- The Laptop was on all night with Azureus working on sharing only, without any downloads (sharing OpenSuse 10.3 ISO files, nothing special). In the morning, when starting-up Firefox, the PC froze and started the blink.

Possible directions:

- Overheating issue? The CPU temperature is about 60 degrees Celsius when it happens, so I guess it can be ruled out.

- Network issue? Trying to work with the wifi turned off, to see if it has anything to do with that.

Good luck tracing the problem!

Dotan

[cats (cats)]

I have the exact same issue, have happened two times in a short time already.

I will look into it more the next time it happens, since I restarted the comp the last time in pure anger I kinda forgot about it and went on with my work.

[xteejx (xteejx)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Murray Cumming (murrayc)]

You need to be more clear about the information you need.

[Mark Grandi (markgrandi)]

yeah, you haven't told us what exactly you want from us.......

changing back to new.

[xteejx (xteejx)]

This was marked Invalid by us as there wasn't enough suitable information and there had been no activity in 5 months. Is this still a problem and can you try with the latest Intrepid release?
Thank you.

[Javier Jardón (jjardon)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!

[Murz (murznn)]

I have found the bug https://bugs.launchpad.net/ubuntu/+bug/134944 - it says that this problem depend on NVidia drivers.

I have the same issue on Kubuntu Jaunty KDE 4.3 RC3 (and on KDE 4.2 too) and NVidia:
the keyboard randomly locks when working. I can't found the static way to reproduce it and have no records in log files when this happines.
When the keyboard locks up, I can turn on/of LED indicators and switch to console (Ctrl+Alt+F1..F7) and back to xorg, in console I can type anything - the keyboard works and fully functional.

This problem is not only on one computer, it is on 3 computers in my office.

Other subscribers, please post here which graphics drivers do you use? This helps our detect this problem.

[Murz (murznn)]

Or maybe it is depend on bug https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/179839 and keyboard locks when the shift key is held down for a 10 seconds.

[Murz (murznn)]

Subscribers to this bug, please post here the info of your configuration:
- Keyboard model, type and connection (PS2, USB, Internal in laptop)
- Version of DE (GNOME, KDE)
- Version and chipset of motherboard
- Model of videocard, version of graphics drivers
- Result of turning on the leds (Num lock, Caps lock, Scroll lock) when keyboard is locked
- Result of pressing "Ctrl+Alt+F1" and trying type something in console, when keyboard is locked

[Murz (murznn)]

My info:
System: Kubuntu Jaunty AMD64
Keyboard: I try two keyboards: Genius USB KB-06XE (USB) and Mitsumi Classic KFKEA4SA (PS2)
DE: KDE - all versions from 4.2 Beta 1 to KDE 4.3 RC3.
MB and video: 1. Gigabyte 945GZM-S2 (Intel 945 chipset) + nVidia Corporation MCP78S [GeForce 8200]
2, on another computer: ASUS M2N68-VM (NVIDIA GeForce 7050 chipset), internal video
Version of NVidia drivers: 180.44
LEDs works, Ctrl+Alt+F1 works, can type anything and switch back to xorg.

[Scribbles (zbdwwtcciq)]

This affects me as well. I haven't tried CTRL-ALT-F1, unfortunately, but I can verify that ssh / VNC connections cannot be made to the system when it is affected so. I am running Jaunty. Sometimes the hang occurs in a day or less of uptime and sometimes after up to 20 days; it seems quite random.

Keyboard:
Logitech cheapo media keyboard

Desktop:
Gnome 2.26.1

Motherboard:
ASUS P5W DH Deluxe, Intel 975X / Intel ICH7R

Video:
GeForce 9800 GT, driver is NVIDIA 180.44

The LEDs which are blinking (caps, scroll) do not change when I hit the caps or scroll lock buttons, but the num lock LED does function correctly.

So the only similarity I see between my setup and the last poster, Murz, is that we are both running the NVIDIA 180.44 drivers...

[Scribbles (zbdwwtcciq)]

I should add that my syslog and messages log do not show anything weird before the hangs.

[xteejx (xteejx)]

Has anyone here performed a memory test? It seems extremely unlikely that there would be random crashes with no pattern at all, which suggests to me there could be a serious hardware problem, i.e. RAM or hard drive on the way out, and this is true in 95% of cases. Instructions for performing a memory test are at https://help.ubuntu.com/community/DebuggingSystemCrash along with ways to find out where the problem occurred. Until we have this information, it will be near impossible to be able to fix this, since we won't know where to look unfortunately.

Also, more importantly:

1) Can this be tested in the Beta release of Lucid.
2) Can every affected user run "apport-collect 220501" from (if possible) the Live CD so we can obtain debugging information which may help.

I know it's a lot to ask, but it will help. Thank you guys. :)

[Jeremy Foshee (jeremyfoshee)]

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu release http://www.ubuntu.com/getubuntu/download . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

[Joe (joedsouza14)]

I have been trying to setup up Hardy Heron (8.04) LTS.

I tried this on two machines with the following configuragion :

1. AMD 2800+ processor, K8v800-M Motherboard, 512 MB DDR-1 (400 Mhz), PS2 Keyboard, PS2 Mouse, 250 GB SATA HDD.

2. Intel 2.40 Ghz Processor, 865GVBGL Motherboard, 512 MB DDR-1 (400 Mhz), PS2 Keyboard, PS2 Mouse, 250 GB SATA HDD.

On both the Machines, the Setup stops at creating files systems and the CAPS Lock, and SCROLL Lock lights on the Keyboard start blinking.

However, on the first Machines (i.e. the AMD 2800+, I did work with Hardy Heron using an 80 GB IDE HDD and it did work fine for quite some time. Since the 80 GB IDE Drive has gone bad and I do not have another 80 GB IDE HDD, I have been trying to load the system using a 250 GB SATA HDD.

Has this something to do with the IDE and SATA or is it to do with the 80 GB and the 250 GB or could it be BOTH ??

Am looking for some clarity on the issue, since I have wasted a lot of time and energy on this one.

Thanks & Regards,
      Joe.

[xteejx (xteejx)]

It may be a good idea to upgrade to the current LTS, as you will be more likely to have better support for SATA. Hardy was released over 3 years ago and is pretty out of date.