Bug 1117453

Created attachment 916502 [details]
File: backtrace

Created attachment 916503 [details]
File: cgroup

Created attachment 916504 [details]
File: core_backtrace

Created attachment 916505 [details]
File: dso_list

Created attachment 916506 [details]
File: environ

Created attachment 916507 [details]
File: exploitable

Created attachment 916508 [details]
File: limits

Created attachment 916509 [details]
File: maps

Created attachment 916510 [details]
File: open_fds

Created attachment 916511 [details]
File: proc_pid_status

Created attachment 916512 [details]
File: var_log_messages

I also saw this under gnome-shell 3.10.4-5, which I had been running for a while with no (similar or similarly serious) issues.

The kernel/intel driver however did update recently...

This seems to happen often on resume from hibernation.

Still happening with 3.10.4-7, almost daily.  This is a quite a pain since the shell can't just be restarted.  I have to reboot, restarting gdm doesn't help.  The shell just displays the "oh no something went wrong" full-screen message.

Not sure if this is related to the segv or not but I've also noticed something is causing my pop-up windows (things that appear when you hover e.g. tooltips) will be all black. Not sure if they've rendered but all colors are black or if they never rendered and I'm only seeing a black background).

After seeing the "black pop-up" problem I tried to remedy it by restarting the shell, which then caused the segv.

The segv is in get_stencil_miptree which suggests to me it could be related to the black pop-up windows (just a guess).

Any update on getting this fixed? It happens frequently and when it does I lose all my workspaces which is a productivity killer.

Reassigning to Mesa, as the crash is inside the intel code, and it seems to be hardware specific in some fashion (for comparison, I don't think I've ever seen this crash, running 3.10 GNOME on Intel hardware.)

What are details of the hardware for people seeing this?

John - is it connected to hibernation for you as well?

I don't think it's connected to hibernation. But it does seem to happen sometime shortly after my menus and other pop-ups get rendered as a just a black window which makes working nearly impossible. When this happens I try to restart Gnome Shell hoping I won't lose all my workspaces so I won't have to recrate everything. It's restarting the shell after the black menu rendering problem appears that seems to crash the shell.

I too suspected this might be a driver issue. I googled black menus and found several bz's and other hits which suggested it has to do with the AccelMode in the Intel driver.

My laptop is a Lenovo T420s with Integrated Graphics Chipset: Intel(R) HD Graphics 3000.

The bugs and other discussions suggest that the default UXA driver is the culprit and one should override UXA driver and force the SNA driver. I created the necessary config file but I haven't rebooted yet to pick it up so I can't comment yet on whether the SNA driver makes a difference.

I'm not sure how menus and popups are rendered, but something seems to be going wrong during their rendering.

It's definitely correlated to resuming from hibernation for me.  Also, it seems to only happen when I am using/changing an external display.

My hardware:

00:02.0 VGA compatible controller: Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller (rev 07) (prog-if 00 [VGA controller])
	Subsystem: Lenovo Device 20e4
	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 45
	Region 0: Memory at f2000000 (64-bit, non-prefetchable) [size=4M]
	Region 2: Memory at d0000000 (64-bit, prefetchable) [size=256M]
	Region 4: I/O ports at 1800 [size=8]
	Expansion ROM at <unassigned> [disabled]
	Capabilities: <access denied>
	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: Lenovo Device 20e4
	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 f2400000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: <access denied>

I see it without hibernation. But I could not find a sure way to reproduce it so far. Happens almost daily for me now.

My Hardward isLenovo T520, Intel Graphics.

“Integrated Graphics Chipset: Intel(R) HD Graphics 3000”

I have this problem when trying to suspend or coming back from suspend.

How can I help?

Intermittent and impossible to reproduce. Lately it seems only to happen when coming back from suspend. The original desktop content is displayed for a second and then following the Gnome gray Oops screen with only a log out button.

After logging back in I have noticed major performance decrease with animated items such as window chooser (Windows button) and with the Chrome tabs circling loading indicators. I have to reboot my laptop to restore the performance. Restarting gdm (ctrl-alt-bs) doesn't help. My laptop is not overheating.

Hardware:

Intel(R) Core(TM)2 Duo CPU     T9550  @ 2.66GHz
width: 64 bits
capabilities: fpu fpu_exception wp vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall nx x86-64 constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf pni dtes64 monitor ds_cpl vmx smx est tm2 ssse3 cx16 xtpr pdcm sse4_1 xsave lahf_lm ida dtherm tpr_shadow vnmi flexpriority cpufreq

Mobile 4 Series Chipset Integrated Graphics Controller
width: 64 bits
clock: 33MHz
capabilities: vga_controller bus_master cap_list rom
configuration: driver=i915 latency=0

82801I (ICH9 Family) USB UHCI Controller, USB2 EHCI Controller, HD Audio Controller, PCI Express Port
width: 32 bits & 64 bits
clock: 33MHz
capabilities: uhci bus_master cap_list ehci pci normal_decode 
configuration: driver=uhci_hcd latency=0

Intel Ultimate N WiFi Link 5300
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=3.16.3-200.fc20.x86_64 firmware=8.83.5.1 build 33692 ip=192.168.1.6 latency=0 link=yes multicast=yes wireless=IEEE 802.11abgn

RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
size: 10Mbit/s
capacity: 1Gbit/s
width: 64 bits
clock: 33MHz
capabilities: bus_master cap_list rom ethernet physical tp mii 10bt 10bt-fd 100bt 100bt-fd 1000bt 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=r8169 driverversion=2.3LK-NAPI duplex=half firmware=rtl_nic/rtl8168d-1.fw latency=0 link=no multicast=yes port=MII speed=10Mbit/s

Intel 82801IBM/IEM (ICH9M/ICH9M-E) 4 port SATA Controller [AHCI mode]
width: 32 bits
clock: 66MHz
capabilities: storage ahci_1.0 bus_master cap_list
configuration: driver=ahci latency=0
resources: irq:44 ioport:6e70(size=8) ioport:6e78(size=4) ioport:6e80(size=8) ioport:6e88(size=4) ioport:6ea0(size=32) memory:fed1c800-fed1cfff

This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 EOL if it remains open with a Fedora  'version'
of '20'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 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  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

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.

I haven't seen this issue for a while now. Seemed already solved in Fedora 20 for me.

Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

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