Date:	Sun, 08 Mar 2015 18:35:29 +0100
From:	Rasmus <kernel-bugzilla@...k.eu>
To:	rjw@...ysocki.net, lenb@...nel.org
Cc:	linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: PROBLEM: Reboots on graphical load w/Intel HD4000 since Linux 3.10

Hi,

Summary of Problem:

    System reboots on graphical load with Intel HD 4000 iGPU since Linux
    3.10

The full bug-report including all attachments is available on bugzilla and
below:

    https://bugzilla.kernel.org/show_bug.cgi?id=94551

I hope I have managed to fill the report correctly and provided enough
information.  My apology for the mistakes that remains.  Please let me
know about further information that would be helpful.

Should I try to git bisec Linux between 3.9 and 3.10?  (I'm not sure how
to do this properly, so pointers would be good).

I'm not subscribed to any Linux ML.  If possible, please keep me in Cc if
replying to the email.

Thanks,
Rasmus


1 Full description of the problem/report
════════════════════════════════════════

  I experience reboots crashing on my Thinkpad W530 with HD4000 whenever
  the iGPU is exposed to moderate load, e.g. playing a video game or
  movies.  This only happens when I employ the Intel iGPU.  It happens
  irrespective of whether Nvidia Optimus in enabled.

  It seems this error was introduced between Linux 3.9 and 3.10.  Fedora
  19 is stable.  Fedora 20 is not.  I have tested 3.9 with the current
  Xorg stack on Archlinux and it is also stable.  3.10 is not.  Windows
  7 is also stable.

  It’s not a hardware issue!  I can run mprime cpu load indefinitely on
  the system without a crash.  The temperature never goes above 90
  degrees when I run any test.  This problem is confirmed on two W530
  machines.

  It does not seem to be a Intel driver bug as I the current Xorg stack
  works with Linux 3.9.  A bug was first filled against Intel drivers,
  see section [#links].

  Logs are produced with clean Fedora images.


  [#links] See section 7.2


2 Keywords
══════════

  hard crash, Kernel, Thinkpad, Intel graphics, iGPU


3 Kernel version (from /proc/version)
═════════════════════════════════════

3.1 Fedora 21
─────────────

  Linux version 3.18.7-200.fc21.x86_64
  (mockbuild@...rnel02.phx2.fedoraproject.org) (gcc version 4.9.2
  20141101 (Red Hat 4.9.2-1) (GCC) ) #1 SMP Wed Feb 11 21:53:17 UTC 2015


3.2 Fedora 19
─────────────

  Linux version 3.9.5-301.fc19.x86_64
  (mockbuild@...rnel01.phx2.fedoraproject.org) (gcc version 4.8.1
  20130603 (Red Hat 4.8.1-1) (GCC) ) #1 SMP Tue Jun 11 19:39:38 UTC 2013


4 Output of Oops.. message (if applicable) with symbolic information
════════════════════════════════════════════════════════════════════

  I don’t see Oops messages…  Please see the enclosed files.


5 How to reproduce
══════════════════

  1. Download gputest from [http://www.geeks3d.com/gputest/]
  2. Run start_furmark_windowed_1024x640.sh.  Put it in full screen if
     you like.
  3. On my system the computer crashes and reboots typically within 10
     minutes.
     The reboot is as if power was cut and returned.  Like if the CPU
     was
     overheating (which it is not).  IOW: The systemctl shutdown logs
     are not
     displayed.


6 Environment
═════════════

  Thinkpad W530?  (I don’t understand this question).


6.1 Software (add the output of the ver_linux script here)
──────────────────────────────────────────────────────────

6.1.1 Fedora 21
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Please see ver_linux_fedora_21.txt.


6.1.2 Fedora 19
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Please see ver_linux_fedora_19.txt.


6.2 Processor information (from /proc/cpuinfo)
──────────────────────────────────────────────

6.2.1 Fedora 21
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  I believe this is part of ver_linux_fedora_21.txt.


6.2.2 Fedora 19
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  I believe this is part of ver_linux_fedora_19.txt.


6.3 Module information (from /proc/modules)
───────────────────────────────────────────

6.3.1 Fedora 21
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Please see modules_fedora_21.txt


6.3.2 Fedora 19
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Please see modules_fedora_19.txt


6.4 Loaded driver and hardware information (/proc/ioports, /proc/iomem)
───────────────────────────────────────────────────────────────────────

6.4.1 Fedora 21
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

6.4.1.1 /proc/ioports
┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄

  Please see ioports_fedora_21.txt.


6.4.1.2 /proc/iomem
┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄

  Please see iomem_fedora_21.txt.


6.4.2 Fedora 19
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

6.4.2.1 /proc/ioports
┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄

  Please see ioports_fedora_19.txt.


6.4.2.2 /proc/iomem
┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄┄

  Please see iomem_fedora_19.txt.


6.5 PCI information (‘lspci -vvv’ as root)
──────────────────────────────────────────

6.5.1 Fedora 21
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Please see lspci_fedora_21.txt


6.5.2 Fedora 19
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Please see lspci_fedora_19.txt


6.6 SCSI information (from /proc/scsi/scsi)
───────────────────────────────────────────

6.6.1 Fedora 21
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 00
    Vendor: ATA Model: Crucial_CT256MX1 Rev: MU01
    Type: Direct-Access ANSI SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 00
    Vendor: MATSHITA Model: DVD-RAM UJ8C0 Rev: SB01
    Type: CD-ROM ANSI SCSI revision: 05


6.6.2 Fedora 19
╌╌╌╌╌╌╌╌╌╌╌╌╌╌╌

  Attached devices:
  Host: scsi0 Channel: 00 Id: 00 Lun: 00
    Vendor: ATA Model: Crucial_CT256MX1 Rev: MU01
    Type: Direct-Access ANSI SCSI revision: 05
  Host: scsi1 Channel: 00 Id: 00 Lun: 00
    Vendor: MATSHITA Model: DVD-RAM UJ8C0 Rev: SB01
    Type: CD-ROM ANSI SCSI revision: 05
  Host: scsi6 Channel: 00 Id: 00 Lun: 00
    Vendor: Kingston Model: DataTraveler 3.0 Rev: PMAP
    Type: Direct-Access ANSI SCSI revision: 06


6.7 Other information that might be relevant to the problem
───────────────────────────────────────────────────────────

  Not that I am aware of.


7 Other notes, patches, fixes, workarounds
══════════════════════════════════════════

7.1 Other enclosures
────────────────────

  dmesg_fedora_21.txt: netconsole output of Fedora 21 with crash.
  dmesg_fedora_19.txt: dmesg after running Furmark for a bit in
                       Fedora 19.  (My understanding is that this should
                       be similar to
                       the netcat output)
  xorg_crash_fedora_21.txt: an example of an Xorg-log when the server
                            is crashing.
  bios_settings.txt: settings in the bios with some notes.


7.2 Other iteration of this bug report
──────────────────────────────────────

  This bug was first reported here:
  [https://bugs.freedesktop.org/show_bug.cgi?id=89451]

  It has been discussed here:
  [http://forum.thinkpads.com/viewtopic.php?f=70&t=116472]


-- 
Got mashed potatoes. Ain't got no T-Bone. No T-Bone

View attachment "bios_settings.txt" of type "text/plain" (3490 bytes)

View attachment "dmesg_fedora_19.txt" of type "text/plain" (73229 bytes)

View attachment "dmesg_fedora_21.txt" of type "text/plain" (209517 bytes)

View attachment "iomem_fedora_19.txt" of type "text/plain" (2892 bytes)

View attachment "iomem_fedora_21.txt" of type "text/plain" (3006 bytes)

View attachment "ioports_fedora_19.txt" of type "text/plain" (1257 bytes)

View attachment "ioports_fedora_21.txt" of type "text/plain" (1314 bytes)

View attachment "lspci_fedora_19.txt" of type "text/plain" (31725 bytes)

View attachment "lspci_fedora_21.txt" of type "text/plain" (31849 bytes)

View attachment "modules_fedora_19.txt" of type "text/plain" (5238 bytes)

View attachment "modules_fedora_21.txt" of type "text/plain" (6198 bytes)

View attachment "ver_linux_fedora_19.txt" of type "text/plain" (9968 bytes)

View attachment "ver_linux_fedora_21.txt" of type "text/plain" (10388 bytes)

View attachment "xorg_crash_fedora_21.txt" of type "text/plain" (42707 bytes)

Powered by blists - more mailing lists