You are not logged in.

#76 2019-12-26 13:31:23

estepan
Member
Registered: 2019-12-26
Posts: 1

Re: i915 Skylake GPU hangs with kernel 5.3.11

I installed mainline kernel (5.5.0 rc2 1) and was working fine for 3 days, but today had another freeze, and this is the log for it, seems like is still not fixed, using modesetting

Dec 26 10:18:17 shockwave kernel: Oops: 0000 [#1] PREEMPT SMP PTI
Dec 26 10:18:17 shockwave kernel: CPU: 1 PID: 1068 Comm: xfwm4 Tainted: G     U     OE     5.5.0-rc2-1-mainline #1
Dec 26 10:18:17 shockwave kernel: Hardware name: LENOVO 80TU/Torronto 4C2, BIOS 3JCN24WW 12/29/2016
Dec 26 10:18:17 shockwave kernel: RIP: 0010:i915_active_acquire_if_busy+0x5/0x30 [i915]
Dec 26 10:18:17 shockwave kernel: Code: 58 a0 5b cf c0 48 89 83 80 00 00 00 48 89 83 88 00 00 00 48 c7 83 90 00 00 00 00 5b cf c0 5b>
Dec 26 10:18:17 shockwave kernel: RSP: 0018:ffffa48143dcfa40 EFLAGS: 00010246
Dec 26 10:18:17 shockwave kernel: RAX: 0000000000000000 RBX: 0000000000000008 RCX: 0000000000000000
Dec 26 10:18:17 shockwave kernel: RDX: ffff9b1de81cdf80 RSI: ffff9b1e1c61f900 RDI: 0000000000000008
Dec 26 10:18:17 shockwave kernel: RBP: ffff9b1ddbf5f180 R08: ffff9b1ddbf5ea88 R09: ffff9b1de9b23400
Dec 26 10:18:17 shockwave kernel: R10: 0000000000000000 R11: ffff9b1e1c61f3e8 R12: 0000000000000000
Dec 26 10:18:17 shockwave kernel: R13: ffff9b1de81cdf80 R14: 0000000000000008 R15: ffff9b1ddbf5e940
Dec 26 10:18:17 shockwave kernel: FS:  00007f1ddc3c5980(0000) GS:ffff9b1e5ac80000(0000) knlGS:0000000000000000
Dec 26 10:18:17 shockwave kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Dec 26 10:18:17 shockwave kernel: CR2: 0000000000000008 CR3: 00000004dbf1a004 CR4: 00000000003606e0
Dec 26 10:18:17 shockwave kernel: Call Trace:
Dec 26 10:18:17 shockwave kernel:  i915_active_acquire+0x14/0x70 [i915]
Dec 26 10:18:17 shockwave kernel:  i915_active_ref+0x21/0x180 [i915]
Dec 26 10:18:17 shockwave kernel:  ? intel_fbc_deactivate+0x19/0x60 [i915]
Dec 26 10:18:17 shockwave kernel:  i915_vma_move_to_active+0x64/0xe0 [i915]
Dec 26 10:18:17 shockwave kernel:  i915_gem_do_execbuffer+0xd35/0x17c0 [i915]
Dec 26 10:18:17 shockwave kernel:  i915_gem_execbuffer2_ioctl+0x1df/0x3d0 [i915]
Dec 26 10:18:17 shockwave kernel:  ? _raw_spin_lock_irqsave+0x26/0x50
Dec 26 10:18:17 shockwave kernel:  ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]
Dec 26 10:18:17 shockwave kernel:  drm_ioctl_kernel+0xb2/0x100 [drm]
Dec 26 10:18:17 shockwave kernel:  drm_ioctl+0x209/0x360 [drm]
Dec 26 10:18:17 shockwave kernel:  ? i915_gem_execbuffer_ioctl+0x2e0/0x2e0 [i915]
Dec 26 10:18:17 shockwave kernel:  do_vfs_ioctl+0x4b7/0x730
Dec 26 10:18:17 shockwave kernel:  ksys_ioctl+0x5e/0x90
Dec 26 10:18:17 shockwave kernel:  __x64_sys_ioctl+0x16/0x20
Dec 26 10:18:17 shockwave kernel:  do_syscall_64+0x4e/0x150
Dec 26 10:18:17 shockwave kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Dec 26 10:18:17 shockwave kernel: RIP: 0033:0x7f1ddd3bc25b
Dec 26 10:18:17 shockwave kernel: Code: 0f 1e fa 48 8b 05 25 9c 0c 00 64 c7 00 26 00 00 00 48 c7 c0 ff ff ff ff c3 66 0f 1f 44 00 00>
Dec 26 10:18:17 shockwave kernel: RSP: 002b:00007ffd0118f018 EFLAGS: 00000246 ORIG_RAX: 0000000000000010
Dec 26 10:18:17 shockwave kernel: RAX: ffffffffffffffda RBX: 00007ffd0118f060 RCX: 00007f1ddd3bc25b
Dec 26 10:18:17 shockwave kernel: RDX: 00007ffd0118f060 RSI: 0000000040406469 RDI: 000000000000000a
Dec 26 10:18:17 shockwave kernel: RBP: 0000000040406469 R08: 00005586d3613d30 R09: 0000000000000000

