Gpu Hang After Resume From Hibernate State With 4.4 and 4.5-rc4

Bug #1545238 reported by Carlos Jimenez
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Incomplete
Medium
Unassigned

Bug Description

GPU HANG DMESG :
[ 191.910261] [drm] stuck on bsd ring
[ 191.914529] [drm] GPU HANG: ecode 5:1:0x01000000, reason: Ring hung, action: reset
[ 191.914533] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 191.914535] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 191.914536] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 191.914538] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 191.914540] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 191.918202] drm/i915: Resetting chip after gpu hang

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-4-generic 4.4.0-4.19
ProcVersionSignature: Ubuntu 4.4.0-4.19-generic 4.4.1
Uname: Linux 4.4.0-4-generic x86_64
NonfreeKernelModules: zfs zunicode zcommon znvpair zavl
ApportVersion: 2.19.4-0ubuntu2
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ozmage 1611 F.... pulseaudio
CRDA:
 country DO: DFS-FCC
  (2402 - 2472 @ 40), (N/A, 30), (N/A)
  (5170 - 5250 @ 80), (N/A, 17), (N/A)
  (5250 - 5330 @ 80), (N/A, 23), (0 ms), DFS
  (5735 - 5835 @ 80), (N/A, 30), (N/A)
CurrentDesktop: Unity
Date: Sat Feb 13 02:17:45 2016
MachineType: TOSHIBA PORTEGE R700
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/UBUNTU/boot/vmlinuz-4.4.0-4-generic root=UUID=a51510b9-ffd0-494a-82fa-e6f25b83833b rw rootflags=subvol=UBUNTU resume=/dev/sda6 loglevel=3 libahci.ignore_sss=1 vt.handoff=7 splash
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-4-generic N/A
 linux-backports-modules-4.4.0-4-generic N/A
 linux-firmware 1.155
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/22/2011
dmi.bios.vendor: TOSHIBA
dmi.bios.version: Version 2.20
dmi.board.asset.tag: 0000000000
dmi.board.name: Portable PC
dmi.board.vendor: TOSHIBA
dmi.board.version: Version A0
dmi.chassis.asset.tag: 0000000000
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.version: Version 1.0
dmi.modalias: dmi:bvnTOSHIBA:bvrVersion2.20:bd12/22/2011:svnTOSHIBA:pnPORTEGER700:pvrPT310U-0K002Y01:rvnTOSHIBA:rnPortablePC:rvrVersionA0:cvnTOSHIBA:ct10:cvrVersion1.0:
dmi.product.name: PORTEGE R700
dmi.product.version: PT310U-0K002Y01
dmi.sys.vendor: TOSHIBA

Revision history for this message
Carlos Jimenez (ozmage809) wrote :
Revision history for this message
Carlos Jimenez (ozmage809) wrote :
Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Joseph Salisbury (jsalisbury) wrote : Re: Gpu Hang After Resume From Hibernate State With 4.4

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.5 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.5-rc4-wily/

