How to debug daily freezes?

eldragon · 2010-01-16 14:23:30

naguz, dont hijack the thread, start a new one with your problem. its unlikely its the same issue

OrangeRoot1000 · 2010-01-16 15:15:41

Jan 12 10:28:16 ARCH-DN kernel: fb: conflicting fb hw usage inteldrmfb vs VESA VGA - removing generic driver

Looks like an X issue. I personally have a i945 Intel and can not keep a stable KDE4.x session up. NO other wm/de's are effected including KDE 3.5.x series. I did not see this note about KMS taking the VGA line out. I like setting my tty font sizes otherwise they are too large. The only thing I have figured out is use only the vesa drivers and stay away from KDE plasmas. Using KDE 4 apps in aNY other de/wm works wonderfully 99% of the time.

I think some would say it is an Intel issue totally. All I can say is that out of the 30-40 de/wm's I've tried trouble free including a prior version of one de and all of a sudden a new window manager brings lockups. Something smells fishee in programmingville.

To protect myself from flash/java overload on some pages that have froze I use no script so I can control how fast the page is populated.

Last edited by OrangeRoot1000 (2010-01-16 15:16:49)

alphazo · 2010-01-19 09:40:23

I have rebuilt my system and went for ext3 (data=ordered and barrier=1) and xf86-video-intel-newest. I noticed that on the system that crashed I also had powernowd (with OPTIONS="-q -u 15 -l 5" ) and acpi-cpufreq module loaded. Has there been any report of hard crashes with those two components enabled?

Alphazo

florianbw · 2010-01-19 09:44:56

I had the same problem, using Dell E6400 with Intel Graphics. After I hard-reseted some times, I had serious data loss on my ext4. Thanks for reminding me of the REISUB combo.

The following measures seem to have fixed my problem (since 5 days no freeze):
* using Firefox 3.6 instead of chromium (chromium seemed to reinforce freezes)
* upgrading to xf86-video-intel-newest (2.10.0-2)
* disabling the locking of the screen and screensaver (I never had freezes while being active in front of the PC)
* disabling KMS

alphazo · 2010-01-19 11:09:41

New install and first crash (sshd was not started yet). I was able to get my ext3 clean after few fsck! I'm now going to try disabling KMS. Pretty frustrating...

eldragon · 2010-01-19 11:29:44

alphazo, have you been able to collect any logs? is it a kernel panic (like described in a previous post?)

alphazo · 2010-01-19 13:48:58

Ashren wrote:

You can disable KMS by appending i915.modeset=0 to the kernel line in /boot/grub/menu.lst:
kernel /boot/vmlinuz26 root=/dev/... i915.modeset=0
This might cause X not to start, but try it out.

I tried as suggested. It booted without the fancy console but in the end it would not launch X (slim). Are there any additional steps to disable KMS and make X working?

alphazo · 2010-01-19 13:55:34

eldragon wrote:

alphazo, have you been able to collect any logs? is it a kernel panic (like described in a previous post?)

I've saved a couple of logs but only after fixing the filesystem. I will have a look at them and see if there is anything relevant. This time I did something that broke it. I wanted to try this new super-cool fast virtual console switching that KMS brings. It worked on my laptop display so I decided to see how it would work on the external VGA display. I connected it and got a picture on both laptop and VGA panels. I was about to use lxrandr to disable the laptop LCD but instead I went straight for a CTRL+ALT 3 for a virtual console and here came the freeze!

davidm · 2010-01-19 18:50:01

florianbw wrote:

* using Firefox 3.6 instead of chromium (chromium seemed to reinforce freezes)

I second this. I had two freezes and the common occurance was chromium running. Since not using chromium it has not happened in weeks. That others noticed this would be a strange coincidence if there were not something to it.

alphazo · 2010-01-25 15:35:36

Today I got another freeze but this time I was granted access to the virtual console.

