https://bugzilla.novell.com/show_bug.cgi?id=723777
https://bugzilla.novell.com/show_bug.cgi?id=723777#c9
--- Comment #9 from Harald Koenig 2011-10-17 09:58:44 UTC ---
just a few observations from last friday's night only -- this weekend the
weather was just too good... :-(
* reading the Xorg.0.log, Egbert and I guess that the evdev crash might be
caused in Xserver restart since X does an unload to evdev and other drivers 1st
before reinitializing (despite that X is running with "-noreset" option --
strange ?!)
"proof" of idea: if I start "xterm -display :0" on VC2 to keep at least one
xclient connected, the Xserver does not crash anymore and the installations
finishes as expected!
BUT: I can't reproduce the X crash in the install environment with a 2nd
Xserver by running
X :1 -noreset .... (all other options from :0) &
xterm -display :1 &
and then "exit" in xterm as single client. even without "-noreset" the Xserver
:1 keeps running for multiple start/stop of that single xterm.
* question: what's going on and who exits/crashes first (yast or X).
idea: run strace on both yast and xserver with timestamps etc.
and check output for the sequence of events.
BUT: running strace with foll output of all syscalls covers the problem,
installation works ok, no Xserver crash anymore
so the problem might be some race condition ?!?
next planned tests (TBD):
- run strace only either on yast or Xserver -- which one causes the issues ?
- run strace with "-e write" or "-e connect" to reduce output (still show
signals like SIGSEGV),
to keep the chance to catch the race
- attach gdb to the running X :0 and set a breakpoint to the evdev stuff to get
some more info why it runns into that code...
- other ideas ?
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.