[ubuntu-x] Ibex x server a little TOO hot-pluggy?

[Bryce Harrington]

On Mon, Nov 03, 2008 at 08:28:30PM -0800, Dan Kegel wrote:
> On Mon, Nov 3, 2008 at 11:23 AM, Dan Kegel <dank at kegel.com> wrote:
> >> Something is definitely crashing either X or the kernel and causing X to
> >> restart.  So that's certainly one issue you'll want to investigate.
> 
> Found it: https://bugs.freedesktop.org/show_bug.cgi?id=13952
> 
> By using startx, or with tail -f on Xorg.log (it rolls over too
> quickly otherwise), I see
> 
> (II) intel(0): DDCModeFromDetailedTiming: 1024x768 Warning: We only
> handle seperate sync.
> 
> Backtrace:
> 0: /usr/X11R6/bin/X(xf86SigHandler+0x79) [0x80c3009]
> 1: [0xb7fea400]
> 2: /usr/X11R6/bin/X(VidModeGetNumOfModes+0x40) [0x80c8270]
> 3: /usr/lib/xorg/modules/extensions//libextmod.so [0xb7b340d0]
> 4: /usr/X11R6/bin/X(Dispatch+0x34f) [0x808c89f]
> 5: /usr/X11R6/bin/X(main+0x47d) [0x8071d1d]
> 6: /lib/tls/i686/cmov/libc.so.6(__libc_start_main+0xe5) [0xb7bf1685]
> 7: /usr/X11R6/bin/X [0x8071101]
> Saw signal 11.  Server aborting.
> 
> Sadly, even with every xorg*-dbg package installed, I see no
> line numbers in the stack dump.

Yeah, unfortunately the stack routines that Xorg has access to (from
libc iirc) don't provide any more detail than this.

However, you can attach to the X process and get a better stack trace
through gdb.  See http://wiki.ubuntu.com/X/Backtracing for directions.
 
> Here's how to reproduce:
> run any Wine conformance test that creates a window
> while the monitor is unplugged.  For instance,
>  $ cd dlls/user32/tests
>  $ rm static.ok
>  $ make static.ok
> will run fine with the cable plugged in, and crash with it unplugged.
> 
> Wine's log file, generated with WINEDEBUG=+all,+synchronous make test,
> seems to indicate the crash is generated very quickly after
> wine starts using X, probably while it is getting a list of
> video modes:
> 
> 0018:trace:module:load_dll Found L"C:\\windows\\system32\\winex11.drv"
> for L"winex11.drv" at 0x60a70000, count=2
> ...
> 0018:trace:x11settings:X11DRV_Settings_SetHandlers Resolution settings
> now handled by: NoRes
> 0018:trace:x11settings:X11DRV_Settings_SetHandlers Initialized new
> display modes array
> 0018:trace:x11settings:X11DRV_Settings_AddOneMode initialized mode 0:
> 1400x1050x32 @60 Hz (NoRes)
> make: *** wait: No child processes.  Schluss.
> make: *** Warte auf noch nicht beendete Prozesse...
> make: *** wait: No child processes.  Schluss.
> 0009: *killed* exit_code=0
> 0008: *process killed*
> XIO:  fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0"
>       after 86 requests (85 known processed) with 0 events remaining.
> 
> I am at your disposal if you need me to test a fix.
> Otherwise I'm off to the store to buy an nvidia card :-)

Thanks for reporting it upstream.  You might want to create your own bug
report rather than appending it to 13952 even though your symptoms seem
the same as that reporter, because upstream likes to handle bugs
regarding different video chipsets as separate bug reports, and because
if you file against -intel instead of xserver, you may be more likely to
get a faster response.

You may also want to ask on #intel-gfx for help with this if you don't
get a reply to your bug report within a day or two.

Bryce