Here are the conditions.
- Arch updated this morning Jan 12, 2010
- xf86-video-intel-newest 2.10.0-2
- acpi-cpufreq module loaded and powernowd started with OPTIONS="-q -u 15 -l 5"
- CPU frequency monitor applet running on XfCE
- Thunderbird, Firefox running
- Working on Digikam...then got hit by Mr Freeze again.

Switched to virtual console and started looking at running processes. Pretty much everything was sleeping except slim (20% CPU). Please note that keyboard was very unresponsive (I had to type two three times on the same key to get it printed). I started to SIGTERM Thunderbird, Firefox and Digikam but still no improvement. I then killed both acpi-cpufreq and powernowd and cpu usage went down to 2% instead of 20%. I then tried to kill X but couldn't get slim back for login so I decided to cleanly reboot the system.

There is a line in /var/log/messages.log that caught my attention:

Jan 25 14:54:44 Arch-DN -- MARK --
Jan 25 15:08:32 Arch-DN kernel: i915: Waking up sleeping processes
Jan 25 15:08:32 Arch-DN kernel: reboot required
Jan 25 15:08:58 Arch-DN kernel: [drm] LVDS-8: set mode 1280x800 31

What do this "Waking up sleeping processes" and more importantly "reboot required" mean?

From now on I've disabled both acpi-cpufreq and powernowd to see if the problem pops up again.

Thanks
Alphazo