Changed in linux (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Incomplete
Revision history for this message
Carlos Jimenez (ozmage809) wrote :

kernel-bug-exists-upstream

Confirmed

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Carlos Jimenez (ozmage809) wrote :

kernel-bug-exists-upstream

summary: - Gpu Hang After Resume From Hibernate State With 4.4
+ Gpu Hang After Resume From Hibernate State With 4.4 and 4.5-rc4
penalvch (penalvch)
description: updated
Revision history for this message
penalvch (penalvch) wrote :

Carlos Jimenez, could you please provide the full computer model as noted on the sticker of the computer itself (not from the Bug Description)?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
tags: added: kernel-bug-exists-upstream kernel-bug-exists-upstream-4.5-rc4
Revision history for this message
Carlos Jimenez (ozmage809) wrote :

OK HERE iS THE MODEL :

Toshiba Portege R700

PART NO:
PT310U-0K002Y02

SERIAL NO:
3B0539284

Revision history for this message
Carlos Jimenez (ozmage809) wrote :

everything was in the bug report the same on the sticker laptop on the bottom

dmi.product.name: PORTEGE R700
dmi.product.version: PT310U-0K002Y01
dmi.sys.vendor: TOSHIBA

Revision history for this message
Carlos Jimenez (ozmage809) wrote :

The bug is not incomplete anymore this bug needs to be fixed i need lastest kernels because i use btrfs and i need the updates.

Thanks.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Carlos Jimenez, to clarify, what is the country of origin of the laptop?

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Carlos Jimenez (ozmage809) wrote :

Made in China

What Else is Needed to change the status ?

i have xenial installed but if i cant fix this bug or anyone else fix it i must have to uninstall ubuntu xenial and go back to wily.

Revision history for this message
penalvch (penalvch) wrote :

Carlos Jimenez, to clarify, I'm asking from what country was the laptop purchased, not what country after the "Made in" is written.

Revision history for this message
Carlos Jimenez (ozmage809) wrote :

I purchased my laptop here in my country Dominican Republic.
Thanks.

Revision history for this message
penalvch (penalvch) wrote :

Carlos Jimenez, to advise, I'm not able to find your laptop so far. Could you please provide the serial number (not model number)?

Revision history for this message
Reinis Zumbergs (reinis-zumbergs) wrote :
Download full text (3.7 KiB)

I have very similar symptoms on Xenial, currently Linux 4.4.0-10-generic.
Graphics hardware acceleration doesn't work after resume from suspend.
Chrome window does not respond, is not redrawn. glxgears and games do not launch.

I have it on Dell Latitude E5520 with Intel HD Graphics 3000.

in dmesg I found a line:
[22663.178783] [drm:i915_hangcheck_elapsed [i915]] *ERROR* Hangcheck timer elapsed... blitter ring idle

And then this follows. It's repeated several times in the dmesg output.

[22684.565185] ------------[ cut here ]------------
[22684.565240] WARNING: CPU: 1 PID: 6031 at /build/linux-w3wMX6/linux-4.4.0/drivers/gpu/drm/drm_irq.c:1268 drm_wait_one_vblank+0x1b5/0x1c0 [drm]()
[22684.565244] vblank wait timed out on crtc 0
[22684.565247] Modules linked in: pci_stub vboxpci(OE) vboxnetadp(OE) vboxnetflt(OE) vboxdrv(OE) drbg ansi_cprng ctr ccm bnep dell_wmi sparse_keymap dell_rbtn dell_laptop dcdbas dell_smm_hwmon btusb btrtl btbcm btintel intel_rapl x86_pkg_temp_thermal uvcvideo intel_powerclamp coretemp kvm_intel videobuf2_vmalloc videobuf2_memops arc4 bluetooth kvm videobuf2_v4l2 videobuf2_core snd_hda_codec_hdmi irqbypass v4l2_common crct10dif_pclmul videodev crc32_pclmul media aesni_intel iwldvm aes_x86_64 lrw snd_hda_codec_idt gf128mul snd_hda_codec_generic glue_helper mac80211 ablk_helper cryptd snd_hda_intel snd_hda_codec joydev snd_hda_core snd_hwdep input_leds iwlwifi serio_raw snd_pcm cfg80211 lpc_ich snd_seq_midi snd_seq_midi_event snd_rawmidi snd_seq snd_seq_device 8250_fintek snd_timer mei_me snd mei dell_smo8800
[22684.565357] mac_hid soundcore shpchp parport_pc ppdev lp parport autofs4 btrfs xor raid6_pq hid_generic usbhid hid i915 i2c_algo_bit drm_kms_helper syscopyarea tg3 psmouse sysfillrect sysimgblt ptp fb_sys_fops pps_core ahci firewire_ohci drm sdhci_pci libahci firewire_core sdhci crc_itu_t wmi fjes video
[22684.565413] CPU: 1 PID: 6031 Comm: Xorg Tainted: G W OE 4.4.0-10-generic #25-Ubuntu
[22684.565417] Hardware name: Dell Inc. Latitude E5520/03PH4G, BIOS A14 12/26/2013
[22684.565422] 0000000000000286 0000000059044e49 ffff880004547ad8 ffffffff813e1963
[22684.565429] ffff880004547b20 ffffffffc00a8b00 ffff880004547b10 ffffffff8107fe12
[22684.565436] ffff8801a64ad000 0000000000000000 0000000000000000 00000000000fc8ee
[22684.565442] Call Trace:
[22684.565454] [<ffffffff813e1963>] dump_stack+0x63/0x90
[22684.565465] [<ffffffff8107fe12>] warn_slowpath_common+0x82/0xc0
[22684.565471] [<ffffffff8107feac>] warn_slowpath_fmt+0x5c/0x80
[22684.565481] [<ffffffff810c23e5>] ? finish_wait+0x55/0x70
[22684.565518] [<ffffffffc00792a5>] drm_wait_one_vblank+0x1b5/0x1c0 [drm]
[22684.565528] [<ffffffff810c2880>] ? wake_atomic_t_function+0x60/0x60
[22684.565606] [<ffffffffc0241aea>] intel_atomic_commit+0x43a/0x6f0 [i915]
[22684.565650] [<ffffffffc0092a37>] drm_atomic_commit+0x37/0x60 [drm]
[22684.565671] [<ffffffffc01a2ec9>] drm_atomic_helper_disable_plane+0xa9/0xf0 [drm_kms_helper]
[22684.565707] [<ffffffffc0081fc9>] __setplane_internal+0x169/0x250 [drm]
[22684.565745] [<ffffffffc009125a>] ? drm_modeset_lock_all_ctx+0x9a/0xb0 [drm]
[22684.565781] [<ffffffffc0085cc6>] drm_mode_setplane+0x136/0x1b0 [drm]...

Read more...

Revision history for this message
penalvch (penalvch) wrote :

Reinis Zumbergs, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.

Revision history for this message
Carlos Jimenez (ozmage809) wrote :
Revision history for this message
Carlos Jimenez (ozmage809) wrote :

Christopher M. Penalver (penalvch) ^^^^^^ That is practically the same Laptop I have

http://www.amazon.com/Memory-Toshiba-Portege-PT310U-0K002Y02-DDR3-10600/dp/B016WUPXCQ

Revision history for this message
Carlos Jimenez (ozmage809) wrote :

the drivers and components are the same.

penalvch (penalvch)
tags: added: latest-bios-2.20
Revision history for this message
penalvch (penalvch) wrote :

Carlos Jimenez, to clarify, what is desired is exactly which model you have (not something close, etc.).

Hence, to confirm, you have precisely http://www.toshiba.co.uk/discontinued-products/portege-r700-1f5/ ?

Revision history for this message
Carlos Jimenez (ozmage809) wrote :
Download full text (68.2 KiB)

[ 0.000000] microcode: microcode updated early to revision 0x4, date = 2013-06-28
[ 0.000000] Linux version 4.6.0-rc5-ex (root@ozmage-lappy) (gcc version 5.3.0 (GCC) ) #1 SMP PREEMPT Sun Apr 24 22:01:18 AST 2016
[ 0.000000] Command line: BOOT_IMAGE=/boot/vmlinuz-linux-ex root=UUID=d27b2815-7e94-43d4-b047-c44f8b1c6461 rw splash rd.udev.log-priority=3 rd.systemd.show_status=false logo.nologo systemd.show_status=0 console=tty0 splash=verbose,theme:arch-black loglevel=3 resume=/dev/sda6 elevator=bfq kdbus=1 libahci.ignore_sss=1 modprobe.blacklist=i915 vt.handoff=7
[ 0.000000] x86/fpu: Legacy x87 FPU detected.
[ 0.000000] x86/fpu: Using 'eager' FPU context switches.
[ 0.000000] e820: BIOS-provided physical RAM map:
[ 0.000000] BIOS-e820: [mem 0x0000000000000000-0x000000000009ebff] usable
[ 0.000000] BIOS-e820: [mem 0x000000000009ec00-0x000000000009ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000000100000-0x00000000b70cffff] usable
[ 0.000000] BIOS-e820: [mem 0x00000000b70d0000-0x00000000b70d01ff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000b70d0200-0x00000000b70d1fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000b70d2000-0x00000000b71cffff] ACPI NVS
[ 0.000000] BIOS-e820: [mem 0x00000000b71d0000-0x00000000b71effff] ACPI data
[ 0.000000] BIOS-e820: [mem 0x00000000b71f0000-0x00000000bfffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed10000-0x00000000fed13fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed18000-0x00000000fed19fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fed1c000-0x00000000fed1ffff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
[ 0.000000] BIOS-e820: [mem 0x00000000ffe00000-0x00000000ffffffff] reserved
[ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000137ffffff] usable
[ 0.000000] NX (Execute Disable) protection: active
[ 0.000000] SMBIOS 2.4 present.
[ 0.000000] DMI: TOSHIBA PORTEGE R700/Portable PC, BIOS Version 2.20 12/22/2011
[ 0.000000] e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
[ 0.000000] e820: remove [mem 0x000a0000-0x000fffff] usable
[ 0.000000] e820: last_pfn = 0x138000 max_arch_pfn = 0x400000000
[ 0.000000] MTRR default type: uncachable
[ 0.000000] MTRR fixed ranges enabled:
[ 0.000000] 00000-9FFFF write-back
[ 0.000000] A0000-BFFFF uncachable
[ 0.000000] C0000-D3FFF write-protect
[ 0.000000] D4000-DFFFF uncachable
[ 0.000000] E0000-EFFFF write-through
[ 0.000000] F0000-FFFFF write-protect
[ 0.000000] MTRR variable ranges enabled:
[ 0.000000] 0 base 0FFE00000 mask FFFE00000 uncachable
[ 0.000000] 1 base 000000000 mask F80000000 write-back
[ 0.000000] 2 base 080000000 mask FC0000000 write-back
[ 0.000000] 3 base 0B8000000 mask FF8000000 uncachable
[ 0.000000] 4 base 100000000 mask FC0000000 write-back
[ 0.000000] 5 disabled
[ 0.000000] 6 disabled
[ ...

Revision history for this message
penalvch (penalvch) wrote :

Carlos Jimenez, posting logs here is useless for this situation. Please just answer my question as I asked it with a yes or no.

Revision history for this message
Carlos Jimenez (ozmage809) wrote :

looks like this old bug i had has been fixed on https://bugs.freedesktop.org/show_bug.cgi?id=94203 on drm-intel-nightly: 2016y-05m-08d-16h-21m-00s

Revision history for this message
Carlos Jimenez (ozmage809) wrote :

sorry i just looked good at my dmesg and i still got gpu hang

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.