You are not logged in.

#1 2010-02-15 02:19:09

alcuadrado
Member
Registered: 2009-11-02
Posts: 21

System completely freezes

First of all, I was doubting whether I should post it here on in laptop issues, but I think it may be a kernel problem.

I have a Dell Inspiron 1545, with windows xp (i need it sometimes sad) and archlinux installed. On January the 11th I upgraded the BIOS, and I think the kernel too. From that day my system completely freezes sometimes, COMPLETELY, doesn't even ALT+SysRq+REISUB works (and I activated it, and works when not frozen) :S

It never freezes in windows sad

I just don't know what to do.

Any help?

Thanks!

PS: I have a friend with the same Laptop and BIOS version running Linux mint 8 (based on ubuntu 9.10) and kernel version 2.6.31-19 with no problem :s

Last edited by alcuadrado (2010-02-15 02:20:51)

Offline

#2 2010-02-15 02:37:49

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,774

Re: System completely freezes

Are there any other clues? Did the kernel panic or did it just go off into la-la land?
Check for a flashing caps-lock indicator on your keyboard.  That is a sure fire sign of a kernel panic.
Also, check your system logs for clues: Panic warnings, complaints about interrupts about which "no one cares", tracebacks and stack dumps, etc.

What video subsystem does the 1545 use?
Does it only freeze in Xorg? Which video driver are you using?
Are you using a wireless connection? What type of driver does it use?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#3 2010-02-15 02:48:21

alcuadrado
Member
Registered: 2009-11-02
Posts: 21

Re: System completely freezes

Hi, I don't have a caps-lock indicator :s so I don't know if its a kernel panic, it justs freeze, I even reinstall the entire system and the problem still there.
I hardly ever use it without Xorg, so I don't know if it freeze without it. The issue is that it sometimes doesn't freeze for DAYS, and sometimes it freezes many times in an hour.

I'm using intel drivers for wifi and video. xf86-video-intel for video, and iwlwifi-5000-ucode for wifi.

Some hardware information:
Processor: Intel® Pentium® T4200 (2.0GHz/800Mhz FSB/1MB cache)
Video: Intel Graphics Media Accelerator X4500HD
Wireless: Mini Tarjeta de Red Inalámbrica Intel WiFi Link 5100 802.11 Wireless-N

I found this log many times:
kernel: hald-probe-inpu[1979]: segfault at 5 ip 00007f174f4de559 sp 00007fff282db810 error 4 in libc-2.11.1.so[7f174f468000+14d000]
but no idea what does it mean.

Offline

#4 2010-02-15 04:02:03

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,774

Re: System completely freezes

kernel: hald-probe-inpu[1979]: segfault at 5 ip 00007f174f4de559 sp 00007fff282db810 error 4 in libc-2.11.1.so[7f174f468000+14d000]

That looks scary.  It is also the sort of thing that might be your root cause.  Are there any indications as to what the kernel was doing just prior to these messages?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#5 2010-02-15 04:16:09

skottish
Forum Fellow
From: Here
Registered: 2006-06-16
Posts: 7,942

Re: System completely freezes

Looking through the output below, it seems as if that error message is actually from a Intel HDA (sound) and ALSA conflict:

http://www.alsa-project.org/db/?f=b5a43 … 3d643e7b4a

Do you have anything in your kernel config that sets VGA modes in grub?

Offline

#6 2010-02-15 04:25:21

alcuadrado
Member
Registered: 2009-11-02
Posts: 21

Re: System completely freezes

ewaller wrote:

kernel: hald-probe-inpu[1979]: segfault at 5 ip 00007f174f4de559 sp 00007fff282db810 error 4 in libc-2.11.1.so[7f174f468000+14d000]

That looks scary.  It is also the sort of thing that might be your root cause.  Are there any indications as to what the kernel was doing just prior to these messages?

