Bug#595913:
Package: xserver-xorg-video-intel Severity: normal I do not have this bug anymore with new version of driver. Please close it. Thanks! -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Apr 12 2007 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1733468 Nov 12 02:27 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1076 Jun 6 2009 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier Configured Video Device EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Kernel version (/proc/version): Linux version 2.6.32-5-686 (Debian 2.6.32-28) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-4) ) #1 SMP Thu Nov 25 18:43:34 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 32024 May 26 2009 /var/log/Xorg.21.log -rw-r--r-- 1 root root 25309 Oct 12 2009 /var/log/Xorg.20.log -rw-r--r-- 1 root root 32922 Jul 18 20:22 /var/log/Xorg.1.log -rw-r--r-- 1 root root 45011 Dec 5 13:49 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.32.25-dsa-ia32 i686 Debian Current Operating System: Linux nfer 2.6.32-5-686 #1 SMP Thu Nov 25 18:43:34 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=UUID=3fc5fba1-9235-b8dd-0991-059d84ce49ac ro quiet acpi_osi=Linux Build Date: 12 November 2010 12:21:56AM xorg-server 2:1.7.7-9 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Nov 30 10:17:28 2010 (==) Using config file: /etc/X11/xorg.conf (==) Using system config directory /usr/share/X11/xorg.conf.d (==) No Layout section. Using the first Screen section. (**) |--Screen Default Screen (0) (**) | |--Monitor Configured Monitor (==) No device specified for screen Default Screen. Using the first device section listed. (**) | |--Device Configured Video Device (==) Automatically adding devices (==) Automatically enabling devices (==) FontPath set to: /usr/share/fonts/X11/misc, /usr/share/fonts/X11/cyrillic, /usr/share/fonts/X11/100dpi/:unscaled, /usr/share/fonts/X11/75dpi/:unscaled, /usr/share/fonts/X11/Type1, /usr/share/fonts/X11/100dpi, /usr/share/fonts/X11/75dpi, /var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType, built-ins (==) ModulePath set to /usr/lib/xorg/modules (II) The server relies on udev to provide the list of input devices. If no devices become available, reconfigure udev or disable AutoAddDevices. (II) Loader magic: 0x81ecca0 (II) Module ABI versions: X.Org ANSI C Emulation: 0.4 X.Org Video Driver: 6.0 X.Org XInput driver : 7.0 X.Org Server Extension : 2.0 (++) using VT number 7 (--) PCI:*(0:0:2:0) 8086:27a2:1179:ff04 Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller rev 3, Mem @ 0xdc10/524288, 0xc000/268435456, 0xdc20/262144, I/O @ 0x1800/8 (--) PCI: (0:0:2:1) 8086:27a6:1179:ff04 Intel Corporation Mobile 945GM/GMS/GME, 943/940GML Express Integrated Graphics Controller rev 3, Mem
Bug#595913: xserver-xorg-video-intel: X random crashes with 945GM
Package: xserver-xorg-video-intel Version: 2:2.12.0+legacy1-1 Severity: important Hi all, I have regular random X crashes, usually every day. It happens I think from the early 2010. With xserver-xorg-video-intel from squeeze I had error about batchbuffer input/output error. I looked through bug reports and tried to install legacy version from sid. And I still have crashes, but now with different error. Here are excerpts from logs: syslog: Sep 7 11:57:29 localhost kernel: [ 4380.608070] [drm:i915_hangcheck_elapsed] *ERROR* Hangcheck timer elapsed... GPU hung Sep 7 11:57:29 localhost kernel: [ 4380.608085] render error detected, EIR: 0x Sep 7 11:57:29 localhost kernel: [ 4380.608110] [drm:i915_do_wait_request] *ERROR* i915_do_wait_request returns -5 (awaiting 1181886 at 1181882) Sep 7 11:58:04 localhost gdm[2360]: WARNING: gdm_slave_xioerror_handler: Фатальная ошибка X - Перезапуск :0 Xorg.log: (EE) intel(0): Detected a hung GPU, disabling acceleration. another Xorg.log: (EE) intel(0): Detected a hung GPU, disabling acceleration. Backtrace: 0: /usr/bin/X (xorg_backtrace+0x3b) [0x80d920b] 1: /usr/bin/X (0x8048000+0x581d5) [0x80a01d5] 2: (vdso) (__kernel_rt_sigreturn+0x0) [0xb76e940c] 3: /usr/lib/xorg/modules/extensions/libdri2.so (0xb731a000+0x1d8c) [0xb731bd8c] 4: /usr/bin/X (0x8048000+0x38067) [0x8080067] 5: /usr/bin/X (0x8048000+0x1e92a) [0x806692a] 6: /lib/i686/cmov/libc.so.6 (__libc_start_main+0xe6) [0xb7418c76] 7: /usr/bin/X (0x8048000+0x1e511) [0x8066511] Segmentation fault at address (nil) Fatal server error: Caught signal 11 (Segmentation fault). Server aborting After crash I can switch to terminal and reboot computer. -- Package-specific info: /var/lib/x11/X.roster does not exist. /var/lib/x11/X.md5sum does not exist. X server symlink status: lrwxrwxrwx 1 root root 13 Apr 12 2007 /etc/X11/X - /usr/bin/Xorg -rwxr-xr-x 1 root root 1725304 Aug 24 18:04 /usr/bin/Xorg /var/lib/x11/xorg.conf.roster does not exist. VGA-compatible devices on PCI bus: 00:02.0 VGA compatible controller: Intel Corporation Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (rev 03) /var/lib/x11/xorg.conf.md5sum does not exist. Xorg X server configuration file status: -rw-r--r-- 1 root root 1076 Jun 6 2009 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # xorg.conf (X.Org X Window System server configuration file) # # This file was generated by dexconf, the Debian X Configuration tool, using # values from the debconf database. # # Edit this file with caution, and see the xorg.conf manual page. # (Type man xorg.conf at the shell prompt.) # # This file is automatically updated on xserver-xorg package upgrades *only* # if it has not been modified since the last upgrade of the xserver-xorg # package. # # If you have edited this file but would like it to be automatically updated # again, run the following command: # sudo dpkg-reconfigure -phigh xserver-xorg Section InputDevice Identifier Generic Keyboard Driver kbd Option XkbRules xorg Option XkbModel pc104 Option XkbLayout us EndSection Section InputDevice Identifier Configured Mouse Driver mouse EndSection Section Device Identifier Configured Video Device EndSection Section Monitor Identifier Configured Monitor EndSection Section Screen Identifier Default Screen Monitor Configured Monitor EndSection Kernel version (/proc/version): Linux version 2.6.32-5-686 (Debian 2.6.32-21) (b...@decadent.org.uk) (gcc version 4.3.5 (Debian 4.3.5-2) ) #1 SMP Wed Aug 25 14:28:12 UTC 2010 Xorg X server log files on system: -rw-r--r-- 1 root root 32024 May 26 2009 /var/log/Xorg.21.log -rw-r--r-- 1 root root 25309 Oct 12 2009 /var/log/Xorg.20.log -rw-r--r-- 1 root root 32922 Jul 18 20:22 /var/log/Xorg.1.log -rw-r--r-- 1 root root 22521 Sep 7 12:09 /var/log/Xorg.0.log Contents of most recent Xorg X server log file /var/log/Xorg.0.log: X.Org X Server 1.7.7 Release Date: 2010-05-04 X Protocol Version 11, Revision 0 Build Operating System: Linux 2.6.26-2-amd64 i686 Debian Current Operating System: Linux nfer 2.6.32-5-686 #1 SMP Wed Aug 25 14:28:12 UTC 2010 i686 Kernel command line: BOOT_IMAGE=/vmlinuz-2.6.32-5-686 root=UUID=3fc5fba1-9235-b8dd-0991-059d84ce49ac ro quiet acpi_osi=Linux Build Date: 24 August 2010 02:59:40PM xorg-server 2:1.7.7-4 (Julien Cristau jcris...@debian.org) Current version of pixman: 0.16.4 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: /var/log/Xorg.0.log, Time: Tue Sep 7 12:08:51 2010 (==) Using config file: /etc/X11/xorg.conf (==) Using system config
Bug#416503: enter behaves strange in vservers
I can't reporoduce this bug neither on amd64, nor on i386 with evdev version 1:1.1.2-6, xorg version 2:1.1.1-21 (versions etch released with). Problem disappeared after reboot; I rebooted computer a few days after bugreport. I can't recall, maybe I updated evdev before this. Anyway, I can't reproduce this bug for a month. В Вск, 22/04/2007 в 22:51 +0200, Brice Goglin пишет: Alexander Vlasov wrote: Sorry, nothing new. I can't reproduce this bug at all. Not sure I am following you here. You can't reproduce anymore??? on i386? with vservers? Or does the latest evdev driver fix the evdev/vserver problem, making this bug fixed? did you initial problem just go away? Brice
Bug#416503: enter behaves strange in vservers
Hello, Sorry, nothing new. I can't reproduce this bug at all. Anyway, I'm using input-evdev on one computer, so if bug will appear once again I'll inform you. В Суб, 21/04/2007 в 02:10 +0200, Brice Goglin пишет: Alexander Vlasov wrote: Could you try xserver-xorg-input-evdev currently in experimental (1:1.1.5-1)? Sure. I'll try today and write another followup. Which xserver-xorg-core are your running ? 2:1.1.1-20 ? Do you see any interesting difference in Xorg.0.log when switching from input+kbd to evdev? xserver-xorg-core: Version: 2:1.1.1-20 xserver-xorg: 1:7.1.0-15 it's current etch versions, no updates available. Xorg.log surely differs, but nothing seems wrong. Anyway, I'll retry this later and attach both logs. Without entering to vservers enter key also works ok. The bug could be caused by vserver then. I know almost nothing about vserver. Is it supposed to be stable? Do you have a way to disable some vserver features to try to locate the problem more precisely? Seems so. No, I see no ways to disable anything console-related. This problem exists even during vserver creation with newvserver. Thanks, Brice Not at all. I'll retry both input drivers later and I'll try to reproduce this bug on i386 arch. Hi Alexander, Did you find out anything new about this problem? Did you have a chance to try xserver-xorg-input-evdev currently in experimental (should enter unstable in a few days since xserver-xorg-core 1.3 arrived yesterday)? Thanks, Brice
Bug#416503: enter behaves strange in vservers
Hello, В Срд, 28/03/2007 в 20:58 +0200, Brice Goglin пишет: (adding the kernel team to Cc: in case they have some ideas). Alexander Vlasov wrote: I'm using vserver-enabled kernel on amd64 arch on my desktop and after switching to evdev from kbd+mouse I found strange enter behavior in vservers (after `vserver blahblah enter'): when I press enter it behaves like enter was pressed many times (~ 50), so working in vservers almost impossible. Could you try xserver-xorg-input-evdev currently in experimental (1:1.1.5-1)? Sure. I'll try today and write another followup. Which xserver-xorg-core are your running ? 2:1.1.1-20 ? Do you see any interesting difference in Xorg.0.log when switching from input+kbd to evdev? xserver-xorg-core: Version: 2:1.1.1-20 xserver-xorg: 1:7.1.0-15 it's current etch versions, no updates available. Xorg.log surely differs, but nothing seems wrong. Anyway, I'll retry this later and attach both logs. Without entering to vservers enter key also works ok. The bug could be caused by vserver then. I know almost nothing about vserver. Is it supposed to be stable? Do you have a way to disable some vserver features to try to locate the problem more precisely? Seems so. No, I see no ways to disable anything console-related. This problem exists even during vserver creation with newvserver. Thanks, Brice Not at all. I'll retry both input drivers later and I'll try to reproduce this bug on i386 arch.
Bug#416503: enter behaves strange in vservers
Package: xserver-xorg-input-evdev Version: 1:1.1.2-6 Hi. I'm using vserver-enabled kernel on amd64 arch on my desktop and after switching to evdev from kbd+mouse I found strange enter behavior in vservers (after `vserver blahblah enter'): when I press enter it behaves like enter was pressed many times (~ 50), so working in vservers almost impossible. I tried different terminals (xterm, rxvt, gnome-terminal) with same result, but this bug doesn't exists in console (real console, tty*). Without entering to vservers enter key also works ok. $ uname -a Linux zulu 2.6.18-4-vserver-amd64 #1 SMP Wed Feb 21 15:03:27 UTC 2007 x86_64 GNU/Linux Here follow parts of my xorg.conf: Section InputDevice Identifier keyboard Driver evdev Option evBits +1 Option keyBits ~1-255 ~352-511 Option Pass3 Option XkbModel evdev Option CoreKeyboard true EndSection Section InputDevice Identifier mouse Driver evdev Option evBits +1-2 Option keyBits ~272-287 Option relBits ~0-2 ~6 ~8 Option Pass3 Option CorePointer true EndSection Section ServerLayout Identifier Default Layout Screen Default Screen InputDevice keyboard InputDevice mouse EndSection -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