Last edited by estepan (2019-12-26 18:28:43)

Offline

#77 2019-12-26 13:48:36

loqs
Member
Registered: 2014-03-06
Posts: 9,601

Re: i915 Skylake GPU hangs with kernel 5.3.11

@estepan https://gitlab.freedesktop.org/drm/inte … -i915-bugs as the backtrace you posted appears distinct to me.
Please also use code tags for commands and their outputs

Offline

#78 2019-12-30 14:46:30

loqs
Member
Registered: 2014-03-06
Posts: 9,601

Re: i915 Skylake GPU hangs with kernel 5.3.11

https://lore.kernel.org/stable/20191230 … co.uk/T/#u
Edit:
Excluding whitespace changes this seems the same as https://bbs.archlinux.org/viewtopic.php … 7#p1878327 which did not work.

Last edited by loqs (2019-12-30 14:49:54)

Offline

#79 2019-12-30 22:21:21

joanbrugueram
Member
Registered: 2018-11-12
Posts: 7

Re: i915 Skylake GPU hangs with kernel 5.3.11

loqs wrote:

this seems the same as [...] which did not work.

As far as I can see from this thread, no one reported problems with the patch (though also no one did solidly confirm that it fixes the problem). Am I missing something or is there any other source you're getting this from?

Last edited by joanbrugueram (2019-12-30 22:21:58)

Offline

#80 2019-12-30 22:32:41

loqs
Member
Registered: 2014-03-06
Posts: 9,601

Re: i915 Skylake GPU hangs with kernel 5.3.11

I thought wioo experienced the issue with the patch in post #60.

Offline

#81 2019-12-30 22:44:56

joanbrugueram
Member
Registered: 2018-11-12
Posts: 7

Re: i915 Skylake GPU hangs with kernel 5.3.11

loqs wrote:

I thought wioo experienced the issue with the patch in post #60.

Oops, you're right, not sure how I missed that. No problems so far from my side, but as I said in a previous post, I only got the issue very occasionally.

Offline

#82 2019-12-31 07:25:34

kihra1
Member
Registered: 2019-12-31
Posts: 1

Re: i915 Skylake GPU hangs with kernel 5.3.11

RE: post #76
I've been seeing the same hang since updating to latest on 12/17 (5.4.3 kernel) with i9-9900 /  Intel UHD Graphics 630 using modesetting. Since the graphics gets frozen, it required a hard reboot.  The intel driver was crashing X, which is almost as disruptive.

The system was installed and running 11/21 packages for about a month without issues and it looks like downgrading everything back to 11/21 is working fine for me.

Last edited by kihra1 (2019-12-31 07:26:20)

Offline

#83 2019-12-31 17:41:11

loqs
Member
Registered: 2014-03-06
Posts: 9,601

Re: i915 Skylake GPU hangs with kernel 5.3.11

https://git.archlinux.org/linux.git/com … 527f8ff836
So should be fixed when 5.4.7 is pushed to testing.

Offline

#84 2020-01-01 00:08:44

wioo
Member
Registered: 2017-05-18
Posts: 24