PS: Furthermore I noticed a bunch of other ACPI related messages in my messages.log (don't know if it is related though).

Jan 25 09:32:11 Arch-DN load-modules.sh: Not loading module alias 'pcspkr' because it is blacklisted
Jan 25 09:32:12 Arch-DN load-modules.sh: Not loading module 'pcspkr' for alias 'platform:pcspkr' because it is blacklisted
Jan 25 09:32:12 Arch-DN load-modules.sh: 'acpi:LNXSYSTM:' is not a valid module or alias name
Jan 25 09:32:12 Arch-DN load-modules.sh: 'acpi:LNXSYBUS:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'platform:vesafb' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'platform:dock' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'pci:v00008086d000027A6sv00001028sd00000201bc03sc80i00' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'pci:v00008086d00002448sv00000000sd00000000bc06sc04i01' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0200:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0800:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0103:PNP0C01:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0100:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0C01:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0F13:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0303:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0C04:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:PNP0000:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:13 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'platform:regulatory' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:14 Arch-DN load-modules.sh: 'acpi:device:' is not a valid module or alias name
Jan 25 09:32:15 Arch-DN load-modules.sh: 'usb:v0B97p7762d0110dc00dsc00dp00ic0Bisc00ip00' is not a valid module or alias name
Jan 25 09:32:22 Arch-DN init: Entering runlevel: 5
Jan 25 09:32:23 Arch-DN powernowd: PowerNow Daemon v1.00, (c) 2003-2008 John Clemens
Jan 25 09:32:23 Arch-DN powernowd: Found 2 scalable units:  -- 1 'CPU' per scalable unit
Jan 25 09:32:23 Arch-DN powernowd:   cpu0: 800Mhz - 1200Mhz (2 steps)
Jan 25 09:32:23 Arch-DN powernowd:   cpu1: 800Mhz - 1200Mhz (2 steps)
Jan 25 09:32:33 Arch-DN kernel: [drm] DAC-6: set mode 1024x768 33
Jan 25 09:32:33 Arch-DN kernel: [drm] LVDS-8: set mode 1024x768 34
Jan 25 09:32:35 Arch-DN kernel: iwlagn 0000:0c:00.0: firmware: requesting iwlwifi-4965-2.ucode
Jan 25 09:32:35 Arch-DN kernel: iwlagn 0000:0c:00.0: loaded firmware version 228.61.2.24

thiagoc · 2010-01-26 00:26:21

My X freeze some times, it seems like when I'm using chromium. I'm using only Firefox now to test.

Here's messages.log from the last freeze:

Jan 25 20:42:38 shitbox kernel: Modules linked in: oss_usb oss_ich osscore ipv6 ipt_REJECT ipt_LOG xt_recent xt_tcpudp nf_conntrack_ipv4 nf_defrag_ipv4 xt_state n
f_conntrack iptable_filter ip_tables x_tables reiserfs usbhid hid i915 ac97_bus drm_kms_helper uhci_hcd drm i2c_algo_bit intel_agp thermal video output button pro
cessor sundance i2c_i801 sg ehci_hcd agpgart usbcore i2c_core shpchp pci_hotplug iTCO_wdt iTCO_vendor_support evdev e100 mii rtc_cmos rtc_core rtc_lib ext4 mbcach
e jbd2 crc16 sr_mod cdrom sd_mod ata_piix ata_generic pata_acpi libata scsi_mod [last unloaded: soundcore]
Jan 25 20:42:38 shitbox kernel:
Jan 25 20:42:38 shitbox kernel: Pid: 2875, comm: X Not tainted (2.6.32-ARCH #1)
Jan 25 20:42:38 shitbox kernel: EIP: 0060:[<f83e4415>] EFLAGS: 00013246 CPU: 0
Jan 25 20:42:38 shitbox kernel: EIP is at i915_gem_evict_everything+0xe5/0x120 [i915]
Jan 25 20:42:38 shitbox kernel: EAX: f6a7c000 EBX: f6457000 ECX: 00000000 EDX: 00006e6e
Jan 25 20:42:38 shitbox kernel: ESI: f69b5400 EDI: f6457e0c EBP: f6457e20 ESP: f6a7dda4
Jan 25 20:42:38 shitbox kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan 25 20:42:38 shitbox kernel: 00000000 00000008 f648edc0 00000008 f69eb120 f83e5a70 c104ec53 00000000
Jan 25 20:42:38 shitbox kernel: <0> c12b831c f69b56b0 00003286 f6461000 f69b5700 f67f35a0 f6457000 f83f0c36
Jan 25 20:42:38 shitbox kernel: <0> f36d5100 f6a69000 f64c7ae0 f35e0500 f6457000 f648edc0 f36d5000 f6a69000
Jan 25 20:42:38 shitbox kernel: [<f83e5a70>] ? i915_gem_execbuffer+0x830/0x1310 [i915]
Jan 25 20:42:38 shitbox kernel: [<c104ec53>] ? mod_timer+0x103/0x260
Jan 25 20:42:38 shitbox kernel: [<c12b831c>] ? __mutex_lock_slowpath+0x1ec/0x2c0
Jan 25 20:42:38 shitbox kernel: [<f83f0c36>] ? intel_mark_busy+0xa6/0xb0 [i915]
Jan 25 20:42:38 shitbox kernel: [<f8093298>] ? drm_ioctl+0x158/0x320 [drm]
Jan 25 20:42:38 shitbox kernel: [<f83e5240>] ? i915_gem_execbuffer+0x0/0x1310 [i915]
Jan 25 20:42:38 shitbox kernel: [<c100bc4b>] ? restore_i387_fxsave+0x6b/0x80
Jan 25 20:42:38 shitbox kernel: [<c10f1919>] ? vfs_ioctl+0x89/0xa0
Jan 25 20:42:38 shitbox kernel: [<c10f1a99>] ? do_vfs_ioctl+0x79/0x5c0
Jan 25 20:42:38 shitbox kernel: [<c100c1d2>] ? restore_i387_xstate+0x122/0x270
Jan 25 20:42:38 shitbox kernel: [<c10e3936>] ? rw_verify_area+0x66/0xe0
Jan 25 20:42:38 shitbox kernel: [<c10f2056>] ? sys_ioctl+0x76/0x90
Jan 25 20:42:38 shitbox kernel: [<c10039f3>] ? sysenter_do_call+0x12/0x28
Jan 25 20:42:38 shitbox kernel: ---[ end trace 8a5d184ebf73dcf7 ]---
Jan 25 20:43:02 shitbox logger: PowerButton pressed: PWRF
Jan 25 20:43:02 shitbox init: Switching to runlevel: 0

Using testing repo.

newcar · 2010-01-26 04:03:58

Same problem here!

All up to date (no testing repo), 64bits arch.

Im pissed, months like this now, blinking leds and all...

Had arch 32 bits for an entire year and no freeze. Could be it?

alphazo · 2010-01-26 09:25:17

Freeze again and without powernowd and acpi-freq! Googling for "i915 waking up sleeping" returns a lot of problems with i915 driver and/or KMS.

davidm · 2010-01-26 16:14:03

thiagoc wrote:

My X freeze some times, it seems like when I'm using chromium. I'm using only Firefox now to test.

Out of curiousity has it happened again since you stopped using Chromium?

thiagoc · 2010-01-27 01:17:33

davidm wrote:

thiagoc wrote:
My X freeze some times, it seems like when I'm using chromium. I'm using only Firefox now to test.
Out of curiousity has it happened again since you stopped using Chromium?

No

It just happened again running firefox... when I opened a new tab, specifically.

I think this is a memory related issue, because it happened when I moved the scrollbar or opened a site in a new tab.

I was watching a live streamming video (flash) when it occurred, after the freeze I could still hear the streamming and log in through SSH.

Last log in messages:

Jan 26 22:56:47 shitbox kernel: Pid: 1931, comm: X Not tainted (2.6.32-ARCH #1)
Jan 26 22:56:47 shitbox kernel: EIP: 0060:[<f864e415>] EFLAGS: 00013246 CPU: 0
Jan 26 22:56:47 shitbox kernel: EIP is at i915_gem_evict_everything+0xe5/0x120 [i915]
Jan 26 22:56:47 shitbox kernel: EAX: f684c000 EBX: f6503000 ECX: 00000000 EDX: 00006f6f
Jan 26 22:56:47 shitbox kernel: ESI: f6b64400 EDI: f6503e0c EBP: f6503e20 ESP: f684dda4
Jan 26 22:56:47 shitbox kernel: DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068
Jan 26 22:56:47 shitbox kernel: 00000000 0000001c cab58700 0000001c f0460060 f864fa70 c1299e4c f684ddfc
Jan 26 22:56:47 shitbox kernel: <0> f684de4c 00000060 f683f600 f683fc00 00000060 f684de2c f6503000 0083fdb4
Jan 26 22:56:47 shitbox kernel: <0> d8651f80 f6534000 f6b86a80 cab58c80 f6503000 cab58700 d8651c00 f6534000
Jan 26 22:56:47 shitbox kernel: [<f864fa70>] ? i915_gem_execbuffer+0x830/0x1310 [i915]
Jan 26 22:56:47 shitbox kernel: [<c1299e4c>] ? unix_stream_sendmsg+0x20c/0x370
Jan 26 22:56:47 shitbox kernel: [<f858e298>] ? drm_ioctl+0x158/0x320 [drm]
Jan 26 22:56:47 shitbox kernel: [<f864f240>] ? i915_gem_execbuffer+0x0/0x1310 [i915]
Jan 26 22:56:47 shitbox kernel: [<c105ad70>] ? autoremove_wake_function+0x0/0x40
Jan 26 22:56:47 shitbox kernel: [<c10f1919>] ? vfs_ioctl+0x89/0xa0
Jan 26 22:56:47 shitbox kernel: [<c10f1a99>] ? do_vfs_ioctl+0x79/0x5c0
Jan 26 22:56:47 shitbox kernel: [<c105e03d>] ? __remove_hrtimer+0x2d/0xa0
Jan 26 22:56:47 shitbox kernel: [<c105ec2b>] ? hrtimer_try_to_cancel+0x6b/0xd0
Jan 26 22:56:47 shitbox kernel: [<c1044692>] ? do_setitimer+0x162/0x1f0
Jan 26 22:56:47 shitbox kernel: [<c10f2056>] ? sys_ioctl+0x76/0x90
Jan 26 22:56:47 shitbox kernel: [<c10039f3>] ? sysenter_do_call+0x12/0x28
Jan 26 22:56:47 shitbox kernel: ---[ end trace b46817c9fd248936 ]---

UPDATE: I just looked at Xorg.log.old and found this:

(EE) intel(0): Failed to submit batch buffer, expect rendering corruption or even a frozen display: No space left on device.

So, WTF? What means this message? If Xorg is refferring to space in disk (I think not), I have 6 GB available in / partition.

Last edited by thiagoc (2010-01-27 01:38:26)

lululaglue · 2010-01-28 18:13:08

Hi

I've same problem on my portable, Nec Versa KW300, with an Intel 945GM graphic card (xf86-video-intel-newest 2.10.0-2) with KMS and DualScreen.
I use Xfce and GDM, Firefox and Thunderbird, I don't use Chromium.

When X freeze, my mouse or keyboard do not respond, but i can connect with ssh, in my X log I have this :

(II) intel(0): EDID vendor "SEC", prod id 12869
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0   68.94  1280 1296 1344 1408  800 801 804 816 -hsync -vsync (49.0 kHz)
(II) intel(0): EDID vendor "SEC", prod id 12869
(II) intel(0): Printing DDC gathered Modelines:
(II) intel(0): Modeline "1280x800"x0.0   68.94  1280 1296 1344 1408  800 801 804 816 -hsync -vsync (49.0 kHz)
(II) intel(0): Allocate new frame buffer 2560x1024 stride 4096

Backtrace:
0: /usr/bin/Xorg (xorg_backtrace+0x3b) [0x809bd9b]
1: /usr/bin/Xorg (0x8048000+0x520e5) [0x809a0e5]
2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb779440c]
3: /usr/bin/Xorg (0x8048000+0x272a0) [0x806f2a0]
4: /usr/bin/Xorg (0x8048000+0x1a685) [0x8062685]
5: /lib/libc.so.6 (__libc_start_main+0xe6) [0xb73b8b86]
6: /usr/bin/Xorg (0x8048000+0x1a271) [0x8062271]

Fatal server error:
Caught signal 3 (Quit). Server aborting


Please consult the The X.Org Foundation support 
     at http://wiki.x.org
 for help. 
Please also check the log file at "/var/log/Xorg.0.log" for additional information.

(II) Macintosh mouse button emulation: Close
(II) UnloadModule: "evdev"
(II) UnloadModule: "synaptics"
(II) AT Translated Set 2 keyboard: Close
(II) UnloadModule: "evdev"
(II) Logitech Logitech USB Keyboard: Close
(II) UnloadModule: "evdev"
(II) Logitech Logitech USB Keyboard: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Video Bus: Close
(II) UnloadModule: "evdev"
(II) Power Button: Close
(II) UnloadModule: "evdev"
(II) Logitech USB-PS/2 Optical Mouse: Close
(II) UnloadModule: "evdev"

If I kill my X and restart Gdm (by ssh) I can open new session and work for a few hours.

thiagoc · 2010-02-01 21:05:43

I have noticed that the X crashes when I move the scrollbar of firefox/chrome with the mouse...

Anyone can confirm this?

4internetanonymity · 2010-02-10 06:03:43

thiagoc wrote:

I have noticed that the X crashes when I move the scrollbar of firefox/chrome with the mouse...
Anyone can confirm this?

You're not imagining this - moving the scroll bar in a browser is certainly one of the things that sets off this insane: "intel: failed to submit batch buffer" crap
I've been dealing with it for several weeks now, and I somehow figured it would work itself out. I'm using Intel 945GME Chipset and am completely up-to-date including testing.

We need a bug fix!

Last edited by 4internetanonymity (2010-02-10 06:04:01)

alphazo · 2010-02-11 21:06:25

So my system has been pretty stable for over two weeks using xf86-video-intel 2.9.1-1.

Today upgrade made me switched to extra/xf86-video-intel 2.10.0-1 and then within few hours I got my first freeze

Feb 11 21:52:08 Arch-DN kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Feb 11 21:52:08 Arch-DN kernel: render error detected, EIR: 0x00000000
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_wait_request] *ERROR* i915_wait_request returns -5 (awaiting 520473 at 520472)
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
....

I guess I should revert back to 2.9.1 and stick to it. Any thoughts?

Thanks
Alphazo

PS: There have been a couple of kernel updates in the meantime too!

Looking at http://bugs.archlinux.org/task/17705 I noticed that it appears to be fixed with libdrm 2.4.17-4 and xf86-video-intel 2.10.0-1. In the past, when I played with -newest version of Intel driver I also installed libdrm-newest-2.4.17-1. So I just replaced it by libdrm-2.4.17-4. Let see how it goes now

Last edited by alphazo (2010-02-11 21:31:12)

eldragon · 2010-02-12 02:13:32

alphazo wrote:

So my system has been pretty stable for over two weeks using xf86-video-intel 2.9.1-1.
Today upgrade made me switched to extra/xf86-video-intel 2.10.0-1 and then within few hours I got my first freeze
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung
Feb 11 21:52:08 Arch-DN kernel: render error detected, EIR: 0x00000000
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_wait_request] *ERROR* i915_wait_request returns -5 (awaiting 520473 at 520472)
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
Feb 11 21:52:08 Arch-DN kernel: [drm:i915_gem_execbuffer] *ERROR* Execbuf while wedged
....
I guess I should revert back to 2.9.1 and stick to it. Any thoughts?
Thanks
Alphazo
PS: There have been a couple of kernel updates in the meantime too!
Looking at http://bugs.archlinux.org/task/17705 I noticed that it appears to be fixed with libdrm 2.4.17-4 and xf86-video-intel 2.10.0-1. In the past, when I played with -newest version of Intel driver I also installed libdrm-newest-2.4.17-1. So I just replaced it by libdrm-2.4.17-4. Let see how it goes now

