Xorg segfault: returns me to login screen after waking from suspend

Asked by Rik Shaw on 2012-07-21

Every few days after waking from suspend, my Lenovo Thinkpad T520 (Intel graphics) will operate for a few minutes and then randomly go blank for a few seconds followed by showing up at the login screen.

I looked in dmesg and found the following entry at the end:

[23710.271916] Xorg[1213]: segfault at 9 ip b7652b28 sp bff29560 error 4 in Xorg[b7532000+1f3000]

Any advice on what else to hunt down to get more info would be appreciated!

I did see something on askubuntu regarding an "error 4 in Xorg" with a Thinkpad x220, which was supposedly solved by disabling compiz. I am not sure how to confirm whether I have a compiz problem or not. No custom tweaks there (except for grid drag to top edge auto maximize is disabled and a few of the unity tweaks).

This is with Ubuntu 12.04. All updates are applied.

Thanks,

iveand

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu xorg Edit question
Assignee:
No assignee Edit question
Solved by:
Rik Shaw
Solved:
2013-12-03
Last query:
2013-12-03
Last reply:
2012-07-22

This question was reopened

Have you tested your RAM using memtest from Grub?

having the same problem with my aspire 1810tz. mostly after suspend, sometimes also while i'm working. thrown back to login. problem first appeared with an update somewhen in july.

graphics from lspci:

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
        Subsystem: Acer Incorporated [ALI] Device 029b
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Interrupt: pin A routed to IRQ 43
        Region 0: Memory at d0000000 (64-bit, non-prefetchable) [size=4M]
        Region 2: Memory at c0000000 (64-bit, prefetchable) [size=256M]
        Region 4: I/O ports at 30d0 [size=8]
        Expansion ROM at <unassigned> [disabled]
        Capabilities: [90] MSI: Enable+ Count=1/1 Maskable- 64bit-
                Address: fee0300c Data: 4171
        Capabilities: [d0] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-
        Kernel driver in use: i915
        Kernel modules: i915

00:02.1 Display controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07)
        Subsystem: Acer Incorporated [ALI] Device 029b
        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
        Status: Cap+ 66MHz- UDF- FastB2B+ ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
        Latency: 0
        Region 0: Memory at d2400000 (64-bit, non-prefetchable) [size=1M]
        Capabilities: [d0] Power Management version 3
                Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0-,D1-,D2-,D3hot-,D3cold-)
                Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME-

samuel (samuel-h) said : #3

To disable compiz just select ubuntu 2d at the login screen from the menu by your name. Or log into a normal ubuntu session then press alt+f2 to run a command and type metacity --replace

Rik Shaw (rik-shaw) said : #4

@actionparsnip - I doubted it to be a RAM issue as it doesn't "crash" with a hung display, but rather just kicks me out to the login prompt. To confirm it wasn't RAM I did run Memtest+ on it and there were no errors after the first full pass.

I was able to re-produce the problem by doing several quick suspend / resumes (it took *approximately* 5 of these before I was then kicked to the login screen). I will later try in Unity 2D to see what happens (w/o compiz). This may help narrow it down a bit more.

Rik Shaw (rik-shaw) said : #5

Added the link to a bug report I have found that seems to match pretty closely (albeit the original poster seems to have an AMD system instead of an Intel one).

Lasse Makholm (lasse-makholm) said : #6

Just FYI, I reported Bug #1026777 and it is indeed the same hardware and same symptoms as yours.

Rik Shaw (rik-shaw) said : #7

Lasse,

Thanks for the followup. We can consolidate the discussion on the bug report so for now I will mark this "question" solved since it does seem to be a bug.

Rik Shaw (rik-shaw) said : #8

I will note here for others that may find this question that the suggestion to try Unity 2D instead of 3D (to get Compiz out of the way) DID NOT change the behavior. The same "kicking out to login screen" happens in either 2D or 3D after 3 consecutive suspend / wake cycles (can now make it consistently happen with this techinque). Again, will continue the disucssion over on the bug listing.

moscowart (moscowart99) said : #9

I have the same problem with the same laptop

Rik Shaw (rik-shaw) said : #10

This seems to have been solved somewhere along the lines by either using the lts-quantal hardware enablement stack or by a standard xorg update. Regardless, it is not a current isuse and I am marking as solved.