Arch Linux

subatomic

Member

From: Berlin

Registered: 2005-06-26

Posts: 180

Re: Hard lockup, no logs, how to debug?

Maybe it is a GPU fail - ran overnight with display off but froze at first program start.
75° idle - I don't know, is that really a problem?

+------------------------------------------------------+                     
| NVIDIA-SMI 3.295.33   Driver Version: 295.33         |                       
|-------------------------------+----------------------+----------------------+
| Nb.  Name                     | Bus Id        Disp.  | Volatile ECC SB / DB |
| Fan   Temp   Power Usage /Cap | Memory Usage         | GPU Util. Compute M. |
|===============================+======================+======================|
| 0.  GeForce 8200              | 0000:02:00.0  N/A    |       N/A        N/A |
|  N/A   75 C  N/A   N/A /  N/A |  57%  144MB /  253MB |  N/A      Default    |
|-------------------------------+----------------------+----------------------|
| Compute processes:                                               GPU Memory |
|  GPU  PID     Process name                                       Usage      |
|=============================================================================|
|  0.           Not Supported                                                 |
+-----------------------------------------------------------------------------+

subatomic

Member

From: Berlin

Registered: 2005-06-26

Posts: 180

Re: Hard lockup, no logs, how to debug?

NO GPU FAIL! I purchased a new card w/ active cooling and 1GB dedicated memeory - still locks up! Temp on the new GPU is down to 37, CPU core temps are about 35-40, a little higher if I disconnect this loud case fan! But I am convinced it is not an overheating problem because after it will reboot immediately and run again for hours.

Last night I attached a USB drive and the whole thing locked up. This is what I'm thinking now - although it freezes quite often when I'm away (overnight) when I am at the keyboard it will freeze up 7x out of 10 just when I have clicked the mouse or as mentioned another event - in short - evdev.

As I posted before I get an xorg.0.log.old before it freezes and here are the last entries

