Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
found 375460 1:1.0.2-8 retitle 375460 server crash when the device configured as core pointer is a keyboard kthxbye On Fri, Jun 30, 2006 at 13:34:20 +0200, Marcel Sebek wrote: > On Fri, Jun 30, 2006 at 12:44:45PM +0200, Michel Dänzer wrote: > > The backtrace looks input related, and indeed, looking at the log file, > > it looks like /dev/input/event1 no longer represents a mouse but a > > keyboard, so the X server ends up running without a core pointer and > > probably chokes on that. > > > > Yes, exactly. event1/2 is switched in the new kernel. The same happened > to me once in the past, but IIRC the xserver printed some reasonable > warning about missing core pointer, so I found that easily. > > I've created a simple udev rule and now have mouse on > /dev/input/psmouse. I should have done it when I started using evdev > interface. Should we consider this a configuration issue? It looks like input-hotplug, or using persistent device names, would prevent this kind of problems. Cheers, Julien signature.asc Description: Digital signature
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Thu, Feb 28, 2008 at 01:55:16PM +0100, Julien Cristau wrote: > found 375460 1:1.0.2-8 > retitle 375460 server crash when the device configured as core pointer is a > keyboard > kthxbye > > On Fri, Jun 30, 2006 at 13:34:20 +0200, Marcel Sebek wrote: > > > On Fri, Jun 30, 2006 at 12:44:45PM +0200, Michel Dänzer wrote: > > > The backtrace looks input related, and indeed, looking at the log file, > > > it looks like /dev/input/event1 no longer represents a mouse but a > > > keyboard, so the X server ends up running without a core pointer and > > > probably chokes on that. > > > > > > > Yes, exactly. event1/2 is switched in the new kernel. The same happened > > to me once in the past, but IIRC the xserver printed some reasonable > > warning about missing core pointer, so I found that easily. > > > > I've created a simple udev rule and now have mouse on > > /dev/input/psmouse. I should have done it when I started using evdev > > interface. > > Should we consider this a configuration issue? It looks like > input-hotplug, or using persistent device names, would prevent this kind > of problems. It shouldn't be a configuration issue if it brings down the server. We should try and revisit this when we move the input-hotplug though, if that's what'll really fix it. - David Nusinow -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Wed, Jun 13, 2007 at 11:52:55AM +0200, Marcel Sebek wrote: > I can still reproduce the segfault when I set mouse event device to > the one used by keyboard or when I don't set the device at all. When running latest xserver-xorg-core (1.3) and drivers ? Could you catch a backtrace of the crash? Either from the end of Xorg.0.log (or Xorg.0.log.old if X already restarted) or (better) with gdb? Also please send the whole output of /usr/share/bug/xserver-xorg-script 3>&1 so that we see your full config and log. This script will include /var/log/Xorg.0.log, so it would be good to run it right after the crash and before restarting a X, so that the log is exact one of the crashed session. Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Thu, Jul 05, 2007 at 08:05:49PM +0200, Brice Goglin wrote: > On Wed, Jun 13, 2007 at 11:52:55AM +0200, Marcel Sebek wrote: > > I can still reproduce the segfault when I set mouse event device to > > the one used by keyboard or when I don't set the device at all. > > When running latest xserver-xorg-core (1.3) and drivers ? Yes, I upgraded to the latest xserver packages from unstable. > > Could you catch a backtrace of the crash? Either from the end of Xorg.0.log > (or Xorg.0.log.old if X already restarted) or (better) with gdb? I used core file, not running X in gdb directly, and xserver-xorg-core-dbg. > > Also please send the whole output of > /usr/share/bug/xserver-xorg-script 3>&1 > so that we see your full config and log. This script will include > /var/log/Xorg.0.log, so it would be good to run it right after the > crash and before restarting a X, so that the log is exact one of the > crashed session. Both gdb and output of this script attached. -- Marcel Sebek Contents of /var/lib/x11/X.roster: xserver-xorg /etc/X11/X target does not match checksum in /var/lib/x11/X.md5sum. X server symlink status: lrwxrwxrwx 1 root root 13 2006-06-03 12:08 /etc/X11/X -> /usr/bin/Xorg -rwxr-xr-x 1 root root 1736280 2007-07-05 07:32 /usr/bin/Xorg Contents of /var/lib/x11/xorg.conf.roster: xserver-xorg VGA-compatible devices on PCI bus: 01:00.0 VGA compatible controller: ATI Technologies Inc Rage 128 Pro Ultra TF /etc/X11/xorg.conf does not match checksum in /var/lib/x11/xorg.conf.md5sum. Xorg X server configuration file status: -rw-r--r-- 1 root root 2809 2007-07-06 11:01 /etc/X11/xorg.conf Contents of /etc/X11/xorg.conf: # /etc/X11/xorg.conf (xorg 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 /etc/X11/xorg.conf manual page. # (Type "man /etc/X11/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 "Files" FontPath"unix/:7100" FontPath"unix/:7101" EndSection Section "Module" # Load"bitmap" Load"dbe" Load"ddc" Load"dri" Load"extmod" # Load"freetype" Load"glx" Load"int10" Load"record" # Load"type1" Load"vbe" Load"evdev" EndSection Section "InputDevice" Identifier "ps2-kbd" Driver "kbd" Option "CoreKeyboard" Option "XkbRules" "xorg" Option "XkbModel" "pc105" Option "XkbLayout" "us,cz" Option "XkbOptions""grp:alt_shift_toggle" Option "AutoRepeat""250 30" EndSection Section "InputDevice" Identifier "mouse" Driver "evdev" Option "CorePointer" # These commented lines are normally uncommented # Option "evBits""+1-2" # Option "keyBits" "~272-287" # Option "relBits" "~0-2 ~6 ~8" # Option "HWheelRelativeAxisButtons" "8 9" # Option "Pass" "3" # And this line is here just for testing (event3 is keyboard) Option "Device""/dev/input/event3" EndSection Section "Device" Identifier "ATI Technologies, Inc. Rage 128 Pro Ultra TF" Driver "ati" BusID "PCI:1:0:0" Option "agpMode" "4" EndSection Section "Monitor" Identifier "Generic Monitor" Option "DPMS" HorizSync 30-70 VertRefresh 50-160 EndSection Section "Screen" Identifier "Default Screen" Device "ATI Technologies, Inc. Rage 128 Pro Ultra TF" Monitor "Generic Monitor" DefaultDepth24 SubSection "Display" Depth 1 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 4 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 8 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 15 Modes "1024x768" "800x600" "640x480" EndSubSection SubSection "Display" Depth 16 Modes "1024x768" "800x600" "640x480" EndSubSection
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Fri, Jul 06, 2007 at 01:54:13PM +0200, Brice Goglin wrote:
> Marcel Sebek wrote:
> > Both gdb and output of this script attached.
> > [...]
> >
> > Backtrace:
> > 0: /usr/bin/X11/X(xf86SigHandler+0x81) [0x80c8591]
> > 1: [0xe420]
> > 2: /usr/bin/X11/X(main+0x6bf) [0x80770af]
> > 3: /lib/i686/cmov/libc.so.6(__libc_start_main+0xdc) [0xb7df1ebc]
> > 4: /usr/bin/X11/X(FontFileCompleteXLFD+0x1e5) [0x80761a1]
> >
> > Fatal server error:
> > Caught signal 11. Server aborting
> >
> > [...]
> >
> > Core was generated by `X'.
> > Program terminated with signal 11, Segmentation fault.
> > #0 0x08084a0e in NumMotionEvents () at ../../dix/devices.c:349
> > 349 ../../dix/devices.c: No such file or directory.
> > in ../../dix/devices.c
> > (gdb) bt
> > #0 0x08084a0e in NumMotionEvents () at ../../dix/devices.c:349
> > #1 0x080770af in main (argc=1, argv=0xbfd0ffb4, envp=0xb7f79cc0)
> > at ../../dix/main.c:473
> > (gdb) quit
> >
>
> Please enter 'bt full' here so that gdb dumps the whole stack of calls
> and arguments.
>
Here is the output.
(gdb) bt full
#0 0x08084a0e in NumMotionEvents () at ../../dix/devices.c:349
No locals.
#1 0x080770af in main (argc=1, argv=0xbfd0ffb4, envp=0xb7f79cc0)
at ../../dix/main.c:473
pScreen =
i =
error = -1076822084
xauthfile =
alwaysCheckForInput = {0, 1}
--
Marcel Sebek
signature.asc
Description: Digital signature
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
Hi, About a year ago, you reported a bug to the Debian BTS regarding Xserver crashing because kernel 2.6.17 change numbering of input events. Did you reproduce this problem recently? With latest xserver-xorg-core and other Xorg packages in unstable? Thanks, Brice -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Mon, May 28, 2007 at 11:35:31PM +0200, Brice Goglin wrote: > About a year ago, you reported a bug to the Debian BTS regarding Xserver > crashing because kernel 2.6.17 change numbering of input events. Did you > reproduce this problem recently? With latest xserver-xorg-core and other > Xorg packages in unstable? > Hi. I can still reproduce the segfault when I set mouse event device to the one used by keyboard or when I don't set the device at all. Note that I use evdev driver for the mouse. -- Marcel Sebek signature.asc Description: Digital signature
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
Package: xserver-xorg Version: 1:7.0.22 Severity: important -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi. I upgraded kernel to 2.6.17 and xserver stopped working. I tried both DRI enabled and disabled. I also tried disabling all modules and removing all font directories, it didn't help. The Xserver receives SIGSEG: Backtrace: 0: /usr/bin/X11/X(xf86SigHandler+0x88) [0x80b8d98] 1: [0xe420] 2: /usr/bin/X11/X(main+0x5cc) [0x806e46c] 3: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd0) [0xb7d51eb0] 4: /usr/bin/X11/X(FontFileCompleteXLFD+0x91) [0x806d881] Fatal server error: Caught signal 11. Server aborting This is the trace with ati driver. I also tried vesa, the trace also started with xf86SigHandler+0x88 and ended with FontFileCompleteXLFD, but it has a few more lines between. - -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.16-ck3 Locale: LANG=C, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Versions of packages xserver-xorg depends on: ii debconf 1.5.2 Debian configuration management sy ii x11-common 1:7.0.22X Window System (X.Org) infrastruc ii xbase-clients1:7.0.1-2 miscellaneous X clients ii xkb-data 0.8-5 X Keyboard Extension (XKB) configu ii xserver-xorg-core1:1.0.2-8 X.Org X server -- core server ii xserver-xorg-input-evdev [xs 1:1.0.0.5-2 X.Org X server -- evdev input driv ii xserver-xorg-input-kbd [xser 1:1.0.1.3-2 X.Org X server -- keyboard input d ii xserver-xorg-video-ati [xser 1:6.5.8.0-1 X.Org X server -- ATI display driv Versions of packages xserver-xorg recommends: pn discover1 | discover (no description available) pn laptop-detect (no description available) pn mdetect(no description available) pn xresprobe (no description available) - -- debconf information: xserver-xorg/multiple_possible_x-drivers: * xserver-xorg/config/monitor/use_sync_ranges: true * xserver-xorg/config/inputdevice/mouse/port: /dev/input/mice xserver-xorg/config/monitor/lcd: false xserver-xorg/config/doublequote_in_string_error: xserver-xorg/config/monitor/screen-size: 17 inches (430 mm) * shared/default-x-server: xserver-xorg xserver-xorg/autodetect_monitor: true * xserver-xorg/config/inputdevice/mouse/protocol: ExplorerPS/2 shared/no_known_x-server: * xserver-xorg/config/display/default_depth: 24 * xserver-xorg/config/display/modes: 1024x768, 800x600, 640x480 xserver-xorg/config/device/bus_id_error: xserver-xorg/config/inputdevice/keyboard/internal: * xserver-xorg/config/monitor/vert-refresh: 50-160 * xserver-xorg/config/inputdevice/keyboard/options: * xserver-xorg/autodetect_keyboard: false * xserver-xorg/config/device/use_fbdev: false * xserver-xorg/config/inputdevice/keyboard/variant: xserver-xorg/config/nonnumeric_string_error: xserver-xorg/config/fontpath/fontserver: * xserver-xorg/config/inputdevice/keyboard/layout: us,cz * xserver-xorg/config/modules: bitmap, dbe, ddc, dri, extmod, freetype, glx, int10, record, type1, vbe * xserver-xorg/config/monitor/identifier: Generic Monitor * xserver-xorg/config/inputdevice/mouse/emulate3buttons: false * xserver-xorg/autodetect_mouse: true * xserver-xorg/config/monitor/horiz-sync: 30-70 * xserver-xorg/config/device/video_ram: xserver-xorg/config/monitor/range_input_error: * xserver-xorg/config/write_dri_section: true * xserver-xorg/config/inputdevice/keyboard/model: pc104 * xserver-xorg/config/device/driver: ati * xserver-xorg/config/device/identifier: ATI Technologies, Inc. Rage 128 Pro Ultra TF * xserver-xorg/config/monitor/selection-method: Advanced xserver-xorg/config/null_string_error: shared/multiple_possible_x-servers: * xserver-xorg/config/device/bus_id: PCI:1:0:0 * xserver-xorg/config/write_files_section: true * xserver-xorg/autodetect_video_card: true xserver-xorg/config/monitor/mode-list: 1024x768 @ 60Hz * xserver-xorg/config/inputdevice/keyboard/rules: xorg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.3 (GNU/Linux) iD4DBQFEn3jCi2PKBl+Ic14RAnllAJimCenkNOvWTdKUIjILY6oj6z0YAKCATw4G IUYdiTk95RxlBZx0OLpoOg== =qlPN -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote: > > I upgraded kernel to 2.6.17 and xserver stopped working. I tried both > DRI enabled and disabled. I also tried disabling all modules and removing > all font directories, it didn't help. > > The Xserver receives SIGSEG: > > Backtrace: > 0: /usr/bin/X11/X(xf86SigHandler+0x88) [0x80b8d98] > 1: [0xe420] > 2: /usr/bin/X11/X(main+0x5cc) [0x806e46c] > 3: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd0) [0xb7d51eb0] > 4: /usr/bin/X11/X(FontFileCompleteXLFD+0x91) [0x806d881] > > Fatal server error: > Caught signal 11. Server aborting > > > This is the trace with ati driver. I also tried vesa, the trace also > started with xf86SigHandler+0x88 and ended with FontFileCompleteXLFD, > but it has a few more lines between. Please provide the full log file and try and get a backtrace with gdb. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Tue, Jun 27, 2006 at 11:38:15AM +0200, Michel Dänzer wrote: > On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote: > > > > I upgraded kernel to 2.6.17 and xserver stopped working. I tried both > > DRI enabled and disabled. I also tried disabling all modules and removing > > all font directories, it didn't help. > > > > The Xserver receives SIGSEG: > > > > Backtrace: > > 0: /usr/bin/X11/X(xf86SigHandler+0x88) [0x80b8d98] > > 1: [0xe420] > > 2: /usr/bin/X11/X(main+0x5cc) [0x806e46c] > > 3: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xd0) [0xb7d51eb0] > > 4: /usr/bin/X11/X(FontFileCompleteXLFD+0x91) [0x806d881] > > > > Fatal server error: > > Caught signal 11. Server aborting > > > > > > This is the trace with ati driver. I also tried vesa, the trace also > > started with xf86SigHandler+0x88 and ended with FontFileCompleteXLFD, > > but it has a few more lines between. > > Please provide the full log file and try and get a backtrace with gdb. > Full log and gdb bt attached. The backtrace was gained from core file because running xserver in gdb resulted in keyboard hard freeze (no sysrq). -- Marcel Sebek X Window System Version 7.0.0 Release Date: 21 December 2005 X Protocol Version 11, Revision 0, Release 7.0 Build Operating System:Linux 2.6.12-1-686 i686 Current Operating System: Linux penguin 2.6.17 #3 PREEMPT Mon Jun 26 07:38:42 CEST 2006 i686 Build Date: 16 March 2006 Before reporting problems, check http://wiki.x.org to make sure that you have the latest version. Module Loader present 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: Mon Jun 26 07:43:47 2006 (==) Using config file: "/etc/X11/xorg.conf" (==) ServerLayout "Default Layout" (**) |-->Screen "Default Screen" (0) (**) | |-->Monitor "Generic Monitor" (**) | |-->Device "ATI Technologies, Inc. Rage 128 Pro Ultra TF" (**) |-->Input Device "ps2-kbd" (**) |-->Input Device "ps2-mouse" (WW) The directory "/usr/share/fonts/X11/cyrillic" does not exist. Entry deleted from font path. (WW) The directory "/usr/lib/X11/fonts/cyrillic" does not exist. Entry deleted from font path. (WW) `fonts.dir' not found (or not valid) in "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID". Entry deleted from font path. (Run 'mkfontdir' on "/var/lib/defoma/x-ttcidfont-conf.d/dirs/CID"). (**) FontPath set to "/usr/share/fonts/X11/misc,/usr/lib/X11/fonts/misc,/usr/lib/X11/fonts/75dpi/:unscaled,/usr/share/fonts/X11/Type1,/usr/lib/X11/fonts/Type1,/usr/share/fonts/X11/75dpi,/usr/lib/X11/fonts/75dpi,/var/lib/defoma/x-ttcidfont-conf.d/dirs/TrueType,/usr/share/fonts/X11/misc/,/usr/share/fonts/X11/TTF/,/usr/share/fonts/X11/OTF,/usr/share/fonts/X11/Type1/,/usr/share/fonts/X11/CID/,/usr/share/fonts/X11/100dpi/,/usr/share/fonts/X11/75dpi/" (==) RgbPath set to "/usr/share/X11/rgb" (==) ModulePath set to "/usr/lib/xorg/modules" (**) Option "StandbyTime" "10" (**) Option "OffTime" "12" (II) Module ABI versions: X.Org ANSI C Emulation: 0.2 X.Org Video Driver: 0.8 X.Org XInput driver : 0.5 X.Org Server Extension : 0.2 X.Org Font Renderer : 0.4 (II) Loader running on linux (II) LoadModule: "bitmap" (II) Loading /usr/lib/xorg/modules/fonts/libbitmap.so (II) Module bitmap: vendor="X.Org Foundation" compiled for 7.0.0, module version = 1.0.0 Module class: X.Org Font Renderer ABI class: X.Org Font Renderer, version 0.4 (II) Loading font Bitmap (II) LoadModule: "pcidata" (II) Loading /usr/lib/xorg/modules/libpcidata.so (II) Module pcidata: vendor="X.Org Foundation" compiled for 7.0.0, module version = 1.0.0 ABI class: X.Org Video Driver, version 0.8 (--) using VT number 7 (II) PCI: PCI scan (all values are in hex) (II) PCI: 00:00:0: chip 1106,0305 card 1019,0987 rev 02 class 06,00,00 hdr 00 (II) PCI: 00:01:0: chip 1106,8305 card , rev 00 class 06,04,00 hdr 01 (II) PCI: 00:07:0: chip 1106,0686 card 1106, rev 22 class 06,01,00 hdr 80 (II) PCI: 00:07:1: chip 1106,0571 card 1106,0571 rev 10 class 01,01,8a hdr 00 (II) PCI: 00:07:4: chip 1106,3057 card 1019,0987 rev 30 class 06,00,00 hdr 00 (II) PCI: 00:07:5: chip 1106,3058 card 1019,0987 rev 20 class 04,01,00 hdr 00 (II) PCI: 00:09:0: chip 10ec,8139 card 10ec,8139 rev 10 class 02,00,00 hdr 00 (II) PCI: 00:0b:0: chip 13f6,0111 card 13f6,0111 rev 10 class 04,01,00 hdr 00 (II) PCI: 00:0d:0: chip 1106,3038 card 1106,3038 rev 61 class 0c,03,00 hdr 80 (II) PCI: 00:0d:1: chip 1106,3038 card 1106,3038 rev 61 class 0c,03,00 hdr 80 (II) PCI: 00:0d:2: chip 1106,3104 card 1106,3104 rev 63 class 0c,03,20 hdr 80 (II) PCI: 01:00:0: chip 1002,5446 card 174b,7106 rev 00 class 03,00,00 hdr 00 (II) PCI: End of PCI scan (II) Host-to-PCI bridge: (II) Bus 0: bridge is at (0:0:0), (0,0,1), BCTRL: 0x0008 (VGA_EN is
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Tue, 2006-06-27 at 16:25 +0200, Marcel Sebek wrote: > On Tue, Jun 27, 2006 at 11:38:15AM +0200, Michel Dänzer wrote: > > On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote: > > > > > > This is the trace with ati driver. I also tried vesa, the trace also > > > started with xf86SigHandler+0x88 and ended with FontFileCompleteXLFD, > > > but it has a few more lines between. > > > > Please provide the full log file and try and get a backtrace with gdb. > > > > Full log and gdb bt attached. The backtrace was gained from core > file because running xserver in gdb resulted in keyboard hard freeze > (no sysrq). Yeah, you can only do that from a remote login, or you end up in a dead lock where gdb stops execution of the X server, which is what provides interaction with gdb... The backtrace looks input related, and indeed, looking at the log file, it looks like /dev/input/event1 no longer represents a mouse but a keyboard, so the X server ends up running without a core pointer and probably chokes on that. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
On Fri, Jun 30, 2006 at 12:44:45PM +0200, Michel Dänzer wrote: > On Tue, 2006-06-27 at 16:25 +0200, Marcel Sebek wrote: > > On Tue, Jun 27, 2006 at 11:38:15AM +0200, Michel Dänzer wrote: > > > On Mon, 2006-06-26 at 08:03 +0200, Marcel Sebek wrote: > > > > > > > > This is the trace with ati driver. I also tried vesa, the trace also > > > > started with xf86SigHandler+0x88 and ended with FontFileCompleteXLFD, > > > > but it has a few more lines between. > > > > > > Please provide the full log file and try and get a backtrace with gdb. > > > > > > > Full log and gdb bt attached. The backtrace was gained from core > > file because running xserver in gdb resulted in keyboard hard freeze > > (no sysrq). > > Yeah, you can only do that from a remote login, or you end up in a dead > lock where gdb stops execution of the X server, which is what provides > interaction with gdb... > > The backtrace looks input related, and indeed, looking at the log file, > it looks like /dev/input/event1 no longer represents a mouse but a > keyboard, so the X server ends up running without a core pointer and > probably chokes on that. > Yes, exactly. event1/2 is switched in the new kernel. The same happened to me once in the past, but IIRC the xserver printed some reasonable warning about missing core pointer, so I found that easily. I've created a simple udev rule and now have mouse on /dev/input/psmouse. I should have done it when I started using evdev interface. Thank you for your time. -- Marcel Sebek signature.asc Description: Digital signature
Re: Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
> I upgraded kernel to 2.6.17 and xserver stopped working. Just for reference, I've upgraded to 2.6.17 but X is working same as it did before (i810). I'm sorry I don't have a suggestion for fixing your crash. Drew -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Processed: Re: Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup
Processing commands for [EMAIL PROTECTED]: > found 375460 1:1.0.2-8 Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup Bug marked as found in version 1:1.0.2-8. > retitle 375460 server crash when the device configured as core pointer is a > keyboard Bug#375460: Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup Changed Bug title to `server crash when the device configured as core pointer is a keyboard' from `Upgrade to linux kernel 2.6.17 makes Xserver crasing on startup'. > kthxbye Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
