Bug 13756 - Text console permanent corruption when killing Xserver.
Summary: Text console permanent corruption when killing Xserver.
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/intel (show other bugs)
Version: 7.3 (2007.09)
Hardware: x86-64 (AMD64) All
: medium normal
Assignee: Gordon Jin
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-12-20 15:30 UTC by Raúl
Modified: 2008-02-20 05:15 UTC (History)
3 users (show)

See Also:
i915 platform:
i915 features:


Attachments

Description Raúl 2007-12-20 15:30:52 UTC
Toshiba laptop, core 2 duo, Debian sid, Linux 2.6.24rc5, intel 965GM.

I hit bug http://bugs.freedesktop.org/show_bug.cgi?id=13511 and trying to recover control on the system I did sysrq-k which killed the Xserver. Instead of just killing the server, it crashed and restarted conveniently, but only in appearence, because on top of the SIGSEGV I had, the text consoles (vt1-6) went garbled and only some noise could be appreciated when writing.

I tried a post blindly, but since the text console was using frambuffer it was futile, also the text console returned to the garbled state when I did chvt7 and chvt back to the text console. The backtrace is:

#0  XkbEnableDisableControls (xkbi=0x190, change=<value optimized out>,
    newValues=<value optimized out>, changes=0x0, cause=0x7fffb40e99e0) at ../../xkb/xkbUtils.c:748
#1  0x0000000000540609 in XkbRemoveResourceClient (inDev=0x8514f0, id=<value optimized out>)
    at ../../xkb/xkbEvents.c:1038
#2  0x000000000044734b in CloseDevice (dev=0x8514f0) at ../../dix/devices.c:603
#3  0x000000000044753f in CloseDownDevices () at ../../dix/devices.c:625
#4  0x000000000056a4d3 in AbortServer () at ../../os/log.c:405
#5  0x000000000056ab25 in FatalError (f=0x573588 "Caught signal %d.  Server aborting\n")
    at ../../os/log.c:552
#6  0x00000000004755c9 in xf86SigHandler (signo=11)
    at ../../../../hw/xfree86/common/xf86Events.c:766
#7  <signal handler called>
#8  0x00002b3ff9b3ca92 in I830PutImage (pScrn=0x802390, src_x=0, src_y=0,
    drw_x=<value optimized out>, drw_y=<value optimized out>, src_w=<value optimized out>,
    src_h=480, drw_w=1021, drw_h=767, id=842094169,
    buf=0x2b40167d6000 '\020' <repeats 200 times>..., width=640, height=480, sync=1,
    clipBoxes=0x7fffb40ea360, data=0x846160, pDraw=0x2492830) at ../../src/i830_video.c:1319
#9  0x000000000049e332 in xf86XVPutImage (client=<value optimized out>, pDraw=0x2492830,
    pPort=0x847200, pGC=<value optimized out>, src_x=24576, src_y=-32752, src_w=4096, src_h=0,
    drw_x=129, drw_y=0, drw_w=<value optimized out>, drw_h=<value optimized out>, format=0x846ef0,
    data=0x2b40167d6000 '\020' <repeats 200 times>..., sync=1, width=<value optimized out>,
    height=<value optimized out>) at ../../../../hw/xfree86/common/xf86xv.c:1777
#10 0x00002b3ff8d61526 in ProcXvShmPutImage (client=0x27f0a70) at ../../Xext/xvdisp.c:1180
#11 0x000000000044e390 in Dispatch () at ../../dix/dispatch.c:502
#12 0x0000000000436b8d in main (argc=8, argv=0x7fffb40eaa38, envp=<value optimized out>)
    at ../../dix/main.c:452
#0  XkbEnableDisableControls (xkbi=0x190, change=<value optimized out>,
    newValues=<value optimized out>, changes=0x0, cause=0x7fffb40e99e0) at ../../xkb/xkbUtils.c:748
#1  0x0000000000540609 in XkbRemoveResourceClient (inDev=0x8514f0, id=<value optimized out>)
    at ../../xkb/xkbEvents.c:1038
#2  0x000000000044734b in CloseDevice (dev=0x8514f0) at ../../dix/devices.c:603
#3  0x000000000044753f in CloseDownDevices () at ../../dix/devices.c:625
#4  0x000000000056a4d3 in AbortServer () at ../../os/log.c:405
#5  0x000000000056ab25 in FatalError (f=0x573588 "Caught signal %d.  Server aborting\n")
    at ../../os/log.c:552
#6  0x00000000004755c9 in xf86SigHandler (signo=11)
    at ../../../../hw/xfree86/common/xf86Events.c:766
#7  <signal handler called>
#8  0x00002b3ff9b3ca92 in I830PutImage (pScrn=0x802390, src_x=0, src_y=0,
    drw_x=<value optimized out>, drw_y=<value optimized out>, src_w=<value optimized out>,
    src_h=480, drw_w=1021, drw_h=767, id=842094169,
    buf=0x2b40167d6000 '\020' <repeats 200 times>..., width=640, height=480, sync=1,
    clipBoxes=0x7fffb40ea360, data=0x846160, pDraw=0x2492830) at ../../src/i830_video.c:1319
#9  0x000000000049e332 in xf86XVPutImage (client=<value optimized out>, pDraw=0x2492830,
    pPort=0x847200, pGC=<value optimized out>, src_x=24576, src_y=-32752, src_w=4096, src_h=0,
    drw_x=129, drw_y=0, drw_w=<value optimized out>, drw_h=<value optimized out>, format=0x846ef0,
    data=0x2b40167d6000 '\020' <repeats 200 times>..., sync=1, width=<value optimized out>,
    height=<value optimized out>) at ../../../../hw/xfree86/common/xf86xv.c:1777
#10 0x00002b3ff8d61526 in ProcXvShmPutImage (client=0x27f0a70) at ../../Xext/xvdisp.c:1180
#11 0x000000000044e390 in Dispatch () at ../../dix/dispatch.c:502
#12 0x0000000000436b8d in main (argc=8, argv=0x7fffb40eaa38, envp=<value optimized out>)
    at ../../dix/main.c:452
Comment 1 Gordon Jin 2007-12-20 17:44:09 UTC
Is this dup with 13196?
Comment 2 Jesse Barnes 2008-01-03 11:22:05 UTC
You're using the intelfb or vesafb framebuffer driver?  At this point, that's an unsupported configuration (and probably never will be supported) so we'll probably have to mark this WONTFIX.
Comment 3 Raúl 2008-01-03 15:16:43 UTC
Indeed I'm using framebuffer, I'm almost sure that it's vesafb.
So if you say that this combination is not supported it is ok, but where should I know what configuration is it supported in order to have framebuffer console and Xorg running and why the mentioned combination it it not supported?

Thanks.
Comment 4 Jesse Barnes 2008-01-03 16:01:21 UTC
I don't think we currently document the fact that the Intel X driver and fb drivers are incompatible (though I've mentioned it on irc and the mailing lists iirc).  We should probably fix that by adding a note to the man page and website...

If you really want to use the fb drivers for some reason (say an embedded application) you can use Xfbdev or other fb applications instead of the accelerated intel driver.  That should work ok.

Jesse
Comment 5 Jesse Barnes 2008-02-06 15:41:08 UTC
Reassigning to Gordon so we can add a note on the website about not using any fb drivers.
Comment 6 Michael Fu 2008-02-20 05:15:20 UTC
added in intellinuxgraphics.org website. mark this as wontfix.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.