[ 30747.870] (II) config/udev: removing device Bluetooth Mouse
[ 30747.870] (II) evdev: Bluetooth Mouse: Close
[ 30747.871] (II) UnloadModule: "evdev"
[ 30748.814] (II) config/udev: Adding input device Bluetooth Mouse (/dev/input/mouse0)
[ 30748.814] (II) No input driver specified, ignoring this device.
[ 30748.814] (II) This device may have been added with another device file.
[ 30748.815] (II) config/udev: Adding input device Bluetooth Mouse (/dev/input/event10)
[ 30748.815] (**) Bluetooth Mouse: Applying InputClass "evdev pointer catchall"
[ 30748.815] (II) Using input driver 'evdev' for 'Bluetooth Mouse'
[ 30748.815] (**) Bluetooth Mouse: always reports core events
[ 30748.815] (**) evdev: Bluetooth Mouse: Device: "/dev/input/event10"
[ 30748.815] (--) evdev: Bluetooth Mouse: Vendor 0xa5c Product 0x1
[ 30748.815] (--) evdev: Bluetooth Mouse: Found 3 mouse buttons
[ 30748.815] (--) evdev: Bluetooth Mouse: Found scroll wheel(s)
[ 30748.815] (--) evdev: Bluetooth Mouse: Found relative axes
[ 30748.815] (--) evdev: Bluetooth Mouse: Found x and y relative axes
[ 30748.815] (--) evdev: Bluetooth Mouse: Found absolute axes
[ 30748.815] (II) evdev: Bluetooth Mouse: Forcing absolute x/y axes to exist.
[ 30748.815] (II) evdev: Bluetooth Mouse: Configuring as mouse
[ 30748.815] (II) evdev: Bluetooth Mouse: Adding scrollwheel support
[ 30748.815] (**) evdev: Bluetooth Mouse: YAxisMapping: buttons 4 and 5
[ 30748.815] (**) evdev: Bluetooth Mouse: EmulateWheelButton: 4, EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[ 30748.815] (**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:04.0/usb4/4-1/4-1:1.0/bluetooth/hci0/hci0:1/input15/event10"
[ 30748.815] (II) XINPUT: Adding extended input device "Bluetooth Mouse" (type: MOUSE, id 10)
[ 30748.815] (II) evdev: Bluetooth Mouse: initialized for relative axes.
[ 30748.815] (WW) evdev: Bluetooth Mouse: ignoring absolute axes.
[ 30748.815] (**) Bluetooth Mouse: (accel) keeping acceleration scheme 1
[ 30748.815] (**) Bluetooth Mouse: (accel) acceleration profile 0
[ 30748.815] (**) Bluetooth Mouse: (accel) acceleration factor: 2.000
[ 30748.815] (**) Bluetooth Mouse: (accel) acceleration threshold: 4
[ 31760.580] (II) config/udev: Adding input device Streamzap PC Remote Infrared Receiver (0e9c:0000) (/dev/input/event5)
[ 31760.580] (**) Streamzap PC Remote Infrared Receiver (0e9c:0000): Ignoring device from InputClass "Ignore Streamzap IR"
[ 31764.660] (II) config/udev: Adding input device Streamzap PC Remote Infrared Receiver (0e9c:0000) (/dev/input/event5)
[ 31764.660] (**) Streamzap PC Remote Infrared Receiver (0e9c:0000): Ignoring device from InputClass "Ignore Streamzap IR"

Although there are no "errors" in the log I'm certain it's related to the lockup, at least as certain as I was with the other suspicions!

Wilco

Member

Registered: 2008-11-09

Posts: 440

Re: Hard lockup, no logs, how to debug?

Anyone managed to solve their hard crashes? Still happens for me on a new netbook, 64 bit, kernel 3.3, but not on my desktop

subatomic

Member

From: Berlin

Registered: 2005-06-26

Posts: 180

Re: Hard lockup, no logs, how to debug?

I just discovered that in my case it is lirc, possibly just KRemoteControl, because I have not yet experienced a freeze in Gnome when the daemon is running. Still very puzzling!

Edit: Scratch that - Gnome just froze on me as well. Perhaps it is the module for my remote?

Last edited by subatomic (2012-05-09 21:24:40)

@leksey

Member

From: Russia

Registered: 2011-06-24

Posts: 19

Re: Hard lockup, no logs, how to debug?

Hi,

I have the same issue, all worked great, but some "pacman -Syu" it happens every week.
I checked memory all night, it is ok, i change videocard and nothing helped me.

Today it happens again, and now i can see in kernel.log some strange records:

Aug  2 20:48:15 localhost kernel: [76707.739754] EXT4-fs (sda1): re-mounted. Opts: commit=0
Aug  2 20:48:16 localhost kernel: [76707.880801] EXT4-fs (sda2): re-mounted. Opts: commit=0
Aug  2 20:48:16 localhost kernel: [76707.886565] EXT4-fs (sdb1): re-mounted. Opts: commit=0
Aug  2 20:48:43 localhost kernel: [76735.515862] device eth0 left promiscuous mode
Aug  2 20:48:44 localhost kernel: [76736.542394] vboxnetflt: dropped 781127 out of 21735422 packets

sda1/sda2/sdb1 are ext3!!!!

and something strange with virtualbox (i have some gues OSs started as headless mode), after last record the PC is hung up and blink me only Caps and Scroll leds.

uname -a
Linux archy 3.4.7-1-ARCH #1 SMP PREEMPT Sun Jul 29 22:02:56 CEST 2012 x86_64 GNU/Linux

I don't understand what is reason of this manner. Hardware problem with some part of my PC or it is software problem, anyone have any idea?

@leksey

Member

From: Russia

Registered: 2011-06-24

Posts: 19

Re: Hard lockup, no logs, how to debug?

It seems the cause of issue in my case - hardware, i found old videocard and now it works more than one day. Of course it is very small time but i hope that issue is solved for me.