yes, well, the commit that fixes the issue is a few days old. i was amazed at the speed it got backported. i guess the packager was suffering from the issue and was following its outcome pretty close (like i did).

new libdrm from the arch repos should fix your issue. more info here: https://bugs.freedesktop.org/show_bug.cgi?id=25475

alphazo · 2010-02-12 06:34:47

I went through the bug report you gave a link for. Does that mean I'm safe with libdrm 2.4.17-4 and xf86-video-intel 2.10.0-1 or do I have to upgrade them to another specific version? What about mesa package?

eldragon · 2010-02-12 11:15:20

your bug should be resolved with latest libdrm. if you are still experiencing issues, then you should file a new bug report about it.

in my case, this was fixed with the mentioned patch.

Arch Linux

#26 2010-01-16 14:23:30

Re: How to debug daily freezes?

#27 2010-01-16 15:15:41

Re: How to debug daily freezes?

#28 2010-01-19 09:40:23

Re: How to debug daily freezes?

#29 2010-01-19 09:44:56

Re: How to debug daily freezes?

#30 2010-01-19 11:09:41

Re: How to debug daily freezes?

#31 2010-01-19 11:29:44

Re: How to debug daily freezes?

#32 2010-01-19 13:48:58

Re: How to debug daily freezes?

#33 2010-01-19 13:55:34

Re: How to debug daily freezes?

#34 2010-01-19 18:50:01

Re: How to debug daily freezes?

#35 2010-01-25 15:35:36

Re: How to debug daily freezes?

#36 2010-01-26 00:26:21

Re: How to debug daily freezes?

#37 2010-01-26 04:03:58

Re: How to debug daily freezes?

#38 2010-01-26 09:25:17

Re: How to debug daily freezes?

#39 2010-01-26 16:14:03

Re: How to debug daily freezes?

#40 2010-01-27 01:17:33

Re: How to debug daily freezes?

#41 2010-01-28 18:13:08

Re: How to debug daily freezes?

#42 2010-02-01 21:05:43

Re: How to debug daily freezes?

#43 2010-02-10 06:03:43

Re: How to debug daily freezes?

#44 2010-02-11 21:06:25

Re: How to debug daily freezes?

#45 2010-02-12 02:13:32

Re: How to debug daily freezes?

#46 2010-02-12 06:34:47

Re: How to debug daily freezes?

#47 2010-02-12 11:15:20

Re: How to debug daily freezes?

Board footer