Re: i915 Skylake GPU hangs with kernel 5.3.11

Unfortunately, at least for me, its not. If i'm not mistaken, a patch is the same as the one from post #56.

uname -a

Linux arch 5.4.7-arch1-1 #1 SMP PREEMPT Tue, 31 Dec 2019 17:20:16 +0000 x86_64 GNU/Linux

dmesg

[    1.477246] i915 0000:00:02.0: vgaarb: deactivate vga console
[    1.477943] i915 0000:00:02.0: Direct firmware load for i915/gvt/vid_0x8086_did_0x191b_rid_0x06.golden_hw_state failed with error -2
[    1.494233] i915 0000:00:02.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem
[    1.494595] [drm] Finished loading DMC firmware i915/skl_dmc_ver1_27.bin (v1.27)
[    1.526148] [drm] Initialized i915 1.6.0 20190822 for 0000:00:02.0 on minor 0
[    1.534047] fbcon: i915drmfb (fb0) is primary device
[    1.562550] i915 0000:00:02.0: fb0: i915drmfb frame buffer device
[    1.592973] i915 0000:00:02.0: MDEV: Registered
[    4.141026] snd_hda_intel 0000:00:1f.3: bound 0000:00:02.0 (ops i915_audio_component_bind_ops [i915])
[18279.687354] i915 0000:00:02.0: GPU HANG: ecode 9:1:0x00000000, hang on rcs0
[18279.687360] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[18279.688378] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18279.689165] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
[18279.689438] i915 0000:00:02.0: Resetting chip for hang on rcs0
[18279.691237] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
[18279.692024] [drm:gen8_reset_engines [i915]] *ERROR* rcs0 reset request timed out: {request: 00000001, RESET_CTL: 00000001}
[18289.713848] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18294.620520] Asynchronous wait on fence i915:compton[685]:13e64a timed out (hint:intel_atomic_commit_ready+0x0/0x50 [i915])
[18297.607150] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18299.527191] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18301.660486] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18303.580479] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18305.713799] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18307.633804] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18309.553793] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18311.687119] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18313.607118] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18315.527080] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18317.660420] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18319.580431] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18321.713746] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18323.636990] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18325.553742] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18327.687072] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18329.607062] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18331.527026] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18333.660375] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18335.580381] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18337.713698] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18339.633703] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18341.553687] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18343.687001] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18345.607010] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18347.527003] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18349.660316] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18351.580321] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
[18353.713634] i915 0000:00:02.0: GPU recovery timed out, cancelling all in-flight rendering.
[18353.713952] i915 0000:00:02.0: Resetting chip for hang on rcs0
[18361.606948] i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

Oh and happy new year to everyone.

Last edited by wioo (2020-01-01 00:14:18)

Offline

#85 2020-01-01 01:37:18

loqs
Member
Registered: 2014-03-06
Posts: 9,601

Re: i915 Skylake GPU hangs with kernel 5.3.11

wioo thank you for testing could you report your findings to https://gitlab.freedesktop.org/drm/intel/issues/673 possibly including the output of dmesg from a boot with the options drm.debug=0x1e log_buf_len=1M
Edit:
Oh also please mention the patch was applied it was not in 5.4.7 but added the arch kernel maintainers.

Last edited by loqs (2020-01-01 01:58:28)

Offline

#86 2020-01-01 12:19:38

wioo
Member
Registered: 2017-05-18
Posts: 24

Re: i915 Skylake GPU hangs with kernel 5.3.11

Offline

#87 2020-01-03 17:32:36

E3LDDfrK
Member
Registered: 2019-10-24
Posts: 10

Re: i915 Skylake GPU hangs with kernel 5.3.11

Same problem with linux 5.4.7-arch1-1. Unless it's already fixed for others, then perhaps it's a different problem. There's a bunch of "Resetting rcs0 for no progress on rcs0" in journalctl, and it hangs once per day now. I don't use the laptop that much, perhaps it can happen more often.

The laptop is Thinkpad X390, Intel UHD 620. Fresh install.  I don't have xf86-video-intel.
I enabled the early KMS, but did not enable GuC / HuC firmware loading. https://wiki.archlinux.org/index.php/In … cs#Loading

