Bug 35508 - X crashes for some reason, drm fails on startup (Arrandale graphics, i915)
Summary: X crashes for some reason, drm fails on startup (Arrandale graphics, i915)
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Wilson
QA Contact:
Depends on:
Reported: 2011-03-21 10:11 UTC by Heiko Tietze
Modified: 2017-07-24 23:05 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

dmesg | tail -40 (1.40 KB, application/x-gzip)
2011-03-29 07:45 UTC, Heiko Tietze
no flags Details
Xorg.0.log (6.88 KB, application/x-gzip)
2011-03-29 07:46 UTC, Heiko Tietze
no flags Details
~./xsession-errors (2.16 KB, application/x-gzip)
2011-03-29 07:47 UTC, Heiko Tietze
no flags Details

Description Heiko Tietze 2011-03-21 10:11:15 UTC
Some but not all OpenGL programs and some web sites crashes X server. German
news http://www.spiegel.de/ section "einestages" fails always (Firefox). X
server reports nothing except "crashed unexpectedly". Problem does not depend
on kernel version, I'm struggling with it since 2.6.35(?).

I'm running openSuSE with tumbleweed repository. Hardware is a Thinkpad T510
with Arrandale graphics.

Bug has been posted first on kernel.org (https://bugzilla.kernel.org/show_bug.cgi?id=31082).

/usr/sbin/hwinfo -gfx
14: PCI 02.0: 0300 VGA compatible controller (VGA)              
  [Created at pci.318]
  Unique ID: _Znp.nUjOwTmEfZC
  SysFS ID: /devices/pci0000:00/0000:00:02.0
  SysFS BusID: 0000:00:02.0
  Hardware Class: graphics card
  Model: "Intel Arrandale Integrated Graphics Controller"
  Vendor: pci 0x8086 "Intel Corporation"
  Device: pci 0x0046 "Arrandale Integrated Graphics Controller"
  SubVendor: pci 0x17aa "Lenovo"
  SubDevice: pci 0x215a 
  Revision: 0x02
  Driver: "i915"
  Driver Modules: "drm"
  Memory Range: 0xf2000000-0xf23fffff (rw,non-prefetchable)
  Memory Range: 0xd0000000-0xdfffffff (ro,non-prefetchable)
  I/O Ports: 0x1800-0x1807 (rw)
  IRQ: 41 (5254 events)
  I/O Ports: 0x3c0-0x3df (rw)
  Module Alias: "pci:v00008086d00000046sv000017AAsd0000215Abc03sc00i00"
  Driver Info #0:
    Driver Status: i915 is active
    Driver Activation Cmd: "modprobe i915"
  Config Status: cfg=no, avail=yes, need=no, active=unknown

X -version

X.Org X Server 1.8.0
Release Date: 2010-04-02
X Protocol Version 11, Revision 0
Build Operating System: openSUSE SUSE LINUX
Current Operating System: Linux linux-5nff.site 2.6.38-rc7-14-desktop #1 SMP PREEMPT Wed Mar 2 17:40:26 CET 2011 x86_64
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.38-rc7-14-desktop root=/dev/disk/by-id/ata-WDC_WD3200BEVT-08A23T1_WD-WXG1A80E9593-part1 resume=/dev/disk/by-id/ata-WDC_WD3200BEVT-08A23T1_WD-WXG1A80E9593-part3 splash=silent quiet showopts vga=0x367
Build Date: 19 August 2010  03:34:22PM
Current version of pixman: 0.18.0
Before reporting problems, check http://wiki.x.org to make sure that you have the latest version.
Comment 1 Chris Wilson 2011-03-29 07:05:39 UTC
I need your dmesg, Xorg.log and probably ~/.xsession-errors probably at least. See http://intellinuxgraphics.org/how_to_report_bug.html for a guide on how to collect the information.
Comment 2 Heiko Tietze 2011-03-29 07:45:36 UTC
Created attachment 44999 [details]
dmesg | tail -40

Fresh restart of X -> crash produced -> output of last 40 lines of dmesg
Comment 3 Heiko Tietze 2011-03-29 07:46:44 UTC
Created attachment 45000 [details]

Fresh restart of X -> crash produced -> /var/log/Xorg.0.log
Comment 4 Heiko Tietze 2011-03-29 07:47:58 UTC
Created attachment 45001 [details]
Comment 5 Heiko Tietze 2011-03-29 07:49:50 UTC
Fresh restart of X -> crash produced -> outputs packed at tty2
Comment 6 Chris Wilson 2011-04-02 01:33:14 UTC
The information points to that your installation of Qt is borked. There are no GPU or driver errors reported, just SIGBUS for akonadi_agent.

I would reinstall the libraries and attach gdb.

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.