The last time it occurred was on feb the 10th (I've been traveling since then, if not, it would have been more recent proabably), I just was watching to a video with VLC, but it happens at any time, even when the computer is idle.

Some logs at the time i think it got stack:

everything.log:

Feb 10 14:47:48 lanobu kernel: input: Genius Optical Mouse as /devices/pci0000:00/0000:00:1d.1/usb7/7-1/7-1:1.0/input/input17
Feb 10 14:47:48 lanobu kernel: generic-usb 0003:0458:003A.0004: input,hidraw0: USB HID v1.11 Mouse [Genius Optical Mouse] on usb-0000:00:1d.1-1/input0
Feb 10 15:07:48 lanobu -- MARK --
Feb 10 15:16:46 lanobu kernel: usb 7-1: USB disconnect, address 3
Feb 10 15:16:48 lanobu kernel: atkbd.c: Unknown key pressed (translated set 2, code 0x8d on isa0060/serio0).
Feb 10 15:16:48 lanobu kernel: atkbd.c: Use 'setkeycodes e00d <keycode>' to make it known.
Feb 10 15:17:01 lanobu crond[2142]: FILE /var/spool/cron/root USER root PID 17416 job sys-daily
Feb 10 15:18:22 lanobu crond[31973]: mailing cron output for user root job sys-daily
Feb 10 15:18:22 lanobu crond[31973]: unable to exec /usr/sbin/sendmail: cron output for user root job sys-daily to /dev/null
Feb 10 15:35:35 lanobu NetworkManager: <info>  (wlan0): supplicant connection state:  completed -> group handshake
Feb 10 15:35:35 lanobu NetworkManager: <info>  (wlan0): supplicant connection state:  group handshake -> completed
Feb 10 15:45:01 lanobu crond[2142]: FILE /var/spool/cron/root USER root PID 32248 job sys-hourly
Feb 10 15:57:39 lanobu syslog-ng[1985]: syslog-ng starting up; version='3.0.4'
Feb 10 15:57:39 lanobu kernel: Linux version 2.6.32-ARCH (tobias@T-POWA-LX) (gcc version 4.4.3 (GCC) ) #1 SMP PREEMPT Tue Feb 9 15:12:10 CET 2010
Feb 10 15:57:39 lanobu kernel: Command line: root=/dev/disk/by-uuid/7c3e45b7-93b8-4ffa-ba3c-6ba4eaac3734 ro
Feb 10 15:57:39 lanobu kernel: KERNEL supported cpus:
Feb 10 15:57:39 lanobu kernel: Intel GenuineIntel
Feb 10 15:57:39 lanobu kernel: AMD AuthenticAMD

Kernel.log: the same

Errors.log:
Feb 10 15:57:41 lanobu NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
Feb 10 20:12:18 lanobu NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed

All the errors of that day

$ sudo grep error /var/log/* | grep "Feb 10"
/var/log/daemon.log.1:Feb 10 09:03:51 lanobu NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
/var/log/daemon.log.1:Feb 10 13:44:04 lanobu NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
/var/log/daemon.log.1:Feb 10 15:57:41 lanobu NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
/var/log/daemon.log.1:Feb 10 20:12:18 lanobu NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
/var/log/everything.log.1:Feb 10 09:03:49 lanobu kernel: hald-probe-inpu[2107]: segfault at 5 ip 00007fd04a662559 sp 00007fff23e039a0 error 4 in libc-2.11.1.so[7fd04a5ec000+14d000]
/var/log/everything.log.1:Feb 10 09:03:51 lanobu NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
/var/log/everything.log.1:Feb 10 13:44:02 lanobu kernel: hald-probe-inpu[2092]: segfault at 5 ip 00007f385d9e5559 sp 00007fff5bb59a80 error 4 in libc-2.11.1.so[7f385d96f000+14d000]
/var/log/everything.log.1:Feb 10 13:44:04 lanobu NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
/var/log/everything.log.1:Feb 10 15:57:40 lanobu kernel: hald-probe-inpu[2044]: segfault at 5 ip 00007f7468a59559 sp 00007fff3b0a7b30 error 4 in libc-2.11.1.so[7f74689e3000+14d000]
/var/log/everything.log.1:Feb 10 15:57:41 lanobu NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
/var/log/everything.log.1:Feb 10 20:12:17 lanobu kernel: hald-probe-inpu[2032]: segfault at 5 ip 00007fa20c252559 sp 00007fff281cb4c0 error 4 in libc-2.11.1.so[7fa20c1dc000+14d000]
/var/log/everything.log.1:Feb 10 20:12:18 lanobu NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
/var/log/kernel.log.1:Feb 10 09:03:49 lanobu kernel: hald-probe-inpu[2107]: segfault at 5 ip 00007fd04a662559 sp 00007fff23e039a0 error 4 in libc-2.11.1.so[7fd04a5ec000+14d000]
/var/log/kernel.log.1:Feb 10 13:44:02 lanobu kernel: hald-probe-inpu[2092]: segfault at 5 ip 00007f385d9e5559 sp 00007fff5bb59a80 error 4 in libc-2.11.1.so[7f385d96f000+14d000]
/var/log/kernel.log.1:Feb 10 15:57:40 lanobu kernel: hald-probe-inpu[2044]: segfault at 5 ip 00007f7468a59559 sp 00007fff3b0a7b30 error 4 in libc-2.11.1.so[7f74689e3000+14d000]
/var/log/kernel.log.1:Feb 10 20:12:17 lanobu kernel: hald-probe-inpu[2032]: segfault at 5 ip 00007fa20c252559 sp 00007fff281cb4c0 error 4 in libc-2.11.1.so[7fa20c1dc000+14d000]
/var/log/messages.log.1:Feb 10 09:03:49 lanobu kernel: hald-probe-inpu[2107]: segfault at 5 ip 00007fd04a662559 sp 00007fff23e039a0 error 4 in libc-2.11.1.so[7fd04a5ec000+14d000]
/var/log/messages.log.1:Feb 10 09:03:51 lanobu NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
/var/log/messages.log.1:Feb 10 13:44:02 lanobu kernel: hald-probe-inpu[2092]: segfault at 5 ip 00007f385d9e5559 sp 00007fff5bb59a80 error 4 in libc-2.11.1.so[7f385d96f000+14d000]
/var/log/messages.log.1:Feb 10 13:44:04 lanobu NetworkManager: <WARN>  nm_generic_enable_loopback(): error -17 returned from rtnl_addr_add():
/var/log/messages.log.1:Feb 10 15:57:40 lanobu kernel: hald-probe-inpu[2044]: segfault at 5 ip 00007f7468a59559 sp 00007fff3b0a7b30 error 4 in libc-2.11.1.so[7f74689e3000+14d000]
/var/log/messages.log.1:Feb 10 15:57:41 lanobu NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files
/var/log/messages.log.1:Feb 10 20:12:17 lanobu kernel: hald-probe-inpu[2032]: segfault at 5 ip 00007fa20c252559 sp 00007fff281cb4c0 error 4 in libc-2.11.1.so[7fa20c1dc000+14d000]
/var/log/messages.log.1:Feb 10 20:12:18 lanobu NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files

______


skottish wrote:

Looking through the output below, it seems as if that error message is actually from a Intel HDA (sound) and ALSA conflict:

http://www.alsa-project.org/db/?f=b5a43 … 3d643e7b4a

Do you have anything in your kernel config that sets VGA modes in grub?

I have a plain grub config:

$ cat /boot/grub/menu.lst
# Config file for GRUB - The GNU GRand Unified Bootloader
# /boot/grub/menu.lst

# DEVICE NAME CONVERSIONS 
#
#  Linux           Grub
# -------------------------
#  /dev/fd0        (fd0)
#  /dev/sda        (hd0)
#  /dev/sdb2       (hd1,1)
#  /dev/sda3       (hd0,2)
#

#  FRAMEBUFFER RESOLUTION SETTINGS
#     +-------------------------------------------------+
#          | 640x480    800x600    1024x768   1280x1024
#      ----+--------------------------------------------
#      256 | 0x301=769  0x303=771  0x305=773   0x307=775
#      32K | 0x310=784  0x313=787  0x316=790   0x319=793
#      64K | 0x311=785  0x314=788  0x317=791   0x31A=794
#      16M | 0x312=786  0x315=789  0x318=792   0x31B=795
#     +-------------------------------------------------+
#  for more details and different resolutions see
#  http://wiki.archlinux.org/index.php/GRUB#Framebuffer_Resolution 

# general configuration:
timeout   5
default   0
color light-blue/black light-cyan/blue

# boot sections follow
# each is implicitly numbered from 0 in the order of appearance below
#
# TIP: If you want a 1024x768 framebuffer, add "vga=773" to your kernel line.
#
#-*

# (0) Arch Linux
title  Arch Linux
root   (hd0,2)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/7c3e45b7-93b8-4ffa-ba3c-6ba4eaac3734 ro
initrd /boot/kernel26.img

# (1) Arch Linux
title  Arch Linux Fallback
root   (hd0,2)
kernel /boot/vmlinuz26 root=/dev/disk/by-uuid/7c3e45b7-93b8-4ffa-ba3c-6ba4eaac3734 ro
initrd /boot/kernel26-fallback.img

# (2) Windows
title Windows
rootnoverify (hd0,0)
makeactive
chainloader +1

PS: I tryed to read the link you gave me skottish, but I don't understand it, sorry

Last edited by alcuadrado (2010-02-15 04:29:47)

Offline

#7 2010-02-15 06:48:51

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,774

Re: System completely freezes

These two events seem to have some correlation.  They occur within 1 second of each other on a couple of occasions.

/var/log/everything.log.1:Feb 10 20:12:17 lanobu kernel: hald-probe-inpu[2032]: segfault at 5 ip 00007fa20c252559 sp 00007fff281cb4c0 error 4 in libc-2.11.1.so[7fa20c1dc000+14d000]
/var/log/everything.log.1:Feb 10 20:12:18 lanobu NetworkManager: <WARN>  default_adapter_cb(): bluez error getting default adapter: The name org.bluez was not provided by any .service files

Are you using any sort of Bluetooth device?
Is it possible that someone/something is trying to associate with your Bluetooth stack coincident with the crashes?

What if you blacklist your Bluetooth kernel modules to see if it improves stability?


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#8 2010-02-15 07:26:43

alcuadrado
Member
Registered: 2009-11-02
Posts: 21

Re: System completely freezes

I have a bluetooth device but I never use it, so let's try that smile

I have a  REALLY newbie question: how do I blacklist that module? as MOD_BLACKLIST=() from /etc/rc.conf is deprecated.

Offline

#9 2010-02-15 07:43:08

ewaller
Administrator
From: Pasadena, CA
Registered: 2009-07-13
Posts: 19,774

Re: System completely freezes

in /etc/rc.conf

In the MODULES line include the module to blacklist, but prefix it with a !

Here is that line from my config:
MODULES=(hp_wmi ssb b43 lib80211_crypt_tkip !wl acpi-cpufreq cpufreq-ondemand cpufreq_conservative cpufreq_powersave !snd_pcm_oss fuse)

It disables wl and snd_pcm_oss.

In your case, I think you need to include one of the modules found in /lib/modules/2.6.32-ARCH/kernel/drivers/bluetooth/.  Check which of those are being loaded using lsmod


Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way

Offline

#10 2010-02-15 07:47:47

alcuadrado
Member
Registered: 2009-11-02
Posts: 21

Re: System completely freezes

I google more about that error (the one of bluetooth) and it was because I haven't set up the bluetooth daemon.

To be sure, I did this:
Restart networkmanager daemon > error log was generated
Start bluetooth daemon
Restart networkmanager daemon > no error log was generated
Stop bluetooth daemon
Restart networkmanager daemon > error log was generated

So that was the problem with that...

I wish that was the cause of the system freezes but not, before reinstalling the system, I had bluetooth daemon installed and fully functional, so that's not the problem sad

PS: By searching more in the logs I found that I got that segfault log exactly after turning on the machine.

# grep "Feb 15" everything.log | grep segfault -B 25 -A 25
Feb 15 04:20:11 lanobu kernel: usb 2-1.1: new full speed USB device using uhci_hcd and address 3
Feb 15 04:20:11 lanobu kernel: usb 2-1.1: configuration #1 chosen from 1 choice
Feb 15 04:20:11 lanobu kernel: input: HID 413c:8161 as /devices/pci0000:00/0000:00:1a.0/usb2/2-1/2-1.1/2-1.1:1.0/input/input14
Feb 15 04:20:11 lanobu kernel: generic-usb 0003:413C:8161.0002: input,hidraw1: USB HID v1.11 Keyboard [HID 413c:8161] on usb-0000:00:1a.0-1.1/input0
Feb 15 04:20:11 lanobu kernel: usb 2-1.2: new full speed USB device using uhci_hcd and address 4
Feb 15 04:20:11 lanobu kernel: usb 2-1.2: configuration #1 chosen from 1 choice
Feb 15 04:20:11 lanobu kernel: input: HID 413c:8162 as /devices/pci0000:00/0000:00:1a.0/usb2/2-1/2-1.2/2-1.2:1.0/input/input15
Feb 15 04:20:11 lanobu kernel: generic-usb 0003:413C:8162.0003: input,hidraw2: USB HID v1.11 Mouse [HID 413c:8162] on usb-0000:00:1a.0-1.2/input0
Feb 15 04:20:11 lanobu kernel: input: Integrated_Webcam_1.3M as /devices/pci0000:00/0000:00:1a.7/usb1/1-6/1-6:1.0/input/input16
Feb 15 04:20:11 lanobu kernel: usbcore: registered new interface driver uvcvideo
Feb 15 04:20:11 lanobu kernel: USB Video Class driver (v0.1.0)
Feb 15 04:20:11 lanobu kernel: usb 2-1.3: new full speed USB device using uhci_hcd and address 5
Feb 15 04:20:11 lanobu kernel: usb 2-1.3: configuration #1 chosen from 1 choice
Feb 15 04:20:11 lanobu kernel: Bluetooth: Core ver 2.15
Feb 15 04:20:11 lanobu kernel: EXT4-fs (sda4): mounted filesystem with ordered data mode
Feb 15 04:20:11 lanobu kernel: NET: Registered protocol family 31
Feb 15 04:20:11 lanobu kernel: Bluetooth: HCI device and connection manager initialized
Feb 15 04:20:11 lanobu kernel: Bluetooth: HCI socket layer initialized
Feb 15 04:20:11 lanobu kernel: Bluetooth: Generic Bluetooth USB driver ver 0.6
Feb 15 04:20:11 lanobu kernel: usbcore: registered new interface driver btusb
Feb 15 04:20:11 lanobu kernel: Adding 3807396k swap on /dev/sda2.  Priority:-1 extents:1 across:3807396k 
Feb 15 04:20:12 lanobu kernel: scsi 4:0:0:0: Direct-Access     Generic- Multi-Card       1.00 PQ: 0 ANSI: 0 CCS
Feb 15 04:20:12 lanobu kernel: sd 4:0:0:0: Attached scsi generic sg2 type 0
Feb 15 04:20:12 lanobu kernel: usb-storage: device scan complete
Feb 15 04:20:12 lanobu kernel: sd 4:0:0:0: [sdb] Attached SCSI removable disk
[b]Feb 15 04:20:12 lanobu kernel: hald-probe-inpu[2032]: segfault at 5 ip 00007fd57bc4d559 sp 00007fffcb484df0 error 4 in libc-2.11.1.so[7fd57bbd7000+14d000][/b]
Feb 15 04:20:13 lanobu NetworkManager: <info>  starting...
Feb 15 04:20:13 lanobu NetworkManager: <info>  Trying to start the modem-manager...
Feb 15 04:20:13 lanobu NetworkManager: Loaded plugin keyfile: (c) 2007 - 2008 Red Hat, Inc.  To report bugs please use the NetworkManager mailing list.
Feb 15 04:20:13 lanobu NetworkManager: <info>  Found wlan radio killswitch rfkill0 (at /sys/devices/pci0000:00/0000:00:1c.1/0000:0c:00.0/ieee80211/phy0/rfkill0) (driver <unknown>)
Feb 15 04:20:13 lanobu NetworkManager: <info>  WiFi enabled by radio killswitch; enabled by state file
Feb 15 04:20:13 lanobu NetworkManager: <info>  WWAN enabled by radio killswitch; enabled by state file
Feb 15 04:20:13 lanobu crond[2077]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel info
Feb 15 04:20:13 lanobu NetworkManager: <info>  (wlan0): driver supports SSID scans (scan_capa 0x01).
Feb 15 04:20:13 lanobu NetworkManager: <info>  (wlan0): new 802.11 WiFi device (driver: 'iwlagn')
Feb 15 04:20:13 lanobu NetworkManager: <info>  (wlan0): exported as /org/freedesktop/NetworkManager/Devices/0
Feb 15 04:20:13 lanobu NetworkManager: <info>  (wlan0): now managed
Feb 15 04:20:13 lanobu NetworkManager: <info>  (wlan0): device state change: 1 -> 2 (reason 2)
Feb 15 04:20:13 lanobu NetworkManager: <info>  (wlan0): bringing up device.
Feb 15 04:20:13 lanobu kernel: iwlagn 0000:0c:00.0: firmware: requesting iwlwifi-5000-2.ucode
Feb 15 04:20:13 lanobu kernel: iwlagn 0000:0c:00.0: loaded firmware version 8.24.2.12
Feb 15 04:20:11 lanobu init: Entering runlevel: 5
Feb 15 04:20:13 lanobu kernel: Registered led device: iwl-phy0::radio
Feb 15 04:20:13 lanobu kernel: Registered led device: iwl-phy0::assoc
Feb 15 04:20:13 lanobu kernel: Registered led device: iwl-phy0::RX
Feb 15 04:20:13 lanobu kernel: Registered led device: iwl-phy0::TX
Feb 15 04:20:13 lanobu NetworkManager: <info>  (wlan0): preparing device.
Feb 15 04:20:13 lanobu NetworkManager: <info>  (wlan0): deactivating device (reason: 2).
Feb 15 04:20:13 lanobu NetworkManager: supplicant_interface_acquire: assertion `mgr_state == NM_SUPPLICANT_MANAGER_STATE_IDLE' failed
Feb 15 04:20:13 lanobu kernel: sky2 eth0: enabling interface
Feb 15 04:20:13 lanobu NetworkManager: <info>  (eth0): carrier is OFF

Last edited by alcuadrado (2010-02-15 07:57:52)

Offline

#11 2010-02-16 20:30:09

alcuadrado
Member
Registered: 2009-11-02
Posts: 21

Re: System completely freezes

It happend one more time and NO log was in /var/log of the last 5minuts before freezing :s

Any idea?

Please help ! (:

Offline

Board footer

Powered by FluxBB