For now I'll follow the suggestion to disable "Use hardware acceleration when available" in chromium. And try the linux-lts later.

Last edited by E3LDDfrK (2020-01-03 17:41:47)

Offline

#88 2020-01-04 20:08:40

jmandawg
Member
Registered: 2011-10-19
Posts: 22

Re: i915 Skylake GPU hangs with kernel 5.3.11

I'm having the same issue as well, no fix yet?

Offline

#89 2020-01-04 21:30:18

loqs
Member
Registered: 2014-03-06
Posts: 9,601

Re: i915 Skylake GPU hangs with kernel 5.3.11

No one has reported the issue under 5.5-rc4.  For 5.4.Y you could trying pinging @ickle on https://gitlab.freedesktop.org/drm/intel/issues/673

Offline

#90 2020-01-06 13:21:04

tpfkanep
Member
From: South Africa
Registered: 2009-12-15
Posts: 100

Re: i915 Skylake GPU hangs with kernel 5.3.11

Opera caused a system crash with hardware acceleration disabled a few days ago:

Jan 01 04:43:30 arch64 systemd-coredump[131387]: Process 99788 (opera) of user 1000 dumped core.
                                                 
                                                 Stack trace of thread 99788:
                                                 #0  0x0000557d61dd5b3f n/a (opera + 0x1ebcb3f)
                                                 #1  0x0000557d64aeffa2 n/a (opera + 0x4bd6fa2)
                                                 #2  0x0000557d64aee7c5 n/a (opera + 0x4bd57c5)
                                                 #3  0x0000557d63a98d70 n/a (opera + 0x3b7fd70)
                                                 #4  0x0000557d61f8c5b8 n/a (opera + 0x20735b8)
                                                 #5  0x0000557d61f8c6ee n/a (opera + 0x20736ee)
                                                 #6  0x0000557d61e90d88 n/a (opera + 0x1f77d88)
                                                 #7  0x0000557d627b4533 n/a (opera + 0x289b533)
                                                 #8  0x0000557d627b5fe2 n/a (opera + 0x289cfe2)
                                                 #9  0x0000557d627b1abf n/a (opera + 0x2898abf)
                                                 #10 0x0000557d63faea9e n/a (opera + 0x4095a9e)
                                                 #11 0x0000557d655b6d1c n/a (opera + 0x569dd1c)
                                                 #12 0x0000557d63fad391 n/a (opera + 0x4094391)
                                                 #13 0x0000557d6189fea4 ChromeMain (opera + 0x1986ea4)
                                                 #14 0x00007f86758f5153 __libc_start_main (libc.so.6 + >
                                                 #15 0x0000557d6168f02a _start (opera + 0x177602a)
                                                 
                                                 Stack trace of thread 99814:
                                                 #0  0x00007f8676f0ac45 pthread_cond_wait@@GLIBC_2.3.2 >
                                                 #1  0x0000557d6407e392 n/a (opera + 0x4165392)
                                                 #2  0x0000557d6407ea71 n/a (opera + 0x4165a71)
                                                 #3  0x0000557d6407e81f n/a (opera + 0x416581f)
                                                 #4  0x0000557d63ff77e4 n/a (opera + 0x40de7e4)
                                                 #5  0x0000557d64037379 n/a (opera + 0x411e379)
                                                 #6  0x0000557d64013a58 n/a (opera + 0x40faa58)
                                                 #7  0x0000557d64049ebf n/a (opera + 0x4130ebf)
                                                 #8  0x0000557d64081cce n/a (opera + 0x4168cce)
                                                 #9  0x00007f8676f044cf start_thread (libpthread.so.0 +>
                                                 #10 0x00007f86759cd2d3 __clone (libc.so.6 + 0xff2d3)

Today, another crash from logging out of LXDE session to TTY:

