Arch Linux

keineeile

Member

Registered: 2012-03-03

Posts: 44

System crashes at random times

Hey guys,

hope I got the right forum...

I have a really annoying problem with my laptop (Acer 4820TG): I'm using the current catalyst driver (catalyst-daemon and catalyst-utils 12.1), and sometimes my system simply crashes and doesn't respond to anything anymore, no key combination, nothing. That appears at random times, sometimes a couple times a day, sometimes not for a week... The only think I can do then is forcefully turning my laptop off (by pressing and holding the power button).

Here are the last couple lines of my Xorg.0.log:

[  1185.256] (II) Power Button: Close
[  1185.256] (II) UnloadModule: "evdev"
[  1185.256] (II) Unloading evdev
[  1185.286] (II) Power Button: Close
[  1185.286] (II) UnloadModule: "evdev"
[  1185.286] (II) Unloading evdev
[  1185.376] (II) Sleep Button: Close
[  1185.376] (II) UnloadModule: "evdev"
[  1185.376] (II) Unloading evdev
[  1185.483] (II) Video Bus: Close
[  1185.483] (II) UnloadModule: "evdev"
[  1185.483] (II) Unloading evdev
[  1185.589] (II) 1.3M WebCam: Close
[  1185.590] (II) UnloadModule: "evdev"
[  1185.590] (II) Unloading evdev
[  1185.709] (II) AT Translated Set 2 keyboard: Close
[  1185.710] (II) UnloadModule: "evdev"
[  1185.710] (II) Unloading evdev
[  1185.923] (II) UnloadModule: "synaptics"
[  1185.923] (II) Unloading synaptics
[  1186.029] (II) Acer WMI hotkeys: Close
[  1186.030] (II) UnloadModule: "evdev"
[  1186.030] (II) Unloading evdev
[  1186.048] (II) fglrx(0): Shutdown CMMQS
[  1186.048] (II) fglrx(0): [uki] removed 1 reserved context for kernel
[  1186.048] (II) fglrx(0): [uki] unmapping 8192 bytes of SAREA 0x2000 at 0x7f6c3d382000
[  1186.095] (II) fglrx(0): Interrupt handler Shutdown.

The kernel.log from the same time has just a couple lines, but to me they don't seem related to the problem. Or are they?

Mar  3 14:20:51 myhost kernel: [ 1183.852149] [fglrx] IRQ 46 Disabled
Mar  3 14:20:51 myhost kernel: [ 1183.974166] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled true, count 0 (implement)
Mar  3 14:20:51 myhost kernel: [ 1184.176783] ieee80211 phy0: brcms_ops_bss_info_changed: qos enabled: false (implement)
Mar  3 14:20:51 myhost kernel: [ 1184.176789] ieee80211 phy0: brcmsmac: brcms_ops_bss_info_changed: disassociated
Mar  3 14:20:51 myhost kernel: [ 1184.176794] ieee80211 phy0: brcms_ops_bss_info_changed: arp filtering: enabled false, count 0 (implement)
Mar  3 14:20:51 myhost kernel: [ 1184.176796] wlan0: deauthenticating from 00:90:4c:91:00:01 by local choice (reason=3)
Mar  3 14:20:51 myhost kernel: [ 1184.229710] cfg80211: Calling CRDA to update world regulatory domain

Any help would be highly appreciated, cause it affects the usability of a system enormously if you always have to be afraid it'll crash... Thanks in advance!!

Regards
keineeile

lagagnon

Member

From: an Island in the Pacific...

Registered: 2009-12-10

Posts: 1,087

Website

Re: System crashes at random times

You seem to be convinced that this is a video problem, but I am not so sure. What I would do is run a Live Linux CD (from CD or pen drive), stress your machine and see if you get same crashes using a Live distro. If you do then you probably have a hardware fault. Let us know what happens at that point.

---

Philosophy is looking for a black cat in a dark room. Metaphysics is looking for a black cat in a dark room that isn't there. Religion is looking for a black cat in a dark room that isn't there and shouting "I found it!". Science is looking for a black cat in a dark room with a flashlight.

keineeile

Member

Registered: 2012-03-03

Posts: 44

Re: System crashes at random times

Well, I actually am kinda convinced it's somehow related to that, cause in the past I already had a couple times issues with the proprietary catalyst driver...

As it is, on my laptop I have a second Arch system installed (for energy saving purposes), which uses the open-source ATI driver and switches the ATI video card off, using the integrated Intel Graphics Chip. Well, I switched over for about two days by now, and didn't encounter a crash - yet. I'll keep using it for another couple days and see if anything happens...