Bug 749534

Created attachment 530463 [details]
Xorg.0.log including backtrace

Please, provide output of the command

rpm -q  xorg-x11-server-Xorg xorg-x11-drv-intel libdrm

Also, if you are able to reproduce the issue, output of the command

dmesg

AFTER the issue happens, but before rebooting, would be helpful.

Thank you

xorg-x11-server-Xorg-1.11.1-1.fc16.x86_64
xorg-x11-drv-intel-2.16.0-2.fc16.x86_64
libdrm-2.4.26-2.fc16.x86_64
libdrm-2.4.26-2.fc16.i686

haven't rebooted yet so dmesg that I'm attaching is valid. Looking at my logs libdrm has recently gone from -1 to -2. dmesg is from a time covering the update, attached Xorg.0.log was after a X restart when drm was already updated. No updates in between, and this comment is written from the immediately following session. 

I've seen similar crashes a few times (but not that many) with libdrm -1 too, so probably not a regression there either.

Hope this helps, will try rebooting/reproducing in the meanwhile.

Created attachment 530807 [details]
dmesg output

In function RecordAReply:
(from frame 3: /usr/lib64/xorg/modules/extensions/librecord.so (0x7ff6c225e000+0x26c3) [0x7ff6c22606c3])
603: RecordAReply(CallbackListPtr *pcbl, pointer nulldata, pointer calldata)
604: {
605:     RecordContextPtr pContext;
606:     RecordClientsAndProtocolPtr pRCAP;
607:     int eci;
608:     int majorop;
609:     ReplyInfoRec *pri = (ReplyInfoRec *)calldata;
610:     ClientPtr client = pri->client;
611:     REQUEST(xReq);
612: 
613: >>>>>>>     majorop = stuff->reqType;
614:     for (eci = 0; eci < numEnabledContexts; eci++)
615:     {
616:    pContext = ppAllContexts[eci];
617:    pRCAP = RecordFindClientOnContext(pContext, client->clientAsMask,
618:                                      NULL);
619:    if (pRCAP)
620:    {
621:        if (pContext->continuedReply)
622:        {
623:            RecordAProtocolElement(pContext, client, XRecordFromServer,


Frame 4: /usr/bin/Xorg (_CallCallbacks+0x3c) [0x43820c]
        /usr/src/debug/xorg-server-1.11.1/dix/dixutils.c:743
        _CallCallbacks
Frame 5: /usr/bin/Xorg (WriteToClient+0x1f5) [0x466315]
        /usr/src/debug/xorg-server-1.11.1/os/../include/callback.h:86
        CallCallbacks
Frame 8: /usr/lib64/xorg/modules/drivers/intel_drv.so (0x7ff6c1bfb000+0x25ae4) [0x7ff6c1c20ae4]
        /usr/src/debug/xf86-video-intel-2.16.0/src/intel_dri.c:965
        I830DRI2FrameEventHandler
Frame 10: /usr/bin/Xorg (WakeupHandler+0x6b) [0x4379db]
        /usr/src/debug/xorg-server-1.11.1/dix/dixutils.c:419
        WakeupHandler
Frame 11: /usr/bin/Xorg (WaitForSomething+0x1a9) [0x460289]
        /usr/src/debug/xorg-server-1.11.1/os/WaitFor.c:236
        WaitForSomething
Frame 12: /usr/bin/Xorg (0x400000+0x3379a) [0x43379a]
        /usr/src/debug/xorg-server-1.11.1/dix/dispatch.c:370
        Dispatch
Frame 13: /usr/bin/Xorg (0x400000+0x22dc5) [0x422dc5]
        /usr/src/debug/xorg-server-1.11.1/dix/main.c:296
        main

"Right after login" may be a red herring, after a reboot to 3.1.0-1 it now crashed after 1.5 days or so of logging in, backtrace looks identical. Was typing an url into chrome when it happened.

Hmpf, it might be gone, haven't seen it for some time:

xorg-x11-server-Xorg-1.11.2-3.fc16.x86_64
xorg-x11-drv-intel-2.17.0-1.fc16.x86_64
libdrm-2.4.27-2.fc16.x86_64

Then again, I've updated chrome too and "start typing an url into chrome" was the trigger several (if not every) times. The wonders of modern desktops ;)

I'll try to remember to close this in a few weeks if I don't see it anymore (or just close it and I'll reopen if necessary, it's probably such a heisenbug that visibility from being open shouldn't hurt tho...)

I saw this early in the f16 betas, and I see it again now in rawhide (f17)

Filed it here https://bugzilla.redhat.com/show_bug.cgi?id=766354

[kmaraas@e4300 ~]$ rpm -q xorg-x11-server-Xorg xorg-x11-drv-intel libdrm
xorg-x11-server-Xorg-1.11.99.1-9.20111109.fc17.i686
xorg-x11-drv-intel-2.17.0-3.fc17.i686
libdrm-2.4.27-2.fc17.i686

Possiby a duplicate of bug 739488

There's a link to an upstream bug in the closed bug in comment #9. This was fixed upstream apparently.

This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '16'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 is end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" and open it against that version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.