Jan 06 15:05:17 arch64 kernel: BUG: kernel NULL pointer dereference, address: 0000000000000008
Jan 06 15:05:17 arch64 kernel: #PF: supervisor read access in kernel mode
Jan 06 15:05:17 arch64 kernel: #PF: error_code(0x0000) - not-present page
Jan 06 15:05:17 arch64 kernel: PGD 0 P4D 0 
Jan 06 15:05:17 arch64 kernel: Oops: 0000 [#1] PREEMPT SMP NOPTI
Jan 06 15:05:17 arch64 kernel: CPU: 2 PID: 851 Comm: Xorg Not tainted 5.4.8-zen1-1-zen #1
Jan 06 15:05:17 arch64 kernel: Hardware name: MSI MS-7A15/H110M PRO-VH PLUS (MS-7A15), BIOS 1.A0 03/19/>
Jan 06 15:05:17 arch64 kernel: RIP: 0010:set_root+0x27/0xd0
Jan 06 15:05:17 arch64 kernel: Code: 00 00 00 0f 1f 44 00 00 55 65 48 8b 04 25 00 5d 01 00 48 89 e5 41 >
Jan 06 15:05:17 arch64 kernel: RSP: 0018:ffffaffa806ab5d8 EFLAGS: 00010202
Jan 06 15:05:17 arch64 kernel: RAX: ffff8a89955f9cc0 RBX: ffffaffa806ab720 RCX: 0000000000000000
Jan 06 15:05:17 arch64 kernel: RDX: 0000000000000001 RSI: 0000000000000041 RDI: ffffaffa806ab720
Jan 06 15:05:17 arch64 kernel: RBP: ffffaffa806ab5f0 R08: ffff8a89a61668c0 R09: ffff8a89a41cac00
Jan 06 15:05:17 arch64 kernel: R10: 0000000000000000 R11: ffff8a89a41cac00 R12: 0000000000000000
Jan 06 15:05:17 arch64 kernel: R13: ffff8a89a58eb020 R14: 0000000000000040 R15: 000000007fffffff
Jan 06 15:05:17 arch64 kernel: FS:  00007ff7e1a7adc0(0000) GS:ffff8a89a7300000(0000) knlGS:000000000000>
Jan 06 15:05:17 arch64 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 06 15:05:17 arch64 kernel: CR2: 0000000000000008 CR3: 000000011680a001 CR4: 00000000003606e0
Jan 06 15:05:17 arch64 kernel: Call Trace:
Jan 06 15:05:17 arch64 kernel:  path_init+0x22a/0x3b0
Jan 06 15:05:17 arch64 kernel:  path_openat+0x80/0x1910
Jan 06 15:05:17 arch64 kernel:  ? _raw_read_unlock_irqrestore+0x1a/0x30
Jan 06 15:05:17 arch64 kernel:  ? ep_poll_callback+0x28b/0x2b0
Jan 06 15:05:17 arch64 kernel:  ? __wake_up_common+0x71/0x1b0
Jan 06 15:05:17 arch64 kernel:  do_filp_open+0xcc/0x170
Jan 06 15:05:17 arch64 kernel:  filp_open+0xf1/0x1c0
Jan 06 15:05:17 arch64 kernel:  kernel_read_file_from_path+0x2c/0x70
Jan 06 15:05:17 arch64 kernel:  _request_firmware+0x47e/0xa30
Jan 06 15:05:17 arch64 kernel:  request_firmware+0x33/0x50
Jan 06 15:05:17 arch64 kernel:  edid_load+0x2d8/0x3a0 [drm]
Jan 06 15:05:17 arch64 kernel:  drm_load_edid_firmware+0xf9/0x150 [drm]
Jan 06 15:05:17 arch64 kernel:  ? kmalloc_array+0x20/0x20 [drm]
Jan 06 15:05:17 arch64 kernel:  drm_do_get_edid+0x94/0x3b0 [drm]
Jan 06 15:05:17 arch64 kernel:  drm_get_edid+0x6b/0x840 [drm]
Jan 06 15:05:17 arch64 kernel:  intel_dp_detect+0x5eb/0x690 [i915]
Jan 06 15:05:17 arch64 kernel:  drm_helper_probe_single_connector_modes+0x146/0x770 [drm_kms_helper]
Jan 06 15:05:17 arch64 kernel:  ? ___preempt_schedule+0x16/0x20
Jan 06 15:05:17 arch64 kernel:  drm_client_modeset_probe+0x272/0x3020 [drm]
Jan 06 15:05:17 arch64 kernel:  ? intel_atomic_commit+0x289/0x2c0 [i915]
Jan 06 15:05:17 arch64 kernel:  ? drm_modeset_drop_locks+0x40/0x50 [drm]
Jan 06 15:05:17 arch64 kernel:  ? drm_client_modeset_commit_atomic+0x150/0x270 [drm]
Jan 06 15:05:17 arch64 kernel:  ? drm_fb_helper_hotplug_event.part.0+0x82/0x150 [drm_kms_helper]
Jan 06 15:05:17 arch64 kernel:  drm_fb_helper_hotplug_event.part.0+0x82/0x150 [drm_kms_helper]
Jan 06 15:05:17 arch64 kernel:  drm_fb_helper_restore_fbdev_mode_unlocked+0x75/0xa0 [drm_kms_helper]
Jan 06 15:05:17 arch64 kernel:  intel_fbdev_restore_mode+0x30/0x70 [i915]
Jan 06 15:05:17 arch64 kernel:  drm_release+0xe7/0x110 [drm]
Jan 06 15:05:17 arch64 kernel:  __fput+0xb3/0x230
Jan 06 15:05:17 arch64 kernel:  task_work_run+0x7f/0xa0
Jan 06 15:05:17 arch64 kernel:  do_exit+0x2d0/0xb50
Jan 06 15:05:17 arch64 kernel:  ? syscall_trace_enter+0x1a7/0x2f0
Jan 06 15:05:17 arch64 kernel:  do_group_exit+0x3a/0xa0
Jan 06 15:05:17 arch64 kernel:  __x64_sys_exit_group+0x14/0x20
Jan 06 15:05:17 arch64 kernel:  do_syscall_64+0x48/0x130
Jan 06 15:05:17 arch64 kernel:  entry_SYSCALL_64_after_hwframe+0x44/0xa9
Jan 06 15:05:17 arch64 kernel: RIP: 0033:0x7ff7e2897ce6
Jan 06 15:05:17 arch64 kernel: Code: Bad RIP value.
Jan 06 15:05:17 arch64 kernel: RSP: 002b:00007ffc55c25358 EFLAGS: 00000246 ORIG_RAX: 00000000000000e7
Jan 06 15:05:17 arch64 kernel: RAX: ffffffffffffffda RBX: 00007ff7e298d470 RCX: 00007ff7e2897ce6
Jan 06 15:05:17 arch64 kernel: RDX: 0000000000000000 RSI: 000000000000003c RDI: 0000000000000000
Jan 06 15:05:17 arch64 kernel: RBP: 0000000000000000 R08: 00000000000000e7 R09: ffffffffffffff80
Jan 06 15:05:17 arch64 kernel: R10: 000000000000004d R11: 0000000000000246 R12: 00007ff7e298d470
Jan 06 15:05:17 arch64 kernel: R13: 00000000000000d0 R14: 00007ff7e2990e68 R15: 0000000000000000
Jan 06 15:05:17 arch64 kernel: Modules linked in: fuse hid_logitech_hidpp input_leds hid_logitech_dj hi>
Jan 06 15:05:17 arch64 kernel: CR2: 0000000000000008
Jan 06 15:05:17 arch64 kernel: ---[ end trace f4439dd69bf0be67 ]---
Jan 06 15:05:17 arch64 kernel: RIP: 0010:set_root+0x27/0xd0
Jan 06 15:05:17 arch64 kernel: Code: 00 00 00 0f 1f 44 00 00 55 65 48 8b 04 25 00 5d 01 00 48 89 e5 41 >
Jan 06 15:05:17 arch64 kernel: RSP: 0018:ffffaffa806ab5d8 EFLAGS: 00010202
Jan 06 15:05:17 arch64 kernel: RAX: ffff8a89955f9cc0 RBX: ffffaffa806ab720 RCX: 0000000000000000
Jan 06 15:05:17 arch64 kernel: RDX: 0000000000000001 RSI: 0000000000000041 RDI: ffffaffa806ab720
Jan 06 15:05:17 arch64 kernel: RBP: ffffaffa806ab5f0 R08: ffff8a89a61668c0 R09: ffff8a89a41cac00
Jan 06 15:05:17 arch64 kernel: R10: 0000000000000000 R11: ffff8a89a41cac00 R12: 0000000000000000
Jan 06 15:05:17 arch64 kernel: R13: ffff8a89a58eb020 R14: 0000000000000040 R15: 000000007fffffff
Jan 06 15:05:17 arch64 kernel: FS:  00007ff7e1a7adc0(0000) GS:ffff8a89a7300000(0000) knlGS:000000000000>
Jan 06 15:05:17 arch64 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 06 15:05:17 arch64 kernel: CR2: 00007ff7e2897cbc CR3: 000000011680a001 CR4: 00000000003606e0
Jan 06 15:05:17 arch64 kernel: Fixing recursive fault but reboot is needed!
Jan 06 15:05:17 arch64 kernel: ------------[ cut here ]------------
Jan 06 15:05:17 arch64 kernel: WARNING: CPU: 2 PID: 851 at kernel/rcu/tree_plugin.h:293 rcu_note_contex>
Jan 06 15:05:17 arch64 kernel: Modules linked in: fuse hid_logitech_hidpp input_leds hid_logitech_dj hi>
Jan 06 15:05:17 arch64 kernel: CPU: 2 PID: 851 Comm: Xorg Tainted: G      D           5.4.8-zen1-1-zen >
Jan 06 15:05:17 arch64 kernel: Hardware name: MSI MS-7A15/H110M PRO-VH PLUS (MS-7A15), BIOS 1.A0 03/19/>
Jan 06 15:05:17 arch64 kernel: RIP: 0010:rcu_note_context_switch+0x45/0x550
Jan 06 15:05:17 arch64 kernel: Code: c3 40 96 02 00 e8 ab 2a 3f 00 89 c0 48 03 1c c5 c0 76 31 8e 0f 1f >
Jan 06 15:05:17 arch64 kernel: RSP: 0018:ffffaffa806abde0 EFLAGS: 00010002
Jan 06 15:05:17 arch64 kernel: RAX: 0000000000000002 RBX: ffff8a89a7329640 RCX: 0000000000000000
Jan 06 15:05:17 arch64 kernel: RDX: ffff8a89955f9cc0 RSI: ffffffff8d9fc823 RDI: 0000000000000000
Jan 06 15:05:17 arch64 kernel: RBP: ffff8a89955f9cc0 R08: 0000000000000773 R09: ffffaffab089d728
Jan 06 15:05:17 arch64 kernel: R10: 0000000000aaaaaa R11: 0000000000000000 R12: 0000000000000001
Jan 06 15:05:17 arch64 kernel: R13: 0000000000000000 R14: ffff8a89955f9cc0 R15: 0000000000000000
Jan 06 15:05:17 arch64 kernel: FS:  00007ff7e1a7adc0(0000) GS:ffff8a89a7300000(0000) knlGS:000000000000>
Jan 06 15:05:17 arch64 kernel: CS:  0010 DS: 0000 ES: 0000 CR0: 0000000080050033
Jan 06 15:05:17 arch64 kernel: CR2: 00007ff7e2897cbc CR3: 000000011680a001 CR4: 00000000003606e0
Jan 06 15:05:17 arch64 kernel: Call Trace:
Jan 06 15:05:17 arch64 kernel:  ? do_exit.cold+0xbc/0xc1
Jan 06 15:05:17 arch64 kernel:  __schedule+0x8d/0xf70
Jan 06 15:05:17 arch64 kernel:  ? do_exit.cold+0xbc/0xc1
Jan 06 15:05:17 arch64 kernel:  schedule+0x83/0x200
Jan 06 15:05:17 arch64 kernel:  do_exit.cold+0xbc/0xc1
Jan 06 15:05:17 arch64 kernel:  ? do_group_exit+0x3a/0xa0
Jan 06 15:05:17 arch64 kernel:  rewind_stack_do_exit+0x17/0x20
Jan 06 15:05:17 arch64 kernel: ---[ end trace f4439dd69bf0be68 ]---

Edit: 5.4.8-zen1-1-zen kernel

Last edited by tpfkanep (2020-01-06 13:21:59)

Offline

#91 2020-01-08 14:59:02

derpda
Member
Registered: 2020-01-08
Posts: 1

Re: i915 Skylake GPU hangs with kernel 5.3.11

I am on 5.4.8-arch1-1 on a Lenovo ThinkPad X1 Carbon Gen7 and can confirm the error still persists.

i915 0000:00:02.0: Resetting rcs0 for stuck wait on rcs0

Edit:
I have so far only seen it when running Electron apps like VSCode and Slack.
Turning off the GPU acceleration with "code --disable-gpu" did not alleviate the issue.
Sometimes hard, sometimes soft freeze.

Last edited by derpda (2020-01-08 15:02:37)

Offline

#92 2020-01-08 15:44:19

CarbonChauvinist
Member
Registered: 2012-06-16
Posts: 206

Re: i915 Skylake GPU hangs with kernel 5.3.11

A little reticent to add to all the "me too" posts - but I can say that I've been running linux-drm-tip-git and have not encountered the hang since changing. It's my understanding that we won't see a real fix in the standard repos until 5.5?


"the wind-blown way, wanna win? don't play"

Offline

#93 2020-01-08 17:15:39

loqs
Member
Registered: 2014-03-06
Posts: 9,601

Re: i915 Skylake GPU hangs with kernel 5.3.11

The fix according to upstream has already been applied but is not working and there has been no response from upstream to reports the backport is not enough.
If the next linux-lts is 5.4 then the issue will move from linux to linux-lts.

Offline

#94 2020-01-10 10:49:08

drag0nius
Member
Registered: 2013-04-20
Posts: 6

Re: i915 Skylake GPU hangs with kernel 5.3.11

I've the same issue on 5.4.10-arch1-1

Offline

#95 2020-01-10 13:10:57

samurai
Member
From: Turkey
Registered: 2010-04-03
Posts: 25

Re: i915 Skylake GPU hangs with kernel 5.3.11

It is weird that such a critical bug still not get fixed.

When will 5.4 be the next lts?

Offline

#96 2020-01-10 13:25:46

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 8,382

Re: i915 Skylake GPU hangs with kernel 5.3.11

It already is.

For Arch it should happen when we move on to 5.5 for linux, but then it should be fixed at least there, if I've followed the progress correctly.

Offline

#97 2020-01-10 17:52:11

xargsgrep
Member
Registered: 2020-01-02
Posts: 1

Re: i915 Skylake GPU hangs with kernel 5.3.11

mainline (5.5rc5-1) seems to have fixed the issue for me. i used to get gpu hangs pretty much every day and i haven't experienced one in almost 4 days now.

Last edited by xargsgrep (2020-01-10 17:53:03)

Offline

#98 2020-01-12 16:04:35

Kotrfa
Member
Registered: 2012-10-25
Posts: 173

Re: i915 Skylake GPU hangs with kernel 5.3.11

That sounds promising. I am still on `5.4.10.arch1-1` and it's super annoying. Any ETA when 5.5 is out officially?

Offline

#99 2020-01-12 19:46:19

loqs
Member
Registered: 2014-03-06
Posts: 9,601

Re: i915 Skylake GPU hangs with kernel 5.3.11

Kotrfa wrote:

That sounds promising. I am still on `5.4.10.arch1-1` and it's super annoying. Any ETA when 5.5 is out officially?

http://phb-crystal-ball.org/
Edit:
5.4.12-arch1 dropped 'drm/i915/gt: Detect if we miss WaIdleLiteRestore'

Last edited by loqs (2020-01-15 13:24:20)

Offline

#100 2020-01-16 11:49:23

sherifnagy
Member
Registered: 2020-01-16
Posts: 1

Re: i915 Skylake GPU hangs with kernel 5.3.11

loqs wrote:
Kotrfa wrote:

That sounds promising. I am still on `5.4.10.arch1-1` and it's super annoying. Any ETA when 5.5 is out officially?

http://phb-crystal-ball.org/
Edit:
5.4.12-arch1 dropped 'drm/i915/gt: Detect if we miss WaIdleLiteRestore'

I still have the same issue on 5.4.12.a-1-hardened , the patch didn't get carried over to 5.4.12, did it?

Offline

Board footer

Powered by FluxBB